Skip Navigation LinksOur-Take-on-Architecture

Our Take on Architecture:

​Keep it Simple!

​Our approach to systems architecture is as simple and straightforward as possible within the constraints of producing a sound, useful and trustworthy results. We absolutely want to avoid large-scale, wall to wall, architectural definition exercises much preferring to keep our efforts focused, contained and time-boxed. Our methodology and toolkit is completely in line with this objective.

​More

"Architecture" vs. "Design"

​In our view, there is “only one architecture” which may be realized by many possible “designs”. In other words, there may be "good" and "bad" designs but only a "right" or "wrong" architecture. You can only create good designs if the architecture is right. We don't mix design pressures with architectural principles.

​​More
​Minimal Methodology

A key design factor in our approach is that extensive methodological training is not needed to start using our methods and tools. We have tailored our approach, methods and tools to fit the requirements of the average architect or business analyst. We don't require "high priests" and have no induction or certification barriers!

​​More
​Rapid Enterprise Architecture with Simple Tool Support

​We offer simple ways of using basic, everyday tools to gather information about the many facets of the organization, to relate these facts to each other and draw conclusions that simplify and clarify the complex decisions that are made in everyday business.

​​More
​Pragmatic Procedures

We only want to build as much of the enterprise architecture as is needed for the immediate problem being addressed. This leads us to the key notion of the “minimum essential model”. We have identified a number of common scenarios that account for a substantial amount of enterprise architecture motivation and effort and provide pre-defined models and procedures to tackle there scenarios 

​​​More
Business Patterns

Patterns are useful in that they describe generic solutions to recurring problems, within a defined context. The basic premise of patterns is that, if something has been done successfully before, don’t “reinvent the wheel.” 

A Business Pattern describes a re-usable approach to the solution of a particular business problem, usually scoped by a business process. It offers a solution based on previous success in defining solutions to the same, or similar, business problems. A business pattern may be described as an 'Architectural template for a business solution'.

We develop Business Patterns. Our Business Pattern for Health and Social Care is in use throughout the world!

​!0 Key Guidelines

​We offer ten key guidelines and recommendations for building your Systems Architecture.