SysML Reference Model Definition Model Based System Development in the Joint Strike Missile project Svein-Erik Søgård KDS/Missile Division.

Slides:



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

Prescriptive Process models
Object-Oriented Software Development CS 3331 Fall 2009.
Virtual University - Human Computer Interaction 1 © Imran Hussain | UMT Imran Hussain University of Management and Technology (UMT) Lecture 16 HCI PROCESS.
PRESENTED BY USHA GHIMIRE. Introduction-The need for MBSE MBSE now and present shortcomings A view of MBSE in the future Key advantages and disadvantages.
Free Mini Course: Applying UML 2.0 with MagicDraw.
Practical Business Modeling in the Unified Process Tom Morgan Software Architect, Fidelity National Information Services
Introduction to Software Engineering Dr. Basem Alkazemi
Requirements Engineering n Elicit requirements from customer  Information and control needs, product function and behavior, overall product performance,
Managing Data Resources
Page 1 Model Based Software Development - a pragmatic view Mikkel Lauritsen Intentia R&D A/S
Introduction to Software Engineering
R R R CSE870: Advanced Software Engineering (Cheng): Intro to Software Engineering1 Advanced Software Engineering Dr. Cheng Overview of Software Engineering.
Creating Architectural Descriptions. Outline Standardizing architectural descriptions: The IEEE has published, “Recommended Practice for Architectural.
171 Use Case Descriptions Chapter 4 – Facade Iteration Initial Requirements (Inception Phase)
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 5 Slide 1 Requirements engineering l The process of establishing the services that the.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 17 Slide 1 Rapid software development.
A Combat Support Agency Defense Information Systems Agency Model Based Systems Engineering and Systems Modeling Language Chris Gedo Chief, Architecture.
Extended Enterprise Architecture Framework (E2AF)
Visualization By: Simon Luangsisombath. Canonical Visualization  Architectural modeling notations are ways to organize information  Canonical notation.
Basic Concepts The Unified Modeling Language (UML) SYSC System Analysis and Design.
Chapter : Software Process
The Software Development Life Cycle: An Overview
Free Mini Course: Applying SysML with MagicDraw
Section 02Systems Documentation1 02 Systems Documentation And Franchise Colleges By MANSHA NAWAZ.
Introduction to RUP Spring Sharif Univ. of Tech.2 Outlines What is RUP? RUP Phases –Inception –Elaboration –Construction –Transition.
Chapter 6 System Engineering - Computer-based system - System engineering process - “Business process” engineering - Product engineering (Source: Pressman,
1 IBM Software Group ® Mastering Object-Oriented Analysis and Design with UML 2.0 Module 1: Best Practices of Software Engineering.
Design Patterns OOD. Course topics Design Principles UML –Class Diagrams –Sequence Diagrams Design Patterns C#,.NET (all the course examples) Design Principles.
Requirements Analysis
-Nikhil Bhatia 28 th October What is RUP? Central Elements of RUP Project Lifecycle Phases Six Engineering Disciplines Three Supporting Disciplines.
Slide 1 Wolfram Höpken RMSIG Reference Model Special Interest Group Second RMSIG Workshop Methodology and Process Wolfram Höpken.
Chapter 4 – Requirements Engineering
1 WEB Engineering Introduction to Electronic Commerce COMM1Q.
1M.Sc.(I.T.), VNSGU, Surat. Structured Analysis Focuses on what system or application is required to do. It does not state how the system should be implement.
Team Skill 6: Building the Right System From Use Cases to Implementation (25)
©Ian Sommerville 2000, Mejia-Alvarez 2009 Slide 1 Software Processes l Coherent sets of activities for specifying, designing, implementing and testing.
Workshop 16: An upward shift in abstraction leads to a corresponding increase in productivity. In the past this has occurred when programming languages.
Effective Requirements Management – an overview Kristian Persson Field Product Manager, Telelogic Asia/Pacific.
User Interface Structure Design Chapter 11. Key Definitions The user interface defines how the system will interact with external entities The system.
Slide 1 Chapter 11 User Interface Structure Design Chapter 11 Alan Dennis, Barbara Wixom, and David Tegarden John Wiley & Sons, Inc. Slides by Fred Niederman.
Dr. Darius Silingas | No Magic, Inc. Domain-Specific Profiles for Your UML Tool Building DSL Environments with MagicDraw UML.
 The need for a formal methodology description  SPEM for describing an agent oriented methodology  PASSI: an example  The needed extension  Discussion.
Introduction To Engineering Bike Lab 1 – 4 Report Agenda: Lab Report Format Team Writing Outline Lab 1 Report.
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.
Cmpe 589 Spring 2006 Lecture 2. Software Engineering Definition –A strategy for producing high quality software.
Process Improvement. It is not necessary to change. Survival is not mandatory. »W. Edwards Deming.
Enterprise Engineering Directorate (EE)
©Ian Sommerville 2006Software Engineering, 8th edition. Chapter 4 Slide 1 Software Processes.
Requirements Analysis
From Use Cases to Implementation 1. Structural and Behavioral Aspects of Collaborations  Two aspects of Collaborations Structural – specifies the static.
INCOSE IW12 MBSE Workshop 15 INCOSE (MBSE) Model Based System Engineering Integration and Verification Scenario Ron Williamson, PhD Raytheon
Model Based Systems Engineering Visualization Steven Corns Missouri University of Science & Technology.
International Workshop Jan 21– 24, 2012 Jacksonville, Fl USA INCOSE IW 2012 MBSE Requirement Flowdown Workshop - Outbrief - John C. Watson Principal Member.
Systems Engineering Concept Model (SECM) Status 03/17/2016 John Watson.
OBJECT ORIENTED VS STRUCTURED WHICH ONE IS YOUR CHOICE.
From Use Cases to Implementation 1. Mapping Requirements Directly to Design and Code  For many, if not most, of our requirements it is relatively easy.
CHESS Methodology and Tool Federico Ciccozzi MBEES Meeting Sälen, January 2011 January 2011.
Slide 1 Wolfram Höpken RMSIG Reference Model Special Interest Group Wolfram Höpken IFITT RMSIG.
Advanced Software Engineering Dr. Cheng
Model-based design inspection based on traceability information models and design slicing Shiva Nejati April 15, 2015.
Unified Process Source & Courtesy: Jing Zou.
Module: Software Engineering of Web Applications
Chapter 13 Logical Architecture.
Introduction to SysML v.2.0 Metamodel (KerML)
© 2018 Lockheed Martin Corporation
Object oriented analysis and design
Chapter 13 Logical Architecture.
Module: Software Engineering of Web Applications
Presentation transcript:

SysML Reference Model Definition Model Based System Development in the Joint Strike Missile project Svein-Erik Søgård KDS/Missile Division

Agenda Introduction –Background –Goals for modeling –Challenges Model definition –Principles –Walktrough of process and reference model Summary –Lessons learned 27/10/2015Page 2WORLD CLASS - through people, technology and dedication.

Background Main motivation for MBSE in JSM –Lack of system and architecture level documentation in previous projects Many documents and model fragments but not up to date, poor value for money (waste), not systematically organized). Very hard for –Maintainability –Introducing new developers –Doing analysis (e.g. safety) –Initiative from Management (LEAN thinking) as well as a JSM core team of developers that would do it better 27/10/2015Page 3WORLD CLASS - through people, technology and dedication.

Background KDS Survey that concluded with SysML and MagicDraw™ modeling tool –Major player in MBSE –Simultaneously evaluated UML tool for SW modeling –smooth transition to SW development was important JSM project main focus so far on functional analysis & design, but also physical architecture is addressed MagicDraw™ is NOT «THE System Tool» –Used in conjunction with other tools –Information management Linking other documentation rather than duplicating it 27/10/2015Page 4WORLD CLASS - through people, technology and dedication.

Goals «Real» Model Based, –Not only drawings and model fragments –Consistent model with a set of well defined views System Model (SysML) characteristics –Complete functional description (concise, right abstraction level) focused on what the system shall do. Easy entry point to what the system shall do and how it works –Physical System Architecture that is precise and detailed about interfaces at different levels (How the system shall be constructed) –Specifications for component design (in other disciplines: SW, PLD electronics, mechanics) –Focus on maintainability (of the model and the product) 27/10/2015Page 5WORLD CLASS - through people, technology and dedication.

Challenges Project size (JSM) is too large to be optimal –“How to do” established later than desirable –doing development and establishing how to model in parallell –Too few resources to follow up new teams Culture (document centric, different philosophy & terminology) –Commitment to the process and methodology Commitment from engineers are even more important than commitment from management –developers tend to fall back to «their old methods» when they get pressed for time SysML is a complex language. Requires time to understand what to use and how to use it to make consistent models. 27/10/2015Page 6WORLD CLASS - through people, technology and dedication.

Reference Model Definition Motivation: SysML is a (too) complex language – we need to define which subset to use and how Steps: –Defined Modeling Process –Defined reference model Subset of SysML (elements and diagrams) Define metamodel of how model elements are related Model organization (views/perspectives) –Tools customization Profile (extension with DSL) Diagram Customization Validation rules 27/10/2015Page 7WORLD CLASS - through people, technology and dedication.

Reference Model Definition Basic Principles –Avoid redundancy and duplication of information –Be very clear about the different abstraction levels (hard!) –Shall not cover all details nor repeat or duplicate information from other tools (link in instead) 27/10/2015Page 8WORLD CLASS - through people, technology and dedication.

Reference Model Definition Process modeled using SysML Activity Diagrams Walkthrough (HTML generated from MagicDraw™) 27/10/2015Page 9WORLD CLASS - through people, technology and dedication.

Summary MUST make a standardization of modeling to make a maintainable model –Do systematic stakeholder analysis –Reference model, guidelines –Tools customization Customized to process and modeling style Suite of validation rules Build up a core team that is skilled before rolling it out –Use consultancy –Do peer modeling –Both SysML and tools experience required 27/10/2015Page 10WORLD CLASS - through people, technology and dedication.

Summary If possible – select a small project (but not too small) and cover all phases/aspects before rolling it out in large scale Do not try to cover all aspects of system engineering/modeling from the start (eat the elephant piece by piece) Be aware on separating between “throw-away” models and maintainable models –«less is more» 27/10/2015Page 11WORLD CLASS - through people, technology and dedication.

kongsberg.com