From Value Streams and Capability Maps to Protocol Models and Back

Value Streams with supporting Capability Maps are a popular trend in modern enterprise architecture design. However, the existing definition of a capability as a collection of selected functionality is imprecise and often results in unmanageable capabilities and capability maps. Conceptual and process models, which are traditionally used to select functionality for system modules are considered too detailed at the strategic level, where capabilities are represented. This paper defines requirements and constraints for manageable capabilities and capability maps. The paper also proposes a method for the design of manageable capabilities and capability maps. This method employs the definition of requirements and constraints, as well as protocol modeling, to achieve this goal. Protocol models of capabilities are defined at the level of business objects and functionality chunks. The composition technique inherent to protocol modeling allows for the seamless movement of business objects and functional chunks between capabilities, thus facilitating the design of a manageable capability map. Furthermore, all protocol models of capabilities and capability maps can be simulated. The simulation process enables the identification of unmanageable and missing capabilities within a capability map. The proposed method can be employed as a reference for the design of manageable capability maps.