NIST Enterprise Architecture Model: Difference between revisions

Revision as of 12:03, 26 July 2013

Revision as of 12:33, 29 July 2013

Line 38:

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" >W. Bradford Rigdon (1989) "Architectures and Standards". In: ''Information Management Directions: The Integration Challenge''. E.N. Fong and A.H. Goldfine (eds.). NIST Sept 1989. p. 135-150</ref> explained that discussions about architecture in that time mostly focus on technology concerns. Their aim was to "takes a broader view, and describes the need for an ''enterprise architecture'' that includes an emphasis on business and information requirements. These higher level issues impact data and technology architectures and decisions."<ref name="Rigdon">Rigdon (1989), p. 136</ref> In order to do so, the working group addressed three issues<ref>Fong and Goldfine (1989, p. 136)</ref>:

* The levels of architecture in an enterprise

* Problems addressed by architecture

Line 53:

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> Rigdon et al. (1989, p. 136)</ref>. It may for example represent "a view of a current situation with islands of automation, redundant processes and data inconsistencies"<ref name= "Rig 1989, 137"> Rigdon (1989), p. 137 </ref>or a "future integrated automation information structure towards which the enterprise will move in a prescribed number on years."<ref> Rigdon et al. (1989, p. 137-38)</ref> The role of standards in architecture is to "enable or constrain the architecture and serve as its foundation".<ref name="Rig 1989, 137"/>

In order to develop an enterprise architecture Rigdon acknowledge<ref> name="Rigdon" (1989), p. 136</ref>:

* There are multiple ways to develop an architecture

* There are multiple ways to implement standards