extending enterprise architecture modeling languages: application to telecommunications

Institut Mines-Télécom

Extending Enterprise Architecture Modeling Languages:Application to Telecommunications

Presenter :Anderson MORAIS (Ph.D. Student at

Telecom SudParis)Ana CAVALLI (Prof. at Telecom SudParis)

Authors:Vanea CHIPRIANOV (Postdoctoral Researcher)Yvon KERMARREC (Prof.)Siegfried ROUVRAIS (Assoc. Prof.)

With the courtesy of:

For questions, contact :(email [email protected] live on twitter @vaneachiprianovor on skypechiprianov.vanea)

SAC, Trento, Italy, March 26-30 2012

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 Perspectives

2/18 Extending EAMLs


Context: Why introduce domain specificity in Enterprise Architecture?

Extending EAMLs3/18

● 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.


Context: Why introduce domain specificity in Enterprise Architecture?

Example of EAML :ArchiMate

Extending EAMLs4/18


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?

Extending EAMLs5/18


Agenda








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.

Extending EAMLs6/18


Solution/Contribution:Through EAML extension

● Language extension with the Meta-modeling approach

Extending EAMLs7/18

EAML

EAMLextension


Agenda








Solution/Contribution:Instanciating to Telecommunications

● Service creation = complex activity because of:

● difficult technical issues, but also

● big number of actors,

● difference in each actor's 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;

● ...

Extending EAMLs8/18


Solution/Contribution :Instanciating to Telecommunications

● Req 1: An overall model

● Req 2: Domain specificity

● Req 3: Rapid prototyping

● EA frameworks and MLs;

● Introduce telecommunications specificity as profiles of EAMLs;

● Meta-modeling approach, through code generation and easy integration with tools for reference language.

How EAMLs answer Service Provider's requirements:

Extending EAMLs9/18


Solution/Contribution: Extending ArchiMate EAML for Telecommunications

● Extending the Abstract Syntax (Technical layer)

Extending EAMLs10/18



● Extending the

Concrete Syntax




● Operational semantics: excerpt of generated Java code



Solution/Contribution: Extending ArchiMate EAML Tools for Telecommunications

Overview oflanguage tools



Solution/Contribution: Extending ArchiMate EAML Tools for Telecommunications

Extended Archi



Agenda








Applying the Extended EAML to modeling a telecommunications conferencing service

A possible model of a conferencing service at the ArchiMate Business layer




● Excerpt from the model of a conferencing service at the ArchiMate Application layer




● Excerpt from the model of a conferencing service at the Telecom ArchiMate Technology layer



Agenda








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: Integratea transversal MLfor capturingDecision Rationale,thus enhancing collaboration.



For questions

● Contact Vanea CHIPRIANOV (live)

● On twitter: @vaneachiprianov

● On Skype: chiprianov.vanea


extending enterprise architecture modeling languages: application to telecommunications

Real Estate

extending eamls

enterprise architecture

domain specificity req

telecommunications specificity

profiles of eamls req

extended eaml

perspectives218 sac

eaml extension profile