20 July, 2004
OSMA Software Assurance Symposium
California Institute of Technology
Requirements Decomposition Analysis Highlights
Examined ST-6 Autonomous Sciencecraft Experiment requirements (approx. 9 pages)
Got a feel for the potential complexity of analyzing the decomposition of resource requirements, while working with a relatively small set of requirements (approximately 9 pages of technical detail)
Focused on the Mars Reconnaissance Orbiter requirements (approx. 1,370 in all)
Developed a means to use the project-provided traceability information to extract all the requirements that are related to a requirement of interest
WHY: Convenience & comprehension – extracts just those requirements connected, directly or indirectly, assembling the results into a (web-browser-viewable) table. The result is easier to study than following individual links within the large set of requirements, and is more focused than the “graphic mode” that the requirements tool DOORS provides. In the event of the need to make a change to a requirement, this capability has potential utility, by finding and reporting all the requirements related (directly or indirectly) to that requirement.
HOW: This is in the form of an automatic script, which takes as input the user’s identification of the requirement of interest, and returns the requirements linked to that (both “parents” of that requirement, and “children” of that requirement), the requirements linked to those requirements, etc.