Content deleted Content added
Rescuing 1 sources and tagging 0 as dead.) #IABot (v2.0 |
Rescuing 1 sources and tagging 0 as dead.) #IABot (v2.0.9.5 |
||
| (9 intermediate revisions by 7 users not shown) | |||
Line 1:
{{Use American English|date = March 2019}}
{{Short description|Reference model
{{Use mdy dates|date = March 2019}}
[[File:NIST Enterprise Architecture Model.jpg|thumb|NIST Enterprise Architecture Model.]]
Line 7:
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]].<ref name="CIOC99"/>
==
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.<ref name="CIOC99"/> The model defined the interrelation as follows:<ref name="FG89"/>
* Business Architecture drives the information architecture
Line 17:
== History ==
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). The results of this research project were published as the NIST Special Publication 500-167, ''Information Management Directions: The Integration Challenge''.<ref name="FG89">
=== The emerging field of information management ===
Line 29:
At the center, the conceptual schema defines the [[Ontology (information science)|ontology]] of the [[concept]]s as the [[user (computing)|user]]s think of them and talk about them. The physical schema according to Sowa (2004) "describes the internal formats of the [[data]] stored in the [[database]], and the external schema defines the view of the data presented to the [[application program]]s".<ref name ="JFS04">[[John F. Sowa]] (2004). "The Challenge of Knowledge Soup," in: ''Research Trends in Science, Technology and Mathematics Education''. Edited by J. Ramadas & S. Chunawala, Homi Bhabha Centre, Mumbai, 2006.</ref>
Since the 1970s the NIST had held a series of four workshops on Database and Information Management Directions. Each of the workshops addresses a specific theme:<ref>{{harvnb|Fong
* "What information about [[database]] technology does the manager need to make prudent decisions about using new technology", in 1975.
* "What information can help a manager assess the impact on a database system?" in 1977.
Line 35:
* "The nature of information [[resource management]] practice and problems" in 1985.
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.<ref>{{harvnb|Fong
=== NIST workshop on Information Management Directions ===
The fifth Information Management Directions workshop in 1989 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]],<ref>[http://www.geoinfo.tuwien.ac.at/staff/index.php?Current_Staff:Frank%2C_Andrew_U. Frank, Andrew U.] Research Group Geoinformation, Vienna. Accessed
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.<ref>{{harvnb|Fong
* the integration of knowledge and data management
* the integration of technical and business data management
Line 48:
In the third working group on systems planning was chaired by [[John Zachman]], and adopted the [[Zachman Framework]] as a basis for discussion.
[[File:NIST AE model 1989.jpg|thumb|Model of Enterprise Architecture, 1989]]
The fifth working group on architectures and standards was chaired [[W. Bradford Rigdon]] of the McDonnell Douglas Information Systems Company (MDISC), a division of [[McDonnell Douglas]]. Rigdon et al. (1989) <ref name="WBR 1989" >
* The levels of architecture in an enterprise
* Problems addressed by architecture
Line 55:
=== Application in the 1990s ===
In a way the NIST Enterprise Architecture Model was ahead of his time. 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.<ref>J.A Zachman (1993) ''[http://www.ies.aust.com/pdf-papers/zachman3.pdf Concepts for Framework for EA - Enterprise Architecture Resources] {{Webarchive|url=https://web.archive.org/web/20201023104637/http://www.ies.aust.com/PDF-papers/zachman3.pdf |date=October 23, 2020 }}''. Zachman International, Inc. paper. p. 1</ref> [[Software architecture]], for example. become an important topic not until the second half of the nineties.<ref>Leonor Barroca, Jon Hall and Patrick Hall (200) "[http://mcs.open.ac.uk/lmb3/introduction.pdf An Introduction and History of Software Architectures, Components, and Reuse]" in: ''Software Architectures'', 2000 p. 1</ref>
To support the NIST Enterprise Architecture Model in the 1990s, it was widely promoted within the [[Federal government of the United States|U.S. federal government]] as Enterprise Architecture management tool.<ref name="CIOC99"/> The NIST Enterprise Architecture Model is applied as foundation in multiple Enterprise Architecture frameworks of U.S. Federal government agencies and in the overall [[Federal Enterprise Architecture Framework]].<ref name="CIOC99"/> In coordinating this effort the NIST model was further explained and extended in the 1997 "Memoranda 97-16 (Information Technology Architectures)" issued by the US Office of Management and Budget.,<ref name="M-97-16">Franklin D. Raines, US OBM (1997) ''[
== NIST Enterprise Architecture Model topics ==
=== Foundations ===
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".<ref>{{harvnb|Rigdon
In order to develop an enterprise architecture Rigdon acknowledge:<ref name="Rigdon" />
Line 75:
=== Levels of architecture ===
Each layer of architecture in the model has a specific intention:<ref>{{harvnb|Rigdon
* Business Architecture level: This level can picture the total or a subunit of any corporation, which are in contact with external organizations.
Line 89:
:''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.''
:''The documentation of the Enterprise Architecture should include a discussion of principles and goals.<ref group=Note>Examples of published architectural "frameworks" include the [[Treasury Information System Architecture Framework]] (TISAF), the US Department of Defense [[Technical Architecture Framework for Information Management]] (TAFIM), and the [[:commons:Category:DOE Information Architecture|Department of Energy's Information Architecture Volume 1]].</ref> For example, the agency's overall management environment, including the balance between centralization and decentralization and the pace of change within the agency, should be clearly understood when developing the Enterprise Architecture. Within that environment, principles and goals set direction on such issues as the promotion of interoperability, open systems, public access, end-user satisfaction, and security.''
In this guidance the five component model of the NIST was adopted and further explained. Agencies were permitted to identify different components as appropriate and to specify the organizational level at which specific aspects of the components will be implemented. 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:<ref name="M-97-16"/>
Line 105:
[[File:FDIC’s Enterprise Architecture Framework.jpg|thumb|FDIC EA Framework.<ref>OIG (2005). [http://www.fdicoig.gov/reports05/05-018-508.shtml Implementation of E-Government Principles] {{Webarchive|url=https://web.archive.org/web/20090114041340/http://fdicoig.gov/reports05/05-018-508.shtml |date=January 14, 2009 }}. May 2005</ref>]]
The NIST Framework was picked up by several U.S. federal agencies and used as the basis for their information strategy.<ref name="Zac06">[http://www.objectwatch.com/whitepapers/IASANewsletterApril2007.pdf "Exclusive Interview with John Zachman"] by Roger Sessions. In: ''Perspectives of the International Association of Software Architects''. April 2006.</ref> The reference model is applicated the following frameworks:
* [[United States Department of Energy|Department of Energy]] (DOE) Information Architecture <ref name="FAA98">Federal Aviation Administration (1998) ''[http://www.faa.gov/niac/pdf/wn18_fia.pdf Federal Information Architecture Initiatives]''. February 1998</ref>
* [[FDIC Enterprise Architecture Framework]] is the Enterprise Architecture framework of the Federal Deposit Insurance Corporation (FDIC).
* [[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.<ref name="CIOC99"/>
Line 123:
{{NIST-PD}}
{{reflist|2}}
===Sources===
*{{Cite book |url=https://entsosaf.eaasos.info/Content/Downloads/NIST_167.pdf |title=Information Management Directions: The Integration Challenge |date=September 1989 |publisher=National Institute of Standards and Technology (NIST) |editor-last=Fong |editor-first=Elizabeth N. |series=NIST Special Publication |volume=500-167 |editor-last2=Goldfine |editor-first2=Alan H.}}
**{{Cite book |last=Rigdon |first=W. Bradford |url=https://entsosaf.eaasos.info/Content/Downloads/NIST_167.pdf |title=Information Management Directions: The Integration Challenge |date=Sep 1989 |publisher=NIST |editor-last=Fong |editor-first=Elizabeth N. |pages=135-150 |chapter=Architectures and Standards |author-link=W. Bradford Rigdon |editor-last2=Goldfine |editor-first2=Alan H.}}
== External links ==
{{Commons category|NIST Enterprise Architecture Model}}
| |||