A method to define SoS requirements Online publication date: Sat, 31-Jan-2015
by Randy G. Walker; Charles B. Keating; Adrian V. Gheorghe; Resit Unal; James Pyne
International Journal of System of Systems Engineering (IJSSE), Vol. 5, No. 4, 2014
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.
Existing subscribers:
Go to Inderscience Online Journals to access the Full Text of this article.
If you are not a subscriber and you just want to read the full contents of this article, buy online access here.Complimentary Subscribers, Editors or Members of the Editorial Board of the International Journal of System of Systems Engineering (IJSSE):
Login with your Inderscience username and password:
Want to subscribe?
A subscription gives you complete access to all articles in the current issue, as well as to all articles in the previous three years (where applicable). See our Orders page to subscribe.
If you still need assistance, please email subs@inderscience.com
Our Blog 
Follow us on Twitter 
Visit us on Facebook