| Content Levels | |
| Register for free access to papers, case studies, and over 50 templates. | |
| Subscribe for complete access: $14.95 monthly or $149/year | |
| Risk-free 15-day trial!
Compare levels View sample templates Corporate subscriptions | |
Quick Summary
Context diagrams are a time-tested method for using simple symbols to illustrate a system's boundaries, benefits, interactions, and data flows. Simple sketches can aid discussions of project features and scope, and detailed graphical interface specifications can improve communication and understanding with non-technical stakeholders.
What this is
Context diagrams graphically depict a system's boundaries, the information that flows in and out of the system, and the other systems and people that will use it and benefit from it. Representing the system as a single “black box” process interacting with its environment, context diagrams provide a picture of project scope.
Context diagrams can be very simple sketches or detailed graphical interface specifications, depending on what you need for a given communication or interaction.
Why it's useful
Any system exists in order to respond and provide services to the world around it. The context model describes how the system relates to its business environment. It depicts the boundary, scope, and benefits of the system in a simple, intuitive format that non-technical stakeholders can easily understand.
Context diagrams provide several additional benefits:
How to use it
Read the guideline for detailed discussions of how to use a context diagram appropriately, and step-by-step instructions for developing one. Use an appropriate level of detail for the circumstances. In a quick conversation with a stakeholder, show only those details relevant to your discussion. When creating a comprehensive specification to begin your system analysis, be sure to include all the details you can think of and use a rigorous naming convention. Be sparing with additional notations; don't muddy up the concepts by adding too many objects or using fancy clip art.
Alan Zimmerman's 35-year career has included hardware and software engineering, system analysis and business planning, project and functional management, technical writing, and training development and delivery. And, along the way, he's thrown in a little rock-and-roll disk jockey and improvisational comedy here and there. His research interests include the on-going maturation of the software engineering profession and the intersection of business and software development processes. As owner of Pragmatic Design Studio, he is using agile methods and web technologies to solve problems in traditionally under-served markets.
©Copyright 2000-2010 Emprend, Inc. All Rights Reserved.
About us Site Map View current sponsorship opportunities (PDF)
Contact us for more information or e-mail info@projectconnections.com
Terms of Service and Privacy Policy