The basic primary components required by an organisation setting out to implement EA are:

• A knowledge structure or metamodel to ensure that everything that anyone needs to know about EA can be recognised and cross-referenced effectively. As with any good data model, this should also minimise the chance of duplicate, redundant or erroneous knowledge being included in the knowledgebase

• A knowledgebase or repository (often but not always based on some proprietary tool), in which to store, syntactically control and publish the knowledge

• A framework, detailing how to organise the knowledge for various purposes, how to evolve it over time, and the impact it has on various stakeholders within the organisation

• A methodology, prescribing how the EA knowledge is captured, maintained, semantically controlled and used by all relevant parties, and across time.

Thes components are all inter-dependent in terms of structure and usage, but may be considered to be centred on a formal knowledge structure or metamodel.

In addition, no EA capability will be successful without taking account of supporting considerations:

• Well-trained staff (in areas relevant to EA)

• Senior management commitment

• Understanding of the organisational maturity with regards to EA

• Establishment of a culture sympathetic to change in the organisation