Essay About Presidential Priority E-Gov Initiatives And Standardization Of Technologies

Enterprise Architecture
Essay Preview: Enterprise Architecture
Report this essay
BACKGROUND
There is a strong need and business case for standardization of technologies and requirements used to
design, build, and implement solutions for the 24 Presidential Priority E-Gov initiatives. Without
standardization and the recommendation of technologies, agencies risk building and deploying solutions
that use proprietary technologies, are not aligned to the Federal Enterprise Architecture (FEA) and isolate
themselves from other initiatives and cross-agency business functions. To mitigate these risks, the FEAProgram
Management Office (PMO) created a Component-Based Architecture that defines a set of
recommendations that should be considered when selecting the tools, technologies, and industrystandards
that will be used to build the 24 Presidential Priority E-Gov initiatives and subsequent business
solutions. A multi-disciplinary and cross-functional working group of initiative representatives is
necessary to assist with the coordination and implementation of the Component-Based Architecture.
INTRODUCTION
Under the direction of the FEA-PMO, the SAWG was created to help agencies and the 24 Presidential
Priority E-Gov initiatives achieve success in areas of system architecture, technology selection, and the
adoption of industry-driven standards (i.e., XML, Web Services, J2EE, .NET) that can be leveraged on a
governmentwide scale. The SAWG will also support FEA efforts, and help integrate the 24 Presidential
Priority E-Gov initiatives with e-authentication. The SAWG is supported by Federal personnel across a
multitude of agencies. Specifically, the SAWG:
Provides E-Gov initiative teams with solution architects who will assist in defining initiative
blueprints and validate system architectures to support the planning and implementation of the
24 Presidential Priority E-Gov initiatives.
Establishes linkages between relevant governmentwide entities (i.e., CIO Council, XML Working
Group) to ensure that standards, best practices, and lessons learned are leveraged across the
entire government.
Selects, recommends, and assists in the deployment of technologies that are proven, stable,
interoperable, portable, secure, and scalable.
Facilitates the migration and transition of E-Gov initiatives from legacy and “inward-driven”
architectures, to architectures that embrace component-driven methodologies and technology
reuse.
FEDERAL ENTERPRISE ARCHITECTURE
PROGRAM MANAGEMENT OFFICE
(FEA-PMO)
Solution Architecture Working Group (SAWG)
Draft v1.0 7/17/2002
Identifies and quickly capitalizes on opportunities to leverage, share, and reuse technologies to
support common business requirements, activities, and operations across the Federal
Government.
Champions the creation and propagation of intellectual capital (IC) that can assist in EGovernment
transformation.
KEY OBJECTIVES
The SAWG has defined several key objectives to help agencies leverage the skills and capabilities of the
working group. These include (but are not limited to):
1. Generation and Distribution of IC. Generate IC on an on-going basis and maintain it within a
collaboration/knowledge management