Introduction to Information Architecture

1
Introduction to Information Architecture

• Informatics Training for CDC Public Health
  Advisors

2
Imagine building a house..

• without any architectural plans
• with only general sketches as to how its
  supposed to look, or only detailed diagrams for
  wiring, plumbing, etc.
• with each subcontractor doing whatever they
  thought best, without consulting with the owner
  or other contractors
• with no specialized functions for the rooms
  (e.g., every room has its own little stove, bed,
  bathtub)
• where the house had to be torn down to remodel
  one roomS.O.P. for building information systems
  in public health.

3
Information architecture

• A metaphor for a systematic, planful approach
  to building enterprise-wide information systems.
  Information architecture refers to the totality
  of the data, processes, and technology used in a
  given enterprise, and the relations between them.
  It includes databases, applications, standards,
  procedures, hardware, software, networks, etc.

4
Attributes of a good architect

• Can communicate well with the customer
• Can develop general drawings and diagrams based
  on the descriptions of customers wants and needs
• Can develop more specific drawings and diagrams
  for communicating with the builders (general
  contractor and subcontractors)
• Can communicate well with the builders, and help
  devise solutions as problems present themselves
• Can provide a consistent, overall vision
  throughout the project, and work with the
  customers and the builders to achieve that vision.

5
An information architecture

• Provides a guiding plan across projects
• Promotes component orientationÞsmaller units,
  more easily upgraded
• Eases maintenance, by defining natural
  boundaries between information systems (e.g.,
  budgeting, surveillance)
• Simplifies systems, by decreasing redundancy of
  data entry, storage

6
An information architecture

• Breaks big problems into manageable chunks
• Allows the efficiency and interoperability
  inherent in standards
• Promotes planning, clarifies business processes
• Facilitates solving a common problem once,
  instead of solving it many ways, many times
• Allows flexible incorporation of new IT

7
An information architecture

• Returns locus of control and decision making to
  the executive level, away from the IT
  community.An information architecture provides
  the basis of business control over the
  distributed development of information systems.

8
Information architecture views

• Multiple levels of architectural plans are
  needed, from the general (representing overall
  business processes objectives), to the
  specific (indicating specific technology and
  implementation details)
• The specific (technical) views of the
  architecture should be based on higher, business
  views--i.e., the IT architecture should be
  tightly tied to the business processes and
  objectives

9
Information architecture views

• Business views of the architecture Þ What needs
  to be automated
• Information technology views of the architecture
  Þ How that should be automated
• Business views should be relatively stable IT
  views should be able to adapt to improvements in
  technology

10
The Zachman Framework

• A two-dimensional structure for describing the
  information architecture of an enterprise
• 1st dimension the roles involved in information
  systems design (planner, owner, designer,
  builder)
• 2nd dimension What, How, Where, etc.

11
(No Transcript)
12
Info Architecture pearls

• We need to develop high-level blueprints of our
  public health agencies information needs, and
  use these blueprints to guide systems development
• Tools exist to help with this process (e.g., the
  Zachman Framework)
• New information systems applications should be
  developed within the context of a larger,
  coherent information architecture
• Public health leaders, not technologists, must
  drive the process

13
Info Architecture pearls (contd)

• See Cooks Building enterprise information
  architectures for an excellent review of this
  area.
• More to come We will revisit the idea of
  information architecture on Thursday.