Enterprise Architecture https://store.theartofservice.com/the-enterprise-architecture-toolkit.html.

Enterprise Architecture https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Service-oriented architecture - Service-oriented enterprise architecture 1 This umbrella architecture incorporates service, composition, and inventory architectures, plus any enterprise-wide technological resources accessed by these architectures e.g. an ERP system. This can be further supplemented by including enterprise-wide standards that apply to the aforementioned architecture types. Any segments of the enterprise that are not service- oriented can also be documented in order to consider transformation requirements if a service needs to communicate with the business processes automated by such segments. https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Enterprise architecture 1 Enterprise architecture (EA) is a contested term that refers to the architecture of an enterprise—an organized complex of people and technologies—and the activity of describing or designing enterprises. The term "enterprise architecture" has been and still is used with various meanings. https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Enterprise architecture - Definitions 1 The MIT Center for Information Systems Research (MIT CISR) in 2007 defined enterprise architecture as the specific aspects of a business that are under examination: https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Enterprise architecture - Definitions 1 Enterprise architecture is the organizing logic for business processes and IT infrastructure reflecting the integration and standardization requirements of the company's operating model. The operating model is the desired state of business process integration and business process standardization for delivering goods and services to customers. https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Enterprise architecture - Definitions 1 The United States Government in 2011 classified enterprise architecture as an Information Technology function, and defines the term not as the process of examining the enterprise, but rather the documented results of that examination https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Enterprise architecture - Definitions 1 The Enterprise Architecture Research Forum defines EA as the continuous practice of describing the essential elements of a socio- technical organization, their relationships to each other and to the environment, in order to understand complexity and manage change.. Note that EA is focused on enabling and supporting human roles and processes by means of information systems (cf. "system theory"), rather the design of human social systems per se (cf. "organization theory" and "systems thinking"). https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Enterprise architecture - Definitions 1 In 2013, Gartner's definition is this: "Enterprise architecture (EA) is a discipline for proactively and holistically leading enterprise responses to disruptive forces by identifying and analyzing the execution of change toward desired business vision and outcomes https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Enterprise architecture - Definitions 1 In a business organization structure today, the enterprise architecture team performs an ongoing business function that helps business and IT managers to figure out the best strategies to support and enable business development and business change - in relation to the business information systems the business depends on. https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Enterprise architecture - Definitions 1 Cioindex provides a business focused definition of enterprise architecture: "Enterprise architecture is a holistic, hierarchical, and abstract description of the essential elements of an organization to maximize shareholder value over time." https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Enterprise architecture - Meanings of enterprise architecture 1 Current perspectives, or beliefs, held by enterprise architecture practitioners and scholars, with regards to the meaning of the enterprise architecture, typically gravitates towards one or a hybrid of three schools of thought: https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Enterprise architecture - Meanings of enterprise architecture 1 Enterprise IT Architecting. According to this school, the purpose of EA is the greater alignment between IT and business concerns. The main purpose of EA is to guide the process of planning and design the IT/IS capabilities of an enterprise in order to meet desired organizational objectives. Typically, architecture proposals and decisions are limited to the IT/IS aspects of the enterprise; other aspects only serve as inputs. https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Enterprise architecture - Meanings of enterprise architecture 1 Enterprise Integrating. According to this school, the purpose of EA is to achieve greater coherency between the various concerns of an enterprise (HR, IT, Operations, etc.) including the linking between strategy formulation and execution. Typically, architecture proposals and decisions encompass all the aspects of the enterprise. https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Enterprise architecture - Meanings of enterprise architecture 1 Enterprise Ecological Adaptation. According to this school, the purpose of EA is to foster and maintain the learning capabilities of enterprises so that they may be sustainable. Consequently, a great deal of emphasis is put on improving the capabilities of the enterprise to improve itself, to innovate and to coevolve with its environment. Typically, proposals and decisions encompass both the enterprise and its environment. https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Enterprise architecture - Meanings of enterprise architecture 1 One’s belief with regards to the meaning of enterprise architecture will impact greatly how one sees the purpose of EA, the scope of EA, the means of achieving EA, the skills needed to conduct EA, and the locus of responsibility for conducting EA https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Enterprise architecture - Scope 1 The term enterprise covers all kinds of business organization, public or private, large or small, including https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Enterprise architecture - Scope 1 Public or private sector organizations https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Enterprise architecture - Scope 1 An entire business or corporation https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Enterprise architecture - Scope 1 A part of a larger enterprise (such as a business unit) https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Enterprise architecture - Scope 1 A conglomerate of several organizations, such as a joint venture or partnership https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Enterprise architecture - Scope 1 A multiple outsourced business operation https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Enterprise architecture - Scope 1 Many collaborating public and/or private organizations in multiple countries https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Enterprise architecture - Scope 1 The term enterprise includes the whole complex, socio-technical system, including people, information, processes and technologies. https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Enterprise architecture - Scope 1 The term architecture refers to a high-level or abstract description of the enterprise as a system - its boundary, the products and services it provides, and its internal structures and behaviors, both human and technical. It is assumed that designers, developers or engineers will complete the most detailed and concrete descriptions of specific enterprise systems, and the architect will retain responsibility for governing that lower level work. https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Enterprise architecture - Enterprise Architecture Description 1 An enterprise architecture description contains a variety of lists, tables and diagrams known as artifacts. These artifacts describe the logical business functions or capabilities, business processes, human roles and actors, the physical organization structure, data flows and data stores, business applications and platform applications, hardware and communications infrastructure. https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Enterprise architecture - Enterprise Architecture Description 1 The UK National Computing Centre EA best practice guidance states https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Enterprise architecture - Enterprise Architecture Description 1 Normally an EA takes the form of a comprehensive set of cohesive models that describe the structure and functions of an enterprise... The individual models in an EA are arranged in a logical manner that provides an ever-increasing level of detail about the enterprise. https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Enterprise architecture - Enterprise Architecture Description 1 The architecture of an enterprise is described with a view to improving the manageability, effectiveness, efficiency or agility of the business, and ensuring that money spent on information technology (IT) is justified. https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Enterprise architecture - Enterprise Architecture Description 1 Paramount to changing the enterprise architecture is the identification of a sponsor, his/her mission, vision and strategy and the governance framework to define all roles, responsibilities and relationships involved in the anticipated transformation. Changes considered by enterprise architects typically include: https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Enterprise architecture - Enterprise Architecture Description 1 innovations in the structure or processes of an organization https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Enterprise architecture - Enterprise Architecture Description 1 innovations in the use of information systems or technologies https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Enterprise architecture - Enterprise Architecture Description 1 the integration and/or standardization of business processes, https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Enterprise architecture - Enterprise Architecture Description 1 improving the quality and timeliness of business information. https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Enterprise architecture - Enterprise Architecture Description 1 See the related articles Enterprise Architecture framework and architecture domain for further information. https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Enterprise architecture - Benefits of enterprise architecture 1 If the enterprise architecture is not kept up to date, the aforementioned benefits will become useless. https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Enterprise architecture - Benefits of enterprise architecture 1 EA is also referred as "Everything Aligned" as the Business-Technology alignment is achieved through EA as a vehicle. The Business and Technology parameters like Availability, Scalability, Security, Interoperability, Maintainability, Lower Cost, Extendability and Reliability can be improved through EA. These critical Business-Technology parameters are called ASSIMPLER parameters. https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Enterprise architecture - Examples of enterprise architecture use 1 Documenting the architecture of enterprises is done within the U.S. Federal Government in the context of the Capital Planning and Investment Control (CPIC) process. https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Enterprise architecture - Examples of enterprise architecture use 1 The Federal Enterprise Architecture (FEA) reference models guides federal agencies in the development of their architectures. https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Enterprise architecture - Examples of enterprise architecture use 1 Companies such as Independence Blue Cross, Intel, Volkswagen AG and InterContinental Hotels Group use enterprise architecture to improve their business architectures as well as to improve business performance and productivity. https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Enterprise architecture - Examples of enterprise architecture use 1 For various understandable reasons, commercial organizations rarely publish substantial enterprise architecture descriptions. However, government agencies have begun to publish architectural descriptions they have developed. Examples include https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Enterprise architecture - Examples of enterprise architecture use 1 US Department of the Interior, https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Enterprise architecture - Examples of enterprise architecture use 1 US Department of Defense Business Enterprise Architecture, or the 2008 BEAv5.0 version. https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Enterprise architecture - Examples of enterprise architecture use 1 Treasury Enterprise Architecture Framework https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Enterprise architecture - Relationship to other disciplines 1 Analyst firm Real Story Group suggested that Enterprise Architecture and the emerging concept of the Digital workplace were "two sides to the same coin." https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Enterprise architecture - Relationship to other disciplines 1 The following image from the 2006 FEA Practice Guidance of US OMB sheds light on the relationship between enterprise architecture and segment (BPR) or Solution architectures. https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Enterprise architecture - Relationship between Enterprise Architecture and Service Oriented Architecture 1 When considering the relationship between EA and SOA, there are a number of issues to consider. Not the least of these is what the enterprise understand EA and SOA to mean. Some guidelines can be found at this reference: https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Enterprise architecture - Notable Enterprise Architecture tools 1 The following table lists the most notable enterprise architecture tools as recognized by Gartner and Forrester Research in their most recent reports. https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Enterprise architecture - Notable Enterprise Architecture tools 1 ABACUSAvolutionAustralia 4.1December 2012 https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Enterprise architecture - Notable Enterprise Architecture tools 1 ADOitBOC GroupAustria5.1 June 2013 https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Enterprise architecture - Notable Enterprise Architecture tools 1 Corporate ModelerCasewise United Kingdom2011.4 August 2013 https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Enterprise architecture - Notable Enterprise Architecture tools 1 Envision VIPFuture Tech SystemsUnited States 10March 2013 https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Enterprise architecture - Notable Enterprise Architecture tools 1 Essential Architecture ManagerEnterprise Architecture SolutionsUnited Kingdom4.1July 2013 https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Enterprise architecture - Notable Enterprise Architecture tools 1 MappITFrankITectureUnited Kingdom4.1July 2013 https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Enterprise architecture - Notable Enterprise Architecture tools 1 ProVisionOpenText (formerly Metastorm)United States9.0 September 2012 https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Enterprise architecture - Notable Enterprise Architecture tools 1 SAMUAtoll Technologies Hungary5.4 https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Enterprise architecture - Notable Enterprise Architecture tools 1 System ArchitectIBM (formerly Telelogic) United States11.4.2 June 2012 https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Enterprise architecture - Notable Enterprise Architecture tools 1 TrouxTroux Technologies (formerly Computas Technology)United States9.1.2March 2013 https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Enterprise architecture - Academic qualifications 1 Enterprise Architecture was included in the Association for Computing Machinery (ACM) and Association for Information Systems (AIS)’s Curriculum for Information Systems as one of the 6 core courses. https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Enterprise architecture - Academic qualifications 1 A new MSc in Enterprise Architecture was introduced at the University of East London in collaboration with Iasa to start February 2013. https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Enterprise architecture - Academic qualifications 1 There are several universities that offer enterprise architecture as a fourth year level course or part of a master's syllabus. California State University offers a post-baccalaureate certificate in enterprise architecture, in conjunction with FEAC Institute. https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Enterprise architecture - Academic qualifications 1 National University offers a Master of Science in Engineering Management with specialization in Enterprise Architecture, again in conjunction with FEAC Institute. The Center for Enterprise Architecture at the Penn State University is one of these institutions that offer EA courses. It is also offered within the Masters program in Computer Science at The University of Chicago. https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Enterprise architecture - Academic qualifications 1 In 2010 researchers at the Meraka Institute, Council for Scientific and Industrial Research, in South Africa organized a workshop and invited staff from computing departments in South African higher education institutions. The purpose was to investigate the current status of EA offerings in South Africa. A report was compiled and is available for download at the Meraka Institute. https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Enterprise architecture - Criticism 1 Despite the benefits that Enterprise Architecture claims to provide, for more than a decade a number of industry leaders, writers, and leading organizations have raised concerns about EA’s many problems and failures. Here is a partial list: https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Enterprise architecture - Criticism 1 Enterprise Architecture as Strategy: Creating a Foundation for Business Execution https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Enterprise architecture - Criticism 1 In 2007 industry giant Ivar Jacobson (a major contributor to UML and pioneer in OO software development) gave his assessment of EA: ”Most EA initiatives failed. My guess is that more than 90% never really resulted in anything useful.” https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Enterprise architecture - Criticism 1 In a 2007 report on EA, Gartner predicted that “... by 2012 40% of [2007’s] enterprise architecture programs will be stopped”. https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Enterprise architecture - Criticism 1 A 2008 study by performed by Rotterdam University and software company IDS Sheer concluded that two-thirds of EA projects failed. https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Enterprise architecture - Criticism 1 In a 2009 article, industry commentator Dion Hinchcliffe wrote that EA was essentially “broken”: “Recently there’s a growing realization that traditional enterprise architecture as it’s often practiced today might be broken in some important way. What might be wrong and how to fix it are the questions du jour.” https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Enterprise architecture - Criticism 1 In a 2011 study performed by Smiths Consulting (UK) summarized their findings: “Enterprise Architecture (EA) initiatives fail far more often than they succeed. This white paper considers why EA initiatives fail, identifies the characteristic signatures of failure – and suggests ways to avoiding them!” https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Enterprise architecture - Criticism 1 In 2011 federal EA consultant Stanley Gaver released a report that examined the massive problems and failures of the federal government’s EA program. Mr. Gaver concluded that the federal EA program had mostly failed; this conclusion was corroborated by a similar one made by the federal government at an October 2010 meeting that was held to determine why the federal EA program wasn’t “as influential and successful as in the past.” https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Enterprise architecture - Criticism 1 But instead of proving the viability of Enterprise Architecture, the very act of trying to explain “what is” and “what isn’t” is an admission, although an inadvertent one, that there’s too much confusion and misunderstanding of the discipline for EA possibly to work. https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

View model - Types of Enterprise Architecture View Models 1 Because the discipline of Enterprise Architecture and Engineering is so broad, and because enterprises can be large and complex, the models associated with the discipline also tend to be large and complex https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

View model - Types of Enterprise Architecture View Models 1 Architecture Frameworks are commonly used in Information technology and Information system governance. An organization may wish to mandate that certain models be produced before a system design can be approved. Similarly, they may wish to specify certain views be used in the documentation of procured systems - the U.S. Department of Defense stipulates that specific DoDAF views be provided by equipment suppliers for capital project above a certain value. https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

View model - Federal Enterprise Architecture views 1 In the US Federal Enterprise Architecture enterprise, segment, and solution architecture provide different business perspectives by varying the level of detail and addressing related but distinct concerns. Just as enterprises are themselves hierarchically organized, so are the different views provided by each type of architecture. The Federal Enterprise Architecture Practice Guidance (2006) has defined three types of architecture: https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

View model - Federal Enterprise Architecture views 1 By definition, Enterprise Architecture (EA) is fundamentally concerned with identifying common or shared assets – whether they are strategies, business processes, investments, data, systems, or technologies https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

View model - Federal Enterprise Architecture views 1 By contrast, segment architecture defines a simple roadmap for a core mission area, business service, or enterprise service. Segment architecture is driven by business management and delivers products that improve the delivery of services to citizens and agency staff. From an investment perspective, segment architecture drives decisions for a business case or group of business cases supporting a core mission area or common or shared service. The primary stakeholders for segment architecture are business owners and managers. Segment architecture is related to EA through three principles: structure, reuse, and alignment. First, segment architecture inherits the framework used by the EA, although it may be extended and specialized to meet the specific needs of a core mission area or common or shared service. Second, segment architecture reuses important assets defined at the enterprise level including: data; common business processes and investments; and applications and technologies. Third, segment architecture aligns with elements defined at the enterprise level, such as business strategies, mandates, standards, and performance measures. https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

The Open Group Architecture Framework - Enterprise architecture domains 1 TOGAF is based on four interrelated areas of specialization called architecture domains: https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

The Open Group Architecture Framework - Enterprise architecture domains 1 Business architecture which defines the business strategy, governance, organization, and key business processes of the organization https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

The Open Group Architecture Framework - Enterprise architecture domains 1 Applications architecture which provides a blueprint for the individual application systems to be deployed, the interactions between the application systems, and their relationships to the core business processes of the organization with the frameworks for services to be exposed as business functions for integration https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

The Open Group Architecture Framework - Enterprise architecture domains 1 Data architecture which describes the structure of an organization's logical and physical data assets and the associated data management resources https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

The Open Group Architecture Framework - Enterprise architecture domains 1 Technical architecture, or technology architecture, which describes the hardware, software, and network infrastructure needed to support the deployment of core, mission- critical applications https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Enterprise architecture framework 1 An 'enterprise architecture framework' (EA framework) defines how to create and use an enterprise architecture. An architecture framework provides principles and practices for creating and using the architecture description of a system. It structures architects' thinking by dividing the architecture description into domains, layers or views, and offers models - typically matrices and diagrams - for documenting each view. https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Enterprise architecture framework - Overview 1 Enterprise architecture regards the enterprise as a large and complex system or system of systems.The Open Group (2008) TOGAF Version 9. Van Haren Publishing, 1 nov. 2008.p. 73 To manage the scale and complexity of this system, an architectural framework provides tools and approaches that help architects abstract from the level of detail that builders work at to bring enterprise design tasks into focus and produce valuable architecture description documentation. https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Enterprise architecture framework - Overview 1 The components of an architecture framework provide structured guidance that is divided into three main areas:Stephen Marley (2003).. NASA /SCI. Retrieved 10 Dec 2008. https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Enterprise architecture framework - Overview 1 * Descriptions of architecture: how to document the enterprise as a system from several viewpoints. Each view describes one slice of the architecture; it includes those entities and relationships that address particular concerns of interest to particular stakeholders; it may take the form of a list, a table, a diagram, or a higher level of composite of such. https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Enterprise architecture framework - Overview 1 * Methods for designing architecture: processes that architects follow. Usually, an overarching enterprise architecture process, composed of phases, breaks into lower-level processes composed of finer grained activities. A process is defined by its objectives, inputs, phases (steps or activities) and outputs. It may be supported by approaches, techniques, tools, principles, rules, and practices. https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Enterprise architecture framework - Overview 1 * Organization of architects: guidance on the team structure, the governance of the team, the skills, experience and training needed. https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Enterprise architecture framework - History 1 Since the 1970s people working in IS/IT have looked for ways to engage business people – to enable business roles and processes - and to influence investment in business information systems and technologies – with a view to the wide and long term benefit of the enterprise. Many of the aims, principles, concepts and methods now employed in EA frameworks were established in the 1980s, and can be found in IS and IT architecture frameworks published in that decade and the next.Graham Berrisford (2008-13) on grahamberrisford.com, last update 16/07/2013. Accessed 16/07?2003 https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Enterprise architecture framework - History 1 By 1980, IBM’s Business Systems Planning (BSP) was promoted as a method for analyzing and designing an organization’s information architecture, with the goals: https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Enterprise architecture framework - History 1 # understand the issues and opportunities with the current applications and technical architecture; https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Enterprise architecture framework - History 1 # develop a future state and migration path for the technology that supports the enterprise; https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Enterprise architecture framework - History 1 # provide business executives with a direction and decision making framework for IT capital expenditures; https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Enterprise architecture framework - History 1 # provide information system (IS) with a blueprint for development. https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Enterprise architecture framework - History 1 Although many popular information systems planning methodologies, design approaches, and various tools and techniques do not preclude or are not inconsistent with enterprise-level analysis, few of them explicitly address or attempt to define enterprise architectures https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Enterprise architecture framework - History 1 The paper did not mention enterprise architecture. https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Enterprise architecture framework - History 1 In 1989, the National Institute of Standards and Technology (NIST) published the NIST Enterprise Architecture Model. This was a five- layer reference model that illustrates the interrelationship of business, information system, and technology domains. It was promoted within the U.S. federal government. It was not an EA framework as we see it now, but it helped to establish the notion of dividing EA into architecture domains or layers. https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Enterprise architecture framework - History 1 The term enterprise architecture did not appear https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Enterprise architecture framework - History 1 Enterprise Architecture Planning is a data-centric approach to architecture planning https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Enterprise architecture framework - History 1 In 1994, the Open Group selected TAFIM from the US DoD as a basis for development of The Open Group Architecture Framework (TOGAF), where architecture meant IT architecture. TOGAF started out taking a strategic and enterprise-wide, but technology-oriented, view. It emerged out of the desire to rationalize a messy IT estate. Right up to version 7, TOGAF was still focused on defining and using a Technical Reference Model (or foundation architecture) to define the platform services required from the technologies that an entire enterprise uses to support business applications. https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Enterprise architecture framework - History 1 In 1996, the US IT Management Reform Act, more commonly known as the Clinger-Cohen Act, repeatedly directed that a US federal government agency’s investment in IT must be mapped to identifiable business benefits. In addition, it made the agency CIO responsible for, “...developing, maintaining and facilitating the implementation of a sound and integrated IT architecture for the executive agency.” https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Enterprise architecture framework - History 1 By 1997, Zachman had renamed and refocused his ISA framework as an EA framework; it remained a classification scheme for descriptive artifacts, not a process for planning systems or changes to systems. https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Enterprise architecture framework - History 1 In 1998, The Federal CIO Council began developing the Federal Enterprise Architecture Framework (FEAF) in accordance with the priorities enunciated in Clinger-Cohen and issued it in 1999. FEAF was a process much like TOGAF’s ADM, in which “The architecture team generates a sequencing plan for the transition of systems, applications, and associated business practices predicated upon a detailed gap analysis.” https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Enterprise architecture framework - History 1 In 2001, the US Chief CIO council published A practical guide to Federal Enterprise Architecture, which starts, “An enterprise architecture (EA) establishes the Agency-wide roadmap to achieve an Agency’s mission through optimal performance of its core business processes within an efficient information technology (IT) environment. https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Enterprise architecture framework - History 1 And many enterprise architects regard their business function/capability hierarchy/map as the fundamental Enterprise Architecture artifact https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Enterprise architecture framework - History 1 Robertson ( (2006) Enterprise Architecture As Strategy: Creating a Foundation for Business Execution https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Enterprise architecture framework - History 1 A 2008 research project for the development of professional certificates in enterprise and solution architecture by the British Computer Society (BCS) showed that enterprise architecture has always been inseparable from information system architecture, which is natural, since business people need information to make decisions and carry out business processes. https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Enterprise architecture framework - History 1 In 2011, the TOGAF 9.1. specification says: Business planning at the strategy level provides the initial direction to enterprise architecture.The Open Group (2011). Proceedings of the 10th IEEE International EDOC Enterprise Computing Conference (EDOC 2006), October 2006, p23-32. https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Enterprise architecture framework - History 1 * Zachman Framework – an architecture framework, based on the work of John Zachman at IBM in the 1980s https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

TOGAF - Enterprise architecture domains 1 * Business architecture which defines the business strategy, governance, organization, and key business processes of the organization https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

TOGAF - Enterprise architecture domains 1 * Applications architecture which provides a blueprint for the individual application systems to be deployed, the interactions between the application systems, and their relationships to the core business processes of the organization with the frameworks for services to be exposed as business functions for integration https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

TOGAF - Enterprise architecture domains 1 * Data architecture which describes the structure of an organization's logical and physical data assets and the associated data management resources https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

TOGAF - Enterprise architecture domains 1 * Technical architecture, or technology architecture, which describes the hardware, software, and network infrastructure needed to support the deployment of core, mission- critical applications https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Service oriented architecture - Service-oriented enterprise architecture 1 This umbrella architecture incorporates service, composition, and inventory architectures, plus any enterprise-wide technological resources accessed by these architectures e.g. an ERP software|ERP system. This can be further supplemented by including enterprise-wide standards that apply to the aforementioned architecture types. Any segments of the enterprise that are not service-oriented can also be documented in order to consider transformation requirements if a service needs to communicate with the business processes automated by such segments. https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Enterprise Life Cycle - Enterprise Architecture Process 1 As a prerequisite to the development of every enterprise architecture, each Agency should establish the need to develop an EA and formulate a strategy that includes the definition of a vision, objectives, and principles https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Federation of Enterprise Architecture Professional Organizations 1 The 'Federation of Enterprise Architecture Professional Organizations' (FEAPO) is a worldwide association of professional organizations which have come together to provide a forum to standardize, professionalize, and otherwise advance the discipline of Enterprise Architecture. https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Federation of Enterprise Architecture Professional Organizations 1 The current members of the FEAPO are:Federation of EA Professional Organizations - Directory, http://feapo.org, Accessed: 18 Nov 2013 https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Federation of Enterprise Architecture Professional Organizations 1 * Association for Enterprise InformationEnterprise Architecture Working Group, Association for Enterprise Information, http://afei.org/WorkingGroups/architecture/P ages/default.aspx, Retrieved 18 Nov 2013 https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Federation of Enterprise Architecture Professional Organizations 1 * Australian Computer Society https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Federation of Enterprise Architecture Professional Organizations 1 * Center for Advancement for the Enterprise Architecture Profession https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Federation of Enterprise Architecture Professional Organizations 1 * DAMA International Education Research Foundation https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Federation of Enterprise Architecture Professional Organizations 1 * IEEE Computer SocietyWalrad, Chuck, et al. Architecting the Profession of Enterprise Architecture| The Roadmap Journey. IT Professional, 24 Jan. 2013(2013): 1-1. https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Federation of Enterprise Architecture Professional Organizations 1 * American_Council_for_Technology_and_Indus try_Advisory_Council | Industry Advisory Council (Enterprise Architecture Shared Interest Group) https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Federation of Enterprise Architecture Professional Organizations 1 * Institute_of_IT_Professionals | Institute of Information Technology Professionals New Zealand https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Federation of Enterprise Architecture Professional Organizations 1 * International Council on Systems EngineeringMartin, James, et al. Team 4: Towards a Common Language for Systems Praxis. International Federation For Systems Research (2012): 75. https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Federation of Enterprise Architecture Professional Organizations 1 * International Institute of Business Analysis https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Federation of Enterprise Architecture Professional Organizations 1 * National Association of State Chief Information OfficersStrategic Partners - Enterprise Architecture and Governance Committee, http://www.nascio.org/committees/ea/, Retrieved 18 Nov 2013 https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Federation of Enterprise Architecture Professional Organizations 1 * Netherlands Architecture Forum https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Federation of Enterprise Architecture Professional Organizations - Publications 1 The focus of this paper is to provide a unified perspective of enterprise architecture to a wide-ranging audience, not just to the architects themselves, but also to the people who interact with the architects, and others who want to learn about enterprise architecture.Cameron, Brian; The FEAPO Enterprise Architecture Perspective Initiative, Architecture and Governance, 6 Nov 2013(2013): issue 9-4 https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Zachman Framework - Framework for enterprise architecture 1 [ http://www.ies.aust.com/PDF- papers/zachman3.pdf Concepts of the Framework for Enterprise Architecture: Background, Description and Utility] https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Zachman Framework - Framework for enterprise architecture 1 In 2008 Zachman Enterprise introduced the Zachman Framework: The Official Concise Definition as a new Zachman Framework standard. https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Zachman Framework - Base for other enterprise architecture frameworks 1 Less obvious are the ways the original Zachman framework has stimulated the development of other enterprise architecture frameworks, such as in the NIST Enterprise Architecture Model, the C4ISTAR|C4ISR AE, the DOE AE, and the DoDAF: https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Zachman Framework - Base for other enterprise architecture frameworks 1 * The Federal Enterprise Architecture Framework (FEAF) is based on the Zachman Framework but only addresses the first three columns of Zachman, using slightly different names, and focuses in the top of the three rows.Roland Traunmüller (2004). Electronic Government p. 51 (see [ http://books.google.nl/books?id=QjB5c_v- uMwCpg=PA51dq=%22Zachman+Framework%22 +updatedlr=lang_enas_brr=0as_pt=ALLTYPES here]) https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Zachman Framework - Example: One-VA Enterprise Architecture 1 The Zachman Framework methodology has for example been used by the United States Department of Veterans Affairs (VA) to develop and maintain its One-VA Enterprise Architecture in 2001 https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Zachman Framework - Example: One-VA Enterprise Architecture 1 The Department of Veterans Affairs at the beginning of the 21st century planned to implement an enterprise architecture fully based on the Zachman Framework. https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Zachman Framework - Example: One-VA Enterprise Architecture 1 * The Zachman Framework was used as a reference model to initiate enterprise architecture planning in 2001. https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Zachman Framework - Example: One-VA Enterprise Architecture 1 * Somewhere in between the VA Zachman Framework Portal was constructed. https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Zachman Framework - Example: One-VA Enterprise Architecture 1 * This VA Zachman Framework Portal is still in use as a reference model for example in the determination of EA information collected from various business and project source documents. https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Zachman Framework - Example: One-VA Enterprise Architecture 1 * Now somewhere in the past this A Tutorial on the Zachman Architecture Framework. https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Zachman Framework - Example: One-VA Enterprise Architecture 1 Eventually an enterprise architecture repository was created at the macro level by the Zachman framework and at a cell level by the meta-model outlined below.[ http://www.va.gov/oit/ea/4_3/process/model ing/metamodel.html Meta-Model Cell Details] Accessed 25 Dec 2009 https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Zachman Framework - Example: One-VA Enterprise Architecture 1 has been incorporated within the VA-EA to provide a symbolic representation of the Metamodeling|metamodel it used, to describe the One-VA Enterprise Architecture and to build an EA Repository without the use of Commercial EA Repository Software https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Zachman Framework - Example: One-VA Enterprise Architecture 1 However, this tool permitted defining entities and relationships and for defining properties upon both entities and relationships, which made it sufficient for building an EA repository, considering the technology available in early 2003. The personal motivation in selecting this tool was that none of the commercial repository tools then available provided a true Zachman Framework representation, and were highly proprietary, making it difficult to incorporate components from other vendors or from open source. https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Zachman Framework - Example: One-VA Enterprise Architecture 1 # Progressing through the rows from top to bottom, one can trace-out the Systems Development Life Cycle (SDLC) which is a de facto standard across the Information Industry; https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Zachman Framework - Example: One-VA Enterprise Architecture 1 # The diagram emphasizes the importance of the often-neglected Zachman Row-Six (the Integrated, Operational Enterprise View). Representations in Mr. Zuech’s interpretation of Zachman row-six consist, largely, of measurable service improvements and cost savings/avoidance that result from the business process and technology innovations that were developed across rows two through five. https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Zachman Framework - Example: One-VA Enterprise Architecture 1 Row-six provides measured return on investment for Individual Projects and, potentially, for the entire investment portfolio. Without row-six the Framework only identifies sunk-cost, but the row-six ROI permits it to measure benefits and to be used in a continuous improvement process, capturing best practices and applying them back through row-two. https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Treasury Enterprise Architecture Framework 1 May 2012 this framework has been subsumed by evolving Federal Enterprise Architecture Policy as documented in The Common Approach to Federal Enterprise Architecture.whitehouse.gov (May 12, 2012)[ http://www.whitehouse.gov/sites/default/file s/omb/assets/egov_docs/common_approach_ to_federal_ea.pdf The Common Approach to Federal Enterprise Architecture] https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Treasury Enterprise Architecture Framework 1 The material presented here is obsolete and only useful for historical reference and is not the current policy in use by the Department of the Treasury. https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Treasury Enterprise Architecture Framework - Overview 1 The Treasury Enterprise Architecture Framework (TEAF) an Enterprise architecture framework|architectural framework that supports Treasury’s business processes in terms of products https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Treasury Enterprise Architecture Framework - Overview 1 * Guidance to Treasury bureaus concerning the development and evolution of information systems architecture, https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Treasury Enterprise Architecture Framework - Overview 1 * A unifying concept, common principles, technologies, and standards for information systems, and https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Treasury Enterprise Architecture Framework - Overview 1 * A template for the development of the Enterprise Architecture. https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Treasury Enterprise Architecture Framework - Overview 1 The TEAF's functional, information and organizational architecture views collectively model the organizations processes, procedures, and business operations. By grounding the architecture in the business of the organization, the TEAF defines the core business procedures and enterprise processes. Through its explicit models, a TEAF-based architecture enables the identification and reasoning of enterprise- and system-level concerns and investment decisions. https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Treasury Enterprise Architecture Framework - History 1 The Treasury Enterprise Architecture Framework (TEAF) is derived from earlier treasury models, such as the US Treasury model (TISAF) released 1997, and the Federal Enterprise Architecture Framework (FEAF), released in 1999.Jaap Schekkerman (2003). How to Survive in the Jungle of Enterprise Architecture Frameworks. p.113 The first version of the TEAF was released July 2000. https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Treasury Enterprise Architecture Framework - History 1 The Treasury Enterprise Architecture will provide a framework to guide IT investment planning, streamline systems, and ensure that IT programs align with business requirements and strategic goals.[ http://www.treas.gov/offices/cio/egov/ E- Government] U.S https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Treasury Enterprise Architecture Framework - Enterprise Architecture 1 The Enterprise Architecture is a vital part of the enterprise’s decision-making process, and will evolve along with the enterprise’s mission https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Treasury Enterprise Architecture Framework - Enterprise Architecture 1 The TEAF has been designed to help both the bureaus and the Department develop and maintain their Enterprise Architectures. The TEAF aims to establish a common Enterprise Architecture structure, consistent practices, and common terminology; and to institutionalize Enterprise Architecture governance across the Department. This architectural consistency will facilitate integration, information sharing, and exploitation of common requirements across Treasury. https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Treasury Enterprise Architecture Framework - Enterprise Architecture Framework 1 The purpose of the Enterprise Architecture Framework is to provide a structure for producing an Enterprise Architecture (EA) and managing Enterprise Architecture assets. To reduce the complexity and scope of developing and using an Enterprise Architecture, it must be subdivided so that portions may be used independently or built incrementally in separate projects. The TEAF subdivides an Enterprise Architecture by: https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Treasury Enterprise Architecture Framework - Enterprise Architecture Framework 1 The TEAF identifies, as shown in the figure, resources and work products that provide direction for EA development, work products constituting the EA description, and work products documenting how to accomplishment an EA implementation. The resources and work products for EA direction and accomplishment are not part of the EA description itself, but are developed and applied during the overall enterprise life cycle. The TEAF Matri, organizes the subdivisions of the EA description and demonstrates the relationships among them. The following sections describe the subdivisions of the EA and their relationships to the TEAF Matrix. https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Treasury Enterprise Architecture Framework - TEAF Matrix of Views and Perspectives 1 The TEAF Matrix is a simplified portrayal of an EA structure to aid in understanding important EA aspects from various vantage points (views and perspectives). The TEAF Matrix aims to provide a simple, uniform structure to an entire framework. As depicted in the figure, the TEAF Matrix consists of four architectural views (Functional, Information, Organizational, and Infrastructure), which are shown as columns, and four perspectives (Planner, Owner, Designer, and Builder), which appear as rows. The TEAF Matrix is a four-by- four matrix with a total of 16 cells. The views and perspectives are described in the following sections. https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Treasury Enterprise Architecture Framework - TEAF Matrix of Views and Perspectives 1 When an EA description work product is shown within one cell of the TEAF Matrix, it means that the main vantage points for developing that work product correspond to that column (view) and row (perspective). However, information from other views (and sometimes other perspectives) is needed to produce a work product. Not all cells must be “filled-in” by producing an associated work product. Each bureau must define in its EA Roadmap its plans for producing and using an EA to match its needs. https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Treasury Enterprise Architecture Framework - Enterprise Life Cycle activities 1 An Enterprise Life Cycle integrates the management, business, and engineering life cycle processes that span the enterprise to align its business and IT activities. Enterprise Life Cycle refers generally to an organization’s approach for managing activities and making decisions during ongoing refreshment of business and technical practices to support its enterprise mission. These activities include investment management, project definition, configuration management, accountability, and guidance for systems development according to a System Development Life Cycle (SDLC). The Enterprise Life Cycle applies to enterprise-wide planning activities and decision making. By contrast, a System Development Life Cycle generally refers to practices for building individual systems. Determining what systems to build is an enterprise-level decision. https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Treasury Enterprise Architecture Framework - Enterprise Life Cycle activities 1 The figure on the left depicts notional activities of an Enterprise Life Cycle methodology. Within the context of this document, Enterprise Life Cycle does not refer to a specific methodology or a specific bureau’s approach. Each organization needs to follow a documented Enterprise Life Cycle methodology appropriate to its size, the complexity of its enterprise, and the scope of its needs. https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Treasury Enterprise Architecture Framework - Products 1 The TEAF provides a unifying concept, common terminology and principles, common standards and formats, a normalized context for strategic planning and budget formulation, and a universal approach for resolving policy and management issues. It describes the enterprise information systems architecture and its components, including the architectures purpose, benefits, characteristics, and structure. The TEAF introduces various architectural views and delineates several modeling techniques. Each view is supported with graphics, data repositories, matrices, or reports (i.e., architectural products). https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Treasury Enterprise Architecture Framework - Products 1 The figure shows a matrix with four views and four perspectives. Essential products are shown across the top two rows of the matrix. It is notable that the TEAF includes an Information Assurance Trust model, the Technical Reference Model, and standards profiles as essential work products. These are not often addressed as critical https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Treasury Enterprise Architecture Framework - Products 1 framework components. One of these frameworks should provide a means to logically structure and organize the selected EA products. Now, in order to effectively create and maintain the EA products, a toolset should be selected. https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Treasury Enterprise Architecture Framework - System Interface Description 1 The System Interface Description (SID) links together the Organizational and Infrastructure Views by depicting the assignments of systems and their interfaces to the nodes and needlines described in the Node Connectivity Description. The Node Connectivity Description for a given architecture shows nodes (not always defined in physical terms), while the System Interface Description depicts the systems corresponding to the system nodes. The System Interface Description can be produced at four levels, as described below. Level 1 is an essential work product, while Levels 2, 3, and 4 are supporting work products. https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Treasury Enterprise Architecture Framework - System Interface Description 1 The System Interface Description identifies the interfaces between nodes, between systems, and between the components of a system, depending on the needs of a particular architecture. A system interface is a simplified or generalized representation of a communications pathway or network, usually depicted graphically as a straight line, with a descriptive label. Often, pairs of connected systems or system components have multiple interfaces between them. The System Interface Description depicts all interfaces between systems and/or system components that are of interest to the architect. https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Treasury Enterprise Architecture Framework - System Interface Description 1 The graphic descriptions and/or supporting text for the System Interface Description should provide details concerning the capabilities of each system. For example, descriptions of information systems should include details concerning the applications present within the system, the infrastructure services that support the applications, and the means by which the system processes, manipulates, stores, and exchanges data. https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Enterprise Architecture Planning 1 'Enterprise Architecture Planning' (EAP) in Enterprise Architecture is the planning process of defining Enterprise Architecture|architectures for the use of information in support of the business and the plan for implementing those architectures.The Chief Information Officers Council (1999). [ http://www.cio.gov/Documents/fedarch1.pdf Federal Enterprise Architecture Framework Version 1.1] September 1999. https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Enterprise Architecture Planning - Overview 1 Hill (1992) Enterprise Architecture Planning: Developing a Blueprint for Data, Applications, and Technology https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Enterprise Architecture Planning - Overview 1 This hierarchy of activity is represented in the figure above, in which the layers are implemented in order, from top to bottom. Based on the Business Systems Planning (BSP) approach developed by John Zachman, EAP takes a data-centric approach to architecture planning to provide data quality, access to data, adaptability to changing requirements, data interoperability and sharing, and cost containment. This view counters the more traditional view that applications should be defined before data needs are determined orx provided for. https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Enterprise Architecture Planning - Zachman framework 1 EAP defines the blueprint for subsequent design and implementation and it places the planning/defining stages into a framework. It does not explain how to define the top two rows of the Zachman Framework in detail but for the sake of the planning exercise, abbreviates the analysis. The Zachman Framework provides the broad context for the description of the architecture layers, while EAP focuses on planning and managing the process of establishing the business alignment of the architectures. https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Enterprise Architecture Planning - Zachman framework 1 EAP is planning that focuses on the development of matrixes for comparing and analyzing data, applications, and technology. Most important, EAP produces an implementation plan. Within the Federal Enterprise Architecture, EAP will be completed segment enterprise by segment enterprise. The results of these efforts may be of Governmentwide value; therefore, as each segment completes EAP, the results will be published on the ArchitecturePlus web site. https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Enterprise Architecture Planning - EAP components 1 * Layer 1 - getting started : This layer leads to producing an EAP workplan and stresses the necessity of high-level management commitment to support and resource the subsequent six components (or steps) of the process. It consists of Planning Initiation, which covers in general, decisions on which methodology to use, who should be involved, what other support is required, and what toolset will be used. https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Enterprise Architecture Planning - EAP components 1 * Layer 2 - where we are today : This layer provides a baseline for defining the eventual architecture and the long-range migration plan. It consists of: https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Enterprise Architecture Planning - EAP components 1 ** Business process modeling, the compilation of a knowledge base about the business functions and the information used in conducting and supporting the various business processes, and https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Enterprise Architecture Planning - EAP components 1 ** Current Systems and Technology, the definition of current application systems and supporting technology platforms. https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Enterprise Architecture Planning - EAP components 1 * Layer 3 - the vision of where we want to be : The arrows delineate the basic definition process flow: data architecture, applications architecture, and technology architecture. It consists of: https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Enterprise Architecture Planning - EAP components 1 ** Data Architecture - Definition of the major kinds of data needed to support the business. https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Enterprise Architecture Planning - EAP components 1 ** Applications Architecture - Definition of the major kinds of applications needed to manage that data and support the business functions. https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Enterprise Architecture Planning - EAP components 1 ** Technology Architecture - Definition of the technology platforms needed to support the applications that manage the data and support the business functions. https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Enterprise Architecture Planning - EAP components 1 * Layer 4 - how we plan to get there : This consists of the Implementation / Migration Plans - Definition of the sequence for implementing applications, a schedule for implementation, a cost/benefit analysis, and a clear path for migration. https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Enterprise Architecture Planning - EAP methodology 1 The Enterprise Architecture Planning (EAP) methodology is beneficial to understanding the further definition of the Federal Enterprise Architecture Framework at level IV. EAP is a how to approach for creating the top two rows of the Zachman Framework, Planner and Owner. The design of systems begins in the third row, outside the scope of EAP. https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Enterprise Architecture Planning - EAP methodology 1 EAP focuses on defining what data, applications, and technology architectures are appropriate for and support the overall enterprise. Exhibit 6 shows the seven components (or steps) of EAP for defining these architectures and the related migration plan. The seven components are in the shape of a wedding cake, with each layer representing a different focus of each major task (or step). https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Enterprise Architecture Planning - Applications 1 Spewak approach to Federal Enterprise Architecture has helped organizations with modeling, business strategy planning, process improvement, data warehousing, and various support systems designs, data administration standards, object-oriented and information engineering methodologies, and project management. https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Enterprise Architecture Assessment Framework 1 and to advance the use of enterprise architecture in the federal government.Pallab Saha (2009) Advances in Government Enterprise Architecture https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Enterprise Architecture Assessment Framework 1 The version 2.2 of the framework was released in October 2007,OMB (july 2007) Federal Enterprise Architecture Program EA Assessment Framework 2.2. (Online copy [ http://www.scribd.com/doc/6846223/OMB- EA-Assessment-Framework-22 here]) and version 3.1 in June 2009. https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Enterprise Architecture Assessment Framework - Overview 1 The OMB Enterprise Architecture Assessment Framework (the Framework) helps Office of Management and Budget|OMB and the List of United States federal agencies|agencies assess the capability of enterprise architecture programs to guide Information technology|IT investments.[ http://www.whitehouse.gov/omb/e-gov/fea/ Federal Enterprise Architecture], Office of Management and Budget, USA https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Enterprise Architecture Assessment Framework - Overview 1 Enterprise Architecture Assessment Framework (EAAF) version 3.1 identifies the measurement areas and criteria by which agencies are expected to use the EA to drive performance improvements that result in the following outcomes: https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Enterprise Architecture Assessment Framework - Overview 1 * Saving money and avoiding cost through collaboration and reuse, productivity enhancements, and elimination of redundancy; https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Enterprise Architecture Assessment Framework - Overview 1 * Strengthening the quality of agency investment portfolios by improving security, inter-operability, reliability, availability, solution development and service delivery time, and overall end-user performance; https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Enterprise Architecture Assessment Framework - Overview 1 * Improving the quality, availability and sharing of data and information government-wide; and https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Enterprise Architecture Assessment Framework - Overview 1 [ http://www.whitehouse.gov/sites/default/file s/omb/assets/fea_docs/OMB_EA_Assessment _Framework_v3_1_June_2009.pdf Improving Agency Performance Using Information and Information Technology : Enterprise Architecture Assessment Framework v3.1] June 2009 https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Enterprise Architecture Assessment Framework - Performance Improvement Lifecycle 1 Government agencies are continually assessing current performance, identifying opportunities for improvement, and translating them into specific actions. Enterprise architecture is an integrated management practice that maximizes the use of an agency’s resources to achieve their goals. Architecture describes the pathway from strategic goals and objectives, through investments, to measurable performance improvements for the entire enterprise or a portion. https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Enterprise Architecture Assessment Framework - Performance Improvement Lifecycle 1 Continuous performance improvement is the principal driver connecting EA program staff with key business stakeholders across each phase of the Performance Improvement Lifecycle. Agency Chief Architects and EA program staff: https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Enterprise Architecture Assessment Framework - Performance Improvement Lifecycle 1 * identify and prioritize enterprise segments and opportunities to improve mission performance, linked to agency goals and objectives; https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Enterprise Architecture Assessment Framework - Performance Improvement Lifecycle 1 * plan a course of action to close performance gaps, using common or shared information assets and information technology assets; https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Enterprise Architecture Assessment Framework - Performance Improvement Lifecycle 1 * allocate agency resources supporting program management and project execution; https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Enterprise Architecture Assessment Framework - Performance Improvement Lifecycle 1 * measure and assess performance to verify and report results; and https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Enterprise Architecture Assessment Framework - Performance Improvement Lifecycle 1 * assess feedback on program performance to enhance architecture, investment and implementation decisions. https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Enterprise Architecture Assessment Framework - Performance Improvement Lifecycle 1 Opportunities to improve mission performance are prioritized in terms of their relative value to the agency’s strategic goals and objectives in the enterprise transition plan (ETP) and segment architecture. https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Enterprise Architecture Assessment Framework - Architect 1 Segments are defined using the Federal Enterprise Architecture (FEA) reference models. https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Enterprise Architecture Assessment Framework - Invest 1 Performance improvement opportunities identified during the “Architect” process are ideally addressed through an agency portfolio of IT investments. This step defines the implementation and funding strategy for individual initiatives in the Enterprise Transition Plan (ETP) and described in the segment architectures. Program management plans are created to implement the individual solutions. https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Enterprise Architecture Assessment Framework - Implement 1 Projects are executed and tracked throughout the system development life cycle (SDLC). Achievement of the program / project plan within acceptable variance for schedule and budget is measured and reported through Earned Value Management (EVM) process. https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Enterprise Architecture Assessment Framework - Measure, assess and improve 1 Information and information technology, as critical enablers of program performance improvements, must be assessed and evaluated in the context of agency missions and outcome-oriented results defined in the enterprise-wide performance architecture. https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Enterprise Architecture Assessment Framework - Measure, assess and improve 1 Performance improvement plans and priorities, including those previously gathered under the PART and Performance Assessment Report (PAR) programs, are reflected in the agency EA, particularly the performance architecture and ETP. Performance metrics previously gathered are used to evaluate the results in agency performance improvement plans, identifying a program’s strengths and weaknesses and addressing ways to improve the program performance. https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Enterprise Architecture Assessment Framework - Agency submission data quality 1 OMB collects a significant amount of IT investment data and other related data from executive agencies during each phase of Performance Improvement Lifecycle. OMB uses the information for development of an IT investment portfolio as a part of the President’s budget request to Congress. https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Federal Enterprise Architecture 1 The most familiar federal enterprise architecture is the enterprise architecture of the Federal government of the United States, the U.S. Federal Enterprise Architecture (FEA) and the corresponding U.S. Federal Enterprise Architecture Framework (FEAF). This lemma will focus on this particular enterprise architecture and enterprise architecture framework. https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Federal Enterprise Architecture - Overview 1 Enterprise architecture (EA) is a management best practice for aligning business and technology resources to achieve strategic outcomes, improve organizational performance and guide federal agencies to better execute their Core business|core missions. An EA describes the current and future state of the agency, and lays out a plan for transitioning from the current state to the desired future state. A federal enterprise architecture is a work in progress to achieve these goals. https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Federal Enterprise Architecture - Overview 1 The U.S. Federal Enterprise Architecture (FEA) is an initiative of the U.S. Office of Management and Budget, Office of E- Government and IT, that aims to realize the value of enterprise architecture within the U.S. Federal Government. Enterprise Architecture became a recognized strategic and management best practice in U.S. Federal Government with the passage of the Clinger- Cohen Act in 1996. https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Federal Enterprise Architecture - Overview 1 There are numerous benefits that accrue from implementing and using an enterprise architecture within the U.S. Federal Government. Among them is to provide a common approach for IT acquisition in the Federal government of the United States|United States federal government. It is also designed to ease sharing of information and resources across federal agencies, reduce costs, and improve citizen services. https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Federal Enterprise Architecture - History 1 In May 2012 OMB published a full new guide, the Common Approach to Federal Enterprise Architecture. https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Federal Enterprise Architecture - History 1 The FEAF overall framework created that time, see image, includes the first three columns of the Zachman Framework and the Steven Spewak|Spewak's Enterprise Architecture Planning methodology. https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Federal Enterprise Architecture - History 1 Overall the Federal Enterprise Architecture (FEA) is mandated by a series of federal laws and mandates. These federal laws have been: https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Federal Enterprise Architecture - History 1 * PRA 1995 : Paperwork Reduction Act https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Federal Enterprise Architecture - History 1 * FISMA 2002 : Federal Information Security Management Act of 2002|Federal Information Security Management Act https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Federal Enterprise Architecture - History 1 Suplementairy OMB circulars have been: https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Federal Enterprise Architecture - History 1 * A-11 : Preparation, Submission and Execution of the Budget https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Federal Enterprise Architecture - History 1 * A-130 : OMB Circular A-130 Management of Federal Information Resources, first issued in December 1985 https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Federal Enterprise Architecture - Reference models 1 The FEA is built using an assortment of reference models that develop a common Taxonomy (general)|taxonomy and Ontology (information science)|ontology for describing IT resources. These include the, (see image): https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Federal Enterprise Architecture - Reference models 1 It is designed to ease sharing of information and resources across federal agencies, reduce costs, and improve citizen services. It is an initiative of the US Office of Management and Budget that aims to comply with the Clinger- Cohen Act. https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Federal Enterprise Architecture - Performance Reference Model (PRM) 1 The PRM is a standardized framework to measure the performance of major IT investments and their contribution to program performance. The PRM has three main purposes: https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Federal Enterprise Architecture - Performance Reference Model (PRM) 1 # Help produce enhanced performance information to improve strategic and daily decision-making; https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Federal Enterprise Architecture - Performance Reference Model (PRM) 1 # Improve the alignment — and better articulate the contribution of — inputs to outputs and outcomes, thereby creating a clear “line of sight” to desired results; and https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Federal Enterprise Architecture - Performance Reference Model (PRM) 1 # Identify performance improvement opportunities that span traditional organizational structures and boundaries https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Federal Enterprise Architecture - Performance Reference Model (PRM) 1 In addition, the PRM was informed by what agencies are currently measuring through PART assessments, GPRA, enterprise architecture, and Capital Planning and Investment Control https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Federal Enterprise Architecture - Performance Reference Model (PRM) 1 *Mission and Business Results https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Federal Enterprise Architecture - Business Reference Model (BRM) 1 The BRM is the first layer of the Federal Enterprise Architecture and it is the main viewpoint for the analysis of data, service components and technology. https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Federal Enterprise Architecture - Business Reference Model (BRM) 1 The BRM is broken down into four areas: https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Federal Enterprise Architecture - Business Reference Model (BRM) 1 The Business Reference Model provides a framework that facilitates a functional (as opposed to organizational) view of the federal government’s LoBs, including its internal operations and its services for the citizens, independent of the agencies, bureaus and offices that perform them. By describing the federal government around common business areas instead of by a stovepiped, agency-by- agency view, the BRM promotes agency collaboration and serves as the underlying foundation for the FEA and E-Gov strategies. https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Federal Enterprise Architecture - Business Reference Model (BRM) 1 While the BRM does provide an improved way of thinking about government operations, it is only a model; its true utility can only be realized when it is effectively used. The functional approach promoted by the BRM will do little to help accomplish the goals of E- Government if it is not incorporated into EA business architectures and the management processes of all Federal agencies and OMB. https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Federal Enterprise Architecture - Service Component Reference Model (SRM) 1 The Service Component Reference Model (SRM) is a business and performance-driven, functional framework that classifies Service Components with respect to how they support business and/or performance objectives. The SRM is intended for use to support the discovery of government-wide business and application Service Components in IT investments and assets. The SRM is structured across horizontal and vertical service domains that, independent of the business functions, can provide a leverage- able foundation to support the reuse of applications, application capabilities, components, and business services. https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Federal Enterprise Architecture - Service Component Reference Model (SRM) 1 * Process Automation Services https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Federal Enterprise Architecture - Service Component Reference Model (SRM) 1 Each Service Domain is decomposed into Service Types. For example, the three Service Types associated with the Customer Services Domain are: Customer Preferences; Customer Relationship Management; and Customer Initiated Assistance. And each Service Type is decomposed further into components. For example, the four components within the Customer Preferences Service Type include: Personalization; Subscriptions; Alerts and Notifications; and Profile Management. https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Federal Enterprise Architecture - Data Reference Model (DRM) 1 The Data Reference Model (DRM) describes, at an aggregate level, the data and information that support government program and business line operations. This model enables agencies to describe the types of interaction and exchanges that occur between the Federal Government and citizens. The DRM categorizes government information into greater levels of detail. It also establishes a classification for Federal data and identifies duplicative data resources. A common data model will streamline information exchange processes within the Federal government and between government and external stakeholders. https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Federal Enterprise Architecture - Data Reference Model (DRM) 1 Volume One of the DRM provides a high-level overview of the structure, usage, and data- identification constructs. This document: https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Federal Enterprise Architecture - Data Reference Model (DRM) 1 * Provides an introduction and high-level overview of the contents that will be detailed in Volumes 2–4 of the model; https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Federal Enterprise Architecture - Data Reference Model (DRM) 1 * Encourages Community of interest (computer security)|community of interest development of the remaining volumes; and https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Federal Enterprise Architecture - Data Reference Model (DRM) 1 * Provides the basic concepts, strategy, and structure to be used in future development. https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Federal Enterprise Architecture - Data Reference Model (DRM) 1 The DRM is the starting point from which data architects should develop modeling standards and concepts. The combined volumes of the DRM support data classification and enable horizontal and vertical information sharing. https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Federal Enterprise Architecture - Technical Reference Model (TRM) 1 The TRM is a component-driven, technical framework categorizing the standards and technologies to support and enable the delivery of Service Components and capabilities. It also unifies existing agency TRMs and E-Gov guidance by providing a foundation to advance the reuse and standardization of technology and Service Components from a government-wide perspective. https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Federal Enterprise Architecture - Technical Reference Model (TRM) 1 * Service Areas : represent a technical tier supporting the secure construction, exchange, and delivery of Service Components. Each Service Area aggregates the standards and technologies into lower-level functional areas. Each Service Area consists of multiple Service Categories and Service Standards. This hierarchy provides the framework to group standards and technologies that directly support the Service Area. (Purple headings) https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Federal Enterprise Architecture - Technical Reference Model (TRM) 1 * Service Categories : classify lower levels of technologies and standards with respect to the business or technology function they serve. In turn, each Service Category comprises one or more Service Standards. (Bold-face groupings) https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Federal Enterprise Architecture - Technical Reference Model (TRM) 1 * Service Standards : define the standards and technologies that support a Service Category. To support agency mapping into the TRM, many of the Service Standards provide illustrative specifications or technologies as examples.(Plain text) https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Federal Enterprise Architecture - Technical Reference Model (TRM) 1 The figure on the right provides a high-level depiction of the TRM. https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Federal Enterprise Architecture - Technical Reference Model (TRM) 1 Aligning agency capital investments to the TRM leverages a common, standardized vocabulary, allowing interagency discovery, collaboration, and interoperability. Agencies and the federal government will benefit from economies of scale by identifying and reusing the best solutions and technologies to support their business functions, mission, and target architecture. Organized in a hierarchy, the TRM categorizes the standards and technologies that collectively https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Federal Enterprise Architecture - Technical Reference Model (TRM) 1 support the secure delivery, exchange, and construction of business and application Service Components that may be used and leveraged in a Component-based software engineering|component-based or service- oriented architecture. https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Federal Enterprise Architecture - FEA Architecture levels 1 In the FEA enterprise, segment, and solution architecture provide different business perspectives by varying the level of detail and addressing related but distinct concerns. Just as enterprises are themselves hierarchically organized, so are the different views provided by each type of architecture. The Federal Enterprise Architecture Practice Guidance (2006) has defined three types of architecture: https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Federal Enterprise Architecture - FEA Architecture levels 1 * Solution architecture. https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Federal Enterprise Architecture - FEA Architecture levels 1 * structure: segment architecture inherits the framework used by the EA, although it may be extended and specialized to meet the specific needs of a core mission area or common or shared service. https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Federal Enterprise Architecture - FEA Architecture levels 1 * reuse : segment architecture reuses important assets defined at the enterprise level including: data; common business processes and investments; and applications and technologies. https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Federal Enterprise Architecture - FEA Architecture levels 1 * alignment : segment architecture aligns with elements defined at the enterprise level, such as business strategies, mandates, standards, and performance measures. https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Federal Enterprise Architecture - FEA Architecture levels 1 Solution architecture is commonly related to segment architecture and enterprise architecture through definitions and constraints https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Federal Enterprise Architecture - FEA tools 1 A number of modeling tools enable you to capture the Federal Enterprise Architect reference models and align your enterprise architecture against them. https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Federal Enterprise Architecture - FEA tools 1 *Adaptive Inc.[ http://www.adaptive.com Metadata Management and Enterprise Architecture Solutions]. Adaptive. Retrieved on 2013-07-29. https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Federal Enterprise Architecture - FEA tools 1 *alfabet with the software suite [ http://www.alfabet.com/en/offering/approach/ planningIT] https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Federal Enterprise Architecture - FEA tools 1 *Troux Technologies Architect https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Federal Enterprise Architecture - FEA tools 1 *Iteraplan – Open Source EA Tool https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Federal Enterprise Architecture - FEA tools 1 *MEGA International MEGA Suite for Federal Enterprise Architecture [ http://www.mega.com/ MEGA]. MEGA. Retrieved on 2013-07-29. https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Federal Enterprise Architecture - FEA tools 1 The CIO Council's [ http://et.gov ET.gov site] can be used to identify technical specifications (standards) that are not yet included in the TRM but should be. Those that have been identified thus far can be discovered using the [ http://etgov.i411.com/etgov/websearchservle t?toplevel=true advanced ET.gov search service] hosted by [ http://www.intelligenx.com/ IntelligenX]. https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Application Portability Profile - APP and the NIST Enterprise Architecture Model 1 The Application Portability Profile (APP) - The U.S. Government’s Open System Environment Profile Version 3.0 provides recommendations on a set of industry, Federal, national, international and other specifications that define interfaces, services, protocols, and data formats to support an Open System Environment (OSE). https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Application Portability Profile - APP and the NIST Enterprise Architecture Model 1 The APP addresses the lowest architecture in the NIST Enterprise Architecture Model, i.e., the Delivery System Architecture. On this level the hardware of the computer architecture, the software and the communications are being specified. Based on these specification recommendations, various services and agencies have defined detailed technical reference models. https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Jaap Schekkerman - Institute For Enterprise Architecture Developments 1 In 2001 Schekkerman founded the Institute For Enterprise Architecture Developments (IFEAD). for research in and knowledge exchange about the emerging field of Enterprise Architecture.Jaap Schekkerman (2004) How to Survive in the Jungle of Enterprise Architecture. p. 221 Some of first accomplishments of the institute were, according to Blokdijk (2008)Gerard Blokdijk (2008) Enterprise Architecture 100 Success Secrets. p. 27 https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Jaap Schekkerman - Institute For Enterprise Architecture Developments 1 : (a) Global Enterprise Architecture Organization (GEAO), a non-profit organization created by and for professionals who specialize in the field of Enterprise Architecture; https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Jaap Schekkerman - Institute For Enterprise Architecture Developments 1 : (b) Federal Enterprise Architecture Certification (FEAC) Institute, provides education and training that leads to a certification in Integrated Security Framework and Federal Enterprise Architecture; https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Jaap Schekkerman - Institute For Enterprise Architecture Developments 1 : (c) DCI University, offers an 8 to 10-hour course with practical strategies to successfully implement Enterprise Architecture; and https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Jaap Schekkerman - Institute For Enterprise Architecture Developments 1 : (d) Radboud University Nijmegen (Netherlands), facilitates a 5-year Master study that addresses all the elements of Enterprise Architecture. https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Jaap Schekkerman - Institute For Enterprise Architecture Developments 1 The Institute works together with a series of institutes in the field[ http://www.enterprise- architecture.info/IFEAD_Partners.htm IFEAD: Partner Program, Alliances Affiliates]. Accessed June 11, 2013. and facilitated a series of publications in the field of Enterprise Architecture.[ http://www.enterprise- architecture.info/Publications%20Jaap%20Schekk erman.htm IFEAD; Jaap Schekkerman Enterprise Architecture Publications]. Accessed June 11, 2013. https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Jaap Schekkerman - How to Survive in the Jungle of Enterprise Architecture Frameworks 1 In his 2003 book How to Survive in the Jungle of Enterprise Architecture Frameworks Schekkerman defined enterprise architecture as: https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Jaap Schekkerman - How to Survive in the Jungle of Enterprise Architecture Frameworks 1 :Enterprise Architecture is a complete expression of the enterprise; a master plan which acts as a collaboration force between aspects of business planning such as goals, visions, strategies and governance principles; aspects of business operations such as business terms, organization structures, processes and data; aspects of automation such as information systems and databases; and the enabling technological infrastructure of the business, such as computers, Operating Systems and networks.Jaap Schekkerman (2004) How to Survive in the Jungle of Enterprise Architecture https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Jaap Schekkerman - How to Survive in the Jungle of Enterprise Architecture Frameworks 1 Starting with the Extended Enterprise Architecture Framework (E2AF) it describes Enterprise Architecture Planning (EAP), The Federal Enterprise Architecture Framework (FEAF), the Treasury Enterprise Architecture Framework (TEAF), the The Open Group Architecture Framework (TOGAF), the Zachman Framework, the Integrated Architecture Framework (IAF), the Joint Technical Architecture (JTA), the C4ISTAR|C4ISR and DoDAF, the Department of Defense Technical Reference Model (DoD TRM), and finished with the reference architecture TAFIM, CIMOSA, Purdue Enterprise Reference Architecture|PERA en the SAGA - Standards and Architectures for e-Government Applications. https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Jaap Schekkerman - Extended Enterprise Architecture Framework 1 Early 2000s Schekkerman developed the Extended Enterprise Architecture (E2A) and Extended Enterprise Architecture Framework (E2AF). The Extended Enterprise Architecture (E2A) is designed to address three different elements in a comprehensive way:Jaap Schekkerman (2001-07) [ http://www.enterprise- architecture.info/Images/Extended%20Enterp rise/Extended%20Enterprise%20Architecture. htm Extended Enterprise Architecture Framework] at enterprise-architecture.info. Accessed 11 June 2013. https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Jaap Schekkerman - Extended Enterprise Architecture Framework 1 * the element of function, and https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Jaap Schekkerman - Extended Enterprise Architecture Framework 1 According to Schekkerman (2007) in enterprise architecture style is reflecting the culture, values, norms and principles of an organization. Most of the time, the term enterprise architecture is dealing with construction and function, without any attention of the style aspect, while the style aspect reflects the cultural behavior, values, norms and principles of that organization in such a way that it reflects the corporate values of that organization. https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Jaap Schekkerman - Extended Enterprise Architecture Framework 1 59 and other elements from Federal Enterprise Architecture Framework|FEAF and TOGAF.Inge Hanschke (2010) Strategic IT Management: A Toolkit for Enterprise Architecture https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

FDIC Enterprise Architecture Framework 1 'FDIC Enterprise Architecture Framework' is the Enterprise Architecture framework of the United States Federal Deposit Insurance Corporation (FDIC). A lot of the current article is about the Enterprise Architecture Framework developed around 2005, and currently anno 2011 out-of-date. https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

FDIC Enterprise Architecture Framework - Overview 1 The FDIC's framework for implementing its Enterprise Architecture is based on Federal and industry best practices, including the Chief Information Officer (CIO) Council's Federal Enterprise Architecture Framework (FEAF) and the Zachman Framework for Enterprise Architecture https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

FDIC Enterprise Architecture Framework - Overview 1 The FDIC EA framework includes five components. The first component, the Business Architecture, focuses on FDIC's business needs. The next three components, the Data Architecture, Applications Architecture, and Technical Infrastructure Architectures, focus on the technological capabilities that support the business and information needs. The final component, the Security Architecture, focuses on specific aspects of interest to the Corporation that span the enterprise and must be integral parts of all other architectures. https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

FDIC Enterprise Architecture Framework - History 1 Starting in the second half of the 1990 a collective, government-wide effort, supported by the Federal CIO Council, utilizing the Federal Enterprise Architecture (FEA), has been undertaken in an effort to yield significant improvements in the management and reuse of IT investments, while improving services to citizens, and facilitating business relationships internally and externally.FDIC (2003) https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

FDIC Enterprise Architecture Framework - History 1 Blanton (2005) [ http://www.aea- dc.org/resources/2006-7-12-Gail-Verley-FDIC- EA-Business-Alignment-Gartner.pdf The FDIC Is Aligning IT to Business Through Enterprise Architecture] Gartner, Inc https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

FDIC Enterprise Architecture Framework - History 1 In 2004 the FDIC received a 2004 Enterprise Architecture Excellence Award from the John Zachman|Zachman Institute for Framework Advancement (ZIFA) for its initiative to manage corporate data collaboratively.[ http://www.fdic.gov/news/news/press/2004/ pr13104.html FDIC Receives Technology Award] https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

FDIC Enterprise Architecture Framework - FDIC EA framework 1 The FDIC EA framework from 2005 included five components. https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

FDIC Enterprise Architecture Framework - FDIC EA framework 1 * Business Architecture : The Business Architecture describes the activities and processes performed by the Corporation to achieve its mission and to realize its vision and goals. Developing the Business Architecture is the first step in creating an Enterprise Architecture (EA) that links the Corporation's business needs to its Information Technology (IT) environment. Maximizing IT support for these requirements will optimize Corporate performance. https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

FDIC Enterprise Architecture Framework - FDIC EA framework 1 * Data Architecture : The Data Architecture describes the activities required to obtain and maintain data that supports the information needed by the Corporation’s major business areas. Data and information are different. Data is the foundation of information. Data is the raw material that is processed and refined to generate information. Information consists of a collection of related data that has been processed into a form that is meaningful to the recipient. https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

FDIC Enterprise Architecture Framework - FDIC EA framework 1 * Applications Architecture : The Applications Architecture describes the major types of applications that manage data to produce the information needed to support the activities of the Corporation. The Applications Architecture provides a framework that enables the migration from the current applications catalog and software development environment to the target integrated applications, development and engineering environments. The target architecture promotes the use of commercial and government off-the-shelf products, consolidating applications, where applicable, and the use of emerging technologies where appropriate. https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

FDIC Enterprise Architecture Framework - FDIC EA framework 1 * Technical Infrastructure Architecture : The IT infrastructure provides access to application systems and office automation tools used in performance of the business processes. The Corporation places high priority on maintaining a consistent, available, and reliable technical infrastructure. The Technical Architecture describes the underlying technology for the Corporation's business, data, and application processing. It includes the technologies used for communications, data storage, application processing, and computing platforms. https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

FDIC Enterprise Architecture Framework - FDIC EA framework 1 * Security Architecture : The Security Architecture establishes a framework for integrating safeguards into all layers of the FDIC's Enterprise Architecture. The security architecture uses a risk management and information assurance strategy that provides access control, confidentiality, integrity, and non-repudiation for the Corporation's information and systems. https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

FDIC Enterprise Architecture Framework - Future IT development 1 The banking business model has become more complex, giving rise to financial instruments such as collateralized debt obligations (CDOs) and structured investment vehicles (SIVs) to manage risk. These instruments have created greater dependencies between the domestic and international financial markets. Financial institutions must, therefore, strike a balance between regulatory, legislative and banker concerns while appropriately managing risk. https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

FDIC Enterprise Architecture Framework - Future IT development 1 As cost savings are realized from a simplified IT environment and more efficient processes, the savings will be reinvested for IT improvements or accrue to the Corporation. This self-funding model is shown on the right. https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

FDIC Enterprise Architecture Framework - Five-year technology roadmap 1 The technology roadmap outlines the major initiatives for standardizing the IT environment and increasing IT’s efficiency and effectiveness over the next five years. The initiatives were determined by various sources including business-side IT roadmaps, executive management planning meetings, client planning sessions, and client year-end reviews. The three major initiatives identified are enterprise architecture, security and privacy programs, and fiscal discipline. https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

FDIC Enterprise Architecture Framework - Five-year technology roadmap 1 The enterprise architecture initiative will focus on simplifying the environment to ensure stable and economical performance for mission-critical applications https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

FDIC Enterprise Architecture Framework - Five-year technology roadmap 1 The organization will continue to enhance IT security and privacy programs to address new and evolving risks by improving controls over sensitive data. In some cases, technology, such as scanning outgoing e-mail for sensitive information and encrypting removable storage devices, can mitigate potential risks. The other cornerstone of mitigating risk is educating employees of emerging security and privacy issues. https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

FDIC Enterprise Architecture Framework - Five-year technology roadmap 1 Lastly, in order to continue sound fiscal discipline and responsibility, the organization will establish IT baselines and metrics, study steady-state costs, manage service level agreements, and more judiciously choose new development projects. These three areas – enterprise architecture, security and privacy programs, and fiscal discipline – are shown below with the estimated time frames. https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Enterprise Interoperability - Interoperability in enterprise architecture 1 Enterprise architecture (EA) presents a high level design of enterprise capabilities in order to define successful IT projects in coherence with enterprise principals and business related requirements https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Enterprise Interoperability - Interoperability in enterprise architecture 1 The interoperability can be considered either as a principal, requirement or constraint that impact the definition of patterns to compose building blocks in the definition of targeted architectural roadmap. In this scope, EA within the TOGAF perspective, aims to reconcile interoperability requirements with potential solutions in order to enhance the capability of developed systems to be interoperable. https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Enterprise Interoperability - Interoperability in enterprise architecture 1 So as to maintain the interoperability challenge quite present in the next steps of system’s lifecycle, several models and Frameworks are developed under the topic enterprise interoperability. https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Enterprise Architecture Management 1 'Enterprise Architecture Management' (or 'EAM') in the field of Enterprise architecture describes and structures complex IT systems in terms of their business, application, information, and technical layers, and to reform programs through the planning process as strategic business demands, and as standards and guidelines for the development of local solutions and service offers. https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Enterprise Architecture Management - Overview 1 The fundamental prerequisites for effective EAM are a current, consistent baseline of information about the as-is landscape and an integrated planning process from demand to budget to reach the to-be landscape. The enterprise architecture function also involves reviewing and consolidating detailed architecture decisions and migration plans to identify efficiencies, advance standardization, and align business and IT priorities. https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Enterprise Architecture Management - Overview 1 This approach is only helpful insofar as it depicts the enterprise architecture as a snapshot in time, but it offers no reiterative process support to develop architecture solutions and test against different scenarios, Benchmarking|benchmarks, and standards as dictated by the ever converging business and IT strategy. https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Enterprise Architecture Management - Overview 1 Moreover, a model-centric approach is prohibitively time-intensive to keep updated and leaves too much room for error as changes to the architecture occur unchecked and isolated in the heads of small groups of architecture specialists. Instead, the EAM effort has to bring the highly distributed knowledge of all experts to the table and allow every participant to provide such knowledge and input in the terms that best fit the experience and expectations of the contributing stakeholders. https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Enterprise Architecture Management - Application 1 Successful Enterprise Architecture programs are approached from a management perspective as opposed to a Business model|modeling perspective. A new generation of EA Planning tools are emerging that support not only the modeling of the architecture, but also the creation of roll-out and implementation plans for continuous IT improvement over time. https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Enterprise Architecture Management - Application 1 An important aspect of this approach is support of collaboration amongst a wide group of stakeholders from both business and IT including C-level, IT strategists, planning teams, technology implementers, and business analysts, who contribute to the EA management and planning process. In this way EAM supports sustainable business strategy realization. https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Federal Enterprise Architecture Framework - History 1 Supplementary OMB circulars have been: https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

Federal Enterprise Architecture Framework - Performance Reference Model (PRM) 1 In addition, the PRM was informed by what agencies are currently measuring through PART assessments, GPRA, enterprise architecture, and Capital Planning and Investment Control https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

NIST Enterprise Architecture Model 1 [http://www.enterprise- architecture.info/Images/Documents/Federal %20EA%20Framework.pdf Federal Enterprise Architecture Framework Version 1.1] https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

NIST Enterprise Architecture Model 1 Developed late-1980s by the National Institute of Standards and Technology (NIST) and others, the federal government of the United States promoted this reference model in the 1990s as the foundation for enterprise architectures of individual U.S. government agencies and in the overall federal enterprise architecture. https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

NIST Enterprise Architecture Model - Overview 1 The NIST Enterprise Architecture Model is a five-layered model for enterprise architecture, designed for organizing, planning, and building an integrated set of information and information technology architectures. The five layers are defined separately but are interrelated and interwoven. The model defined the interrelation as follows: https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

NIST Enterprise Architecture Model - Overview 1 * Business Architecture drives the information architecture https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

NIST Enterprise Architecture Model - Overview 1 * Information architecture prescribes the information systems architecture https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

NIST Enterprise Architecture Model - Overview 1 * Information systems architecture identifies the data architecture https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

NIST Enterprise Architecture Model - Overview 1 * Data Delivery Systems (Software, Hardware, Communications) support the data architecture. https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

NIST Enterprise Architecture Model - Overview 1 The hierarchy in the model is based on the notion that an organization operates a number of business functions, each function requires information from a number of source, and each of these sources may operation one or more operation systems, which in turn contain data organized and stored in any number of data systems.John O'Looney (2002). Wiring Governments: Challenges and Possibilities for Public Managers. Greenwood Publishing Group. p.67. https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

NIST Enterprise Architecture Model - History 1 The NIST Enterprise Architecture Model is initiated in 1988 in the fifth workshop on Information Management Directions sponsored by the NIST in cooperation with the Association for Computing Machinery (ACM), the IEEE Computer Society, and the Federal Data Management Users Group (FEDMUG) https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

NIST Enterprise Architecture Model - The emerging field of information management 1 With the proliferation of information technology starting in the 1970s, the job of information management had taken a new light, and also began to include the field of data maintenance. No longer was information management a simple job that could be performed by almost anyone. An understanding of the technology involved, and the theory behind it became necessary. As information storage shifted to electronic means, this became more and more difficult. https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

NIST Enterprise Architecture Model - The emerging field of information management 1 In this emerging field the NIST had held a series of four workshops on Database and Information Management Directions since the 1970s. Each of the workshops addresses a specific theme:Fong and Goldfine (1989, p. 5) https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

NIST Enterprise Architecture Model - The emerging field of information management 1 * What information about database technology does the manager need to make prudent decisions about using new technology, in 1975. https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

NIST Enterprise Architecture Model - The emerging field of information management 1 * Information management tools from the standpoint of: uses; policies and controls; logical and physical database design in 1980; and https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

NIST Enterprise Architecture Model - The emerging field of information management 1 * The nature of information resource management practice and problems in 1985. https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

NIST Enterprise Architecture Model - The emerging field of information management 1 The fifth workshop in 1989 was held by the National Computer Systems Laboratory (NCSL) of the NIST. By then this was one of the four institutes, that performed the technical work of the NIST. The specific goal of the NCSL was to conduct research and provide scientific and technical services to aid Federal agencies in the selection, acquisition, application, and use of computer technology.Fong and Goldfine (1989, p. i) https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

NIST Enterprise Architecture Model - NIST workshop on Information Management Directions 1 The fifth Information Management Directions workshop focused on integration and productivity in information management. Five working groups considered specific aspects of the integration of knowledge, data management, systems planning, development and maintenance, computing environments, architectures and standards. Participants came from academia, industry, government and consulting firms. Among the 72 participants were Tom DeMarco, Ahmed K. Elmagarmid, Elizabeth N. Fong, Andrew U. Frank,[http://www.geoinfo.tuwien.ac.at/staff/ index.php?Current_Staff:Frank%2C_Andrew_ U. Frank, Andrew U.] Research Group Geoinformation, Vienna. Accessed JUly 15, 2013. Robert E. Fulton,David Terraso (2004) [http://www.whistle.gatech.edu/archives/04/ mar/01/fultonobit.shtml Robert Fulton, 72, dies: Engineering professor and county commissioner]. at whistle.gatech.edu Alan H. Goldfine,[http://www.informatik.uni- trier.de/~ley/pers/hd/g/Goldfine:Alan_H= Alan H. Goldfine] at DBLP. Dale L. Goodhue,[http://www.informatik.uni- trier.de/~ley/pers/hd/g/Goodhue:Dale.html Dale Goodhue] at DBLP. Richard J. Mayer, Shamkant Navathe, T. William Olle, W. Bradford Rigdon, Judith A. Quillard, Stanley Y. W. Su,[http://www.informatik.uni- trier.de/~ley/pers/hd/s/Su:Stanley_Y=_W= Stanley Y. W. Su] at DBLP. and John Zachman. https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

NIST Enterprise Architecture Model - NIST workshop on Information Management Directions 1 Tom DeMarco delivered the keynote speech, claiming that standards do more harm than good when they work against the prevailing culture, and that the essence of standardization is discovery, not innovation.Fong and Goldfine (1989, p. ix) The five working groups met to discuss different aspects of integration: https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

NIST Enterprise Architecture Model - NIST workshop on Information Management Directions 1 * the integration of technical and business data management https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

NIST Enterprise Architecture Model - NIST workshop on Information Management Directions 1 * the integration of distributed, heterogeneous computing environments, and https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

NIST Enterprise Architecture Model - NIST workshop on Information Management Directions 1 In the third working group on systems planning was chaired by John Zachman, and adopted the Zachman Framework as a basis for discussion. https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

NIST Enterprise Architecture Model - NIST workshop on Information Management Directions 1 Their aim was to takes a broader view, and describes the need for an enterprise architecture that includes an emphasis on business and information requirements https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

NIST Enterprise Architecture Model - NIST workshop on Information Management Directions 1 * The levels of architecture in an enterprise https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

NIST Enterprise Architecture Model - NIST workshop on Information Management Directions 1 * Problems addressed by architecture https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

NIST Enterprise Architecture Model - NIST workshop on Information Management Directions 1 * Benefits and risks of having architecture https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

NIST Enterprise Architecture Model - NIST workshop on Information Management Directions 1 To illustrate the levels of architecture, what has become known as the NIST Enterprise Architecture Model, was presented. https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

NIST Enterprise Architecture Model - Application in the 1990s 1 According to Zachman (1993) in the 1980s the architecture was acknowledged as a topic of interest, but there was still little consolidated theory concerning this concept.J.A Zachman (1993) [http://www.ies.aust.com/pdfpapers/zachman3.pdf Concepts for Framework for EA - Enterprise Architecture Resources] https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

NIST Enterprise Architecture Model - Application in the 1990s 1 Federal government agencies and in the overall Federal Enterprise Architecture Framework https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

NIST Enterprise Architecture Model - Foundations 1 According to Rigdon et al. (1989) an architecture is a clear representation of a conceptual framework of components and their relationship at a point in time.Rigdon et al. (1989, p. 136) It may for example represent a view of a current situation with islands of automation, redundant processes and data inconsistenciesRigdon (1989), p. 137 or a future integrated automation information structure towards which the enterprise will move in a prescribed number on years.Rigdon et al. (1989, p. 137-38) The role of standards in architecture is to enable or constrain the architecture and serve as its foundation. https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

NIST Enterprise Architecture Model - Foundations 1 In order to develop an enterprise architecture Rigdon acknowledge: https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

NIST Enterprise Architecture Model - Foundations 1 * There are multiple ways to develop an architecture https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

NIST Enterprise Architecture Model - Foundations 1 * Development and implementation should be customized to the environment https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

NIST Enterprise Architecture Model - Foundations 1 * Yet, every architecture itself can be divided into different levels. https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

NIST Enterprise Architecture Model - Foundations 1 The different levels of an enterprise architecture can be visualized as a pyramid: On top the business unit of an enterprise, and at the bottom the delivery system within the enterprise. The enterprise can consist of one or more business units, working in specific business area. The five levels of architecture are defined as: Business Unit, Information, Information System, Data and Delivery System. https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

NIST Enterprise Architecture Model - Foundations 1 The separate levels of an enterprise architecture are interrelated in a special way. On every level the architectures assumes or dictates the architectures at the higher level. The illustration on the right gives an example of which elements can constitute an Enterprise Architecture. https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

NIST Enterprise Architecture Model - Levels of architecture 1 Each layer of architecture in the model has a specific intention:Rigdon et al. (1989, p. 139-140) https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

NIST Enterprise Architecture Model - Levels of architecture 1 * Business Architecture level: This level can picture the total or a subunit of any corporation, which are in contact with external organizations. https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

NIST Enterprise Architecture Model - Levels of architecture 1 * Information architecture level: This level specifies types of content, presentation forms, and format of the information required. https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

NIST Enterprise Architecture Model - Levels of architecture 1 * Information systems architecture level: Specifications for automated and procedure- oriented information systems. https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

NIST Enterprise Architecture Model - Levels of architecture 1 * Data Architecture level: Framework for maintenance, access and use of data, with data dictionary and other naming conventions. https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

NIST Enterprise Architecture Model - Levels of architecture 1 * Data Delivery Systems level: Technical implementation level of software, hardware, and communications that support the data architecture. https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

NIST Enterprise Architecture Model - Levels of architecture 1 A sample elements of how the Enterprise Architecture can be described in more detail is shown in the illustration. https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

NIST Enterprise Architecture Model - Information Technology Architecture 1 The Memoranda 97-16 (Information Technology Architectures) gave the following definition of enterprise architecture: https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

NIST Enterprise Architecture Model - Information Technology Architecture 1 :The Enterprise Architecture is the explicit description of the current and desired relationships among business and management process and information technology. It describes the target situation which the agency wishes to create and maintain by managing its IT portfolio. https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

NIST Enterprise Architecture Model - Information Technology Architecture 1 Although the substance of these components, sometimes called architectures or sub- architectures, must be addressed in every agency's complete Enterprise Architecture, agencies have great flexibility in describing, combining, and renaming the components, which consist of: https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

NIST Enterprise Architecture Model - Information Technology Architecture 1 * Business Processes: This component of the Enterprise Architecture describes the core business processes which support the organization's missions https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

NIST Enterprise Architecture Model - Information Technology Architecture 1 * Information Flows and Relationships: This component analyzes the information utilized by the organization in its business processes, identifying the information used and the movement of the information within the agency. The relationships among the various flows of information are described in this component. These information flows indicate where the information is needed and how the information is shared to support mission functions.The US Department of Agriculture has incorporated this component into its Business Architecture, while the US Department of Defense and Treasury have built it into their Operational Architectures. https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

NIST Enterprise Architecture Model - Information Technology Architecture 1 * Applications : The Applications component identifies, defines, and organizes the activities that capture, manipulate, and manage the business information to support mission operations. It also describes the logical dependencies and relationships among business activities.The US Department of Energy incorporates Business Applications into its Applications Subarchitecture, while the US Department of Treasury includes them in its Functional Architecture. https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

NIST Enterprise Architecture Model - Information Technology Architecture 1 * Data Descriptions: This component of the Enterprise Architecture identifies how data is maintained, accessed, and used https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

NIST Enterprise Architecture Model - Information Technology Architecture 1 * Technology Infrastructure : The Technology Infrastructure component describes and identifies the physical layer including, the functional characteristics, capabilities, and interconnections of the hardware, software, and communications, including networks, protocols, and nodes. It is the wiring diagram of the physical IT infrastructure.The US Department of Agriculture had incorporated this architecture into its Technical Standard and Telecommunications Architectures. US DoD uses its System Architecture, and US Treasury its Infrastrucsture to describe the physical layer. https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

NIST Enterprise Architecture Model - Information Technology Architecture 1 With the exception of the Business Processes component, the interrelationships among and priorities of these components are not prescribed by this guidance; there is no hierarchy of relationships implied. Furthermore, agencies should document not only their current environment for each of these components, but also the target environment that is desired. https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

NIST Enterprise Architecture Model - Applications 1 The NIST Framework was picked up by several U.S. federal agencies and used as the basis for their information strategy.[http://www.objectwatch.com/white papers/IASANewsletterApril2007.pdf Exclusive Interview with John Zachman] by Roger Sessions. In: Perspectives of the International Association of Software Architects. April 2006. The reference model is applicated the following frameworks: https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

NIST Enterprise Architecture Model - Applications 1 * United States Department of Energy|Department of Energy (DOE) Information Architecture Federal Aviation Administration (1998) [http://www.faa.gov/niac/pdf/wn18_fia.pdf Federal Information Architecture Initiatives]. February 1998 https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

NIST Enterprise Architecture Model - Applications 1 * FDIC Enterprise Architecture Framework is the Enterprise Architecture framework of the Federal Deposit Insurance Corporation (FDIC). https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

NIST Enterprise Architecture Model - Applications 1 * Federal Enterprise Architecture Framework (FEAF) : The 1999 documentation of the Federal Enterprise Architecture Framework Version 1.1 explains how the NIST Framework is used as a foundation of the Federal Enterprise Architecture|FEA Framework. https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

NIST Enterprise Architecture Model - Applications 1 * NWS Enterprise Architecture : Enterprise Architecture of the National Weather ServiceBobby Jones (2003) [http://ams.confex.com/ams/pdfpapers/7321 1.pdf NWS Enterprise Architecture]. In: 20th International Conference on Interactive Information and Processing Systems. 2004. https://store.theartofservice.com/the-enterprise-architecture-toolkit.html

For More Information, Visit: https://store.theartofservice.co m/the-enterprise-architecture- toolkit.html https://store.theartofservice.co m/the-enterprise-architecture- toolkit.html The Art of Service https://store.theartofservice.com

Enterprise Architecture https://store.theartofservice.com/the-enterprise-architecture-toolkit.html.

Similar presentations

Presentation on theme: "Enterprise Architecture https://store.theartofservice.com/the-enterprise-architecture-toolkit.html."— Presentation transcript:

Similar presentations

About project

Feedback

Log in

Auth with social network:

Enterprise Architecture https://store.theartofservice.com/the-enterprise-architecture-toolkit.html.

Similar presentations

Presentation on theme: "Enterprise Architecture https://store.theartofservice.com/the-enterprise-architecture-toolkit.html."— Presentation transcript:

Similar presentations

About project

Feedback