Scribd
Upload
79 views9 pages

Requirements Engineering

Requirement engineering (RE) refers to the process of defining, documenting, and maintaining requirements in the engineering design process. The key aspects of requirement engineering include understanding customer needs, analyzing feasibility, specifying solutions clearly, and managing requirements as the system is developed. The main steps of the requirement engineering process are: 1) Conducting a feasibility study to evaluate if requirements are acceptable, flexible, and conform to standards. 2) Eliciting and analyzing requirements through methods like interviews and reviewing existing systems to identify inconsistencies and defects. 3) Creating a software requirements specification document to define requirements technically for the development team. 4) Validating requirements to ensure they are practical, correct, unambiguous, and fully

Uploaded by

Harshit Barde
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
79 views9 pages

Requirements Engineering

Requirement engineering (RE) refers to the process of defining, documenting, and maintaining requirements in the engineering design process. The key aspects of requirement engineering include understanding customer needs, analyzing feasibility, specifying solutions clearly, and managing requirements as the system is developed. The main steps of the requirement engineering process are: 1) Conducting a feasibility study to evaluate if requirements are acceptable, flexible, and conform to standards. 2) Eliciting and analyzing requirements through methods like interviews and reviewing existing systems to identify inconsistencies and defects. 3) Creating a software requirements specification document to define requirements technically for the development team. 4) Validating requirements to ensure they are practical, correct, unambiguous, and fully

Uploaded by

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

Topic: Requirements Engineering

P RES E N T ED BY: S H I VA M G RO V E R G U I D ED
BY:
CS 1 8 0 4 9 D R. G A N E SH
RE G U LWA R
 Requirement Engineering

Requirements engineering (RE) refers to the process of defining,


documenting, and maintaining requirements in the engineering design
process. Requirement engineering provides the appropriate mechanism to
understand what the customer desires, analyzing the need, and assessing
feasibility, negotiating a reasonable solution, specifying the solution clearly,
validating the specifications and managing the requirements as they are
transformed into a working system. Thus, requirement engineering is the
disciplined application of proven principles, methods, tools, and notation to
describe a proposed system's intended behavior and its associated
constraints.
 Requirement Engineering Process

1) Feasibility Study
2) Requirement Elicitation and Analysis
3) Software Requirement Specification
4) Software Requirement Validation
5) Software Requirement Management
 Requirement Engineering Process
1. Feasibility Study:
The objective behind the feasibility study is to create the reasons for developing the
software that is acceptable to users, flexible to change and conformable to established
standards.

Types of Feasibility:
1. Technical Feasibility - Technical feasibility evaluates the current technologies, which are
needed to accomplish customer requirements within the time and budget.
2. Operational Feasibility - Operational feasibility assesses the range in which the required
software performs a series of levels to solve business problems and customer requirements.
3. Economic Feasibility - Economic feasibility decides whether the necessary software can
generate financial profits for an organization.
2. Requirement Elicitation and Analysis:
This is also known as the gathering of requirements. Here, requirements are identified with the help of
customers and existing systems processes, if available.
Analysis of requirements starts with requirement elicitation. The requirements are analyzed to identify
inconsistencies, defects, omission, etc. We describe requirements in terms of relationships and also resolve
conflicts if any.
Problems of Elicitation and Analysis
• Getting all, and only, the right people involved.
• Stakeholders often don't know what they want
• Stakeholders express requirements in their terms.
• Stakeholders may have conflicting requirements.
• Requirement change during the analysis process.
• Organizational and political factors may influence system requirements.
3. Software Requirement Specification:
Software requirement specification is a kind of document which is created by a software analyst after the
requirements collected from the various sources - the requirement received by the customer written in
ordinary language. It is the job of the analyst to write the requirement in technical language so that they
can be understood and beneficial by the development team.

Data Flow Diagrams: Data Flow Diagrams (DFDs) are used widely for modeling the requirements. DFD
shows the flow of data through a system. The system may be a company, an organization, a set of
procedures, a computer hardware system, a software system, or any combination of the preceding. The
DFD is also known as a data flow graph or bubble chart.
Data Dictionaries: Data Dictionaries are simply repositories to store information about all data items
defined in DFDs. At the requirements stage, the data dictionary should at least define customer data items,
to ensure that the customer and developers use the same definition and terminologies.
Entity-Relationship Diagrams: Another tool for requirement specification is the entity-relationship diagram,
often called an "E-R diagram." It is a detailed logical representation of the data for the organization and
uses three main constructs i.e. data entities, relationships, and their associated attributes.
4. Software Requirement Validation:
After requirement specifications developed, the requirements discussed in this document are validated.
The user might demand illegal, impossible solution or experts may misinterpret the needs. Requirements
can be the check against the following conditions –

• If they can practically implement


• If they are correct and as per the functionality and specially of software
• If there are any ambiguities
• If they are full
• If they can describe
• Requirements Validation Techniques
THANK YOU!

You might also like