UML 2 0 Redux for HPEC Dr Jeffrey

  • Slides: 6
Download presentation
UML 2. 0 Redux for HPEC Dr. Jeffrey E. Smith Mercury Computer Systems, Inc.

UML 2. 0 Redux for HPEC Dr. Jeffrey E. Smith Mercury Computer Systems, Inc. Manfred Koethe 88 solutions Corp. High Performance Embedded Computing (HPEC) Conference September 25, 2003 © 2001 Mercury Computer Systems, Inc.

UML Overview l Visual modeling language w Providing controllable levels of abstraction w Definition

UML Overview l Visual modeling language w Providing controllable levels of abstraction w Definition of static and dynamic model features w Communicating/predicting application design characteristics in domain-terms w Supporting automation of development process w Derived from OMT, Use Case and Booch (Component) methodologies l Dominant modeling language for software architecture “blueprints” State Machines MOF Profiles OCL Structured Classes and Components Activities Interactions Detailed Actions Flows Basic UML (Classes, Basic behavior, Internal structure, Use cases…) UML Infrastructure © 2003 Mercury Computer Systems, Inc. Credit Bran Selic, “An Overview of Model-Driven Development and UML 2. 0” 2

Richer Language Features l Architectural modeling: composition and stronger encapsulation via structured classes w

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

Enhanced Behavioral Modeling Capture Problems at Model Level l Extended sequence diagrams permit more

Enhanced Behavioral Modeling Capture Problems at Model Level l Extended sequence diagrams permit more detailed complex interactions sd ATM-transaction w Supports sub-diagrams w Decomposition of SDL, MSC and LSC messages w Control structures: loop, parallel execution, alternative execution, protected regions, . . . l client: atm: ref Check. Pin alt ref [chk= OK] Do. Transaction error(bad. PIN) Activities permit more flexible parallelism, I/O options and data/control flow modeling w w Petri Net model to derive concurrency Unstructured activities possible Pre/post conditions HPEC features described in HPEC 2001 e. g. interruptible regions and execution ordering © 2003 Mercury Computer Systems, Inc. 4 dbase: insert. Card [else]

Timing and State Modeling l Precise modeling of timing via timing subdiagrams w Previous

Timing and State Modeling l Precise modeling of timing via timing subdiagrams w Previous profile for modeling schedulability, performance and time embedded in UML 2. 0 w Enables next level of integrating hardware modeling to platform design sd Driver. Protocol d : Driver Idle Wait Busy Idle o : Out. Pin 0111 0001 0111 t=0 l t=5 t = 10 t = 15 Statecharts now have sub-statecharts and inheritance © 2003 Mercury Computer Systems, Inc. 5

UML 2. 0 Provides HPEC “Potential” for Software Design Automation l l Action semantics

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