Home / Program Offices / Chief Information Officer / EA / Enterprise Architecture Practice


Chief Information Officer

Enterprise Architecture


Enterprise Architecture


Enterprise Architecture


Enterprise Architecture

HUD's Enterprise Architecture (EA) Practice initiates an information technology (IT) lifecycle that is comprised of three integrated phases - architecture, investment, and implementation. EA work is business-driven, and technology solutions begin with the intended business model as the goal. HUD "architects" before design, and designs before building and deploying technologies.

Enterprise Architects and Solutions Architects work collaboratively with business and technical subject-matter experts from throughout the Department and other agencies to guide the development of information technology Blueprints, which represent segments within the HUD Enterprise Architecture v4.0. The Practice provides strategic direction to the IT Investment Management (ITIM) process by aligning common solutions across HUD's strategic lines of business, business functions and core IT services. These activities enable accelerated IT Modernization at HUD.

HUD is mandated by the Clinger-Cohen Act and by OMB Circular A-130 to develop and enforce a single enterprise architecture. EA is also a key E-Government component in the progress of the President's Management Agenda.

This enterprise approach:

Simplifies IT investment decision-making

HUD's EA practice uses blueprints to enhance the evaluation of proposed IT initiatives. Blueprints provide a common language that links IT initiatives with the Department's strategic objectives and core business functions. Our simple approach provides executive-level staff with a strategic, enterprise view of HUD's IT portfolio.

Accelerates system implementation

HUD's EA practice applies existing blueprints to accelerate system design and development. Blueprints are working documents. They define core business processes, common data elements, cross-cutting applications, and standard system platforms. Blueprints are used to verify common system needs that span program areas, and facilitate enhanced communication between program areas and technical staff to define custom requirements. Our leveraged approach means that system design does not start from scratch.

Reduces system diversity

HUD's EA practice uses blueprints to streamline HUD's IT environment. Blueprints define core business processes, common data elements, and standard applications and platforms. Standardization reduces the number of IT products, reduces system maintenance and operation costs, and simplifies staff training. Our standards-based approach reduces systems diversity across the Department.



Related Links: