Introduction
...
Alternatively one could choose to approach a capability from the architectural unification approach POLDAT
- Process (business processes)
- Organisation (structures)
- Location (Geographical information)
- Data (models, life cycles, security etc)
- Application (software, security, interoperability etc)
- Technology (infrastructure)
Both TEPIDOIL and POLDAT pay no attention to organisation unit boundaries (business unit, sector, service, function etc) but weave a path through organisation units, selecting those areas within those units that, deliver the characteristics needed by the capabilities.
More often than not, a goal is delivered through multiple capabilities
Defining a capability is an extensive task but once done can lead to a major simplification in the overall understanding and modelling of a problem domain. Consider the following example, you you want to build a home from scratch, core required capabilities
...