Requirement Engineering Tasks

•  The process of collecting the software requirement from the client then understand, evaluate and document it is called as requirement engineering.
•  Requirement engineering constructs a bridge for design and construction.

It encompasses seven distinct tasks: inception, elicitation, elaboration, negotiation, specification, validation, and management.


1. Inception

1. Inception is a task where the requirement engineering asks a set of questions to establish a software process.
2. In this task, it understands the problem and evaluates with the proper solution.
3. It collaborates with the relationship between the customer and the developer.
4. The developer and customer decide the overall scope and the nature of the question.

2. Elicitation

1.    Elicitation means to find the requirements from anybody.
2.    The requirements are difficult because the following problems occur in elicitation.

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

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

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


3. Elaboration

1. In this task, the information taken from user during inception and elaboration and are expanded and refined in elaboration.
2. Its main task is developing pure model of software using functions, feature and constraints of a software.

4. Negotiation

1. In negotiation task, a software engineer decides the how will the  project be achieved with limited business resources.
2. To create rough guesses of development and access the impact of the requirement on the project cost and delivery time.

5. Specification

1. In this task, the requirement engineer constructs a final work product.
2. The work product is in the form of software requirement specification.
3. In this task, formalize the requirement of the proposed software such as informative, functional and behavioral.
4. The requirements are formalize in both graphical and textual formats.

6. Validation

1. The work product is built as an output of the requirement engineering and that is accessed for the quality through a validation step.
2. The formal technical reviews from the software engineer, customer and other stakeholders helps for the primary requirements validation mechanism.

7. Requirement management

1. It 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.
2. These tasks start with the identification and assign a unique identifier to each of the requirement.
3. After finalizing the requirement traceability table is developed.
4. The examples of traceability table are the features, sources, dependencies, subsystems and interface of the requirement.