Many applications that are developed do not completely fulfil the requirements of their stakeholders. This can be a result of inadequate requirements elicitation and poorly defined requirements. Many solutions, including model-driven inspired ones, have been proposed to improve the elicitation of the requirements, though many of them are not yet widely used in practice as they require training ...

Problem-based Learning (PBL) is a learning technique that is used for stimulating learners with problematic dilemma and encouraging the learners to solve the problem based on learner’s capability. It is more to learner-centred approach whereby teacher or instructor plays role in guiding them to succeed. This paper enlightens on collaboration activities in e-learning and what element can be cons...

Requirements Elicitation is one of the activities held during the Requirements Engineering stage. Its main goal is to discover the requirements that stakeholders demand on a system-to-be. There are many strategies to conduct this activity, whose success depends on their effectiveness and efficiency in their context of application. This paper presents our PABRE method for conducting the Requirem...

No requirements elicitation technique has capability of finding all of the software requirements so we have to use variety of techniques that will help us to cover all the requirements, resulting in more effective elicitation. Each technique has its features which makes it different from all other techniques and which make it suitable for a particular condition. The important thing is to use th...

In this article we defend the idea that social aspects have strong influence in the software requirements elicitation (Goguen 1993), which drive us to find help in the social sciences. The Activity Theory is a theory developed in the Psychology that focuses the human practices of development process, both the individual and social levels. This theory states that any human action must be underst...

In networked environments, the importance of eliciting security requirements as part of the process of requirements elicitation is increasing. Yet, it is difficult to articulate what security requirements are and how they can be elicited and implemented in the system. Few security requirements elicitation methods deal with the security needs of the end-users in specific contexts towards other e...

Software requirements elicitation is a difficult process with many existing problems, and no single elicitation method solves all these problems. We introduce a new way of looking at the requirements elicitation process. Our model shows the requirements elicitation problem as a process of merging the users’ wants and the users’ needs into the same entity. In the context of our model, existing p...

This paper presents a language called ScreenSpec that can be used to specify screens at requirements elicitation phase. ScreenSpec was successfully applied in 8 real projects. It is very effective: average time needed to specify a screen is 2 minutes, and takes an hour to become proficient in using it. Visual representation generated from ScreenSpec can be attached to requirements specification...