Content deleted Content added
Phil Boswell (talk | contribs) Reference edited with ProveIt #proveit |
Phil Boswell (talk | contribs) →Information Technology Architecture: Adding/improving reference(s) |
||
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"/>
| |||