The NASA System Engineering (SE) handbook aims to provide general guidance and information on systems engineering, as it should be applied throughout NASA. The handbook introduces 3 common technical processes. One of these, is the System Design Process, describing the stakeholders expectations, requirements definition, logical decomposition and design solution definition. The 4 activities can be supported by a Model-Based Systems Engineering (MBSE) approach. To do so, an appropriate method and tool is necessary as the one provided by the ARChitecture Analysis & Design Integrated Approach.
ARCADIA, with its modeler CAPELLA, is a MBSE solution supporting system modeling activities. Based on 4 architectural layers, which are Operational Analysis, System Analysis, Logical and Physical Architecture, it is a structured architecture engineering method for defining and validating multi-domain systems.
This talk will present an educational overview of the ARCADIA methodology and System Design Process from the NASA SE, by introducing MBSE artefacts for space system.
The HUBBLE Space Telescope (HST) is a Cassegrain reflector telescope. Orbiting above the earth, HST elaborates a clear view of the universe free from the blurring and absorbing effects of the atmosphere. In order to illustrate the journey throughout CAPELLA, the HST will be introduced, as example, based on public information available.
Capella Days 2021 | Enhancing CubeSat design through ARCADIA and Capella: a c...Obeo
The new space economy asks for an overall improvement of systems engineering practices due to aggressive development time and complex systems design, implementation and operation by a number of players who grow with mission complexity. The talk proposes a critical analysis of a Model-Based Systems Engineering approach using ARCADIA and the Capella tool, applied to real CubeSat mission, with the aim of showing potentials and lacks.
Firstly, the way requirements are managed and traced using the Requirements Viewpoint is presented, highlighting the necessity of having a dedicated diagram for the trees generation; a solution to that is proposed in order to easily trace backwards requirements whenever needed. Following the ARCADIA method, the approach begins with the high-level objectives definition through the Operational Analysis, moving to a first internal functional analysis exploiting the second level of Capella, the System Analysis. The Logical Architecture is then developed introducing the concept of subsystem, leading to big decisions which will drive the successive Physical Architecture. The latter opens the road to all CubeSat components modeling using the concept of Node Physical Component, together with physical interfaces definition. Great use of all Capella concepts is done, such as Functional Chains, Control Functions, Replicas, Basic Mass and Price Viewpoints etc.
As the approach has been applied to a real space project, Phases and Modes have also been modeled exploiting respectively Scenario Diagrams, also used to define mission Concept of Operations, and State Machine Diagrams. Some thoughts oriented toward an improvement of the Modes management will be discussed. Lastly, ARCADIA and Capella do not provide a proper way of dealing with Assembly, Integration, Verification and Testing activities within the same architectural model, therefore an innovative approach is proposed and discussed to include such aspects in the model.
Modeling & Simulation of CubeSat-based Missions'Concept of OperationsObeo
Discover how Arcadia/Capella is used to model and simulate concept of operations scenarios for CubeSat-based missions. During this webinar, Danilo Pallamin de Almeida, who worked as a Space Systems Engineer for the NanosatC-BR2 mission at INPE, the Brazilian Institute for Space Research, will present how CubeSat-based missions have been modeled with Capella.
The model describing an initial architecture mission and concept of operations (CONOPS) is used to generate a script that configures a satellite simulator with the corresponding mission parameters.
You will see how it allows the INPE to:
- run concept of operations scenarios simulations,
- use the results for power/data-budget analyses and trade studies
System of Systems modeling comes with a tough decision for practitioners using traditional SysML V1 tools. Do I go with SysML V1, or do I look at Unified Architecture Framework? Capella eliminates that challenge with one notation that can be used for both.
By Tony Komar (Siemens)
Tony Komar has been practicing and supporting systems engineering for over 35 years.
Today he is a key contributor to the development and deployment of model-based system engineering products for Siemens Digital Industries Software.
Capella Days 2021 | A STEP towards Model-based: Case Study covering Conceptua...Obeo
STEP (Spherical Tokamak for Energy Production) is a £220M project aiming to develop a conceptual design for a First of a Kind (FOAK) commercially viable Fusion Power Plant by 2024.
Designing a power plant at this scale comes with immense challenges: Systems engineering approach is relatively new to the industry, where the industry has been heavily research based and engineering processes are not fully in place. UKAEA, the organisation running the STEP project, is applying Model-Based Systems Engineering using the Capella tool.
The focus of our approach in managing the complexity of the system is to perform system analysis and logical architecture analysis, to generate engineering artefacts from the model. Through NGO (Needs, Goals, Objectives) analysis key system capabilities were realised to functional chains, which forms the basis for further refinement of the Logical Architecture. The differentiation between logical and physical architectures has ensured that the design stays at the logical space and the team focuses on defining the problem space. This approach has improved interface management process, by creating model-based interface documents, using the model as ‘single source of truth’ to achieve consistency. The architecture definition activities allowed early formalisation of the textual requirements, to drive detailed engineering design in the next phase.
Adopting Capella comes with challenges - one of which stems from the unique characteristic of the concept phase – the need to generate architectural variants and evaluating them. The framework and the language are limited in performing variant modelling, a topic UKAEA plans to investigate further. Another challenge was that middle-out approach was favoured for STEP whereas Arcadia method prefers the top-down approach.
Throughout this journey, adopting Capella with its use-friendly interfaces has allowed us to better engage with the programme in the MBSE approach and indoctrinate better SE practices.
Is your system robust to the loss of one or more functions? Does your system require interaction with other systems to operate safely?
Does the design and operational concept of the system include contingency means? Do these contingency means correctly mitigate the risks?
These and other similar considerations are becoming more important with the emergence of autonomous systems and complex systems of systems. The introduction of digital tools and in particular model-based systems engineering allows to capture the complexity of these products starting from the operational analysis and supporting the process throughout the whole product life cycle.
With ATICA, system architects and designers will be able to analyze safety implications starting from the conceptual needs and mission description; modeling risks associated to the system, assessing the probability of occurrence and severity, and deciding upon the needs of contingency and mitigation means. ATICA enriches the Arcadia framework and provides safety analysis capabilities for each step of the system definition, design, and verification process.
In this webinar, we will address an example with an autonomous vertical take-off and landing (VTOL) vehicle, conceived for operation in urban environments (urban air mobility). We will present the operational description and system architecture, and we will conduct the Functional Hazard Analysis (FHA) directly from Capella and aligned with the normative standards in force in the aeronautic industry (ARP-4761 / ED-135).
Finally, we will introduce safety analysis covering the logical and physical architecture levels, showcasing the use of Capella, Arcadia and ATICA for Fault Tree Analysis (FTA) and Failure Modes and Effects Analysis (FMEA).
***
Pablo López Negro
Chief Innovation Officer at Anzen Engineering
Pablo López Negro is the product owner of ATICA MBSA. He has been involved in the aerospace industry for nearly 10 years. Started as guidance, navigation and control engineer where he first discovered model-based / model-driven approaches and Capella. Then he evolved towards a system engineering position before becoming MBSE specialist and designer/developer of MBSE frameworks in Anzen.
CapellaDays2022 | NavalGroup | Closing the gap between traditional engineerin...Obeo
Closing the gap between traditional engineering and digital-native model-based driven engineering requires helping engineers to embrace new techniques. Naval Group decided to tackle the following issues: lack of interoperability with other systems, lack of bridge between functional definitions in PID schemas and MBSE physical layers, lack of documenting cross-layers relationships for a specific object's type.
CapellaDays2022 | Saratech | Interface Control Document Generation and Linkag...Obeo
Generation of Interface Control Documents (ICDs) using a model-based method has a number of advantages over text-based approaches. This paper describes the Python-based software that was written to automatically generate different versions of an ICD from a structure model in Capella. One use case for this approach is checking parts changes captured in the Engineering Bill of Materials (EBOM) using a PLM tool. We demonstrate an automated workflow that links changes in the EBOM to a request to vet the change against the ICD. This presentation will discuss our rationale, approach, results, and lessons learned.
STPA Analysis of Automotive Safety Using Arcadia and CapellaDavid Hetherington
This presentation demonstrates the use of the Arcadia methodology and the open source Capella tool to implement a STPA-based analysis technique that augments the conventional HARA, HAZOP. The STPA approach extends the conventional methods to include a holistic perspective considering hardware, software, humans, and control failures in a balanced manner.
Delivered by David Hetherington and Pascal Roques at the ERTS 2022 conference in Toulouse, France on 1 June 2022.
Capella Days 2021 | Enhancing CubeSat design through ARCADIA and Capella: a c...Obeo
The new space economy asks for an overall improvement of systems engineering practices due to aggressive development time and complex systems design, implementation and operation by a number of players who grow with mission complexity. The talk proposes a critical analysis of a Model-Based Systems Engineering approach using ARCADIA and the Capella tool, applied to real CubeSat mission, with the aim of showing potentials and lacks.
Firstly, the way requirements are managed and traced using the Requirements Viewpoint is presented, highlighting the necessity of having a dedicated diagram for the trees generation; a solution to that is proposed in order to easily trace backwards requirements whenever needed. Following the ARCADIA method, the approach begins with the high-level objectives definition through the Operational Analysis, moving to a first internal functional analysis exploiting the second level of Capella, the System Analysis. The Logical Architecture is then developed introducing the concept of subsystem, leading to big decisions which will drive the successive Physical Architecture. The latter opens the road to all CubeSat components modeling using the concept of Node Physical Component, together with physical interfaces definition. Great use of all Capella concepts is done, such as Functional Chains, Control Functions, Replicas, Basic Mass and Price Viewpoints etc.
As the approach has been applied to a real space project, Phases and Modes have also been modeled exploiting respectively Scenario Diagrams, also used to define mission Concept of Operations, and State Machine Diagrams. Some thoughts oriented toward an improvement of the Modes management will be discussed. Lastly, ARCADIA and Capella do not provide a proper way of dealing with Assembly, Integration, Verification and Testing activities within the same architectural model, therefore an innovative approach is proposed and discussed to include such aspects in the model.
Modeling & Simulation of CubeSat-based Missions'Concept of OperationsObeo
Discover how Arcadia/Capella is used to model and simulate concept of operations scenarios for CubeSat-based missions. During this webinar, Danilo Pallamin de Almeida, who worked as a Space Systems Engineer for the NanosatC-BR2 mission at INPE, the Brazilian Institute for Space Research, will present how CubeSat-based missions have been modeled with Capella.
The model describing an initial architecture mission and concept of operations (CONOPS) is used to generate a script that configures a satellite simulator with the corresponding mission parameters.
You will see how it allows the INPE to:
- run concept of operations scenarios simulations,
- use the results for power/data-budget analyses and trade studies
System of Systems modeling comes with a tough decision for practitioners using traditional SysML V1 tools. Do I go with SysML V1, or do I look at Unified Architecture Framework? Capella eliminates that challenge with one notation that can be used for both.
By Tony Komar (Siemens)
Tony Komar has been practicing and supporting systems engineering for over 35 years.
Today he is a key contributor to the development and deployment of model-based system engineering products for Siemens Digital Industries Software.
Capella Days 2021 | A STEP towards Model-based: Case Study covering Conceptua...Obeo
STEP (Spherical Tokamak for Energy Production) is a £220M project aiming to develop a conceptual design for a First of a Kind (FOAK) commercially viable Fusion Power Plant by 2024.
Designing a power plant at this scale comes with immense challenges: Systems engineering approach is relatively new to the industry, where the industry has been heavily research based and engineering processes are not fully in place. UKAEA, the organisation running the STEP project, is applying Model-Based Systems Engineering using the Capella tool.
The focus of our approach in managing the complexity of the system is to perform system analysis and logical architecture analysis, to generate engineering artefacts from the model. Through NGO (Needs, Goals, Objectives) analysis key system capabilities were realised to functional chains, which forms the basis for further refinement of the Logical Architecture. The differentiation between logical and physical architectures has ensured that the design stays at the logical space and the team focuses on defining the problem space. This approach has improved interface management process, by creating model-based interface documents, using the model as ‘single source of truth’ to achieve consistency. The architecture definition activities allowed early formalisation of the textual requirements, to drive detailed engineering design in the next phase.
Adopting Capella comes with challenges - one of which stems from the unique characteristic of the concept phase – the need to generate architectural variants and evaluating them. The framework and the language are limited in performing variant modelling, a topic UKAEA plans to investigate further. Another challenge was that middle-out approach was favoured for STEP whereas Arcadia method prefers the top-down approach.
Throughout this journey, adopting Capella with its use-friendly interfaces has allowed us to better engage with the programme in the MBSE approach and indoctrinate better SE practices.
Is your system robust to the loss of one or more functions? Does your system require interaction with other systems to operate safely?
Does the design and operational concept of the system include contingency means? Do these contingency means correctly mitigate the risks?
These and other similar considerations are becoming more important with the emergence of autonomous systems and complex systems of systems. The introduction of digital tools and in particular model-based systems engineering allows to capture the complexity of these products starting from the operational analysis and supporting the process throughout the whole product life cycle.
With ATICA, system architects and designers will be able to analyze safety implications starting from the conceptual needs and mission description; modeling risks associated to the system, assessing the probability of occurrence and severity, and deciding upon the needs of contingency and mitigation means. ATICA enriches the Arcadia framework and provides safety analysis capabilities for each step of the system definition, design, and verification process.
In this webinar, we will address an example with an autonomous vertical take-off and landing (VTOL) vehicle, conceived for operation in urban environments (urban air mobility). We will present the operational description and system architecture, and we will conduct the Functional Hazard Analysis (FHA) directly from Capella and aligned with the normative standards in force in the aeronautic industry (ARP-4761 / ED-135).
Finally, we will introduce safety analysis covering the logical and physical architecture levels, showcasing the use of Capella, Arcadia and ATICA for Fault Tree Analysis (FTA) and Failure Modes and Effects Analysis (FMEA).
***
Pablo López Negro
Chief Innovation Officer at Anzen Engineering
Pablo López Negro is the product owner of ATICA MBSA. He has been involved in the aerospace industry for nearly 10 years. Started as guidance, navigation and control engineer where he first discovered model-based / model-driven approaches and Capella. Then he evolved towards a system engineering position before becoming MBSE specialist and designer/developer of MBSE frameworks in Anzen.
CapellaDays2022 | NavalGroup | Closing the gap between traditional engineerin...Obeo
Closing the gap between traditional engineering and digital-native model-based driven engineering requires helping engineers to embrace new techniques. Naval Group decided to tackle the following issues: lack of interoperability with other systems, lack of bridge between functional definitions in PID schemas and MBSE physical layers, lack of documenting cross-layers relationships for a specific object's type.
CapellaDays2022 | Saratech | Interface Control Document Generation and Linkag...Obeo
Generation of Interface Control Documents (ICDs) using a model-based method has a number of advantages over text-based approaches. This paper describes the Python-based software that was written to automatically generate different versions of an ICD from a structure model in Capella. One use case for this approach is checking parts changes captured in the Engineering Bill of Materials (EBOM) using a PLM tool. We demonstrate an automated workflow that links changes in the EBOM to a request to vet the change against the ICD. This presentation will discuss our rationale, approach, results, and lessons learned.
STPA Analysis of Automotive Safety Using Arcadia and CapellaDavid Hetherington
This presentation demonstrates the use of the Arcadia methodology and the open source Capella tool to implement a STPA-based analysis technique that augments the conventional HARA, HAZOP. The STPA approach extends the conventional methods to include a holistic perspective considering hardware, software, humans, and control failures in a balanced manner.
Delivered by David Hetherington and Pascal Roques at the ERTS 2022 conference in Toulouse, France on 1 June 2022.
Introduction to Capella and Arcadia with a Simple SystemObeo
Discover both Capella and Arcadia with an example of product design
Learn how to build a toy catapult system thanks to the Arcadia method and the Capella open MBSE tool.
In this Webinar, We:
- Distinguish between systems engineering, which is concerned with the entire design-build-test-deploy cycle of systems development, and systems architecture, which is concerned
with system concept development and architectural design.
- Contrast the System Modeling Language, SysML,
appropriate for systems engineering, with the more focused tool, Capella, and its associated methodology, Arcadia,
which is more appropriate for systems architecture development.
- Provide an overview of the attractive features of Capella,
from the point of view of initiating modelers into the language of systems architecture and briefly demonstrate our longer free public tutorial.
This webinar was driven by Professor Peter L. Jackson
Pr. Jackson is Head, Engineering Systems and Design Pillar at Singapore University of Technology and Design. He served as the Director of the Cornell University Systems Engineering Program and led the introduction of its online Master of Engineering degree program in systems engineering ranked in the top eight such programs by US News and World Report. He published over thirty articles and is the author of an introductory text on systems engineering, 'Getting Design Right: A Systems Approach'. He is a celebrated instructor of industrial engineering and the creator of dozens of experiential learning games and tools.
A common need in system architecture design is to verify that if the architect is correct and can satisfy its requirements.
Execution of system architect model means to interact with state machines to test system’s control logic. It can verify if the logical sequences of functions and interfaces in different scenarios are desired.
However, only sequence itself is not enough to verify its consequence or output. So we need each function to do what it is supposed to do during model execution to verify its output, and that is what we called “simulation”.
This presentation introduced how to embed Python or MATLAB® codes inside functions to do “simulation” within Capella.
Nowadays, we are surrounded by system of systems, autonomous systems, interconnected systems or distributed heterogeneous systems with an increase in architecture complexity.
Keeping these systems operational is a challenge as the number of potential failures which may affect their availability also increases drastically. In order to optimize availability, maintenance activities have to be designed within the design phase of the system.
Whatever the implementation choice, detection, diagnostic or prevention of failures require tests.
The goal for autonomous systems also pushes towards embedded detection and prevention capabilities and thus arguing and decision making between system engineers and maintenance engineers to share solutions in their respective activities.
In this presentation, we talk about the ability of a system designed with Capella to be tested, including in the maintenance phase. This means to interconnect several kinds of models representing different perspectives: System Design (MBSE), RAMS Analysis (Reliability, Availability, Maintainability and Safety) and Testability.
We present how a MBSE approach with Capella can be used to initiate a testability study performed with the eXpress tool from DSI International.
Strategies and Tools for Model Reuse with CapellaObeo
How to manage libraries and building blocks?
Reusing models or parts of models with Capella
is not only conceptually appealing, it is a real productivity enabler.
But it is also a true challenge!
Technical solutions initially dedicated to simple duplication
and synchronisation of model parts have recently evolved
and now enable multiple, classical use cases of reusing models.
In this webinar, we will illustrate:
How the Capella technology of replicable elements (aka REC/RPL) both enables
flexible design workflows (including instance-driven modeling) and
makes possible the modeling of architectures by assembly of building blocks.
How Yuzu leverages Capella to help manage the life-cycle
of building blocks and model assets, their dependencies,
their versioning, their publication, etc.
Architecture frameworks provide an approach to describing systems and the presentation of these elements and relationships to deliver the stakeholder needs. Essentially, frameworks provide templates for our engineering artefacts.
The design of a framework must accommodate a level of freedom in its usage; specific enough to answer the majority of stakeholder concerns whilst generic enough to allow for differences between projects. This balancing act often results in framework design being more generic to allow for a wider audience. Having an untailored framework, which is more ‘open’, can lead to creating inconsistent viewpoints.
Arcadia is one such framework as implemented through the Capella tool. The framework provides 4 perspectives/levels for product definition:
- The Operational Analysis, where the user needs are considered. Note: no concept of the System at this level.
- The System Analysis, where we define the contribution and scope of the System as a ‘black box’, identifying external interfaces, and top-level system functions.
- The Logical Architecture, where we break the System down into logical ‘blocks’ and decompose the functionality.
- The Physical Architecture, in which we define a (candidate) physical architecture, further decompose the functions, and deploy this functionality to the physical sub-systems, hardware, software and/or firmware.
In this talk, we acknowledge the strengths of the Arcadia framework, and the benefits it brings, whilst considering the need to tailor the generic viewpoints. We will provide examples of how we have adopted the generic Arcadia framework and further specified some of the viewpoints to meet the needs of our stakeholders. We will discuss future work looking at how we can translate these specialisations across other areas of the model. Finally, we will provide some suggestions and advice on tailoring views to meet your own needs and ensuring stakeholder engagement with the model.
CapellaDays2022 | ThermoFisher - ESI TNO | A method for quantitative evaluati...Obeo
Development of high-tech systems is a complex task done by diverse specialists distributed across the globe. Reference architectures including a clear functional breakdowns can support them and support their decisions. This presentation proposes an approach to improve the development of advanced electron microscopes by using Capella as an authoritative source of information. To support design decisions, a Capella AddOn has been developed to obtain quantitative information, such as throughput numbers, for a particular workflow. First, we will illustrate how functional and system decompositions can be captured and serve as company-wide architecting assets to inform design decisions. Next, we will outline how simulating Capella models can bring valuable insights to modelers. During a demo, we’ll simulate Capella’s Functional chains using the open-source simulation tool POOSL (https://github.com/eclipse/poosl) , and visualize results using the freely available TRACE4CPS tool (https://www.eclipse.org/trace4cps/). Re-using functions from the reference architecture allows us reason about design aspects such as the relation between throughput and design choices about function allocation and parallelism.
***
The open-source code of the solution is available at https://github.com/TNO/capella-workflow-dse
Capella Days 2021 | Where to Start with MBSE when Thousands of System Require...Obeo
The Thales OneSKY Australia Program is delivering a new Australia-wide integrated Civil and Military Air Traffic Management System, known as CMATS. CMATS replaces the current civilian Air Traffic Management (ATM) system and Defence ATM system, delivering the most advanced and integrated ATM system in the world. It will manage more than 11% of the earth’s airspace and will deliver Air Traffic Services to some of the world’s busiest air routes.
Scope: Over the last 4 years of the Design phases of the program, the System-of-Systems Architecture team has defined and deployed a new way of working by focussing on capturing the system-of-systems architecture using state-of-the-art modelling techniques.
A plan was put in place where the team collectively defined a target set of modelling goals in order to grow the team’s competency. Part of this plan was a roadmap for the longer term which focused on extending the current approach to further increase the business value of the architecture modelling activities.
This approach has resulted in a stable working environment that not only allows the management of consistency and complexity, but also enables the team to collaboratively and efficiently work on the architecture definition, which has been critical during the recent working from home period and hectic project phases.
The key Capella solutions that are used within this activity are the Team for Capella solution, application of the Requirements Viewpoint and the Property Value Management Tool.
One of the important aspects of the modelling plan is to ensure information within the model can be used by the wider organisation, this is achieved through a Thales specific documentation generation solution and a bespoke csv export capability that allows to export data from the information captured in the architecture model.
This talk will cover the modelling goals for this activity; where the team is standing today; the best practices and lessons learned.
Scripting with Python to interact with Capella modelObeo
Scripting with Python to interact with Capella model
Have you ever wanted to easily extract engineering data from your Capella model? Have you ever wanted to easily modify your Capella model and import information into it to update it?
This webinar presents a prototype Capella Add-on that will address several example use cases
- Read information from a Capella model and export to Excel, with queries
- Update information in a Capella model
- Add elements in a Capella model
This new Capella add-on uses a common scripting language, not dedicated to Capella: Python.
- It offers the capacity to use sample scripts addressing basic need and to build its own scripts, with libraries for common add-ons (Requirement, PVMT)
- It’s easy to share, to use, has high customization capabilities
support of Capella and Team for Capella, wide compatibility with Capella versions
It is presented by :
- Sophie Plazanet (Thales Group) - MBSE Specialist
Master of Engineering & Master of Research in Advanced Systems & Robotics – Arts & Métiers ParisTech
- Arnaud Dieumegard (Obeo) - Eclipse Modeling Consultant
Ph.D. in Reliability for Systems and Software - INP Toulouse
To illustrate the examples, you'll find the videos on this playlist: https://bit.ly/capella_webinar_211216_playlist
CapellaDays2022 | Politecnico di Milano | Interplanetary Space Mission as a r...Obeo
Systems engineering is an iterative approach traditionally applied one-way, from the definition of the user needs to the implementation of a solution that satisfies certain requirements and is constrained by cost and schedule. This presentation instead aims at exploring the educational benefits of applying the opposite practice, thus retrieving system and subsystem level requirements based on a solution already implemented and taking advantage of the MBSE possibilities to realize a model of the system according to the ARCADIA method and systems engineering approach, using the Capella MBSE Tool. This reverse-engineering process has been applied to a renowned Space mission, the ESA Mars Express satellite, whose goal is to investigate all aspects of the martian environment, including the subsurface, surface and atmosphere of the planet, in order to search for evidence of extinct or extant life. The uppermost goal of this project is to demonstrate the benefits for university students at a Master's level keen on systems engineering in implementing the Capella tool to retrieve the system architecture and the operational processes in a "reversed" strategy. In this work, students have been compelled to apply systems engineering processes to justify the design choices and exploit the already well-known missions and capabilities to build the architecture and functional chains as a starting point for the reverse engineering of the identified subsystems. The results prove it is possible, and also recommendable time-wise, to teach Space engineering and Systems engineering students by using this inverse approach, rather than the canonic one in which students have to design a whole mission from scratch.
[Capella Days 2020] Innovating with MBSE – Medical Device ExampleObeo
by Tony Komar (Siemens)
Sustained innovation is the goal of many development organizations. Sustaining innovation is depicted on an Innovation as matrix as the result of a well-defined problem, and a well-defined domain definition. An example will be presented how an MBSE tool, based on open-source tool Capella, can enhance both the problem definition and domain definition of a ventilator. It will show how the MBSE tool enhanced the understanding of the problem, and how that understanding can lead to an innovative solution.
Connecting Textual Requirements with Capella Models Obeo
SES ENGINEERING Studio: Achieving the perfect equilibrium between Textual Requirements and Models in Capella enhanced by Automatic Interoperability, Quality & Traceability operations
The importance of models is imperative in any Systems Engineering project. However, truth is not exclusively found within models. The need to describe external contracts, regulations, or non-functional requirements, for instance, can be more efficiently satisfied by using textual specifications. In order to achieve the desired “Common Source of Truth”, model and textual requirements must be connected and coexist, desirable enhanced by the automatization of the consistency checking, automatically modifying one side when changes are produced on the other end...
Within The REUSE Company, we have realised how crucial it is to facilitate this connection and provide Systems Engineers with the tools required for applying SE across the entire process as seamlessly as possible. This solution is the SES ENGINEERING Studio, and within this webinar, the following capabilities will be shown:
- The SES ENGINEERING Studio offers the capability to assess consistency between textual requirements and Capella models.
- Automatic generation of Capella models from Textual Requirements inside an RMS (Requirements Management System). This also involves the possibility to complete the exact opposite operation, generating textual requirements from Capella models.
- Seamless traceability management between textual requirements (in any RMS) and model elements in Capella; This includes the possibility to automatically suggest traces based on the semantic content of the textual requirement.
- If the preferred option is to maintain these textual requirements inside Capella, we offer the possibility to provide a round-trip process between any RMS and Requirements Viewpoint within Capella; thus, allowing that modification at either end, to be synchronized.
- Automatic quality assessment of Capella models following a number of pre-established rules or allowing the users to define tailored rules.
- Automatic interoperability between SysML and Arcadia models.
Presented by José Pereira and José Fuentes (The Reuse Company)
Rolls-Royce UseCase: Capella for large complex mechanical systemsObeo
Rolls-Royce is a pre-eminent engineering company focused on world-class power and propulsion systems.
This webinar will discuss how Rolls-Royce is using Arcadia / Capella to define the architecture of a large civil aerospace turbofan engine. MBSE promises to help manage system complexity and minimise the associated risk.
This webinar was driven by Jim Daly:
Jim Daly has nearly forty years’ experience in aerospace engine development: fuel systems; control systems; software development; process improvement and thirteen years in current role as a System Architect at Rolls-Royce, responsible for control system and whole engine architecture and since 2016 deployment of MBSE.
CapellaDays2022 | Thales | Stairway to heaven: Climbing the very first stepsObeo
We MBSE enthusiasts love to imagine or witness sophisticated model-based engineering practices. We dream or in the best cases take advantage of digital continuity, automation, large-scale consistency, integration of disciplines, and end-to-end impact analyses.
However, not all of our architect and engineer fellows are in a situation in which they can appreciate sophistication of engineering practices the same way as we do. Entangled in everyday problems and facing the pressure to deliver, they perceive the introduction of model-based practices as an additional risk for a benefit that too often appears intangible.
Reaching the top of the stairs requires climbing the very first steps. This talk focuses on one of the most challenging aspects of MBSE deployment: lowering the height of the first steps. Paired with a pragmatic and incremental change management strategy, Capella and its add-ons are precious helpers.
Capella Days 2021 | An example of model-centric engineering environment with ...Obeo
Today a number of EU railway operators are on a journey to define what the future of railway operations should look like. In Germany, DB AG works within the sector initiative Digitale Schiene Deutschland. Next to the implementation of ETCS/DSTW technology in the first stage, the initiatives aims in the second stage to improve the performance, quality and efficiency of the railway system by higher degrees of automation in traffic management, train driving and infrastructure operation. This requires implementation of new technologies like artificial intelligence, localization and perception sensors, cloud computing and 5G connectivity.
MBSE with Arcadia method step-by-step Physical Architecture.pdfHelder Castro
The objective of the Physical Architecture in defining the “real” concrete components that comprise the system. To start the Physical level based on the Logical level, Capella proposes transitions similar to those that we used when we went from the Operational Analysis to the System Analysis, then from the System Analysis to the Logical Architecture. Thus, it can be created as many Physical Functions as Logical Functions, by also keeping the Functional Exchanges and Functional Chains.
CapellaDays2022 | Thales DMS | A global engineering process based on MBSE to ...Obeo
Project Challenges
functional and non-functional requirements
big team, multi-business units, and multi-geographical sites
MBSE skills development
...
Project engineering process based on MBSE
multi-level MBSE approach (SSS, SSDD, transition to sub-systems, ...)
incremental engineering and AGILE development
engineering artefacts used and how they're linked (ARCADIA, conventional and AGILE artefacts)
Feed Forward
Our successes and pains
What we expect from Capella for the coming years
Simplifying MBSE Tasks with Capella and MapleMBSEObeo
Discover how to use Excel-based interfaces to collaborate on Capella models
MapleMBSE 2020.1 adds support for Capella. Organizations using Capella can now edit models within MapleMBSE, allowing them to simplify MBSE tasks and increase engagement with MBSE processes at their company.
During this webinar, you will see how to work with a Capella systems model using MapleMBSE
The demonstration will highlight how all stakeholders can collaborate through the systems model using task-specific, Excel-based interfaces found in MapleMBSE.
Model-based systems engineering is everywhere - everyone talks about it, everyone wants to use it, but what is actually behind it? This question will be outlined by means of a playful approach and a real problem: "I pack my suitcase and take with me...".
Based on this problem, we will successively use the game to pack the suitcase with the help of SE and finally MBSE and present it by means of a small demonstration. Let's go together on the hopefully soon journey and pack our suitcase.
[ Capella Day 2019 ] Augmenting requirements with models to improve the artic...Obeo
Model-based systems engineering has developed significantly over the last few years, resulting in an increased usage of models in systems specification and architecture description. The question of the positioning of requirement engineering versus MBSE is a recurrent one.
This talk describes one vision of this articulation where textual and model requirements actually complete each other. The results are improved contracts across engineering levels and more formalized V&V practices.
Stéphane Bonnet, Thales Corporate Engineering
Stéphane Bonnet is in charge of Thales Corporate MBSE Coaching and Design Authority of the Capella open source modeling solution. For the last ten years, he has led the development of Capella and has been an active contributor to the Arcadia model-based method for systems, hardware and software architectural design. In Thales, he is animating a wide community of modeling experts from all domains and countries to investigate low-maturity modeling topics, capture end-user needs, and orient method and workbench roadmaps.
MBSE with Arcadia method step-by-step System Analysis.pdfHelder Castro
The Operational Analysis described is the previous article, MBSE with Arcadia method step-by-step: Operational Analysis [1], involves defining and creating a domain model, independently of the future system to be realized. The principle is to create a level of abstraction from the system under study in order to focus on the needs of the different stakeholders.
The System Analysis level, on the other hand, is where the System-of-Interest (SoI) to be defined emerges. The following questions for the system definition needs to be answered:
• What must the system do?
• What are the external interfaces to the system?
In order to answer the first question, the expected behaviour is modelled as Functions.
Introduction to Capella and Arcadia with a Simple SystemObeo
Discover both Capella and Arcadia with an example of product design
Learn how to build a toy catapult system thanks to the Arcadia method and the Capella open MBSE tool.
In this Webinar, We:
- Distinguish between systems engineering, which is concerned with the entire design-build-test-deploy cycle of systems development, and systems architecture, which is concerned
with system concept development and architectural design.
- Contrast the System Modeling Language, SysML,
appropriate for systems engineering, with the more focused tool, Capella, and its associated methodology, Arcadia,
which is more appropriate for systems architecture development.
- Provide an overview of the attractive features of Capella,
from the point of view of initiating modelers into the language of systems architecture and briefly demonstrate our longer free public tutorial.
This webinar was driven by Professor Peter L. Jackson
Pr. Jackson is Head, Engineering Systems and Design Pillar at Singapore University of Technology and Design. He served as the Director of the Cornell University Systems Engineering Program and led the introduction of its online Master of Engineering degree program in systems engineering ranked in the top eight such programs by US News and World Report. He published over thirty articles and is the author of an introductory text on systems engineering, 'Getting Design Right: A Systems Approach'. He is a celebrated instructor of industrial engineering and the creator of dozens of experiential learning games and tools.
A common need in system architecture design is to verify that if the architect is correct and can satisfy its requirements.
Execution of system architect model means to interact with state machines to test system’s control logic. It can verify if the logical sequences of functions and interfaces in different scenarios are desired.
However, only sequence itself is not enough to verify its consequence or output. So we need each function to do what it is supposed to do during model execution to verify its output, and that is what we called “simulation”.
This presentation introduced how to embed Python or MATLAB® codes inside functions to do “simulation” within Capella.
Nowadays, we are surrounded by system of systems, autonomous systems, interconnected systems or distributed heterogeneous systems with an increase in architecture complexity.
Keeping these systems operational is a challenge as the number of potential failures which may affect their availability also increases drastically. In order to optimize availability, maintenance activities have to be designed within the design phase of the system.
Whatever the implementation choice, detection, diagnostic or prevention of failures require tests.
The goal for autonomous systems also pushes towards embedded detection and prevention capabilities and thus arguing and decision making between system engineers and maintenance engineers to share solutions in their respective activities.
In this presentation, we talk about the ability of a system designed with Capella to be tested, including in the maintenance phase. This means to interconnect several kinds of models representing different perspectives: System Design (MBSE), RAMS Analysis (Reliability, Availability, Maintainability and Safety) and Testability.
We present how a MBSE approach with Capella can be used to initiate a testability study performed with the eXpress tool from DSI International.
Strategies and Tools for Model Reuse with CapellaObeo
How to manage libraries and building blocks?
Reusing models or parts of models with Capella
is not only conceptually appealing, it is a real productivity enabler.
But it is also a true challenge!
Technical solutions initially dedicated to simple duplication
and synchronisation of model parts have recently evolved
and now enable multiple, classical use cases of reusing models.
In this webinar, we will illustrate:
How the Capella technology of replicable elements (aka REC/RPL) both enables
flexible design workflows (including instance-driven modeling) and
makes possible the modeling of architectures by assembly of building blocks.
How Yuzu leverages Capella to help manage the life-cycle
of building blocks and model assets, their dependencies,
their versioning, their publication, etc.
Architecture frameworks provide an approach to describing systems and the presentation of these elements and relationships to deliver the stakeholder needs. Essentially, frameworks provide templates for our engineering artefacts.
The design of a framework must accommodate a level of freedom in its usage; specific enough to answer the majority of stakeholder concerns whilst generic enough to allow for differences between projects. This balancing act often results in framework design being more generic to allow for a wider audience. Having an untailored framework, which is more ‘open’, can lead to creating inconsistent viewpoints.
Arcadia is one such framework as implemented through the Capella tool. The framework provides 4 perspectives/levels for product definition:
- The Operational Analysis, where the user needs are considered. Note: no concept of the System at this level.
- The System Analysis, where we define the contribution and scope of the System as a ‘black box’, identifying external interfaces, and top-level system functions.
- The Logical Architecture, where we break the System down into logical ‘blocks’ and decompose the functionality.
- The Physical Architecture, in which we define a (candidate) physical architecture, further decompose the functions, and deploy this functionality to the physical sub-systems, hardware, software and/or firmware.
In this talk, we acknowledge the strengths of the Arcadia framework, and the benefits it brings, whilst considering the need to tailor the generic viewpoints. We will provide examples of how we have adopted the generic Arcadia framework and further specified some of the viewpoints to meet the needs of our stakeholders. We will discuss future work looking at how we can translate these specialisations across other areas of the model. Finally, we will provide some suggestions and advice on tailoring views to meet your own needs and ensuring stakeholder engagement with the model.
CapellaDays2022 | ThermoFisher - ESI TNO | A method for quantitative evaluati...Obeo
Development of high-tech systems is a complex task done by diverse specialists distributed across the globe. Reference architectures including a clear functional breakdowns can support them and support their decisions. This presentation proposes an approach to improve the development of advanced electron microscopes by using Capella as an authoritative source of information. To support design decisions, a Capella AddOn has been developed to obtain quantitative information, such as throughput numbers, for a particular workflow. First, we will illustrate how functional and system decompositions can be captured and serve as company-wide architecting assets to inform design decisions. Next, we will outline how simulating Capella models can bring valuable insights to modelers. During a demo, we’ll simulate Capella’s Functional chains using the open-source simulation tool POOSL (https://github.com/eclipse/poosl) , and visualize results using the freely available TRACE4CPS tool (https://www.eclipse.org/trace4cps/). Re-using functions from the reference architecture allows us reason about design aspects such as the relation between throughput and design choices about function allocation and parallelism.
***
The open-source code of the solution is available at https://github.com/TNO/capella-workflow-dse
Capella Days 2021 | Where to Start with MBSE when Thousands of System Require...Obeo
The Thales OneSKY Australia Program is delivering a new Australia-wide integrated Civil and Military Air Traffic Management System, known as CMATS. CMATS replaces the current civilian Air Traffic Management (ATM) system and Defence ATM system, delivering the most advanced and integrated ATM system in the world. It will manage more than 11% of the earth’s airspace and will deliver Air Traffic Services to some of the world’s busiest air routes.
Scope: Over the last 4 years of the Design phases of the program, the System-of-Systems Architecture team has defined and deployed a new way of working by focussing on capturing the system-of-systems architecture using state-of-the-art modelling techniques.
A plan was put in place where the team collectively defined a target set of modelling goals in order to grow the team’s competency. Part of this plan was a roadmap for the longer term which focused on extending the current approach to further increase the business value of the architecture modelling activities.
This approach has resulted in a stable working environment that not only allows the management of consistency and complexity, but also enables the team to collaboratively and efficiently work on the architecture definition, which has been critical during the recent working from home period and hectic project phases.
The key Capella solutions that are used within this activity are the Team for Capella solution, application of the Requirements Viewpoint and the Property Value Management Tool.
One of the important aspects of the modelling plan is to ensure information within the model can be used by the wider organisation, this is achieved through a Thales specific documentation generation solution and a bespoke csv export capability that allows to export data from the information captured in the architecture model.
This talk will cover the modelling goals for this activity; where the team is standing today; the best practices and lessons learned.
Scripting with Python to interact with Capella modelObeo
Scripting with Python to interact with Capella model
Have you ever wanted to easily extract engineering data from your Capella model? Have you ever wanted to easily modify your Capella model and import information into it to update it?
This webinar presents a prototype Capella Add-on that will address several example use cases
- Read information from a Capella model and export to Excel, with queries
- Update information in a Capella model
- Add elements in a Capella model
This new Capella add-on uses a common scripting language, not dedicated to Capella: Python.
- It offers the capacity to use sample scripts addressing basic need and to build its own scripts, with libraries for common add-ons (Requirement, PVMT)
- It’s easy to share, to use, has high customization capabilities
support of Capella and Team for Capella, wide compatibility with Capella versions
It is presented by :
- Sophie Plazanet (Thales Group) - MBSE Specialist
Master of Engineering & Master of Research in Advanced Systems & Robotics – Arts & Métiers ParisTech
- Arnaud Dieumegard (Obeo) - Eclipse Modeling Consultant
Ph.D. in Reliability for Systems and Software - INP Toulouse
To illustrate the examples, you'll find the videos on this playlist: https://bit.ly/capella_webinar_211216_playlist
CapellaDays2022 | Politecnico di Milano | Interplanetary Space Mission as a r...Obeo
Systems engineering is an iterative approach traditionally applied one-way, from the definition of the user needs to the implementation of a solution that satisfies certain requirements and is constrained by cost and schedule. This presentation instead aims at exploring the educational benefits of applying the opposite practice, thus retrieving system and subsystem level requirements based on a solution already implemented and taking advantage of the MBSE possibilities to realize a model of the system according to the ARCADIA method and systems engineering approach, using the Capella MBSE Tool. This reverse-engineering process has been applied to a renowned Space mission, the ESA Mars Express satellite, whose goal is to investigate all aspects of the martian environment, including the subsurface, surface and atmosphere of the planet, in order to search for evidence of extinct or extant life. The uppermost goal of this project is to demonstrate the benefits for university students at a Master's level keen on systems engineering in implementing the Capella tool to retrieve the system architecture and the operational processes in a "reversed" strategy. In this work, students have been compelled to apply systems engineering processes to justify the design choices and exploit the already well-known missions and capabilities to build the architecture and functional chains as a starting point for the reverse engineering of the identified subsystems. The results prove it is possible, and also recommendable time-wise, to teach Space engineering and Systems engineering students by using this inverse approach, rather than the canonic one in which students have to design a whole mission from scratch.
[Capella Days 2020] Innovating with MBSE – Medical Device ExampleObeo
by Tony Komar (Siemens)
Sustained innovation is the goal of many development organizations. Sustaining innovation is depicted on an Innovation as matrix as the result of a well-defined problem, and a well-defined domain definition. An example will be presented how an MBSE tool, based on open-source tool Capella, can enhance both the problem definition and domain definition of a ventilator. It will show how the MBSE tool enhanced the understanding of the problem, and how that understanding can lead to an innovative solution.
Connecting Textual Requirements with Capella Models Obeo
SES ENGINEERING Studio: Achieving the perfect equilibrium between Textual Requirements and Models in Capella enhanced by Automatic Interoperability, Quality & Traceability operations
The importance of models is imperative in any Systems Engineering project. However, truth is not exclusively found within models. The need to describe external contracts, regulations, or non-functional requirements, for instance, can be more efficiently satisfied by using textual specifications. In order to achieve the desired “Common Source of Truth”, model and textual requirements must be connected and coexist, desirable enhanced by the automatization of the consistency checking, automatically modifying one side when changes are produced on the other end...
Within The REUSE Company, we have realised how crucial it is to facilitate this connection and provide Systems Engineers with the tools required for applying SE across the entire process as seamlessly as possible. This solution is the SES ENGINEERING Studio, and within this webinar, the following capabilities will be shown:
- The SES ENGINEERING Studio offers the capability to assess consistency between textual requirements and Capella models.
- Automatic generation of Capella models from Textual Requirements inside an RMS (Requirements Management System). This also involves the possibility to complete the exact opposite operation, generating textual requirements from Capella models.
- Seamless traceability management between textual requirements (in any RMS) and model elements in Capella; This includes the possibility to automatically suggest traces based on the semantic content of the textual requirement.
- If the preferred option is to maintain these textual requirements inside Capella, we offer the possibility to provide a round-trip process between any RMS and Requirements Viewpoint within Capella; thus, allowing that modification at either end, to be synchronized.
- Automatic quality assessment of Capella models following a number of pre-established rules or allowing the users to define tailored rules.
- Automatic interoperability between SysML and Arcadia models.
Presented by José Pereira and José Fuentes (The Reuse Company)
Rolls-Royce UseCase: Capella for large complex mechanical systemsObeo
Rolls-Royce is a pre-eminent engineering company focused on world-class power and propulsion systems.
This webinar will discuss how Rolls-Royce is using Arcadia / Capella to define the architecture of a large civil aerospace turbofan engine. MBSE promises to help manage system complexity and minimise the associated risk.
This webinar was driven by Jim Daly:
Jim Daly has nearly forty years’ experience in aerospace engine development: fuel systems; control systems; software development; process improvement and thirteen years in current role as a System Architect at Rolls-Royce, responsible for control system and whole engine architecture and since 2016 deployment of MBSE.
CapellaDays2022 | Thales | Stairway to heaven: Climbing the very first stepsObeo
We MBSE enthusiasts love to imagine or witness sophisticated model-based engineering practices. We dream or in the best cases take advantage of digital continuity, automation, large-scale consistency, integration of disciplines, and end-to-end impact analyses.
However, not all of our architect and engineer fellows are in a situation in which they can appreciate sophistication of engineering practices the same way as we do. Entangled in everyday problems and facing the pressure to deliver, they perceive the introduction of model-based practices as an additional risk for a benefit that too often appears intangible.
Reaching the top of the stairs requires climbing the very first steps. This talk focuses on one of the most challenging aspects of MBSE deployment: lowering the height of the first steps. Paired with a pragmatic and incremental change management strategy, Capella and its add-ons are precious helpers.
Capella Days 2021 | An example of model-centric engineering environment with ...Obeo
Today a number of EU railway operators are on a journey to define what the future of railway operations should look like. In Germany, DB AG works within the sector initiative Digitale Schiene Deutschland. Next to the implementation of ETCS/DSTW technology in the first stage, the initiatives aims in the second stage to improve the performance, quality and efficiency of the railway system by higher degrees of automation in traffic management, train driving and infrastructure operation. This requires implementation of new technologies like artificial intelligence, localization and perception sensors, cloud computing and 5G connectivity.
MBSE with Arcadia method step-by-step Physical Architecture.pdfHelder Castro
The objective of the Physical Architecture in defining the “real” concrete components that comprise the system. To start the Physical level based on the Logical level, Capella proposes transitions similar to those that we used when we went from the Operational Analysis to the System Analysis, then from the System Analysis to the Logical Architecture. Thus, it can be created as many Physical Functions as Logical Functions, by also keeping the Functional Exchanges and Functional Chains.
CapellaDays2022 | Thales DMS | A global engineering process based on MBSE to ...Obeo
Project Challenges
functional and non-functional requirements
big team, multi-business units, and multi-geographical sites
MBSE skills development
...
Project engineering process based on MBSE
multi-level MBSE approach (SSS, SSDD, transition to sub-systems, ...)
incremental engineering and AGILE development
engineering artefacts used and how they're linked (ARCADIA, conventional and AGILE artefacts)
Feed Forward
Our successes and pains
What we expect from Capella for the coming years
Simplifying MBSE Tasks with Capella and MapleMBSEObeo
Discover how to use Excel-based interfaces to collaborate on Capella models
MapleMBSE 2020.1 adds support for Capella. Organizations using Capella can now edit models within MapleMBSE, allowing them to simplify MBSE tasks and increase engagement with MBSE processes at their company.
During this webinar, you will see how to work with a Capella systems model using MapleMBSE
The demonstration will highlight how all stakeholders can collaborate through the systems model using task-specific, Excel-based interfaces found in MapleMBSE.
Model-based systems engineering is everywhere - everyone talks about it, everyone wants to use it, but what is actually behind it? This question will be outlined by means of a playful approach and a real problem: "I pack my suitcase and take with me...".
Based on this problem, we will successively use the game to pack the suitcase with the help of SE and finally MBSE and present it by means of a small demonstration. Let's go together on the hopefully soon journey and pack our suitcase.
[ Capella Day 2019 ] Augmenting requirements with models to improve the artic...Obeo
Model-based systems engineering has developed significantly over the last few years, resulting in an increased usage of models in systems specification and architecture description. The question of the positioning of requirement engineering versus MBSE is a recurrent one.
This talk describes one vision of this articulation where textual and model requirements actually complete each other. The results are improved contracts across engineering levels and more formalized V&V practices.
Stéphane Bonnet, Thales Corporate Engineering
Stéphane Bonnet is in charge of Thales Corporate MBSE Coaching and Design Authority of the Capella open source modeling solution. For the last ten years, he has led the development of Capella and has been an active contributor to the Arcadia model-based method for systems, hardware and software architectural design. In Thales, he is animating a wide community of modeling experts from all domains and countries to investigate low-maturity modeling topics, capture end-user needs, and orient method and workbench roadmaps.
MBSE with Arcadia method step-by-step System Analysis.pdfHelder Castro
The Operational Analysis described is the previous article, MBSE with Arcadia method step-by-step: Operational Analysis [1], involves defining and creating a domain model, independently of the future system to be realized. The principle is to create a level of abstraction from the system under study in order to focus on the needs of the different stakeholders.
The System Analysis level, on the other hand, is where the System-of-Interest (SoI) to be defined emerges. The following questions for the system definition needs to be answered:
• What must the system do?
• What are the external interfaces to the system?
In order to answer the first question, the expected behaviour is modelled as Functions.
MBSE with Arcadia method step-by-step System Analysis.pdf
Similar to Capella Days 2021 | Introduction to CAPELLA/ARCADIA and NASA Systems Engineering Handbook: Modeling overview with the HUBBLE Space Telescope
DLP: a Web-based Facility for Exploration and Basic Modification of Ontologie...Luca Mazzola
this is the presentation given into iiWAS2017conference for the paper:
Mazzola L., and Kapahnke P. (2017). DLP: a Web-based Facility for Exploration and Basic Modification of Ontologies by Domain Experts. In Proceedings of The 19th Int. Conference on Information Integration and Web-based Applications & Services, Salzburg, Austria, December 4–6, 2017 (iiWAS ’17), 5 pages. DOI: https://doi.org/10.1145/3151759.3151816
Crossplane allows users to extend their Kubernetes clusters using CRDs. The CRDs map any infrastructure or managed service, ensuring that the creation process for the users is as simple as the Kubernetes resources creation. Using a collection of YAML manifests, the development teams can assemble the needed cloud services for their applications removing this duty from the operation teams: this is “shift left” at its best. All this powerfulness comes with a cost in terms of security, governance, cognitive load and maintenance. In this talk we’ll discuss strategies and techniques to better map the complexity of this infrastructure.
Tackling Consistency-related Design Challenges of Distributed Data-Intensive ...Susanne Braun
In the presentation we share the results of an action research study. In this study we set off to investigate how consistency-related design challenges of distributed, data-intensive systems can be tackled.
DoDAF architecture example using a functional “thread” of Search and Rescue (SAR) concept
Provides an architectural example of DoDAF 2.0 in Action using a real world construct
Shows how architectural analysis can answer SAR Program Management questions.
1
Lesson 5.3
UML Deployment Diagrams
Lesson 5.2
Distributed Systems Architecture (DSA) for Deployment
Lesson 5.1
Basic Vocabulary of the Deployment View
1
2
3
4
5
Learning Module Table of Contents
Reference
Rozanski, N. and Woods, E. (2012) Software systems architecture (2nd Edition). Chapters 21 and 20.
Lesson 5.4 (time permitting)
Using Deployment Diagrams to Illustrate the Development View
1
2
Lesson 5.3
UML Deployment Diagrams
Lesson 5.2
Distributed Systems Architecture (DSA) for Deployment
Lesson 5.1
Basic Vocabulary of the Deployment View
1
2
3
4
5
Let’s get started with the first lesson of the module
Reference
Rozanski, N. and Woods, E. (2012) Software systems architecture (2nd Edition). Chapters 21 and 20.
Lesson 5.4
Using Deployment Diagrams to Illustrate the Development View
2
System Architecture Views (using the ISO/IEC 42010 standard)
3
REF: ISO Software Architecture Standard as described by Rozanski and Woods
CONTEXT Views
FUNCTIONAL View
DATA View
TIMING View
DEVELOPMENT View
DELPOYMENT View
(we are here)
OPERATIONAL View
Not a new idea in systems design
Other architectural standards
Kruchten’s 4 + 1 architecture (IBM)
IEEE Standard 1471 that is the basis for your textbook
Zachman’s Framework for Information Systems Architecture
3
4
The Deployment View focuses on how hardware and software elements of your new system will be distributed or assigned across a network.
The deployment view includes both technical and non–technical
sub-views.
The deployment view shows how various implementation components will be distributed to specific ”nodes” on the network.
The deployment view shows the communication lines (wired and wireless) between processing nodes
What is the Deployment View of a System’s Design?
Overview of the Deployment ViewCharacteristics ExplanationDefinitionDescribes the processing and storage environment of your IT system/solution, and the potential points of failure for which you may need a service disruption and business continuity plan.ConcernsAll hardware, software, and storage nodes required for your system
Commercial (third party components) that must be purchased
Software components that must be built and where each will be executed (run-time environment)
Data storage components, capacity, and recovery
Network requirements and capacities
Points of failureArchitectural DescriptionsRun-time models
Network models
Technology dependency ModelsPossible ProblemsUnclear or inaccurate dependencies between required nodes in the network
Unproven technology choices, or obsolete technology choices
Missing or poorly developed service level agreements with user community
Lack of necessary technical knowledge or expertise
Deployment becoming an after thought – compromising design and construction already completed
Poor or no capacity planning analysis
No service disruption business continuity plan, or disaster recovery plan and environment
5
REF: Adapted from Rozanski and Woods (2012)
...
#SiriusCon 2015: Talk by Christophe Boudjennah "Experimenting the Open Source...Obeo
Capella is a Model Based Systems Engineering (MBSE) solution using Sirius for its diagrams rendering.
It has been initially developed in house by Thales and has been open sourced (in Polarsys) within the context of the CLARITY project. This was actually the very first step of CLARITY, which aims at developing and structuring an international ecosystem around Capella. The CLARITY project now investigates customization capabilities for Capella and aims at complementing the ecosystem with a community that brings together major actors of the entire engineering value chain (industrials, integrators, technology providers and consultants, academia) for open innovation in MBSE within Capella.
In this context, Areva and Airbus Defence & Space already made lots of experimentations and are helping the ecosystem to mature up by providing feedbacks to the community. In this talk, you will get an overview of what those 2 Industrial companies have realized so far.
[About Christophe Boudjennah:
Christophe is a senior system/software architect and project manager. His experience leads him to work for various domains such as defense, IT, or the Automotive industry. Most of his career has been focused on Systems Engineering for complex embedded systems, whether it is from the "methods and tools provider" point of view or from the operational one. He is now working for Obeo, and is dealing with various open source and systems engineering related topics. One of his current main responsibilities is to be the project coordinator of Clarity, a large R&D project whose purpose is to open-source Capella (an industrial workbench for system engineering).]
[Sirius Day Eindhoven 2018] ASML's MDE Going SiriusObeo
Talk done by Wilbert Alberts (ASML) at Sirius Day Eindhoven:
ASML is the world's leading provider of lithography systems for the semiconductor industry. Such systems are controlled by more than 20 million lines of code. To improve the efficiency and quality of its software development process, ASML is using, amongst others, model-driven-engineering and associated tools and techniques.
Recently, subsystems are being developed according to an architecture pattern that separates Data, Control and Algorithms (DCA). To support this pattern, the ASML software architecture group is working towards a SW development environment (ASOME). This environment consists of a set of modeling languages, associated editors that allow specification of (sub)systems according to this DCA pattern. Furthermore, it contains model-to-model transformations to (COTS) analysis tools (e.g. model checkers) and model-to-text transformation to generate (parts of) the implementation.
In this presentation, I will briefly introduce ASML and the kind of (software) systems that we develop. Some aspects of the DCA architectural pattern, the languages that we are developing and the associated Sirius based editors, will be presented. For the Data part, a DSL and editor have been developed allowing the definition of various kinds of datatypes from which various kinds of repositories can be generated supporting clone based data or reference based data, modifiable and read-only entities etc. In order support the Control aspect; a language and editor have been defined that allow specification of interfaces and their realization based on state machines. A system editor allows decomposition of a system into subsystems while allowing delegation of incoming requests to internal parts. The editors are mostly Sirius based graphical editors, where the created models are persisted textually using XText.
The presentation will focus on sharing some of our experiences with both the development and deployment of products based on Sirius technology. Building the ASOME environment imposes many challenges and I would like to conclude with some that specifically target the development of the front ends of this environment.
WiSANCloud: a set of UML-based specifications for the integration of Wireless...Priscill Orue Esquivel
Giving the current trend to combine the advantages of Wireless Sensor and Actor Networks (WSANs) with the Cloud Computing technology, this work proposes a set of specifications, based on the Unified Modeling Language - UML, in order to provide the general framework for the design of the integration of said components. One of the keys of the integration is the architecture of the WSAN, due to its structural relationship with the Cloud in the definition of the combination. Regarding the standard applied in the integration, UML and its subset, Systems Modeling Language - SysML , are proposed by the Object Management Group - OMG to deal with cloud applications; so, this indicates the starting point of the process of the design of specifications for WSAN-Cloud Integration. Based on the current state of UML tools for analysis and design, there are several aspects to take into account in order to define the integration process.
Nowadays software systems are essential to the environment of most organizations, and their maintenance is a key point to support business dynamics. Thus, reverse engineering legacy systems for knowledge reuse has become a major concern in software industry. This article, based on a survey about reverse engineering tools, discusses a set of functional and nonfunctional requirements for an effective tool for reverse engineering, and observes that current tools only partly support these requirements. In addition, we define new requirements, based on our group’s experience and industry feedback, and present the architecture and implementation of LIFT: a Legacy InFormation retrieval Tool, developed based on these demands. Furthermore, we discuss the compliance of LIFT with the defined requirements. Finally, we applied the LIFT in a reverse engineering project of a 210KLOC NATURAL/ADABAS system of a financial institution and analyzed its effectiveness and scalability, comparing data with previous similar projects performed by the same institution.
Similar to Capella Days 2021 | Introduction to CAPELLA/ARCADIA and NASA Systems Engineering Handbook: Modeling overview with the HUBBLE Space Telescope (20)
INCOSE IS 2023 | You deserve more than the best in class MBSE toolObeo
As Model-Based Systems Engineering (MBSE) becomes more widely adopted in industry, projects involving collaborating teams require efficient collaboration and coordination. This talk will explore the challenges of industrializing MBSE projects and present solutions using the Capella modeling tool. We will discuss how the Cloud for Capella, Publication for Capella and Team for Capella extensions can support effective collaboration and communication among stakeholders working on MBSE projects. These extensions enable all project participants to remain aligned and up-to-date with project progress, ensuring that the project runs smoothly and efficiently. By the end of the talk, attendees will have a better understanding of how to industrialize MBSE projects and the role Capella can play in supporting these efforts.
Biography: Stephane Lacrampe
Stephane Lacrampe co-founded Obeo in 2005 in France and acted as the company's CEO until 2018. Obeo is an independent software vendor with a global reach, leading in open-source modeling software for system and software engineers, enterprise architects, and domain modeling experts. He is now the director of Obeo Canada. He is a very active member of the Capella community and is in charge of developing the Capella ecosystem in North and South America. He is a regular MBSE speaker who speaks at conferences in America and beyond. Stephane LACRAMPE is co-chair of the INCOSE Systems Engineering Tools Database Working Group and the INCOSE Canada chapter webmaster.
CapellaDays2022 | COMAC - PGM | How We Use Capella for Collaborative Design i...Obeo
COMAC is one of the leading suppliers of civil aircraft in the world. We will introduce how we use Capella in COMAC for collaborative design, including how to collaborate between overall design group and ATA design groups, and how to collaborate between different ATA design groups. We have done a series of extension development based on the System to Subsystem Transition add-on, to support the business process. These extensions include the integration from subsystem models to system model, the refinement of functional exchanges, the synchronization of newly added functional exchanges, and so on.
In the last three years CILAS has been tailoring and applying the Arcadia methodology to several international projects related to complex optronics products development. Even though the implementation is not yet thorough and systemic within the company, CILAS is already reaping benefits of this approach on several fronts (e.g. communication, identification of optimization opportunities, knowledge capitalization etc). All in all Arcadia is a powerful methodology that significantly helps CILAS reinforcing its core skills and meeting its objectives in very challenging sectors.
CapellaDays2022 | SIEMENS | Expand MBSE into Model-based Production Engineeri...Obeo
Mind Game: You want to build a LEGO Mindstorms Factory for Toy Cars and you are Head of Factory Planning. You identify that your manufacturing planning team and your product design team don’t collaborate with each other, because they work in silos and speak different languages. Their progress is too slow and the results are not synchronized.
Imagine: You succeed in merging your experts into one interdisciplinary team where everyone is collaboratively working together – already in the early stages of the engineering cycle. And imagine they start to speak the same language. Doubtless, you would speed up your engineering process. Furthermore, you would also reach a synchronized global solution for your manufacturing system and to be produced toy cars, building bridges inside your organization.
But how? This has been introduced by Dr.-Ing. C. Sinnwell in February 2020 in her PhD-thesis. There, she published the latest version of a methodology referred to as “MBPE – Model-Based Production Engineering”. The MBPE-methodology is a new approach for the conceptual design of manufacturing systems based on early product information supported by MBSE using UML.
The presentation will spotlight the MBPE-methodology, explaining how to use MBSE in the context of interdisciplinary factory and manufacturing planning. Also, it will be shown, how the methodology could be adapted to be realized with Eclipse Capella instead of any UML-modeling tool, illustrated by an example on how to conceptualize and model a LEGO Mindstorms production line for Toy Cars.
Gestion applicative des données, un REX du Ministère de l'Éducation NationaleObeo
Gestion applicative des données, un REX du Ministère de l'Éducation Nationale
Slides du webinaire IS Designer du Jeudi 10 Novembre 2022.
Une approche de modélisation et de
génération automatique avec IS Designer.
Le pôle de Versailles du Ministère de l'Éducation Nationale a utilisé l'outil open-source Information System Designer sur plusieurs projets à portée nationale pour modéliser les bases de données et les couches applicatives d'accès aux données (DAO).
Ce retour d'expérience sera présenté en détail lors de ce webinaire :
✔ la démarche mise en place,
✔ comment l'outil a été utilisé,
✔ les bénéfices constatés.
"Pour la dizaine de développeurs impliqués sur ces projets, la production automatique des Tests Unitaires a aussi permis de s'approprier plus facilement le socle technique, grâce à une approche par l'exemple, mais également d’avoir une assurance de non régression sur les fonctionnalités produites."
From Model-based to Model and Simulation-based Systems ArchitecturesObeo
Achieving quality engineering through descriptive and analytical models
Systems architecture design is a key activity that affect the
overall systems engineering cost. It is hence fundamental
to ensure that the system architecture reaches a proper quality.
In this paper, we leverage on MBSE approaches and complement them
with simulation techniques, as a prom-ising way to improve the quality of the system architecture definition, and to come up with inno-vative solutions while securing the systems engineering process.
Sirius Web Advanced : Customize and Extend the PlatformObeo
Beyond the no code approach, Sirius Web is an open and extensible platform that you can customize in order to support your needs. Discover how to develop specific features in Sirius Web and integrate your modeler with other web applications.
Stéphane Bégaudeau, Obeo
Stéphane Bégaudeau graduated from the Nantes University of Sciences and Technology and is currently working as an Eclipse Modeling consultant at Obeo in France.
Sirius Web 101 : Create a Modeler With No CodeObeo
Learn step-by-step how to create a domain model and define your first diagrams with Sirius Web, without any line of code. It will allow you to easily create custom graphical representations that automatically represent your data in the web.
Frédéric Madiot, Obeo
Frédéric Madiot is Marketing Manager at Obeo. He has more than 25 years of experience in developing model-driven tools to industrialize the development of new applications and the modernization of existing systems.
What's new in Sirius Web ? Discover the current version and what will come in the next releases.
Mélanie Bats, Obeo
Mélanie Bats works as CTO at Obeo. In my daily work, I am mainly focused on managing the R&D team, creating products based on our own open source technologies. I am used to work in the development of modeling tools with Sirius like UML Designer. I am committer for the EEF and the Sirius projects. I am also involved in the Eclipse community as being the Eclipse Planning Council chair. I am also a free software activist who has organized and participated in free software events in the Toulouse area.
Visualizing, Analyzing and Optimizing Automotive Architecture Models using Si...Obeo
Visualizing, Analyzing and Optimizing Automotive Architecture Models using Sirius
Advancing digitalization affects almost all aspects of our modern world. A prominent example is that of modern automobiles. From primarily mechanical machines, cars have evolved into driving complex cyber-physical systems over the last decades. Optimizing such systems consisting of vast networks of sensors, actuators, control units, and communication systems is a huge challenge for today's automotive industry and requires standardized and integrated toolchains fit for purpose. Together with a prestigious automotive industry partner, the Technical University of Ilmenau developed an application together with an integrated toolchain for evaluating and optimizing automotive architecture models. This application is based on the Obeo Sirius project as well as the Eclipse Modeling Framework. Based on Sirius, we created a model editor which is used for visualizing, editing, but also analyzing and optimizing automotive models across the boundaries of different architectural layers.
Maximilian Hammer, Technical University of Ilmenau
Maximilian Hammer is a Research Assistant at Technical University of Ilmenau
The openCAESAR project provides an EMF-based implementation of the Ontological Modeling Language (OML), which simplifies the use of semantic web ontologies for modeling and analysis. An OML model can be either be a vocabulary model that defines the terms and rules in a business domain with precise syntax and logical semantics, or can be a description model that uses that vocabulary to describe knowledge. OML has successfully been used at the Jet Propulsion Laboratory (JPL) in the context of Model Based Systems Engineering (MBSE), specifically to define the JPL systems engineering methodology in a highly modular and extensible way. Sirius has been used to define the authoring viewpoints that support such methodology. In this talk, we present how OML and Sirius can be used together, through the OML Rosetta Workbench, to streamline the development of an ontology-based modeling methodology and the authoring tools for it. The ideas will be demonstrated on a small example.
Maged Elaasar, NASA - Jet Propulsion Laboratory
Maged Elaasar is a Senior Software Systems Architect at NASA’s Jet Propulsion Laboratory (JPL) at the California Institute of Technology (Caltech). He technically leads a JPL-wide strategic R&D program called Integrated Model Centric Engineering (IMCE). Prior to that, Maged was a Senior Software Engineer at IBM, where he led the R&D of various software and systems modeling technologies. Maged is also the founder of Modelware Solutions, a company based in California that provides development, consulting, and training services in the area of model based engineering (MBE)
Development of DSL for Context-Aware Mobile ApplicationsObeo
In recent years, technological growth has been exponential in relation to mobile devices (such as embedded sensors as GPS or accelerometer) that has allowed developing context-aware mobile applications for the market. This growth generates a new challenge about how to support the creation of this kind of application in order to adapt them to the user’s current demand. There are at present several approaches that could be used to create context-aware mobile applications, but these approaches are not designed to support variability in the kind of generated applications.Our aim is to propose a building tool that allows generating a wide variety of applications. Our tool has been designed from scratch considering a taxonomy of variability concepts (relevance, combination, precision and accuracy’s margins, configuration type, and execution type) which help to identify the potential variability points to obtain more flexible building approaches.
Estevan Gomez, Universidad de las Fuerzas Armadas - ESPE
Estevan R. Gómez-Torres, PhD (c) Universidad Nacional de la Plata Argentina, Master in Systems Management and Systems Engineering from Universidad de las Fuerzas Armadas 'ESPE' in Quito-Ecuador. His field of work and research include lines such as: Big Data, Internet of Things, Project Management, Development of mobile applications in contexts, Artificial Intelligence, Data Analytics, Machine Learning, Smart Cities.
SimfiaNeo - Workbench for Safety Analysis powered by SiriusObeo
Safety Analysts produce fault trees to perform Reliability, Availability, Maintainability and Safety (RAMS) studies of systems (vehicles, plants, electrical networks, etc.). Because systems are more and more complex, creating, reviewing and maintaining fault trees are tedious tasks. Model-Based Safety Analysis (MBSA) allows to add dysfunctional behaviors and failure propagation on top of an existing system design coming from a MBSE tool. SimfiaNeo is a MBSA software based on Eclipse RCP, Eclipse Sirius and other Eclipse modeling tools. SimfiaNeo abstracts the AltaRica language to provide an user friendly graphical modeler to design, validate and compute RAMS studies.
In this session, we will show SimfiaNeo in action. How we customized Eclipse UI to take advantage of the full potential of Sirius while keeping it as simple as possible for adoption by non Eclipse users.
How we reused compoments coming from the previous MBSA tool (SIMFIA, which was not based on Eclipse). How we manage large number of data stored outside the EMF model but linked to it.
Yann Mortier, APSYS - Airbus Group
Yann Mortier is currently working as lead developer of SimfiaNeo in Apsys.
Xavier de Bossoreille, APSYS - Airbus Group
Xavier de Bossoreille is currently working as MBSA specialist and product owner of SimfiaNeo in Apsys.
Get into MBSE-MBSA process with a dedicated toolchainObeo
E/E systems and cyber-physical systems are carrying out more and more advanced and safety critical features in many domains such as transport, energy, industry, farming, medical, etc. Therefore, during last few years, to manage the development of those complex systems, companies have moved from a document-based approach to a model-based approach associated with very specific tools.
However, system and safety engineering, and some other related engineering domains like cybersecurity for instance, are still too often conducted independently, whereas safety and system attributes are largely interdependent. There is a need to foster greater collaboration between these disciplines to avoid errors and also to maintain time-to-market.
That's why since several years, ALL4TEC, with its safety analysis tool Safety Architect, has been working to connect its tool with system solutions to couple MBSE and MBSA. The goal is to better ensure consistency between system design and safety analysis.
During this talk, ALL4TEC will present its Capella add-on that allows annotation of Capella models with basic safety information, smart export and dynamic connection to share data between Capella and Safety Architect to support MBSE-MBSA.
2022, here we are! It's the perfect time to take a look back at 2021 and make plans for 2022!
In this webinar, Juan Navas presents the major events of 2021, the roadmap for 2022, and the main features included in the latest version of Capella, but also reviews the ecosystem's innovations and the evolutions of the add-ons
Juan Navas is MBSE Expert in Thales Corporate Engineering. He leads the team that accompanies managers and architects implement MBSE practices on operational projects to improve their engineering performance. He is a System Architect with +10 years’ experience, he holds a PhD in Computer Science, an MSc in control and computer science, and Electronics and Electrical Engineering Degrees.
Générez automatiquement vos diagrammes d'architecture | Webinaire Obeo SmartEAObeo
Comment assurer une certaine cohérence des données dans un référentiel d'architecture, et produire à grande échelle des représentations graphiques pertinentes ?
Obeo SmartEA 6.3 apporte deux nouvelles fonctionnalités permettant de répondre à ce besoin :
- des stéréotypes pour cadrer les propriétés dynamiques ArchiMate,
- des templates pour générer des diagrammes spécifiques.
Découvrez ces nouveautés et leur mise en œuvre sur un cas concret : la création d'un catalogue de services applicatifs.
Capella (once again) in space, meeting nanosatellitesObeo
Previously, Capella models (slightly extended by new features dedicated to system test specification) was used by the French Space Agency (CNES) to demonstrate that the current document-centric process could be improved. Applied on the “Space Variable Objects Monitor (SVOM)” operational use case, it helped the CNES in the definition and the validation of its future space system dedicated to the gamma ray detection and study. Proof being made, Kineis, created by the CNES and the CLS, reiterates the experience and continues to make it a strategic technology for science. Its current challenge is to add 25 state-of-the-art nano-satellites to the existing system to enhance IoT capabilities and address new markets. In line with the CNES Capella experience, Kinéis decided to build its “System Test” process on Capella. The extendibility and the flexibility of Capella nevertheless allowed them to carry on the previously initiated toolchain in order to cover the full process and support more use cases.
Jonathan Lasalle (Artal / Magellium)
- In charge of MBSE-related activities at Artal / Magellium
- Architect of the Citrus framework dedicated to model-based test mean engineering
Identifier et suivre les applications à risque pour des processus métier | We...Obeo
Quelles sont les applications du SI dont l'obsolescence technique menace la bonne exécution de certains processus métier?
Répondre à cette question, et gérer les situations à risque, nécessite de pouvoir s'appuyer sur un référentiel de données fiables et exploitables qui décrivent le SI et ses liens avec le métier.
Après un premier webinaire il y a quelques mois, consacré à la collecte des données, Romain Guider vous propose un deuxième webinaire pour discuter de l'exploitation de ces données, dans le cadre d'une gestion de l'obsolescence applicative.
Quality defects in TMT Bars, Possible causes and Potential Solutions.PrashantGoswami42
Maintaining high-quality standards in the production of TMT bars is crucial for ensuring structural integrity in construction. Addressing common defects through careful monitoring, standardized processes, and advanced technology can significantly improve the quality of TMT bars. Continuous training and adherence to quality control measures will also play a pivotal role in minimizing these defects.
TECHNICAL TRAINING MANUAL GENERAL FAMILIARIZATION COURSEDuvanRamosGarzon1
AIRCRAFT GENERAL
The Single Aisle is the most advanced family aircraft in service today, with fly-by-wire flight controls.
The A318, A319, A320 and A321 are twin-engine subsonic medium range aircraft.
The family offers a choice of engines
Forklift Classes Overview by Intella PartsIntella Parts
Discover the different forklift classes and their specific applications. Learn how to choose the right forklift for your needs to ensure safety, efficiency, and compliance in your operations.
For more technical information, visit our website https://intellaparts.com
Water scarcity is the lack of fresh water resources to meet the standard water demand. There are two type of water scarcity. One is physical. The other is economic water scarcity.
Cosmetic shop management system project report.pdfKamal Acharya
Buying new cosmetic products is difficult. It can even be scary for those who have sensitive skin and are prone to skin trouble. The information needed to alleviate this problem is on the back of each product, but it's thought to interpret those ingredient lists unless you have a background in chemistry.
Instead of buying and hoping for the best, we can use data science to help us predict which products may be good fits for us. It includes various function programs to do the above mentioned tasks.
Data file handling has been effectively used in the program.
The automated cosmetic shop management system should deal with the automation of general workflow and administration process of the shop. The main processes of the system focus on customer's request where the system is able to search the most appropriate products and deliver it to the customers. It should help the employees to quickly identify the list of cosmetic product that have reached the minimum quantity and also keep a track of expired date for each cosmetic product. It should help the employees to find the rack number in which the product is placed.It is also Faster and more efficient way.
Saudi Arabia stands as a titan in the global energy landscape, renowned for its abundant oil and gas resources. It's the largest exporter of petroleum and holds some of the world's most significant reserves. Let's delve into the top 10 oil and gas projects shaping Saudi Arabia's energy future in 2024.
Vaccine management system project report documentation..pdfKamal Acharya
The Division of Vaccine and Immunization is facing increasing difficulty monitoring vaccines and other commodities distribution once they have been distributed from the national stores. With the introduction of new vaccines, more challenges have been anticipated with this additions posing serious threat to the already over strained vaccine supply chain system in Kenya.
Event Management System Vb Net Project Report.pdfKamal Acharya
In present era, the scopes of information technology growing with a very fast .We do not see any are untouched from this industry. The scope of information technology has become wider includes: Business and industry. Household Business, Communication, Education, Entertainment, Science, Medicine, Engineering, Distance Learning, Weather Forecasting. Carrier Searching and so on.
My project named “Event Management System” is software that store and maintained all events coordinated in college. It also helpful to print related reports. My project will help to record the events coordinated by faculties with their Name, Event subject, date & details in an efficient & effective ways.
In my system we have to make a system by which a user can record all events coordinated by a particular faculty. In our proposed system some more featured are added which differs it from the existing system such as security.
Democratizing Fuzzing at Scale by Abhishek Aryaabh.arya
Presented at NUS: Fuzzing and Software Security Summer School 2024
This keynote talks about the democratization of fuzzing at scale, highlighting the collaboration between open source communities, academia, and industry to advance the field of fuzzing. It delves into the history of fuzzing, the development of scalable fuzzing platforms, and the empowerment of community-driven research. The talk will further discuss recent advancements leveraging AI/ML and offer insights into the future evolution of the fuzzing landscape.
Capella Days 2021 | Introduction to CAPELLA/ARCADIA and NASA Systems Engineering Handbook: Modeling overview with the HUBBLE Space Telescope
1. CAPELLA DAYS 2021 WARM-UP session
Introduction to CAPELLA/ARCADIA and
NASA Systems Engineering handbook:
Modeling overview with the HUBBLE
Space Telescope
DROUIN Remy
2. ➢ Avionic systems engineer in the French Air Force
➢ Team Leader in automotive industry designing connected solutions
➢ Program Manager in elevator industry designing connected solutions
➢ Head of system department in defense industry designing High Energy Laser Systems
➢ Lecturer for French universities introducing Systems Engineering and Model-Based Systems Engineering
Speaker introduction Speaker: DROUIN Remy
“The NASA System Engineering (SE) handbook aims to provide general guidance and information on systems engineering, as it should be applied throughout NASA. The handbook introduces 3
common technical processes. One of these, is the System Design Process, describing the stakeholders expectations, requirements definition, logical decomposition and design solution definition.
The 4 activities can be supported by a Model-Based Systems Engineering (MBSE) approach. To do so, an appropriate method and tool is necessary as the one provided by the ARChitecture Analysis
& Design Integrated Approach. ARCADIA, with its modeler CAPELLA, is a MBSE solution supporting system modeling activities. Based on 4 architectural layers, which are Operational Analysis,
System Analysis, Logical and Physical Architecture, it is a structured architecture engineering method for defining and validating multi-domain systems. This talk will present an educational
overview of the ARCADIA methodology and System Design Process from the NASA SE, by introducing MBSE artefacts for space system.
The HUBBLE Space Telescope (HST) is a Cassegrain reflector telescope. Orbiting above the earth, HST elaborates a clear view of the universe free from the blurring and absorbing effects of the
atmosphere. In order to illustrate the journey throughout CAPELLA, the HST will be introduced, as example, based on public information available.”
Capella Days November 15, 2021
3. ➢NASA Systems Engineering Handbook
➢MBSE
➢CAPELLA/ARCADIA
➢Modeling overview with HUBBLE Space Telescope
TALK Life Cycle Speaker: DROUIN Remy
Capella Days November 15, 2021
4. « All models are wrong, but some are useful »
George E.P.Box (British statistician)
Speaker: DROUIN Remy
Capella Days November 15, 2021
6. NASA Systems Engineering Handbook Speaker: DROUIN Remy
NASA Systems Engineering Handbook is intended to provide
general guidance and information on systems engineering that
will be useful to the NASA community. It provides a generic
description of Systems Engineering (SE) as it should be applied
throughout NASA. This handbook describes systems
engineering best practices that should be incorporated in the
development and implementation of large and small NASA
programs and projects.
NASA Handbook MBSE CAPELLA/ARCADIA HST
Expanded Guidance for NASA Systems Engineering
Vol1
Vol2
Capella Days November 15, 2021
7. NASA SE Handbook – Systems Engineering Speaker: DROUIN Remy
NASA Handbook MBSE CAPELLA/ARCADIA HST
The systems engineer usually plays the key role
in leading:
➢ the development of the concept of operations
and resulting system architecture
➢ defining boundaries
➢ defining and allocating requirements
➢ evaluating design tradeoffs
➢ balancing technical risk between systems
“Systems engineering” is defined as a methodical, multi-disciplinary approach for the design, realization, technical
management, operations, and retirement of a system.
➢ defining and assessing interfaces, providing oversight of verification and validation activities
Capella Days November 15, 2021
8. There are 3 sets of common technical processes: system design, product realization, and technical management.
NASA SE Handbook - Processes Speaker: DROUIN Remy
NASA Handbook MBSE CAPELLA/ARCADIA HST
Capella Days November 15, 2021
9. The four system design processes are used to define and baseline stakeholder expectations, generate and baseline
technical requirements, decompose the requirements into logical and behavioral models, and convert the technical
requirements into a design solution that will satisfy the baselined stakeholder expectations.
NASA SE Handbook – System Design Process Speaker: DROUIN Remy
NASA Handbook MBSE CAPELLA/ARCADIA HST
Capella Days November 15, 2021
10. NASA SE Handbook – Requirements definition process Speaker: DROUIN Remy
NASA Handbook MBSE CAPELLA/ARCADIA HST
The main purpose of this process is to identify who the stakeholders are and how they intend to use the product.
Stakeholder expectations
Capella Days November 15, 2021
11. NASA SE Handbook – Requirements definition process Speaker: DROUIN Remy
NASA Handbook MBSE CAPELLA/ARCADIA HST
The Requirements Definition process transforms the stakeholder expectations into a definition of the problem.
Requirements definition
Capella Days November 15, 2021
12. NASA SE Handbook – Technical solution definition process Speaker: DROUIN Remy
NASA Handbook MBSE CAPELLA/ARCADIA HST
Logical decomposition utilizes functional analysis to create a system architecture and to decompose top-level
requirements and allocate them down to the lowest desired levels.
Logical decomposition
Capella Days November 15, 2021
13. NASA SE Handbook – Technical solution definition process Speaker: DROUIN Remy
NASA Handbook MBSE CAPELLA/ARCADIA HST
Design solution definition
The Design Solution Definition process is used to translate the requirements derived from the stakeholder
expectations and the outputs of the Logical Decomposition process into a design solution.
Capella Days November 15, 2021
14. NASA SE Handbook – Functional Analysis Speaker: DROUIN Remy
NASA Handbook MBSE CAPELLA/ARCADIA HST
➢ Functional analysis can be performed by Functional
Flow Block Diagrams (FFBDs). They are functionally
oriented and not solution oriented
➢ It is made of functional block representing an action to
be accomplished
➢ The functional architecture is developed using a
decomposition and interactions between each functions
(functional flows)
➢ Functional analysis looks across all life cycle processes
Capella Days November 15, 2021
16. Speaker: DROUIN Remy
Model-based systems engineering(MBSE) is a systems engineering methodology that focuses on creating and exploiting
domain models as the primary means of information exchange between engineers, rather than on document-based
information exchange. MBSE is a formalized application of modeling to support system requirements, design, analysis,
verification and validation activities beginning in the conceptual design phase and continuing throughout development and
later life cycle phases.
MBSE Introduction
Document centric
NASA Handbook MBSE CAPELLA/ARCADIA HST
System
engineer
Test
engineer
Integration
engineer
Subsystem
engineer
System
engineer
Test
engineer
Integration
engineer
Subsystem
engineer
Requirements
Behaviours
Interfaces
Etc…
From document-based
to model-based
Model centric
Capella Days November 15, 2021
17. Speaker: DROUIN Remy
MBSE - Modeling
NASA Handbook MBSE CAPELLA/ARCADIA HST
Modeling objectives (sample)
Characterize an existing system
Specify and design a new or modified system
Evaluate a system
Train users on how to operate or maintain a system
A model consists of elements that represent requirements , design element, and their relationships. SYSML is a graphical
modeling language that supports modeling activities.
Capella Days November 15, 2021
18. Speaker: DROUIN Remy
MBSE across SE engine (NASA SE)
NASA Handbook MBSE CAPELLA/ARCADIA HST
System Design Processes MBSE Contributions (NASA)
Stakeholders expectations
definition
Need, goals and objectives are kept within the model and form the top tier of eventual requirements
flowdown
Technical requirements Requirements are kept within the models
Logical decomposition Requirements can be categorized into functional, behavioral, performance etc… These can be used to
develop functional block and behavior diagrams
Design Solution Definition Allows integration of information and designs from different engineering domains supporting the
single source of truth
1 2
3
4
1
2
3
4
Capella Days November 15, 2021
19. Speaker: DROUIN Remy
MBSE Benefits
NASA Handbook MBSE CAPELLA/ARCADIA HST
NASA MBSE benefits (sample)
Greater consistency of all products because any single piece of design information can be
expressed authoritatively in a single place that can later be referred to by others for
decisions, derivations, or formation of artifacts
Better visibility into the salient characteristics of a system because multiple views can be
created that succinctly address specific stakeholder concerns
Model-based artifacts can be generated automatically, lowering the effort to keep them up
to date with the result that artifacts can always match the best available information
Navigation, traceability, and interrogation of information are facilitated in the model-based
approach
Can be less investment lost in erroneous design because sometimes the model reveals a
flaw as soon as it is created, enabling correction before downstream work is done, work
that would be invalid if the upstream mistake were not corrected immediately
Model-based systems engineering does not affect process but will enable the opportunity for overall better quality, lower cost,
and lower risk.
Overall MBSE benefits (sample):
Enhance communication
Reduce development risk
Encourage collaboration
Manage complexity
Automatic document generation
Reuse of existing models in several projects
Better requirements traceability
More stakeholder involvement
Digitalization
Single source of truth
Capella Days November 15, 2021
21. ARCADIA/CAPELLA - Introduction Speaker: DROUIN Remy
Architecture Analysis & Design Integrated Approach (ARCADIA) is a structured architecture engineering method for defining and
validating multi-domain systems, based on architecture-centric and model-driven engineering activities. ARCADIA is a method
based on functional analysis and focuses on developing the system by starting from needs analysis and solution development up
to integrated verification and validation.
➢ Ensure engineering-wide collaboration by sharing the same
reference architecture
➢ Master the complexity of systems and architectures
➢ Define the best optimal architectures through trade-off
analysis
➢ Master different engineering levels and traceability with
automated transition and information refinement
NASA Handbook MBSE CAPELLA/ARCADIA HST
Capella Days November 15, 2021
22. ARCADIA/CAPELLA - Introduction Speaker: DROUIN Remy
NASA Handbook MBSE CAPELLA/ARCADIA HST
Method
The Arcadia method enforces an
approach structured on different
engineering perspectives
establishing a clear separation
between system context and need
modeling (operational need analysis
and system need analysis) and
solution modeling (logical and
physical architectures).
Language
The Arcadia concepts are mostly
similar to the UML/SysML standard
and the NATO Architecture
Framework (NAF) standard. 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.
Diagrams
Arcadia method is supported by
various kinds of diagrams largely
inspired by UML and SysML:
➢ Architecture diagrams;
➢ Dataflows diagrams;
➢ Functional chains diagrams;
➢ Sequence diagrams;
➢ Tree diagrams;
➢ Mode and States diagrams;
➢ Classes and Interfaces diagrams.
Designing complex and critical systems, and more generally architectures that are subject to multiple functional
and non-functional constraints, is an activity which requires a level of rigor that can only be provided by formalized
and tooled modeling approaches like the ones based on Arcadia/Capella and SysML tools.
Capella Days November 15, 2021
23. ARCADIA/CAPELLA - Diagram description Speaker: DROUIN Remy
NASA Handbook MBSE CAPELLA/ARCADIA HST
Diagram Description
Breakdown diagram Stakeholders/Functions/Components
decomposition through graphical tree
Capability diagram Equivalent to a use-case diagram, used to
organize the functional analysis
Dataflow diagram Provide informations exchanged between
functions
Architecture diagram Described the assembly of components or
functions and interfaces
Scenario Provdes dynamic behavior between functions
Mode&State Provide the working type of function or actor or
system.
Class diagram Often, data-class diagram compress of exchange
items or data parameters utilized in a system
Capella Days November 15, 2021
24. ARCADIA/CAPELLA – Functional analysis Speaker: DROUIN Rémy
NASA Handbook MBSE CAPELLA/ARCADIA HST
Define the system
Define the functions
Define the tree diagram
Define the functional dependencies
Capella Days November 15, 2021
25. ARCADIA/CAPELLA - Operational Analysis Speaker: DROUIN Remy
Define Stakeholder needs and environment
• Capture and consolidate operational needs from stakeholders
• Define what the users have to accomplish
• Identify entity, actors, roles, activities and concepts
NASA Handbook MBSE CAPELLA/ARCADIA HST
[OEBD] Operational Entity Breakdown diagram
[OCB] Operational Capabilities diagram
[OAB] Operational Architecture diagram
[OES]
Operational
Entity
Scenario
[OAIB] Operational Activity Interaction diagram
Capella Days November 15, 2021
26. ARCADIA/CAPELLA - System Analysis Speaker: DROUIN Remy
Formalize system requirements
• Identify the boundary of the system
• Define what the system has to accomplish for the users
• Model functional dataflows and dynamic behaviour
NASA Handbook MBSE CAPELLA/ARCADIA HST
[MCB] Mission Capabilities Blank diagram
[CSA] Contextual System Actors diagram
[SDFB] Functional Dataflow Blank diagram
[FS]
Functional
Scenario
[SAB] System Architecture diagram
Capella Days November 15, 2021
27. ARCADIA/CAPELLA - Logical Architecture Speaker: DROUIN Remy
Developp system logical architecture
• See the system as a white box define how the system will work
so as to fulfill expectations
• Perform a trade-off analysis
NASA Handbook MBSE CAPELLA/ARCADIA HST
[LFBD] Functional Breakdwon diagram
[LDFB] Functional Dataflow Blank diagram
[LCBD] Logical Component Breakdown diagram
[LAB] Logical Architecture diagram
[ES] Exchange Scenario
Capella Days November 15, 2021
28. ARCADIA/CAPELLA - Physical Architecture Speaker: DROUIN Remy
Develop system Physical architecture
• How the system will be developed and built
• Software vs. hardware allocation, specification of interfaces,
• deployment configurations, trade-off analysis
NASA Handbook MBSE CAPELLA/ARCADIA HST
[PDFB] Physical Dataflow Blank diagram
[PCBD] Physical Component Breakdown diagram
[PAB]
Physical
Architecture
diagram
Capella Days November 15, 2021
29. Speaker: DROUIN Remy
ARCADIA/CAPELLA - Add ons sample
The Mass viewpoint enables to simply describe the non-functional aspect of mass in Capella.
The Price viewpoint enables to simply describe the non-functional aspect of price in Capella.
The Performance viewpoint enables to simply describe the non-functional aspect of performance in Capella.
Xhtml docgen addon enables the end-user to generate an HTML website from a Capella project.
Sharing models with all stakeholders is essential in model-based systems engineering. Publishing and
sharing HTML versions of models helps make models The reference of all engineering activities.
M2Doc generates MS-Word documents from Capella models. M2Doc uses customable Word templates to
extract data and diagrams from your models and display them in a docx file.
Several add ons are availables in order to unleash the power of MBSE workbench
Open-Source Add ons
NASA Handbook MBSE CAPELLA/ARCADIA HST
Price Mass Performance
Capella Days November 15, 2021
30. Speaker: DROUIN Remy
ARCADIA/CAPELLA - WEBSITE
https://www.eclipse.org/capella/arcadia.html
https://www.youtube.com/c/EclipseCapella
@Pascal Roques
@Jean Luc Voirin
“Systems Architecture Modeling with
the ARCADIA Method”
“Model-Based Systems and
Architecture Engineering with
the ARCADIA Method
NASA Handbook MBSE CAPELLA/ARCADIA HST
Capella Days November 15, 2021
31. Speaker: DROUIN Remy
ARCADIA/CAPELLA - HELP
@HELP Contents [CAPELLA modeler ]
https://forum.mbse-capella.org/
NASA Handbook MBSE CAPELLA/ARCADIA HST
Capella Days November 15, 2021
32. ARCADIA Versus NASA System Engineering Handbook Speaker: DROUIN Remy
1 2
3
1
2
3
4
4
NASA Handbook MBSE CAPELLA/ARCADIA HST
Requirements definition process
Technical solution definition process
Need understanding
Solution architectural design
Capella Days November 15, 2021
34. Hubble is a Cassegrain reflector telescope. Light from celestial objects travels down a tube, is collected by a bowl-like,
inwardly curved primary mirror and reflected toward a smaller, dome-shaped, outwardly curved secondary mirror. The
secondary mirror bounces the light back to the primary mirror and through a hole in its center. The light is focused on a small
area called the focal plane, where it is picked up by its various science instruments.
HUBBLE Space Telescope - Introduction Speaker: DROUIN Remy
Orbiting high above the Earth, the Hubble Space Telescope has a clear view of the universe free from the blurring and
absorbing effects of the atmosphere. In addition to observing visible and near-infrared light, Hubble detects ultraviolet light,
which is absorbed by the atmosphere and visible only from space. The telescope has beamed hundreds of thousands of
celestial images back to Earth during its time in space.
NASA Handbook MBSE CAPELLA/ARCADIA HST
The goal is not to apply the MBSE approach to the entire system, but just to apply few diagrams showing the application of
ARCADIA/CAPELLA
« All models are wrong, but some are useful » George E.P.Box (British statistician)
Capella Days November 15, 2021
35. HUBBLE Space Telescope facts Speaker: DROUIN Remy
➢ Launched: April 24, 1990
➢ Deployed: April 25, 1990. First Image – May 20, 1990
➢ Servicing missions: 4 (SM1 – SM4)
➢ Launch vehicle: Space Shuttle Discovery (STS-31)
➢ Launch site: Kennedy Space Center, Florida
➢ Location: Orbiting 340 miles (540 kilometers) above the Earth
➢ Orbital Period: Approximately 95 minutes to complete one orbit around Earth
➢ Speed: About 17,000 mph (27,300 kph)
➢ Wavelength coverage: Sensitivity to light: Ultraviolet through Infrared (115-1700nm)
NASA Handbook MBSE CAPELLA/ARCADIA HST
Capella Days November 15, 2021
36. HUBBLE Space Telescope science Speaker: DROUIN Remy
Answer some of the most compelling astronomical questions of our time, and uncovered mysteries we never knew existed
Solar System Exoplanets Stars&Nebulas Galaxies Universe Cosmic Wonders
NASA Handbook MBSE CAPELLA/ARCADIA HST
Capella Days November 15, 2021
37. Operational Analysis Speaker: DROUIN Remy
Operational Analysis
NASA Handbook MBSE CAPELLA/ARCADIA HST
Requirements definition process
Technical solution definition process
Need understanding
Solution architectural design
Capella Days November 15, 2021
38. Operational Analysis Speaker: DROUIN Remy
NASA Handbook MBSE CAPELLA/ARCADIA HST
Activity explorer
Activity explorer
Diagram editor
Capella Days November 15, 2021
39. Operational Analysis Speaker: DROUIN Remy
[OEBD] Operational Entity Breakdown diagram
NASA Handbook MBSE CAPELLA/ARCADIA HST
Capella Days November 15, 2021
40. Operational Analysis Speaker: DROUIN Remy
[OCB] Operational Capabilities diagram
NASA Handbook MBSE CAPELLA/ARCADIA HST
November 15, 2021
41. Operational Analysis Speaker: DROUIN Remy
NASA Handbook MBSE CAPELLA/ARCADIA HST
[OAB]
Operational
Architecture
diagram
[OAIB] Operational Activity Interaction diagram
Capella Days November 15, 2021
42. Operational Analysis Speaker: DROUIN Remy
Operations Support Room
Mission Operations Room
[OAB]
Operational
Architecture
diagram
[OES]
Operational
Entity
Scenario
NASA Handbook MBSE CAPELLA/ARCADIA HST
Capella Days November 15, 2021
43. System Analysis Speaker: DROUIN Remy
System Analysis
NASA Handbook MBSE CAPELLA/ARCADIA HST
Requirements definition process
Technical solution definition process
Need understanding
Solution architectural design
Capella Days November 15, 2021
44. System Analysis Speaker: DROUIN Remy
NASA Handbook MBSE CAPELLA/ARCADIA HST
Diagram editor
Activity explorer
Activity explorer
Capella Days November 15, 2021
45. System Analysis Speaker: DROUIN Remy
[MCB] Mission Capability Blank diagram
[CSA] Contextual System Actors diagram
NASA Handbook MBSE CAPELLA/ARCADIA HST
Capella Days November 15, 2021
46. System Analysis Speaker: DROUIN Remy
[M&S] Mode&State diagram
NASA Handbook MBSE CAPELLA/ARCADIA HST
Capella Days November 15, 2021
[SFBD]
Functional
Breakdown
diagram
47. System Analysis Speaker: DROUIN Remy
[SDFB] Functional Dataflow Blank diagram
NASA Handbook MBSE CAPELLA/ARCADIA HST
James Webb Telescope
HUBBLE Telescope
F1 Capture
cosmic light
Capella Days November 15, 2021
48. System Analysis Speaker: DROUIN Remy
[SAB] System Architecture diagram
NASA Handbook MBSE CAPELLA/ARCADIA HST
Capella Days November 15, 2021
49. System Analysis Speaker: DROUIN Remy
[SAB] System Architecture diagram
NASA Handbook MBSE CAPELLA/ARCADIA HST
Capella Days November 15, 2021
50. System Analysis Speaker: DROUIN Remy
NASA Handbook MBSE CAPELLA/ARCADIA HST
2
1
1
2
[CDB] Class diagram
1
2
Capella Days November 15, 2021
51. System Analysis Speaker: DROUIN Remy
[FS]
Functional
Scenario
NASA Handbook MBSE CAPELLA/ARCADIA HST
[ES]
Exchange
Scenario
Capella Days November 15, 2021
52. Logical Architecture Speaker: DROUIN Remy
Logical Architecture
NASA Handbook MBSE CAPELLA/ARCADIA HST
Requirements definition process
Technical solution definition process
Need understanding
Solution architectural design
Capella Days November 15, 2021
53. Logical Architecture Speaker: DROUIN Remy
NASA Handbook MBSE CAPELLA/ARCADIA HST
Activity explorer
Activity explorer
Diagram editor
Capella Days November 15, 2021
54. From System Analysis From Logical Architecture
Logical Architecture Speaker: DROUIN Remy
NASA Handbook MBSE CAPELLA/ARCADIA HST
[LFBD] Functional Breakdown diagram
Capella Days November 15, 2021
2
1
1
2
55. Logical Architecture Speaker: DROUIN Remy
[LDFB] Functional Dataflow Blank diagram
NASA Handbook MBSE CAPELLA/ARCADIA HST
[LFBD] Functional Breakdown diagram
[LFBD]
Functional
Breakdown
diagram
Capella Days November 15, 2021
56. Logical Architecture Speaker: DROUIN Remy
[LCBD] Logical Component Breakdown diagram
NASA Handbook MBSE CAPELLA/ARCADIA HST
Capella Days November 15, 2021
57. Logical Architecture Speaker: DROUIN Remy
[LAB] Logical Architecture diagram
NASA Handbook MBSE CAPELLA/ARCADIA HST
[LCBD]
Logical Component Breakdown diagram
Capella Days November 15, 2021
58. Logical Architecture Speaker: DROUIN Remy
[LAB] Logical Architecture Diagram
NASA Handbook MBSE CAPELLA/ARCADIA HST
Capella Days November 15, 2021
59. Logical Architecture Speaker: DROUIN Remy
NASA Handbook MBSE CAPELLA/ARCADIA HST
Pointing control subsystem analysis
Breakdown/Mode&State/Sequence diagam
[LCBD] Logical Component Breakdown diagram
[ES] Exchange Scenario
[ES] Exchange Scenario
[M&S]
Mode&State
diagram
Capella Days November 15, 2021
60. Speaker: DROUIN Remy
Logical Architecture
NASA Handbook MBSE CAPELLA/ARCADIA HST
Logical Components/Logical functions allocation matrix
[LAB] Logical Architecture Diagram
Capella Days November 15, 2021
61. Physical Architecture Speaker: DROUIN Remy
Physical Architecture
NASA Handbook MBSE CAPELLA/ARCADIA HST
Requirements definition process
Technical solution definition process
Need understanding
Solution architectural design
Capella Days November 15, 2021
62. Physical Architecture Speaker: DROUIN Remy
NASA Handbook MBSE introduction CAPELLA HST
NASA Handbook MBSE CAPELLA/ARCADIA HST
Activity explorer
Diagram editor
Activity explorer
Capella Days November 15, 2021
64. Physical Architecture Speaker: DROUIN Remy
NASA Handbook MBSE CAPELLA/ARCADIA HST
[PCBD] Physical Component Breakdown diagram
Capella Days November 15, 2021
Instruments
Sensors
Actuators
65. Physical Architecture Speaker: DROUIN Remy
NASA Handbook MBSE CAPELLA/ARCADIA HST
Capella Days November 15, 2021
[LAB] Logical Architecture Diagram
From [LAB]
To [PAB]
[PAB] Physical Architecture diagram
66. The Fixed Head Star Tracker (“Determine attitude by measuring location&brightness of stars”” function) is a sensitive,
electro-optical detector which has the capability of locating and tracking a target star within its Field Of View
Physical Architecture Speaker: DROUIN Remy
NASA Handbook MBSE CAPELLA/ARCADIA HST
Physical Architecture
Logical Architecture
[PFBD] Functional Breakdown diagram
System Analysis
[PDFB] Physical Dataflow Blank diagram
Capella Days November 15, 2021
67. Physical Architecture Speaker: DROUIN Remy
NASA Handbook MBSE CAPELLA/ARCADIA HST
[PAB]
Physical
Architecture
diagram
Capella Days November 15, 2021
68. Physical Architecture Speaker: DROUIN Remy
NASA Handbook MBSE CAPELLA/ARCADIA HST
[PAB] Physical Architecture diagram
1
2
1
2
[CDB] Class diagram
Capella Days November 15, 2021
69. Way to share data Speaker: DROUIN Remy
NASA Handbook MBSE CAPELLA/ARCADIA HST
Operational Analysis
System Analysis
Logical Architecture
Physical Architecture
Capella Days November 15, 2021