Abstract
AbstractAs model‐based systems engineering (MBSE) gains ground as a real alternative for complex industrial projects compared to the traditional plan or document‐driven systems engineering paradigm, several challenges remain to be dealt with. MBSE requires not only the technological system‐of‐interest to be included in the common model repository used for MBSE, but also other elements and structures that are used to describe vital aspects of a complex technical project. This paper elaborates on how the primary planning document, the Systems Engineering Plan (SEP) can be evolved from the document‐driven to the model‐driven paradigm, and how some SysML diagram types along with architecture framework viewpoints may be used to model the most common content of a SEP. The evaluation is based on industrial experiences using MBSE in real‐world industrial development and procurement projects. Several examples on how SysML may be used to represent SEP elements are presented along with suggestions on potential directions for further work.
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
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.