Agencies should select reusable and sharable services and products to obtain mission or support functionality. Standardization on common functions and customers will help Federal Agencies implement change in a timely manner. Federal EA promotes intra- and inter-agency standards for aligning strategic direction with
business activities and technology enablement. EA solutions should support a diversity of public and private access methods for Government public information, including multiple access points, the separation of transactional from analytical data, and data warehousing architecture. Appropriate security monitoring and planning, including an analysis of risks and contingencies and the implementation of appropriate contingency plans, must be completed to prevent unauthorized access to Federal information. Incorporating new or proven technologies in a timely manner will help Agencies to cope with change. At the center of FEAF is the Consolidated Reference Model (CRM). The CRM equips Federal agencies with a shared language and framework that is needed to unilaterally describe and analyze investments. There are six sub-architecture domains within the Framework. These domains include: Strategy Business Data Applications Infrastructure Security
The Federal EA Framework, version 2.0 (FEAF-II) meets these criteria, an example of which is provided in Figure 2. The geometry of the FEAF-II shows the hierarchical relationship of the major areas of the architecture, which serves to emphasize that strategic goals drive business services, which in turn provide the requirements for enabling technologies. This framework also shows the relationship
You've reached the end of your free preview.
Want to read all 7 pages?
- Spring '16
- federal agencies, Enterprise Architecture framework, Federal Enterprise Architecture, FEAF