What is Context Diagram in Project? How is it useful in project? Saving Changes...
Sort By:
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
Context diagram is about solution and mainly product/service/result to be created not to project. Can you use it for project? Of course, as any other type of tool. But will not help you too much. Saving Changes...
A context diagram should come into play during requirements. You don't need one for every project, but it is an early step to identify actors, systems, and inputs/outputs between actors and systems. Once you create a "big picture" of these interactions, you can identify which systems, data, and processes are in scope for the project. Saving Changes...
A Context Diagram is a scope model used in Collect Requirements process of Project Scope Management. It illustrates the product scope by showing inputs from internal users into Project System (processes, equipment, computers system, etc), how it relates and interacts with internal as well as external users. Arrows indicate relationship between the inputs into the system, and outputs to users. Saving Changes...
There are many different views you can create of a project/system to help describe what it is. The high level description system of interest is known as the system architecture. This includes what it is, the requirements, how it's used, how the pieces function. etc.
One of the common views in an architeture is how the end product is intended to operate, to put that system into context. To give you an example, look up "OV-1 diagram". That is an operational view from the US Govt. DODAF (Dept. of Defense Architectural Framework), and provides context as to how the product you are project managing, will be used by the purchasing customer. This helps tell the story of what they system/project does, how operators interact with it, how it interacts with the environment in which it is used, etc. Saving Changes...
Community Champion
