ECM Decomposition

Showing results for 
Search instead for 
Did you mean: 

ECM Decomposition

0 0 1,423

Obsolete Pages{{Obsolete}}

The official documentation is at:

Looking for a challenge? Get involved in this project.

The goal of this poster which a work in progress is to functionally break down ECM into a descriptive framework.  This enables us to examine the space and the overlap in many of the areas.  Because ECM is such a large space it is difficult to think about it all at once. Its possible if we choose the right granularity or find a way to express finer level of granularity in ways that can be ignore.


You’ll note that description spans from left to right.  Granularity runs from top to bottom (it’s a tree, child nodes give detail).  Dark blue nodes can are constructs which can be found as trunks where they are define and a children where they apply. Light blue nodes are the services that make up ECM. Services are provided by composing constructs.  The orange node give details, the green nodes express a relationship that contains detail.

This mapping is by far incomplete.  The task at hand is a challenging and your help is requested.

I hope to keep domain specific information out of this document in order to make it useful to the largest section of users.  It would be nice to create domain specific renditions once we get the generalized form closer to completion.


Content Services are based on John Newton's blog entry


  • Russ Danner - bulk of the inital document
  • Jon Cox - several suggestions (Jon should I post these in the discussion area?)