369:
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."
541:
685:
301:(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
176:
25:
391:
108:
585:
2754:
453:
286:. 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".
350:, 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.
2744:
260:
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".
339:, 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.
324:, 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.”
376:
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
158:
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
368:
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
138:
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
568:
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
293:
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
162:
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
357:
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 which processes they must execute well, and have implemented the IT systems to digitise those
564:
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
331:
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
289:
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
259:
In 1982, when working for IBM and with BSP, John Zachman outlined his framework for enterprise-level "Information Systems Architecture". Then and in later papers, Zachman used the word enterprise as a synonym for business. "Although many popular information systems planning methodologies, design
464:
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
312:
from the US DoD as a basis for development of 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
151:. 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.
234:
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,
615:
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
556:
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
435:
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).
278:
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.
492:
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.
548:
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
1348:. In Information Management Directions: The Integration Challenge (NIST Special Publication 500-167), E.N. Fong, A.H. Goldfine (Eds.), Gaithersburg, MD: National Institute of Standards and Technology (NIST), pp.135-150.
365:(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.
439:
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
849:
313:
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.
327:
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.
231:(TOGAF) and other EA frameworks can be traced back to the article of Marshall K. Evans and Lou R. Hague titled "Master Plan for Information Systems" published in 1962 in Harvard Business Review.
932:(SABSA) is an open framework and methodology for Enterprise Security Architecture and Service Management, that is risk based and focuses on integrating security into business and IT management.
235:
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.
1617:
Gianni, Daniele; Lindman, Niklas; Fuchs, Joachim; Suzic, Robert (2012). "Introducing the European Space Agency Architectural Framework for Space-Based Systems of Systems Engineering".
895:(LAF) is a collection of good practices thanks to which the IT environment will respond consistently and quickly to a changing business situation while maintaining its consistent form.
808:
for use within the US Government (not to be confused with the 2002 Federal Enterprise Architecture (FEA) guidance on categorizing and grouping IT investments, issued by the US Federal
1502:
720:– 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
264:
1564:
898:
MEGAF (Mega-modeling Architecture Framework) is an infrastructure for realizing architecture frameworks that conform to the definition of architecture framework provided in
892:
711:
294:
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.
428:
139:
for making systemic design decisions on all the components of the system and making long-term decisions around new design requirements, sustainability, and support.
657:
conventions, principles and practices for the description of architectures established within a specific domain of application and/or community of stakeholders
465:
technology component layer behind the platform services defined in the "Technical Reference Model" - very much according to the philosophy of TAFIM and POSIX.
1171:
358:
processes.") and to engage business managers with the benefits that strategic cross-organisational process integration and/or standardisation could provide.
346:, TOGAF 8 shifted focus from the technology architecture layer to the higher business, data and application layers. It introduced structured analysis, after
749:
Architecture Framework – a widely used framework including an architectural Development Method and standards for describing various types of architecture.
267:
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.
1788:
856:
54:
1481:
1462:
825:
1013:
Pragmatic Enterprise Architecture Framework (PEAF) - part of Pragmatic Family of Frameworks developed by Kevin Lee Smith, Pragmatic EA, from 2008
929:
532:
Most modern EA frameworks (e.g. TOGAF, ASSIMPLER, EAF) include most of the above. Zachman has always focused on architecture description advice.
166:
Organization of architects: guidance on the team structure and the governance of the team, including the skills, experience, and training needed.
1619:
Complex Systems Design & Management. Proceedings of the Second International Conference on Complex Systems Design & Management CSDM 2011
2230:
1782:
70:
1358:
Richardson, G.L.; Jackson, B.M.; Dickson, G.W. (1990). "A Principles-Based Enterprise Architecture: Lessons from Texaco and Star Enterprise".
1816:
676:
Architecture frameworks conforming to the standard can include additional methods, tools, definitions, and practices beyond those specified.
484:
Technology Layer (generic hardware, network and platform applications offering platform services to each other and to business applications).
1066:
1253:
2783:
1037:
945:
Avancier Methods (AM) Processes and documentation advice for enterprise and solution architects, supported by training and certification.
984:
835:
200:
701:
ARCON – A Reference Architecture for Collaborative Networks – not focused on a single enterprise but rather on networks of enterprises
1601:
801:
948:
BRM (Build-Run-Manage) Framework - an architecture framework created by Sanjeev "Sunny" Mishra during his early days at IBM in 2000.
1859:
1016:
573:
572:
An example of the list of reference architecture patterns in the application and information architecture domains are available at
561:). The Class, subject and entity forms a hierarchical view of data. Enterprises may have millions of instances of data entities.
242:(BSP) was promoted as a method for analyzing and designing an organization's information architecture, with the following goals:
796:
1201:
2747:
2613:
2542:
1644:
1032:
228:
2436:
2339:
908:, an open enterprise methodology, contains an enterprise architecture framework called the Enterprise System Topology (EST)
361:
A 2008 research project for the development of professional certificates in enterprise and solution architecture by the
2223:
1663:
1124:
830:
815:
347:
283:
184:
111:
481:
Information System Layer (business applications offering information services to each other and to business functions)
2416:
2283:
2268:
1809:
1082:
952:
275:
94:
1770:. Proceedings of the 10th IEEE International EDOC Enterprise Computing Conference (EDOC 2006), October 2006, p23-32.
59:
2778:
1087:
399:
298:
188:
46:
1046:
Solution Architecting Mechanism (SAM) – A coherent architecture framework consisting of a set of integral modules.
332:
transition of systems, applications, and associated business practices predicated upon a detailed gap analysis .”
809:
457:
196:
1529:
Camarinha-Matos, L.M.; Afsarmanesh, H. (2008). "On reference models for collaborative networked organizations".
154:
The components of an architecture framework provide structured guidance that is divided into three main areas:
2572:
2499:
2489:
2334:
2263:
1976:
1869:
1844:
965:- An open Visual Enterprise Architecture Method recently recognized by The Open Group as Architecture Framework
793:
European Space Agency Architectural Framework (ESAAF) - a framework for European space-based Systems of Systems
759:
2757:
2623:
2552:
2494:
2216:
1935:
1849:
843:
550:
2562:
2421:
2288:
2197:
1802:
853:
402:(EAP) in 1993 – and perhaps before then – it has been normal to divide enterprises architecture into four
2484:
2479:
2293:
2012:
1925:
1478:
780:
1459:
540:
2679:
2527:
2522:
2474:
2451:
2431:
1874:
919:
252:
provide business executives with a direction and decision making framework for IT capital expenditures;
824:
Nederlandse Overheid Referentie Architectuur (NORA) – a reference framework from the Dutch Government
2684:
2674:
2022:
2007:
1433:
1418:
1229:
The Practice of Enterprise Architecture: A Modern Approach to Business and IT Alignment (2nd Edition)
1141:
942:
ASSIMPLER Framework – an architecture framework, based on the work of Mandar Vanarse at Wipro in 2002
558:
422:
302:
239:
1627:
472:
Environment (the external entities and activities monitored, supported or directed by the business).
2587:
2386:
2369:
2278:
2037:
1915:
1910:
1854:
684:
362:
175:
2537:
2381:
1884:
1879:
1572:
1519:
L.M. Camarinha-Matos, H. Afsarmanesh, Collaborative Networks: Reference Modeling, Springer, 2008.
1077:
721:
705:
609:
246:
understand the issues and opportunities with the current applications and technical architecture;
131:
115:
50:
1250:
163:
outputs. It may be supported by approaches, techniques, tools, principles, rules, and practices.
2592:
2349:
2344:
2159:
1864:
1622:
1102:
1092:
880:
805:
135:
2411:
2364:
2093:
2063:
1839:
997:
819:
629:
475:
Business Layer (business functions offering services to each other and to external entities).
410:
2709:
2547:
2406:
2396:
2308:
2253:
2239:
2184:
2154:
1434:
TOGAF® 9.1 > Part II: Architecture Development Method (ADM) > Introduction to the ADM
1205:. Version 2.0. 9 April 2001. p. 11, mentioned that also the DoD TRM is influenced by POSIX.
1026:
1020:
1765:
1751:
1598:
249:
develop a future state and migration path for the technology that supports the enterprise;
8:
2729:
2714:
2582:
2446:
2354:
2298:
2164:
2149:
2118:
1825:
724:
692:
Nowadays there are now countless EA frameworks, many more than in the following listing.
633:
403:
35:
390:
2719:
2359:
2174:
2169:
1920:
1889:
1546:
1497:
1400:
1375:
978:
508:
Process advice: some kind of Architecture Development Method, with supporting guidance.
179:
Overview of Enterprise Architecture Frameworks evolution (1987–2003). On the left: The
39:
2633:
2391:
2128:
2068:
1640:
1419:
TOGAF® 9.1 > Part II: Architecture Development Method (ADM) > Preliminary Phase
1049:
1041:
993:– an Enterprise Architecture framework, as an elaboration of the work of John Zachman
733:– a four-nation effort to develop a common ontology for architecture interoperability
441:
416:
321:
180:
148:
107:
74:
1550:
867:
227:
The earliest rudiments of the step-wise planning methodology currently advocated by
2704:
2648:
2426:
2318:
2313:
2133:
2103:
2032:
2027:
1966:
1951:
1632:
1538:
1367:
1183:
601:
270:
In 1987, John Zachman, who was a marketing specialist at IBM, published the paper,
63:
2724:
2577:
2557:
2441:
2303:
2179:
2078:
2073:
2017:
1992:
1956:
1667:
1636:
1605:
1485:
1466:
1405:
Enterprise Architecture As Strategy: Creating a Foundation for Business Execution
1292:
1257:
1128:
860:
584:
282:
In 1989, the National Institute of Standards and Technology (NIST) published the
505:
Description advice: some kind of Architecture Artifacts Map or Viewpoint Library
147:
Enterprise architecture regards the enterprise as a large and complex system or
2628:
2532:
2273:
2108:
2098:
2053:
1997:
1894:
1392:
1001:
605:
1542:
1278:
Business Systems Planning and Business Information Control Study: A comparison
2772:
2608:
2376:
2088:
2083:
2058:
1930:
1121:
1097:
968:
899:
652:
641:
1660:
553:(SOA). The technical services are typically supported by software products.
2643:
2638:
2567:
2123:
1313:
Extending and formalising the framework of information systems architecture
1273:
1053:
1396:
730:
688:
Just a few of the Enterprise Architecture frameworks utilized today, 2011
1659:
US Department of the Treasury Chief Information Officer Council (2000).
1577:
2653:
2618:
2208:
2113:
746:
597:
452:
1794:
1379:
1469:. PMP CEA, Enterprise Architecture Team, USDA-OCIO. January 25, 2006.
956:
887:
736:
637:
255:
provide the information system (IS) with a blueprint for development.
1335:. In: Journal of Enterprise Architecture, vol. 12, no. 1, pp. 29-37.
818:(GEA) – a common framework legislated for use by departments of the
2401:
1371:
1299:. In: IBM Systems Journal, vol 26, no 3. IBM Publication G321-5298.
839:
600:
is a framework that defines the set of views or approaches used in
1701:
1447:
1188:
How to Survive in the Jungle of Enterprise Architecture Frameworks
1010:
Labnaf - Unified Framework for Driving Enterprise Transformations
501:
In addition to three major framework components discussed above.
496:
468:
The view of architecture domains as layers can be presented thus:
1971:
987:- from Institute For Enterprise Architecture Developments in 2003
962:
905:
535:
216:
1333:
The History of Enterprise Architecture: An Evidence-Based Review
478:
Data Layer (Business information and other valuable stored data)
2258:
1961:
1789:
A Comparison of the Top Four Enterprise Architecture Frameworks
972:
717:
672:
correspondence rules integrating those viewpoints cited before.
544:
Enterprise architecture reference architecture with sub domains
1740:
1134:
2458:
1690:
1071:
915:
774:
768:
742:
712:
Generalised Enterprise Reference Architecture and Methodology
679:
373:
309:
220:
212:
208:
204:
192:
1679:
1074:(The Guide to the Enterprise Architecture Body of Knowledge)
2669:
2002:
1446:
TOGAF 9.1 White Paper An Introduction to TOGAF Version 9.1
981:
Enterprise architecture concept based on Web 2.0 technology
923:
911:
589:
1783:
Enterprise Architecture Frameworks: The Fad of the Century
1528:
659:, and proposes an architecture framework is specified by:
1727:
159:
table, a diagram, or a higher level of composite of such.
57:
and tools are available to assist in formatting, such as
1712:
1357:
879:
Enterprise architecture frameworks that are released as
447:
1616:
991:
16:
Frame in which the architecture of a company is defined
1218:, Harvard Business Review, Vol. 40, No. 1, pp. 92-103.
708:(Trusted Cloud Initiative) TCI reference architecture.
114:
initiated in 1989, one of the earliest frameworks for
1122:
Federal Enterprise Architecture Framework Version 1.1
771:– the US Department of Defense Architecture Framework
511:
Organization advice: including an EA Governance Model
1251:
A brief history of EA: what is in it and what is not
1174:. NASA /SCI. At Webarchive.org, retrieved 3-04-2015.
655:. The standard defines an architecture framework as
651:
In its latest version, the standard is published as
337:
A practical guide to Federal Enterprise Architecture
1503:
Engineering Enterprise Architecture: Call to Action
777:– the UK Ministry of Defence Architecture Framework
1052:– an architecture framework, based on the work of
870:is a reference framework from Government of India.
866:India Enterprise Architecture (IndEA) framework -
669:architecture viewpoints framing those concerns and
569:architect, enterprise information architect, etc.
1221:
1067:Architecture patterns (EA reference architecture)
863:a framework for all the Colombian Public Agencies
695:
274:. The paper provided a classification scheme for
2770:
1297:A Framework for Information Systems Architecture
914:– a general systems-oriented framework based on
628:Perhaps the best-known standard in the field of
272:A Framework for Information Systems Architecture
1202:Department of Defense Technical Reference Model
1120:The Chief Information Officers Council (1999).
930:Sherwood Applied Business Security Architecture
854:Marco de Referencia de Arquitectura Empresarial
765:DNDAF – the DND/CF Architecture Framework (CAN)
497:Components of enterprise architecture framework
753:
536:Enterprise architecture domains and subdomains
460:, which has defined five architectural layers.
2224:
1810:
1264:, last update 16/07/2013. Accessed 16/07?2003
1007:Infomet - conceived by Pieter Viljoen in 1990
804:(FEAF) – a framework produced in 1999 by the
666:the types of concerns arising in that domain,
1732:
335:In 2001, the US Chief CIO council published
38:, which are uninformative and vulnerable to
850:Colombian Enterprise Architecture Framework
646:architecture of a software-intensive system
53:and maintains a consistent citation style.
2231:
2217:
1817:
1803:
1661:Treasury Enterprise Architecture Framework
1327:
1325:
1323:
1321:
1307:
1305:
1288:
1286:
1038:Service-oriented modeling framework (SOMF)
985:Extended Enterprise Architecture Framework
836:Treasury Enterprise Architecture Framework
680:Types of enterprise architecture framework
1758:
1626:
1531:International Journal Production Research
1479:FEA Consolidated Reference Model Document
1245:
1243:
1241:
1239:
1237:
1158:. Van Haren Publishing, 1 nov. 2008.p. 73
936:
874:
802:Federal Enterprise Architecture Framework
565:subdomains is in the image on the right.
95:Learn how and when to remove this message
2422:Software development process/methodology
2238:
1860:Earth systems engineering and management
1460:The USDA Enterprise Architecture Program
1017:Purdue Enterprise Reference Architecture
787:
683:
663:the relevant stakeholders in the domain,
583:
574:Architectural pattern (computer science)
539:
451:
389:
174:
106:
1824:
1522:
1513:
1318:
1302:
1283:
1267:
762:– the France DGA Architecture Framework
2771:
1719:
1653:
1557:
1234:
1231:. Melbourne, Australia: SK Publishing.
1166:
1164:
797:FDIC Enterprise Architecture Framework
515:An ideal EA framework should feature:
394:Layers of the enterprise architecture.
385:
380:
2212:
1798:
1753:Solution Architecting Mechanism (SAM)
1610:
1452:
1214:Evans, M. K. and Hague, L. R. (1962)
1114:
1033:SAP Enterprise Architecture Framework
1023:at the Purdue University early 1990s.
448:Layers of the enterprise architecture
229:The Open Group Architecture Framework
2743:
2437:Software verification and validation
2340:Component-based software engineering
1565:"The CSA TCI reference architecture"
1472:
1029:(RCDA), developed by CGI since 2015.
18:
1216:Master Plan for Information Systems
1161:
355:Enterprise Architecture As Strategy
130:) defines how to create and use an
45:Please consider converting them to
13:
2784:Enterprise architecture frameworks
1280:in IBM Systems Journal 21(1). p32.
1027:Risk- and Cost-Driven Architecture
831:NIST Enterprise Architecture Model
816:Government Enterprise Architecture
739:Framework for enterprise modelling
623:
519:Business value measurement metrics
348:information technology engineering
284:NIST Enterprise Architecture Model
112:NIST Enterprise Architecture Model
14:
2795:
2417:Software configuration management
2284:Search-based software engineering
2269:Experimental software engineering
1895:Sociocultural Systems Engineering
1776:
1764:Tony Shan and Winnie Hua (2006).
1315:IBM Systems Journal, Vol 31, No 3
1083:Enterprise architecture artifacts
953:Integrated Architecture Framework
783:– the NATO Architecture Framework
308:In 1994, the Open Group selected
124:enterprise architecture framework
2753:
2752:
2742:
1199:US Department of Defense (2001)
1088:Enterprise architecture planning
400:Enterprise Architecture Planning
299:Enterprise Architecture Planning
23:
1767:Solution Architecting Mechanism
1745:
1706:
1695:
1684:
1673:
1592:
1491:
1448:http://www.opengroup.org/togaf/
1440:
1425:
1410:
1407:. Harvard Business Review Press
1386:
1351:
1338:
810:Office of Management and Budget
458:federal enterprise architecture
297:In 1993, Stephen Spewak's book
2264:Empirical software engineering
1977:Systems development life cycle
1870:Enterprise systems engineering
1845:Biological systems engineering
1621:. Springer. pp. 335–346.
1208:
1193:
1190:. p.89 gives a similar scheme.
1177:
1148:
696:Consortia-developed frameworks
590:4+1 view model of architecture
528:Enterprise communication model
49:to ensure the article remains
1:
1936:System of systems engineering
1850:Cognitive systems engineering
1249:Graham Berrisford (2008-13) "
1108:
844:US Department of the Treasury
579:
551:service-oriented architecture
320:, more commonly known as the
2289:Site reliability engineering
1637:10.1007/978-3-642-25203-7_24
653:ISO/IEC/IEEE 42010:2011
608:, or the construction of an
265:PRISM architecture framework
185:NIST Enterprise Architecture
7:
2294:Social software engineering
2013:Quality function deployment
1926:Verification and validation
1346:Architectures and Standards
1331:Svyatoslav Kotusev (2016).
1227:Kotusev, Svyatoslav (2021)
1060:
893:Lean Architecture Framework
754:Defense industry frameworks
142:
10:
2800:
2432:Software quality assurance
1875:Health systems engineering
1488:. whitehouse.gov May 2005.
838:(TEAF) – a framework for
353:In 2006, the popular book
170:
2738:
2697:
2662:
2601:
2515:
2508:
2467:
2327:
2246:
2193:
2142:
2046:
2023:Systems Modeling Language
1985:
1944:
1903:
1832:
1680:https://lafinstitute.org/
1543:10.1080/00207540701737666
559:entity-relationship model
423:Applications architecture
303:Business Systems Planning
240:Business Systems Planning
2588:Model-driven engineering
2387:Functional specification
2370:Software incompatibility
2279:Requirements engineering
2038:Work breakdown structure
1916:Functional specification
1911:Requirements engineering
1855:Configuration management
1508:Common Defense Quarterly
1458:Niles E Hewlett (2006),
1437:. Accessed July 16, 2013
1422:. Accessed July 16, 2013
1311:Zachman and Sowa (1992)
363:British Computer Society
318:IT Management Reform Act
2779:Enterprise architecture
2382:Enterprise architecture
1885:Reliability engineering
1880:Performance engineering
1670:. Version 1, July 2000.
1573:Cloud Security Alliance
1172:Architectural Framework
1170:Stephen Marley (2003).
1078:Enterprise architecture
1040:, based on the work of
971:framework developed by
918:1.2 and released under
706:Cloud Security Alliance
610:enterprise architecture
429:Technology architecture
398:Since Stephen Spewak's
132:enterprise architecture
116:enterprise architecture
2593:Round-trip engineering
2350:Backward compatibility
2345:Software compatibility
2160:Industrial engineering
1865:Electrical engineering
1431:The Open Group (2011)
1416:The Open Group (2011)
1154:The Open Group (2008)
1103:Reference architecture
1093:Enterprise engineering
937:Proprietary frameworks
875:Open-source frameworks
806:US Federal CIO Council
689:
593:
545:
461:
395:
224:
136:architecture framework
119:
2412:Software architecture
2365:Forward compatibility
2094:Arthur David Hall III
2064:Benjamin S. Blanchard
1840:Aerospace engineering
1714:Avancier Methods (AM)
1000:(IFW) – conceived by
998:Information FrameWork
820:Queensland Government
788:Government frameworks
687:
630:software architecture
587:
543:
455:
411:Business architecture
393:
178:
110:
2710:Computer engineering
2407:Software archaeology
2397:Programming paradigm
2309:Software maintenance
2254:Computer programming
2240:Software engineering
2185:Software engineering
2155:Computer engineering
1510:. January 2011, p. 9
1344:W.B. Rigdon (1989).
1262:grahamberrisford.com
1021:Theodore J. Williams
588:Illustration of the
404:architecture domains
203:2000. On the right:
2730:Systems engineering
2715:Information science
2495:Service orientation
2447:Structured analysis
2355:Compatibility layer
2299:Software deployment
2165:Operations research
2150:Control engineering
2119:Joseph Francis Shea
1826:Systems engineering
1056:at IBM in the 1980s
842:, published by the
725:distributed systems
644:for describing the
634:system architecture
522:EA initiative model
386:Architecture domain
381:EA framework topics
2720:Project management
2485:Object orientation
2452:Essential analysis
2360:Compatibility mode
2175:Quality management
2170:Project management
1998:Function modelling
1921:System integration
1890:Safety engineering
1666:2009-03-18 at the
1604:2011-04-24 at the
1580:on 6 November 2016
1498:Dennis E. Wisnosky
1484:2010-07-05 at the
1465:2007-05-08 at the
1401:David C. Robertson
1256:2013-09-18 at the
1127:2012-02-13 at the
1098:ISO/IEC/IEEE 42010
979:Dynamic Enterprise
900:ISO/IEC/IEEE 42010
859:2021-05-10 at the
690:
648:approved in 2000.
594:
546:
462:
396:
344:Enterprise Edition
342:In 2002/3, in its
225:
215:1995, DoD TRM and
120:
2766:
2765:
2693:
2692:
2634:Information model
2538:Incremental model
2392:Modeling language
2206:
2205:
2129:Manuela M. Veloso
2069:Wernher von Braun
1646:978-3-642-25202-0
1131:. September 1999.
1050:Zachman Framework
525:EA maturity model
442:IT infrastructure
417:Data architecture
322:Clinger-Cohen Act
181:Zachman Framework
149:system of systems
105:
104:
97:
55:Several templates
2791:
2756:
2755:
2746:
2745:
2705:Computer science
2513:
2512:
2427:Software quality
2319:Systems analysis
2314:Software testing
2233:
2226:
2219:
2210:
2209:
2134:John N. Warfield
2104:Robert E. Machol
2033:Systems modeling
2028:Systems analysis
1967:System lifecycle
1952:Business process
1819:
1812:
1805:
1796:
1795:
1771:
1762:
1756:
1749:
1743:
1736:
1730:
1723:
1717:
1710:
1704:
1699:
1693:
1688:
1682:
1677:
1671:
1657:
1651:
1650:
1630:
1614:
1608:
1596:
1590:
1589:
1587:
1585:
1576:. Archived from
1569:
1561:
1555:
1554:
1537:(9): 2453–2469.
1526:
1520:
1517:
1511:
1495:
1489:
1476:
1470:
1456:
1450:
1444:
1438:
1429:
1423:
1414:
1408:
1390:
1384:
1383:
1355:
1349:
1342:
1336:
1329:
1316:
1309:
1300:
1290:
1281:
1271:
1265:
1247:
1232:
1225:
1219:
1212:
1206:
1197:
1191:
1184:Jaap Schekkerman
1181:
1175:
1168:
1159:
1152:
1146:
1145:
1138:
1132:
1118:
990:EACOE Framework
636:started life as
602:systems analysis
316:In 1996, the US
100:
93:
89:
86:
80:
78:
67:
27:
26:
19:
2799:
2798:
2794:
2793:
2792:
2790:
2789:
2788:
2769:
2768:
2767:
2762:
2734:
2725:Risk management
2689:
2658:
2597:
2578:Waterfall model
2548:Prototype model
2543:Iterative model
2504:
2480:Aspect-oriented
2463:
2442:Software system
2323:
2304:Software design
2242:
2237:
2207:
2202:
2189:
2180:Risk management
2138:
2079:Harold Chestnut
2074:Kathleen Carley
2042:
2018:System dynamics
1993:Decision-making
1981:
1957:Fault tolerance
1940:
1899:
1828:
1823:
1779:
1774:
1763:
1759:
1750:
1746:
1737:
1733:
1724:
1720:
1711:
1707:
1700:
1696:
1689:
1685:
1678:
1674:
1668:Wayback Machine
1658:
1654:
1647:
1628:10.1.1.214.9671
1615:
1611:
1606:Wayback Machine
1597:
1593:
1583:
1581:
1567:
1563:
1562:
1558:
1527:
1523:
1518:
1514:
1496:
1492:
1486:Wayback Machine
1477:
1473:
1467:Wayback Machine
1457:
1453:
1445:
1441:
1430:
1426:
1415:
1411:
1391:
1387:
1356:
1352:
1343:
1339:
1330:
1319:
1310:
1303:
1293:John A. Zachman
1291:
1284:
1272:
1268:
1258:Wayback Machine
1248:
1235:
1226:
1222:
1213:
1209:
1198:
1194:
1182:
1178:
1169:
1162:
1156:TOGAF Version 9
1153:
1149:
1140:
1139:
1135:
1129:Wayback Machine
1119:
1115:
1111:
1063:
959:company in 1993
939:
877:
861:Wayback Machine
826:E-overheid NORA
790:
756:
698:
682:
626:
624:Standardization
582:
538:
499:
456:Example of the
450:
388:
383:
290:architecture".
238:By 1980, IBM's
173:
145:
101:
90:
84:
81:
69:
58:
44:
28:
24:
17:
12:
11:
5:
2797:
2787:
2786:
2781:
2764:
2763:
2761:
2760:
2750:
2739:
2736:
2735:
2733:
2732:
2727:
2722:
2717:
2712:
2707:
2701:
2699:
2698:Related fields
2695:
2694:
2691:
2690:
2688:
2687:
2682:
2677:
2672:
2666:
2664:
2660:
2659:
2657:
2656:
2651:
2646:
2641:
2636:
2631:
2629:Function model
2626:
2621:
2616:
2611:
2605:
2603:
2599:
2598:
2596:
2595:
2590:
2585:
2580:
2575:
2570:
2565:
2560:
2555:
2550:
2545:
2540:
2535:
2533:Executable UML
2530:
2525:
2519:
2517:
2510:
2506:
2505:
2503:
2502:
2497:
2492:
2487:
2482:
2477:
2471:
2469:
2465:
2464:
2462:
2461:
2456:
2455:
2454:
2444:
2439:
2434:
2429:
2424:
2419:
2414:
2409:
2404:
2399:
2394:
2389:
2384:
2379:
2374:
2373:
2372:
2367:
2362:
2357:
2352:
2342:
2337:
2331:
2329:
2325:
2324:
2322:
2321:
2316:
2311:
2306:
2301:
2296:
2291:
2286:
2281:
2276:
2274:Formal methods
2271:
2266:
2261:
2256:
2250:
2248:
2244:
2243:
2236:
2235:
2228:
2221:
2213:
2204:
2203:
2201:
2200:
2194:
2191:
2190:
2188:
2187:
2182:
2177:
2172:
2167:
2162:
2157:
2152:
2146:
2144:
2143:Related fields
2140:
2139:
2137:
2136:
2131:
2126:
2121:
2116:
2111:
2109:Radhika Nagpal
2106:
2101:
2099:Derek Hitchins
2096:
2091:
2086:
2081:
2076:
2071:
2066:
2061:
2056:
2054:James S. Albus
2050:
2048:
2044:
2043:
2041:
2040:
2035:
2030:
2025:
2020:
2015:
2010:
2005:
2000:
1995:
1989:
1987:
1983:
1982:
1980:
1979:
1974:
1969:
1964:
1959:
1954:
1948:
1946:
1942:
1941:
1939:
1938:
1933:
1928:
1923:
1918:
1913:
1907:
1905:
1901:
1900:
1898:
1897:
1892:
1887:
1882:
1877:
1872:
1867:
1862:
1857:
1852:
1847:
1842:
1836:
1834:
1830:
1829:
1822:
1821:
1814:
1807:
1799:
1793:
1792:
1786:
1778:
1777:External links
1775:
1773:
1772:
1757:
1744:
1731:
1718:
1705:
1694:
1683:
1672:
1652:
1645:
1609:
1591:
1556:
1521:
1512:
1490:
1471:
1451:
1439:
1424:
1409:
1393:Jeanne W. Ross
1385:
1372:10.2307/249787
1366:(4): 385–403.
1350:
1337:
1317:
1301:
1282:
1266:
1233:
1220:
1207:
1192:
1176:
1160:
1147:
1133:
1112:
1110:
1107:
1106:
1105:
1100:
1095:
1090:
1085:
1080:
1075:
1069:
1062:
1059:
1058:
1057:
1047:
1044:
1035:
1030:
1024:
1014:
1011:
1008:
1005:
1002:Roger Evernden
994:
988:
982:
976:
966:
960:
949:
946:
943:
938:
935:
934:
933:
927:
909:
903:
896:
890:
876:
873:
872:
871:
864:
847:
833:
828:
822:
813:
799:
794:
789:
786:
785:
784:
778:
772:
766:
763:
755:
752:
751:
750:
740:
734:
728:
715:
709:
702:
697:
694:
681:
678:
674:
673:
670:
667:
664:
625:
622:
606:systems design
581:
578:
537:
534:
530:
529:
526:
523:
520:
513:
512:
509:
506:
498:
495:
486:
485:
482:
479:
476:
473:
449:
446:
433:
432:
426:
420:
414:
387:
384:
382:
379:
257:
256:
253:
250:
247:
207:influenced by
172:
169:
168:
167:
164:
160:
144:
141:
103:
102:
85:September 2022
47:full citations
31:
29:
22:
15:
9:
6:
4:
3:
2:
2796:
2785:
2782:
2780:
2777:
2776:
2774:
2759:
2751:
2749:
2741:
2740:
2737:
2731:
2728:
2726:
2723:
2721:
2718:
2716:
2713:
2711:
2708:
2706:
2703:
2702:
2700:
2696:
2686:
2683:
2681:
2678:
2676:
2673:
2671:
2668:
2667:
2665:
2661:
2655:
2652:
2650:
2649:Systems model
2647:
2645:
2642:
2640:
2637:
2635:
2632:
2630:
2627:
2625:
2622:
2620:
2617:
2615:
2612:
2610:
2607:
2606:
2604:
2600:
2594:
2591:
2589:
2586:
2584:
2581:
2579:
2576:
2574:
2571:
2569:
2566:
2564:
2561:
2559:
2556:
2554:
2551:
2549:
2546:
2544:
2541:
2539:
2536:
2534:
2531:
2529:
2526:
2524:
2521:
2520:
2518:
2516:Developmental
2514:
2511:
2507:
2501:
2498:
2496:
2493:
2491:
2488:
2486:
2483:
2481:
2478:
2476:
2473:
2472:
2470:
2466:
2460:
2457:
2453:
2450:
2449:
2448:
2445:
2443:
2440:
2438:
2435:
2433:
2430:
2428:
2425:
2423:
2420:
2418:
2415:
2413:
2410:
2408:
2405:
2403:
2400:
2398:
2395:
2393:
2390:
2388:
2385:
2383:
2380:
2378:
2377:Data modeling
2375:
2371:
2368:
2366:
2363:
2361:
2358:
2356:
2353:
2351:
2348:
2347:
2346:
2343:
2341:
2338:
2336:
2333:
2332:
2330:
2326:
2320:
2317:
2315:
2312:
2310:
2307:
2305:
2302:
2300:
2297:
2295:
2292:
2290:
2287:
2285:
2282:
2280:
2277:
2275:
2272:
2270:
2267:
2265:
2262:
2260:
2257:
2255:
2252:
2251:
2249:
2245:
2241:
2234:
2229:
2227:
2222:
2220:
2215:
2214:
2211:
2199:
2196:
2195:
2192:
2186:
2183:
2181:
2178:
2176:
2173:
2171:
2168:
2166:
2163:
2161:
2158:
2156:
2153:
2151:
2148:
2147:
2145:
2141:
2135:
2132:
2130:
2127:
2125:
2122:
2120:
2117:
2115:
2112:
2110:
2107:
2105:
2102:
2100:
2097:
2095:
2092:
2090:
2089:Barbara Grosz
2087:
2085:
2084:Wolt Fabrycky
2082:
2080:
2077:
2075:
2072:
2070:
2067:
2065:
2062:
2060:
2059:Ruzena Bajcsy
2057:
2055:
2052:
2051:
2049:
2045:
2039:
2036:
2034:
2031:
2029:
2026:
2024:
2021:
2019:
2016:
2014:
2011:
2009:
2006:
2004:
2001:
1999:
1996:
1994:
1991:
1990:
1988:
1984:
1978:
1975:
1973:
1970:
1968:
1965:
1963:
1960:
1958:
1955:
1953:
1950:
1949:
1947:
1943:
1937:
1934:
1932:
1931:Design review
1929:
1927:
1924:
1922:
1919:
1917:
1914:
1912:
1909:
1908:
1906:
1902:
1896:
1893:
1891:
1888:
1886:
1883:
1881:
1878:
1876:
1873:
1871:
1868:
1866:
1863:
1861:
1858:
1856:
1853:
1851:
1848:
1846:
1843:
1841:
1838:
1837:
1835:
1831:
1827:
1820:
1815:
1813:
1808:
1806:
1801:
1800:
1797:
1790:
1787:
1784:
1781:
1780:
1769:
1768:
1761:
1755:
1754:
1748:
1742:
1741:
1738:Pragmatic EA
1735:
1729:
1728:
1722:
1716:
1715:
1709:
1703:
1698:
1692:
1687:
1681:
1676:
1669:
1665:
1662:
1656:
1648:
1642:
1638:
1634:
1629:
1624:
1620:
1613:
1607:
1603:
1600:
1595:
1579:
1575:
1574:
1566:
1560:
1552:
1548:
1544:
1540:
1536:
1532:
1525:
1516:
1509:
1505:
1504:
1499:
1494:
1487:
1483:
1480:
1475:
1468:
1464:
1461:
1455:
1449:
1443:
1436:
1435:
1428:
1421:
1420:
1413:
1406:
1402:
1398:
1394:
1389:
1381:
1377:
1373:
1369:
1365:
1361:
1360:MIS Quarterly
1354:
1347:
1341:
1334:
1328:
1326:
1324:
1322:
1314:
1308:
1306:
1298:
1294:
1289:
1287:
1279:
1275:
1270:
1263:
1259:
1255:
1252:
1246:
1244:
1242:
1240:
1238:
1230:
1224:
1217:
1211:
1204:
1203:
1196:
1189:
1185:
1180:
1173:
1167:
1165:
1157:
1151:
1143:
1142:"Tech Target"
1137:
1130:
1126:
1123:
1117:
1113:
1104:
1101:
1099:
1096:
1094:
1091:
1089:
1086:
1084:
1081:
1079:
1076:
1073:
1070:
1068:
1065:
1064:
1055:
1051:
1048:
1045:
1043:
1039:
1036:
1034:
1031:
1028:
1025:
1022:
1019:developed by
1018:
1015:
1012:
1009:
1006:
1003:
999:
995:
992:
989:
986:
983:
980:
977:
974:
970:
967:
964:
961:
958:
955:(IAF) – from
954:
950:
947:
944:
941:
940:
931:
928:
925:
921:
917:
913:
910:
907:
904:
901:
897:
894:
891:
889:
886:
885:
884:
882:
869:
865:
862:
858:
855:
851:
848:
846:in July 2000.
845:
841:
837:
834:
832:
829:
827:
823:
821:
817:
814:
811:
807:
803:
800:
798:
795:
792:
791:
782:
779:
776:
773:
770:
767:
764:
761:
758:
757:
748:
744:
741:
738:
735:
732:
729:
726:
723:
719:
716:
713:
710:
707:
703:
700:
699:
693:
686:
677:
671:
668:
665:
662:
661:
660:
658:
654:
649:
647:
643:
642:IEEE Standard
639:
635:
631:
621:
619:
613:
611:
607:
603:
599:
591:
586:
577:
575:
570:
566:
562:
560:
554:
552:
542:
533:
527:
524:
521:
518:
517:
516:
510:
507:
504:
503:
502:
494:
491:
483:
480:
477:
474:
471:
470:
469:
466:
459:
454:
445:
443:
437:
430:
427:
424:
421:
418:
415:
412:
409:
408:
407:
405:
401:
392:
378:
375:
370:
366:
364:
359:
356:
351:
349:
345:
340:
338:
333:
329:
325:
323:
319:
314:
311:
306:
304:
300:
295:
291:
287:
285:
280:
277:
273:
268:
266:
263:In 1986, the
261:
254:
251:
248:
245:
244:
243:
241:
236:
232:
230:
222:
218:
214:
211:, JTA, JTAA,
210:
206:
202:
198:
194:
190:
186:
182:
177:
165:
161:
157:
156:
155:
152:
150:
140:
137:
133:
129:
125:
117:
113:
109:
99:
96:
88:
76:
75:documentation
72:
65:
64:documentation
61:
56:
52:
48:
43:
41:
37:
32:This article
30:
21:
20:
2644:Object model
2639:Metamodeling
2568:Spiral model
2468:Orientations
2124:Katia Sycara
2008:Optimization
1766:
1760:
1752:
1747:
1739:
1734:
1726:
1721:
1713:
1708:
1697:
1686:
1675:
1655:
1618:
1612:
1594:
1582:. Retrieved
1578:the original
1571:
1559:
1534:
1530:
1524:
1515:
1507:
1501:
1493:
1474:
1454:
1442:
1432:
1427:
1417:
1412:
1404:
1388:
1363:
1359:
1353:
1345:
1340:
1332:
1312:
1296:
1277:
1274:John Zachman
1269:
1261:
1228:
1223:
1215:
1210:
1200:
1195:
1187:
1179:
1155:
1150:
1144:. SearchCIO.
1136:
1116:
1054:John Zachman
1042:Michael Bell
878:
691:
675:
656:
650:
645:
627:
617:
614:
595:
571:
567:
563:
555:
547:
531:
514:
500:
489:
487:
467:
463:
438:
434:
397:
377:technology.
371:
367:
360:
354:
352:
343:
341:
336:
334:
330:
326:
317:
315:
307:
296:
292:
288:
281:
271:
269:
262:
258:
237:
233:
226:
153:
146:
128:EA framework
127:
123:
121:
91:
82:
71:Citation bot
33:
2335:Abstraction
1791:(July 2021)
1785:(July 2016)
1397:Peter Weill
975:since 2004.
881:open source
731:IDEAS Group
618:view models
488:Each layer
2773:Categories
2654:View model
2619:Data model
2114:Simon Ramo
1109:References
951:Capgemini
747:Open Group
598:view model
580:View model
219:1996, and
51:verifiable
2663:Languages
1904:Processes
1833:Subfields
1623:CiteSeerX
957:Capgemini
888:ArchiMate
852:- MRAE -
737:ISO 19439
638:IEEE 1471
490:delegates
372:In 2013,
276:artifacts
199:1999 and
36:bare URLs
2758:Category
2624:ER model
2490:Ontology
2402:Software
2328:Concepts
2198:Category
1945:Concepts
1664:Archived
1602:Archived
1551:51802872
1482:Archived
1463:Archived
1295:(1987).
1254:Archived
1125:Archived
1061:See also
857:Archived
840:treasury
143:Overview
40:link rot
2748:Commons
2573:V-model
1972:V-Model
1725:Labnaf
1500:(2011)
1403:(2006)
1276:(1982)
1186:(2004)
1004:in 1996
963:Dragon1
906:Praxeme
714:(GERAM)
305:(BSP).
171:History
2509:Models
2259:DevOps
2247:Fields
2047:People
1962:System
1643:
1625:
1584:7 July
1549:
1506:. in:
1399:, and
1380:249787
1378:
973:Sogeti
745:– The
718:RM-ODP
195:1997,
191:1992,
187:1989,
183:1987,
60:reFill
2685:SysML
2609:SPICE
2602:Other
2563:Scrum
2523:Agile
2475:Agile
2459:CI/CD
1986:Tools
1702:SABSA
1691:MEGAF
1599:DNDAF
1568:(PDF)
1547:S2CID
1376:JSTOR
1260:" on
1072:EABOK
916:MODAF
868:IndEA
775:MODAF
769:DoDAF
760:AGATE
743:TOGAF
640:, an
374:TOGAF
310:TAFIM
223:2003.
221:DoDAF
217:C4ISR
213:TOGAF
209:POSIX
205:TAFIM
193:TISAF
134:. An
34:uses
2670:IDEF
2614:CMMI
2500:SDLC
2003:IDEF
1641:ISBN
1586:2020
996:IBM
924:GFDL
912:TRAK
722:open
704:The
632:and
201:TEAF
197:FEAF
68:and
2680:USL
2675:UML
2553:RAD
2528:EUP
1633:doi
1539:doi
1368:doi
969:DYA
920:GPL
781:NAF
444:).
189:EAP
122:An
2775::
2583:XP
2558:UP
1639:.
1631:.
1588:.
1570:.
1545:.
1535:46
1533:.
1395:,
1374:.
1364:14
1362:.
1320:^
1304:^
1285:^
1236:^
1163:^
883::
620:.
612:.
604:,
596:A
576:.
406:.
2232:e
2225:t
2218:v
1818:e
1811:t
1804:v
1649:.
1635::
1553:.
1541::
1382:.
1370::
926:.
922:/
902:.
812:)
727:.
592:.
431:.
425:,
419:,
413:,
126:(
118:.
98:)
92:(
87:)
83:(
79:.
77:)
73:(
66:)
62:(
42:.
Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.
