Separation of concerns
Statement
Separation of concerns ensures that the responsibilities and capabilities of a digital solution or service are organised into distinct architectural building blocks with clear and well-defined scopes.
Identifier |
|
|---|---|
Category |
|
Interoperability layers |
|
Governance model |
|
Influence on DPS lifecycle |
|
Influence on DPS attributes |
|
Scope |
Business agnostic |
ELAP release |
4.0.0 |
Rationale
Separating concerns reduces architectural complexity by ensuring that each building block addresses a coherent set of responsibilities and capabilities. Clear boundaries help prevent unrelated or duplicated functionality from being distributed across multiple parts of a solution and make the architecture easier to understand, govern and maintain.
Separation of Concerns supports modular solution design by allowing individual architectural elements to be designed, developed, tested and maintained according to their specific responsibilities. It also improves accountability by making it clearer which components or organisational actors are responsible for particular capabilities.
Clear separation of responsibilities provides the architectural foundation for managing dependencies between building blocks. In this sense, Separation of Concerns complements Loose Coupling: Separation of Concerns establishes appropriate boundaries, while Loose Coupling ensures that dependencies across those boundaries are minimised and appropriately managed.
Implications
Digital solutions and public services should be decomposed into architectural building blocks with clearly defined responsibilities, capabilities and boundaries. Each building block should address a coherent set of concerns, and unnecessary duplication or overlap of responsibilities between building blocks should be avoided.
The responsibilities and interfaces of architectural building blocks should be explicitly defined and documented so that their role within the overall architecture can be clearly understood and governed.
The separation of concerns should be maintained throughout the lifecycle of the solution. Changes and extensions should respect established responsibility boundaries and avoid introducing functionality into components where it does not logically belong.
Separation should be applied at the appropriate architectural levels, including organisational processes, information and data responsibilities, applications, services and technical components, according to the nature and complexity of the digital public service.
Source
Applying the principle of separation of concerns in software development
In the source, an article, the principle is revised. The principle of separation of concerns finds application to a number of aspects of software development, some well-known, such as de-coupling modules, some less well-known, such as organising case analyses. Three example applications of the principle of separation of concerns are presented, with the aim of helping the reader to apply the principle better and to find new situations in which the principle can be applied.