Document Type
Working Paper
Publication Date
3-2016
Abstract
A work in progress to define a metrics set for requirements. Metrics are defined that apply to either the entire requirements set (requirements document as a whole) or individual atomic (or singular, individual) requirements statements. Requirements are identified with standard names and a identification scheme and include both subjective and objective measures.
An example metric for the full set of requirements: Rd2 - Requirements Consistency, Is the set of atomic requirements internally consistent, with no contradictions, no duplication between individual requirements? An example of a metric for a single requirement: Ra4 - Requirement Verifiability, How adequately can this requirement be tested? Is it perfectly clear what test(s) are needed to confirm the requirement is met? Is it clear what should be considered a failure of a test of this requirement?
Recommended Citation
Honig, William L.. Requirements Metrics - Definitions of a Working List of Possible Metrics for Requirements Quality. , , : , 2016. Retrieved from Loyola eCommons, Computer Science: Faculty Publications and Other Works,
Creative Commons License
This work is licensed under a Creative Commons Attribution-Noncommercial-No Derivative Works 3.0 License.
Copyright Statement
© 2016 William L. Honig.
Included in
Computer Engineering Commons, Electrical and Computer Engineering Commons, Software Engineering Commons
Comments
See also Requirements Quick Notes and Atomic Requirements Quick Notes.