Abstract
This study seeks to compare the quantity of information that is automatically transferred through the associations generated using a model-based systems engineering (MBSE) approach versus a traditional systems engineering approach to measure the benefits of MBSE in architecting a robotic space system. Both an MBSE approach and non-MBSE approach were applied to architecting an orbiting sample Capture and Orient Module (COM) system concept for a Capture, Containment, and Return System (CCRS) payload concept for Mars Sample Return (MSR). These approaches were applied in parallel to provide a side-by-side comparison of the approaches. The approaches were analyzed using design structure matrices (DSM) and evaluated based on the amount of information transferred between process tasks manually (e.g., elements physically typed into text boxes in a presentation slide) vs automatically (e.g., elements automatically filled out within a block in a model view due to explicitly defined element associations). A total of 4,819 information element transfers were traced in DSMs and used to quantitatively compare the two approaches. The non-MBSE approach required manual transfer for all 4,819 information elements. The MBSE approach required manual transfer for 4,189 information elements and automatic transfer for 630 information elements, providing a minor increase in the automation of information transfer relative to the non-MBSE approach. By incorporating the use of additional MBSE artifacts into the trade study and peer review tasks, manual transfer could potentially be reduced to 931 information elements, and automatic transfer increased to 3,888 information elements.
Highlights
On August 5, 2012, National Aeronautics and Space Administration (NASA)’s 900 kg Mars Science Laboratory (MSL) Curiosity rover successfully landed on the surface of Mars and set out to search for evidence of past habitable environments [1], [2]
The purpose of this research is to explore the advantages of an model-based systems engineering (MBSE) approach in architecting a robotic space system relative to a non-MBSE approach, as assessed by the quantity of information transfer that can be automated for carrying out the architecting process
This section presents the system architecting process developed for both the non-MBSE and MBSE approaches, describes the RBSs and design structure matrices (DSM) generated for each approach, and compares the quantities of information manually and automatically transferred between tasks in the DSMs of each approach
Summary
On August 5, 2012, NASA’s 900 kg Mars Science Laboratory (MSL) Curiosity rover successfully landed on the surface of Mars and set out to search for evidence of past habitable environments [1], [2]. A metric for design changes used by NASA is ‘‘drawing growth’’ after the Critical Design Review (CDR), where MSL saw a 147% growth [6]. Some of these late design changes were attributed to the discovery of divergent requirements uncovered late during the testing phase. MBSE aims to provide benefits over traditional, document-based systems engineering in terms of reduced effort to implement system development through increased productivity, reduced inefficiencies, and reduced lag in information flow [16], [25]–[27]
Sign-in/Register to view highlights & summary 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 callDisclaimer: 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.
