Action | Conditional | Continuance | Imperative | Incomplete | Option | Risk Level | Source | Weak Phrase

Action
Handle: Action
Description: Represents the number of actions the requirement needs to be capable of performing.
Observation: This metric is generated by manual requirements analysis. 
Frequency: Frequency is determined by the requirements of each project.
Scale: This is a count.
Range: Unlimited.
Usage: None, currently.
Relationship: Unknown.
Threshold: Unknown.
Validation: None, currently.

+ Top

Conditional
Handle: Conditional
Description: Represents whether the requirement will be addressing more than one condition. This indicates a higher level of complexity in dealing with multiple conditions within the requirement (i.e., If, when, in the event of).
Observation: This metric is generated by manual requirements analysis.
Frequency: Frequency is determined by the requirements of each project.
Scale: This is a count.
Range: Unlimited.
Usage: None, currently.
Relationship: Unknown.
Threshold: Unknown.
Validation: None, currently.

+ Top

Continuance
Handle: Continuance
Description: Phrases such as "the following:" that follow an imperative and precede the definition of lower level requirement specification. The extent that continuances are used is an indication that requirements have been organized and structured. These characteristics contribute to the tractability and maintenance of the subject requirement specification. However, extensive use of continuances indicate multiple, complex requirements that may not be adequately factored into development resource and schedule estimates.
Observation: This This metric is generated with the Automated Requirement Metrics Tool (ARM).
Frequency: Frequency is determined by the requirements of each project.
Scale: This is a count.
Range: Unlimited.
Usage: None, currently.
Relationship: Unknown.
Threshold: Unknown.
Validation: None, currently.

+ Top

Imperative
Handle: Imperative
Description: Those words and phrases that command that something must be provided. "Shall" normally dictates the provision of a functional capability. "Must" or "must not", normally establish performance requirements or constraints. "Will" normally indicates that something will be provided from outside the capability being specified. The ARM report lists the imperatives and their associated counts in descending order of forcefulness. An explicit specification will have most of its counts high in the report IMPERATIVE list (i.e. shall, must, required).
Observation: This metric is generated with the Automated Requirement Metrics Tool (ARM)..
Frequency: Frequency is determined by the requirements of each project.
Scale: This is a count.
Range: Unlimited.
Usage: None, currently.
Relationship: Unknown.
Threshold: Unknown.
Validation: None, currently.

+ Top

Incomplete
Handle: Incomplete
Description: P hrases such as "TBD" or "TBR". They are used when a requirement has yet to be determined. These are considered critical to requirements documents and need to be corrected as soon as possible. They can cause unexpected delays and high costs.
Observation: This This metric is generated with the Automated Requirement Metrics Tool (ARM)..
Frequency: Frequency is determined by the requirements of each project.
Scale: This is a count.
Range: Unlimited.
Usage: None, currently.
Relationship: Unknown.
Threshold: Unknown.
Validation: None, currently.

+ Top

Option
Handle: Option
Description: Those words that give the developer latitude in the implementation of the specification that contains them. This type of statement loosens the specification, reduces the acquirer's control over the final product, and establishes a basis for possible cost and schedule risks.
Observation: This This metric is generated with the Automated Requirement Metrics Tool (ARM).
Frequency: Frequency is determined by the requirements of each project.
Scale: This is unclear.
Range: Unlimited
Usage: None, currently.
Relationship: Unknown.
Threshold: Unknown.
Validation: None, currently.

+ Top

Risk Level
Handle: Risk Level
Description: A calculated risk level metric based on weighted averages from metrics collected for each requirement.
Level 1) - Indicates a non-complex straight forward requirement containing one imperative, single action and single source.
Level 2) - Indicates a requirement containing multiple imperatives, more than one action and/or more than one source.
Level 3) - Indicates a requirement containing conditionals and more than one action and/or source.
Observation: This This metric is generated by manual requirements analysis.
Frequency: Frequency is determined by the requirements of each project.
Scale: One to three.
Range: One to Three.
Usage: None, currently.
Relationship: Unknown.
Threshold: Unknown.
Validation: None, currently.

+ Top

Source
Handle: Source
Description: Represents the number of sources the requirement will interface with or receive data from.
Observation: This metric is generated with by manual requirements analysis.
Frequency: Frequency is determined by the requirements of each project.
Scale: This is a count.
Range: Unlimited.
Usage: None, currently.
Relationship: Unknown.
Threshold: Unknown.
Validation: None, currently.

+ Top

Weak Phrase
Handle: Weak Phrase
Description: Clauses that are apt to cause uncertainty and leave room for multiple interpretations. Use of phrases such as "adequate" and "as appropriate" indicate that what is required is either defined elsewhere or worst, the requirement is open to subjective interpretation. Phrases such as "but not limited to" and "as a minimum" provide the basis for expanding requirements that have been identified or adding future requirements. Weak Phrase total is indication of the extent that the specification is ambiguous and incomplete.
Observation: This metric is generated with the Automated Requirement Metrics Tool (ARM).
Frequency: Frequency is determined by the requirements of each project.
Scale: This is a count.
Range: Unlimited.
Usage: None, currently.
Relationship: Unknown.
Threshold: Unknown.
Validation: None, currently.

+ Top