Scribd
Upload
227 views2 pages

Inception

This document outlines the key steps in requirements engineering: inception involves understanding the problem and scope with the customer and developer. Elicitation finds requirements but can involve problems of scope, understanding, and volatility. Elaboration expands and refines information from inception and elicitation. Negotiation decides how the project will be achieved given limited resources. Specification constructs a final requirements document formally specifying requirements graphically and textually. Validation assesses the requirements document for quality through reviews. Requirement management identifies, controls, tracks, and traces requirements and changes throughout the project.

Uploaded by

sufiyan irfan
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
227 views2 pages

Inception

This document outlines the key steps in requirements engineering: inception involves understanding the problem and scope with the customer and developer. Elicitation finds requirements but can involve problems of scope, understanding, and volatility. Elaboration expands and refines information from inception and elicitation. Negotiation decides how the project will be achieved given limited resources. Specification constructs a final requirements document formally specifying requirements graphically and textually. Validation assesses the requirements document for quality through reviews. Requirement management identifies, controls, tracks, and traces requirements and changes throughout the project.

Uploaded by

sufiyan irfan
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 2

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 with 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 give 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
In this task, the information taken from user during inception and elaboration and are
expanded and refined in elaboration.
Its main task is developing pure model of software using functions, feature and constraints of
a software.

4. Negotiation
In negotiation task, a software engineer decides the 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 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. 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
helps for 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 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.

You might also like