- Technical Architecture Modelling Tools
- Technical Architecture Definition
- Technical Architecture Document
This has too many enumerations and lists. May be in need of reorganization to comply with Wikipedia's.
Please help by to make improvements to the overall structure. (June 2016) Enterprise architecture ( EA) is 'a well-defined practice for conducting analysis, design, planning, and implementation, using a comprehensive approach at all times, for the successful development and execution of strategy. Enterprise architecture applies architecture principles and practices to guide organizations through the business, information, process, and necessary to execute their strategies. These practices utilize the various aspects of an enterprise to identify, motivate, and achieve these changes.' Practitioners of enterprise architecture, are responsible for performing the analysis of business structure and and are often called upon to draw conclusions from the information collected to address the goals of enterprise architecture:, and.
Contents. Overview In the enterprise architecture literature and community, there are various perspectives in regards to the meaning of the term enterprise architecture. As of 2012, no official definition exists; rather, various organizations (public and private) promote their understanding of the term. Consequently, the enterprise architecture literature offers many definitions for the term enterprise architecture; some of which are complementary, others are nuances, and others yet are in opposition. The (MIT CISR) in 2007 defined enterprise architecture as the specific aspects of a business that are under examination: Enterprise architecture is the organizing logic for business processes and 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. The defines enterprise architecture as a practice, which analyzes areas of common activity within or between organizations, where information and other resources are exchanged to guide future states from an integrated viewpoint of strategy, business, and technology.
IT analysis firm defines the term as a discipline where an enterprise is led through change. According to their glossary, '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. EA delivers value by presenting business and IT leaders with signature-ready recommendations for adjusting policies and projects to achieve target business outcomes that capitalize on relevant business disruptions. EA is used to steer toward the evolution of the future state architecture.' Each of the definitions above underplays the historical reality that enterprise architecture emerged from methods for documenting and planning architectures, and the current reality that most enterprise architecture practitioners report to a CIO or other IT department manager. 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 that the business depends on.
Topics The terms enterprise and architecture The term enterprise can be defined as describing an, organization, or collection of organizations that share a set of common goals and to provide specific products or services to customers. In that sense, the term enterprise covers various types of organizations, regardless of their size, ownership model, operational model, or geographical distribution.
It includes those organizations' complete socio-technical systems, including people, information, processes, and technologies. The term architecture refers to fundamental concepts or properties of a system in its environment, embodied in its elements, relationships, and in the principles of its design and evolution. Understood as a socio-technical system, the term enterprise defines the scope of the enterprise architecture. Scopes Perspectives, or beliefs, held by enterprise architecture practitioners and scholars, with regards to the meaning of the enterprise architecture, typically gravitate towards one or a hybrid of three schools of thought:. Enterprise IT design – the purpose of EA is the greater alignment between IT and business concerns. The main purpose of enterprise architecture is to guide the process of planning and designing 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.
Enterprise integrating – According to this school of thought, 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. Enterprise ecological adaptation – 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 and to coevolve with its environment. Typically, proposals and decisions encompass both the enterprise and its environment.
One’s belief with regards to the meaning of enterprise architecture will impact how one sees its purpose, its scope, the means of achieving it, the skills needed to conduct it, and the locus of responsibility for conducting it Architectural description of an enterprise According to the standard, the product used to describe the architecture of a system is called an architectural description. In practice, an architectural description contains a variety of lists, tables, and diagrams. These are models known as views. In the case of Enterprise Architecture, these models describe the logical business functions or capabilities, human roles and actors, the physical organization structure, and, and platform applications, hardware, and communications infrastructure. The UK National Computing Centre EA best practice guidance states: 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. 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 (IT) is justified.
Paramount to changing the enterprise architecture is the identification of a. His/her mission, and strategy, and the governance framework define all roles, responsibilities, and relationships involved in the anticipated transformation. Changes considered by enterprise architects typically include:. innovations in the structure or processes of an organization.
innovations in the use of information systems or technologies. the integration and/or of business processes, and.
improving the quality and timeliness of business information. A methodology for developing and using architecture to guide the from a baseline state to a target state, sometimes through several transition states, is usually known as an. A framework provides a structured collection of processes, techniques, artifact descriptions, reference models and guidance for the production and use of an enterprise-specific architecture description. See also: Benefits The benefits of enterprise architecture are achieved through its direct and indirect contributions to organizational goals. It has been found that the most notable benefits of enterprise architecture can be observed in the following areas:.
Organizational design - Enterprise architecture provides support in the areas related to design and re-design of the organizational structures during mergers, acquisitions or during general organizational change. Organizational processes and process standards - Enterprise architecture helps enforce discipline and standardization of business processes, and enable process consolidation, reuse, and integration.
Enterprise architecture supports investment decision-making and work prioritization. Project management - Enterprise architecture enhances the collaboration and communication between project stakeholders. Enterprise architecture contributes to efficient project scoping, and to defining more complete and consistent project deliverables. Enterprise architecture increases the speed of requirement elicitation and the accuracy of requirement definitions, through publishing of the enterprise architecture documentation.
System development - Enterprise architecture contributes to optimal system designs and efficient resource allocation during system development and testing. and decision making - Enterprise architecture is found to help enforce discipline and standardization of IT planning activities and to contribute to a reduction in time for technology-related decision making.
IT value - Enterprise architecture helps reduce the system's implementation and operational costs, and minimize replication of IT infrastructure services across business units. IT complexity - Enterprise architecture contributes to a reduction in IT complexity, consolidation of data and applications, and to better of the systems. IT openness - Enterprise architecture contributes to more and IT as reflected through increased accessibility of data for, and increased transparency of infrastructure changes. Enterprise architecture contributes to the reduction of business risks from system failures and security breaches. Enterprise architecture helps reduce risks of project delivery. Examples Documenting the architecture of enterprises is done within the in the context of the (CPIC) process.
The (FEA) reference model guides federal agencies in the development of their architectures. Companies such as, and use enterprise architecture to improve their business architectures as well as to improve and. 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:. Business Enterprise Architecture, or the 2008 BEAv5.0 version. Relationship to other disciplines According to the Federation of EA Professional Organizations (FEAPO), Enterprise Architecture interacts with a wide array of other disciplines commonly found in business settings.
According to FEAPO: An Enterprise Architecture practice collaborates with many interconnected disciplines, including performance engineering and management, process engineering and management, IT and enterprise portfolio management, governance and compliance, IT strategic planning, risk analysis, information management, metadata management, and a wide variety of technical disciplines as well as organizational disciplines such as organizational development, transformation, innovation, and learning. Increasingly, many practitioners have stressed the important relationship of Enterprise Architecture with emerging holistic design practices such as design thinking, systems thinking, and user experience design.
As Enterprise Architecture has emerged in various organizations, the broad reach has resulted in this business role being included in the processes of many organizations. While this may imply that enterprise architecture is closely tied to IT, it should be viewed in the broader context of in that it addresses, and process architecture, as well as more technical subjects. Discussions of the intersection of Enterprise Architecture and various IT practices have been published by various IT analysis firms. Gartner and Forrester have stressed the important relationship of Enterprise Architecture with emerging holistic design practices such as and. Analyst firm suggested that Enterprise Architecture and the emerging concept of the were 'two sides to the same coin.' The Cutter Consortium describes Enterprise Architecture as an information and knowledge-based discipline. The enterprise architecture of an organization is too complex and extensive to document in its entirety, so techniques provide a way to explore and analyze these hidden, tacit, or implicit areas.
In return, enterprise architecture provides a way of documenting the components of an organization and their interaction, in a systemic and holistic way that complements. In various venues, enterprise architecture has been discussed as having a relationship with, a particular style of application integration. Research points to enterprise architecture promoting the use of SOA as an enterprise-wide integration pattern. Tools The following table lists some notable enterprise architecture tools listed by and in their 2013 and 2014 reports.
Product Vendor Headquarters ABACUS Australia Netherlands (formerly ) Germany Australia iteratec Germany Germany Mega Suite France planningIT (formerly ) Germany SAP PowerDesigner Germany ProVision (formerly Metastorm) Canada QPR EnterpriseArchitect Finland Unicomm formerly ( (formerly )) United States Product Vendor Headquarters Criticism Despite the benefits that enterprise architecture claims to provide, for more than a decade, writers and organizations raised concerns about enterprise architecture as an effective practice. Here is a partial list of those objections:.
In 2007, computer scientist (a major contributor to UML and pioneer in OO software development) gave his assessment of enterprise architecture: 'Around the world introducing an Enterprise Architecture EA has been an initiative for most financial institutions (banks, insurance companies, government, etc.) for the last five years or so, and it is not over. I have been working with such companies and helped some of them to avoid making the worst mistakes. Most EA initiatives failed. My guess is that more than 90% never really resulted in anything useful.'
. In a 2007 report, on enterprise architecture, predicted that '. En 12368 download.
By 2012 40% of 2007’s enterprise architecture programs will be stopped.' . A 2008 study, by performed by Erasmus University Rotterdam and software company concluded that two-thirds of enterprise architecture projects failed to improve business and IT alignment. In a 2009 article, industry commentator Dion Hinchcliffe wrote that traditional enterprise architecture might be 'broken': 'At its very best, enterprise architecture provides the bright lines that articulate the full range of possibilities for a business, even describing how to go about getting there.
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.' .
In 2011, federal enterprise architecture consultant Stanley Gaver released a report that examined problems within the United States federal government’s enterprise architecture program. Gaver concluded that the federal enterprise architecture 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 enterprise architecture program was not 'as influential and successful as in the past.' A key concern about EA has been the difficulty in arriving at metrics of success, because of the broad-brush and often opaque nature of EA projects. See also., pioneer of enterprise architecture.
References.
Initiated in 1989, one of the earliest frameworks for. An enterprise architecture framework ( EA framework) defines how to create and use an. An 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. This allows for making systemic design decisions on all the components of the system and making long-term decisions around new design requirements, sustainability, and support. Contents. Overview Enterprise architecture regards the enterprise as a large and complex system. 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 at which builders work, to bring enterprise design tasks into focus and produce valuable architecture description documentation. The components of an architecture framework provide structured guidance that is divided into three main areas:. 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. Methods for designing architecture: processes that architects follow.
Usually, an overarching enterprise architecture process, composed of phases, broken 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. Organization of architects: guidance on the team structure and the governance of the team, including the skills, experience, and training needed. Overview of Enterprise Architecture Frameworks evolution (1987–2003). On the left: The 1987, 1989, 1992, 1997, 1999 and 2000. On the right: influenced by, JTA, JTAA, 1995, DoD TRM and 1996, and 2003.
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 benefits 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. By 1980, IBM’s (BSP) was promoted as a method for analyzing and designing an organization’s information architecture, with the following goals:. understand the issues and opportunities with the current applications and technical architecture;. develop a future state and migration path for the technology that supports the enterprise;. provide business executives with a direction and decision making framework for IT capital expenditures;. provide the information system (IS) with a blueprint for development.
In 1982, when working for IBM and with BSP, John Zachman was perhaps the first to mention Enterprise Architecture in the public domain. Then and in later papers, Zachman used the word enterprise as a synonym for business. '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.' However, in this article the term 'Enterprise Architecture' was mentioned only once without any specific definition and all subsequent works of Zachman used the term 'Information Systems Architecture'. In 1986, the was developed as a result of the research project sponsored by a group of companies, including IBM, which was seemingly the first published EA framework. In 1987, John Zachman, who was a marketing specialist at IBM, published the paper, A Framework for Information Systems Architecture. The paper provided a classification scheme for artifacts that describe (at several levels of abstraction) the what, how, where, who, when and why of information systems.
Given IBM already employed BSP, Zachman had no need to provide planning process. The paper did not mention enterprise architecture. In 1989, the National Institute of Standards and Technology (NIST) published the. 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.
The NIST Enterprise Architecture Model seemingly was the first publication that consistently used the term 'Enterprise Architecture'. In 1990, the term 'Enterprise Architecture' was formally defined for the first time as an architecture that 'defines and interrelates data, hardware, software, and communications resources, as well as the supporting organization required to maintain the overall physical structure required by the architecture'. In 1992, a paper by Zachman and Sowa started thus 'John Zachman introduced a framework for information systems architecture (ISA) that has been widely adopted by systems analysts and database designers.' The term enterprise architecture did not appear. The paper was about using the ISA framework to describe, “.the overall information system and how it relates to the enterprise and its surrounding environment.” The word enterprise was used as a synonym for business. In 1993, Stephen Spewak’s book (EAP) defined a process for defining architectures for the use of information in support of the business and the plan for implementing those architectures.
The business mission is the primary driver. Then the data required to satisfy the mission.
Then the applications built to store and provide that data. Finally the technology to implement the applications. Enterprise Architecture Planning is a data-centric approach to architecture planning. An aim is to improve data quality, access to data, adaptability to changing requirements, data interoperability and sharing, and cost containment. EAP has its roots in IBM’s (BSP). In 1994, the Open Group selected 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 from 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. In 1996, the US IT Management Reform Act, more commonly known as the, 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.” 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. 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 between baseline and target architectures.” 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.' At that point, the processes in TOGAF, FEAF, EAP and BSP were clearly related. In 2002/3, in its Enterprise Edition, TOGAF 8 shifted focus from the technology architecture layer to the higher business, data and application layers. It introduced structured analysis, after, which features, for example, mappings of organization units to business functions and data entities to business functions. Today, business functions are often called business capabilities. And many enterprise architects regard their business function/capability hierarchy/map as the fundamental Enterprise Architecture artifact.
They relate data entities, use cases, applications and technologies to the functions/capabilities. In 2006, the popular book Enterprise Architecture As Strategy reported the results of work by MIT’s Center for Information System Research. This book emphasises the need for enterprise architects to focus on core business processes ('Companies excel because they've decided which processes they must execute well, and have implemented the IT systems to digitise those processes.' ) and to engage business managers with the benefits that strategic cross-organisational process integration and/or standardisation could provide. A 2008 research project for the development of professional certificates in enterprise and solution architecture by the (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.
In 2011, the TOGAF 9.1. Specification says: 'Business planning at the strategy level provides the initial direction to enterprise architecture.' Normally, the business principles, business goals, and strategic drivers of the organization are defined elsewhere.
In other words, Enterprise Architecture is not a business strategy, planning or management methodology. Enterprise Architecture strives to align business information systems technology with given business strategy, goals and drivers. The TOGAF 9.1 specification clarified, that, 'A complete enterprise architecture description should contain all four architecture domains (business, data, application, technology), but the realities of resource and time constraints often mean there is not enough time, funding, or resources to build a top-down, all-inclusive architecture description encompassing all four architecture domains, even if the enterprise scope is.
less than the full extent of the overall enterprise.' In 2013, is the most popular Architecture framework (judged by published certification numbers) that some assume it defines EA.
However, some still use the term Enterprise Architecture as a synonym for Business Architecture, rather than covering all four architecture domains - business, data, applications and technology. EA framework topics. Artist impression. Architecture and building governance People who remodel a home are aware that the architect produces detailed drawings that specify plumbing, electrical, and building construction information for the entire structure. The architect responsible for the design produces (or oversees others who produce) blueprints for each phase of the project—from structural changes to size and layout of rooms. Moreover, to successfully complete the project, the architect operates within a framework of building codes. City or county inspections ensure the work complies with building codes.
Enterprise architecture works in a similar manner. An architecture description document can be thought of as the blueprint for the procurement and realization of a system. But an enterprise architecture includes more than just an abstract description of the system's structure and behavior. It includes also principles, policies and standards (akin to building codes) that ensure that systems are soundly constructed.
Governance of the enterprise architecture and of its implementation requires organization and processes (akin to city and county inspectors and the processes for checking building improvement projects). Architecture domain. Layers of the enterprise architecture. Since Stephen Spewak's (EAP) in 1993, and perhaps before then, it has been normal to divide enterprises architecture into four.
Note that the applications architecture is about the choice of and relationships between applications in the enterprise's application portfolio, not about the internal architecture of a single application (which is often called application architecture). Many EA frameworks combine data and application domains into a single (digitized) information system layer, sitting below the business (usually a human activity system) and above the technology (the platform ). Layers of the enterprise architecture. Example of the, which has defined five architectural layers. For many years, it has been common to regard the architecture domains as layers, with the idea that each layer contains components that execute processes and offer services to the layer above. This way of looking at the architecture domains was evident in TOGAF v1 (1996), which encapsulated the technology component layer behind the platform services defined in the 'Technical Reference Model' - very much according to the philosophy of TAFIM and POSIX.
The view of architecture domains as layers can be presented thus:. Environment (the external entities and activities monitored, supported or directed by the business).
Business Layer (business functions offering services to each other and to external entities). Data Layer (Business information and other valuable stored data). Information System Layer (business applications offering information services to each other and to business functions). Technology Layer (generic hardware, network and platform applications offering platform services to each other and to business applications). Each layer delegates work to the layer below.
In each layer, the components, the processes and the services can be defined at a coarse-grained level and decomposed into finer-grained components, processes and services. The graphic shows a variation on this theme. Components of enterprise architecture framework In addition to three major framework components discussed above. Description advice: some kind of Architecture Artifacts Map or Viewpoint Library.
Process advice: some kind of Architecture Development Method, with supporting guidance. Organization advice: including an EA Governance Model An ideal EA framework should feature:. Business value measurement metrics.
EA initiative model. EA maturity model. Enterprise communication model Most modern EA frameworks (e.g. TOGAF, ASSIMPLER, EAF) include most of the above.
Zachman has always focused on architecture description advice. Enterprise architecture domains and subdomains. Enterprise architecture reference architecture with sub domains The application and technology domains (not to be confused with business domains) are characterized by domain capabilities and domain services. The capabilities are supported by the services. The application services are also referred to in (SOA). The technical services are typically supported by software products. The data view starts with the data classes which can be decomposed into data subjects which can be further decomposed into data entities.
The basic data model type which is most commonly used is called merda (master entity relationship diagrams assessment, see ). The Class, subject and entity forms a hierarchical view of data. Enterprises may have millions of instances of data entities. The Enterprise Architecture Reference Traditional Model offers a clear distinction between the architecture domains (business, information/data, application/integration and technical/infrastructure). These domains can be further divided into Sub domain disciplines. An example of the EA domain and subdomains is in the image on the right. Many enterprise architecture teams consist of Individuals with Skills aligned with the Enterprise Architecture Domains and sub-domain disciplines.
Here are some examples: enterprise business architect, enterprise documentational architect, enterprise application architect, enterprise infrastructure architect, enterprise information architect, etc. An example of the list of reference architecture patterns in the application and information architecture domains are available. View model. Illustration of the. A is a framework that defines the set of views or approaches used in, or the construction of an.
Since the early 1990s, there have been a number of efforts to define standard approaches for describing and analyzing system architectures. Many of the recent Enterprise Architecture frameworks have some kind of set of views defined, but these sets are not always called view models. Standardization Perhaps the best-known standard in the field of and started life as, an for describing the architecture of a software-intensive system approved in 2000. In its latest version, the standard is published as. The standard defines an architecture framework as conventions, principles and practices for the description of architectures established within a specific domain of application and/or community of stakeholders, and proposes an architecture framework is specified by:.
the relevant stakeholders in the domain,. the types of concerns arising in that domain,. architecture viewpoints framing those concerns and. correspondence rules integrating those viewpoints cited before. Architecture frameworks conforming to the standard can include additional methods, tools, definitions, and practices beyond those specified.
Types of enterprise architecture framework. Just a few of the Enterprise Architecture frameworks utilized today, 2011 Nowadays there are now countless EA frameworks, many more than in the following listing. Consortia-developed frameworks. ARCON – A Reference Architecture for Collaborative Networks – not focused on a single enterprise but rather on networks of enterprises.
(GERAM). – the Reference Model of Open Distributed Processing (ITU-T Rec. X.901-X.904 ISO/IEC 10746) defines an enterprise architecture framework for structuring the specifications of. – a four-nation effort to develop a common ontology for architecture interoperability. Framework for enterprise modelling. – The Architecture Framework – a widely used framework including an architectural Development Method and standards for describing various types of architecture.
The Chief Information Officers Council (1999). 2012-02-13 at the. September 1999.
Technical Architecture Modelling Tools
The Open Group (2008) TOGAF Version 9. Van Haren Publishing, 1 nov.
73. ^ Stephen Marley (2003). At Webarchive.org, retrieved 3-04-2015. (2004) How to Survive in the Jungle of Enterprise Architecture Frameworks. P.89 gives a similar scheme. US Department of Defense (2001).
9 April 2001. 11, mentioned that also the DoD TRM is influenced by POSIX.
![Definition Definition](https://image.slidesharecdn.com/togaf9-120515103930-phpapp01/95/enterprise-architecture-for-dummies-togaf-9-enterprise-architecture-overview-47-728.jpg?cb=1337078510)
^ Graham Berrisford (2008-13) ' on grahamberrisford.com, last update. Accessed. (1982) Business Systems Planning and Business Information Control Study: A comparison in IBM Systems Journal 21(1). A Framework for Information Systems Architecture.
In: IBM Systems Journal, vol 26, no 3. IBM Publication G321-5298. ^ Zachman and Sowa (1992) Extending and formalising the framework of information systems architecture IBM Systems Journal, Vol 31, No 3.
^ Svyatoslav Kotusev (2016). The History of Enterprise Architecture: An Evidence-Based Review. In: Journal of Enterprise Architecture, vol. Rigdon (1989). Architectures and Standards. In Information Management Directions: The Integration Challenge (NIST Special Publication 500-167), E.N.
Goldfine (Eds.), Gaithersburg, MD: National Institute of Standards and Technology (NIST), pp.135-150. Richardson, G.L.; Jackson, B.M.; Dickson, G.W. 'A Principles-Based Enterprise Architecture: Lessons from Texaco and Star Enterprise'.
Technical Architecture Definition
MIS Quarterly. 14 (4): 385–403., and ( (2006) Enterprise Architecture As Strategy: Creating a Foundation for Business Execution. Harvard Business Review Press. The Open Group (2011). Accessed July 16, 2013.
The Open Group (2011). Accessed July 16, 2013. TOGAF 9.1 White Paper An Introduction to TOGAF Version 9.1. ^ Rob Thomas and Phil Cullen (2001).
In: US Customs Today April 2001. Niles E Hewlett (2006),. PMP CEA, Enterprise Architecture Team, USDA-OCIO. January 25, 2006. Whitehouse.gov May 2005.
In: Common Defense Quarterly. January 2011, p. Camarinha-Matos, H. Afsarmanesh, Collaborative Networks: Reference Modeling, Springer, 2008. Camarinha-Matos, L.M.; Afsarmanesh, H. 'On reference models for collaborative networked organizations'. International Journal Production Research.
46 (9): 2453–2469. 2011-04-24 at the. Complex Systems Design & Management: 335–346.:. Retrieved 2013-06-16. Gianni, D., Lindman, N., Fuchs, J., & Suzic, R.
Introducing the european space agency architectural framework for space-based systems of systems engineering. In Complex Systems Design & Management (pp.
Springer Berlin Heidelberg. US Department of the Treasury Chief Information Officer Council (2000). 2009-03-18 at the. Version 1, July 2000. Pragmatic EA. Tony Shan and Winnie Hua (2006).
Technical Architecture Document
Proceedings of the 10th IEEE International EDOC Enterprise Computing Conference (EDOC 2006), October 2006, p23-32., Svyatoslav Kotusev, British Computer Society (BCS), July 2016. Sabine Buckl, Alexander Ernst, Josef Lankes and Christian Schweda (2009). State of the Art in Enterprise Architecture Management. Software Engineering for Business Information Systems (SEBIS), Munich, Germany, pp., Linda Tucci, visited 3 August 2016., Jason Bloomberg, visited 3 August 2016 External links. (July 2016).