Scribd
Upload
27 views

05 Requirementanalysis

The document discusses the importance of software requirement analysis and outlines the key steps in the requirement analysis process. These include inception, elicitation, analysis, negotiation, documentation, and review. The goal is to understand customer needs, document requirements, and ensure requirements are clear before software development begins.

Uploaded by

seena15
Copyright
© Attribution Non-Commercial (BY-NC)
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
27 views

05 Requirementanalysis

The document discusses the importance of software requirement analysis and outlines the key steps in the requirement analysis process. These include inception, elicitation, analysis, negotiation, documentation, and review. The goal is to understand customer needs, document requirements, and ensure requirements are clear before software development begins.

Uploaded by

seena15
Copyright
© Attribution Non-Commercial (BY-NC)
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
You are on page 1/ 11

Requirement Analysis

 software requirement analysis and specification is


the most important step in s/w development
 To understand the requirements of the customer.
 Main goal- to document the requirements
 It is a disciplined application of the proven principles,
method, and tools to describe the proposed system’s
behavior.
 This helps software engineers to better understand the
problem they work to solve.
 It encompasses the set of tasks to understand the
business impact of the software, what customer
wants, how end-users will interact with the software.
Steps in Requirement analysis

 Inception
 Elicitation
 Requirement analysis or elaboration
 Negotiation
 Requirement documentation or specification.
 Review or validation
 Management
Inception
 The preliminary meeting or communication
between customer and the proposed team.
 Engineers ask some context-free questions like:
 Who is behind the request for this work?
 Who will use the solution?
 What will be the economic benefit of a successful
solution.
 Aim to create a basic idea of the objective and
suggested constraints.
Elicitation
 It is the requirement gathering step
 Most crucial and error prone.
 Problems faced can be
 Problems of scope : boundary of the system is defined
 Problem of understanding : poor understanding of the
customers.
 Problems of volatility : requirements changes over
time
Requirement Analysis or Elaboration

 Further expansion and refinement of the requirement

 Either by communication or by using the already


established process models.

 End product is an analysis model

 It contains the basic information regarding the


functional & behavioral domain of the problem
Negotiation
 Customers asks for more with limited business
resources or customers among themselves have
conflicting requirements.
 Software engineers must reconcile these conflicts.
 Done by ranking, discussions, risk identification and
analysis, impact of cost and delivery
 Must give some measure of satisfaction to each
customer
Requirement Documentation or
Specification
 Proper document of requirements is created.

 Serves as the foundation of the software design.

 End product is called SRS (Software Requirement


Specification)

 Both software and hardware aspects are discussed.

 So also called System Requirement Specification or SRS


Review or Validation

 The SRS is validated by software engineers,


customers, users etc
 Primary requirement validation mechanism is the
formal technical review.
 Look for errors in content or interpretation, missing
information, inconsistencies, conflicting requirements
or unrealistic requirements
Analysis Model
 The analysis model describes the
structure of the system or application that
you are modeling. It consists of class
diagrams and sequence diagrams that
describe the logical implementation of the
functional requirements that you identified
in the use case model.
Types of Analysis Model
 Data Model
 Explain the data objects, attributes and relationships
 ER Diagram
 Functional Model
 Explain various process in the system and the flow of
data and control
 E.g. DFD, CFD
 Behavioral Model
 Explain how the system behaves as a consequence of
external events
 E.g. State Transition Diagrams

You might also like