Explore chapters and articles related to this topic
Using an enterprise architecture model for assessing the resilience of critical infrastructure
Published in Stein Haugen, Anne Barros, Coen van Gulijk, Trond Kongsvik, Jan Erik Vinnem, Safety and Reliability – Safe Societies in a Changing World, 2018
Gonçalo Cadete, Miguel Mira da Silva
For the second DSRM iteration, an EA model was created, to model the new RAF framework that resulted from the first DSRM iteration. The ArchiMate (The Open Group 2016) modeling language was used for the EA representations. An open source EA tool (Archi 2017) was used for providing an integrated EA repository, as well as the Archi-Mate views. The viewpoint representing the goals cascade and the PAM is shown in Figure 4. Note that this viewpoint clearly shows the relation between the goal cascade elements (stakeholder drivers and needs, organizational goals, business area goals, and enabling process goals), as well as the relations between all their subcomponents. Also, note that the graphical arrangement intuitively conveys the notion of top-down and bottom-up alignment – important for relating management and operational concerns.
A systematic mapping study on enterprise architecture mining
Published in Enterprise Information Systems, 2019
Ricardo Perez-Castillo, Francisco Ruiz-Gonzalez, Marcela Genero, Mario Piattini
Apart from the TOGAF framework, ‘The Open Group’ released ArchiMate (The Open Group 2016a), a modelling language with which to representing different EA information models. ArchiMate allows the modelling of EA from different viewpoints, in which the position within the cells highlights the stakeholders’ concerns (see Figure 2). ArchiMate considers two dimensions: layers and aspects. Core layers represent the three levels at which it is possible to model an enterprise in ArchiMate, i.e. business, application, and technology. Aspects refers to: (i) the active structure (elements representing who makes the things), (ii) behaviour (elements indicating what is made and how it is made), and (iii) passive structure (things on which behaviour is performed). ArchiMate also allows composite elements that do not necessarily fit in a single aspect, but these may combine two or more aspects. The full framework in Archimate 3 also includes additional layers for strategy, physical and implementation/migration elements, and a fourth aspect with motivational elements.
Integration of Business Process Architectures within Enterprise Architecture Approaches: A Literature Review
Published in Engineering Management Journal, 2019
Fernanda Gonzalez-Lopez, Guillermo Bustos
This section provides the comparison of general and detailed EA-BPA integration aspects based on data presented in Exhibit 11. To contextualize, we first include the main focus of each EA approach, as shown in the second column of Exhibit 11. We found that most of the EA approaches present an architectural framework as the main element of the approach (Lankhorst, 2004; Loucopoulos & Kavakli, 1997; Simon et al., 2014; The Open Group, 2011; Zachman, 1987). This finding, consistent with Schekkerman (2004) and Simon et al. (2013), identifies EA frameworks as the most researched aspect of EA. In addition, we observed EKD and TOGAF provide a methodology for building an EA along with a framework and MIT’s FE solely focuses on EA methodological aspects. The frameworks and methodologies are heterogeneous in their level of detail. ArchiMate provides an architecture description language, and TOGAF, offering best practices and reference models, has an overall wider coverage of EA specifications.
Using intelligent ontology technology to extract knowledge from successful project in IoT enterprise systems
Published in Enterprise Information Systems, 2022
Jinfeng Ding, TianRan Tang, Yaqin Zhang, Wi Chi
Based on an in-depth analysis of the existing approaches in applying semantic technologies to business process management (BPM) research in the perspective of cross-enterprise collaboration or so-called business-to-business integration, we analyse, discuss and compare methodologies, applications and best practices of the surveyed approaches with the proposed criteria. This article identifies various relevant research directions in semantic BPM (SBPM). Founded on the result of our investigation, we summarise the state of art of SBPM. We also address areas and directions for further research activities (Hoang, Jung, and Tran 2013). The accessibility of project knowledge obtained from experiences is an important and crucial issue in enterprises. This information need about project knowledge can be different from one person to another depending on the different roles he or she has. Therefore, a new ontology-based case-based reasoning (OBCBR) approach that utilises an enterprise ontology is introduced in this article to improve the accessibility of this project knowledge. Utilising an enterprise ontology improves the case-based reasoning (CBR) system through the systematic inclusion of enterprise-specific knowledge. This enterprise-specific knowledge is captured using the overall structure given by the enterprise ontology named ArchiMEO, which is a partial ontological realisation of the enterprise architecture framework (EAF) ArchiMate. This ontological representation, containing historical cases and specific enterprise domain knowledge, is applied in a new OBCBR approach. To support the different information needs of different stakeholders, this OBCBR approach has been built in such a way that different views, viewpoints, concerns and stakeholders can be considered. This is realised using a case viewpoint model derived from the ISO/IEC/IEEE 42010 standard. The introduced approach was implemented as a demonstrator and evaluated using an application case that has been elicited from a business partner in the Swiss research project (Martin et al. 2017).