Abstract
This paper examines the nature of the issues in defining SoS requirements and examines an emerging methodology for deriving SoS requirements. The methodology focuses on SoS characteristics common to most SoS regardless of their composition of constituent systems, and proposes a combined top-down, bottoms-up approach to deriving unifying SoS requirements. The top-down analysis considers the SoS’ high-level capability objectives, which can be derived from top-level characterisations of the SoS (e.g., operational mission threads, operational concepts, mission-area tasks). This derived set of capability objectives is then decomposed into functional themes, which are then tempered by a bottom-up validation by aggregating common system functions across the constituent system elements within the SoS. The resulting SoS requirements are more granular than capability objectives yet more abstract than the detailed system requirements. This paper concludes with the current implications and future challenges the methodology poses for SoS-based initiatives and the requirements engineering field.
Sign-in/Register to access full text options 
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a callMore From: International Journal of System of Systems Engineering
Disclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.
