HUD Enterprise Architecture V5.0 — Volume 1 of 2

事例(Case Study)


Definition, Purpose, and Benefits of Target Enterprise Architecture

The Enterprise Architecture (EA) for the Department of Housing and Urban Development (HUD) is a business-driven plan that describes the desired current and end-state for HUD’s performance, business, applications and services, technology, data, and security architectures. The primary purpose of the EA is to capture the information required to effectively plan a course for achieving HUD’s strategic vision and goals. It is one element in a broader set of inter-related planning activities that collectively enable HUD managers and staff to define a vision, develop strategies and plans for achieving the vision, make resource decisions, implement strategies, and evaluate performance.

By defining the desired current and end-state from several distinct perspectives (e.g., business, data, etc.), the EA also provides stakeholders with a “line of sight” into the complex relationships that exist among these different perspectives. For example, the Target EA provides insight into how a particular customer need translates into a set of target HUD business processes, and how those business processes will be supported by a common set of technologies.

HUD has more than 200 information systems, executes overlapping business and information management processes, and relies on various technologies that are expensive to maintain. To reduce cost and streamline operations, HUD has adopted a service-oriented and component-based approach to architecture. This approach, consistent with government and industry best practice, enables HUD to “build once, use often.” In other words, by separating out the functionality or capabilities of a business process or application into discrete pieces, components can be shared and reused across the enterprise. As a result of this approach, the HUD EA will:

  • Improve Program Performance – The overarching benefit of the EA is that it provides opportunities to improve the efficiency and effectiveness of HUD’s programs. It ensures that business services support strategic goals and priorities, data is optimized in support of the business, and applications and technology solutions are driven by business needs. It also allows HUD to more readily share services across organizational and functional lines.
  • Simplify Investment Decisions – The EA provides a line of sight from strategy to business function to technology, allowing decision-makers to be able to more quickly assess the relative value of initiatives, and to identify duplicative or misaligned initiatives.
  • Reduce IT Diversity and Complexity – The EA simplifies HUD’s IT environment by promoting standards and the sharing and reuse of common technologies.
  • Improve Interoperability - The EA establishes enterprise-wide standards that promote platform and vendor independence, enabling greater interoperability across disparate applications, both internal and external.
  • Improve Utilization of Resources – The EA reduces system development and operation and maintenance costs by eliminating duplicative investments, promoting sharing of common services, and establishing Department-wide standards.
  • Accelerate System Implementation – The EA equips the Department’s system developers and architects with a pallet of component-based services from which to choose that provide well defined functionality, thus maximizing reuse and portability of previously developed processes, components, code, etc.

Purpose of EA Version 5.0 Document

The purpose of EA Version 5.0 is to update the EA to address stakeholder comments received and to make other refinements as needed. HUD’s EA will continue to evolve and improve as stakeholders actively participate in the development and implementation of the HUD EA. The intended near-term uses and impacts for EA Version 5.0 include:

  • Technical Reference Model (TRM) updated monthly, published on HUD’s intranet and internet
  • Performance Reference Model (PRM): HUD’s PRM was updated several times throughout FY2007. Business performance results were added to the model and aligned with CPIC evaluation and control data.
  • Execution of HUD’s standard Modernization Planning Process
  • IT Master Schedule is updated on a monthly basis to monitor the completion of performance milestones
  • Update of TRM Governance: In order to simplify TRM access and oversight
  • Update of EA Governance to reflect the process of measuring performance through the IT Master Schedule, PRM and CPIC.