Business Change Method

Security Architecture Framework

Project Architects' Toolkit

Data Management Architecture

Data Management Infrastructure

Enterprise Architecture has grown in prominence and stature as a key enabler to organisations’ success.  gEAM is a holistic approach to overcoming the challenges of defining and delivering architecture throughout an organisation as well as aligning business and IT through formalisation of how different organisational and architectural constructs inter-relate.  gEAM is not a proprietary architecture method; it incorporates features of other frameworks but is more prescriptive to improve consistently and repeatability.  gEAM can be mapped onto TOGAF 8.1 relatively easily although gEAM’s scope is broader.

The glue: EA Methodology (gEAM) is an integrated set of practical, industry based, best-practice standards and guidelines for the development of an organisation’s EA.

glue: Enterprise Architecture Methodology

The methodology is open and flexible having been evolved from the best frameworks and methods available in the market place. It consists of:

• Product Based Planning Standards - which define the structure of an EA development project in the form of specific activities, with clear dependencies between them and tangible outputs.
• Technique guides - which provide consultants with a set of proven usable techniques, notations, defined rules and guidelines on when and how to use them.
• Product Descriptions - defining the means of recording the products of the development activities at a detailed level.

gEAM’s scope is broader than most other Enterprise Architecture frameworks as it covers both the traditional Enterprise Architecture methodology scope as well as organisation and environment aspects of performing Enterprise Architecture.

glue:’s EA Methodology can accept bottom-up input into it as well as top-down where necessary.  This allows the very realistic physical constraints an organisation may operate under to be considered for both current-state and future-state modeling.

glue:’s Enterprise Architecture Methodology

glue:’s EA Reference Model

glue: works to an EA Reference Model containing a number of sub-architectures.
The method we use creates, in phases, the sub-architectures of this model at various points in time – ‘As-Is’ (current state) and ‘To-Be’ (future state, e.g. 2, 3, 5 years).

From a business perspective, detailed current state models allow stakeholders within the business to clearly see which processes, data, functionality and physical assets are required to run and support the business today. These are created to a level of detail that clearly identifies where these cross business boundaries.

Future state models allow business stakeholders to understand the impact of changes to the business; this may include the impact on processes, the location of enterprise data, the requirements for business functionality within applications and physical IT assets such as servers, networks, storage etc.

Maturity/ Capability Model