A new viewpoint for change management in RM-ODP systems

1. A new viewpoint for change management in RM-ODP systems Nesrine Yahiaoui1,2, Bruno Traverson1, Nicole Lévy2 1 EDF R&D - 2 UVSQ PRiSM Workshop on ODP for Enterprise Computing WODPEC 2005 Enschede, September 19 Versailles University

2. Contents • Problem Statement • Links for Change Management • Design Framework • Implementation with Eclipse/EMF • Conclusion Enschede --- September 19,2005

3. ProblemStatement • Designing a system is a complex task • The system is divided into several views (models), • Each view represents the system according to a particular concern, • The basic concepts of a particular concern are described into a viewpoint (meta-model). • Systems are continuously changing • A change may occur on any view, • A change may impact several views. Enschede --- September 19,2005

4. Enterprise Information Computational Engineering Technology Reference Model for Open Distributed Processing ISO-10746 Enschede --- September 19,2005

5. Discussion • Issues • RM-ODP abstractly specifies correspondence rules between concepts defined in different viewpoints • how to verify that they are satisfied ? • Some solutions • ODAC (LIP 6), DASIBAO ( EDF R&D), EDOC ( OMG) • Formalize the viewpoints using meta-modeling (MOF) • Define UML Profiles to specify the views • Guarantee consistency between views by construction • Problem • These rules are not memorized Enschede --- September 19,2005

6. Discussion • Our objective is to study the impact of modification on a view • Our solution • Introduce traceability between views • Use the traceability to manage the impact of a modification • Introduce correspondence link • To memorize the correspondence between views • To be able to verify the satisfaction of the correspondence rules Enschede --- September 19,2005

7. Correspondence Rule • Describes a constraint applied to concepts from two different viewpoints in order to achieve a consistency between views. • RM-ODP defines a set of rules in an abstract way • Enterprise and Computational • an enterprise object corresponds to computational object or a configuration of computational objects. • Enterprise and Engineering • a policy may correspond to and determines transparency requirements that engineering objects support. • Computational and Engineering • a computational binding, primitive or via a binding object, corresponds to a local or distributed binding (via a channel). Enschede --- September 19,2005

8. Correspondence Link • Introduce a new viewpoint that specifies the correspondence link concept • Explicit binding between instances of concepts belonging to two different views. • Bi-directional, possibility to navigate from any of the two views • Constrained by a rule Enschede --- September 19,2005

9. EnterpriseMM ComputationalMM EngineeringMM 1..* 1..* 1..* LinkMM * References * References * References 1 1 1 1 Computational-EndPoint Concept Engineering-EndPoint link Concept Concept Enterprise-EndPoint Rule Computational-EngineeringLink Enterprise-Computational Link 1..* Identifies 1..* Identifies 1..* Identifies 1..* Identifies Constrain 1..* 1 Link Meta-model Enschede --- September 19,2005

10. Enterprise View Rule: Rule1 Role: ProduceElectricity EnterEnp enp1 Ent-ComLink: Corres1 CompEnp enp2 Rule: Rule2 CompEnp enp3 EngEnp enp4 Com-EngLink: Corres2 Link View Computational View InterfaceOperation: startProduction Engineering view InterfaceEngineering: manageStopProduction InterfaceOperation: stopProduction Illustration Enschede --- September 19,2005

11. Design Framework • The models ( views) are described according to their respective meta-models (viewpoints) • The description of a link model explicitly binds the elements of different models. • The Impact management is triggered in the other views when one view is modified • The modification in a view is described by a scenario • Kinds of impact management • Manual • Semi-automatic • Automatic Enschede --- September 19,2005

12. meta-models repository Evolution descriptor use Impact management Evolution management Models repository Parser manipulate Impact scenario builder Link-model Repository manipulate Design Framework Local consistency controller Integrator Enschede --- September 19,2005

13. meta-models repository Evolution descriptor x use Impact management evolution management Models repository Parser manipulate Impact scenario builder Local consistency controller x Link-model Repository Integrator manipulate y Automatic y Semi-automatic Manual Design Framework Enschede --- September 19,2005

14. Implementation with Eclipse/EMF • Eclipse is • Universal platform for integrating development tools • Open, extensible architecture based on plug-ins • Eclipse Modeling Framework • Eclipse plug-in • Models and meta-models • Code generation facility • Serialization and loading Enschede --- September 19,2005

15. Link view Enterprise view Computational view Implementation with Eclipse/EMF Description of evolution Execute button Enschede --- September 19,2005

16. Conclusion • Assets • We proposed the concept of link that binds the elements that are in correspondence. • We proposed a design framework that uses the correspondence links to manage modifications impact. • Implementation is based on Eclipse/EMF. • Issues • How can we make the impact management more automatic ? Enschede --- September 19,2005