China 
Africa 
Explore chapters and articles related to this topic
Systems Theory
Published in Vivek Kale, Digital Transformation of Enterprise Architecture, 2019
The term framework is used to describe a prescribed set of steps and artifacts that are created as a course of designing an enterprise system or system of systems. EAFs embody design strategies and provide step-by-step guidance, and even templates, for designing and documenting the enterprise. EAFs prescribe a set of artifacts for specific enterprise stakeholders. Using the EAF, the enterprise architect creates various artifacts intended to be views of the system from the perspective of the enterprise stakeholders. Most enterprise architecture frameworks identify a number of concerns that will guide the design of enterprises, such as: Business requirements: The business needs of the organization.Stakeholders: Those who will interact with the enterprise in some way.Business processes: A series of activities leading to the achievement of a measurable business result.Environment: Those conditions in which the enterprise must operate.Software: The standard software suite that is closely coupled to the infrastructure, such as operating systems, drivers, database systems, and so forth.Data: High-level data designs that describe the structure of an enterprise’s data needs in terms of entities and relationships between entities.Infrastructure: The enterprise’s general IT assets, such as networks, hardware, computing systems, routers, and so forth.
Integration of Business Process Architectures within Enterprise Architecture Approaches: A Literature Review
Published in Engineering Management Journal, 2019
Fernanda Gonzalez-Lopez, Guillermo Bustos
Enterprise elements are generally organized into multiple viewpoints as in ArchiMate, EKD, TOGAF, the Zachman framework, and Simon’s BAF and include contextual and business-oriented viewpoints as well as implementation-oriented ones. ArchiMate and TOGAF do not predefine the viewpoints; however, an enterprise architect can define them according to the organization. The MIT’s FE approach solely provides one viewpoint, the EA overview. Specific BPA viewpoints are uncommon among the analyzed EA approaches. As previously stated, most of the approaches do not differentiate a BPA but rather identify (business) processes as an integral part of the overall EA. Only EKD and the Zachman framework present standalone BPA viewpoints as the former refers to an enterprise process sub-model and the latter to a process identification artifact. Nevertheless, all approaches consider processes as a constituent element of the overall EA architecture; MIT’s FE integrates processes to its single EA overview viewpoint, TOGAF considers functions as part of the business architecture, ArchiMate sees processes as a constituent of the EA business layer, and Simon’s BAF integrates business processes into the execution layer of EA.