1. UML 1.4 to Core Scenario Model Transformation for PUMA Project Kathleen H. Shen Kathleenshen@yahoo.com Department of Systems and Computer Engineering Carleton University June 29 th, 2004

2. PUMA Project 06/29/20042 Conceptual High Level View UML To CSM Transformation Annotated UML Design Model Core Scenario Model XMI Reader (NSUML ) Internal Data Structure (UML Metamodel) Transformation algorithm implemented by JAVA

3. PUMA Project 06/29/20043 Input Model – Deployment Diagram > Security CardReader > DoorLock Actuator > Video Camera > Disk > LAN Acess Control VideoAcquisition Video Controller Store Proc > Buffer Acquire Proc Buffer Manager > ApplicCPU Data base > DB_CPU

4. PUMA Project 06/29/20044 Input Model – Activity Diagrams

5. PUMA Project 06/29/20045 Input Model – Activity Diagrams(Cond.)

6. PUMA Project 06/29/20046 UML MetaModel  Deployment diagram MModelElement (from Core) MComponent Instance MNodeInstance +residence * 0..1 Part of MetaModel Elements used in Deployment diagram

7. PUMA Project 06/29/20047 Internal Data Structure- Deployment Diagram AppliCPU: MNodeInstance +residence 0..1 VideoController MComponent Instance BufferMagager: MComponent Instance StoreProc: MComponent Instance AcqurieProc: MComponent Instance VideoController: MComponent Instance AccessControl MComponent Instance DB_CPU: MNodeInstance +residence 0..1 Database: MComponent Instance LAN: MNodeInstance LinkEnd MLinkEnd Link: MLink LinkEnd MLinkEnd Link: MLink

8. PUMA Project 06/29/20048 UML MetaModel  Activity diagram MSubactivityState MActionState MModelElement MStateMachine MTransition MCompositeStateMSimpleStateMFinalState MStateVertex MActivityGraph MPartition MState 1 0..* 0..1 1 * 0..* 0..1 * MPseudoState +source +target +outgoing +incoming

9. PUMA Project 06/29/20049 Internal Data Structure- Activity Diagram ProcOneImage: MSubactivityState T1: MTransition cycleOverhead: MSimpleState End: MFinalState BSSHL:: MActivityGraph VideoController: MPartition +source +target +outgoing +incoming Initial : MPseudoState T2: MTransition T3: MTransition +source +outgoing +incoming +target +source +outgoing +target +incoming

10. PUMA Project 06/29/200410 Internal Data Structure- Activity Diagram (Cond.) Activity1: MSimpleState Fork: MPseudoState Activity2: MSimpleState Activity3: MSimpleState Join: MPseudoState Activity4: MSimpleState T1: MTransition Activity2Activity3 Activity1 Activity4

11. PUMA Project 06/29/200411 Internal Data Structure- Activity Diagram (Cond.) Activity2Activity3 Activity1 Activity4 Activity1: MSimpleState Branch MPseudoState Activity2: MSimpleState Activity3: MSimpleState Junction: MPseudoState Activity4: MSimpleState T1: MTransition T2: MTransitionT3: MTransition T4: MTransitionT5: MTransition

12. PUMA Project 06/29/200412 CSM class diagram CSM General Resource Abstract Step Scenario Active Resource Passive Resource (Protected Logical Resource) External Operation Processing Resource Component Step Path Connection SequenceBranchMergeForkJoin Start End Resource Acquire Resource Release Workload root 1 0..1 * * m pre n post host 1 demand 1..* 1 1

13. PUMA Project 06/29/200413 Transformation Rules: Deployment Diagram AppliCPU: MNodeInstance +residence 0..1 Buffer: MComponent Instance BufferMagager: MComponent Instance StoreProc: MComponent Instance AcqurieProc: MComponent Instance VideoController: MComponent Instance AccessControl MComponent Instance Node Instance with >  ProcessingResource LAN: MNodeInstance Node Instance with >  PassiveResource Component Instance with >  PassiveResource Component Instance  Component LAN: Passive Resource AppliCPU: Processing Resource Buffer: Passive Resource Access Control: Component

14. PUMA Project 06/29/200414 Generated part in CSM CSM General Resource Abstract Step Scenario Active Resource Passive Resource (Protected Logical Resource) External Operation Processing Resource Component Step Path Connection SequenceBranchMergeForkJoin Start End Resource Acquire Resource Release Workload root 1 0..1 * * m pre n post host 1 demand 1..* 1 1

15. PUMA Project 06/29/200415 Transformation Rules: Activity Diagram  Initial State T1: MTransition Initial : MPseudoState Partition1 Partition1: MPartition > {PApopulation=1} activity1 aStart: Start id: Name: Workload: Successor aSequence: Sequence id: Name: Source: Target: partition1RA : Resource Acquire predecessor: Successor: Id: aWorkLoad: Workload id: Population: Resp_time: aSequence: Sequence id: Name: Source: Target: activity1: Step id: Name: Workload: Successor activity1: MSimpleState

16. PUMA Project 06/29/200416 activity1: MSimpleState Fork: MPseudoState activity2: MSimpleState activity3: MSimpleState T1: MTransition T2: MTransitionT3: MTransition Transformation Rules: Activity Diagram  Fork aFork: Fork ID: Source: Target: activity1: Step id: Name: activity3: Step id: Name: activity2: Step id: Name: activity1 activity2activity3

17. PUMA Project 06/29/200417 Transformation Rules: Activity Diagram  Transition Activity1: MSimpleState T1: MTransition Activity2: MSimpleState Partion1: MPartition Partition2: MPartition Activity1 Activity2 Partition1Partition2 RL RA aSequence: Sequence id: Source: Target: Partition2RA: Resource Release Partition1RL: Resource Acquire id: Predecessor: Successor: id: Predecessor: Successor: Activity1: Step id: Successor: aSequence: Sequence id: Name: Source: Target: aSequence: Sequence id: Source: Target: Activity2: Step id: Predecessor

18. PUMA Project 06/29/200418 Generated part in CSM CSM General Resource Abstract Step Scenario Active Resource Passive Resource (Protected Logical Resource) External Operation Processing Resource Component Step Path Connection SequenceBranchMergeForkJoin Start End Resource Acquire Resource Release Workload root 1 0..1 * * m pre n post host 1 demand 1..* 1 1

19. PUMA Project 06/29/200419 Example:  BSS > Security CardReader > DoorLock Actuator > Video Camera > Disk > LAN Aces s Cont rol VideoAcquisition Video Controller Store Proc > Buffer Acquire Proc Buffer Manager > ApplicCPU Data base > DB_CPU

20. PUMA Project 06/29/200420 CSM representation for BSS(1) ResAcq:: procOneImage: Step cycleOverhead: Step ResAcq:: Workload: videoController: Component Start:: End:: Applic_CPU: Processing Resource

21. PUMA Project 06/29/200421 ResAcq:: Acquire: Component Start:: ResRel:: ResAcq:: ResRel:: ResAcq:: getBuffer: Step allocBuf: Step getImage: Step passImage: Step ResRel:: Fork: PathConnection BufferManager: Component StoreProc: Component Database: Component End:: storeImage: Step store: Step writeImage Step ResRel:: ResAcq:: ResRel:: ResAcq:: freeBuf Step ResRel:: ResAcq:: releaseBuf: Step ResRel:: ResAcq:: Wait_SP End ResAcq:: DB_CPU: Processing Resource CSM representation for BSS(2) ExtOP: Network ExtOP: writeBuffer

22. PUMA Project 06/29/200422 Generated CSM in XML format (1)

23. PUMA Project 06/29/200423 Generated CSM in XML format (2)

24. PUMA Project 06/29/200424 Generated CSM in XML format (3)

25. PUMA Project 06/29/200425 Generated CSM in XML format (4)

26. PUMA Project 06/29/200426 Status Designed and Implemented UML to Core Scenario Model prototype, the transformation implemented for UML 1.4 Annotated UML model contains: Deployment diagram  Allocation of Resources; Activity diagrams  Scenarios Scenarios can be also represented by interaction diagrams Sequence diagrams Collaboration diagrams In UML 1.4 interaction diagrams are quite simplistic, but they are better in UML 2.0.