Enterprise Framework - Holistic Enterprise Design

The Enterprise Framework is a tool for managing the elements of enterprise development. It can be implemented in any appropriate content management tool *) that is used in the organisation. The framework is agnostic to visualisation languages and notations by default.

*) Content management tools used in the organisation can be e.g. Atlassian Confluence (combining text, tables, and figures), an EA-tool such as QualiWare or BlueDolphin from ValueBlue – with which it is possible to use different languages that complete each other (such as EDGY, ArchiMate, BPMN).

The purpose of the Enterprise Framework is to:

Serve as the landing page of all the content that covering the behavior and structure of the enterprise.
Provide a conceptual content model for enterprise development across all involved disciplines (e.g., business owners, designers, architects, and developers).
Maintain all design and development descriptions and models in a centralised, easily accessible location.
Maintain an inventory and track all enterprise elements relevant to understanding the enterprise.

This version is a template that can be adapted (adjusted & tuned) to fit the specific needs and context of the enterprise.

This framework can be used as a ‘landing page‘ in a content management tool. For example, in the Confluence, this framework can represent the main page, the cover page into all the content in all the sub-pages in the organisation. The elements in the ‘house’ can be links to sub-pages with specific content such as text, tables and figures. The figures can be made with an appropriate tool such as Draw.io. (Examples using the Draw.io with EDGY here: link).

The contents of the framework:

Navigation in the ‘House’. The ‘House’ elements support a drill-down effect: selecting an element opens a dedicated sub-page or figure for more granular detail. Each sub-page can act as a directory for related content, such as system landscapes or interaction diagrams. Alternatively, the link can open a specific diagram, such as a stakeholder map. However, the core idea is that each element on the ‘landing page’ acts as a link to a specific sub-page. These sub-pages can contain text, tables, and figures, or provide further links to deeper sub-pages related to the topic.

In this form, the ‘House’ model serves as the Enterprise Architecture framework, which can be implemented using an appropriate modeling tool or the enterprise’s existing content management system.

Yet Another Framework (YAF), yes, but a simplistic and minimal one that can be used for various purposes, modified and applied to fit for purpose – whatever is appropriate in the case.

The Enterprise Framework is lightweight: it is easy to understand and use, simple enough to start with, modular, and quick to adopt and iterate.

Why Enterprise Framework? For:

Flexibility: Works for any domain or scale.
Clarity: Focuses on what matters.
Collaboration: Simple enough for everyone to use – for multipurpose and multidisciplinary use.

Enterprise Framework is lightweight, flexible and collaborative.

Principles: designed to be simple, modular, adaptable and purpose-driven.

Simple: Contains only what’s necessary, what is typical and common for enterprises.
Modular: Components (elements) of the framework can be added, removed, or replaced – as needed.
Adaptable: Fit for purpose, use those components and elements that are relevant in the context.
Purpose-driven: Always ask “why” before “how” or “what” when adding things.

Best practices:

Visual notation:
- Use what is common to most of the people involved in the enterprise development.
- Use a simple, shared notation to communicate with all the disciplines and stakeholders.
  - E.g.
    - Boxes for entities (organisations, applications, data elements etc.)
    - Arrowed lines for relationships or flows (e.g., value, information, dependencies).
    - Straight lines for associations between elements (such as entities)
    - with connection lines (straight lines or arrowed lines)

Anti-patterns (what not to do):

Overcomplicate: If it feels heavy, you’re doing it wrong. Adapt to the situation, don’t force-fit.
Set in Stone: Frameworks should adapt and evolve with needs.
Jargon Overload: Keep it understandable for all stakeholders.

The Enterprise Wheel can be used to support enterprise development. For more details, see Enterprise Wheel.

The elements of enterprise cover all the aspects of enterprise development.

See Enterprise Elements for more details.

The Enterprise Framework is the next evolutionary step from the so-called Lean EA framework that integrates the enterprise architecture discipline into the overall development work in an organisation. The Lean EA framework is introduced here:

Lean Enterprise Architecture Method for Value Chain Based Development in Public Sector
- Research Gate: link

Summary

The Framework represents the behavior and structure of the enterprise

The Enterprise Framework is a holistic tool for visualising and governing an enterprise’s behavior and structure.

Represented as a ‘House‘ model, it serves as a bridge between high-level strategy and everyday operations and development activities.

By providing a shared conceptual model, it ensures that all disciplines – from business owners and service designers to architects and developers – speak the same language and use the same content repository of enterprise elements.

Key Concepts

The ‘House‘ as a Navigation Hub.
- The core of the framework is a visual “landing page” (the House). This model organises the enterprise into logical layers, typically moving from the “Why” (Strategy) down to the “How” (Technology).
- Roof (‘Management’):
  - Strategy, Vision, and Identity.
- Middle Floors (‘Operations’, the ‘foundation’):
  - Customer Experience View: journeys, channels, offerings
  - Operations and Architectural View: Processes, data, applications, technologies.
  - Organisation and Business Actor View: organisation structures, roles, stakeholders.
- Bottom layer (‘Development’).
  - The bottom layer focuses on the change and innovation of the operations. It describes how the enterprise evolves and builds new capabilities.
  - Content: Development programs, projects, architecture principles, and the “Systems of Innovation” or new technology pilots.
  - Purpose: To ensure the continuous improvement and future-proofing of the enterprise
The Drill-Down Effect.
- The framework is designed for layered navigation. A user can start at the high-level House view and “drill down” by clicking on specific elements. This leads to:
  - Detailed sub-pages: Containing text, tables, and specific descriptions.
  - Visual diagrams: Such as stakeholder maps, system interaction diagrams, or process models.
Tool-Agnostic Implementation.
- The framework is not tied to a specific software platform. It can be implemented in:
  - Modeling tools: (e.g. QualiWare, BlueDolphin from ValueBlue or Sparx EA) for deep architectural analysis.
  - Content Management Systems (CMS): (e.g. Atlassian Confluence) for wide organisational accessibility and collaboration.
- The framework is also notation-agnostic, meaning it does not restrict the user to a single modeling language. Instead, it allows for the use of the most appropriate notation for each purpose.
  - It supports a multi-layered approach where different modeling languages complement each other based on the level of abstraction. High-level strategic designs and conceptual models are often best represented with EDGY, whereas detailed process flows and system architectures can be further refined using specialised notations like BPMN, ArchiMate, or UML.
  - Ideally, the framework enables the interoperability of different languages: for instance, high-level concepts and sketches can be created using EDGY, while more technical or granular details can be documented using BPMN, ArchiMate, or UML as needed.

Modern versions of the framework can incorporate the EDGY language, which balances three critical facets:

Identity: What the enterprise is (Purpose, Mission, Vision, Goals, Brand).
Experience: How the enterprise is perceived (Customer/Employee journey).
Architecture: How the enterprise is operating (Processes, data, applications, technologies).

Conclusion

Ultimately, the Enterprise Framework is a living repository. It prevents organisational silos by keeping all design and development descriptions in one findable location, ensuring that any change – whether a new regulation, a service, or an application update – is understood within the context of the whole enterprise.

The Enterprise Framework serves as the foundation for an Enterprise Digital Twin, providing a virtual representation of the enterprise’s behavior and structure. It acts as a centralised source of truth, supporting both strategic decision-making and continuous enterprise development.