Scribd
Upload
23 views

19

The document discusses the key areas of effort in software requirements analysis: problem recognition, evaluation and synthesis, modeling, specification, and review. It emphasizes understanding the software in the system context and establishing communication to ensure problem recognition. The goals are to identify the basic problem elements as perceived by customers and users. It also lists the main analysis concepts as identifying the customer, building analysis models, focusing on data and function, representing behavior, prototyping uncertain areas, developing a specification to guide design, and conducting formal technical reviews.

Uploaded by

Aravind Chintalapalli
Copyright
© Attribution Non-Commercial (BY-NC)
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
23 views

19

The document discusses the key areas of effort in software requirements analysis: problem recognition, evaluation and synthesis, modeling, specification, and review. It emphasizes understanding the software in the system context and establishing communication to ensure problem recognition. The goals are to identify the basic problem elements as perceived by customers and users. It also lists the main analysis concepts as identifying the customer, building analysis models, focusing on data and function, representing behavior, prototyping uncertain areas, developing a specification to guide design, and conducting formal technical reviews.

Uploaded by

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

System Engineering - Analysis Concepts

SoItware requirements analysis may be divided into Iive areas oI eIIort: (1) problem
recognition, (2) evaluation and synthesis, (3) modeling, (4) speciIication, and (5) review.
Initially, the analyst studies the System SpeciIication (iI one exists) and the SoItware Project
Plan.
It is important to understand soItware in a system context and to review the soItware
scope that was used to generate planning estimates. Next, communication Ior analysis must be
established so that problem recognition is ensured. The goal is recognition oI the basic problem
elements as perceived by the customer/users.

Analysis Concepts
o identiIy the 'customer and work together to negotiate 'product-level requirements
o build an analysis model
o Iocus on data
o deIine Iunction
o represent behavior
o prototype areas oI uncertainty
o develop a speciIication that will guide design
o conduct Iormal technical reviews





the probIem
requirements
eIicitation

buiId a
prototype
create
anaIysis
modeIs
develop
Specification
Review

You might also like