Model Based System Engineering with Capella

of 28
All materials on our website are shared by users. If you have any questions about copyright issues, please report us to resolve them. We are always happy to assist you.
Document Description
Model Based System Engineering with Capella Laetitia Saoud TAS/ CTO / SSEPG - System Modelling expertise DOC-TAS-FR /06/2016 Ref.: SCOPE of the presentation 2 Introduction Arcadia & Capella
Document Share
Document Transcript
Model Based System Engineering with Capella Laetitia Saoud TAS/ CTO / SSEPG - System Modelling expertise DOC-TAS-FR /06/2016 Ref.: SCOPE of the presentation 2 Introduction Arcadia & Capella overview Co-architecting & multi criteria trade-off Example Additional information 02/06/2016 Ref.: Introduction Spatial systems: functional complexity & variety of criteria A wide range of needs combined with a lot of criteria and variety of technology lead to more and more complex system architectures From Requirements Allocation to Architecture Mastering Requirements Reqs Operational Need Functional Need Nonfunctional Constraints «Requirement to Box allocation» Architecture building & Justification Architecture Tradeoff late discovery of design issues during IVV Early validation of the Architecture Mastering and optimisation of product & IVV And from Document driven to MBSE practices Document Driven Model Driven Specifications Interface specifications System Design Analysis & Trade-off Test plans & procedures Moving from Document Centric to Data Centric Need for a collaborative architecting solution A global engineering approach, not limited to System engineers. To enable: HW and SW teams to: Customer Specialty engineers Operations engineers - work In co-engineering with system engineering team - take benefits for their own architecting activities IVVQ & Operations to: -express specific IVV needs, System Architects - build an IVVQ strategy driven by functions & architecture Domain analyses / specialty engineering to: - contribute to architecture early validation and optimization, - introduce architecture constraints from analyses 02/06/2016 SW/HW designers & developpers IVVQ manager Ref.: Arcadia & Capella Overview Thales MBE solution : Capella It embeds a Model Based Engineering method called ARCADIA : Customer need & operational concepts refinement System Functional analysis Solution architecture definition : Logical Architecture (sub-systems specification and internal interfaces) Physical Architecture (architecture as developed and deployed, incl. SW/HW allocation) 02/06/2016 Ref.: Capella core concepts Functions & dataflows Structure Interfaces & data Behaviour: scenario Behaviour: modes Ref.: Thales MBE solution : Capella Capella: Physical architecture System mission Functional analysis Provides graphical views for major engineering concerns Based on a central design database (model) = consistency and impact analysis Modes & States M O D E L Logical Architecture 02/06/2016 Scenarios (operations, IVV, protocols ) Interfaces Data model Interfaces definition Ref.: System modelling approach Operational Analysis Mission Operational processes description Voice of the customer 12 System Analysis Functional analysis/ mapping to upper level System externalinterfaces System lifecycle and scenarios Logical Architecture Physical Architecture System internalarchitecture: Groundcentersallocation and interfaces Space segment architecture (PL/PF alloc) Refinedoperationalscenarios, additionalfdir scenarios Physical design consolidation: Network and redundancies considerations Physical constraints/ perfo assessment Refined satellite FDIR End-to-end system analysis Ref.: 02/06/2016 Co-architecting & multi criteria trade-off Engineering disciplines constraints sharing Customer System Engineer - Architect SW / HW engineer Requirements Domain constraints and req. System model Domain teams Architecture constraints Parameters + constraints Domain engineering tools (perfo, RAM, safety) Analysis Ref.: 6/2/2016 Architecture Building & Design: the Art of Compromise Product Architecture must deal with potentially contradictory Constraints, which impact Breakdown, e.g. : Safety Performances Complexity of internal interfaces Ease of System Integration Cost, sub-contracting Product line Solution Architecture Architect RAMS, ILS, IVV Performance Non-Functional Viewpoint 2 Causal analysis -Tool locates problems -Quantitative analysis 3 Architecture improvement: -Lighter protocols -Higher bandwidth -Hardware processing 1 Automatic analysis: -CPU overloaded -Bus overloaded -Latency in excess Safety Non-Functional Viewpoint 2 Causal analysis -Tool locates problems -Failure propagation algorithm 1 Automatic analysis: -Rule: No single source for major failure condition -Not met for video 3 Architecture improvement: -Second redundant server Multi-Viewpoints Trade-off Confrontation rules for multi-viewpoints trade-off Exemple of functional allocation trade-off Functional allocation trade-off example : the problem Allocation trade-off on reference architecture security cost complexibility flexibility safety TM/TC bandwidth CPU Maturity Autonomy Timing Operation procedure specification Ground/board IRD PL IRD s/s Specification derivation OBCP specification PL management specification Functional allocation trade-off example : candidate architectures Autonomous payload Dumb payload managed from ground Functional allocation trade-off example : candidate architectures & automated evaluation. Dumb payload managed from OBCP Automated evaluation of criteria Some of the criteria may be automatically evaluated by the modeling environment: TM/TC bandwith, Sub-system complexity (from function complexity), Timing performances Compromise to be found for the precision of modeling (behaviours, timing, ) to obtain a representative model and the benefits wrt to manual evaluation. Additional information Open sourcing as Capella Melody Advance has been open sourced in 2015 as CAPELLA Clarity project: - Airbus D&S, Areva, Continental Automotive, OHB... - Collaboration/Contribution with external companies to develop extensions or tools integration What is Open Source? Va l u e Viewpoints IVV Product Line Safety Performance Etc. Expertise, Know-how, Core business Domain end-user solutions Domain platform Technical platform Advanced add-ons Teamworking Model maintenance Non functional Etc. Focus on one s value - Keep as competitive Advantage Share - Co-develop - Contribute - Use 26 ANY QUESTION? 02/06/2016 Ref.: The Thales MBE Odyssey Corporate Research Program Engineering Practices Transformation Plan Early Experiments Method Building Commercial Tools Experiments Pilot Deployments Short-Loop Validation & Adjustment Dedicated Tool Development Real Operational Use Tool Open Sourcing 02/06/2016 Ref.: NatoAF Unique and shared reference END USER CUSTOMER SYSTEM MODEL Subcontractors Specification & design ILS & operations Perfo RAMS AIV Managing the system complexity: Breakdown according to system layers, Mastering the product behaviour, Asking the right questions at the right time. Support requirement and design engineering wrt to customer inputs : Logical derivation from customer need analysis down to solution, Design data formalisation and organization A unique and shared reference for system definition: Viewpoints integration and sharing, Early validation Early preparation of ILS, AIV Support to analyses (trade-off, change impacts )
Search Related
We Need Your Support
Thank you for visiting our website and your interest in our free products and services. We are nonprofit website to share and download documents. To the running of this website, we need your help to support us.

Thanks to everyone for your continued support.

No, Thanks

We need your sign to support Project to invent "SMART AND CONTROLLABLE REFLECTIVE BALLOONS" to cover the Sun and Save Our Earth.

More details...

Sign Now!

We are very appreciated for your Prompt Action!