SysML 2.0 Interface Concepts Modeling Core Team

Slides:



Advertisements
Similar presentations
Software Modeling SWE5441 Lecture 3 Eng. Mohammed Timraz
Advertisements

A Brief Introduction. Acknowledgements  The material in this tutorial is based in part on: Concurrency: State Models & Java Programming, by Jeff Magee.
Unified Modeling Language
Introduction and Overview “the grid” – a proposed distributed computing infrastructure for advanced science and engineering. Purpose: grid concept is motivated.
Developed by Reneta Barneva, SUNY Fredonia Component Level Design.
Systems Engineering Foundations of Software Systems Integration Peter Denno, Allison Barnard Feeney Manufacturing Engineering Laboratory National Institute.
 The Open Systems Interconnection model (OSI model) is a product of the Open Systems Interconnection effort at the International Organization for Standardization.
© 2007 Cisco Systems, Inc. All rights reserved.Cisco Public 1 Version 4.0 Communicating over the Network Network Fundamentals – Chapter 2.
Protocols and the TCP/IP Suite Chapter 4. Multilayer communication. A series of layers, each built upon the one below it. The purpose of each layer is.
Free Mini Course: Applying SysML with MagicDraw
An Introduction to Software Architecture
SAMANVITHA RAMAYANAM 18 TH FEBRUARY 2010 CPE 691 LAYERED APPLICATION.
Lecture 3: Visual Modeling & UML 1. 2 Copyright © 1997 by Rational Software Corporation Computer System Business Process Order Item Ship via “ Modeling.
SWE © Solomon Seifu ELABORATION. SWE © Solomon Seifu Lesson 10 Use Case Design.
Chapter 10 Analysis and Design Discipline. 2 Purpose The purpose is to translate the requirements into a specification that describes how to implement.
ניתוח מערכות מידע 1 Unified Modeling Language (UML) § § The Unified Modeling Language (UML) is the industry-standard language for: Specifying, Visualizing,
FDT Foil no 1 On Methodology from Domain to System Descriptions by Rolv Bræk NTNU Workshop on Philosophy and Applicablitiy of Formal Languages Geneve 15.
Logical view –show classes and objects Process view –models the executables Implementation view –Files, configuration and versions Deployment view –Physical.
Class Diagrams. Terms and Concepts A class diagram is a diagram that shows a set of classes, interfaces, and collaborations and their relationships.
Object Oriented Programming and Data Abstraction Earl Huff Rowan University.
Diagrams. Typically, we view the static parts of a system using one of the four following diagrams. 1. Class diagram 2. Object diagram 3. Component diagram.
SysML and Modelica Integration Working Group Meeting 3/11/09 Peter Fritzson Wladimir Schamai.
Systems Modeling Language (SysML). 2 What is SysML? A graphical modeling language in response to UML for Systems Engineering developed by the OMG, INCOSE,
Integrating BPMN and SoaML Based on an example from SoaML spec.
Interface Concepts Modeling Core Team Marc Sarrel Steve Hetfield June 23, 2016.
Language = Syntax + Semantics + Vocabulary
SysML 2.0 Requirements for Visualization
IBM Rational Rhapsody Advanced Systems Training v7.5
Interface Concepts Modeling Core Team
A Representative Application of a Layered Interface Modeling Pattern
SysML 2.0 Requirements for Visualization
A modeling pattern for layered system interfaces
Course Outcomes of Object Oriented Modeling Design (17630,C604)
COMPONENT & DEPLOYMENT DIAGRAMS
Current Framework and Fundamental Concepts
IEEE 802 OmniRAN Study Group: SDN Use Case
Layered Interface Modeling Approach
SysML v2 Formalism: Requirements & Benefits
Modeling Systems-of-Systems Interfaces with SysML
Unified Modeling Language
SysML v2 Usability Working Session
SysML 2.0 Interface Concepts Modeling Core Team
CT1303 LAN Rehab AlFallaj.
Web Ontology Language for Service (OWL-S)
Application of ODP for Space Development
Software Architecture & Design Pattern
Chapter 13 Logical Architecture.
SysML 2.0 Concept and Needs for Visualization
SysML 2.0 Interface Concepts Modeling Core Team Status Update
Chapter 2 Database Environment Pearson Education © 2009.
A Representative Application of a Layered Interface Modeling Pattern
Interface Concepts Modeling Core Team
EEC-484/584 Computer Networks
Unified Modeling Language
SysML 2.0 Interface Concepts Modeling Core Team Status Update
Object Oriented Analysis and Design
Chapter 20 Object-Oriented Analysis and Design
Chapter 13 Logical Architecture.
Architecture Description Languages
Layering & protocol stacks Johan Lukkien
An Introduction to Software Architecture
SAMANVITHA RAMAYANAM 18TH FEBRUARY 2010 CPE 691
Copyright © 2015, 2012, 2009 Elsevier Inc. All rights reserved.
Copyright © 2015, 2012, 2009 Elsevier Inc. All rights reserved.
Overview of the ETSI Test Description Language
Copyright © 2015, 2012, 2009 Elsevier Inc. All rights reserved.
Design Yaodong Bi.
Modeling Modelica Interfaces with SysML v1.3
Chapter 2 Database Environment Pearson Education © 2009.
Software Development Process Using UML Recap
Presentation transcript:

SysML 2.0 Interface Concepts Modeling Core Team Marc Sarrel, Jet Propulsion Laboratory, California Institute of Technology Steve Hetfield, BAE Systems, Inc. 2017-03-22 © 2017 California Institute of Technology. Government sponsorship acknowledged.

Primary Goals for Interface Modeling The information captured in the model includes equivalent information that is generally contained in an interface specification document and interface design document (e.g. IRS, IDD, ICD, ...) The interface concepts are consistent with the behavior, structure, and other concepts of the language The concepts of interface specification and interface realization are distinct such that the model can clearly capture how interface specifications can be realized. Ensure a consistent approach to model a diverse range of interfaces (e.g. electrical, mechanical, software, user IF), and include the ability to model Modelica-like physical interface concepts and flow based concepts Ensure ability to support nested interfaces and reusable interfaces Ensure the ability to readily model different interface viewpoints that address a broad range of interface concerns 2017-03-22

Context Elaborate Interface Concept Model in context of Structure WG Incorporate concepts from prior interface modeling work From interface needs document there are three orthogonal dimensions Interface Definition vs Interface Usage Interface Specification vs Realization Interface Layers (e.g. OSI protocol layers) Levels of Abstraction (e.g. showing and hiding detail and intermediate systems) Will address first three. Assume that Levels of Abstraction is handled by Visualization and Model Construction groups. 2017-03-22

Definition of Interface We take the definition of an interface to include: The things on either end The connection between them This applies both for the Interface Definition and the Interface Usage Interface End Interface End Interface Connection 2017-03-22

2017-03-22

Specification vs Realization Have changed concept model in this area. No longer have separate concepts for specification and realization. Specification vs Realization Interface Context Interface Definition Interface Participant / Component Interface Context Interface Definition port Interface Medium Component Interface Participant / Component Item Specification Interface End port Interface Usage port connector Interface Usage port connector 2017-03-22

Specification Realizes Over Realization Over Over Over Over 2017-03-22

Realizes Realizes Item Specification 2017-03-22

Component RFC 793 Realizes Interface Connector Component Behavior Exchange Agreement 2017-03-22

Interface Layers 2017-03-22

Levels of Abstraction 2017-03-22

Interface Concept Model 1 2017-03-22

Interface Concept Model 2 2017-03-22

Interface Concept Model 3 2017-03-22

Interface Concept Model 4 2017-03-22

Mapping to Structure Concepts 2017-03-22

Interface Requirements 1 Interface Context The SysML v2 specification shall represent an Interface Context that allows the assembly and connection of Interface Participants and Interface Agreements. Interface Participant The SysML v2 specification shall represent an Interface Participant as a special kind of Interface Context that present Interface Ends and may be connected to other Interface Participants. Component The SysML v2 specification shall represent a Component as a special kind of Interface Participant that models a real item, either physical or logical. Interface Medium Component The SysML v2 specification shall represent an Interface Medium Component as a special kind of Component that models an interface medium. Function The SysML v2 specification shall represent a Function as a special kind of Interface Participant that models an abstract function. 2017-03-22

Interface Requirements 2 Interface Association The SysML v2 specification shall represent an Association that defines the which Interface Participants may be connected. Interface End The SysML v2 specification shall represent an Interface End that defines the specification presented to other Interface Participants, and defines to which Associations an Interface Participant may be connected. Interface Constraint The SysML v2 specification shall represent an Interface Constraint that constrains the interactions between Interface Participants. Interface Agreement The SysML v2 specification shall represent an Interface Agreement as a special kind of Interface Constraint that defines the mathematical parametric relationships between Interface Participants. Exchange Agreement The SysML v2 specification shall represent an Exchange Agreement as a special kind of Interface Constraint that defines when and how Item Specifications are exchanged between Interface Participants. 2017-03-22

Interface Requirements 3 Item Specification The SysML v2 specification shall represent an Item Specification that defines the items that may be exchanged according to an Exchange Agreement. Across Value Type The SysML v2 specification shall represent an Across Value Type, a special kind of Value Type (from structure) that defines across values. Through Value Type The SysML v2 specification shall represent an Through Value Type, a special kind of Value Type (from structure) that defines across values. Across Interface Agreement The SysML v2 specification shall represent an Across Interface Agreement as a special kind of Interface Agreement that defines the mathematical parametric relationships between Across Value Types of Interface Participants. Through Interface Agreement The SysML v2 specification shall represent a Through Interface Agreement as a special kind of Interface Agreement that defines the mathematical parametric relationships between Through Value Types of Interface Participants. 2017-03-22

Interface Requirements 4 Realizes The SysML v2 specification shall represent a Realizes relation that defines how an abstract interface usage is reified by a more concrete interface usage. Over The SysML v2 specification shall represent an Over relation, that specifies how an interface usage at an upper layer of a layered interface is transformed into an interface usage at a lower layer between Interface Participants. 2017-03-22