Requirements engineering (RE) is often seen as an essential facet in software development. It is a vital process before each project starts. In the context of systems engineering, an understanding and application of systems theory and practice is also relevant to RE. The contexts in which RE takes place habitually involve human activities. Therefore, RE needs to be sensitive to how people perce...

Requirements engineering (RE) is often seen as an essential facet in software development. It is a vital process before each project starts. In the context of systems engineering, an understanding and application of systems theory and practice is also relevant to RE. The contexts in which RE takes place habitually involve human activities. Therefore, RE needs to be sensitive to how people perce...

Objective:  Presents a business goal-driven requirements engineering approach for IT to better understand system requirements, as requirements are generated from the business goals and provide assistance for analyzing business goals quickly.

Requirements Engineering (RE) contains many different practices to elicit, communicate and document customer requirements. Developers need to understand these requirements properly in order to achieve project success by fulfilling them [1]. A prerequisite for developers’ understanding of relevant requirements and their meaning is successful requirements communication [2]. Therefore, the selecte...

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...

Software Requirements Specification (SRS) is the key documentation, defining the functional and non-functional system requirements. By revisiting a number of in the literature much discussed key aspects related to SRS and extracting essential views from the author’s daily work experience, this papers stresses the importance of the SRS and examines the process, which enables the emergence of a q...

This paper proposes that requirements engineering for COTS-based business systems should be flexible to cater for changes in users’ requirements during the development process. It suggests exposing in real-time the traceability of development activity to user requirements as a key mechanism to facilitate communication between the systems development and user communities. The channels of communi...

The requirements elicited from stakeholders are typically informal, incomplete, ambiguous, and inconsistent. It is the task of Requirements Engineering to transform them into an eligible (formal, sufficiently complete, unambiguous, consistent, modifiable and traceable) requirements specification of functions and qualities that the system-to-be needs to operationalize. To address this requiremen...

User requirements look at the functionality of the software product from the perspectives of the various users of that product. They define what the software has to do in order for the users to accomplish their objectives. In order to fulfill a business requirement, there may be multiple user level requirements. For example, the business requirement to allow the customer to pay for the gas at t...

The primary measure of success of a software system is the level to which it meets the purpose for which it was projected and requirements engineering (RE) is the process of discovering that purpose. The RE process includes five distinct phases: Requirements Elicitation, Requirements Analysis & Negotiation, Requirements Documentation, Requirements Verification & Validation, and Requirements Man...