1 / 6

UML 2.0 Redux for HPEC

Explore the features of UML 2.0 for High Performance Embedded Computing (HPEC), including architectural modeling, enhanced behavioral modeling, timing and state modeling, and the potential for software design automation.

ptoole
Download Presentation

UML 2.0 Redux for HPEC

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. UML 2.0 Redux for HPEC Dr. Jeffrey E. Smith Mercury Computer Systems, Inc. Manfred Koethe 88solutions Corp. High Performance Embedded Computing (HPEC) ConferenceSeptember 25, 2003

  2. MOF Profiles OCL StateMachines StructuredClasses andComponents Activities Interactions DetailedActions Flows Basic UML(Classes, Basic behavior, Internal structure, Use cases…) UML Infrastructure UML Overview • Visual modeling language • Providing controllable levels of abstraction • Definition of static and dynamic model features • Communicating/predicting application design characteristics in domain-terms • Supporting automation of development process • Derived from OMT, Use Case and Booch (Component) methodologies • Dominant modeling language for software architecture “blueprints” Credit Bran Selic, “An Overview of Model-Driven Development and UML 2.0”

  3. A B Richer Language Features • Architectural modeling: composition and stronger encapsulation via structured classes • Components model internal structure, required interfaces and support deployment • Ports connect class interfaces toenvironment • Protocol definable on connection • Data or control flow • Deeper profile extension mechanism (than stereotypes, tags and constraints) with UML meta-model extensions • P latform-specific terminology, UML symbols and semantics • Full integration with MOF providing tool integration

  4. sd ATM-transaction client: atm: dbase: insertCard ref CheckPin alt [chk= OK] ref DoTransaction error(badPIN) [else] Enhanced Behavioral Modeling Capture Problems at Model Level • Extended sequence diagrams permit more detailed complex interactions • Supports sub-diagrams • Decomposition of SDL, MSC and LSC messages • Control structures: loop, parallel execution, alternative execution,protected regions, ... • Activities permit more flexible parallelism, I/O options and data/control flow modeling • Petri Net model to derive concurrency • Unstructured activities possible • Pre/post conditions • HPEC features described in HPEC 2001 e.g. interruptible regions and executionordering

  5. sd DriverProtocol d : Driver Idle Wait Busy Idle o : OutPin 0111 0111 0011 0001 t = 0 t = 5 t = 10 t = 15 Timing and State Modeling • Precise modeling of timing via timing sub-diagrams • Previous profile for modeling schedulability, performance and time embedded in UML 2.0 • Enables next level of integrating hardware modeling to platform design • Statecharts now have sub-statecharts and inheritance

  6. UML 2.0 Provides HPEC “Potential” for Software Design Automation • Action semantics integrate activities with related low-level actions • There are many methods of UML-based code generation • State translation (I-Logix, Rose RT) • Formal translation (NU research, Telelogix) • Direct template translation (Pathfinder) • MDA-based model execution (Pathfinder, Component-X, 88solutions) • Generate/discover components (PCA) • Low-level data/state flow import (MathWorks) • Informal indirect translation to non-mainstream tools and PGO (HPEC 2000) • Model Integrated Computing (MIC, MOBIES)

More Related