Model Driven Development with Rhapsody By Will Fritz.

Slides:



Advertisements
Similar presentations
Using MapuSoft Instead of OS Vendor’s Simulators.
Advertisements

SWE 316: Software Design and Architecture Objectives Lecture # 23 Software Reengineering SWE 316: Software Design and Architecture  To describe the activities.
Telelogic Lifecycle Solutions Connecting People, Process, and Tools
Lockheed Martin Aeronautics Company © 2001 Lockheed Martin Corporation F-16 Modular Mission Computer Application Software Achieving Cross-Platform Compatibility.
COM vs. CORBA.
Lockheed Martin Aeronautics Company © 2001 Lockheed Martin Corporation F-16 Modular Mission Computer Application Software Achieving Cross-Platform Compatibility.
Software Architecture Frameworks A Family of Implementations Nikunj Mehta Computer Science Department University of Southern California Los Angeles, CA.
Enterprise Application Integration (EAI). Overview  What is EAI?  Advantages/Disadvantages  Problems  Software Options.
CS487 Software Engineering Omar Aldawud
Chapter 22 UML Tooks and UML as Blueprint Model-Driven Architecture (MDA) Object-Constraint Language (OCL)
MDA > Model Driven Architecture > Orçun Dayıbaş > December, 2006 > METU, Ankara.
Amit, Keyur, Sabhay and Saleh Model Driven Architecture in the Enterprise.
7 July 2003 MDA presentation Dennis Wagelaar 1 Model-Driven Architecture The current state of affairs.
Model Driven Architecture (MDA) Partha Kuchana. Agenda What is MDA Modeling Approaches MDA in a NutShell MDA Models SDLC MDA Models (an Example) MDA -
Executable UML By Luca Pellicoro. Definitions Acronym: xtUML or xUML Technology where models (such as state diagrams and class diagrams) are automatically.
CS 290C: Formal Models for Web Software Lecture 6: Model Driven Development for Web Software with WebML Instructor: Tevfik Bultan.
Chapter 1 The Systems Development Environment Modern Systems Analysis and Design Sixth Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich.
Chapter 1 The Systems Development Environment
- Chaitanya Krishna Pappala Enterprise Architect- a tool for Business process modelling.
 1. Introduction  2. Development Life-Cycle  3. Current Component Technologies  4. Component Quality Assurance  5. Advantages and Disadvantages.
Software Reuse Course: # The Johns-Hopkins University Montgomery County Campus Fall 2000 Lecture # 1 - September 7, 2004.
Configuration Management System
MDA Guide Version CYT. 2 Outline OMG Vision and Process Introduction to MDA How is MDA Used? MDA Transformations Other MDA Capabilities Using the.
Chapter 1 The Systems Development Environment
© 2006 ITT Educational Services Inc. SE350 System Analysis for Software Engineers Unit 11 Slide 1 Chapter 1 The Systems Development Environment.
COM vs. CORBA Computer Science at Azusa Pacific University September 19, 2015 Azusa Pacific University, Azusa, CA 91702, Tel: (800) Department.
Chapter 1 The Systems Development Environment Modern Systems Analysis and Design Sixth Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich.
3 April SOA: Services Oriented Architecture MDA: Model Driven Architecture.
Test Driven Development in the.Net Framework Sam Lee Mayur Mehta Jaymeen Shah McCoy College of Business Administration Texas State University-San Marcos.
I n t e g r i t y - S e r v i c e - E x c e l l e n c e UPDM Review Session Col. Jack Jibilian Enterprise Architecting & Warfighting Decision Support SAF/XCPA.
BLU-ICE and the Distributed Control System Constraints for Software Development Strategies Timothy M. McPhillips Stanford Synchrotron Radiation Laboratory.
Wind River Simics: A Simulation Environment for Research and Development Abhinav Srivastava QUARBZ.
Chapter 1 The Systems Development Environment Modern Systems Analysis and Design Sixth Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich.
WSMX Execution Semantics Executable Software Specification Eyal Oren DERI
University of Southern California Center for Systems and Software Engineering Model-Based Software Engineering Supannika Koolmanojwong Spring 2013.
© 2012 xtUML.org Bill Chown – Mentor Graphics Model Driven Engineering.
Model Driven Development An introduction. Overview Using Models Using Models in Software Feasibility of MDA MDA Technologies The Unified Modeling Language.
Slide title In CAPITALS 50 pt Slide subtitle 32 pt Model based development for the RUNES component middleware platform Gabor Batori
A Static Approach to Consistency Verification of UML Models Andrea Baruzzo Department of Computer Science University of Udine MoDeV.
By Garrett Kelly. 3 types or reasons for distributed applications Data Data used by the application is distributed Computation Computation is distributed.
Unified Modeling Language* Keng Siau University of Nebraska-Lincoln *Adapted from “Software Architecture and the UML” by Grady Booch.
HRL © 2009 IBM Corporation Model-Driven Product-Lines for Embedded Software and for Supply-Chain Companies Tali Yatzkar-Haham Julia Rubin,
2006 Chapter-1 L1: "Embedded Systems - Architecture, Programming and Design", Raj Kamal, Publs.: McGraw-Hill, Inc. 1 Introduction to Embedded Systems.
Compilers for Embedded Systems Ram, Vasanth, and VJ Instructor : Dr. Edwin Sha Synthesis and Optimization of High-Performance Systems.
 Some Terms To Know  Definition and Good Process  Models  History  Advantages and Disadvantages  Standardization  Industry Specific Usage  Current.
Experiences from Representing Software Architecture in a Large Industrial Project Using Model Driven Development Andres Mattsson 1 Björn Lundell 2 Brian.
An Introduction to SysML
Source Mastering UML with Rational Rose 2002 Information System Engineering Introduction to UML.
Scientific Programmes Committee Centre for Aerospace Systems Design & Engineering Amitay Isaacs Department of Aerospace Engineering Indian Institute of.
© 2013, published by Flat World Knowledge Chapter 10 Understanding Software: A Primer for Managers 10-1.
Author Software Engineering Institute
Source Mastering UML with Rational Rose 2002 Information System Engineering Introduction to UML.
Yu, et al.’s “A Model-Driven Development Framework for Enterprise Web Services” In proceedings of the 10 th IEEE Intl Enterprise Distributed Object Computing.
From Use Cases to Implementation 1. Structural and Behavioral Aspects of Collaborations  Two aspects of Collaborations Structural – specifies the static.
 Can access all API’s made available by OS vendor.  SDK’s are platform-specific.  Each mobile OS comes with its own unique tools and GUI toolkit.
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.
Dr D. Greer, Queens University Belfast ) Software Engineering Chapter 7 Software Architectural Design Learning Outcomes Understand.
Chapter 5 – System Modeling Lecture 1 1Chapter 5 System modeling.
Status of SysML v2 Planning & Requirements Berlin, Germany June 16, roadmap:sysml_assessment_and_roadmap_working_group.
Modelowanie i analiza systemów informacyjnych Model Driven Architecture Marek Bazan Marzec 2017.
Model-Driven Approach
What is Wrong with Models?
Microprocessor and Assembly Language
Component Based Software Engineering
Component-Based Software Engineering: Technologies, Development Frameworks, and Quality Assurance Schemes X. Cai, M. R. Lyu, K.F. Wong, R. Ko.
Interpreter Style Examples
UML profiles.
Artisan Software Tools A Pragmatic Approach Using Ada and UML
Status of SysML v2 Planning & Requirements
Presentation transcript:

Model Driven Development with Rhapsody By Will Fritz

What is Model Driven Development? A method for producing software quickly, efficiently, and with as little cost as possible. A method for producing software quickly, efficiently, and with as little cost as possible. Based around generating code directly from UML or other modeling languages. Based around generating code directly from UML or other modeling languages.

Why use Model Driven Development? MDD allows for easier building and maintenance of complex state machines than direct work with code. MDD allows for easier building and maintenance of complex state machines than direct work with code. Many embedded systems have too many states to keep straight easily through standard development methods Many embedded systems have too many states to keep straight easily through standard development methods

Why use MDD (cont.) With quality MDD tools, systems can be maintained wholly through their state diagrams and other models. With quality MDD tools, systems can be maintained wholly through their state diagrams and other models.

Advantages of MDD There are many advantages to using model driven development. There are many advantages to using model driven development. “By using models, software engineers and other stakeholders are able to argue conceptually about a problem without worrying about syntax or other platform specific issues.”[4] “By using models, software engineers and other stakeholders are able to argue conceptually about a problem without worrying about syntax or other platform specific issues.”[4]

Advantages of MDD (cont.) The added ease of communication can lead to fast design times. The added ease of communication can lead to fast design times.

System independence System can be designed with very little information about final platform. System can be designed with very little information about final platform. MDD emphasizes building system independent models, then applying model transformations to make it fit the target system. MDD emphasizes building system independent models, then applying model transformations to make it fit the target system. This leads to better portability for the system. This leads to better portability for the system.

Rhapsody Rhapsody is a MDD tool from Telelogic. Rhapsody is a MDD tool from Telelogic. It currently supports final code generation into Ada, C, C++, and Java. It currently supports final code generation into Ada, C, C++, and Java. It also supports 8, 16, 32, and 64 bit systems. It also supports 8, 16, 32, and 64 bit systems.

Rhapsody (cont.) Rhapsody can run simulations of the designed system. Rhapsody can run simulations of the designed system. It can also run debugging on the target hardware. It can also run debugging on the target hardware. Lastly it includes support for built in requirements and model based testing. Lastly it includes support for built in requirements and model based testing.

Standards CORBA: Common Object Request Broker Architecture CORBA: Common Object Request Broker Architecture D0-178B D0-178B UML UML SysML SysML DoDAF: Department of Defense Architecture Framework DoDAF: Department of Defense Architecture Framework AUTOSAR: soon AUTOSAR: soon

Rhapsody Animator Rhapsody has a debugging tool called the Animator. It shows the current state of the simulation within the diagrams. Rhapsody has a debugging tool called the Animator. It shows the current state of the simulation within the diagrams.

Rhapsody Animator

Target Debugging with Tornado When used for target debugging along with the Tornado IDE Rhapsody is able to show the status of the system in diagrams via the animator while target debugging. When used for target debugging along with the Tornado IDE Rhapsody is able to show the status of the system in diagrams via the animator while target debugging.

Customers Airbus Airbus Boeing Boeing Hamilton Sunstrand Hamilton Sunstrand Lockheed Martin Lockheed Martin Smiths Aerospace Smiths Aerospace Ford Ford Mazda Mazda Mitsubishi Mitsubishi CISCO CISCO Motorola Motorola Nokia Nokia Panasonic Panasonic Sony Electronics Sony Electronics 3Com 3Com Medtronic Medtronic HP HP Intel Intel Trane Trane

Trane Example Used to design software for new high- efficiency water chiller Used to design software for new high- efficiency water chiller Project went from blackboard to testing in three months Project went from blackboard to testing in three months Manager of SE Pat Wilson marked that as very fast for that type of project Manager of SE Pat Wilson marked that as very fast for that type of project

References [1] Hofstader, Joseph; Building Distributed Applications Model-Driven Development, us/library/aa964145(d=printer).aspx [1] Hofstader, Joseph; Building Distributed Applications Model-Driven Development, us/library/aa964145(d=printer).aspx us/library/aa964145(d=printer).aspx us/library/aa964145(d=printer).aspx [2] Mellor, S., Scott, K., Uhl, A. and Weise, D. MDA Distelled; Principles of Model-Driven Architecture, Addison Wesley, [2] Mellor, S., Scott, K., Uhl, A. and Weise, D. MDA Distelled; Principles of Model-Driven Architecture, Addison Wesley, [3] Rutherford, Matthew J. and Wolf, Alexander L.; A Case for Test-Code Generation in Model-Driven Systems, Springer-Verlag Berlin Heidelberg, 2003 [3] Rutherford, Matthew J. and Wolf, Alexander L.; A Case for Test-Code Generation in Model-Driven Systems, Springer-Verlag Berlin Heidelberg, 2003 [4] Bull, R. Ian; Integrating Dynamic Views Using Model Driven Development, 2006 [4] Bull, R. Ian; Integrating Dynamic Views Using Model Driven Development, 2006