CubeSat Model Based System Engineering (MBSE) Reference Model - Application in the Concept Lifecycle Phase

Abstract

Model-Based Systems Engineering (MBSE) is a key practice to advance systemsengineering that can benefit CubeSat missions. MBSE involves creating a system model that is a single source for system engineering such as architecture development and interface management. The system model also integrates other discipline specific engineering models and simulations. Our application of MBSE uses System Modeling Language (SysML), a graphical modeling language, to model all aspects of a system either directly or through an interface with another model. SysML diagrams are used to describe requirements, structures, behaviors, and parametrics from the system down to the component level. The model is intended for use by aerospace students in their classroom or by a CubeSat team building a mission-specific CubeSat. Using the CubeSat Reference Model as a starting point, a user can populate a mission-specific model with the concept lifecycle stakeholders and stakeholder needs, objectives, constraints, and measures of effectiveness (MOEs) and carry out concept life-cycle studies.

Cross-Industry Principles for Digital Representations of Complex Technical Systems in the Context of the MBSE Approach: A Review

“…An analysis of the application of the approach shows that it is important to provide a hierarchy, which involves dividing a system of systems into different levels of decomposition and nesting components within each other [84][85][86][87][88]. Hierarchical modeling involves integrating validated subcomponent-level, component-level, or subsystem-level models into a large-scale system-level model [85].…”

“…Hierarchical modeling involves integrating validated subcomponent-level, component-level, or subsystem-level models into a large-scale system-level model [85]. To determine the boundary conditions of a complex technical system, it is necessary to rise to the level of a hierarchically higher complex technical system and identify the incoming and outgoing data in the complex technical system under consideration, and vice versa to the hierarchical level of the lower complex technical system, and repeat this process iteratively [84][85][86][87][88]. As the model and structure of the system are built, these operations must be repeated and, if necessary, move along the chain to even higher and lower levels of complex technical systems.…”