Content deleted Content added
m →History |
m link term |
||
Line 94:
* ''Applications'' : The Applications component identifies, defines, and organizes the activities that capture, manipulate, and manage the business information to support mission operations. It also describes the logical dependencies and relationships among business activities.<ref>The US Department of Energy incorporates Business Applications into its Applications Subarchitecture, while the US Department of Treasury includes them in its Functional Architecture.</ref>
* ''Data Descriptions'': This component of the Enterprise Architecture identifies how data is maintained, accessed, and used. At a high level, agencies define the data and describe the relationships among data elements used in the agency's information systems. The Data Descriptions and Relationships component can include data models that describe the data underlying the business and information needs of the agency. Clearly representing the data and data relationships is important for identifying data that can be shared corporately, for minimizing redundancy, and for supporting new applications<ref>The US Department of Agriculture has included in this element in its Business/Data Architecture, while the US Department of Treasury incorporates it in its Information Architecture.</ref>
* ''Technology Infrastructure'' : The Technology Infrastructure component describes and identifies the physical layer including, the functional characteristics, capabilities, and interconnections of the hardware, software, and communications, including networks, protocols, and nodes. It is the "wiring diagram" of the physical [[IT infrastructure]].<ref>The US Department of Agriculture had incorporated this architecture into its Technical Standard and Telecommunications Architectures. US DoD uses its System Architecture, and US Treasury its Infrastrucsture to describe the physical layer.</ref>
With the exception of the Business Processes component, the interrelationships among and priorities of these components are not prescribed by this guidance; there is no hierarchy of relationships implied. Furthermore, agencies should document not only their current environment for each of these components, but also the target environment that is desired.<ref name="M-97-16"/>
| |||