Extending Enterprise Architecture Modeling Languages: Application to Telecommunications

1,057 views

Published on

Presentation at the 27th Symposium on Applied Computing (SAC), 2012.03, Trento, Italy.

Published in: Real Estate, Technology, Business
  • Be the first to comment

Extending Enterprise Architecture Modeling Languages: Application to Telecommunications

  1. 1. Extending Enterprise Architecture Modeling Languages: Application to Telecommunications Presenter : Anderson MORAIS (Ph.D. Student at Telecom SudParis)With the courtesy of: Ana CAVALLI (Prof. at Telecom SudParis) Authors:For questions, contact : Vanea CHIPRIANOV (Postdoctoral Researcher)(email vanea.chiprianov Yvon KERMARREC (Prof.)@telecom-bretagne.eu Siegfried ROUVRAIS (Assoc. Prof.)or live on twitter@vaneachiprianovor on skypechiprianov.vanea) Institut Mines-Télécom
  2. 2. Agenda ● How and why introduce domain specificity in Enterprise Architecture? ● Through Enterprise Architecture Modeling Language (EAML) extension ● Instanciating to Telecommunications ● Applying the extended EAML to a case study ● Conclusion and Perspectives2/18 SAC, Trento, Italy, March 26-30 2012 Extending EAMLs
  3. 3. Agenda ● How and why introduce domain specificity in Enterprise Architecture? ● Through Enterprise Architecture Modeling Language (EAML) extension ● Instanciating to Telecommunications ● Applying the extended EAML to a case study ● Conclusion and Perspectives2/18 SAC, Trento, Italy, March 26-30 2012 Extending EAMLs
  4. 4. Context: Why introduce domain specificity in Enterprise Architecture? ● Enterprise = complex adaptive system. ● Enterprise Architecture (EA) = a way to document, understand and master this complexity. ● EA Framework = describe a wide range of domains; – Integrated models of the enterprise: – Business and Application layer - OK; – Technical layer – more details are needed to describe a system. ● EA Modeling Language (ML) = a language for vizualizing, specifying, constructing and documenting the artifacts of a software-intesive enterprise.3/18 SAC, Trento, Italy, March 26-30 2012 Extending EAMLs
  5. 5. Context: Why introduce domain specificity in Enterprise Architecture?Example of EAML :ArchiMate 4/18 SAC, Trento, Italy, March 26-30 2012 Extending EAMLs
  6. 6. Problem: How to introduce domain specificity in Enterprise Architecture? ● Use EA framework and ML at Business and Application layer ● AND Introduce more domain specificity at Technical layer ● HOW?5/18 SAC, Trento, Italy, March 26-30 2012 Extending EAMLs
  7. 7. Agenda ● How and why introduce domain specificity in Enterprise Architecture? ● Through Enterprise Architecture Modeling Language (EAML) extension ● Instanciating to Telecommunications ● Applying the extended EAML to a case study ● Conclusion and Perspectives5/18 SAC, Trento, Italy, March 26-30 2012 Extending EAMLs
  8. 8. Solution/Contribution: Through EAML extension ● Profile = generic extension mechanism for customizing reference languages with constructs that are specific to particular domains, platforms. ● Advantages: ● Reuse of reference language and tools – benefic both for users and tool builders; ● Strictly additive extension => profile tools have to process only additions; ● Reference language – facilitates interoperability between all its profiles.6/18 SAC, Trento, Italy, March 26-30 2012 Extending EAMLs
  9. 9. Solution/Contribution: Through EAML extension ● Language extension with the Meta-modeling approachEAMLextensionEAML 7/18 SAC, Trento, Italy, March 26-30 2012 Extending EAMLs
  10. 10. Agenda ● How and why introduce domain specificity in Enterprise Architecture? ● Through Enterprise Architecture Modeling Language (EAML) extension ● Instanciating to Telecommunications ● Applying the extended EAML to a case study ● Conclusion and Perspectives7/18 SAC, Trento, Italy, March 26-30 2012 Extending EAMLs
  11. 11. Solution/Contribution: Instanciating to Telecommunications ● Service creation = complex activity because of: ● difficult technical issues, but also ● big number of actors, ● difference in each actors perspective and objectives. ● One actor: Service Provider = organization that creates value-added services. ● Service Provider requirements: ● Req 1: An overall model; ● Req 2: Domain specificity; ● Req 3: Rapid prototyping; ● ...8/18 SAC, Trento, Italy, March 26-30 2012 Extending EAMLs
  12. 12. Solution/Contribution : Instanciating to Telecommunications How EAMLs answer Service Providers requirements: ● Req 1: An overall model ● EA frameworks and MLs; ● Req 2: Domain specificity ● Introduce telecommunications specificity as profiles of EAMLs; ● Req 3: Rapid prototyping ● Meta-modeling approach, through code generation and easy integration with tools for reference language.9/18 SAC, Trento, Italy, March 26-30 2012 Extending EAMLs
  13. 13. Solution/Contribution: Extending ArchiMate EAML for Telecommunications ● Extending the Abstract Syntax (Technical layer)10/18 SAC, Trento, Italy, March 26-30 2012 Extending EAMLs
  14. 14. Solution/Contribution: Extending ArchiMate EAML for Telecommunications ● Extending the Concrete Syntax11/18 SAC, Trento, Italy, March 26-30 2012 Extending EAMLs
  15. 15. Solution/Contribution: Extending ArchiMate EAML for Telecommunications ● Operational semantics: excerpt of generated Java code12/18 SAC, Trento, Italy, March 26-30 2012 Extending EAMLs
  16. 16. Solution/Contribution: Extending ArchiMate EAML Tools for TelecommunicationsOverview oflanguage tools13/18 SAC, Trento, Italy, March 26-30 2012 Extending EAMLs
  17. 17. Solution/Contribution: Extending ArchiMate EAML Tools for TelecommunicationsExtended Archi14/18 SAC, Trento, Italy, March 26-30 2012 Extending EAMLs
  18. 18. Agenda ● How and why introduce domain specificity in Enterprise Architecture? ● Through Enterprise Architecture Modeling Language (EAML) extension ● Instanciating to Telecommunications ● Applying the extended EAML to a case study ● Conclusion and Perspectives14/18 SAC, Trento, Italy, March 26-30 2012 Extending EAMLs
  19. 19. Applying the Extended EAML to modeling a telecommunications conferencing serviceA possiblemodel of aconferencingservice at theArchiMateBusiness layer 15/18 SAC, Trento, Italy, March 26-30 2012 Extending EAMLs
  20. 20. Applying the Extended EAML to modeling a telecommunications conferencing service ● Excerpt from the model of a conferencing service at the ArchiMate Application layer16/18 SAC, Trento, Italy, March 26-30 2012 Extending EAMLs
  21. 21. Applying the Extended EAML to modeling a telecommunications conferencing service ● Excerpt from the model of a conferencing service at the Telecom ArchiMate Technology layer17/18 SAC, Trento, Italy, March 26-30 2012 Extending EAMLs
  22. 22. Agenda ● How and why introduce domain specificity in Enterprise Architecture? ● Through Enterprise Architecture Modeling Language (EAML) extension ● Instanciating to Telecommunications ● Applying the extended EAML to a case study ● Conclusion and Perspectives17/18 SAC, Trento, Italy, March 26-30 2012 Extending EAMLs
  23. 23. Conclusion and Perspectives● Identified a real need for extending EAMLs with domain specificity rather than define new MLs.● Proposed as solution the extension of EAMLs as profiles, with the Meta-modeling approach.● Future: Integrate a transversal ML for capturing Decision Rationale, thus enhancing collaboration. 18/18 SAC, Trento, Italy, March 26-30 2012 Extending EAMLs
  24. 24. For questions ● Contact Vanea CHIPRIANOV (live) ● On twitter: @vaneachiprianov ● On Skype: chiprianov.vanea18/18 SAC, Trento, Italy, March 26-30 2012 Extending EAMLs

×