Your what is my how: Why requirements and architectural design should be iterative

Research output: Chapter in Book/Report/Conference proceedingConference contribution

4 Scopus citations

Abstract

Systems are naturally constructed in hierarchies in which design choices made at higher levels of abstraction levy requirements on system components at lower levels of abstraction. Thus, whether an aspect of the system is a design choice or a requirement depends largely on one's location within the hierarchy of system components. In addition, it is often the case that systems are not constructed top-down, but rather middle-out; compatibility with existing systems and architectures, or availability of specific physical components may influence high-level requirements. Despite these facts, several of the reference models commonly used for requirements, including the four-variable model and world machine model, do not account for hierarchical decomposition. In this position paper, we argue that requirements and architectural design should be more closely aligned: that requirements reference models should account for hierarchical system construction, and that architectural design notations should better support specification of requirements for system components. We briefly describe work to this end that was performed on the META II project and describe the gaps in this work that need to be addressed to meet practitioner needs.

Original languageEnglish (US)
Title of host publication2012 1st IEEE International Workshop on the Twin Peaks of Requirements and Architecture, TwinPeaks 2012 - Proceedings
Pages36-40
Number of pages5
DOIs
StatePublished - Dec 14 2012
Event2012 1st IEEE International Workshop on the Twin Peaks of Requirements and Architecture, TwinPeaks 2012 - Chicago, IL, United States
Duration: Sep 25 2012Sep 25 2012

Publication series

Name2012 1st IEEE International Workshop on the Twin Peaks of Requirements and Architecture, TwinPeaks 2012 - Proceedings

Other

Other2012 1st IEEE International Workshop on the Twin Peaks of Requirements and Architecture, TwinPeaks 2012
CountryUnited States
CityChicago, IL
Period9/25/129/25/12

Keywords

  • architecture
  • formal methods
  • model checking
  • refinement
  • requirements

Fingerprint Dive into the research topics of 'Your what is my how: Why requirements and architectural design should be iterative'. Together they form a unique fingerprint.

Cite this