SysML 2.0 Interface Concepts Modeling Core Team Status Update

Slides:



Advertisements
Similar presentations
A Brief Introduction. Acknowledgements  The material in this tutorial is based in part on: Concurrency: State Models & Java Programming, by Jeff Magee.
Advertisements

Issues of Security and Privacy in Networking in the CBA Karen Sollins Laboratory for Computer Science July 17, 2002.
Recall The Team Skills 1. Analyzing the Problem (with 5 steps) 2. Understanding User and Stakeholder Needs 3. Defining the System A Use Case Primer Organizing.
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.
© 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.
The Design Discipline.
1 IBM Software Group ® Mastering Object-Oriented Analysis and Design with UML 2.0 Module 1: Best Practices of Software Engineering.
SWE © Solomon Seifu ELABORATION. SWE © Solomon Seifu Lesson 10 Use Case Design.
Systems Analysis and Design in a Changing World, 3rd Edition
Software Engineering Prof. Ing. Ivo Vondrak, CSc. Dept. of Computer Science Technical University of Ostrava
UML - Development Process 1 Software Development Process Using UML.
Chapter 6 Guidelines for Modelling. 1. The Modelling Process 1. Modelling as a Transformation Process 2. Basic Modelling Activities 3. Types of Modelling.
Systems Realization Laboratory SysML-based Reference Models for Fluid Power Components Chris Paredis, Raphael Kobi Product & Systems Lifecycle Management.
Systems Engineering Concept Model (SECM) Status 03/17/2016 John Watson.
MBSE Panel Integrating MBSE into a Multi-Disciplinary Engineering Environment An ELECTRICAL SYSTEM ENGINEERING Perspective Alex Jimenez Jet Propulsion.
Interface Concepts Modeling Core Team Marc Sarrel Steve Hetfield June 23, 2016.
Washington, D.C., U.S.A May Some concepts of systems architectures Industrialization of statistics and software architecture Study cases.
CLUE WG Interim Meeting San Jose, CA Sept , 2012
Process 4 Hours.
CLOUD ARCHITECTURE Many organizations and researchers have defined the architecture for cloud computing. Basically the whole system can be divided into.
Interface Concepts Modeling Core Team
A Representative Application of a Layered Interface Modeling Pattern
Systems Engineering Concept Model (SECM) Update
SysML 2.0 Requirements for Visualization
A modeling pattern for layered system interfaces
Course Outcomes of Object Oriented Modeling Design (17630,C604)
CLUE WG Interim Meeting San Jose, CA Sept , 2012
COMPONENT & DEPLOYMENT DIAGRAMS
IEEE 802 OmniRAN Study Group: SDN Use Case
Local Area Networks Chapter 4.
Layered Interface Modeling Approach
Modeling Systems-of-Systems Interfaces with SysML
SysML v2 Usability Working Session
SysML 2.0 Interface Concepts Modeling Core Team
Note Well Any submission to the IETF intended by the Contributor for publication as all or part of an IETF Internet-Draft or RFC and any statement made.
Reference: COS240 Syllabus
CT1303 LAN Rehab AlFallaj.
CHAPTER 3 Architectures for Distributed Systems
P802.1CF NRM Discussions Abstract
ITU languages for ODP - a personal view - I may be wrong!
Enterprise Data Model Enterprise Architecture approach Insights on application for through-life collaboration 2018 – E. Jesson.
Chapter 13 Logical Architecture.
A Representative Application of a Layered Interface Modeling Pattern
Software Reuse Objectives
Interface Concepts Modeling Core Team
Systems Engineering Concept Model (SECM) Update
A Pattern Language for Software Architecture
EEC-484/584 Computer Networks
Unified Modeling Language
SysML 2.0 Interface Concepts Modeling Core Team Status Update
Object Oriented Analysis and Design
Interface Needs Model Diagrams Review
Chapter 20 Object-Oriented Analysis and Design
Chapter 13 Logical Architecture.
Verification Concepts for SysmL v2
Architecture Description Languages
SysML-based Reference Models for Fluid Power Components
An Introduction to Software Architecture
Copyright © 2015, 2012, 2009 Elsevier Inc. All rights reserved.
Overview of the ETSI Test Description Language
Modeling Modelica Interfaces with SysML v1.3
Verification Concepts for SysmL v2
SysML 2.0 Interface Concepts Modeling Core Team
Brokering as a Core Element of EarthCube’s Cyberinfrastructure
Systems Engineering Concept Model (SECM) Update
Software Development Process Using UML Recap
Status of SysML v2 Planning & Requirements
Note Well Any submission to the IETF intended by the Contributor for publication as all or part of an IETF Internet-Draft or RFC and any statement made.
Presentation transcript:

SysML 2.0 Interface Concepts Modeling Core Team Status Update Marc Sarrel, Jet Propulsion Laboratory, California Institute of Technology Steve Hetfield, BAE Systems, Inc. 2016-12-08 © 2016 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 2016-12-08

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 (NEW) 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. 2016-12-08

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 2016-12-08

Interface Concept Model From John Watson’s Interface Needs Presentation 2016-12-08

Updated Interface Concept Model 2016-12-08

2016-12-08

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 2016-12-08

Specification Realization Realizes 2016-12-08

Realizes Realizes Item Specification 2016-12-08

Component RFC 793 Realizes Interface Connector Component Behavior Exchange Agreement 2016-12-08

Realizes 2016-12-08

Interface Layers «Over» may be replaced by «Realizes» 2016-12-08

Levels of Abstraction 2016-12-08