Done, your profile is created.Finish your profile by filling in the following fields
Forgot Password Earn Money,Free Notes
Password sent to your Email Id, Please Check your Mail
Updating Cart........ Please Wait........
What is REQUIREMENT ENGINEERING
The process to gather the software requirements from client, analyze and document them is known as requirement engineering.| Download free ppt
1. What is requirement engineering?
2. Goal of requirement engineering
3. Requirement engineering process
4. Requirement engineering activities
5. What is requirement elicitation?
6. Requirement elicitation process
7. Requirement elicitation techniques
8. Requirements specification
9. Requirement analysis
10. Requirement management
11. Requirement validationWHAT IS REQUIREMENT
“ 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
It is a four step process, which
▫Software Requirement Specification
▫Software Requirement Validation1. Feasibility study
It explores technical aspects of the project and product
such as usability, maintainability, productivity and
The output of this phase should be a feasibility study
report that should contain adequate comments and
recommendations for management about whether or not
the project should be undertaken.
62. Requirement Gathering
If the feasibility report is positive towards undertaking the
project, next phase starts with gathering requirements from
Analysts and engineers communicate with the client and
end-users to know their ideas on what the software should
provide and which features they want the software to include.
3. Software Requirement Specification
SRS should come up with following features:
User Requirements are expressed in natural language.
Technical requirements are expressed in structured language,
which is used inside the organization.
Design description should be written in Pseudo code.
Format of Forms and GUI screen prints.
Conditional and mathematical notations for DFDs etc.
84. Software Requirement Validation
Requirements can be checked against following conditions –
If they can be practically implemented
If they are valid and as per functionality and domain of software
If there are any ambiguities
If they are complete
If they can be demonstrated
Requirement validationWHAT IS REQUIREMENT
“ Requirements Elicitation is the process to find out the
requirements for an intended software system by
communicating with client, end users, system users and
others who have a stake in the software system
The developers discuss with The developers prioritize and
the client and end users and
arrange the requirements in order
know their expectations from
of importance, urgency and
Negotiation & discussion
If requirements are ambiguous
All formal & informal,
or there are some conflicts in
functional and non-functional
requirements of various
requirements are documented
stakeholders, if they are, it is
and made available for next
then negotiated and discussed
with stakeholders. Requirements
may then be prioritized and
reasonably compromised.REQUIREMENT ELICITATION
There are various ways to discover requirements:-
Interviews are strong medium to collect requirements. Types of interviews such as:
Structured (closed) interviews
Non-structured (open) interviews
Organization may conduct surveys among various
stakeholders by querying about their expectation
and requirements from the upcoming system.
document with pre-defined set of objective
questions and respective options is handed over to
all stakeholders to answer, which are collected
Every software falls into some domain category.
The expert people in the domain can be a great
4. Domain Analysis
help to analyze general and specific requirements.17
Team of engineers and developers may analyze the
5. Task analysis
operation for which the new system is required.
An informal debate is held among various
stakeholders and all their inputs are recorded for
further requirements analysis.
Prototyping is building user interface without adding
detail functionality for user to interpret the features
of intended software product.
Team of experts visit the client‟s organization or
workplace. They observe the actual working of the
existing installed systems.REQUIREMENT SPECIFICATION
A complete Software Requirement Specifications must be:
and resolving stakeholder
to the requirements
as the system is
developed and put