Julia Reznik, Marc Born

Transcription

1 UML Notation for an Automated Deployment Process Julia Reznik, Marc Born GMD Fokus

2 Agenda Motivation Packaging and Deployment Model Driven Solution in order to support the automation of software deployment process UML Notation for software components CCM: Packaging and Deployment automated Generation of CCM Deployment Description 2

3 Motivation Large network environments have moved to the center stage in the field of software deployment New tools are needed to automate the component-based software deployment life cycle in a distributed environment Deployment life cycle: wide range of deployment tasks: Packaging, installation, update, reconfigure, adapt, remove 3

4 Packaging and Deployment Deployment Tool Software components manual automated Packaging Application Deployment requirements System properties Deployment Pprocess Component distribution, loading, configuration and execution Middleware Target environment 4

5 Deployment Tool XML Deployment Tool XML Target environment description Deployment software description 5

6 MDA Solution: Deployment Software Description Bridges the gap between design and deployment phase of distributed applications Provides conventions for applying and specializing standard UML to the graphical deployment notation Bases on the the definitions of the XML DTDs used by the CORBA Components Can be realized with existing UML tools (e.g. Rational Rose) Provides automatic generation of XML descriptors with a UML tool 6

7 Test Service Example for distributed systems Computational Object Types (COs): TestManager Node Main Test Component (MTC) Parallel Test Component (PTC) System Under Test (SUT) Node Test Manager MTC Node PTC PTC Node Node SUT SUT 7

8 Stereotypes: UML Extension Mechanisms Sub-classification of an existing UML element The new element has its own special properties (expressed as tagged values), semantics and notation Tagged Values: New information about model elements and presentation elements (new properties) Constraints: Conditions and restrictions, that apply to model elements 8

9 Diagrams and Stereotypes Class diagram : Computational Object Types (CO Types) and their interfaces Collaboration diagram: Initial configuration of COs and their factories Component diagram: implementation components Stereotypes: UML-Metamodel element Class Class Class Component Package Association Association Dependency Stereotype <<Factory>> <<Interface>> <<implementation>> <<assembly>> <<uses>> <<provides>> <<instantiate>> 9

10 Class diagram: CO Types and interfaces TestManager <<Interface>> i_mtccontrol settestparams() settestbehavior() starttest() stoptesting() <<uses>> mtc <<provides>> mtc_control MTC <<uses>> ptc_controls < < In t e r f a c e > > i_tccontrol settestcaseparams() settestbehavior() starttest() < < p r o v i d e s > > control PTC <<Interface>> Calculator plus() <<uses>> <<provides>> calculate calculate SUT <<provides>> mtc_notify <<Interface>> i_testmanagernotify <<uses>> mtc <<provides>> ptc_notify <<Interface>> i_mtcnotify <<uses>> ptc_notify submitttestresult() submitttestresult() 0

11 Initial Configuration Class diagram COs <<Factory>> TestManagerFactory (from Logical View) <<Factory>> PTCFactory (f rom Logical View) <<Factory>> MTCFactory (f rom Logical View) <<Factory>> SUTFactory (f rom Logic al View) <<instatiate>> <<instatiate>> <<instatiate>> <<instatiate>> <<Assembly>> TestService TestManager (f rom Logical View) PTC (f rom Logical View) MTC (f rom Logical View) SUT (f rom Logic al View) testmanagerfactory : TestManagerFactory ptcfactory : PTCFactory sutfactory : SUTFactory mtcfactory : MTCFactory link Collaboration diagram InitialConfiguration tm : TestManager mtc : MTC link2

12 Tagged Values () DCL specific keyword pairs: property name and value For stereotypes and <<Implementation>> tagged values are defined in the profile Source: CORBA Components Descriptors Software Package CORBA Component Component Assembly 2

13 <<implementation>> TestManager_W Tagged Values (2) <<C O >> TestManager 3

14 Constraints <<assembly>> must have two diagrams: COs and InitialConfiguration diagram a class diagram of <<assembly>> package contains only classes with and <<Factory>> Generalisation: all elements of the same stereotype (e.g. ) Valid association stereotype combinations: To: From: <<Factory>> <<Interface>> <<uses>> <<provides>> <<Factory>> <<instantiate>> <<Interface>> 4

15 Realization with UML tool Rational Rose Rational Rose provides graphical support for UML automatic generation of XML-Descriptors using Rose Extensibility Interface (REI) TestManager <<implementation>> TestManager_W CO Type TestManager <<implementation>> TestManager_S Softpkg * TestManager <<implementation>> TestManager_W <<implementation>> TestManager_S 5

16 Generation of softpkg descriptor () TestManager 6

17 Generation of Softpkg descriptor (2) 7

18 Generation of Component descriptor TestManager 8

19 Generation of Assembly descriptor <<Assembly>> TestService 9

20 Conclusion Graphical support for automated deployment process Specification of component-based software systems requirements Specification of Initial Configuration of component instances Automatic generation of XML-Descriptors for the Deployment process Under development: Automatic generation of UML Deployment diagram from the XML Description of target environment 20

21 Thank you! 2