Recently, a lot of research efforts in software engineering have focused on integrating organizational modeling as a key piece in requirements engineering. In these research works, the business models are proposed as the source of the software requirements specification process. However, the majority of these works focus only on the definition of notations that permit the representation of the ...

Faulty requirements specifications lead to developing a faulty software system. This may require repeating the whole software engineering cycle wasting time and money. This paper presents an interactive semi-automated system that is a compromise between two approaches. The first tries to avoid the introduction of imprecision while the software requirements are being written. The other attempts ...

This paper surveys and evaluates techniques for eliciting requirements of computer-based systems, paying particular attention to how they deal with social issues. The methods surveyed include introspection, interviews, questionnaires, and protocol, conversation, interaction, and discourse analyses. Although they are relatively untried in Requirements Engineering, we believe there is much promis...

This paper presents a review on the Business/IT alignment with the goal of exploring how requirements engineering can help model business environment and how business environment can help perform requirements engineering tasks in order to develop a system which meets business expectations. It discusses ten lessons learned from the Business/IT alignment research area in the context of requiremen...

Context: Ethics have broad applications in different fields of study and contexts. Like other study, ethics a significant impact on the decisions made computing concerning software artifact production its processes. Hence, this research, is considered context requirements engineering during development process. Objective: The aim paper to discuss investigation results regarding ethical problems...

Requirements engineering process usually is supported by certain tools. The choice of the tools may depend on several organizational and personal factors and can result in a large set of tools and the necessity to move requirements engineering artifacts from one tool to others continuously. In this paper the hypothesis that it is preferable to limit the number of the tools in use is discussed. ...

One of the challenges of requirements engineers is to understand domain issues and elicit requirements effectively. One of the possible strategies is to perform a manual inspection of similar projects to quickly gain leverage of domain concepts underlying the projects. However, this task is time-consuming and limited to the projects at hand. To ensure comprehensive elicitation using more widely...

When software development teams modify their requirements engineering process as an independent variable, they often examine the implications of these process changes by assessing the quality of the products of the requirements engineering process, e.g., a software requirements specification (SRS). Using the quality of the SRS as the dependent variable is flawed. As an alternative, this paper p...