The following are official DSIA definitions that disambiguate the term “information architecture” as it applies to application user interface design.
Information Architecture (Web Practice)
In the domain of software development for human engagement, information architecture is the function that provides the conceptual “blueprint” for application user interfaces. This is achieved by defining and maintaining a relation-based model of the concepts, content, and situational factors that influence sustainable human interaction with technology.
When done well, information architecture helps to simplify how people navigate and engage with content that’s presented in application user interfaces or information environment. That means delivering content to users when and how they need it. And doing this effectively requires IA practitioners to produce compelling insight into an explanation of why users need the content.
This holistic (or systemic) perspective uniquely situates information architecture as a vital consideration for a coherent strategy, design ideation, and software development activities.
Information Architecture (Work Product)
As a work product, the “information architecture” of an application user interface or system of interfaces functions as the governing framework for content behavior. It represents the aggregate of assumptions and governing conceptual constructs for assigning properties and attributes to content, and the endowment and evolution of conceptual and content relationships over time for a given context.
Information architecture is often misunderstood as a tangible design artifact like site navigation or labeling with which a user might engage in a user interface. Or, the path that a user might take in order to navigate to desired content and functionality. In actuality, these are only parts of a much larger whole.
The information architecture for an application user interface should be managed as a set of structural definitions (see List 1.0) which correlate to the concept and content constraints of a target environment. IA structural definitions are generally consumed as diagrams and reference models and are shared with team members to help inform activities that involve strategy, interface design, and software development.
List 1.0 – DSIA Structural Definitions that are considered when scoping and managing the information architecture of a given context
- Base (page-level component) model
- Business (Context) model
- Concept model
- Content model
- Controlled vocabulary
- Domain model
- Entity model
- Flow model
- Information model
- Channel mapping
- Mental model