How detailed should architecture documentation be? Architecture documentation should contain enough information to support decision-making, governance and delivery. Too little documentation creates ambiguity. Too much…
Which Tools Can Be Used to Document Enterprise Architecture? Enterprise Architecture can be documented using a combination of EA modelling tools, diagramming platforms, repositories and…
How should architecture documentation be maintained? Architecture documentation should have clear ownership. Important architecture information should be reviewed when significant business, technology or organisational changes…
What are architecture principles? Architecture principles are high-level rules that guide decisions. Examples include: Cloud-first: New services should use cloud where appropriate unless there is…
What is a reference architecture? A reference architecture is a reusable model or blueprint for addressing a particular type of architectural problem. For example, an…
What is a transition architecture? Large transformations rarely happen in one step. A transition architecture describes an intermediate state between the current and target environments.…
What is a target-state architecture? A target-state architecture describes the desired future environment. It represents what the organisation is trying to achieve and provides a…
What is a current-state architecture? A current-state architecture describes how the organisation operates today. It may include business capabilities, processes, applications, data, technology and integrations.…
What Deliverables Should an Enterprise Architecture Function Produce? An effective Enterprise Architecture (EA) function should produce practical decision-support artefacts, not documentation for its own sake.…
