Config & Change Management of Models

Transkript

1 Config & Change Management of Models HOOD GmbH Keltenring Oberhaching Germany Tel: onf Config & Change Management of models

2 Speaker HOOD Group Keltenring Oberhaching Germany ~ 40 Employees Requirements Management Config & Change Management Dr. Rudolf Hauber UML and technology senior consultant [email protected] > 10 year modelling experiance -2- onf Config & Change Management of models

3 Motivation System and software development is not trivial! System are getting more and more complex The answer: using abstraction to handle complexity The approach: modelling reduces complexiy improves communication simplifies re-use Requires suitable modelling techniques Well-tried Commonly accepted Tool supported (Von Rational Websources) -3- onf Config & Change Management of models

4 Collaboration System are getting more and more complex Teams are growing Analysis gets more important Collaboration is needed Within teams Across sites/locations -4- onf Config & Change Management of models

5 Model information storage Typical model element storages File based inherent exclusive access RDBMS based inherent concurrent access Filesystem RDBMS LogicalView Table Analysis SubA Table Table Table Design -5- onf Config & Change Management of models

6 File based models Model splitted into finer grained units use file system mechanisms for access control: controlled units. Depending on size up to thousands Filesystem LogicalView Analysis.rtlogpkg LogicalView Design_Model SubA corresponds Design.rtlogpkg Design_Model SubA.rtlogpkg SubA.rtlogpkg.rtlogpkg -6- onf Config & Change Management of models

7 Branches and visibility Different teams work on different tasks. using iterative processes, there are multiple version of one model element Different branches can handle these issues. VersionSystem (VS) SubA SubA SubA formal delivery main release integration working visible configuration Iteration delivery bugfix change request -7- onf Config & Change Management of models

8 Configurations and Views Different version of one model element exists in parallel Visible configurations of the model must be specified Configurations can be identified by label names VS SubA view view working Config spec Config spec integration working integration _RELEASE_2_0 visible configuration -8- onf Config & Change Management of models

9 Multisite structure Synchronization of multiple sites can be handled by file system multi-site solutions LogicalView LogicalView Multisite VS Munich Analysis.rtlogpkg Analysis.rtlogpkg SubA.rtlogpkg SubA.rtlogpkg SubA Design.rtlogpkg Design.rtlogpkg Design_Model Design_Model.rtlogpkg SubA.rtlogpkg.rtlogpkg.rtlogpkg LogicalView LogicalView Multisite VS Rom Analysis.rtlogpkg Analysis.rtlogpkg SubA.rtlogpkg SubA.rtlogpkg SubA Design.rtlogpkg Design.rtlogpkg Design_Model Design_Model.rtlogpkg SubA.rtlogpkg.rtlogpkg.rtlogpkg LogicalView LogicalView Multisite VS Boston Analysis.rtlogpkg Analysis.rtlogpkg SubA.rtlogpkg SubA.rtlogpkg SubA Design.rtlogpkg Design.rtlogpkg Design_Model Design_Model common.rtlogpkg SubA.rtlogpkg.rtlogpkg.rtlogpkg site specific -9- onf Config & Change Management of models

10 Changes and Concurrent Development Test Solution Test Spec Req. Spec D1 D1 D2 D3 D2 D3 D1 D1 D2 D3 D2 D3 t -10- onf Config & Change Management of models

11 Changes integration How to handle changes affecting other deliverys? Development for delivery1 Development for delivery2 Development for delivery3 SPS update1 SPS update1 PCR B1_1 PCR B1_1 PCR B2_1 PCR B2_1 PCR B1_2 PCR B3_1 PCR B1_2-11- onf Config & Change Management of models

12 Change Request Impact Analysis UML Model During change request analysis, the impact to affected delivery elements (subsystems or whatever) has to be analysed Trace change requests to affected model elements For deeper impact analysis use UML implicit tracing features Tracing to components, collaborations, interfaces, implicitly affected subsystems,... CR213: The CDI shall recognize... Related model element DnD Model D1 DnD Model D2 DnD Model D3 EEC CDI EEC CDI EEC CDI FightHMI FightHMI FightHMI -12- onf Config & Change Management of models

13 Change Request Resolution UML Model Change affected model element as needed You can use the RoseRT Model Integrator to merge the changes across deliveries Therefore all models CR213: The CDI shall recognize... DnD Model D2 DnD Model D2 DnD Model D3 EEC CDI EEC CDI EEC CDI FightHMI FightHMI FightHMI DnD VOB merge -13- onf Config & Change Management of models

14 Merge levels Merge of model can be done on ASCII, XMI or model level. UML Merge UML Merge Merging on an inappropriate level makes the merge very hard. Visual merge appropriate for visual language Because of model element dependency-network, much harder than source code merge XMI Merge XMI Merge ASCII Merge ASCII Merge onf Config & Change Management of models

15 Rebaselining 3. One model for all deliveries, but delivery specific branches 9 Pros 9 Handling of variants and cross-delivery changes seems to be simpler Cons Very complex branching Very complex config specs Subsystem-A VersionSystem Component1 Component2 Component3 ReqPro RM database: nearly impossible Subsystem-A Component1 D1 D2 D3 Component2-15- onf Config & Change Management of models

16 Integrated QA Compare build mechanisms for source code using ANT, MAKE or other mechanisms Integrated tests to ensure the quality of a configuration Integrated doc generation to ensure latest news At modelling level Check UML syntax Check modeling guideline conformance Generate documentation VersionSystem Subsystem-A Component1 Component2 Component3 Check out Or periodically Subsystem-A Component1 Component2 D1 D2 Model check Docu generation D3 Check in Or approval -16- onf Config & Change Management of models

17 Conclusion File based models Source code CCM mechanisms can be lift up to model level for file based models. All mechanisms fit very well. RDBMS based models Much harder to handle the above issues. I am not aware of a good CCM strategy onf Config & Change Management of models

18 From Use Cases to Test Cases Thanks for your pat ience! Quest ions & Disscussion Please contact me: -18- onf Config & Change Management of models