REQUIREMENT ENGINEERING

REQUIREMENT ENGINEERING
DEFINITION:

The process of defining, documenting, and maintaining requirements in

the engineering design process.
 User Requirements

System Requirements
TYPES OF
REQUIREMENTS
Functional Requirements

Non-Functional
Requirements
 0
1 USER REQUIREMENTS
User requirements are statements, in a natural and simple language of what services the
system is expected to provide to system users and the constraints under which it must
operate. The user requirements may vary from broad statements of the system features
required to detailed, precise descriptions of the system functionality.
 0
2
SYSTEM REQUIREMENTS
System requirements is a statement that identifies the functionality that is needed by
a system in order to satisfy the customer’s requirements. System requirements are
more detailed descriptions of the software system’s functions, services, and
operational constraints.
0 FUNCTIONAL
3
REQUIREMENTS
• A functional requirement defines a system or its component.
• It specifies “What should the software system do?”
• Functional requirement is specified by User.
• Helps you verify the functionality of the software
 04 NON-FUNCTIONAL
REQUIREMENTS
• Nonfunctional Requirements defines system attributes.
• The attributes are:
security
reliability
performance
maintainability
scalability
usability.
• Helps you to verify the performance of the software.
• Describes how the product works.
 EXAMPLE
 A system loads a webpage when someone clicks on a
button. The related non-functional requirement specifies
how fast the webpage must load
 REQUIREMENT ENGINEERING
PROCESS
Definition:
“Requirement Engineering is the process of defining ,documenting and maintaining the
requirements .
• It is the description of features and functionalities of the target system.
• It is the description of what the system should do.

STEPS:
It is a four step process, which includes:
1. Feasibility study
2. Requirement Elicitation and Analysis
3. Software Requirement Specification
4. Software Requirement Validation
Key Activity Of RE
 Feasibility Study
Definition:
Studying the possibilities to do some task in every manner is known as feasibility
study.
Types:
1. Economic Feasibility
2. Technical Feasibility
3. Operational Feasibility
 REQUIREMENT ELICATION AND
ANALYSIS
 It is a process of Requirement Gathering of a system from users, customers, and
other stakeholders.

Requirements Elicitation Techniques:

There are a number of requirements elicitation techniques. Few of them are listed
below – 
 Stakeholder Analysis
 Brainstorming
 Document Analysis/Review
 Prototyping
 Survey/Questionnaire
REQUIREMENT SPECIFICATION
Definition:
A software requirements specification (SRS) is a document that describes what
the software will do and how it will be expected to perform.

It lays out the functional and non-functional requirements of the software to be

developed.

It may include a set of use cases that describe user interactions that the software
must provide to the user for perfection interaction.
 SRS STRUCTURE
1. Introduction
1.1 Purpose
1.2 Intended Audience
1.3 Scope
1.4 Definitions
1.5 References
2. Overall description
2.1 User Interfaces
2.2 System Interfaces
2.3 Constraints
2.4 User Characteristics
 SYSTEM FEATURES AND
REQUIREMENTS
1. Functional Requirements
2. Use Cases
3. Non-Functional Requirement
 REQUIREMENT VALIDATION
Requirements validation is the process of checking that requirements define the system
that the customer really wants. It overlaps with elicitation and analysis, as it is
concerned with finding problems with the requirements.

Requirements validation is critically important because errors in a requirements

document can lead to extensive rework costs when these problems are discovered during
development or after the system is in service

The cost of fixing a requirements problem by making a system change is usually much
greater than repairing design or coding errors. A change to the requirements usually
means that the system design and implementation must also be changed.
 Checks In Validation Process
During the requirements validation process, different types of checks should be
carried out on the requirements in the requirements document. These checks
include:
1. Validity checks
2. Consistency checks
3. Completeness checks
4. Realism checks
5. Verifiability
 Techniques In Validation Process
A number of requirements validation techniques can be used individually or in
conjunction with one another:

1. Requirements reviews.
2. Prototyping.
3. Test-case generation.
 REQUIREMENT MANAGEMENT
Requirement management is the process of managing changing in requirements during
requirement engineering process and system development.

New requirements is emerge as a system is being developed and after it has gone into
use.

You need to keep track of individual requirements and maintain links between dependent
requirements so that you can access the impact of requirement changes.
 Reason For Changing Requirements
 The business and technical environment of the system always changes after
installation.

 The people who pay for a system and the users of that system are rarely the same
people.

 Large systems usually have a diverse stakeholder community, with stakeholders

having different requirements. Their priorities may be conflicting or contradictory.
 Requirement Management Planning
Requirements management planning is concerned with establishing how a set of
evolving requirements will be managed. During the planning stage, you have to decide
on a number of issues:

1. Requirements identification
2. A change management process
3. Traceability policies
4. Tool support
 Requirement Change Management
Requirements change management should be applied to all proposed changes to a
system’s requirements after the requirements document has been approved.
There are three principal stages to a change management process:

1. Problem analysis and change specification

2. Change analysis and costing
3. Change implementation
THANK YOU