What are the major task of requirement engineering? Explain.

Requirement Engineering

- The process of collecting the software requirement from the client and then understanding, evaluating, and documenting it is called requirement engineering.

- Requirement engineering constructs a bridge for design and construction.

# Requirement engineering consists of seven different tasks as follows:

1. Inception

- Inception is a task where the requirement engineering asks a set of questions to establish a software process.

- In this task, it understands the problem and evaluates the proper solution.

- It collaborates with the relationship between the customer and the developer.

- The developer and customer decide the overall scope and the nature of the question.


2. Elicitation

- Elicitation means to find the requirements from anybody.

- The requirements are difficult because the following problems occur in elicitation.

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

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

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


3. Elaboration

- In this task, the information is taken from the user during inception and elaboration and is expanded and refined in elaboration.

- Its main task is developing a pure model of software using functions, features, and constraints of the software.


4. Negotiation

- In a negotiation task, a software engineer decides how will the project be achieved with limited business resources.

- To create rough guesses of development and access the impact of the requirement on the project cost and delivery time.


5. Specification

- In this task, the requirement engineer constructs a final work product.

- The work product is in the form of a software requirement specification.

- In this task, formalize the requirement of the proposed software such as informative, functional, and behavioral.

- The requirement is formalized in both graphical and textual formats.


6. Validation

- The work product is built as an output of the requirement engineering and that is accessed for the quality through a validation step.

- The formal technical reviews from the software engineer, customer, and other stakeholders help with the primary requirements validation mechanism.


7. Requirement management

- 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 during the ongoing project.

- These tasks start with the identification and assign a unique identifier to each of the requirements.

- After finalizing the requirement traceability table is developed.

- The examples of the traceability tables are the features, sources, dependencies, subsystems, and interface of the requirement.



Comments

Popular posts from this blog

Suppose that a data warehouse consists of the four dimensions; date, spectator, location, and game, and the two measures, count and charge, where charge is the fee that a spectator pays when watching a game on a given date. Spectators may be students, adults, or seniors, with each category having its own charge rate. a) Draw a star schema diagram for the data b) Starting with the base cuboid [date; spectator; location; game], what specific OLAP operations should perform in order to list the total charge paid by student spectators at GM Place in 2004?

Define Business ethics . Explain its significance.

Short Note on Security Architecture of E-governance