To facilitate efforts to transform the Federal Government into one that is citizen-centered, results-oriented, and market-based, the Office of Management and Budget (OMB) is developing the Federal Enterprise Architecture (FEA), a business-based framework for Government-wide improvement.
The FEA is being constructed through a collection of interrelated "reference models" designed to facilitate cross-agency analysis and the identification of duplicative investments, gaps, and opportunities for collaboration within and across Federal Agencies.
The FEA Technical Reference Model (TRM) provides a foundation to describe the standards, specifications, and technologies supporting the secure delivery, exchange, and construction of business (or Service) components and e-Gov solutions. The FEFA TRM unifies existing Agency TRMs and electronic Government (e-Gov) guidance by providing a foundation to advance the re-use of technology and component services from a Government-wide perspective.
TARGET AUDIENCE
Program Managers - responsible for assembling components and technology to support the implementation of a project or program that may require cross-agency collaboration and the re-use of agency assets.
Chief Architects - responsible for the definition and target planning of an Agency's Enterprise Architecture.
System / Solution Architects / Developers - responsible for building / assembling systems, and selecting technologies and standards that leverage existing assets and services across the government and industry
SUMMARY OF TRM VERSION 1.0
The TRM, as illustrated in homepage, outlines the standards, specifications, and technologies that collectively support the secure delivery, exchange, and construction of business and application components (Service Components) that may be used and leveraged in a Component-Based or Service Orientated Architecture. The TRM identifies the core technologies that support the Federal Government information technology (IT) transition towards interoperable e-Government solutions.
TECHNICAL REFERENCE MODEL BACKGROUND
Definition
The TRM is a component-driven, technical framework used to identify the standards, specifications, and technologies that support and enable the delivery of service components and capabilities.
Purpose
The TRM serves to outline the technology elements that collectively support the adoption and implementation of component-based architectures. The model provides the foundation to advance the re-use of technology and component services across the Federal Government through standardization. Aligning Agency capital investments to the TRM leverages a common, standardized vocabulary, allowing inter-Agency and intra-Agency discovery, collaboration, and interoperability. Agencies, and the Federal Government, will benefit from economies of scale by identifying and re-using the best solutions and technologies to support their business functions, mission, and target architecture.
Specifically, the TRM was created to:
Create a government-wide reference model that unifies agency TRMs and existing e-Gov guidance
Focus technology standards, specifications, and recommendations on those that embrace the Internet and related approaches
Create a foundation that focuses heavily on the secure delivery and construction of Service Components and their interfaces
Identify the layers of a Component-Based Architecture, the supporting technologies, and recommendations for each
KEY CONCEPTS AND DEFINITIONS
Technologies - refers to a specific implementation of a standard within the context of a given specification.
The following describes for illustrative purpose the use of the term 'technologies' as used in the TRM.
1.PL/SQL is an Oracle implementation of the SQL Standard
2.ISQL/w is a Microsoft implementation of the SQL Standard
3.ODBC is an implementation of a data access standard within various Microsoft specifications
4.JDBC is an implementation of a data access standard within the Sun Microsoft specifications
While all are based on an Open Standard, each vendor has their own implementation of the standard based on their specific technologies.
Legacy - refers to both software and/or hardware from previous technology generations. From a software perspective, legacy in the TRM refers to any technologies that are not Internetenabled and not component-based.
Component - a self-contained business process or service with predetermined functionality that may be exposed through a business or technology interface.
Component Based Architecture (CBA) - a technology architecture comprised of run-time services and control structures together with an application infrastructure. The CBA consists of the component model and the architecture services that are built around the model. As illustrated in homepage, solutions based on a CBA are more dynamic, flexible, and maintainable than traditional monolithic solutions.
Service Area - is a technical tier that supports the secure construction, exchange, and delivery of business or service components. Each Service Area groups the requirements of component-based architectures within the Federal Government into functional areas.
Service Category - is a sub-tier of the Service Area to classify lower levels of technologies, standards, and specifications in respect to the business or technology function they serve.
Standard - hardware, software, or specifications that are widely used and accepted (de facto), or are sanctioned by a standards organization (de jure). Standards are typically categorized as follows:
1.Programming Language Standards
2.Character Code Standards
3.Hardware Interface Standards
4.Storage Media Standards
5.Operating System Standards
6.Communication and Networking Standards
7.Machine Language Standards
8.File System Management Standards
9.Database Management System Standards
10.Text Systems Standards
11.Graphic Systems Standards
12.Internet Standards
Specification - a formal layout/blueprint/design of an application development model for developing distributed component-based architectures.
Developing components based on a specification simplifies enterprise applications by basing them on standardized, modular components, and by providing a complete set of services to those components.
Two specifications for Agency use that promote the concept of Internet-enabled distributed component-based architectures are described in this TRM: Microsoft.NET and Sun Microsystems J2EE.
DEVELOPMENT OF THE TRM
In developing the TRM, the FEAPMO leveraged previous Federal architecture efforts, such as the Federal Enterprise Architecture Framework (FEAF) to guide the design of the government-wide model. The FEAPMO then performed extensive research on industry and government standards, specifications, and technologies to further refine and enhance the model.
The information contained within these sources provided thorough documentation of the many services, capabilities and technologies that industry and government applications and IT initiatives deliver. The FEAPMO used this information to normalize and categorize standards, specifications, and technologies that support the business and service components and capabilities.
Once a list of Service Areas, Service Representations, Service Categories and Specifications was developed, definitions were given to each of the layers of the model and their contents.
Continued refinement of the TRM will include factoring in additional Agency architectures, such as DoD's C4ISR architecture and their Core Architecture Data Model (CADM).
VALIDATION
The TRM was reviewed, validated and revised by the FEA-PMO and the SAWG, then released to agencies for feedback on January 29, 2003. Agency comments on the TRM were received and compiled through March 31, 2003. This feedback was analyzed by the FEA-PMO to further advance/evolve the model. The FEA-PMO's response to Agency comments will be published in a Comments Response Document, and will be available via Agency Chief Information Officers (CIOs).
A first pass was performed at aligning the TRM to the Agencies' major IT initiatives, as well as the 24 Presidential Priority E-Gov initiatives to the TRM. The alignment will be validated by agencies through the Federal Enterprise Architecture Management System (FEAMS), discussed further in Chapter 4 of this document.
VENDOR-SPECIFIC PRODUCTS
The TRM is not intended to provide or endorse particular vendor products. Where specific products are listed, they are products sanctioned by the Federal CIO Council, and are those that specifically pertain to developing web solutions, as are all of the technologies, standards and specifications contained within the TRM. For example you will see a product such as Microsoft .NET within the TRM because it's a product contained within the CIO Council list, and it's used for developing web pages and web service/component-based solutions, a component of CBA.
You will not see technologies such as FORTRAN or COBOL as these programming languages are primarily for developing computational and client/server systems, and not web-based e-Government solutions.
您对本站有任何意见或建议，请直接与管理员联系
Copyright© 1998-2008 ITCore版权所有. All
rights reserved.