CPRE-FL Module 8: Managing Requirements

Requirements attribute schemes
This document is a partial preview. Full document download can be found on Flevy:
http://flevy.com/browse/document/8-managing-requirements-2563

Attribute schemes
Set of all defined attributes for a class of requirements is
called an attribute scheme
Template-based attribute schemes have the advantage that
Information of same type can always be found in same position
It is harder for Requirements Engineer to overlook important
information

Project-specific attribute scheme
Consider following aspects to
define a project specific
requirements attribute scheme:
Properties of the project
Constraints of the
organization
Properties and regulations of
the application domain
Modeling guidelines,
standards, constraints, and
Restrictions of development
process

Prioritizing requirements
Requirements are prioritized during
requirements engineering using
different prioritization criteria
Requirements are prioritized to
determine their order of
implementation
The below mentioned steps can be
followed for requirements prioritization:
Define goal (i.e., purpose) of
prioritization
Document constraints of prioritization
Depending on the goal of prioritization,
choose criterion / criteria for
prioritizing requirements
Involve relevant stakeholders in
prioritization process
Choose requirements from same level
of abstraction for prioritization

Requirements traceability
Ability to trace requirements to source,
implementation and relationships
among requirements
Advantages of Traceable Requirements
Verifiability
Identification of gold-plated solutions
Impact analysis
Reuse of past work products
Accountability
Maintenance
Purpose-driven traceability

Requirements versioning
Aims at providing access to the specific
changed states of individual requirements
over the entire life cycle of the system
It is marked by a unique version number
While versioning requirements, there are
two aspects to consider –
Version and
Increment of version number

Management of Requirements Changes
Requirements change during the
life of a system due to
Better understanding of the system
and context
Changes in stakeholder needs
Modification of laws
Partial and erroneous requirements
Requirements which may have led to
failure of a system
Evolution of context
Advent of new technologies
Increased competition in the market
etc.

Change request (CR)
A change request contains at least the following information:
IdentifierIdentifier TitleTitle DescriptionDescription JustificationJustification
Date filedDate filedApplicantApplicant
Requested
priority
Requested
priority
Change
Validator
Change
Validator
Impact
Analysis
status
Impact
Analysis
status
CCB
decision
status
CCB
decision
status
CCB
priority
CCB
priority
Responsi
ble
Responsi
ble
System
release
System
release

Basic method for corrective and adaptive
changes
Impact analysis
This phase includes effort estimation for performing the
change
All the requirements affected by changes, existing or new, must
be identified
Posterior development artifacts which needs to be worked
upon must also be considered
Once the above two steps are carried out, the effort required
to implement change in each affected artifact must be
estimated and a sum total of effort must be calculated
Using traceability information
Identification of affected requirements and posterior
development artifacts can be done using
Traceability information or
Through automation.

Requirements measurements
A metric is a standard for measuring or evaluating
something
The results obtained from various metrics provides
an insight into product and process quality
Product vs. Process Metric
Metrics used in requirements engineering can be
broadly classified into:
Product metrics and
Process metrics

Correct Option for Question 1
A. The best option

Question 3
3. Additional information on requirements is managed using
attributes. An example of such additional information is a
unique identifier. Which of the following statements is not true
on the sense of unique identifiers? “Unique identifiers are
helpful...”
a. ...for estimating the overall size of a specification
b. ...for having an unambiguous basis for communication
c. ...for establishing references to other requirements
d. ...for establishing traceability to other development artifacts

C. Question is on requirement's prioritization.

Question 6
6. Traceability can be established
a. Between requirements to other requirements
b. Requirements to solution components
c. Requirements to test cases
d. All of the above

D. Definition of requirements prioritization

Question 9
9. Recording the dependencies and relationships for the
requirements helps in ...
a. ...determining the sequence in which requirements are to be
addressed.
b. ...determining which requirements carry the most risk.
c. ...determining the total cost for the solution to be implemented.
d. ...determining the total time for the solution to be implemented.

C. RM Plan contains approach to requirements
prioritization.

1
Flevy (www.flevy.com) is the marketplace
for premium documents. These
documents can range from Business
Frameworks to Financial Models to
PowerPoint Templates.
Flevy was founded under the principle that
companies waste a lot of time and money
recreating the same foundational business
documents. Our vision is for Flevy to
become a comprehensive knowledge base
of business documents. All organizations,
from startups to large enterprises, can use
Flevy— whether it's to jumpstart projects, to
find reference or comparison materials, or
just to learn.
Contact Us
Please contact us with any questions you may have
about our company.
• General Inquiries
support@flevy.com
• Media/PR
press@flevy.com
• Billing
billing@flevy.com

CPRE-FL Module 8: Managing Requirements

Recommended

Recommended

More Related Content

Viewers also liked

Viewers also liked (12)

More from Flevy.com Best Practices

More from Flevy.com Best Practices (20)

Recently uploaded

Recently uploaded (20)

CPRE-FL Module 8: Managing Requirements