Helder Castro on LinkedIn: MBSE Arcadia step-by-step guide - Home (2024)

Exploring new ways to learn is essential for mastering Model-Based Systems Engineering with Arcadia and Capella.Your input will help shape future educational resources and strategies.Please take a moment to vote and share your insights. Thank you for contributing! 🚀#arcadia #capella #mbse #systemarchitecture #systemsemgineering

This content isn’t available here

Access this content and more in the LinkedIn app

3

I have been asked if the "Capturing textual requirements in Capella step-by-step guide", could be available in PDF format.Attached a PDF version of the same article: https://lnkd.in/egpMQqqiThanks all for your comments and support messages 👍#capella #arcadia #mbse #requirements #systemsengineering

116

17 Comments

Textual requirement can be captured directly in a MBSE modelling tool.This article captures a Capella step-by-step guide to capture, view, manage and export textual requirements from the MBSE Capella modelling tool.Share your comments 👍 #arcadia #capella #mbse #requirements #systemsengineering

124

12 Comments

Management of modes and states is a wide, complex, and often underestimated part of systems engineering. As systems become more complex, the potential combination of modes and states across system, subsystem, and component levels becomes exponential and difficult to master.Arcadia proposes definitions for modes and states not intended to establish a universal reference for what a mode or what a state is, but, definitions are provided in the scope of the Arcadia method and in the context of the methodological guidance it provides. In Arcadia, it is possible to capture modes and states in a Mode and State Machine diagram [MSM].Modes and States are defined separately, that is, modes are not allowed within states or states within modes.The paper "Modelling system modes, states, configurations with Arcadia and Capella: method and tool perspectives" (https://lnkd.in/eejgMFnJ), captures definitions for modes and states, but also the challenges for mastering modes and states.It introduces the concept of configurations and situations.Authors of the paper, capture the purpose of modes and states in the different Arcadia perspectives. Quite interesting and challenging topic when capturing modes and states for a complex system.It is proposed a methodological approachfor mastering modes and states. For those who whish to go deeper in detail and learn more, I do recommend to read the book Model-based System and Architecture Engineering with the Arcadia Method, by Jean-Luc Voirin:- Chapter 14: System Supervision, States and Modes AND- Chapter 18: Concepts of States and ModesThis book goes in deeper detail on the principles, concepts, all the topics mentioned above providing examples for better understanding. A must read.For those who want to practise and implement modes and states with the MBSE Capella modelling tool, I do recommend reading the book Systems Architecture Modeling with the Arcadia Method: A Practical Guide to Capella, by Pascal Roques, chapter:- Chapter 4.8: Modes and States at the System level.A Capella add-on is under development; the Modes & States viewpoint for Capella is to enrich the capabilities regarding the definition of Modes & States, but also the capabilities in order to analyse their consistency. Reference to the add-on: https://lnkd.in/e6nbbCyR.A webinar talking about Modelling states and modes with Arcadia and Capella: method and tool perspectives, by one of the same paper author, Stephane Bonnet: https://lnkd.in/eFDwfJXTI hope the above will be useful for those who want to learn, master and practise modes and states with Arcadia and Capella.It would be great to learn from others what are their perspectives on this topic, method and tool usage 👍 #arcadia #capella #mbse #systemsengineering

81

5 Comments

Thanks Lou W. for sharing your thoughts on this topic.I will add my thoughts that MBSE is not about simulation or drawing (sometimes mislead with Visio). MBSE is supported by a modelling language: Arcadia, SysML, UML, BPMN, UAF, for example, but also it may be supported by a MBSE framework.A MBSE framework defines an ontology and viewpoints, promoting consistency in views and traceability inherent in the model. I like the fact that you mentioned: "Also, one size doesn't fit all".Project and organisations "jump" start into MBSE without asking first:- What is the MBSE value expected for OUR project and organisation?- What resources (people + tools + process) will be required?MBSE can be used to:- Breakdown and understand systems growing complexity- Promote and encourage communication and tackle silos.- Detect defects earlier in the system development cycle by on-going requirements validation through design verification and the use of simulation and automatic verification.- Reduce costs. This is interesting, as MBSE may increase costs at the very first stages of the development, but by promoting correctness, consistency and completeness (CCC), may reduce risks, redevelopment and reuse of diagrams when V&V.#mbse

17

2 Comments

Arcadia concepts are mostly similar to System Modelling Language (SysML) standard. The Arcadia/Capella solution focuses on the design of systems architectures. For the sake of an easier learning curve and because of the precise scope addressed by Arcadia/Capella, the expression means are sometimes reduced compared to SysML. The ultimate goal of Arcadia/Capella is to have systems engineers embrace the cultural change of MBSE rather than having modelling “experts” owning the model on behalf of systems engineers. Therefore, Arcadia/Capella are strongly driven by the current practices and concerns of system engineering practitioners.The Arcadia method enforces an approach structured on different engineering perspectives establishing a clear separation between system context and need modelling (operational need analysis and system need analysis) and solution modelling (logical and physical architectures), in accordance with the standard ISO/IEC/IEEE 15288 (covering parts of).The Arcadia concepts are mostly similar to the UML/SysML standard and the NATO Architecture Framework (NAF) standard. Interoperability with SysML tools is possible. Because of the focus on architectural design, some of the SysML concepts have been simplified or specialized in order to better match the concepts system engineering practitioners already use in their engineering documents and assets. This is the case of the concepts related to functional analysis for instance.For the main SysML diagrams, Arcadia proposes a twin diagram.See below the similarities and equivalences between SysML diagrams and the corresponding ones in Arcadia:#arcadia #sysml #mbse #systemsengineering

67

19 Comments

Artificial Intelligence (AI) and Natural Language Processing (NLP) capabilities and considerations applied to System Engineering (SE).What it can be the role for Artificial Intelligence (AI) and Natural Language Processing (NLP)?- Can AI help, support and even propose design, starting from textual requirements?- Can AI techniques be used to process natural language and transform into textual requirements?The above questions can be asked, and extended, at any level within requirements engineering environment, facing growing challenges as systems complexity grows.#ai #nlp #arcadia #capella #incose #systemsengineering #sysml #requirements #mbse #ontology

30

When working with the #mbse #capella modelling tool there are several options to capture textual requirements in a model:1 - Capture textual requirements directly in the modelling tool. There is the need to install the Requirements Viewpoint add-on2 - Import textual requirements captured in an external tool:2.1 - Using ReqIF files2.2 - Capella connector add-ons as captured in previous post (https://lnkd.in/euM_8PVk).This post will describe one way for importing and exporting ReqIF files between the Capella and IBM Doors 9.x requirements management tool.Use case: a systems engineer holding different roles (requirements engineer and system modeller) needs to export textual requirements from IBM Doors, import them to Capella, create traceability links between textual requirements and model elements, export traceability and import and update textual requirements attributes; complete textual requirements and Capella modelling tool roundtrip.Steps 1 - 4: enumerates a typical IBM Doors module creation, requirements and attributes capture, configure and export a ReqIF file from Doors.Step 5: If the model in hosted on a server, a modeller may need to download a local copy before importing the ReqIF file.Step 6 - 7: Import ReqIF file and upload local model to the server. It is very important to import ReqIF first and not creating requirements in the Capella tool.Note: It is relevant to make sure the above step is followed for the first time, that is, import the textual requirements ReqIF file exported from Doors and not creating a new requirements module in Capella. This activity will allow Capella to create and configure the Capella Requirement Module with the ReqIF Identifier.Step 8: Formalise textual requirements as describe in the post: https://lnkd.in/eXUvRNaE.Step 9: Establish traceability between textual requirements and model elements. It is assumed traceability link types (e.g., satisfy, derive) were previously created and can be used for traceability.Step 10: From project explorer, select textual requirements (only) and send it to "Mass Visualization View". Hide and show columns in the Mass Visualization View tab. Click on .csv to export to a CSV file. Step 11: On the exported .csv file, reword and match attributes against the Doors requirements module. If not new attributes will be created.Step 12: Import ReqIF file.Last step will update (at least the allocated elements - example of a name attribute that captures traceability) the requirements attributes in the requirements module.It is not advised to update textual #requirements in the Capella tool. This may break any defined process and source of truth for textual requirements, which should be the selected requirements management tool.#systemsengineering #requirementsengineering

101

14 Comments

At the very beginning of my learning journey and in addition to my post last week (https://lnkd.in/eR3ik-ee), I did find, in my notes, a diagram captured in a modelling tool and language other than #arcadia and #capella.The diagram captures many of the Arcadia diagrams that can be found in the language; probably more that a modeller may ever need 😄 Sharing with the community.#mbse #engineering

48

6 Comments