An MDE Process for Generating and Integrating Software Tools: Application to Collaborative
Construction of Telecom Services
Vanea Chiprianov Yvon Kermarrec Siegfried Rouvrais
Agenda
1.Requirements of Telecom Service Providers and Developers
2.A Collaborative Process for the Construction of
Telecom Services
3.An MDE Process for Generating and Integrating
Software Tools
Telecom Service Life-cycle
Our Focus on Telecom Service Life-cycle
Requirements of Providers and Developers for Service Construction
1.An overall model 2.Domain specificity 3.Rapid prototyping 4.Collaborative support 5.Early verification/simulation 6.Integration 7.Reuse
8.Wide range of services
9.Easy evolution of services
Agenda
1.Requirements of Telecom Service Providers and
Developers
2.A Collaborative Process for the Construction of Telecom Services
3.An MDE Process for Generating and Integrating
Software Tools
Responsiblities of a Modeler
Define the architecture/design of the system Explore alternatives, make choices
Synthetize a solution, validate it Discuss/work with other teams
1.Model
2.Test
3.Collaborate (design decisions and argumentation)
4.Interoperate
[Kruchten, 2008]
A Collaborative Process for the Construction of Telecom Services 1.Model 2.Test 3.Collaborate 4.Interoperate
Modeling with DSMLs 1.Model 2. 3. 4. DSML = graphical language that offers, through
appropriate notations and abstractions, expressive
power focused on a particular domain, to visualize, specify, construct and document the artifacts of a
software-intensive system. [Booch, 2005], [Deursen, 2000]
How do DSMLs contribute towards fullfiling Service Construction Requirements
1.An overall model 2.Domain specificity 3.Rapid prototyping 4.Collaborative support 5.Early verification/simulation 6.Integration 7.Reuse
8.Wide range of services
Testing through leverage of COTS 1. 2.Test 3. 4.
COTS (Components Off The Shelf) = ''a commercially available or open source piece of software that other software projects can reuse and integrate into their own products'' [Torchiano, 2004]
How do Integration of COTS contribute towards fullfiling Service Construction Requirements 1.An overall model 2.Domain specificity 3.Rapid prototyping 4.Collaborative support 5.Early verification/simulation 6.Integration 7.Reuse
8.Wide range of services
Collaborating by capturing and retrieving Decision Rationale 1. 2. 3.Collaborate 4. Decision Rationale DSML Decision Rationale = the justification behind
decisions, the reasoning that goes into
determining the design of the artifact. [Dutoit, 2006]
How does a Decision Rationale DSML contribute towards fullfiling Service Construction Requirements 1.An overall model 2.Domain specificity 3.Rapid prototyping 4.Collaborative support 5.Early verification/simulation 6.Integration 7.Reuse
8.Wide range of services
A Collaborative Process for the Construction of Telecom Services 1. 2. 3. 4.Interoperate Model Transformations, ontologies, Higher Order model Transformations
How does a Decision Rationale DSML contribute towards fullfiling Service Construction Requirements 1.An overall model 2.Domain specificity 3.Rapid prototyping 4.Collaborative support 5.Early verification/simulation 6.Integration 7.Reuse
8.Wide range of services
How do proposed Software Tools contribute towards fullfiling Service Construction Requirements 1.An overall model 2.Domain specificity 3.Rapid prototyping 4.Collaborative support 5.Early verification/simulation 6.Integration 7.Reuse
8.Wide range of services
1.Model
2.Test
3.Collaborate
Agenda
1.Requirements of Telecom Service Providers and
Developers
2.A Collaborative Process for the Construction of
Telecom Services
3.An MDE Process for Generating and Integrating Software Tools
An MDE Process for Developing DSMLs
How do proposed Software Tools contribute towards fullfiling Service Construction Requirements 1.An overall model 2.Domain specificity 3.Rapid prototyping 4.Collaborative support 5.Early verification/simulation 6.Integration 7.Reuse
8.Wide range of services
9.Easy evolution of services
1.Model
2. 3. 4.
An MDE Process for Leveraging COTS for testing 1.
An MDE Process for Composing Transversal DSMLs 1. 2. 3.Collaborate 4.
An MDE Process for Ensuring DSML Interop. 1.
An Integrated MDE Process 1.Model 2.Test 3.Collaborate 4.Interoperate
Agenda
1.Requirements of Telecom Service Providers and
Developers
2.A Collaborative Process for the Construction of
Telecom Services
3.An MDE Process for Generating and Integrating
Software Tools
Conclusions and Perspectives
Define MMi – essential activity • Currently – informal
• Need for formal methods of eliciting and evolving
domain models (MMi)
Waterfall-like process
• Currently – still reflect practice in some industries • Future – iterative or agile methods
Publication
Chiprianov V., Kermarrec Y., Rouvrais S.: Integrating DSLs into a Software Engineering
Process: Application to Collaborative Construction of Telecom Services. Formal and Practical Aspects of Domain-Specific Languages: Recent Developments, Ed. Marjan Mernik, IGI
Publications
1.Chiprianov V., Kermarrec Y., Rouvrais S.: Extending Enterprise Architecture Modelling Languages: Application to Telecommunications Service Creation. The 9th Enterprise Engineering track at the 27th Symposium on Applied
Computing (SAC), Trento, Italy, 6pp, accepted, (2011) – rank B [ERA].
2.Chiprianov V., Alloush I., Kermarrec Y., Rouvrais S.: Telecommunications Service Creation: Towards
Extensions for Enterprise Architecture Modeling Languages. In: Proc. of the 6th Intl Conf. on Software and Data Technologies (ICSOFT), Seville, Spain, vol 1, pp. 23-29, (2011) - rank B [ERA].
3.Chiprianov V., Kermarrec Y., Rouvrais S.: Towards semantic interoperability of graphical domain specific modeling languages for telecommunications service design. In: Proc. of the 2nd Intl Conf. on Models and
Ontology-based Design of Protocols, Architectures and Services (MOPAS), Budapest, Hungary, pp.21-24, (2011).
4.Chiprianov, V., Kermarrec, Y. and Alff, P.: A Model-Driven Approach for Telecommunications Network Services Definition. In: Proceedings of the 15th Open European Summer School and IFIP TC6. 6 WS on The Internet of the Future, LNCS, pages 199–207, Barcelona, Spain, (2009).
5.Rouvrais S., Chiprianov V.: Modeling and Architecting Educational Frameworks. In: Electronic Proc. of the 7th Intl CDIO Conf., Technical University of Denmark, Copenhagen (2011).
6.Chiprianov, V., Kermarrec, Y., Rouvrais, S.: Meta-tools for Software Language Engineering: A Flexible Collaborative Modeling Language for Efficient Telecommunications Service Design. In: FlexiTools WS, 32nd ACM/IEEE Intl. Conf. on Soft. Engineering (ICSE), Cape Town, South Africa, 5 pp, (2010).
7.Chiprianov, V., Kermarrec, Y.: An Approach for Constructing a Domain Definition Metamodel with ATL. In: Model Transformation with ATL, 1st Intl. WS,Nantes,France, pp 18-33, (2009).
8.Chiprianov V., Kermarec Y., Rouvrais S.: Practical Model Extension for Modeling Language Profiles. An
Enterprise Architecture Modeling Language Extension for Telecommunications Service Creation. 7émes Journées sur l’Ingénierie Dirigée par les Modèles, Lille, France, pp. 85-91, 2011.
Bibliography
[Berndt, 1994] Hendrik Berndt, Peter Graubmann & Masaki Wakano. Service
Specification Concepts in TINA-C. In Proceedings of the 2nd Intl. Conf. on Intelligence in Broadband Services and Networks: Towards a Pan-European Telecommunication Service Infrastructure, pages 355–366, London, UK, 1994.
[Hållstrand, 1994] Joacim Hållstrand & Declan Martin. Industrial Requirements on a
Service Creation Environment. In Proceedings of the 2nd Intl. Conf. on Intelligence in Broadband Services and Networks: Towards a Pan-European Telecommunication Service Infrastructure, pages 17–25, London, UK, 1994.
[Khlifi, 2008] H. Khlifi & J.-C. Gregoire. IMS Application Servers: Roles, Requirements,
and Implementation Technologies. Internet Computing, IEEE, vol. 12, no. 3, pages 40 – 51, may-june 2008.
[Kosmas, 1997] Nikolaos Kosmas & Kenneth J. Turner. Requirements for Service
Creation Environments. In 2nd International Workshop on Applied Formal Methods in System Design, p. 133 - 137, 1997
[Kruchten, 2008] P. Kruchten. Controversy Corner: What do software architects really
