Title: A method to define SoS requirements
Authors: Randy G. Walker; Charles B. Keating; Adrian V. Gheorghe; Resit Unal; James Pyne
Addresses: National Centers for System of Systems Engineering, Old Dominion University, Norfolk, Virginia, USA ' National Centers for System of Systems Engineering, Old Dominion University, Norfolk, Virginia, USA ' National Centers for System of Systems Engineering, Old Dominion University, Norfolk, Virginia, USA ' National Centers for System of Systems Engineering, Old Dominion University, Norfolk, Virginia, USA ' National Centers for System of Systems Engineering, Old Dominion University, Norfolk, Virginia, USA
Abstract: The purpose of this paper, following completion of the initial research effort, is to provide an update to the previously-published article in this same journal, which examined the nature of the issues surrounding SoS requirements definition and discussed and demonstrated an emerging methodology. With the related research stage complete, the now SoS requirements definition method shows promise for being transportable to a wide range of SoS domains and can significantly enhance requirements practices for engineering SoS to provide element system managers and engineers a higher level SoS focus to their efforts while still maximising their autonomy to achieve system-level requirements. The method combines top-down, bottoms-up approaches to discerning and deriving unifying SoS requirements. The end result is a set of SoS requirements that are more granular than high-level capability objectives yet more abstract than the detailed system requirements.
Keywords: system of systems engineering; SoSE; requirements method; requirements definition; requirements elicitation; requirements engineering.
DOI: 10.1504/IJSSE.2014.067102
International Journal of System of Systems Engineering, 2014 Vol.5 No.4, pp.289 - 323
Received: 09 Aug 2014
Accepted: 05 Sep 2014
Published online: 31 Jan 2015 *