|
|
|
|
|
|
Definitions |
|
Baselines
A baseline is a snapshot in time. It captures and preserves
all the information as it stood at that moment in time.
A baseline is a known point from which changes can be introduced and reviewed in a controlled manner.
Change Management
Change Management ensures that any changes are recorded,
communicated and agreed. Requirements Management enables the analysis of
the effect of any change.
Because any changes can impact any part of a system's development, it is essential that a complete history of all such modifications is retained.
It is therefore necessary that any agreed change be communicated
to all necessary parties and incorporated into documents
and the design in a manner in which history is retained
as to what has changed, when, why
and by whom so that future reference to the change is
fully understood.
Cross Reference Matrix
A Cross Reference Matrix or traceability matrix is used to show the relationship (traceability) between requirements, design and test details in a
tabular format.
The VCRM is the most common Cross
Reference Matrix and is used to show the relationship between the user’s requirements and the test or
analysis which proves (or otherwise) that the requirement has been met.
The Cross Reference Matrix may contain whatever information
is deemed necessary.
The Cross Reference matrix may also be used to ensure
all requirements located to, e.g. a specific
sub-system, have either been met or have been agreed
to be non-compliant.
History
History is the part of the Change Management Process
which records and tracks when changes were made and by
whom.
Links
Links articulate the specific relationship between objects
such as “This requirement or design is derived from or satisfies the
Higher level requirement object”.
(Also see - Traceability)
Management
\Man"age*ment\, n. [From Manage, v.]
1. The act or art of managing; the manner of treating, directing, carrying on, or using, for a purpose; conduct; administration; guidance; control;
as, the management of a family or of a farm; the management of state affairs. ``The management of the voice.''
2. Judicious use of means to accomplish an end; conduct directed by art or address; skilful treatment; cunning practice;
Syn: Conduct; administration; government; direction; guidance; care; charge; contrivance; intrigue.
Source: Webster's Revised Unabridged Dictionary, © 1996, 1998 MICRA, Inc.
Metrics
Metrics are used to view the status and quality of requirements or the process. Some measures include:
- The number of requirements met by the design
- The number of requirements not met by the design
- The status of each requirement
- Stability of the requirements (frequency and number of changes)
Requirement
\Re*quire"ment\ (-ment), n.
1. The act of requiring; demand; requisition.
2. That which is required; an imperative or authoritative command; an essential condition; something needed or necessary; a need.
Source: Webster's Revised Unabridged Dictionary, © 1996, 1998 MICRA, Inc.
Requirements Capture
[See Requirements Elicitation and Requirements Definition]
Requirements Clarification
Requirements Clarification is the process of discussion and / or negotiation to ensure that requirements are clear and consistently understood by all parties.
Requirements Definition
Requirements Definition is the step of analysing the needs of the user and converting them into requirements against which a system can be developed
and its success measured.
Requirements Elicitation
Requirements Elicitation is the process of identification
of requirements from the user. A customer may already
have a predefined need, however it is often necessary
for further, and perhaps more detailed,
requirements to be ascertained.
Requirements Identification
[See Requirements Elicitation]
Traceability
The term traceability is used to denote a relationship between a requirement and any other element of the system engineering process such as a design
component or specification document. Traceability provides a relationship between requirements, design and final implementation of a system.
Traceability is used to provide the ability to trace and discover the history of implemented system features.
The relationship described or defined by traceability is often viewed as ‘Links’.
If traceability has been used in a consistent manner it is possible to use it to help answer, amongst others, the following questions:
- What impact will changing a requirement have?
- How is this requirement implemented?
- Are all requirements allocated to a part of the design / owner?
- What user case / user need does this requirement address?
- Is this function necessary?
- Are the requirements met by the implementation?
- How (which test) will a requirement be verified / validated?
- How is this requirement interpreted? What is its history?
- Is the requirement complete?
Traceability Matrix
[See Cross Reference Matrix]
Verification Cross Reference Module (VCRM)
[See Cross Reference Matrix]
The VCRM is used to show that all requirements have been
incorporated into the development and how they have been
tested to prove (Verify) compliance.
|
|
![](../"_images/spacer.gif"){kind=spacer}
