1 / 18

Model Driven Development with Ada

Edmund Mayer I-Logix, Inc. 17 November 2004. Model Driven Development with Ada. Document Driven Approach. System Acceptance. Requirements Capture & Analysis. Requirements Document. Systems Analysis & Design. (Sub-)System Integration & Test. HW/SW Design Document. Module

kina
Télécharger la présentation

Model Driven Development with Ada

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. Edmund Mayer I-Logix, Inc. 17 November 2004 Model Driven Development with Ada

  2. Document Driven Approach System Acceptance RequirementsCapture & Analysis Requirements Document Systems Analysis & Design (Sub-)System Integration & Test HW/SW Design Document Module Integration & Test SW Design .exe .doc .exe .doc SW Design Specification SW Implementation & Unit Test

  3. Model Driven Approach

  4. UML Execution on Host and Target

  5. UML 2.0 Diagrams Activity Diagrams Package Diagrams Class Diagrams Structure Diagrams State Machine Diagrams Object Diagrams Behavioral Diagrams Structural Diagrams Deployment Diagrams Use Case Diagrams Interaction Diagrams Timing Diagrams Component Diagrams Communication Diagrams Sequence Diagrams Interaction Diagrams

  6. Use Case Diagram This diagram shows what the system does and who uses it.

  7. Detailing Use Cases: Activity Diagram Starting Point Activity Swimlane Ending Point Used to describe behaviour for operations, classes or use cases. As soon as one activity finishes the next one starts.

  8. Sequence Diagram Sequence Diagrams show how instances communicate over time.

  9. Class and Object Diagrams Provide a structural view of the system

  10. State Machine Diagram Trigger Exit action Entry action State machines are used when we need to wait until something happens before going to a different state.

  11. Structure Diagram This diagram shows the internal structure of classes.

  12. Deployment Diagram

  13. One Model, Many Views A Class Diagram A Sequence Diagram Another Class Diagram A Use Case Diagram Source Code Code Gen The Model An Activity Diagram Roundtrip A Deployment Diagram A State Machine Modeling Tool Browser

  14. Code Generation from Model SourceCode The Model

  15. Mapping Model to Code using Rules UML meta-types Script categories for selected type Source code preview Script content Scripts for selected type

  16. Platform Independent Modeling Platform Independent Model Platform Independent Model Generated Code External Code Object Execution Framework Virtual Machine Platform (Hardware, Operating System) Platform (Hardware, Operating System) • A virtual machine or execution framework abstracts the platform, and is defined as a set of parts and services (communications, scheduling, naming, etc.), which are defined independently of any specific platform and which are realized in platform-specific ways on different platforms

  17. Reusing Legacy Code Legacy Code The Model

  18. end Model_Driven_Development_with_Ada;

More Related