Architecture

• Business architecture:

The structure and behaviour of a business system (not necessarily related to computers). Covers business goals, business functions or capabilities, business processes and roles etc. Business functions and business processes are often mapped to the applications and data they need.

1. business goals
2. business functions or capabilities
3. business processes and roles

• Data architecture:

The data structures used by a business and/or its applications. Descriptions of data in storage and data in motion. Descriptions of data stores, data groups and data items. Mappings of those data artifacts to data qualities, applications, locations etc.

1. data in storage and in motion
2. data stores, data groups and data items
3. data qualities, applications, locations

• Applications architecture:

The structure and behaviour of applications used in a business, focused on how they interact with each other and with users. Focused on the data consumed and produced by applications rather than their internal structure. In application portfolio management, the applications are usually mapped to business functions and to application platform technologies.
Application (or Component) architecture: The internal structure, the modularisation of software, within an application. This is software architecture at the lowest level of granularity. It is usually below the level of modularisation that solution architects define. However, there is no rigid dividing line.

1. structure and behavior of applications used in a business
2. how they interact with each other and with users
3. the data consumed and produced by applications

Technology architecture/Technical architecture or infrastructure architecture:

The structure and behaviour of the IT infrastructure. Covers the client and server nodes of the hardware configuration, the infrastructure applications that run on them, the infrastructure services they offer to applications, the protocols and networks that connect applications and nodes.