100%(11)11 out of 11 people found this document helpful
This preview shows page 1 - 3 out of 6 pages.
EA Framework Research PaperIFSM 31130 June 2019Introduction
The Federal Enterprise Architecture Framework (FEAF) was established in response to the Clinger-Cohen Act of 1996. The Clinger-Cohen Act was established to provide guidance to federal agencies with regards to governing and managing IT policies. The act provides a means for federal agencies to better manage strategic planning along with IT acquisition practices. The act was also a means of accountability for federal agencies with regards to the entire federal IT structure. The FEAF streamlines and facilitates common practices and information sharing between federal and governmental agencies. The FEAF is broken down into four categories: business, data, applications, and technology architectures (FEAF, 2016). Utility and interoperability are leveraged to the maximum extent possible when using FEAF. PurposeFEAF is principle framework utilized by federal agencies to ensure that all EA used by the federal government is consistent in its processes and practices. Consistency provides better mission effectiveness and promoted integration within various federal agencies. Prior to the FEAR being established, federal agencies were basically left to their own devices with each agency establishing its own EA framework without regard to whether or not integration with other agencies was required. By establishing a framework that took into considerations other federal agencies, the FEAF allowed a more streamlined and efficient EA that eliminated duplicative processes and “leaned out” the EA into a more efficient architecture that served various agencies and not just one particular agency.