Site Feed

Sunday, April 02, 2006

Context Modeling

As far as Modeling techniques go, I am finding Context Modeling to be one of my favorites. Instead of boring you with the details, the Model provides a graphical summary view of a process, a system, a role - I like to use it in many ways.

Here is an example I found during a Google Image Search (GIS):

Context Diagram of a Personal Sound System

I prefer this one because it has all the red-shaded boxes in the center enclosed by a larged blue-shaded box. I prefer Context Diagrams that show, visually, what pieces are part of an enclosed system, such as all of the red-shaded boxes over Context Diagrams that do not.

If I were process modeling, I would have four parts. To the left would be the Inputs. Inputs could include people, documents, triggers, anything that will initiate the process. The center will be the process as the large box, and all the steps of the process as small boxes enclosed therein. On the right will be the Outputs. This could be documents, results, triggers for another process, people, I have a lot of levity with this. On the bottom will be a brief summary of the systems used, (but not a long detail on how and when to use them.) It is a good overview. It helps a user new to the process to visually see and map it out. Think of the Context Diagram as an Outline. After the outline is complete, you fill in the details.

0 Comments:

Post a Comment

<< Home