Interface-based enterprise and software architecture mapping
|
|
- Marcia Ross
- 6 years ago
- Views:
Transcription
1 Interface-based enterprise and software architecture mapping Aziz Ahmad Rais Department of Information Technologies University of Economics, Prague Prague, Czech Republic DOI: /jsi.v7i2.253 Abstract: Information technology (IT) becomes more and more complex because of various technologies, methodologies, techniques and practices. Even though the goal of all technologies, methodologies, practices and techniques is to facilitate construction, to simplify, and to increase the reusability of information systems, in practice integrating all these becomes a challenge. This challenge can be met by creating more abstract levels in the information systems in question. Higherlevel abstraction simplifies different views of complex problems, but at the same time it generates a knock-on issue regarding how actually to implement such an abstract-level view, and/or how to map it back to the lower levels of abstraction. The goal of this article is to simplify the implementation of enterprise architecture and map it to software architecture using an interface-based analysis technique. In order to achieve this goal, service-oriented architecture (SOA), which is composed of multiple concepts, will be used. The concepts are flexible, so they can be applied in enterprise architecture as well as in software architecture. Key words: TOGAF, enterprise architecture, service-oriented architecture (SOA), software architecture 1. Introduction In order to simplify and implement enterprise architecture using service-oriented architecture (SOA), we first need to describe the fundamentals of both architectures styles. The architecture style according to the ISO/IEC/IEEE (2010) is characterization of a family of systems that are related by sharing structural and semantic properties. This means finding commonalities between enterprise architecture and SOA structure and semantic properties to map, or rather to integrate them. Service-oriented architecture is a paradigm applicable in different types of architecture, such as, for example, software architecture, component design, enterprise architecture, and so on. In other words, the Open Group's SOA Working Group (SOA, 2009) explains SOA as follows: Service-Oriented Architecture (SOA) is an architectural style that supports service orientation. Service orientation is a way of thinking in terms of services and service-based development and the outcomes of services. A service: Is a logical representation of a repeatable business activity that has a specified outcome (e.g., check customer credit; provide weather data, consolidate drilling reports) 1. Is self-contained 2. May be composed of other services 3. Is a black box to consumers of the service Other standards, like the advancing open standards for the information society (OASIS, 2006), describe SOA as a paradigm with the following concepts: visibility, interaction, real-world effect, execution context, contract and policy, service description, and service. According to both standards, the concept of service is key for SOA. However, OASIS defines the concept of service as: JOURNAL OF SYSTEMS INTEGRATION 2016/2 33
2 AZIZ AHMAD RAIS 1. The capability to perform work for another 2. The specification of the work offered for another 3. The offer to perform work for another Sometimes, SOA is described as an integration concept, (Schmutz, 2010), for which, for example, an enterprise service bus can be used (ESB). The service is orchestrated as independent, distributed service calls, as in the following diagram: Fig. 1: Service-oriented architecture (Schmutz, 2010) The ESB has the capability of orchestrating requests, and supports the collaboration between different systems in a decoupled way. The interpretation of SOA as an integration concept is also implied by the Open Group s definition of SOA provided above, especially by its third sub-definition. Following from the above definitions and concepts, any implementation without the use of reference architecture would hinder SOA construction. SOA reference architecture offers another view of SOA. According to The Open Group Standard Group s clarification of SOA reference architecture (SOA Ref. Arch, 2011), SOA is composed of layers that are divided into two types: the logical (the Service Component Layer, the Services Layer, the Business Process Layer, and the Consumer Layer) and the physical (Operational Systems Layer). Fig. 2: Logical Solution View of the SOA RA (The Open Group Standard, 2011) 34 JOURNAL OF SYSTEMS INTEGRATION 2016/2
3 INTERFACE-BASED ENTERPRISE AND SOFTWARE ARCHITECTURE MAPPING The layers can be identified as follows: Governance Layer (availability, registries and repositories), Integration Layer, Quality of Service Layer (administration, monitoring and management) and the Information Layer (defining events) support five vertical layers. In practice, a supportive layer means an optional layer. Thus, if architecture does not implement them but is nevertheless service-driven, it can still be labeled SOA. The architecture development method (ADM) explained by the Open Group Architecture Framework, describes enterprise architecture, like SOA, as the composition of multiple layers (TOGAF, 2011). This is illustrated in the diagram below: Enterprise architecture Business architecture layer System architecture layer Application architecture layer Data architecture layer Technology architecture layer Fig. 3: Layered view of enterprise architecture (the author) Business architecture is mainly about business services composed of business functions and business processes. Application architecture provides application components that implement the business service. The technology layer is composed of all the technologies, such as operation systems, networks, hardware, application servers, and so on. In other words, technology architecture is the operation layer of the application architecture. According to SOA, it is necessary to develop service components in order to implement enterprise architecture. The service component can be implemented by one or more software components. The software component will refer to a software system or an element, such as module, unit, data, or document as defined by SO/IEC/IEEE (2010). For the development of the software component, we need the service-oriented software architecture to involve different types of software design methods, like, for example the design methods as mentioned by (IEEE Computer Society, 2014): object-oriented design, component-based design, function-oriented (structure) design, and data-structure design. 2. Mapping enterprise architecture to SOA The term service is generic and can be applied at different system levels, such as, for example, those of business system, information system and software system. Thus, when we make each of these three systems service oriented, the results will be business service, information system service, and software service. According to the open group architecture framework in (TOGAF, 2011), the information system service is: The automated elements of a business service. An information system service may deliver or support part or all of one or more business services. By identifying the layers of enterprise architecture and SOA, we can find the proper layer of business service. In enterprise architecture, business service are delivered by the business domain, and thus by business architecture. According to the SOA paradigm, business service is involved in the business JOURNAL OF SYSTEMS INTEGRATION 2016/2 35
4 AZIZ AHMAD RAIS process layer and service layer. The consumer layer can be another information system service, or human. In both cases, the goal of SOA is to design a service from a consumer perspective. Thus, the consumer layer is also part of business service. The service components in the service component layer of SOA reference architecture are one or more software components that can share or run in separate runtime environments. In TOGAF, application architecture is understood as A description of the structure and interaction of the applications as groups of capabilities that provide key business functions and manage the data assets. Every application in application architecture can be considered application software, because the latter is, according to the SO/IEC/IEEE (2010) definition, software or a program that helps the user perform a task or a business function, and manage the data asset. In conclusion, application software can itself be a software component. To conclude, the TOGAF information system service which is composed of application and data architecture is actually equivalent to SOA service components layer. The operation layer in SOA is the runtime environment for software components, and is equivalent to technology architecture. Technology architecture, according to TOGAF, is a service platform provided by technologies such as the operation system, network, hardware, and devices that all together create runtime environments for application software (TOGAF, 2011). Last, to use SOA within enterprise architecture, or to build service-oriented enterprise architecture, we need to carry out the mapping below. The conclusion above can also be inferred from the Open Group s explanation of SOA, which appears in The Open Group's SOA Working Group (SOA, 2009) as follows: An enterprise architect looks at the overall construction of the enterprise. SOA is a particular construction technique that can be used to build enterprise IT. Enterprise architecture SOA layers Business architecture layer equivalent Business service Consumer layer System architecture layer Business process layer Application architecture layer service layer Data architecture layer equivalent Serv ice component layer Technology architecture layer equivalent Operation layer Fig. 4: Mapping enterprise architecture to SOA (the author) 3. Mapping software architecture to SOA Software architecture can also be composed of multiple layers, implies from (VOŘÍŠEK, 2008). Each layer can be created based on a particular concern. These concerns can be, for example, how users will employ the software functionalities and how to access them (the presentation layer); what types of functionality the software will provide (the software service layer); how to reuse the functionalities of other software or software services (the integration layer or, for example, with the help of an ESB); how software will gather and store or keep the business data; or, finally, what technologies to use for software construction and for runtime software (the technology layer or operation layer). The integration layer helps the software layer compose software services from other software services. Based on the concerns outlined here, an example of application software can be composed from the following layers: 36 JOURNAL OF SYSTEMS INTEGRATION 2016/2
5 INTERFACE-BASED ENTERPRISE AND SOFTWARE ARCHITECTURE MAPPING Software architecture Presentation layer Software serv ice layer Service interface Data access layer Integration layer Data layer Operation layer Fig. 5: Example of multi-layer software architecture (the author) Multi-layer software architecture makes mapping software architecture to SOA easy, because the layers are similar in both types. The functionality provided by the software-service layer in software architecture has lower granularity than the information system service in enterprise architecture. The presentation layer in software architecture is the same as the consumer layer in SOA; it presents the software service to the user or consumer. The presentation layer also controls and executes the business process. The business process consumes the software service implemented by the software service layer. Service-component implementation by software has to be done in multiple sub-layers, because software has to be composed from objects, classes, and methods. According to Service oriented architecture Modeling Language in (SoaML, 2012), a software service model is composed of various objects: interface, concrete instance, request, channel, and service data. Additionally, a software service needs other objects: participants, contracts and capabilities. The first five SoaML objects are also important for model-driven architecture and development (OMG MDA, 2014), because the model can be transformed into software source code skeletons. So the service layer in 0 represents the software service interface, and the concrete instance of the service is composed by invoking the data access and integration layers. The data layer in 0 represents the service data gathered from the incoming request. The following diagram maps multi-layered software architecture to SOA reference architecture as illustrated in 0: JOURNAL OF SYSTEMS INTEGRATION 2016/2 37
6 AZIZ AHMAD RAIS SW architecture layers Presentation layer SOA Layers Consumer layer Serv ice component layer Business process layer Software service layer Service interface Service layer Data access layer Integration layer Serv ice component layer Data layer Operation layer Operation layer Fig. 6: Mapping software architecture to SOA (the author) 4. Mapping enterprise architecture to software architecture In the two types of mapping outlined above, we identified that the linchpin of integration between all architecture styles is the service layer. Thus, by mapping the service layers properly, we will be able to produce accurate enterprise architecture. This means mapping technologies and technology architecture will not cause any complexity when business services are implemented in an enterprise. Software service components are identified by SoaML and, in order to compare and map between both types of service, we need to understand business service. The TOGAF Core Content Metamodel in (TOGAF, 2011) shows that the main business service components are Process, Function, Role, Actor, and Organization Unit); see the diagram below: Fig. 7: Relationship between business service components and entities in the TOGAF Core Content Metamodel (The Open Group Standard, 2011) 38 JOURNAL OF SYSTEMS INTEGRATION 2016/2
7 INTERFACE-BASED ENTERPRISE AND SOFTWARE ARCHITECTURE MAPPING The most important implication of the TOGAF Core Content Metamodel is that business service is realized through the application component (in the Core Metamodel, the application component is the application software component). In the section entitled Mapping enterprise architecture to SOA, it was shown that the application component can be one or more software components. Furthermore, each software component provides a software service to support the business service, as described in the section entitled Mapping software architecture to SOA. To summarize, it has been clarified that, from a component perspective, business service and software service are the same, and the former uses the latter for its realization. In addition, the TOGAF Core Content Metadmodel implies on the one hand that business service involves the whole organization in its process, and the consumer of the business service s process and functions is human. On the other hand, software service involves only part of the organization, and its consumer can also be other software. The goal of this article is to simplify the implementation and understanding of enterprise architecture, and we can see that the key to mapping between business service and software service is mapping the interfaces of both services. Business service or business architecture can be described using the enterprise architecture modeling language ArchiMate, which is an extension of UML, or by using UML itself (ArchiMate, 2013). Due to the fact that ArchiMate provides different meta-objects, which can cause additional complexity, UML used with the proper stereotypes is sufficient for mapping and understanding enterprise architecture and software architecture. According to BABOK in (IIBA, 2009), an information system can be described with the use of interface analysis techniques. TOGAF defines an information system as a combination of application software and data (TOGAF, 2011). Further, ISO/IEC/IEEE (2010) describes it as a processing system associated with organization assets, such as human resources, technical resources, and financial resources. Combining these definitions, therefore, we can understand application software and data as technical resources consumed by organization employees, handling finances, and likewise requiring financial investment themselves. Moreover, according to the TOGAF Core Content Metadmodel, a service is bounded by the functions that can be grouped in an interface. Consequently, the following enterprise architecture model is constructed with the help of an interface, and describes only the information-system part of the enterprise. The example of an information system in 0 below models an enterprise providing a service of flower sales, which is composed of several sub-services: flower ordering, flower delivery, and accounting. «organization» Enterprise «business service» Enterprise::Flower sales service «business sub-service» Enterprise::Flower ordering serv ice «business sub-service» Enterprise::Flower deliv ery serv ice «business sub-service» Enterprise::Accounting service Business process Order flowers Order recieved record order Accounting activities record delivery StartFlowerOrder Client&Order Client&flower&deliveryaddress Deliver flowers Pay cash (if payment method is cash) realized Client registration Flower display Flower order Delivery address Payment method Delivery method Application software component : Fig. 8: Information-system model and its mapping to the application software component (the author) JOURNAL OF SYSTEMS INTEGRATION 2016/2 39
8 AZIZ AHMAD RAIS From the TOGAF Core Content Metadmodel, we already know that a service is realized by a process, and this process will, therefore, be mapped to the interfaces of an application software component. The following model describes how the ordering service processes are mapped to the interfaces of an application software component. StartOrderProcess Client registration Select flowers Enter delivery address Choose delivery method Choose payment method Submit order Client registration Flower display Delivery address Delivery method Payment method Flower order Application software component Fig. 9: Mapping a business process supported by an applicaion software component (the author) 5. Conclusion In the introduction section, we saw a high-level description of the SOA concepts used to describe enterprise architecture in a service-oriented way. Mapping between both types of service is simplified because software can also be service oriented, thereby removing technology architecture from enterprise and software architecture. The TOGAF concept of service implies that the latter is implemented by a business process or a process in general, and is bounded by functions. As a result, we can group functions into interfaces and map them to processes. Thus, the example of the business service and information system of enterprise architecture of a flower sales business, with its three types of sub-service, was described with the use of interfaces, where one service interface was mapped for demonstration to the application software services through mapping the sub-process of the flower order service to the interfaces of an application software component. References Advancing open standards for the information society (OASIS), 2006: Reference Model for Service Oriented Architecture 1.0. [online] OASIS Standard, 12 October Available at: [Accessed 10 March 2016] IEEE Computer Society, 2014: Guide to the Software Engineering Body of Knowledge. Version 3.0. A Project of the IEEE Computer Society. New York: Pierre Bourque, Richard E., ISBN-13: , pp. 59 International Institute of Business Analysis (IIBA), 2009: A Guide to the Business Analysis Body of Knowledge (BABOK Guide), Version 2.0. Toronto: IIBA, ISBN-13: pp International Organization for Standardization (ISO/IEC/IEEE 24765), Systems and software engineering Vocabulary Object Management Group (OMG MDA), 2014: Model Driven Architecture (MDA) MDA Guide rev [Online] OMG Document ormsc/ Available at: 01.pdf [Accessed 12 March 2016] Schmutz Guido, Liebhart Daniel, Welkenbach Peter, 2010: Service-Oriented Architecture: An Integration Blueprint. Birmingham:Packt Publishing Ltd. ISBN , pp Service oriented architecture Modeling Language, 2012: Service oriented architecture Modeling Language (SoaML) Specification. [online] Version 1.0.1, Available at: [Accessed 10 March 2016] The Open Group's SOA Working Group (SOA), 2009: SOA Source Book. [online] First Edition, Available at: [Accessed 5 March 2016] The Open Group Standard (SOA Ref. Arch.), 2011: SOA Reference Architecture. Document Number: C119. ISBN: JOURNAL OF SYSTEMS INTEGRATION 2016/2
9 INTERFACE-BASED ENTERPRISE AND SOFTWARE ARCHITECTURE MAPPING The Open Group Standard (TOGAF), 2011: The open group architecture framework. Version 9.1, Document Number: G116. ISBN: The Open Group Standard (ArchiMate), 2013: ArchiMate 2.1 Specification. ISBN: Voříšek, J. a kol., 2008: Principy a modely řízení podnikové informatiky. Praha:Oeconomica. ISBN pp 118. JEL: L86, M15 JOURNAL OF SYSTEMS INTEGRATION 2016/2 41
The Open Group SOA Ontology Technical Standard. Clive Hatton
The Open Group SOA Ontology Technical Standard Clive Hatton The Open Group Releases SOA Ontology Standard To Increase SOA Adoption and Success Rates Ontology Fosters Common Understanding of SOA Concepts
More informationStandard SOA Reference Models and Architectures
Standard SOA Reference Models and Architectures The Open Group Perspective 4 February 2009 Dr Christopher J Harding Forum Director Tel +44 774 063 1520 (mobile) c.harding@opengroup.org Thames Tower 37-45
More informationOMG Specifications for Enterprise Interoperability
OMG Specifications for Enterprise Interoperability Brian Elvesæter* Arne-Jørgen Berre* *SINTEF ICT, P. O. Box 124 Blindern, N-0314 Oslo, Norway brian.elvesater@sintef.no arne.j.berre@sintef.no ABSTRACT:
More informationQoS-aware model-driven SOA using SoaML
QoS-aware model-driven SOA using SoaML Niels Schot A thesis submitted for the degree of MSc Computer Science University of Twente EEMCS - TRESE: Software Engineering Group Examination committee: Luís Ferreira
More informationDesigning a System Engineering Environment in a structured way
Designing a System Engineering Environment in a structured way Anna Todino Ivo Viglietti Bruno Tranchero Leonardo-Finmeccanica Aircraft Division Torino, Italy Copyright held by the authors. Rubén de Juan
More informationEvent Metamodel and Profile (EMP) Proposed RFP Updated Sept, 2007
Event Metamodel and Profile (EMP) Proposed RFP Updated Sept, 2007 Robert Covington, CTO 8425 woodfield crossing boulevard suite 345 indianapolis in 46240 317.252.2636 Motivation for this proposed RFP 1.
More informationDomain-Driven Development with Ontologies and Aspects
Domain-Driven Development with Ontologies and Aspects Submitted for Domain-Specific Modeling workshop at OOPSLA 2005 Latest version of this paper can be downloaded from http://phruby.com Pavel Hruby Microsoft
More informationBSIF. A Freeware Framework for. Integrated Business Solutions Modeling. Using. Sparx Systems. Enterprise Architect
33 Chester Rd Tawa 5028 Wellington New Zealand P: (+64) 4 232-2092 m: (+64) 21 322 091 e: info@parkconsulting.co.nz BSIF A Freeware Framework for Integrated Business Solutions Modeling Using Sparx Systems
More informationExperimental transformations between Business Process and SOA models
International Journal of Informatics Society, VOL.4, NO.2 (2012) 93-102 93 Experimental transformations between Business Process and SOA models Akira Tanaka, and Osamu Takahashi view5 LLC, Japan School
More informationArchitecture Viewpoint Template for ISO/IEC/IEEE 42010
Architecture Viewpoint Template for ISO/IEC/IEEE 42010 Rich Hilliard r.hilliard@computer.org VERSION 2.1b Abstract This is a template for specifying architecture viewpoints in accordance with ISO/IEC/IEEE
More informationiserver Free Archimate ArchiMate 1.0 Template Stencil: Getting from Started Orbus Guide Software Thanks for Downloading the Free ArchiMate Template! Orbus Software have created a set of Visio ArchiMate
More informationBUSINESS ARCHITECTURE AND THE OPEN GROUP I A S A e S u m m i t
BUSINESS ARCHITECTURE AND THE OPEN GROUP 2 0 17 I A S A e S u m m i t OVERVIEW Introduction to the organizations The Business Architecture Guild and the Business Architecture Framework The Open Group and
More informationConceptual Modeling and Specification Generation for B2B Business Processes based on ebxml
Conceptual Modeling and Specification Generation for B2B Business Processes based on ebxml HyoungDo Kim Professional Graduate School of Information and Communication, Ajou University 526, 5Ga, NamDaeMoonRo,
More information6. The Document Engineering Approach
6. The Document Engineering Approach DE + IA (INFO 243) - 11 February 2008 Bob Glushko 1 of 40 Plan for Today's Class Modeling Methodologies The Document Engineering Approach 2 of 40 What Modeling Methodologies
More information1 Executive Overview The Benefits and Objectives of BPDM
1 Executive Overview The Benefits and Objectives of BPDM This is an excerpt from the Final Submission BPDM document posted to OMG members on November 13 th 2006. The full version of the specification will
More informationSolution Architecture Template (SAT) Design Guidelines
Solution Architecture Template (SAT) Design Guidelines Change control Modification Details Version 2.0.0 Alignment with EIRA v2.0.0 Version 1.0.0 Initial version ISA² Action - European Interoperability
More informationwebmethods EntireX for ESB: Leveraging Platform and Application Flexibility While Optimizing Service Reuse
December 2008 webmethods EntireX for ESB: Leveraging Platform and Application Flexibility While Optimizing Service Reuse By Chris Pottinger, Sr. Manager Product Development, and Juergen Lind, Sr. Product
More informationRich Hilliard 20 February 2011
Metamodels in 42010 Executive summary: The purpose of this note is to investigate the use of metamodels in IEEE 1471 ISO/IEC 42010. In the present draft, metamodels serve two roles: (1) to describe the
More informationDeveloping Software Applications Using Middleware Infrastructure: Role Based and Coordination Component Framework Approach
Developing Software Applications Using Middleware Infrastructure: Role Based and Coordination Component Framework Approach Ninat Wanapan and Somnuk Keretho Department of Computer Engineering, Kasetsart
More informationConceptual Framework
ArchiMate in a Nutshell v11 Conceptual Framework Generic Meta Model / Framework / Meta Model Creative Commons Attribution-No Derivative Works Licence 2.0 Attribution: You may copy, distribute and display
More informationEnterprise Architecture Modelling with ArchiMate 3 - Overview
Enterprise Architecture Modelling with ArchiMate 3 - Overview Knut Hinkelmann Reference The ArchiMate 3 specification is available at http://pubs.opengroup.org/architecture/archimate3-doc/ It is referenced
More informationIntroducing the UML Eng. Mohammed T. Abo Alroos
Introducing the UML Eng. Mohammed T. Abo Alroos Islamic University of Gaza Introduction to the UML: The UML stands for Unified Modeling Language. It was released in 1997 as a method to diagram software
More informationHPE Enterprise Maps Data Model, ArchiMate, TOGAF. HPE Software, Cloud and Automation
HPE Enterprise Maps Data Model, ArchiMate, TOGAF HPE Software, Cloud and Automation Data Model Enterprise Maps ArchiMate Overview Modeling language for EA 2002-2004 - NL university + government + industry
More informationSemantic Reconciliation in Interoperability Management through Model-driven Approach
Semantic Reconciliation in Interoperability Management through Model-driven Approach Frédérick Bénaben 1, Nicolas Boissel-Dallier 1,2, Jean-Pierre Lorré 2, Hervé Pingaud 1 1 Mines Albi Université de Toulouse,
More informationProposed Revisions to ebxml Technical. Architecture Specification v1.04
Proposed Revisions to ebxml Technical Architecture Specification v1.04 Business Process Team 11 May 2001 (This document is the non-normative version formatted for printing, July 2001) Copyright UN/CEFACT
More informationModeling Web Services with RoaML
26 Economy Informatics vol. 15, no. 1/2015 Modeling Web Services with RoaML Cătălin STRÎMBEI, Georgiana OLARU (AVRAM) Al. I. Cuza University of Iasi linus@uaic.ro, geo.olaru@gmail.com In this paper we
More informationIntroduction in the Dragon1 open EA Method
Introduction in the Dragon1 open EA Method Dragon1 starts the third wave in Enterprise Architecture: Entering the era of Visual EA Management Overview Revision date: 28 November 2013 Management Overview
More informationBusiness Architecture Implementation Workshop
Delivering a Business Architecture Transformation Project using the Business Architecture Guild BIZBOK Hands-on Workshop In this turbulent and competitive global economy, and the rapid pace of change in
More informationAlignment of Business and IT - ArchiMate. Dr. Barbara Re
Alignment of Business and IT - ArchiMate Dr. Barbara Re What is ArchiMate? ArchiMate is a modelling technique ("language") for describing enterprise architectures. It presents a clear set of concepts within
More informationObject Management Group Model Driven Architecture (MDA) MDA Guide rev. 2.0 OMG Document ormsc/
Executive Summary Object Management Group Model Driven Architecture (MDA) MDA Guide rev. 2.0 OMG Document ormsc/2014-06-01 This guide describes the Model Driven Architecture (MDA) approach as defined by
More informationINTRODUCING A MULTIVIEW SOFTWARE ARCHITECTURE PROCESS BY EXAMPLE Ahmad K heir 1, Hala Naja 1 and Mourad Oussalah 2
INTRODUCING A MULTIVIEW SOFTWARE ARCHITECTURE PROCESS BY EXAMPLE Ahmad K heir 1, Hala Naja 1 and Mourad Oussalah 2 1 Faculty of Sciences, Lebanese University 2 LINA Laboratory, University of Nantes ABSTRACT:
More informationFundamentals to Creating Architectures using ISO/IEC/IEEE Standards
Fundamentals to Creating Architectures using ISO/IEC/IEEE Standards What to Architect? How to Architect? IEEE Goals and Objectives Chartered by IEEE Software Engineering Standards Committee to: Define
More informationAUTOMATED BEHAVIOUR REFINEMENT USING INTERACTION PATTERNS
MASTER THESIS AUTOMATED BEHAVIOUR REFINEMENT USING INTERACTION PATTERNS C.J.H. Weeïnk FACULTY OF ELECTRICAL ENGINEERING, MATHEMATICS AND COMPUTER SCIENCE SOFTWARE ENGINEERING EXAMINATION COMMITTEE dr.
More informationMetadata Management and Change Management for SOA. Ron Schmelzer And Jason Bloomberg ZapThink, LLC. October 25, Take Credit Code: MMCMSOA
Metadata Management and Change Management for SOA Ron Schmelzer And Jason Bloomberg ZapThink, LLC October 25, 2005 Take Credit Code: MMCMSOA What are Metadata? Literally, data about data More broadly,
More informationData and Process Modelling
Data and Process Modelling 8a. BPMN - Basic Modelling Marco Montali KRDB Research Centre for Knowledge and Data Faculty of Computer Science Free University of Bozen-Bolzano A.Y. 2014/2015 Marco Montali
More informationRequirements to models: goals and methods
Requirements to models: goals and methods Considering Garlan (2000), Kruchen (1996), Gruunbacher et al (2005) and Alter (2006-08) CIS Department Professor Duane Truex III Wojtek Kozaczynski The domain
More informationSoftware Language Engineering of Architectural Viewpoints
Software Language Engineering of Architectural Viewpoints Elif Demirli and Bedir Tekinerdogan Department of Computer Engineering, Bilkent University, Ankara 06800, Turkey {demirli,bedir}@cs.bilkent.edu.tr
More informationModel Driven Production of Domain-Specific Modeling Tools
Model Driven Production of Domain-Specific Modeling Tools Bassem KOSAYBA, Raphaël MARVIE, Jean-Marc GEIB Laboratoire d Informatique Fondamentale de Lille UMR CNRS 8022 59655 Villeneuve d Ascq {kosayba,marvie,geib}@lifl.fr
More informationThe ATCP Modeling Framework
The ATCP 2+9+1 Modeling Framework Bobbi Underbakke Adaptive Team Collaboration, Inc. 800.837.0677 atcprocess.com Adaptive Team Collaboration, Inc. March 22, 2005 Chris Armstrong Armstrong Process Group,
More informationEnterprise Architecture Views and Viewpoints in ArchiMate
member of Enterprise Architecture Views and Viewpoints in ArchiMate ArchiMate 3 Chapter 14 The Core of Architecture Description http://www.iso-architecture.org/ieee-1471/cm/ Architecture Views and Viewpoints
More informationTOGAF Framework and ArchiMate Modeling Language Harmonization
ArchiMate and TOGAF Aligning core concepts Symbols (boxes & lines) Concept framework Relations 1. order and derivation 2. grouping 3. realisation Diagram types Find this and related slide shows on the
More informationArchiMate 2.0. Structural Concepts Behavioral Concepts Informational Concepts. Business. Application. Technology
ArchiMate Core Structural Concepts Behavioral Concepts Informational Concepts interaction Technology Application Layer Concept Description Notation Concept Description Notation Actor An organizational
More informationAn Information Model for High-Integrity Real Time Systems
An Information Model for High-Integrity Real Time Systems Alek Radjenovic, Richard Paige, Philippa Conmy, Malcolm Wallace, and John McDermid High-Integrity Systems Group, Department of Computer Science,
More informationConstruction of BPMN-based Business Process Model Base
Construction of BPMN-based Business Process Model Base Yanjie Lu Hongming Cai Lihong Jiang Shanghai Jiaotong University hmcai@sjtu.edu.cn doi:10.4156/ijiip.vol1. issue2.3 Shanghai Jiaotong University lvyanjie@sjtu.edu.cn
More informationLinking ITSM and SOA a synergetic fusion
Linking ITSM and SOA a synergetic fusion Dimitris Dranidis dranidis@city.academic.gr CITY College, Computer Science Department South East European Research Centre (SEERC) CITY College CITY College Founded
More informationIBM Research Report. Model-Driven Business Transformation and Semantic Web
RC23731 (W0509-110) September 30, 2005 Computer Science IBM Research Report Model-Driven Business Transformation and Semantic Web Juhnyoung Lee IBM Research Division Thomas J. Watson Research Center P.O.
More informationComplex event processing in reactive distributed systems
Complex event processing in reactive distributed systems Ján JANÍK Slovak University of Technology Faculty of Informatics and Information Technologies Ilkovičova 3, 842 16 Bratislava, Slovakia xjanikj@is.stuba.sk
More informationService Vs. System. Why do we need Services and a Services Viewpoint in DM2 and DoDAF? Fatma Dandashi, PhD March 4, 2011
Service Vs. System Why do we need Services and a Services Viewpoint in DM2 and DoDAF? Fatma Dandashi, PhD March 4, 2011 1. Does DoD Need To Model a Service? Bottom Line Up front (BLUF) DoD has a requirement
More informationEnterprise Architecture Frameworks
Enterprise Architecture Frameworks Learning Objective of Chapter 2 Topic: Enterprise Architecture Framework Content and structure of enterprise architecture descriptions This is necessary because Enterprises
More informationWeb Services Annotation and Reasoning
Web Services Annotation and Reasoning, W3C Workshop on Frameworks for Semantics in Web Services Web Services Annotation and Reasoning Peter Graubmann, Evelyn Pfeuffer, Mikhail Roshchin Siemens AG, Corporate
More informationGeneric and Domain Specific Ontology Collaboration Analysis
Generic and Domain Specific Ontology Collaboration Analysis Frantisek Hunka, Steven J.H. van Kervel 2, Jiri Matula University of Ostrava, Ostrava, Czech Republic, {frantisek.hunka, jiri.matula}@osu.cz
More informationArchitectural Blueprint
IMPORTANT NOTICE TO STUDENTS These slides are NOT to be used as a replacement for student notes. These slides are sometimes vague and incomplete on purpose to spark a class discussion Architectural Blueprint
More informationfor TOGAF Practitioners Hands-on training to deliver an Architecture Project using the TOGAF Architecture Development Method
Course Syllabus for 3 days Expert led Enterprise Architect hands-on training "An Architect, in the subtlest application of the word, describes one able to engage and arrange all elements of an environment
More informatione-governance Other Government Central Government Business State Citizen
5th International Conference on e-governance e-governance Technology Perspectives December 28, 2007 WELCOME S. Ramakrishnan ramki@cdac.in e-governance e-governance is the use of IT to support government
More informationINRIA ADT galaxy An open agile SOA platform
1 INRIA ADT galaxy An open agile SOA platform Alain Boulze Tuvalu team & galaxy lead Séminaire IN Tech INRIA Montbonnot - 12-nov-2009 galaxy, an open SOA R&D platform enabling agility 2 Open An open internal
More informationTOGAF Certified (Level 1 and 2) 9.1. Lesson Plan. This course covers all learning materials for TOGAF v9.1. Mock Exam: Duration: Language:
TOGAF Certified (Level 1 and 2) 9.1 Lesson Plan This course covers all learning materials for TOGAF v9.1 Delivery: e-learning Certificate: Examination (vouchers included) Accredited By: The Open Group
More informationProposed Revisions to ebxml Technical Architecture Specification v ebxml Business Process Project Team
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 Proposed Revisions to ebxml Technical Architecture Specification v1.0.4 ebxml Business Process Project Team 11
More informationMDA. SOA = Model Driven SOA
Introducing Model Driven SOA MDA + SOA = Model Driven SOA SoaML an Emerging Standard for SOA Modeling Dr. Darius Silingas Principal Trainer/Consultant darius.silingas@nomagic.com Introduction Who Am I?
More informationArchitecture and the UML
Architecture and the UML Models, Views, and A model is a complete description of a system from a particular perspective Use Case Use Case Sequence Use Case Use Case Use Case State State Class State State
More informationDevelopment and Implementation of Workshop Management System Application to Explore Combing Multiple Design Patterns
St. Cloud State University therepository at St. Cloud State Culminating Projects in Computer Science and Information Technology Department of Computer Science and Information Technology 5-2015 Development
More informationOntology-based Model Transformation
Ontology-based Model Transformation Stephan Roser Advisor: Bernhard Bauer Progamming of Distributed Systems Institute of Computer Science, University of Augsburg, Germany [roser,bauer]@informatik.uni-augsburg.de
More informationTowards a UML Profile for Service-Oriented Architectures 1
Towards a UML Profile for Service-Oriented Architectures 1 Reiko Heckel, Marc Lohmann, and Sebastian Thöne Faculty of Computer Science, Electrical Engineering and Mathematics University of Paderborn, Germany
More informationJOURNAL OF OBJECT TECHNOLOGY
JOURNAL OF OBJECT TECHNOLOGY Online at http://www.jot.fm. Published by ETH Zurich, Chair of Software Engineering JOT, 2004 Vol. 3, No. 7, July-August 2004 UML 2 Activity and Action Models Part 5: Partitions
More informationTOGAF days. Course description
TOGAF 9.1 5 days Course description TOGAF stands for The Open Group Architecture Framework It is the industry-standard methodology and framework for performing EA work and is used by thousands of Enterprise
More informationMappings from BPEL to PMR for Business Process Registration
Mappings from BPEL to PMR for Business Process Registration Jingwei Cheng 1, Chong Wang 1 +, Keqing He 1, Jinxu Jia 2, Peng Liang 1 1 State Key Lab. of Software Engineering, Wuhan University, China cinfiniter@gmail.com,
More informationEnterprise Architecture
Enterprise Architecture Dr. Adnan Albar Faculty of Computing & Information Technology King AbdulAziz University - Jeddah 1 Dimensions of Architectural Modeling Lecture 7 Week 6 Slides King AbdulAziz University
More informationOpen Source egovernment Reference Architecture. Cory Casanave, President. Data Access Technologies, Inc.
Open Source egovernment Reference Architecture Cory Casanave, President www.enterprisecomponent.com Slide 1 What we will cover OsEra OsEra Overview Model to Integrate From business model to execution Synthesis
More informationContext-aware Services for UMTS-Networks*
Context-aware Services for UMTS-Networks* * This project is partly financed by the government of Bavaria. Thomas Buchholz LMU München 1 Outline I. Properties of current context-aware architectures II.
More information* Corresponding Author
A Model Driven Architecture for REA based systems Signe Ellegaard Borch, Jacob Winther Jespersen, Jesper Linvald, Kasper Østerbye* IT University of Copenhagen, Denmark * Corresponding Author (kasper@it-c.dk)
More informationThe Analysis and Proposed Modifications to ISO/IEC Software Engineering Software Quality Requirements and Evaluation Quality Requirements
Journal of Software Engineering and Applications, 2016, 9, 112-127 Published Online April 2016 in SciRes. http://www.scirp.org/journal/jsea http://dx.doi.org/10.4236/jsea.2016.94010 The Analysis and Proposed
More informationPicasso: A Service Oriented Architecture for Model-based Automation
Picasso: A Service Oriented Architecture for Model-based Automation Sharad Singhal, James Pruyne, Vijay Machiraju Enterprise Systems and Software Laboratory HP Laboratories Palo Alto HPL-2007-50R1 January
More informationVARIABILITY MODELING FOR CUSTOMIZABLE SAAS APPLICATIONS
VARIABILITY MODELING FOR CUSTOMIZABLE SAAS APPLICATIONS ABSTRACT Ashraf A. Shahin 1, 2 1 College of Computer and Information Sciences, Al Imam Mohammad Ibn Saud Islamic University (IMSIU) Riyadh, Kingdom
More informationDelivered in the context of SC289DI An introduction to the European Interoperability Reference Architecture (EIRA) v1.1.
Delivered in the context of SC289DI07172 An introduction to the European Interoperability Reference Architecture (EIRA) v1.1.0 EIRA EUROPEAN INTEROPERABILITY REFERENCE ARCHITECTURE Modification Change
More informationASSURING DATA INTEROPERABILITY THROUGH THE USE OF FORMAL MODELS OF VISA PAYMENT MESSAGES (Category: Practice-Oriented Paper)
ASSURING DATA INTEROPERABILITY THROUGH THE USE OF FORMAL MODELS OF VISA PAYMENT MESSAGES (Category: Practice-Oriented Paper) Joseph Bugajski Visa International JBugajsk@visa.com Philippe De Smedt Visa
More informationAn Efficient Methodology for Developing and Maintaining Consistent Software Using OOAD Tools
An Efficient Methodology for Developing and Maintaining Consistent Software Using OOAD Tools S. Pasupathy 1, Dr. R. Bhavani 2 Associate Professor, Dept. of CSE, FEAT, Annamalai University, Tamil Nadu,
More informationDelivering Enterprise Architecture with TOGAF and ArchiMate
Delivering Enterprise Architecture with TOGAF and ArchiMate Enterprise Architecture using open standards Harmen van den Berg, BiZZdesign BiZZdesign in one slide Tools Powerfull User friendly Consultancy
More informationINF5120 Modelbased System development
INF5120 Modelbased System development Lecture 11: 09.04.2018 Arne-Jørgen Berre arneb@ifi.uio.no and Arne.J.Berre@sintef.no 1 2 Course parts (16 lectures) - 2018 Part I-a -(Introduction to Modeling): 15/1
More informationHierarchical vs. Flat Component Models
Hierarchical vs. Flat Component Models František Plášil, Petr Hnětynka DISTRIBUTED SYSTEMS RESEARCH GROUP http://nenya.ms.mff.cuni.cz Outline Component models (CM) Desired Features Flat vers. hierarchical
More informationModelling in Enterprise Architecture. MSc Business Information Systems
Modelling in Enterprise Architecture MSc Business Information Systems Models and Modelling Modelling Describing and Representing all relevant aspects of a domain in a defined language. Result of modelling
More informationEnterprise Architect. User Guide Series. Domain Models
Enterprise Architect User Guide Series Domain Models What support for modeling domains? Sparx Systems Enterprise Architect supports a range of modeling languages, technologies and methods that can be used
More informationOG0-091 Q&As TOGAF 9 Part 1
CertBus.com OG0-091 Q&As TOGAF 9 Part 1 Pass The Open Group OG0-091 Exam with 100% Guarantee Free Download Real Questions & Answers PDF and VCE file from: 100% Passing Guarantee 100% Money Back Assurance
More informationINF5120 and INF9120 Modelbased System development
INF5120 and INF9120 Modelbased System development Lecture 5: 13.02.2016 Arne-Jørgen Berre arneb@ifi.uio.no and Arne.J.Berre@sintef.no Telecom and Informatics 1 Course parts (16 lectures) - 2017 January
More informationOG The Open Group OG TOGAF 9 Combined Part 1 and Part 2
The Open Group OG0-093 TOGAF 9 Combined Part 1 and Part 2 1 Set1, Part 1 QUESTION: 1 Which of the following TOGAF components was created to enable architects to design architectures addressing Boundaryless
More informationEnterprise IT Architectures. Lecture Overview & Introduction. Dr. Hans-Peter Hoidn Distinguished IT Architect (Open Group certified)
Dr. Hans-Peter Hoidn Distinguished IT Architect (Open Group certified) Enterprise IT Architectures Lecture Overview & Introduction Introduction to the Course 2 Aim of the course The course is providing
More informationWeb Services. Lecture I. Valdas Rapševičius. Vilnius University Faculty of Mathematics and Informatics
Web Services Lecture I Valdas Rapševičius Vilnius University Faculty of Mathematics and Informatics 2014.02.28 2014.02.28 Valdas Rapševičius. Java Technologies 1 Outline Introduction to SOA SOA Concepts:
More informationCoE CENTRE of EXCELLENCE ON DATA WAREHOUSING
in partnership with Overall handbook to set up a S-DWH CoE: Deliverable: 4.6 Version: 3.1 Date: 3 November 2017 CoE CENTRE of EXCELLENCE ON DATA WAREHOUSING Handbook to set up a S-DWH 1 version 2.1 / 4
More informationRealizing the Army Net-Centric Data Strategy (ANCDS) in a Service Oriented Architecture (SOA)
Realizing the Army Net-Centric Data Strategy (ANCDS) in a Service Oriented Architecture (SOA) A presentation to GMU/AFCEA symposium "Critical Issues in C4I" Michelle Dirner, James Blalock, Eric Yuan National
More informationOO Analysis and Design with UML 2 and UP
OO Analysis and Design with UML 2 and UP Dr. Jim Arlow, Zuhlke Engineering Limited Clear View Training 2008 v2.5 1 UML principles Clear View Training 2008 v2.5 2 1.2 What is UML? Unified Modelling Language
More informationMeta Architecting: Towered a New Generation of Architecture Description Languages
Journal of Computer Science 1 (4): 454-460, 2005 ISSN 1549-3636 Science Publications, 2005 Meta Architecting: Towered a New Generation of Architecture Description Languages Adel Smeda, Tahar Khammaci and
More informationDimensions for the Separation of Concerns in Describing Software Development Processes
Dimensions for the Separation of Concerns in Describing Software Development Processes Pavel Hruby Navision Software Frydenlunds Allé 6 DK-2950 Vedbæk, Denmark ph@navision.com http://www.navision.com,
More informationVendor: The Open Group. Exam Code: OG Exam Name: TOGAF 9 Part 1. Version: Demo
Vendor: The Open Group Exam Code: OG0-091 Exam Name: TOGAF 9 Part 1 Version: Demo QUESTION 1 According to TOGAF, Which of the following are the architecture domains that are commonly accepted subsets of
More informationExploring Synergies between TOGAF and Frameworx
Exploring Synergies between TOGAF and Frameworx White Paper Industry Group Liaison TOGAF and TM Forum Frameworx Collaboration Project Document 1: Mapping of TOGAF and Frameworx Solutions Business Process
More informationIBM 00M passed
IBM 00M-646 - passed Number: 000-000 Passing Score: 800 Time Limit: 120 min File Version: 1.0 http://www.gratisexam.com/ IBM 00M-646 IBM WebSphere Sales Mastery Test v5 Version: 4.0 QUESTION NO: 1 Per
More informationDUBAI GRAND HOTEL. March 26 to (4 days) 9 am to 4 pm
TOGAF 9.1 Certification Training DUBAI GRAND HOTEL March 26 to 29-2017 (4 days) 9 am to 4 pm ISIDUS TECH TEAM FZE PO Box 9798 Dubai UAE, email mr@isidus.net M: +97150 7840755 T +97155 1602215 http://www.isidus.net
More informationKillTest *KIJGT 3WCNKV[ $GVVGT 5GTXKEG Q&A NZZV ]]] QORRZKYZ IUS =K ULLKX LXKK [VJGZK YKX\OIK LUX UTK _KGX
KillTest Q&A Exam : OG0-091 Title : TOGAF 9 Part 1 Version : Demo 1 / 5 1.According to TOGAF, Which of the following are the architecture domains that are commonly accepted subsets of an overall enterprise
More informationAvancier Methods (AM) CONCEPTS
Methods (AM) CONCEPTS Mapping generic ArchiMate entities to and TOGAF meta model entities It is illegal to copy, share or show this document (or other document published at ) without the written permission
More informationCredit where Credit is Due. Goals for this Lecture. Introduction to Design
Credit where Credit is Due Lecture 17: Intro. to Design (Part 1) Kenneth M. Anderson Object-Oriented Analysis and Design CSCI 6448 - Spring Semester, 2002 Some material presented in this lecture is taken
More information1Z Oracle IT Architecture SOA 2013 Essentials Exam Summary Syllabus Questions
1Z0-475 Oracle IT Architecture SOA 2013 Essentials Exam Summary Syllabus Questions Table of Contents Introduction to 1Z0-475 Exam on Oracle IT Architecture SOA 2013 Essentials 2 Oracle 1Z0-475 Certification
More informationService Creation in the SPICE Service Platform
1 Creation in the Platform João Paulo Almeida, Alberto Baravaglio, Mariano Belaunde, Paolo Falcarin, Ernö Kovacs Abstract Convergence is driving the uptake of new technologies on networking and layers.
More informationTopic #1: Digital Economy Transformation - A Top Priority' for Singapore s Companies
Topic #1: Digital Economy Transformation - A Top Priority' for Singapore s Companies Aaron Tan Dani, Chairman of Iasa Asia Pacific aarontan@iasahome.org Chairman of EA-SIG, Singapore Computer Society aarontan@scs.org.sg
More information