Viewpoint Modeling and Model-Based Media Generation for Systems Engineers Automatic View and Document Generation for Scalable Model- Based Engineering.

Slides:



Advertisements
Similar presentations
Integration of MBSE and Virtual Engineering for Detailed Design
Advertisements

HL7 V2 Implementation Guide Authoring Tool Proposal
IEC Substation Configuration Language and Its Impact on the Engineering of Distribution Substation Systems Notes Dr. Alexander Apostolov.
Requirements Engineering n Elicit requirements from customer  Information and control needs, product function and behavior, overall product performance,
Building Enterprise Applications Using Visual Studio ®.NET Enterprise Architect.
L4-1-S1 UML Overview © M.E. Fayad SJSU -- CmpE Software Architectures Dr. M.E. Fayad, Professor Computer Engineering Department, Room #283I.
Creating Architectural Descriptions. Outline Standardizing architectural descriptions: The IEEE has published, “Recommended Practice for Architectural.
CASE Tools CIS 376 Bruce R. Maxim UM-Dearborn. Prerequisites to Software Tool Use Collection of useful tools that help in every step of building a product.
CS 290C: Formal Models for Web Software Lecture 6: Model Driven Development for Web Software with WebML Instructor: Tevfik Bultan.
System Engineering Instructor: Dr. Jerry Gao. System Engineering Jerry Gao, Ph.D. Jan System Engineering Hierarchy - System Modeling - Information.
The Software Product Life Cycle. Views of the Software Product Life Cycle  Management  Software engineering  Engineering design  Architectural design.
XML Exchange Development CAM Technology Tutorial – Public Sector NIEM Team, June 2011 CAM Test Model Data Deploy Requirements Build Exchange Generate Dictionary.
LEVERAGING THE ENTERPRISE INFORMATION ENVIRONMENT Louise Edmonds Senior Manager Information Management ACT Health.
Framework for Model Creation and Generation of Representations DDI Lifecycle Moving Forward.
Enterprise Architecture
OASIS document rules Nigel Shaw Eurostep Limited.
State of Connecticut Core-CT Project Query 4 hrs Updated 1/21/2011.
Chapter 7: The Object-Oriented Approach to Requirements
Model Based Systems Engineering (MBSE) using SysML GSFC Systems Engineering Seminar June 8, 2010 Sanford Friedenthal Lockheed Martin
Developing Enterprise Architecture
Principles of Object Technology Module 1: Principles of Modeling.
BRUE Behavioral Reverse Engineering in UML as Eclipse Plugin MSE Presentation 1 Sri Raguraman.
Web Development Process Description
Requirements Analysis
Implementation Yaodong Bi. Introduction to Implementation Purposes of Implementation – Plan the system integrations required in each iteration – Distribute.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 6 Slide 1 Chapter 6 Requirements Engineering Process.
ITEC224 Database Programming
Introduction to MDA (Model Driven Architecture) CYT.
Requirements Engineering Requirements Elicitation Process Lecture-8.
OOI CI LCA REVIEW August 2010 Ocean Observatories Initiative OOI Cyberinfrastructure Architecture Overview Michael Meisinger Life Cycle Architecture Review.
Slide 12.1 Chapter 12 Implementation. Slide 12.2 Learning outcomes Produce a plan to minimize the risks involved with the launch phase of an e-business.
Unified Modeling Language* Keng Siau University of Nebraska-Lincoln *Adapted from “Software Architecture and the UML” by Grady Booch.
Fifth Lecture Hour 9:30 – 10:20 am, September 9, 2001 Framework for a Software Management Process – Life Cycle Phases (Part II, Chapter 5 of Royce’ book)
L6-S1 UML Overview 2003 SJSU -- CmpE Advanced Object-Oriented Analysis & Design Dr. M.E. Fayad, Professor Computer Engineering Department, Room #283I College.
Requirements Formulation: Document Management vs
Health eDecisions Use Case 2: CDS Guidance Service Strawman of Core Concepts Use Case 2 1.
Rational Unified Process Fundamentals Module 7: Process for e-Business Development Rational Unified Process Fundamentals Module 7: Process for e-Business.
International Workshop Jan 21– 24, 2012 Jacksonville, Fl USA Model-based Systems Engineering (MBSE) Initiative Slides by Henson Graves Presented by Matthew.
Architecture View Models A model is a complete, simplified description of a system from a particular perspective or viewpoint. There is no single view.
Enterprise Engineering Directorate (EE)
XASTRO-2 Presentation CCSDS SAWG th November 2004.
VirtualWorks Format and Objectives The engineering process of VirtualWorks encompasses a set of functions to build a software system in line with the.
ANALYSIS PHASE OF BUSINESS SYSTEM DEVELOPMENT METHODOLOGY.
21/1/ Analysis - Model of real-world situation - What ? System Design - Overall architecture (sub-systems) Object Design - Refinement of Design.
Viewpoint Modeling and Model Based Web App Generation for Systems Engineers Document Generation and Scalable Model Based Engineering Christopher Delp NASA/Caltech.
Enterprise Architectures. Core Concepts Key Learning Points: This chapter will help you to answer the following questions: What are the ADM phase names.
Architecture Ecosystem SIG March 2010 Update Jacksonville FL.
System Modeling Assessment & Roadmap WG Meeting Boston, MA June 17, 2014 Eldad Palachi Sandy Friedenthal.
® 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.
1 Copyright © 2013 by Lockheed Martin Corporation 8/1/2013 John Watson Lockheed Martin Document Definition and Generation within a SysML Model.
Architecture for View Modeling in SysML Auto-View Generation Working Group Lead: Christopher Delp NASA JPL.
MSG-085 2RS Common Interest Group SINEX OVERVIEW
SysML v2 Model Interoperability & Standard API Requirements Axel Reichwein Consultant, Koneksys December 10, 2015.
Model Based Engineering Environment Christopher Delp NASA/Caltech Jet Propulsion Laboratory.
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.
1 The XMSF Profile Overlay to the FEDEP Dr. Katherine L. Morse, SAIC Mr. Robert Lutz, JHU APL
CIS 375 Bruce R. Maxim UM-Dearborn
Interface Concepts Modeling Core Team
Discussion Topics for Exploring OMG UPDM Way-ahead
Integrating MBSE into a Multi-Disciplinary Engineering Environment A Software Engineering Perspective Mark Hoffman 20 June 2011 Copyright © 2011 by Lockheed.
Overview of MDM Site Hub
SysML v2 Formalism: Requirements & Benefits
Computer Aided Software Engineering (CASE)
Proposed SysML v2 Submission Plan
System Modeling Assessment & Roadmap Joint OMG/INCOSE Working Group
UML profiles.
NIEM Tool Strategy Next Steps for Movement
Status of SysML v2 Planning & Requirements
Presentation transcript:

Viewpoint Modeling and Model-Based Media Generation for Systems Engineers Automatic View and Document Generation for Scalable Model- Based Engineering Christopher Delp NASA/Caltech Jet Propulsion Laboratory Chair: SysML 1.4 RTF Auto-View Generation Working Group

Useful Links Auto-View Generation Working Group – autoview:auto-view_generation_working_group

Outline Auto-View Working Group Background First Phase of Effort Plan Forward Summary

AUTO-VIEW GENRATION WORKING GROUP Purpose and Objectives

Purpose of Presentation Review and obtain feedback on preliminary AVGWG work products – Concepts – Requirements – Use cases Describe issues Next steps – Evaluate and propose solutions

Auto-View Working Group Need: – Capability to generate views of the modeling information based on specified viewpoints. These views may include presentation of the information in multiple formats such as diagrams, tables, and entire documents. Goals: – Establish a standardized approach for generating views from the models leveraging current practices where practical. The intent is to enable SysML tool vendors to support view generation in a more standard way. Objectives: – Define the changes needed to SysML to enable automated document and view generation from a SysML model and related external artifacts based primarily on refinements to the view and viewpoint concepts in SysML. Note: this work group began as part of the SysML 1.4 Revision Task Force (RTF), but this site is being maintained under the OMG SysML™ Project Portal. This enables additional participants, and also provides visibility to activities outside the scope of this RTF.

Scope Identify requirements Potential solutions Identify changes within the scope of the SysML v1.4 RTF Identify changes that are out of scope of the SysML v1.4 RTF. – identify broader stakeholder participation to develop a roadmap on how to move forward with the changes outside of this RTF.

Deliverables Issue identification 4 issues identified Requirements Set of draft requirements documented Summary of current solutions refer to SE DSIG on June 19, 2012 as a starting point and add as required  Proposed solution to the above issue  should include actual specification changes including new stereotypes, model libraries, and examples  Prototype application of this solution  auto-generate the SysML v1.4 specification

BACKGROUND Document generation across industry

Background At the SE DSIG meeting on June 18, 2012 in Cambridge, several individuals presented and demonstrated practices for view generation from the model that are now in common use. Refer to the meeting minutes and presentations in the Cambridge SE DSIG meeting page. This working group was formed as a follow-up action from this meeting.Cambridge SE DSIG meeting page.

Auto-View Generation Approaches Across Industry ESO MBDG Open Source Docgen JPL MBEE (Docgen, Docweb, View Editor, System Database) Lockheed Martin DocGen Atos Gendoc

Common Features Across Industry A need to communicate with stakeholders – According to terms of the stakeholders Variety of representations Edit the Model Information through multiple UI Enterprise integration of multiple applications and modeling tools

CONCEPTS REQUIREMENTS AND USECASES First Phase of Effort

Communication as a Principle Communicating through understanding point of view – Understanding the Point of View of Stakeholders Concerns – Describing the model from that Point of View Identifying parts of the model that address concerns – Telling the story of the Views Linearization of the Views of the Model

Engineer “The glass is twice as big as it needs to be”

View and Viewpoint Update 3/2/13

Generating Reports from Models Document Generator 17 Model, Viewpoints and View Models Reports output using styles and formats specified in the method Model Repository Document Repository Model Editing Tool Web –based Model Editors Model transformation from SysML to Documents (HTML, PDF etc)

Types of Requirements Analysis Architecture Framework Extensibility Configuration Management Conformance Diagram Views Dynamic Views Editability Executable Independence Inclusion Interoperability Method Separation of Models Styles Tool Independence Viewpoint Model

Use Cases

EXAMPLE USECASES

Lockheed Example Usecase

Features & Capabilities Recursive Document Structure Modeling – Define the recursive document structure – Define the loop using «startLoop» and «closeLoop» dependencies – Define the data sets used in this structure – Reference the data sets using «referenceTo»

Features & Capabilities Scope Query

Document Preview and Validation Document Preview Document Preview Component Preview Component Preview View the list of ≪ dataReference ≫ objects and their data Extract valid property names to Excel spreadsheet Create a file to schedule an autorun Validation Logs

ESO Example Usecase

JPL Example Usecase

Building the Viewpoint Model Viewpoint Model – Purpose informed by Stakeholder Concerns – Methods and Analysis for constructing the View from the Model – Presentation Rules

Method and Analysis Methods – Ordered steps for producing the View Analysis – describe the nature of queries of the model – Analytical assertions – Rules for completeness and consistency Format and Presentation Style – Describe the conventions styles and formats for how the information is presented in the View

Viewpoint and View

Views of Models

Simple Spacecraft Diagram Views Spacecraft SysML IBD Star Tracker Behavior Scenario Spacecraft Star tracker Behavior

Linearizing the Views Model of Views – Story of Views – Outline of Views – Template Outline of Viewpoints “Template” Outline of Viewpoints 2 Model Outlines of Views based on the same Viewpoint Template

Libraries Viewpoints – Collections of standard representations Methods – Reusable methods for producing different models and representations used in Views Analyses – Libraries of model analyses, queries and rules for checking models Presentation Styles – Styles for presenting models and data such as colors, layout schemes, and conventions Format – Models for formatting information such as Docbook, Office Schemas and modeling languages

ISSUES View Modeling

View and Viewpoint Limitations Issue Viewpoint method limitations Viewpoint description limitations View import limitations Other view construction limitations

View and Viewpoint Issues

Model Issues

PLAN FORWARD

Plan Forward Form and Scope Working Group Define Requirements Define Usecases Articulate issues  Propose Solutions

SUMMARY

Summary Critical capability for industry Synthesized Industry Innovation Concept Requirements Usecases Submitted 1.4 RTF Issues  Working Solutions

BACKUP

Information Rendered According to Viewpoints Domain Specific Modeling Applications Document and Report Generation Web Editable View Apps CAD (Mechanical, Electrical etc) Software Design (UML etc) MBSE (SysML etc) Analysis (Analytic, Simulation, spreadsheet) Production Models Viewpoints and Domain Specific Languages Model Repository Viewpoints For Domain specific Apps Web- editable Viewpoints Final products rendered according to Viewpoints and Models