Introduction to SysML v.2.0 Metamodel (KerML)

Slides:



Advertisements
Similar presentations
Language Specification using Metamodelling Joachim Fischer Humboldt University Berlin LAB Workshop Geneva
Advertisements

Professor John Hosking, Dean of Engineering and Computer Science Models, Modelling, MBSE.
IEC Substation Configuration Language and Its Impact on the Engineering of Distribution Substation Systems Notes Dr. Alexander Apostolov.
Automated Analysis and Code Generation for Domain-Specific Models George Edwards Center for Systems and Software Engineering University of Southern California.
The Architecture Design Process
Unified Modeling (Part I) Overview of UML & Modeling
1/31 CS 426 Senior Projects Chapter 1: What is UML? Chapter 2: What is UP? [Arlow and Neustadt, 2005] January 22, 2009.
Basic Concepts The Unified Modeling Language (UML) SYSC System Analysis and Design.
1 IBM Software Group ® Mastering Object-Oriented Analysis and Design with UML 2.0 Module 1: Best Practices of Software Engineering.
Architecture Ecosystem Foundation (AEF) RFP aesig/ Draft RFP Presentation June 2010.
Assessing the Suitability of UML for Modeling Software Architectures Nenad Medvidovic Computer Science Department University of Southern California Los.
Copyright 2002 Prentice-Hall, Inc. Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich Chapter 20 Object-Oriented.
I n t e g r i t y - S e r v i c e - E x c e l l e n c e UPDM Review Session Col. Jack Jibilian Enterprise Architecting & Warfighting Decision Support SAF/XCPA.
SysML Reference Model Definition Model Based System Development in the Joint Strike Missile project Svein-Erik Søgård KDS/Missile Division.
Modeling Component-based Software Systems with UML 2.0 George T. Edwards Jaiganesh Balasubramanian Arvind S. Krishna Vanderbilt University Nashville, TN.
ICT EMMSAD’05 13/ Assessing Business Process Modeling Languages Using a Generic Quality Framework Anna Gunhild Nysetvold* John Krogstie *, § IDI,
Architecture View Models A model is a complete, simplified description of a system from a particular perspective or viewpoint. There is no single view.
© Fraunhofer IESE Fraunhofer IESE Multi-Language Development of Embedded Systems Dr. Thomas Kuhn Tel.:
Requirement Engineering with URN: Integrating Goals and Scenarios Jean-François Roy Thesis Defense February 16, 2007.
Ontologies Reasoning Components Agents Simulations An Overview of Model-Driven Engineering and Architecture Jacques Robin.
SysML v2 Planning & Requirements Working Group Meeting December 8 & 10, roadmap:sysml_assessment_and_roadmap_working_group.
Viewpoint Modeling and Model-Based Media Generation for Systems Engineers Automatic View and Document Generation for Scalable Model- Based Engineering.
System Modeling Assessment & Roadmap WG Meeting Boston, MA June 17, 2014 Eldad Palachi Sandy Friedenthal.
Systems Engineering Concept Model (SECM) Status 03/17/2016 John Watson.
® IBM Software Group © 2009 IBM Corporation Viewpoints and Views in SysML Dr Graham Bleakley
International Workshop 28 Jan – 2 Feb 2011 Phoenix, AZ, USA Modeling Standards Activity Team Model-based Systems Engineering (MBSE) Initiative Roger Burkhart.
Multi-disciplinary Approach for Industrial Phases in Space Projects Evolution of classic SE into MBSE Harald EisenmannAstrium Satellites Joachim Fuchs.
INCOSE MDSD SysML/AP233 Mapping Workshop Results David Price Allison Feeney
Modeling Formalism Modeling Language Foundations System Modeling & Assessment Roadmap WG SE DSIG Working Group Orlando – June 2016.
1 Modeling Formalism (Modeling Language Foundations) System Modeling Assessment & Roadmap Working Group Meeting – SE DSIG Reston – March, 2016 Yves BERNARD.
Status of SysML v2 Planning & Requirements Berlin, Germany June 16, roadmap:sysml_assessment_and_roadmap_working_group.
SysML v2 Formalism Requirements Formalism WG September 15, 2016.
Language = Syntax + Semantics + Vocabulary
SysML v2 RFP WG Meeting Introduction
Modeling Formalism Modeling Language Foundations
Interface Concepts Modeling Core Team
Systems Engineering Concept Model (SECM) Update
Systems Engineering Concept Model (SECM) Update
Integrating SysML with OWL (or other logic based formalisms)
SysML 2.0 Requirements for Visualization
SysML 2.0 Formalism Requirements and Potential Language Architectures
SysML 2.0 Formalism: Requirement Benefits, Use Cases, and Potential Language Architectures Formalism WG December 6, 2016.
CSCE 548 Secure Software Development Use Cases Misuse Cases
IS301 – Software Engineering Dept of Computer Information Systems
What is UML? What is UP? [Arlow and Neustadt, 2005] October 5, 2017
SysML v2 Planning & Requirements Working Group Meeting
SysML v2 Formalism: Requirements & Benefits
SysML v2 Usability Working Session
Syntactic Requirements
System Engineering Concept Model – Domain 8/5/2015 Status
Enterprise Data Model Enterprise Architecture approach Insights on application for through-life collaboration 2018 – E. Jesson.
Model-Driven Analysis Frameworks for Embedded Systems
SysML 2.0 Concept and Needs for Visualization
System Engineering Concept Model – Domain 9/24/2015 Status
File Systems and Databases
Systems Engineering Concept Model (SECM) Update
Status of the Systems Engineering Concept Model (SECM)
Systems Engineering Concept Model (SECM) Status Update
Introduction to UML.
Chapter 20 Object-Oriented Analysis and Design
UML profiles.
Status of the Systems Engineering Concept Model (SECM)
IDEAS Core Model Concept
John D. McGregor Module 6 Session 1 More Design
Automated Analysis and Code Generation for Domain-Specific Models
Quick orientation for MBSE Usability Group
Systems Engineering Concept Model (SECM) Update
Status of SysML v2 Planning & Requirements
MBSE / SysML adoption issues
Software Architecture & Design
Presentation transcript:

Introduction to SysML v.2.0 Metamodel (KerML) Charles Galey Bjorn Cole Conrad Bock

Agenda What is the Kernel Model? Motivation Architectural Principles As-is/To-be Abstract Syntax Examples Python Sanity Check Wrap-up

Kernel Modeling Language (KerML) A computer program that is the core of a computer's operating system (wikipedia)

Kernel Modeling Language (KerML) Started in 2014 as a part of the early development of the “Model Development Environment” a predecessor to today’s OpenMBEE Informed by experience and implementation challenges from development of OpenMBEE and “K” Began by identifying the basic set of concepts needed to create a simplified Systems Modeling Language Evolved into a more standards focused effort informed by Onto-Behavior Paper (Bock and Odell, 2011) Tactical needs of JPL’s Europa Clipper project ”K” Language

Motivation Address significant gaps in UML/SysML Without disturbing existing implementations Respond to SysML v.2 RFP

Major Focus: Language Simplification UML/SysML is unnecessarily complex Redundancy e.g. Classifier, Class, and Type Multiple overlapping behavior models Language hard to learn Lack of precision needed for reliable analysis and execution These problems make it hard for SysML to support primary systems engineering concerns Analysis Interface Definition Testing/Verification

Architectural Principles Simple and parsimonious Patterns to ensure symmetry and consistency Extensible SE Domain concepts build on Kernel concepts E.g., System sub-classes Block Leverage Model Libraries Formalize Semantics Reduces Complexity Provides Extensibility Support queries This was emphasized in the original concept model by the way Oliver made the symantic dictionary Grounding Points It is sufficient to define the concepts alone It outlines key goals for libraries 11/14/2018

Approach Bottoms up approach ”Onto” Identify M0 things to be modeled (i.e a spacecraft to be built) Create M1 Elements that model them (i.e the Class “Spacecraft”) Identify common concepts needed to formalize M1 Elements (i.e. “Anything with weight”) Add M2 elements as needed to simplify usage of M1 (i.e. Block etc.) Apply this approach to areas of UML we identified as concerns Introduce concepts to complete the picture General and special classes (i.e. Element and ControlFlow) in order to not disturb implementations Services model to support native Configuration Management

Measures of Effectiveness Quantitative SysML 1.x (Coverage/Issue Resolution) UML 2.5.X (Coverage/Issue Resolution/Compatibility) SysML 2.0 RFP (Requirements Satisfaction) Qualitative INCOSE Article MoE Analyzers and reasoners (Compatibility)

Comparison between As-Is/To-Be Status Quo (UML/SysML) KerML >200 metamodel elements Primary extension mechanism is at M2 Multiple behavior models that are not integrated with structure Complex abstract class terminology No Configuration Management model to define service requirements for implementers File based interoperability and separate verification tooling <100 metamodel elements Primary extension mechanism at M1 Unified structure and behavior model More sensible abstract terminology Configuration Management model to drive common service requirements Modeled interoperability and verification

Status Quo Modeling Environment

KerML Modeling Environment

Structure/Behavior Unification Example https://mms.openmbee.org/alfresco/mmsapp/mms.html#/projects/ PROJECT-d9ff6adf-53e5-44e5-8f6b- fb5b71687f0c/master/documents/_18_5_2_71301a1_150645987391 6_424306_36453/views/_18_5_2_71301a1_1506459916025_770253 _36523

Wrap-up Coverage of SysML v2.0 Requirements Coverage of UML 2.5.X Next steps

KerML Statistics for July draft RFP Req’s Total Req’s ~ 270 Covered by KerML core concepts ~ 75 Coverable by user libraries defined against KerML ~ 123 Key aspects of support: Unified structure and behavior Classification / individual approach Supports abstract to concrete, semantics for formal definition and constraints Jumping-off point for executable semantics Procedural (construction of instances, moving a “cursor” around the model for queries) Declarative (legal instances to create, requirements, constraints) Need math connection

Coverage of UML In the process of an exercise to evaluate UML concepts vs. KerML concepts Evaluating based on the following criteria: Integrated Merged Moved to M1 Library Compatible but not Integrated TBD

Next-steps Continue evaluation of work done so far (UML Coverage) Export of completed work to View Editor Specification format for Abstract Syntax Complete definitions for all Types and Properties Slide Deck replication Language Tasks State Machines (In Progress) Input/Output and Ports (In Progress) Sequence Diagrams Instance/ValueRestrictions

Python Sanity Check

Backup

INCOSE Article MoE Expressive: Ability to express the system concepts Precise: Representation is unambiguous and concise Presentation/communication: Ability to effectively communicate with diverse stakeholders Model construction: Ability to efficiently and intuitively construct models Interoperable: Ability to exchange and transform data with other models and structured data Manageable: Ability to efficiently manage change to models Usable: Ability for stakeholders to efficiently and intuitively leverage the modeling environment and modeling artifacts Adaptable/Customizable: Ability to extend models to support domain specific concepts and terminology 11/14/2018

Example of Service Data Model