China
Africa
Explore chapters and articles related to this topic
DoDAF and Other Frameworks
Published in Howard Eisner, Systems Architecting, 2019
We note, in this section, the fact that many other frameworks and architectures have appeared in practice and the literature. For example, Sillitto has explored system architecting in his informative and leading-edge book [6]. Dickerson, along with other authors, has used architectures for research, development, and acquisition (RDA) [7]. Steven Spewak was well known for his development of Enterprise Architecture Planning (EAP) [8]. At the federal government level, there came to be a federal enterprise architecture framework (FEAF) as an initiative of the Office of Management and Budget [9]. Another relevant approach was formulated by NIST as an Enterprise Architecture Model [10]. MITRE documented its approach to dealing with architecture frameworks in its exposition of architectural frameworks, models, and views [11]. The well-known service-oriented architecture was described in a Wiley series [12], and yet another Wiley book [13], well worth examining, documented “system architectures.”
Safety enterprise architecture approach for a railway safety management system
Published in Stein Haugen, Anne Barros, Coen van Gulijk, Trond Kongsvik, Jan Erik Vinnem, Safety and Reliability – Safe Societies in a Changing World, 2018
Federal Enterprise Architecture Framework (FEAF) of US government is to facilitate the shared development of common processes and information among US federal entities (Odongo et al. 2010, Sessions 2007). FEAF is based on Zachman framework, but refers only to the first three columns that represent what-data, how-function and where-network respectively and focuses on the top three rows presenting various perspectives to provide standard terms and definitions through Business Reference Model (BRM), Components Reference Model (CRM), Technical Reference Model (TRM), Data Reference Model (DRM), and Performance Reference Model (PRM) with each have unique goals. It uses architecture analysis, architectural definition, investment and funding strategy and program management plan as a four-step process for creating an EA.
Moving Enterprise Architecture from Professional Certificates to Academic Credentials
Published in Ibrahiem M. M. El Emary, Anna Brzozowska, Shaping the Future of ICT, 2017
Organizations in different disciplines started to look for standard ways to support describing and documenting their processes and systems using EA frameworks such as TOGAF, Zachman, Federal Enterprise Architecture Framework (FEAF), and Treasury Enterprise Architecture Framework (TEAF). An architecture is a framework of principles, guidelines, standards, models, and strategies that direct the design, construction, and deployment of business processes, resources, and information technology throughout the enterprise. Architectures are usually high-level views of the system they describe. An architecture is typically made up of A picture of the current stateA blueprint or vision for the futureA roadmap on how to get there
Managing digital transformation of smart cities through enterprise architecture – a review and research agenda
Published in Enterprise Information Systems, 2021
Gartner framework is another EA which includes architecting, business strategy, current-state architecture, environmental trends, governing and managing. Gartner framework provide cities with a logical method to develop an EA, it employs a multiphase, nonlinear, and iterative model, that represents synthesis and key features of best practices of how the most effective enterprises have deployed and sustained their EA. Gartner framework is reliable, and vendor-neutral, thus municipalities can choose to adopt it with another EA framework. The Federal Enterprise Architecture Framework (FEAF) establish the basis for initiating the behaviours and rules of an organisation (Council 2001). It provides principles that govern the implementation of the EA process. It is divided into business, applications, data and technology layers. FEAF aims to facilitate all US federal agency Chief Information Officers (CIOs) to design, develop, and implement an integrated architecture to exploit the value and reduce risks related to IT projects. Also, FEAF includes all necessary initiatives needed to design an EA and is suitable for more complex enterprises.
Smart city data architecture for energy prosumption in municipalities: concepts, requirements, and future directions
Published in International Journal of Green Energy, 2020
The Federal Enterprise Architecture Framework (FEAF) was developed as a legislation (the Clinger Cohen Act of 1994), also known as the Information Technology Management Reform Act which directed federal enterprises to design a master strategy for managing IT acquisitions, assimilating new technologies, assessing, and reporting on IT performance (Cisco 2009). FEAF aims to facilitate all US Federal Agency Chief Information Officers (CIOs) to design, develop, and implement an integrated architecture to exploit the value and reduce risks related to IT projects. The first version of FEAF was made public in 1999 after which it has been modified and expanded over time (Council, 1999). Due to the diversity of concerns that federal enterprises deal with and several levels of measure at which the federal government level, FEAF is multilayered, complex, and large. It consists of a collection of management strategies expressed in IT terms more than a formal methodology or taxonomy. It can be viewed as a methodology for developing EA as well as the outcome of applying that process to a specific enterprise namely the United State government (Cameron and McMillan 2013). Besides, FEAF includes all necessary initiatives needed to design an EA and is suitable for more complex enterprises. Moreover, FEAF attempted to achieve a seamless incorporation of various architectures that existed in different federal agencies to connect all stakeholders involved by supporting better and faster access to information in a more profitable manner (Cameron and McMillan 2013). It comprises of performance, business, components, technology, and data layers (Cisco 2009).
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).