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

2. © 2003 Mercury Computer Systems, Inc. 2 UML Overview l Visual modeling language wProviding controllable levels of abstraction wDefinition of static and dynamic model features wCommunicating/predicting application design characteristics in domain-terms wSupporting automation of development process wDerived from OMT, Use Case and Booch (Component) methodologies l Dominant modeling language for software architecture “blueprints”OCL Basic UML (Classes, Basic behavior, Internal structure, Use cases…) MOFProfiles State Machines Structured Classes and Components ActivitiesInteractions Detailed Actions Flows UML Infrastructure Credit Bran Selic, “An Overview of Model-Driven Development and UML 2.0”

3. © 2003 Mercury Computer Systems, Inc. 3 Richer Language Features l Architectural modeling: composition and stronger encapsulation via structured classes wComponents model internal structure, required interfaces and support deployment wPorts connect class interfaces to environment wProtocol definable on connection wData or control flow l Deeper profile extension mechanism (than stereotypes, tags and constraints) with UML meta-model extensions wPlatform-specific terminology, UML symbols and semantics wFull integration with MOF providing tool integration AB

4. © 2003 Mercury Computer Systems, Inc. 4 Enhanced Behavioral Modeling Capture Problems at Model Level l Extended sequence diagrams permit more detailed complex interactions wSupports sub-diagrams wDecomposition of SDL, MSC and LSC messages wControl structures: loop, parallel execution, alternative execution, protected regions,... l Activities permit more flexible parallelism, I/O options and data/control flow modeling wPetri Net model to derive concurrency wUnstructured activities possible wPre/post conditions wHPEC features described in HPEC 2001 e.g. interruptible regions and execution orderingHPEC 2001 sd ATM-transaction client:atm:dbase: insertCard CheckPin ref alt [chk= OK] [else] error(badPIN) DoTransaction ref

5. © 2003 Mercury Computer Systems, Inc. 5 Timing and State Modeling l Precise modeling of timing via timing sub- diagrams wPrevious profile for modeling schedulability, performance and time embedded in UML 2.0 wEnables next level of integrating hardware modeling to platform design l Statecharts now have sub-statecharts and inheritance sd DriverProtocol d : Driver o : OutPin t = 0 t = 5t = 10t = 15 IdleWaitBusyIdle 011100110001 0111

6. © 2003 Mercury Computer Systems, Inc. 6 UML 2.0 Provides HPEC “Potential” for Software Design Automation l Action semantics integrate activities with related low-level actions l There are many methods of UML-based code generation wState translation (I-Logix, Rose RT) wFormal translation (NU research, Telelogix)Formal translation wDirect template translation (Pathfinder) wMDA-based model execution (Pathfinder, Component-X, 88solutions) wGenerate/discover components (PCA)PCA wLow-level data/state flow import (MathWorks) wInformal indirect translation to non-mainstream tools and PGO (HPEC 2000)HPEC 2000 wModel Integrated Computing (MIC, MOBIES)MOBIES