bdf44fbe35d581aba753b0dc01d0b4c1.ppt
- Количество слайдов: 63
SYSTEMS ENGINEERING COURSE BASICS OF SYSML Hervé Panetto, Professor University of Lorraine, TELECOM Nancy Research Centre for Automatic Control (CRAN UMR 7039 CNRS) Chair of IFAC CC 5 « Manufacturing and Logistics Systems » Herve. Panetto@univ-Lorraine. fr
Copyright This work is licensed under Creative Commons Attribution. Non. Commercial-Share. Alike 3. 0 available online at http: //creativecommons. org/licenses/by-nc-sa/3. 0/
Agenda ØWhat is Sys. ML? Relationship between UML and Sys. ML Examples of Extensions Industrial Control Concluding Remarks 3
What is Sys. ML? A graphical modeling language in response to the UML for Systems Engineering RFP developed by the OMG, INCOSE, and AP 233 ¦ a UML Profile that represents a subset of UML 2 with extensions Supports the specification, analysis, design, verification and validation of systems that include hardware, software, data, personnel, procedures, and facilities Supports model and data interchange via XMI and the evolving AP 233 standard (in-process) Sys. ML is a Critical Enabler for Model Driven SE 4
Sys. ML Background UML for System Engineering RFP issued – 28 March 2003 Sys. ML Partners Kickoff meeting – 6 May 2003 ¦ Chaired by S. Friedenthal and C. Kobryn v 0. 9 Submission to OMG – 10 Jan 2005 ¦ Addendum stereotypes chapter – 30 May 2005 SST and SP split – 30 August 2005 SST/SP revised submissions to OMG – 14 November 2005 INCOSE and OMG Evaluations – December 2005 thru January 2006 Sys. ML Merge Team (SMT) submission v 0. 99 (ad/2006 -02 -01) – 13 February 2006 SMT formally announced - 15 February 2006 OMG Systems Modeling Language (OMG Sys. ML) Specification - Final Adopted Specification ptc/06 -05 -04 – 6 July 2006 – Final public version planned in April 2007. 5
Sys. ML Partners Industry ¦ American Systems, EADS Astrium, BAE SYSTEMS, Boeing, Deere & Company, Eurostep, Israel Aircraft Industries, Lockheed Martin, Motorola, Northrop Grumman, oose. de, Raytheon, THALES Government ¦ Do. D/OSD, NASA/JPL, NIST Vendors ¦ Artisan, Ceira, Gentleware, IBM/Rational, I-Logix, Pivot. Point Technology, Popkin, Project Technology, 3 SL, Telelogic, Vitech Liaisons ¦ AP-233, CCSDS, EAST, INCOSE, Rosetta 6
Sys. ML Context Services - Enterprise Systems - Operations Layers FEA-DEA-BEA Federal and Defense Enterprise Architectures Enterprise Architects Do. DAF Program Architects System Architects And Engineers Do. D Architectural Framework across multiple levels (Zachman And Mo. DAF are similar) UPDM Unified Modeling Language (UML) Profile for Do. DAF and Mod. AF SCBA FEA extension to Services and Components Sys. ML UML Extension for Systems Engineering SOA Architecture based on services SDF Service Interface Descriptions MDA Software Architects Developers UML Models For software Architecture, Components and interfaces SCA Component Interface Description Testbeds such as Federated Development and Certification Environment (FDCE) including Live Systems, Modules, Components , Services and Simulations 7
Sys. ML Specification Outline Preface • • Allocations • Requirements • Profiles & Model Libraries Part I - Introduction Part II – Structural Constructs ¦ Model Elements ¦ Blocks ¦ Ports and Flows ¦ Constraint Blocks Part III – Behavioral Constructs ¦ Activities ¦ Interactions ¦ State Machines Part IV – Crosscutting Constructs • Part V Appendices • • Diagrams Sample Problem Non-Normative Extensions Model Interchange * Requirements Traceability Terms and Definitions * BNF Diagram Syntax Definitions ¦ Use Cases 8
Harmony – a System Engineering Development Process 9
Agenda üWhat is Sys. ML? ØRelationship between UML and Sys. ML Examples of Extensions Industrial Control Concluding Remarks 10
Relationship Between Sys. ML and UML 4 Sys. ML Profile 11
Sys. ML Diagram Taxonomy 12
Major Extensions to UML 2 New Diagram Types ¦ Requirement Diagram (visual modeling of requirements) ¦ Parametric Diagram (showing relations between parameters) Structure Diagram ¦ Block Definition Diagram (based on UML class diagram with blocks instead of classes) ¦ Internal Block Diagram (based on UML composite structure diagram with restrictions and extensions) Activity Diagram ¦ extensions for continuous flow modeling ¦ extensions to support disabling control and control operators. 13 ¦ accommodate needs of Extended Functional Flow Block
Agenda üWhat is Sys. ML? üRelationship between UML and Sys. ML ØExamples of Extensions Industrial Control Concluding Remarks 14
Sys. ML Diagram Frames 15
Blocks are Basic Structural Elements 16
Block Definition Diagram 17
Internal Block Diagram 18
Internal Block Diagram Example Control signals 19
Requirements Diagram (NEW) 20
Parametric Diagram (NEW) Used to express constraints (equations) between value properties ¦ Provides support for engineering analysis (e. g. , performance, reliability) Constraint block captures equations ¦ Expression language can be formal (e. g. , Math. ML, OCL) or informal ¦ Computational engine is defined by applicable analysis tool and not by Sys. ML Parametric diagram represents the usage of the constraints in an analysis context ¦ Binding of constraint usage to value properties of blocks (e. g. , vehicle mass bound to F= m × a) Parametrics Enable Integration of Engineering Analysis with Design Models 21
Example: Defining Vehicle Dynamics 22
Example: Vehicle Dynamics Analysis – Parametric Diagram 23
Parametric Example - Usage Parametric Diagram 24
Activity Diagram Notation Flows can be discrete, streaming or control 25
Sys. ML EFFBD Profile 26
Allocations Provides general relationship to map one model element to another Includes specific subclasses of allocation with constraints on their usage ¦Behavioral ¦Structural ¦Flow Explicit allocation of activities to swim lanes (e. g. activity partitions) Graphical and/or tabular representations 27
Different Allocation Representations Allocate Relationship Compartment Notation Explicit Allocation of Activity to Swim Lane Callout Notation 28
Example - Sys. ML Allocation to SW and HW 29
4 Pillars of Sys. ML ABS Example 1. Structure 2. Behavior interaction state machine activity/ function definition use 3. Requirements 30 4. Parametrics
Cross Connecting Model Elements 2. Behavior 1. Structure ate c allo value binding satisfy 3. Requirements verify 31 4. Parametrics
Agenda üWhat is Sys. ML? üRelationship between UML and Sys. ML üExamples of Extensions ØIndustrial Control Concluding Remarks 32
System Modeling 33
Combining Model-Driven and Model Based Design in Industrial Machine Control MDD: Model Driven Development in Rhapsody (Telelogic) MBD: Model Based Design in Simulink (Mathworks) 34
MDD versus MBD Feature Comparison Table 1. MDD versus MBD feature comparison 35
Complementary Tool Solution The Rhapsody MDD environment covers standard UML 2. 0 / Sys. ML based software and systems design Simulink is the de-facto standard for dynamic systems modeling ¦ allowing block diagrams of complex dynamic (mathematical) algorithms to be captured analyzed Simulink connection to Rhapsody 36
Rhapsody – Simulink Integration (1) 37
Rhapsody – Simulink Integration (2) Simulink Model and Code Imported into Rhapsody 38
Agenda üWhat is Sys. ML? üRelationship between UML and Sys. ML üExamples of Extensions üIndustrial Control ØConcluding Remarks 39
Concluding Remarks Sys. ML contains many interesting extensions of UML It will be good to get a more common language between different disciplines Question is what kind of validation can be made with these different models ¦ What about common semantics? ¦ What about time connectivity between discrete event an continuous simulators? 40
WHERE WE’VE COME FROM… A HISTORICAL PERSPECTIVE INCOSE US D. O. D OO Programming : ADA Eiffel Smalltalk Simula C++ Bell Labs XEROX PARC Booch Sys. ML Wirfs-Brock Jacobson: OOSE ecc. . . Shlaer/Mellor Structured Method: SA&SD Entity Modelling Event Modellingi yrs ’ 60 yrs ’ 70 UML SPEM MOF BPMN XMI DDS Coad/Yourdon Rumbaugh: OMT Martin/Odell yrs ’ 80 yrs ’ 90 MDA yrs 2000 41
SYSML CONTEXT Services - Enterprise Systems - Operations Layers FEA-DEA-BEA Federal and Defense Enterprise Architectures Enterprise Architects Do. DAF Program Architects System Architects And Engineers Do. D Architectural Framework across multiple levels (Zachman And Mo. DAF are similar) UPDM Unified Modeling Language (UML) Profile for Do. DAF and Mod. AF SCBA FEA extension to Services and Components Sys. ML UML Extension for Systems Engineering SOA Architecture based on services SDF Service Interface Descriptions MDA Software Architects Developers UML Models For software Architecture, Components and interfaces SCA Component Interface Description Testbeds such as Federated Development and Certification Environment (FDCE) including Live Systems, Modules, Components , Services and Simulations
A UNIFYING SYSTEMS LANGUAGE Sys. ML A Language to document the properties from different disciplines to describe the whole solution 43
RELATIONSHIP BETWEEN SYSML AND UML 4 Sys. ML Profile
THE FOUR PILLARS OF SYSML (ABS EXAMPLE) 2. Behavior 1. Structure interaction definition state machine activity/function use 4. Parametrics 3. Requirements 45
SYSML DIAGRAM TAXONOMY
Sys. ML: A Key Enabler for MBSE The Systems Modeling Language (OMG Sys. MLTM) is a visual, general purpose modeling language What Can be Expressed in Sys. ML? ¦ All the information and knowledge needed for the application of a systems development methodology u u u Specification Analysis Design Verification Validation u u u Hardware Software Data Personnel Procedures Facilities
Pillars of Sys. ML — 4 Main Diagram Types 1. Structure (Source: Friedenthal, www. omgsysml. org) 2. Behavior definition 4. Requirements 3. Parametrics
Pillars of Sys. ML — 4 Main Diagram Types 1. Structure definition (Source: Friedenthal, www. omgsysml. org) 2. Behavior use 4. Requirements 3. Parametrics
Pillars of Sys. ML — 4 Main Diagram Types 1. Structure (Source: Friedenthal, www. omgsysml. org) 2. Behavior interaction definition use 4. Requirements 3. Parametrics
Pillars of Sys. ML — 4 Main Diagram Types 1. Structure (Source: Friedenthal, www. omgsysml. org) 2. Behavior interaction state machine definition use 4. Requirements 3. Parametrics
Pillars of Sys. ML — 4 Main Diagram Types 1. Structure (Source: Friedenthal, www. omgsysml. org) 2. Behavior interaction state machine activity/ function definition use 4. Requirements 3. Parametrics
Pillars of Sys. ML — 4 Main Diagram Types 1. Structure (Source: Friedenthal, www. omgsysml. org) 2. Behavior interaction state machine activity/ function definition use 4. Requirements 3. Parametrics
Pillars of Sys. ML — 4 Main Diagram Types 1. Structure (Source: Friedenthal, www. omgsysml. org) 2. Behavior interaction state machine activity/ function definition use 4. Requirements 3. Parametrics
Cross Connecting Model Elements 1. Structure 4. Requirements (Source: Friedenthal, www. omgsysml. org) 2. Behavior 3. Parametrics
Cross Connecting Model Elements 1. Structure (Source: Friedenthal, www. omgsysml. org) 2. Behavior ate c allo 4. Requirements 3. Parametrics
Cross Connecting Model Elements 1. Structure (Source: Friedenthal, www. omgsysml. org) 2. Behavior ate c allo 4. Requirements 3. Parametrics
Cross Connecting Model Elements 1. Structure (Source: Friedenthal, www. omgsysml. org) 2. Behavior ate c allo satisfy 4. Requirements 3. Parametrics
Cross Connecting Model Elements 1. Structure (Source: Friedenthal, www. omgsysml. org) 2. Behavior ate c allo satisfy 4. Requirements 3. Parametrics
Cross Connecting Model Elements 1. Structure (Source: Friedenthal, www. omgsysml. org) 2. Behavior ate c allo satisfy 4. Requirements value binding 3. Parametrics
Cross Connecting Model Elements 1. Structure (Source: Friedenthal, www. omgsysml. org) 2. Behavior ate c allo satisfy 4. Requirements value binding 3. Parametrics
Cross Connecting Model Elements 1. Structure (Source: Friedenthal, www. omgsysml. org) 2. Behavior ate c allo value binding satisfy verify 4. Requirements 3. Parametrics
SYSTEMS ENGINEERING COURSE BASICS OF SYSML Hervé Panetto, Professor University of Lorraine, TELECOM Nancy Research Centre for Automatic Control (CRAN UMR 7039 CNRS) Chair of IFAC CC 5 « Manufacturing and Logistics Systems » Herve. Panetto@univ-Lorraine. fr
bdf44fbe35d581aba753b0dc01d0b4c1.ppt