process of checking

that a product meets its

specification Requirements verification
process of checking that a Sommerville (2007):
the needs
product meets Requirements validation
expectations
Requirements Verification &
Walkthrough Validation
Checklist Reviews the requirements specification
Inspection
Techniques
Prototyping
Acceptance Tests

To build the requirements SRS (software requirements

document specification)
official document consists
requirements have of information guide the
been defined system developers the
requirements analysis development of the
has been correctly product
performed for gathering requirements
requirements provide A process for skills writing formal documents
information needed to determine Requirements and report
develop the solution. Specification
requirements ready for involve technical writers assess and plan documentation tasks.
formal review and determine the questions concern to
Verification the customers and users regarding
validation by the
know non-functional requirements
customer and users
Completeness Correct
Correctness Focuses on Complete
Usability Consistent
srs Attributes Unambiguous
Testable
Traceable
Verifiable

requirements are accurate,

correctly align to the needs
A process for
of the customer,
determine
have appropriate level of detail.
Supporting business Validation
objectives
one thing causes a series of
Aligning with business objectives, Focuses on
Ripple Effect other things to happen
Meet stakeholders needs
inevitable
Changes in requirements
must be allowed
Requirements minor change require lot
Management of work
Managing changes to requirements
Managing configuration of
requirements and
Requirements management requirements document
Maintaining requirements traceability
Tracking requirements status

RE Process (module 3) part

3

change management
principles and guideline The change management
activities of the change process Failure to elicit the real
management process. define a set of change
management policies and requirements
to avoid changes from causing Basic policies procedures creates new requirements.
overruns in project schedule and
budget encounter technical,schedule or cost
Internal Factors problems
resulting negative impact on The change impact analysis
the product’s quality. Fail to create a practical
requirements change management
recording and updating
Why requirement process
applied to the
requirements document, changes problem trying to solve change as a result
and providing version of a changing economy, government
control, release regulations, consumer preferences
management, and issue Customers and users change
tracking External Factors their minds
Prevents any unauthorised The customers’ organization may
and potentially destructive Requirements configuration
management change its structure, procedures and
Preserves the revisions Managing requirements processes
Facilitates the retrieval and/or Benefits (Leffingwell and changes
recreation Widrig, 2003)
Prevents simultaneous updates
Prevents conflicting and
uncoordinated updates
ability to describe and follow
the life of a requirement Gotel and Finkelstein (1994): Managing requirements
to show the dependencies traceability
between requirements traceability matrix Technique
ensure existing requirements
are addressed Monitoring implementation
traceable throughout the status of each requirement
development life cycle.
proposed Tracking requirements status Tracking requirements status
approved supports overall project status
E.g.: tracking
verified
rejected