NIST Enterprise Architecture Model: Difference between revisions

Revision as of 22:31, 14 July 2013

Revision as of 22:52, 14 July 2013

Line 1:

[[File:NIST Enterprise Architecture Model.jpg|thumb|NIST Enterprise Architecture Model.<ref name="CIOC99"> The Chief Information Officers Council (1999). [http://www.enterprise-architecture.info/Images/Documents/Federal%20EA%20Framework.pdf Federal Enterprise Architecture Framework Version 1.1]. September 1999.</ref>]]

'''NIST Enterprise Architecture Model''' ('''NIST EA Model''') is a late 1980s [[Enterprise Architecture framework|reference model]] for [[Enterprise Architecture]], thatwhich illustrates the "interrelationship of enterprise business, information, and technology environments".<ref name="CIOC99"/>

Developed late 1980s by the [[National Institute of Standards and Technology]] (NIST), in the 1990s this reference model in the 1990s became widely accepted and promoted within the [[Federal government of the United States|U.S. federal government]] as Enterprise Architecture management tool.<ref name="CIOC99"/> It is applied as foundation of multiple U.S. Federal Enterprise Architecture frameworks, for example the [[Federal Enterprise Architecture Framework]].<ref name="CIOC99"/>

It is used as one of the foundations of multiple U.S. Federal Enterprise Architecture frameworks, for example the [[Federal Enterprise Architecture Framework]].<ref name="CIOC99"/>

== Overview ==

The NIST Enterprise Architecture Model is a five-layered model allows 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"/> This interrelation between the architecture layers is defined in the model:<ref name="FG89"/>

* ''Business Architecture'', which drives the information architecture

* ''Information architecture'', which prescribes the information systems architecture

* ''Information systems architecture'', which identifies the data architecture

* ''Data Architecture'', which suggests specific data delivery systems, and

* ''Data Delivery Systems'', (Software, Hardware, Communications) support the data architecture.

The hierarchy in the model is based on the notion that an organization operates a number of business functions, each function requires information from a number of source, and each of these sources may operation one or more operation systems, which in turn contain data organized and stored in any number of data systems.<ref>John O'Looney (2002). ''Wiring Governments: Challenges and Possibilities for Public Managers''. Greenwood Publishing Group. p.67.</ref>

Line 18 ⟶ 16:

[[File:DoE Information Architecture View.jpg|thumb|DoE Information Architecture View.<ref name="FAA98"/>]]

[[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]. May 2005</ref>]]

The origin from the NIST Enterprise Architecture Model was a NIST research project in 1989, published as the NIST Special Publication 500-167, ''Information Management Directions: The Integration Challenge''.<ref name="FG89"> Elizabeth N. Fong and Alan H. Goldfine (1989) ''Information Management Directions: The Integration Challenge''. National Institute of Standards and Technology (NIST) Special Publication 500-167, September 1989.</ref> InThis thispublication projectwas twothe Frameworksresult wereof proposed:the fifth workshop in the 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).

* a [[Zachman Framework]] addressing [[enterprise engineering]]; and

* a single dimensional classification of subject areas supporting Information Strategy,

This classification in the 1990s became known as the NIST Framework.

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: