Through a series of models, the Information Architecture specifies the key elements of information systems the NIH uses in executing its business processes. These elements include the information itself, the applications that use the information to enable the business processes, and how applications and information together support the enterprise’s business functions.
Together with the Business Architecture the Information Architecture maps business systems, or “applications”, and enterprise data to business processes. The information architecture also specifies which parts of the business process are supported by each application and where each type of data is stored and managed.
NIH’s Information Architecture is comprised of three sub-architectures:
- Data Architecture – Through data models, the Data Architecture identifies the data NIH manages to perform its mission. For example, access and distribution models identify NIH enterprise data stores and information flows.
- Integration Architecture – The Integration Architecture consists of models that identify how applications are integrated to support end-to-end business processes and operations. It also includes NIH’s strategy for application integration.
- Application Architecture – The NIH Application Architecture represents its application portfolio and identifies the business systems that enable and support the execution of NIH business processes. It provides a cross reference of application to business functions and processes to illustrate application boundaries.
Information Architecture Artifacts
The primary artifacts of the information architecture are models. These various models are currently under development. As the Office of the Chief IT Architect (OCITA) validates these models with the appropriate stakeholders, they will be posted to the Information Architecture library.
Examples of NIH Information Architecture artifacts, by sub-architecture, are as follows.
Data Architecture
- Enterprise Conceptual Data Model (CDM). A CDM is list of the key data objects (referred to as “data entities”), which are of interest to the NIH. It presents a formal representation of the data needed to run the NIH. The CDM is independent of any software or data storage structure.
Integration Architecture
- Application Integration Model. Integration models illustrate how applications or systems integrate in order to share common information needed by those applications. The NIH is currently moving towards a Service-Oriented Architecture (SOA) approach to application integration. The SOA approach will enable the transition through application integration middleware. OCITA completed a proof-of-concept study in October of 2005 to help identify toolsets capable of supporting the evolution of an SOA approach and plans to publish Integration Architecture artifacts in the first quarter of calendar year 2006.
Application Architecture
- Application Boundary Map. The NIH Application Boundary Map groups, or “bounds”, NIH business processes by function. Each boundary represents the functional scope within which NIH information systems operate.
Information Architecture Principles
Data Principles
Integration Principles
Application Principles