[Inspired] [Prod&Svcs] [People] [Associates] [Contact] [Philosophy] [Reference] [Clients]

Architecture is a term which we intuitively understand when it is used in the context of building or engineering of, say, a bridge. In the context of information systems, computer technology and business, it is less well understood. In this short paper, we hope to clarify what architectures are in this context, what they address, why you might want them and some of the key concepts involved.

The Oxford dictionary defines the following terms:

Architect n One who prepares plans for, and superintends the work of, building; designer of complex structure

Architecture n art or science of building; style of building

These capture the essence of the concept. Architecture is concerned with the high level, conceptual design of some desired end product. We want an architecture for several good reasons. It allows us to:

Ÿ Ensure the pieces fit together
Ÿ Provide a shared vision to implementors
Ÿ Manage multiple concurrent projects towards realisation
Ÿ Identify dependencies - facilitates prioritising
Ÿ Facilitate implementing common infrastructure and reuse
Ÿ Control costs

Conversely, the lack of an architecture can lead to:

Ÿ Lack of reliable data to run the business effectively
Ÿ Non-integrated systems which fail to deliver reliable service
Ÿ Waste of money on duplication of resources
Ÿ Inability to predict and manage the impact of change
Ÿ Omitting key components from the infrastructure or our set of skills which inhibits our ability to capitalise
       on future opportunities

The idea of enterprise information architectures was promoted by John Zachman in the late 1970's and has evolved rapidly. With the rapid spread of I.T. into every facet of organizations, the increased dependence upon systems, explosion in variety and sophistication of technology and the need for integration of all of these to meet business pressures, architectures have become essential to organizations.

They form a vital link between the visions or concepts which we pursue, and the planning and infrastructure to ensure that they are realised. Furthermore, carefully executed and using industry and international standards, they can allow us to take advantage of components and functionality created elsewhere, making our response to the market quicker and more cost effective. Compatibility also allows us to link our systems to those of our business partners in extended value chains to offer customers even better value - thus generating competitive advantage for our organization.

The Inspired architecture framework has four major interrelated components. These cover the Business Architecture, the Applications (systems) Architecture, the Information (Data) Architecture and the Technology (Hardware and Software) Architectures respectively.

The Business Architecture details the structure of the business in relation to customers, markets, channels, partners and suppliers. Products and services offered are included with relevance to their ascendance or declining proportion of the revenue stream. Internal factors such as resources (cash, assets, personnel and skills), business processes and intellectual capital (patents, designs, copyright, brand etc.) form part of the picture. The business architecture will have implications for the required information to manage the enterprise and the necessary systems to support its proper functioning.

The Information Architecture seeks to provide the business with the necessary information to support operations and decision making in an integrated and reliable way. It also helps us to understand changing types of information (for example the move to multimedia and video) as well as changes in how we acquire information. The transition from paper based or manual systems to online information is facilitated.

The Applications Architecture provides a map of the systems required to support the business and their interrelationships. For example, a billing system might feed off data from a network monitoring system, while the billing system itself might provide input for profitability analysis by product in a decision support tool. The information is mapped to the other architectures so that we have a picture of which applications use which data and where this is located as well as what technology is employed.

The Technical Architecture allows us to plan and build the infrastructure to support the diverse platforms, systems, databases and I.T. development capabilities that we need. It ensures that the components selected are compatible and that changes in technology are incorporated in a non-disruptive and advantageous way. It details computers (PCs, Unix machines, mainframes), network components (hubs, switches, routers, links etc.) and all of the system software required to make good use of and manage the environment.

It also includes database management, system development tools, middleware (software to tie disparate technologies and systems together) and system management tools (e.g. monitoring, fault diagnosis, work flow).

It is proposed that organizations adopt an architecture approach to link the strategies conceived in business planning to the existing infrastructure in the business and to manage the transition of the current situation to the desired future.

We caution that architectures are no "silver bullet". They will not immediately solve existing problems. They can help us understand them and the necessary activities which will be necessary to resolve them as well as to avoid future difficulties. Adopting the approach will, however, require commitment and concerted effort over a period of time.

Architecture management can be greatly facilitated by the use of suitable knowledge mangement tools and controlled but widely available repository. View details of our tool supporting architecture management - Archi.