We think you have liked this presentation. If you wish to download it, please recommend it to your friends in any social system. Share buttons are a little bit lower. Thank you!
Presentation is loading. Please wait.
Published byCarmella Webster
Modified about 1 year ago
SysML in META Greg Eakman, Ph.D. BAE Systems V 1.2 7/7/2011
SysML in META Model-driven systems engineering * Capture of vehicle Reference Architecture Capture of requirements and mapping to abstract architecture -* Map requirements onto components and attributes -Use of parametrics-like capability to define constraints for component selection -* Domain specific language based on SysML * Front end to AMIL – transform SysML elements to AMIL Definition of CML meta model and CML contents -Use SysML to generate CML schema Framework for test case design, automated test case generation -Model environmental components Feedback to user -Display of component PCCs within Reference Architecture views -Show selections from CML March 2011 © BAE Systems All rights reserved. See title page for handling instructions. 2 * Target for July demo
Vehicle Reference Architecture Model the invariants of ground vehicles No need to start from scratch for every new vehicle Account for commonalities, variabilities (product line concepts) Map requirements onto architecture Captures relationships from all viewpoints With behavioral component models, requirements become executable Use as a framework for early requirements analysis -Identified as key time sink as customer may change mind, or does not understand conflicting or unfeasible requirements. March 2011 © BAE Systems All rights reserved. See title page for handling instructions. 3 Thermodynamic view Power view
Reference Architecture Data Partitions Vehicle reference architecture -Invariant model of a generic ground vehicle Instance specific requirements and constraints -Vehicle specific that drive choices within the framework of the architecture Component Model Library (CML) -Abstract components -Detailed component info from all viewpoints -Operational limits, parameters, interfaces, behaviors -Equations and executable models that can plug into a hybrid, distributed, simulation framework like HLA. Integration patterns: Patterns for connecting components -Eg. Brake pedal to brakes -Hydraulics -Electrical sensor on pedal, networked to actuator on brakes AMIL Output – component selections and interconnections March 2011 © BAE Systems All rights reserved. See title page for handling instructions. 4
March 2011 © BAE Systems All rights reserved. See title page for handling instructions. 5
Vehicle Chassis Reference Architecture March 2011 © BAE Systems All rights reserved. See title page for handling instructions. 6
EntryWay Reference Architecture* March 2011 © BAE Systems All rights reserved. See title page for handling instructions. 7 * Images used without permission
Analysis of Alternatives (AoA) META should support the AoA for components All requirements flow to each alternative A component may have many alternatives AMIL and its components, and simulations and results, help select best alternative March 2011 © BAE Systems All rights reserved. See title page for handling instructions. 8 EntryWay1: Hatch orientation: az=0, el=90 opening.area=5.25 sq ft EntryWay2: Door orientation: az=90, el=0 opening.area=15 sq ft
AoA (2) March 2011 © BAE Systems All rights reserved. See title page for handling instructions. 9 AutoSelect
Component and Interfaces Components have interfaces in multiple viewpoints -Eg. Power, therodynamic, mechanical, structural, … All viewpoints must eventually be accounted for -Many may be defaulted/ignored during early design stages Interfaces (SysML ports) define connection/interaction points -With other components of the system -With the environment Connection with CML March 2011 © BAE Systems All rights reserved. See title page for handling instructions. 10
Domain Specific Language for Vehicle Requirements Define new component types -Attributes -Interfaces Insert components into architecture Attributes optionally filled in, or unspecified Interfaces connected or free Connection patterns New viewpoints Components viewed on multiple diagrams Connect new component types with CML March 2011 © BAE Systems All rights reserved. See title page for handling instructions. 11
Modeling with the RA The Reference Architecture is a starting place for defining a component -Describes all the possible configurations -Modeling documents the requirements and design choices to select one configuration of components RA defines a meta-model for a component The model defines a specific configuration of block instances, links, and properties March 2011 © BAE Systems All rights reserved. See title page for handling instructions. 12
Mapping Requirements to the RA General requirements are mapped to reference architecture meta-model components. Eg. Safety requirements Specific requirements are mapped to block instances in the model The effects of requirements on block properties are captured in a dialog March 2011 © BAE Systems All rights reserved. See title page for handling instructions. 13
Modeling with the RA Sometimes the model becomes normative -expressing the requirement directly March 2011 © BAE Systems All rights reserved. See title page for handling instructions. 14 The ramp motor shall have two operating switches, one by the driver and one in the cargo bay
META Reference Architecture Meta-model Architectural model consists of -Components -Attributes -Interfaces Create ground vehicle requirements domain specific language based on SysML March 2011 © BAE Systems All rights reserved. See title page for handling instructions. 15
SysML for Test Case Design Framework Quantitative Qualitative Selection of system and environmental components and input parameter models March 2011 © BAE Systems All rights reserved. See title page for handling instructions. 16
Quantitative Simulation Environment Cannot remove quantitative, monte carlo sims from process -Can use it more efficiently with input from qualitative sim Distributed, cloud-based Component behaviors “plug-in” to simulation bus Scalable -Hardware in the loop -Human in the loop -Training Existing frameworks already exist, eg. HLA Environmental components are just like system components March 2011 © BAE Systems All rights reserved. See title page for handling instructions. 17
Relation of Qualitative and Quantitative Simulation Qualitative sim finds possible reachable states of a component -Some may not be reachable in the system due to input bindings Use quantitative to verify qualitative results Fault injection -Initialize component into bad state identified by qualitative simulation -Determine how the rest of the system responds -Needed because qualitative simulations are not composable, and defect subcomponent states may be omitted from higher level simulations March 2011 © BAE Systems All rights reserved. See title page for handling instructions. 18
Ground Vehicle Viewpoints March 2011 © BAE Systems All rights reserved. See title page for handling instructions. 19
Reference Architecture Meta Model March 2011 © BAE Systems All rights reserved. See title page for handling instructions. 20
March 2011 © BAE Systems All rights reserved. See title page for handling instructions. 21
Requirements and Test Cases March 2011 © BAE Systems All rights reserved. See title page for handling instructions. 22
Semantic Linking Enables Agile Design, Test, and Diagnosis March 2011 © BAE Systems All rights reserved. See title page for handling instructions. 23 Semantic linkage enables: Thorough exploration of design alternatives with existing design tools Distributed design efforts and crowd sourcing of design alternatives Use of New algorithms (qualitative simulation and reach set analysis) for stress testing and diagnosis revealing design tradeoffs; (On exemplary COA Planning Problem: (est.) run-time compression for the same analysis as compared to traditional stochastic simulator (e.g., OneSAF) Discover & Diagnose Issues Resulting from Design Choices (and Req’ts) Early Software InfrastructureGoal Capability Implements 3 Master Model Qualitative Model Quantitative Model Reach Set Analysis Envisioner Galileo Simulation Compiler Simulation Environment AMIL Service Design Modeling Tools MagicDraw Pro/E MatLab Plug-ins / Wrappers Component Model Library SysML Model / Use Cases Pro/E Model MatLab Model Inform Design
A Systemic Solution to Achieve 5x Reduction In Development Time March 2011 © BAE Systems All rights reserved. See title page for handling instructions. 24 Confidently ID & Eliminate Design Failures in Virtual Environment Before Production ARRoW (Adaptive, Reflexive, Robust Workflow) Early and Continuous Testing, Verification, and Validation Do in Parallel Currently Serial Design Steps -Across design elements -Across levels of abstraction Integrate Existing Design Tools -Detect unwanted interactions “at the seams” early when costs can be minimized Avoid Problems from “Leaky Abstractions” via Design Lookaheads Reveal Important Design Tradeoffs Early -Metrics for Complexity and Adaptability -Algorithms Facilitating Stress Testing of Designs
1/24/11 25 System of Systems!
Course Instructor: Aisha Azeem Architectural Design.
> Power Supervison Desired Output level Source Diesel Valve Sink Diesel Valve > Valve Regulator Sink T = 40 ms Air Valve CBSE Course The SaveComp Component.
Automated Analysis and Code Generation for Domain-Specific Models George Edwards Center for Systems and Software Engineering University of Southern California.
© 2009 Artisan Software Tools. All rights reserved. Testing Solutions with UML/SysML Andrew Stuart, Matthew Hause.
Model-Driven Analysis Frameworks for Embedded Systems George Edwards USC Center for Systems and Software Engineering
Architecture View Models A model is a complete, simplified description of a system from a particular perspective or viewpoint. There is no single view.
Eng. Mohammed Timraz Electronics & Communication Engineer University of Palestine Faculty of Engineering and Urban planning Software Engineering Department.
A common meta-model for the interoperation of tools with heterogeneous data models ECMFA 2010 Third Workshop on Model-Driven Tool & Process Integration.
Analysis Stage (Phase I) The goal: understanding the customer's requirements for a software system. n involves technical staff working with customers n.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 10Slide 1 Architectural Design l Establishing the overall structure of a software system.
Romaric GUILLERM Hamid DEMMOU LAAS-CNRS Nabil SADOU SUPELEC/IETR.
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.
Presented by: Thabet Kacem Spring Outline Contributions Introduction Proposed Approach Related Work Reconception of ADLs XTEAM Tool Chain Discussion.
Chapter 10 Analysis and Design Discipline. 2 Purpose The purpose is to translate the requirements into a specification that describes how to implement.
1 Capturing Requirements As Use Cases To be discussed –Artifacts created in the requirements workflow –Workers participating in the requirements workflow.
Integration of MBSE and Virtual Engineering for Detailed Design Presented by: Akshay Kande Advisor: Dr. Steven Corns Missouri University of Science & Technology.
4.2.1 Programming Models Technology drivers – Node count, scale of parallelism within the node – Heterogeneity – Complex memory hierarchies – Failure rates.
© Drexel University Software Engineering Research Group (SERG) 1 Based on the paper by Philippe Kruchten from Rational Software.
© 2012 xtUML.org Bill Chown – Mentor Graphics Model Driven Engineering.
Modelling Class T08 Conceptual Modelling – Behaviour Flow-Based Behavior References: –Conceptual Modeling of Information Systems (Chapters 11 and 12) –A.
SWE © Solomon Seifu ELABORATION. SWE © Solomon Seifu Lesson 10 Use Case Design.
SAFe Automotive aRchItecture SAFARI. SAFARI_Presentation_Short_v1.ppt 2 / /P. Cuenot/ © Continental AG ARTEMIS/Call2 R&D Project Proposal Project.
Approaching a Problem Where do we start? How do we proceed?
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.
Systems Modeling Language ™ Overview Cris Kobryn and Sandy Friedenthal SysML Partners (www.SysML.org)www.SysML.org October 2003.
Behavioral Design Outline –Design Specification –Behavioral Design –Behavioral Specification –Hardware Description Languages –Behavioral Simulation –Behavioral.
Software Design Deriving a solution which satisfies software requirements.
MODEL-BASED SOFTWARE ARCHITECTURES. Models of software are used in an increasing number of projects to handle the complexity of application domains.
Modelling Class T16: Conceptual Modelling – Architecture Image from
1 The XMSF Profile Overlay to the FEDEP Dr. Katherine L. Morse, SAIC Mr. Robert Lutz, JHU APL
OOD OO Design. OOD-2 OO Development Requirements Use case analysis OO Analysis –Models from the domain and application OO Design –Mapping of model.
Ch:8 Design Concepts S.W Design should have following quality attribute: –Functionality –Usability –Reliability –Performance –Supportability (extensibility,
INCOSE IW12 MBSE Workshop 15 INCOSE (MBSE) Model Based System Engineering Integration and Verification Scenario Ron Williamson, PhD Raytheon
An Introduction to Software Architecture Software Engineering Lab. Summer 2006.
1 CASE Computer Aided Software Engineering. 2 What is CASE ? A good workshop for any craftsperson has three primary characteristics 1.A collection of.
Spectra Software Defined Radio Products Applying Model Driven Design, Generative Programming, and Agile Software Techniques to the SDR Domain OOPSLA '05.
Requirements Analysis Concepts & Principles Instructor: Dr. Jerry Gao.
Systems Architectures System Integration & Architecture.
Model Checking and Model-Based Design Bruce H. Krogh Carnegie Mellon University.
1 FM Overview of Adaptation. 2 FM RAPIDware: Component-Based Design of Adaptive and Dependable Middleware Project Investigators: Philip McKinley, Kurt.
EMEA Beat Schwegler Architect Microsoft EMEA HQ Ingo Rammer Principal Consultant thinktecture
Aurora: A Conceptual Model for Web-content Adaptation to Support the Universal Accessibility of Web-based Services Anita W. Huang, Neel Sundaresan Presented.
Computing and SE II Chapter 9: Design Methods and Design Models Er-Yu Ding Software Institute, NJU.
Unified Modeling (Part I) Overview of UML & Modeling Elizabeth Bigelow Carnegie Mellon University.
11 CORE Architecture Mauro Bruno, Monica Scannapieco, Carlo Vaccari, Giulia Vaste Antonino Virgillito, Diego Zardetto (Istat)
Applying the Human Views for MODAF to the conception of energy-saving work solutions Dr Anne Bruseberg Systems Engineering & Assessment Ltd, UK on behalf.
Rational Unified Process Fundamentals Module 4: Disciplines II.
Ahmed Gamal Ahmed Nile University Bioinformatics Group.
Chapter 10: Architectural Design Presented By: Andy Carroll.
Chapter 9 Architectural Design. Why Architecture? The architecture is not the operational software. Rather, it is a representation that enables a software.
© 2017 SlidePlayer.com Inc. All rights reserved.