Capability Modeling Guidelines: How to Structure a Capability Map: Revision history

Diff selection: Mark the radio buttons of the revisions to compare and hit enter or the button at the bottom.
Legend: (cur) = difference with latest revision, (prev) = difference with preceding revision, m = minor edit.

curprev 14:3914:39, 13 September 2025‎ Stephan2 talk contribs‎ 4,303 bytes +49‎ No edit summary
curprev 13:4813:48, 13 September 2025‎ Stephan2 talk contribs‎ 4,254 bytes +203‎ No edit summary

curprev 08:0508:05, 11 September 2025‎ Stephan2 talk contribs‎ 4,051 bytes −35‎ No edit summary

curprev 08:4008:40, 10 September 2025‎ Stephan2 talk contribs‎ 4,086 bytes +29‎ No edit summary

curprev 09:5609:56, 2 September 2025‎ Stephan2 talk contribs‎ 4,057 bytes 0‎ No edit summary
curprev 09:1209:12, 2 September 2025‎ Stephan2 talk contribs‎ 4,057 bytes −159‎ No edit summary
curprev 09:0209:02, 2 September 2025‎ Stephan2 talk contribs‎ 4,216 bytes −4‎ No edit summary
curprev 09:0209:02, 2 September 2025‎ Stephan2 talk contribs‎ 4,220 bytes +5‎ No edit summary

curprev 15:5715:57, 1 September 2025‎ Stephan2 talk contribs‎ 4,215 bytes +51‎ No edit summary

curprev 15:5015:50, 1 September 2025‎ Stephan2 talk contribs‎ 4,164 bytes +4,164‎ Created page with "=How to structure a Capability Map= A Capability Map is a two-dimensional, one-page, high-level representation of the architecture of the enterprise. It provides an overview of the enterprise's architecture (what Capabilities it needs to operate) and can represent the as-is state or to-be states related to particular design challenges. The one-page view provides a widely-agreed, complete overview of the Capability|Capabilitie..."

13 September 2025

11 September 2025

10 September 2025

2 September 2025

1 September 2025