Towards an integrated service-oriented reference enterprise architecture

Transcription

1 Towards an integrated service-oriented reference enterprise architecture Alfred Zierann 1, Kurt Sandkuhl 2, Michael Pretz 3, Michael Falkenthal 1, Dierk Jugel 1, Matthias Wißotzki 3 1 Faculty of Inforatics, University of Applied Sciences Reutlingen, Gerany firstnae.lastnae@reutlingen-university.de 2 Inforation Systes, University of Rostock, Gerany firstnae.lastnae@uni-rostock.de 3 Enterprise-Architecture & Innovation, Dailer AG, Gerany ichael.pretz@dailer.co **Full ACM reference as provided by ACM** e.g.: Alfred Zierann, Kurt Sandkuhl, Michael Pretz, Michael Falkenthal, Dierk Jugel, and Matthias Wißotzki Towards an integrated service-oriented reference enterprise architecture. In Proceedings of the 2013 International Workshop on Ecosyste Architectures. ACM, New York, NY, USA, DOI= / author3333=3{Alfred3Zierann3and3Kurt3Sandkuhl3and3Michael3 33 : 33333Pretz3and3Michael3Falkenthal3and3Dierk3Jugel3and Matthias3Wi\ssotzki},3 33title33333=3{Towards3an3integrated3serviceJoriented3reference enterprise3architecture},3 33booktitle3=3{Proceedings3of3the320133International3Workshop3on Ecosyste3Architectures},3 33year333333=3{2013},3 33pages33333=3{26JJ30},3 33publisher3=3{ACM},3 33doi =3{ / }3 }3 ACM 2013 This is the author's version of the work. It is posted here by perission of ACM for your personal use. Not for redistribution. The definitive version is available at ACM: Perission to ake digital or hard copies of all or part of this work for personal or classroo use is granted without fee provided that copies are not ade or distributed for profit or coercial advantage and that copies bear this notice and the full citation on the first page. To copy otherwise, to republish, to post on servers or to redistribute to lists, requires prior specific perission and/or a fee.

2 Towards an Integrated Service-Oriented Reference Enterprise Architecture Alfred Zierann Faculty of Inforatics Architecture Reference Lab Reutlingen, Gerany Kurt Sandkuhl University of Rostock Faculty of Coputer Science Inforation Systes Rostock, Gerany Michael Pretz Dailer AG Enterprise Architecture Manageent SOA Innovation Lab Stuttgart, Gerany Michael Falkenthal Faculty of Inforatics Architecture Reference Lab Reutlingen, Gerany Dierk Jugel Faculty of Inforatics Architecture Reference Lab Reutlingen, Gerany Matthias Wissotzki University of Rostock Faculty of Coputer Science Inforation Systes Rostock, Gerany ABSTRACT New business inforation systes are integrating eerging cloud infrastructures with service-oriented platfors and intelligent user-centered obile systes. Both architecture engineering and anageent of service-oriented enterprise architectures is coplex and has to integrate synergistic disciplines like EAM - Enterprise Architecture and Manageent for Services & Cloud Coputing, Seantic-based Decision Support through Ontologies and Knowledge-based Systes, Big Data Manageent, as well as Mobility and Collaboration Systes. It is necessary to identify affected decisions by runtie changes of a service-oriented runtie environent and architecture. We have to ake transparent the ipact of these changes over the integral landscape of affected EAM-capabilities, like directly and transitively ipacted business categories, processes, applications, services, platfors and infrastructures. The paper describes a new Metaodel-based integration approach for Service-oriented Reference Enterprise Architectures. Categories and Subject Descriptors C.0 [Coputer Systes Organization]: Syste Architectures D.2.11 [Software Engineering]: Software Architectures H.1 [Inforation Systes]: Models and Principles General Ters Manageent, Measureent, Design, Standardization, Theory. Keywords Service-oriented Reference Enterprise Architecture, Architecture Metaodel Integration Method, Metaodel and Ontology. Perission to ake digital or hard copies of all or part of this work for personal or classroo use is granted without fee provided that copies are not ade or distributed for profit or coercial advantage and that copies bear this notice and the full citation on the first page. To copy otherwise, or republish, to post on servers or to redistribute to lists, requires prior specific perission and/or a fee. Conference 10, Month 1 2, 2010, City, State, Country. Copyright 2010 ACM /00/0010 $ INTRODUCTION In recent years innovation oriented copanies have introduced service-oriented coputing [24] paradigs and cobined the with traditional inforation systes. Inforation and data are central coponents of our everyday activities. Social networks, sart portable devices, and intelligent cars, represent a few instances of a pervasive, inforation-driven vision of current enterprise systes with service-oriented enterprise architectures. Social graph analysis and anageent, big data, and cloud data anageent, ontological odeling, sart devices, personal inforation systes, hard non-functional requireents, such as location-independent response ties and privacy are challenging essentials of the above scenario. Service-oriented systes close the business - IT gap by delivering appropriate business functionality efficiently and integrating new service types coing fro the cloud [2-3]. As the architecture of service-oriented enterprise systes becoes ore and ore coplex, and we are going rapidly into cloud coputing settings, we need a new and iproved set of ethodological wellsupported instruents and tools for anaging, decision support, diagnostics and for optiization of coplex service-oriented enterprise architectures and related inforation systes. The current state of art research in service-oriented enterprise architecture for services and cloud coputing [2-3] and [23] lack an integral understanding of enterprise architecture and anageent [19-21] and shows an abundant set of low-level integrated standards, ethods and tools. The ai of our research is to close this gap and enhance analytical instruents for cyclic evaluations of business and syste architectures in real business enterprise syste environents. In this paper we introduce our extended service-oriented enterprise architecture reference odel in the context of our new architecture etaodel integration approach and ontology for integral enterprise architectures of services and cloud coputing systes. Our research ais to develop a etaodel-based odel extraction and integration approach for enterprise architecture viewpoints, odels, standards, fraeworks [4] and tools for EAM towards consistent seantic-supported service-oriented reference enterprise architectures in cloud environents. The goal is to be

3 able to support architecture developent, assessents, architecture diagnostics, onitoring with decision support, and optiization of the business, inforation systes, and technologies. We intend to provide a unified and consistent ontology-based EAM-ethodology for the architecture anageent odels of relevant inforation resources, especially for service-oriented and cloud coputing systes. Our research results are currently validated and extended in research and practical scenarios [24-25] by industrial and acadeic partners of the SOA Innovation Lab and Gerany and Switzerland. In our current research we are extending our first version of ESARC Enterprise Services Architecture Reference Cube [24-25]. ESARC is an integral service-oriented enterprise architecture classification fraework, which sets a standard of coparison for analyzed enterprise architecture descriptions as a guiding instruent for concrete architecture engineering scenarios. ESARC akes it possible to verify, define and track the iproveent path of different business and IT changes considering alternative business operating odels, business functions and business processes, enterprise services and systes, their architectures and related cloud-enabled technologies, like infrastructures and platfors as a service. We are interested in a discussion about our approach towards integrated service-oriented reference enterprise architectures for current and new inforation resources and systes. The novelty in our current research paper coprises new aspects for Enterprise Architecture Manageent (EAM) and Architectures of Services & Cloud Coputing (SCC). The following Section 2 describes our research platfor for Service-oriented Reference Enterprise Architecture. Section 3 presents our new Enterprise Architecture Metaodel Integration approach for Service-oriented Enterprise Architectures and presents exeplar ontological representations for the & Inforation Reference Architecture in the context of ajor standards. Section 4 presents conclusions and outlines our ongoing research. 2. SERVICE-ORIENTED REFERENCE ENTERPRISE ARCHITECTURE The ESARC Enterprise Services Architecture Reference Cube [24] (see Figure 1) is ore specific and copletes existing architectural standards in the context of EAM Enterprise Architecture Manageent [22], [21], and [19] and extends these architecture standards for services and cloud coputing. ESARC is an original architecture reference odel, which provides a holistic classification odel with eight integral architectural doains. ESARC abstracts fro a concrete business scenario or technologies, but is applicable for concrete architectural instantiations. The OASIS Reference Model for Service Oriented Architecture [12] defines an abstract fraework, which guides our concept of reference architectures, as in [1], [7], and [18]. Reference odels are conceptual odels of a functional decoposition of odel eleents together with the data flows between the. The Reference Model for Service Oriented Architecture of OASIS [12] defines basic generic eleents and their relationships of a service-oriented architecture. This reference odel is not a standard, but provides a coon seantics for the ore specific reference architectures. Reference architectures, in [7] and [18], are specialized odels of a reference odel. Reference architectures provide a coposition of architectural eleents, which are built fro typed building blocks as the result of a pattern-based apping of reference odels to software concepts. The Open Group Architecture Fraework [19] provides the basic blueprint and structure for our extended service-oriented enterprise architecture doains (Figure 1) of ESARC [24], [25] Enterprise like: Architecture Architecture Manageent Governance, Architecture Manageent, ESARC - Enterprise and Inforation Software Architecture Architecture, Reference Inforation Cube Systes Architecture Architecture, Capability Technology Diagnostics, Architecture, Monitoring, Operation and Optiization Architecture, and Cloud Services Architecture. ESARC provides a coherent aid! ESARC defines an original holistic classification schee for cyclic diagnostics and optiization of eight types for (viewpoints) exaination, of service-oriented coparison, enterprise software classification, architectures quality evaluation and optiization of architectures. Hochschule Reutlingen! ESARC substantiates the TOGAF standard with other odels to provide a useful apping foundation of a reference architecture, defining ain architecture artifacts and their relationships 25 Alfred Zierann Figure and 1. SOA Enterprise Innovation Lab 2011 Services Architecture Reference Prof. Cube. Dr. Alfred Zierann Architecture Governance, as in [24], defines and aintains the Architecture Governance Cycle [22]. It sets the abstract governance frae for concrete architecture activities within the enterprise or a product line developent and specifies the following anageent activities: plan, define, enable, easure, and control. The second ai of Architecture Governance is to set rules for architecture copliance to internal and external standards. Enterprise and software architects are acting on a sophisticated connection path eanating fro business and IT strategy to the architecture landscape realization for interrelated business doains, applications and technologies. Architecture Governance has to set rules for the epowerent of people, defining the structures and procedures of an Architecture Governance Board, and setting rules for counication. We specify architecture governance odels for concepts such as: service strategy and life cycle anageent of software and syste architecture artifact s state, service security, service testing and onitoring, service contracts, registries, service reuse, service ownership, definition and versioning. The and Inforation Reference Architecture - BIRA [24-25] provides, for instance, a single source and coprehensive repository of knowledge fro which concrete corporate initiatives will evolve and link. This knowledge is odel-based and defines an integrated enterprise business odel, which includes organization odels and business processes. The BIRA opens a connection to IT infrastructures, IT systes, and software as well as security architectures. The BIRA confers the basis for business- IT alignent and therefore odels the business and inforation strategy, the organization, and ain business deands as well as requireents for inforation systes, such as key business processes, business rules, business products, services, and related business control inforation. The Inforation Systes Reference Architecture ISRA [24-25] is the application reference architecture and contains ain application-specific service types, defining their relationship by a layer odel of building services. The core functionality of doain services is linked with application interaction services and with the business processes of the custoer organization. In our

4 research we are considering the standard reference odels [12] and reference architectures [7] and [21] for services coputing. We have differentiated a consistent set of layered service types. The inforation services for enterprise data can be thought of as data centric coponents [24], providing access to the persistent entities of the business process. Close to the access of enterprise data are context anageent services, which are provided by the technology architecture: error copensation or exception handling, seeking for alternative inforation, transaction processing of both atoic and long running and prevalent distributed transactions. Process services [24] are long running services, which copose task services and inforation services into workflows, to ipleent the procedural logic of business processes. Process services can activate rule services, to swap out a part of the potentially unstable gateway-related causal decision logic. Process services are frontend by interaction services or by specific diagnostic service and process onitoring services. Often process services anage distributed data and application state indirectly, by activating task and inforation services. When processes services participate in huan interaction workflows, they have to support long-running transactions where copensation of possible errors or exceptions happens in the business logic. Cloud architectures are still under developent and have not reached so far their full potential in integrating EAM with Services Coputing and Cloud Coputing. Integrating and exploring these three architectural diensions into consistent reference architectures is a central part of our current research. The Cloud Services Reference Architecture provides a referenceodel-based synthesis of current standards and reference architectures fro [11], [2], and [3]. Today s developent of cloud coputing technologies and standards are growing very fast and provide a ore and ore standardized base for cloud products and service offerings. The NIST Cloud Coputing Reference Architecture [11] defines the Conceptual Reference Model fro the perspectives of the following Actors in Cloud Coputing: Cloud Consuer, Cloud Provider, Cloud Auditor, and the Cloud Broker. The NIST standard defines following deployent odels: private cloud, counity cloud, public cloud, and hybrid cloud. Cloud Coputing offers essential characteristics like: on-deand self-services, broad network access, resource pooling, rapid elasticity, and easured services. The fundaental part of the NIST Reference Architecture is defined by following Cloud Service Models: IaaS Infrastructure as a Service, PaaS Platfor as a Service, and SaaS Software as a Service. Soe Standard extensions like [2] provide practical additions for supporting ore directly odern business architectures by BPaaS Process as a Service and giving a direct link to Service-oriented Enterprise Architectures. The IBM Cloud Coputing Reference Architecture provides in [2] additionally to the standardization of NIST best-of-industry knowledge and cloud product specifications by integrating the NIST standard with own technology stacks, iddleware, as well as service-oriented prograing and runtie platfors. The IBM Cloud Coputing Reference Architecture [2] has integrated the basic NIST standard of the Cloud Coputing Reference Architecture [11] with the SOA Reference Architecture [18] fro the Open Group: All cloud services are SOA services, but not all SOA services are also Cloud services. The security additions fro the CSA Security Guidelines for Critical Areas of Focus in Cloud Coputing [3] defines a Jericho-Security-focused Service-oriented Reference Architecture for Cloud Coputing and integrates the anageent perspectives fro standards like ITIL and TOGAF [19]. The Service-Oriented Cloud Coputing (SOCCI) Fraework [20] is an enabling fraework for an integrated set of cloud infrastructure coponents. Basically it is the synergy of serviceoriented and cloud architectures by eans of a consistent As-a- Service-Mechanis for all types of cloud services. The basic characteristics of a Service-oriented Infrastructure (SOI) are: business-driven infrastructure on-deand, operational transparency, service easureent, and consuer provider odel. The SOCCI-Service-Oriented Cloud Coputing Fraework is the extension of the Service-oriented Infrastructure (SOI) apped to the SOA Reference Architecture [18]. The SOI- Fraework is the layer on top of the basic infrastructure and provides iportant eleents of SOCCI: Copute, Network, Storage, and Facilities. SOCCI extends these basic eleents of SOCCI by and Operational SOCCI Manageent Building Blocks. 3. ENTERPRISE ARCHITECTURE METAMODEL INTEGRATION METHOD Our originally developed integration odel ESAMI Enterprise Services Architecture Metaodel Integration [26] serves as an integration ethod for integrating systeatically base odels of enterprise architecture standards, like [19], [21], architecture fraeworks [5], [8], [6], [4], [13], and [14], etaodels fro practice and fro tools. ESAMI is based on our approach of correlation analysis and a systeatic integration process. Current work extends our basic service-oriented enterprise architecture odel fro ESARC by integrating EA-Models fro architecture fraeworks, fro books and conference papers, and fro etaodels of EAM-tools and specifications fro our industrial partners. To be able to integrate these resources efficiently and exactly we have developed ESAMI Enterprise Services Architecture Metaodel Integration, which is a correlation-based odel integration approach for service-oriented enterprise architectures with following steps: 1. Analyze fro each resource the structure of each Architecture Base Model using Concept Maps, 2. Extract the Base Viewpoint Model fro each resource: Viewpoint, Model, Eleent, Exaple, 3. Initialize the Architectural Reference Model fro Base Viewpoint Models: Viewpoint, Model, Eleent 4. Analyze Correlations (Concept Mappings) between Base Viewpoint Models and the Architectural Reference Model, and optionally conclude transitive correlations 5. Deterine Integration Options for the resulting Viewpoint Integration Model 6. Develop the Synthesis Metaodel fro Base Metaodels 7. Consolidate the Architectural Reference Model according the Synthesis Metaodel, and finally readjust Correlations and Integration Options 8. Develop the Viewpoint Map (Capability Map) and Ontology of the Architectural Reference Model 9. Develop Correspondence Rules between Model Eleents 10. Develop Patterns for Architecture Diagnostics and Optiization.

5 First we have to analyze and transfor given architecture resources with concept aps and extract their coarse-grained aspects in a standard way [26] by deliiting architecture viewpoints, architecture odels, their eleents, and illustrating these odels by a typical exaple. Architecture viewpoints are representing and grouping conceptual business and technology functions regardless of their ipleentation resources like people, processes, inforation, systes, or technologies. They extend these inforation by additional aspects like quality criteria, service levels, KPI, costs, risks, copliance criteria a. o. We are using odeling concepts fro ISI/IEC [5] like Architecture Description, Viewpoint, View, and Model. Architecture odels are coposed of their eleents and relationships, and are represented by architectural diagras. For each architecture resource we are extracting then a Base Viewpoint Model in a standardized way. Then we develop the odel of the initial Architectural Reference Model fro each Base Viewpoint Model. This first version of the Architectural Reference Model is the result of a siple union fro Base Viewpoint Models and could enclose redundant odel inforation. In the next step we extend the initial Architectural Reference Model (Figure 2) by analyzing odel correlations as quantified appings between analyzed architecture odels and by deriving synthesis or integration options for an optiized Enterprise Architectural Architecture Manageent Reference & Cloud Model. Coputing A Synthesis Metaodel of the ESAMI Base Metaodels Enterprise Services following Architecture the specifications Metaodel of Integration the Integration Consolidated Options supports EAM Reference this step. Architecture: Analysis and Integration Reference Origin ArchiMate Specific. and TOGAF Standard Viewpoint Activator Organization EAM Reference Model Correlation Index Integration Options Model Eleent ArchiMate TOGAF ArchiMate TOGAF Actor 2 2 p Role 3 2 Collaboration 3 0 ActorRole Organiz. 1 3 p Unit Function 3 3 p Event 3 3 Collaboration 3 0 Organiz. 0 Unit no 1 correlation 3 p Organi- Driver 1 3 low correlation 3 zation Location 2 Goal ediu correlation strong correlation Objective 3 3 Location 3 3 Docuents 9 SERVICE COMPUTATION 2013 Valencia, Inforatik 2013 Koblenz Prof. Dr. Alfred Zierann r p r r p File ESAMI Pages reject partially andatory (leading odel) 89 Figure 2. Correlation Analysis and Integration Options. Authors The Architecture Metaodel (Figure 3) is the base for the synthesized Architectural Reference Model, with its set up based on consolidated correlation and synthesis indicators fro (Figure 2). Finally we cluster the resulting Viewpoint Map as a base for the Capability Map with final their Models and Eleents. Ontologies, as in [25], [23], and [17], provide both a fundaental base for a clear understanding of the integrated architectural concepts and for additional knowledge representation and inference echaniss. We are currently researching about seantic-supported representations for service-oriented enterprise architectures to provide a base for easier navigation and siulation within the coplex space of enterprise architectures. The sei-autoated navigation between architectural concepts enables new functionalities for ipact anageent as well as for cyclic architecture evaluations and for real-tie architecture analytics, diagnostics and decision support. We are using etaodels [16], [26] to define architecture odel eleents and their relationships within ESARC. We use etaodels as an abstraction for architectural eleents and relate the to architecture ontologies [25], [26]. Architecture ontologies represent a coon vocabulary for enterprise architects who need to share their inforation based on explicitly defined concepts. Ontologies include the ability to autoatically infer transitive knowledge. The Metaodel of the & Inforation Reference Architecture BIRA consists of ESARC-specific concepts, which are derived as specializations Hochschule fro Reutlingen Enterprise Architecture Manageent generic concepts such as Eleent and Coposition fro the Open ESAMI Enterprise Services Architecture Metaodel Integration Group s SOA Ontology SOA Typed Ontology Metaodel [17]. of Reference Architecture Collaboration (HuanActor) Organization Unit Location Knowledge Skills Role (HuanActor) Actor (HuanActor) Driver Goal Objective Function Event Process (Process) Service (Service) Service Quality (Thing) Contract (ServiceContract) Coposite (Coposition) Inforation (Inforation Type) Representation Product Rule Eleent Meaning Value Figure 3. Ontology-supported Architecture Metaodel. 27 Prof. Dr. Alfred Zierann The technical standard of Service-oriented Architecture Ontology fro [17] defines core concepts, terinology, and seantics of a service-oriented architecture in order to iprove the alignent between the business and IT counities. In our understanding architecture ontologies represent a coon vocabulary for enterprise architects who need to share their inforation based on explicitly defined concepts. Ontologies include the ability to infer autoatically transitive knowledge. Our developed ontology for ESARC ([25], [26] and Figure 3) follows [17] has soe practical reasons: share the coon understanding of the ESARC Architecture doains and their structures, reuse of the architectural knowledge, ake architectural requireents, structures, building blocks explicit and proote reusability of architectural artifacts, separate the architectural knowledge according orthogonal architectural doains, classify, analyze, diagnose enterprise systes according to the service-oriented reference architecture od ESARC. The SOA ontology represents core concepts of a generic serviceoriented architecture as classes and properties. The SOA ontology includes in addition natural language descriptions of ain concepts and relationships UML diagras, which show graphically the seantic concepts as classes and the properties as UML associations. The UML diagras are intended for explanation only, but are helpful constructs for understanding the odeled doain of SOA architecture and ore concise than the ore spacious foral descriptions in OWL. The SOA ontology defines the relations between seantic concepts, without entioning the exact usage of these architecture concepts. We have developed the ESARC Ontology, as in [9], and [10], and defined ontology concepts for ESARC using the ontology editor Protégé [15]. We have erged our specialized ESARC Ontology with the generic SOA Ontology fro [17]. The so-called Asserted View fro Protégé shows the is-a-relationship between specific concepts of the & Inforation Reference Architecture and the Open Group s generic SOA Ontology Reference Architecture. The terinal concepts are specific concepts of ESARC. In Figure 3 we point within parentheses to the linked generic concepts of the SOA Ontology. Additionally we have deterined knowledge properties for the odeled ontology concepts of ESARC. Using the ESARC ontology we intend

6 further to navigate easier within the coplex space of enterprise architecture anageent structures and to enable seanticsupported decisions and ore transparency for stakeholders. 4. CONCLUSION AND FUTURE WORK The basic approaches within each field are already well known and used. However, those are not directly applicable and properly integrated for decision-support in service-oriented enterprise engineering and architectures. Our ontology approach for Serviceoriented Enterprise Architectures for cloud-based inforation systes extends previous research about seantic support through ontologies for service-oriented reference architectures, reference ipleentations and reference odels for EAM - Enterprise Architecture Manageent for Services & Cloud Coputing, the odels of ESARC - Enterprise Services Architecture Reference Cube, as well as associated architecture etaodels, ontologies and architecture patterns. Our approach provides a sound basis for architecture decision support fro theory and fro practical evaluations of service-oriented platfors in heterogeneous environents with four ajor global technology providers, like IBM, SAP, ORACLE, and Microsoft, and vendors of Enterprise Architecture Manageent tools. Future work will include conceptual work on both static and dynaic architecture coplexity, and in connecting architecture quality procedures with prognostic processes on architecture aturity with siulations of enterprise and software architectures. Additional iproveent opportunities will focus on ethods for ipact anageent, decision linking, visualization of architecture artifacts and architecture control inforation, which has to be operable in an architecture anageent cockpit. 5. ACKNOWLEDGMENTS This work was partially supported by the SOA Innovation Lab. 6. REFERENCES [1] Bass, C., Cleents, P., and Kazan, R Software Architecture in Practice. Addison Wesley. [2] Behrendt, M., Glaser, B., Kopp, P., Diekann, R., Breiter, G., Pappe, S., Kreger, H., and Arsanjani, A Introduction and Architecture Overview IBM Cloud Coputing Reference Architecture 2.0. IBM. [3] CSA Cloud Security Alliance Security Guidance for Critical Areas of Focus in Cloud Coputing V2.1. [4] DoDAF DoDAF Architecture Fraework. Version 2.0, Volue 1, Departent of Defense USA, 28 May [5] Eery, D., and Hilliard, R Every Architecture Description needs a Fraework: Expressing Architecture Fraeworks Using ISO/IEC In IEEE/IFIP WICSA/ECSA 2009, pp [6] Essential Architecture Project last access: May 19, [7] Estefan, J. A., Laskey, K., McCabe, F. G., and Thornton, D OASIS Reference Architecture for Service Oriented Architecture. Version 1.0, OASIS Public Review Draft 1, April 23, [8] Firesith, D. G. with Capell, P., Falkenthal, D., Haons, C. B., Latier, D., and Merendino, T The Method Fraework for Engineering Syste Architectures. CRC Press - Taylor & Francis Group. [9] Gasevic, D., Djuric, D., and Devedzic, V Model Driven Engineering and Ontology Developent. 2 nd Edition, Springer. [10] Horridge, M., and Knoblauch, H., Rector, A., Stevens, R., Wroe, C., Jupp, S., Moulton, G., and Druond, N A Practical Guide To Building OWL Ontologies Using Protégé 4 and CO-ODE Tools. Edition 1.2. The University of Manchester. [11] Liu, F., Tong, J., Mao, J., Bohn, R., Messina, J., Badger, L., and Leaf, D NIST Cloud Coputing Reference Architecture. US Departent of Coerce NIST SP [12] MacKenzie, C. M., Laskey, K., McCabe, F., Brown, P. F., and Metz, R OASIS Reference Model for Service Oriented Architecture 1.0. OASIS Standard. [13] MODAF MOD Architectural Fraework, Executive Suary, Version 1.0, 31 August, Ministry of Defense UK. [14] NAF NATO Architecture Fraework. Version 3. [15] Noy, N. F., and McGuiness, D. L Ontology Developent 101: A Guide to Creating Your First Ontology. Stanford University, USA. [16] OMG Meta Object Facility (MOF). Core Specification. Version 2.0, Object Manageent Group. [17] Open Group Service-Oriented Architecture Ontology. Technical Standard. The Open Group. [18] Open Group 2011a. SOA Reference Architecture. The Open Group. [19] Open Group 2011b. TOGAF The Open Group Architecture Fraework. Version-9.1, The Open Group. [20] Open Group 2011c. Service-Oriented Cloud Coputing Infrastructure (SOCCI) Fraework. The Open Group. [21] Open Group ArchiMate 2.0 Specification. Open Group Standard. The Open Group. [22] Ross, J. W., Weill, P., and Robertson, D Enterprise Architecture as Strategy Creating a Foundation for Execution. Harvard School Press. [23] Youseff, L., Butrico, M., and Da Silva, D Towards a Unified Ontology of Cloud Coputing. In: Grid Coputing Environents Workshop (GCE# 08), Nov. 2008, pp [24] Zierann, A., Buckow, H., Groß, H.-J., Nandico, O. F., Piller, G., and Prott, K Capability Diagnostics of Enterprise Service Architectures using a dedicated Software Architecture Reference Model. In IEEE-SCC2011: Washington DC July 5-10, 2011, pp [25] Zierann, A., and Zierann G Enterprise Architecture Ontology for Services Coputing. In Proc. of SERVICE COMPUTATION 2012: Nice France, July 22-27, 2012, ISBN , pp [26] Zierann, A., Sandkuhl, K., Pretz, M., Falkenthal, M., Jugel, D., and Wissotzki, M Metaodell-basierte Integration von Service-orientierten EA- Referenzarchitekturen. Inforatik 2013, Septeber 16-20, Koblenz, Gerany, Lecture Notes in Inforatics (to appear)