Introduction
...
Alternatively one could choose to define 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)
...
Our next task is to try and illustrate this weaving nature that we have described above? One approach that we are currently trying is to map the thread through a UML activity model. We use swimlanes to provide a visual way of representing organisational units and other sub units.
This model captures the weaving nature through our first example of one capability to deliver a goal |  |
|---|
In this example we show multiple capability paths delivering a goal |  |
|---|
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
...