Page 228 - DCAP405_SOFTWARE_ENGINEERING

Unit 13: Building the Analysis Model

Notes
Did u know? What are the basics of requirements?

Requirements must be measurable, testable, related to identified business needs or
opportunities, and defined to a level of detail sufficient for system design.

Figure 13.1: Requirements Process

13.2.1 Requirement Analysis Objective

The objective of the requirements analysis phase is to recognize and secure approval for a
project requirements specification.
A complete requirements analysis is needed to ensure fast project delivery and optimal return
on information management investment.
13.2.2 Philosophy

This topic is concerned with the process of analyzing requirements to
Detect and resolve conflicts between requirements
Discover the bounds of the software and how it must interact with its environment

Elaborate system requirements to derive software requirements
The conventional view of requirements analysis has been that it be reduced to conceptual
modeling using one of a number of analysis methods such as the Structured Analysis and Design
Technique (SADT). While conceptual modeling is significant, we include the classification of
requirements to help inform trade-offs between requirements (requirements classification) and
the process of establishing these trade-offs (requirements negotiation).

!
Caution Care must be taken to explain requirements precisely enough to enable the
requirements to be validated, their implementation to be verified, and their costs to be
estimated.

LOVELY PROFESSIONAL UNIVERSITY 221