Can anyone give a quick overview of a context diagram. Is it the same as a Data Flow Diagram?
When are the best times to use it? (ie what is it good for?)
Thanks
Craig,
The Context Diagram is and is not the same as the Data Flow Diagram. It is the same regarding the look and feel, and it is not the same in everything else.
After the context diagram has been agreed upon, you may start with the Data Flow Diagram. You take a single process from the Context Diagram and decompose it in a Data Flow Diagram.
Both Context and Data Flow Diagrams are part of the structured analysis approach.
If you work with Use Cases you may replace the Context Diagram with the Use Case Model of the system and the Data Flow Diagram with a Sequence Diagram.
-Vessela
A context diagram is a data flow diagram with just one function.
Tony
I often use two types of context diagrams: one to document the work scope in the beginning of the project and another to document the product scope of the system to be developed. The work scope context diagram looks at the business process as a single black box with its interactions with outside entities. It acts as a communication tool that allows everyone invovled to agree on the work that is being looked at for the new system. The product scope context diagram is more focused on the system to be developed. It treats the system as a black box and shows the inputs and outputs to and from external entities. Both are similar, but after doing some initial analysis, it may be determined that the product scope is smaller than the work scope.
here is a presentation pack on how to deliver data flow diagrams (and some other stuff)
brought to you by enabling practitioners & organizations to achieve their goals using: