- Details
- Written by: Tim Milbourne
- Hits: 392
An enterprise, organised for a particular purpose, will be more assured of successful delivery if:
- The characteristics and capabilities of its people and resources are understood and applied to their best advantage
- Processes can be broken down into constituent parts and made more efficient
- Problems can be consistently analysed and solutions developed from reusable and composable tools and materials
- Decisions can be made using consistent measurements and evaluation frameworks.
- Details
- Written by: Tim Milbourne
- Hits: 375
Having discussed the sub-domains and domains of our enterprise architecture we can now bring them together in a single depiction shown below.
The enterprise strategy defines the purpose, the measures, and the means for delivering the enterprise architecture:
- Drivers - the purpose of the enterprise, its motivation
- Stakeholders - who is responsible for setting direction/objectives and delivering them?
- Objectives - what changes need to be effected, outcomes achieved, and targets reached when?
- Constraints - what are the restrictions on design, planning and delivery? For example, regulatory, budgetary, structural (manpower, plant, machinery)
- Assumptions - what are we to assume, who has made the assumption, and how are they justified?
- Measures - How do we know when we have delivered? How is success measured?
- Details
- Written by: Tim Milbourne
- Hits: 427
In effect, infrastructure architecture is a type of technical architecture. It describes and designs the way that technology solutions are deployed and connected together. In manufacturing industries this may consist of conveyor belts and logistical solutions that move products and materials between the assembly technicians. In information technology terms, infrastructure is the specialised software that runs the applications and moves data between them. Regardless of these specialisations the aim of infrastructure architecture is to provide a shared environment for deploying, managing, and linking technology solutions together.
- Details
- Written by: Tim Milbourne
- Hits: 424
The technology architecture domain describes the technology capabilities that the enterprise uses to support its functional architecture. The capabilities may be provided by physical machines and tools or software platforms and applications, and the description of these will conform to a technology strategy that incorporates standards and policies. Thus, the technology architecture comprises the following:
- Standards, principles, and definitions
- Application or solution architecture
- Technical capabilities across the various applications/solutions
- Data persistence (repositories)
- Integration (how the applications are used together to support enterprise functions)
- Metrics and measurement (the tools and frameworks used to measure operations and progress towards targets/goals)
- Details
- Written by: Tim Milbourne
- Hits: 311
Data in the broad sense consist of metrics and measures of physical and abstract entities that are important to the business. In developing a data architecture for the enterprise it is common to use a layered structure as follows:
- A set of standards, principles and definitions of concepts, entities and their relationships
- A conceptual model of the data
- A logical model of the entities (including a list of their data attributes) and their relationships
- A physical model for implementing and maintaining the data (technical/solution architecture for data persistence and provision)
- A technical specification of its implementation in systems (database designs/storage and retrieval designs)