What are the Requirement Engineering Tasks ?

The process to gather the software requirements from client, analyze and document them is known as requirement engineering. The goal of requirement engineering is to develop and maintain sophisticated and descriptive ‘System Requirements Specification’ document. Requirement engineering constructs a bridge for design and construction. The Requirement engineering consists various tasks, which are as follows :

1. Inception :- Inception is a task where the requirement engineering asks a set of questions to establish a software process. software engineers use context-free questions to establish a basic understanding of the problem, the people who want a solution, the nature of the solution, and the effectiveness of the collaboration between customers and developers.

2. Elicitation :- In elicitation the software engineers need to find out from customers what the product objectives are, what is to be done, how the product fits into business needs, and how the product is used on a day to day basis. The requirements are difficult because the following problems occur in elicitation :

3. Problem of scope :- The customer give the unnecessary technical detail rather than clarity of the overall system objective.

4. Problem of understanding :- Poor understanding between the customer and the developer regarding various aspect of the project like capability, limitation of the computing environment.

5. Problem of volatility :- In this problem, the requirements change from time to time and it is difficult while developing the project.

6. Elaboration :-  In this task, the information taken from user during inception and elaboration and are expanded and refined in elaboration. In this phase the main focus is on developing a refined model of software functions, features and constraints. This is an analysis phase. It defines the functional, informational and behavioral constraints of the problem domain.

4. Negotiation :- In negotiation, a software engineer decides the how will the  project be achieved with limited business resources. In this phase requirements are categorized and organized into subsets, relations among requirements identified, requirements reviewed for correctness, requirements prioritized based on customer needs.

5. Specification :- In specification task, the requirement engineer constructs a final work product. The work product is in the form of software requirement specification. In this task, formalize the requirement of the proposed software such as informative, functional and behavioral. The requirement are formalize in both graphical and textual formats.

6. Requirement Validation :- In this task, the specification is examined to ensure that all the software requirements have been stated unambiguously and errors have been detected and corrected. The formal technical reviews from the software engineer, customer and other stakeholders helps for the primary requirements validation mechanism.

7. Requirement Management :- Requirement management is a set of activities that help the project team to identify, control and track the requirements and changes can be made to the requirements at any time of the ongoing project. These tasks start with the identification and assign a unique identifier to each of the requirement. After finalizing the requirement traceability table is developed. The examples of traceability table are the features, sources, dependencies, subsystems and interface of the requirement.

Next Topic :

No comments:

Post a Comment