This Article 
   
 Share 
   
 Bibliographic References 
   
 Add to: 
 
Digg
Furl
Spurl
Blink
Simpy
Google
Del.icio.us
Y!MyWeb
 
 Search 
   
Your "What" Is My "How": Iteration and Hierarchy in System Design
March-April 2013 (vol. 30 no. 2)
pp. 54-60
Michael W. Whalen, University of Minnesota
Andrew Gacek, Rockwell Collins
Darren Cofer, Rockwell Collins
Anitha Murugesan, University of Minnesota
Mats P.E. Heimdahl, University of Minnesota
Sanjai Rayadurgam, University of Minnesota
Systems are naturally constructed in hierarchies, in which design choices made at higher levels of abstraction levy requirements on system components at the lower levels. Thus, whether an aspect of a system is a design choice or a requirement largely depends on your vantage point within the system components' hierarchy. Systems are also often constructed from the middle-out rather than top-down; compatibility with existing systems and architectures and availability of specific components influence high-level requirements. Requirements and architectural design should be more closely aligned: requirements models must account for hierarchical system construction and architectural design notations must better support requirements specification for system components.
Index Terms:
Computer architecture,Contracts,Software,Analytical models,Cognition,Aerospace electronics,architecture,formal methods,requirements,refinement,model checking
Citation:
Michael W. Whalen, Andrew Gacek, Darren Cofer, Anitha Murugesan, Mats P.E. Heimdahl, Sanjai Rayadurgam, "Your "What" Is My "How": Iteration and Hierarchy in System Design," IEEE Software, vol. 30, no. 2, pp. 54-60, March-April 2013, doi:10.1109/MS.2012.173
Usage of this product signifies your acceptance of the Terms of Use.