Reuse of Capability Design

The lifecycle of a capability pattern with relations to components of CDD environment is summarized here. Patterns are modelled in Capability Design Tool (CDT) and described by a set of problem, context and solution diagrams. Diagrams are based on the elements from the Capability Meta Model. The designer can also enter a free-form text based version of problem, context, solution and usage guidelines, specify a category name for the pattern. It can be decided whether to document problem, context and solution in form of diagrams and/or free-form text. The patterns created in the CaaS project are available in the CaaS pattern repository (here).


In the Reuse of capability design the following activities can be distinguished:

  • Pattern Elicitation and Elaboration: the first step is pattern elicitation where a list of candidate patterns is created by analysing existing models or creating new ones. The feasibility of each candidate pattern is evaluated by reviewing its usefulness, quality and cost. The list of remaining pattern drafts is then finalized for publishing in Capability Pattern Repository (CPR). Patterns can be published by using a CPR REST web service or by the user interface of CPR (see figure below).


  • Patter browsing: once the patterns are documented thet are available to capability analysis and designers for viewing and inclusion in the capability designs. Screen shot of a pattern in the CPR is below.


  • Pattern Application and Performance Evaluation: after the pattern has been published in CPR it can be used as a building block during creation of capabilities. Patterns discovery is performed by using the user interface of CPR or by its REST web services. When pattern is applied a reference to it is stored in the capability model in CDT keeping track of all patterns being used. To measure performance of a pattern under certain context and keep track of where patterns are currently used the capability is also deployed to the CPR. A scheduled adjustment in CDT is then configured to periodically send performance data to CPR which is used to calculate PPI and for analytical purposes. Based on this data designer can revise the capability design and substitute a pattern with alternative one.