Defining System Boundaries with Context Diagrams, Step by Step

UPI Study › Courses › System Analysis and Design › Free lessons › Lesson 4.2 Free with a free account

Defining System Boundaries with Context Diagrams

System Analysis and Design · Chapter 4: Requirements Validation, Modeling, and UMLSection 4.2 · lesson 25 of 698 min · free with a free account

← Validation in Practice: Prototyping, Surveys, Document Reviews, and User AnalysisNext lesson: UML Models Unpacked: Design Patterns and Practical Cases →

Earn 3 college credits for System Analysis and DesignRecommended for credit by NCCRS · Computer Science 390 · self-paced · one payment, lifetime access
Enroll in System Analysis and Design · $250 →Download the syllabus (PDF)

In this lesson

One process, the entities around it, and everything that crosses the line.

  • Explain what a context diagram shows, and why scope comes first
  • Identify external entities, outside the system boundary
  • Explain the single-process view of the system
  • Label data flows correctly and apply the drawing rules

Transcript

Everything said in the video, section by section (1,162 words). Read along, or search it.

Requirements Validation, Modeling, and UML

Defining System Boundaries with Context Diagrams

This chapter moves from gathering requirements to modeling them. And the first model an analyst draws answers the most basic question of all. Where does the system start, and where does it stop? The tool for that is the context diagram. We will look at what it shows, the rules for drawing it, and a complete worked example.

Scope First

Where Does the System Start and Stop?

Before a system can be modeled in any detail, everyone involved needs to agree on its boundary. A context diagram settles that question. It is the highest-level data flow diagram. It shows the entire system as a single unit, along with everything outside it that it exchanges information with. Getting the boundary right matters more than it might first appear. Draw it too broadly, and the project takes on work that was never really its responsibility. Draw it too narrowly, and important interactions get missed, and surface later as expensive surprises. A context diagram forces that decision into the open, early. It is a picture stakeholders can react to, and agree on, before any internal detail is designed. It is much easier to spot a missing interaction in a picture than in pages of text.

Outside the Line

External Entities

Around the outside of a context diagram sit the external entities. An external entity is a person, organization, or other system that sends information into the system, or receives information from it. But it sits outside the system's boundary, and outside the system's control. External entities generally fall into a few familiar categories. A role or type of person, like a student or a customer. An organization or department, like a registrar's office, or a supplier. Or another system entirely, like a payment processor, or an external database. What they all have in common is this. The system cannot dictate how they behave. It can only send them data, and receive data from them. That is the test to apply. If the system controls it, it belongs inside the boundary. If not, it is an external entity.

The Whole System as One Shape

The Single-Process View

Now the system itself. A context diagram deliberately shows the entire system as one process, usually labeled zero. There are no internal processes, and no data stores, drawn inside it. That is not an accidental oversimplification. It is the whole point of the diagram. By collapsing everything the system does into a single shape, the diagram keeps attention on the boundary itself. What crosses in, and what crosses out. The internal detail is not lost. It is saved for later. Once the boundary and the entities around it are agreed, process zero becomes the starting point. More detailed diagrams then break it down into the system's actual internal processes and data stores.

What Crosses the Line

Data Flows

The lines connecting entities to the system are data flows. A data flow is a labeled arrow representing a specific piece of information, moving between an external entity and the system. Each flow is named with a noun or noun phrase, describing the data itself. Enrollment confirmation, not confirm enrollment. The flow represents data, not an action. And a single arrow only ever runs in one direction. If information moves both ways, say a request going out and a response coming back, that is two separate labeled arrows. Never one double-headed arrow. A request and its response are two distinct pieces of data. Drawing them separately also forces you to name both, which often reveals a response nobody had thought about.

The Rules

6 Drawing Rules

Put together, context diagrams follow six drawing rules. Single process only. The entire system is one process, numbered zero, with no internal processes. No data stores. Those belong to more detailed diagrams. Entity to process only. Every data flow connects the process to an entity. Entities are never connected directly to each other. One direction per arrow. A two-way exchange is drawn as two separate arrows. Noun-phrase labels. Every flow is labeled with the data it carries, not the action that produces it. And one diagram, whole scope. The context diagram captures the system's entire scope, in a single view, with no internal detail.

Figure 4.1

A Course Registration System

Here is a worked example, a course registration system. The system itself is the single process at the center, process zero. Four external entities surround it. A student, an instructor, the registrar's office, and a payment gateway. Each entity is connected by two data flows, one running in, and one running out. That makes eight flows in total, every one of them crossing the system boundary. Notice what is missing. There are no lines between the entities themselves. The diagram says nothing about how registration works inside. Only what enters, and what leaves.

Reading Figure 4.1

8 Flows Across the Boundary

Let's read the flows, entity by entity. The student sends course selections into the system, the courses they choose to register for. And receives an enrollment confirmation back, confirming the registration was completed. The instructor sends final grades in, at the end of a term. And receives the class roster, the current list of students enrolled in their class. The registrar's office sends catalog updates, new or changed course information. And receives enrollment records, the official enrollment data it keeps on file. The payment gateway receives a payment request, a request to charge the student for registration. And sends back a payment confirmation, confirming the payment was processed successfully. Every label is a noun phrase, and every arrow runs one way. Notice also that the payment gateway is another system, not a person. External entities do not have to be human.

What Is Not Drawn

No Entity-to-Entity Flows

Notice one more thing about the example. Every flow connects an entity to process zero. None of the four entities connect to one another directly. That is true even though a payment confirmation and an enrollment record might, in reality, end up related. If that relationship matters, it belongs inside the system, in a more detailed diagram. It does not belong on the context diagram. The context diagram has exactly one job. To show what crosses the system's own boundary.

Key Terms

The Vocabulary of This Section

Let's lock in the key terms. A context diagram is the highest-level data flow diagram, showing the whole system as one process, with its external entities. The system boundary is the line between what the system does, and what lies outside it. An external entity is a person, organization, or system that exchanges data with the system, but sits outside its control. Process zero is the single shape representing the entire system. And a data flow is a labeled, one-direction arrow, naming the data that crosses the boundary.

Key Takeaways

What to Carry Forward

To pull this together. A context diagram is the highest-level data flow diagram. It shows scope and boundary, before any internal detail is modeled. External entities send data into the system, or receive data from it, but are outside its control. The system is shown as a single process, usually numbered zero, with no internal processes or data stores. Data flows are labeled with nouns, run in one direction only, and always connect an entity to the process. And a good context diagram captures the system's entire scope, in a single, uncluttered view.

About System Analysis and Design at UPI Study

System Analysis and Design (Computer Science 390) is a self-paced online course of 69 video lessons in 9 chapters, from the analyst's role and requirements to UML modeling, interface and database design, testing, maintenance and project management. It carries a NCCRS credit recommendation for 3 semester credits.

Every lesson transcript is free on pages like this one, and the videos are free with a free UPI Study account. Enrolling adds a practice quiz after each lesson, the graded work and final exam that earn the credit, lifetime access, and an official transcript on completion. UPI Study has helped over 130,000 students with college credits. ACE and NCCRS have over 2,100 cooperating colleges that will consider accepting credits; the final decision is with the universities.

Enroll now → Course details Download the syllabus All Computer Science courses Every course with PRO →

Compare: Software Engineering vs Systems Analysis

Why take it here

Why students take System Analysis and Design with UPI Study

From business problem to working systemSystem Analysis and Design teaches how analysts study a business need and turn it into a system design: requirements, UML and data-flow models, interface and database design, implementation and project management. It is a core course in information systems and IT degrees.
Credit at a fraction of the priceThe same 3 credits can cost $750 or more at a US college. Here it is one payment, self-paced, with lifetime access.
Finish your degree soonerTransfer credits reduce the courses you still owe, so you can graduate earlier or lighten a heavy semester.
Strengthen an applicationA completed college-level course on an official transcript shows admissions and scholarship committees you can do the work.
Study on your own scheduleNo start dates, no deadlines. Watch the lessons, practice, and take the final when you are ready.
130,000+students helped with college creditsACE and NCCRS have over 2,100 cooperating colleges that will consider accepting credits; the final decision is with the universities.

Where the credit goes

Universities that work with NCCRS

System Analysis and Design carries a NCCRS credit recommendation. These universities work with NCCRS; some are UPI Study's signed partners. ACE and NCCRS have over 2,100 cooperating colleges that will consider accepting credits; the final decision is with the universities.

Thomas Edison State UniversityThomas Edison State UniversitySigned partnerUniversity of the PeopleUniversity of the PeopleSigned partnerCharter Oak State CollegeCharter Oak State CollegeSigned partnerStrayer UniversityStrayer UniversitySigned partnerColumbia Southern UniversityColumbia Southern UniversitySigned partnerIndiana TechIndiana TechSigned partnerPenn StatePenn StateWorks with NCCRSSouthern New Hampshire UniversitySouthern New Hampshire UniversityWorks with NCCRSSUNYSUNYWorks with NCCRS +many more cooperating universitiesFind my college →

Find my college → Not listed? Ask Athena in the corner of this page, or book a 15-minute call.

FAQ

Questions students ask us

About Defining System Boundaries with Context Diagrams

What is a context diagram in systems analysis?
A context diagram is the highest-level data flow diagram, showing the entire system as a single process along with the external entities it exchanges information with. Its job is to define the system's scope and boundary before any internal detail is modeled. Because it is a simple picture, stakeholders can react to it and agree on what is inside and outside the system early in the project.
What is an external entity in a context diagram?
An external entity is a person, organization, or other system that sends information into the system or receives information from it, but sits outside the system's boundary and control. Examples include a student or customer, a registrar's office or supplier, and another system such as a payment processor. The test is control: if the system controls something, it belongs inside the boundary; if not, it is an external entity.
Why does a context diagram show the whole system as one process?
A context diagram shows the whole system as one process, usually numbered zero, so attention stays on the boundary and on what crosses in and out. It deliberately includes no internal processes and no data stores. That internal detail is not lost but saved for later, when more detailed data flow diagrams break process zero down into the system's actual internal processes and data stores.
How should data flows be labeled and drawn on a context diagram?
Data flows on a context diagram should be labeled with a noun or noun phrase naming the data, such as enrollment confirmation rather than confirm enrollment. Each arrow runs in one direction only, so a request and its response are drawn as two separate arrows instead of one double-headed arrow. Every flow connects an external entity to the system, and entities are not connected directly to each other.

About the System Analysis and Design course

How many college credits is System Analysis and Design?
System Analysis and Design (Computer Science 390) carries a NCCRS credit recommendation for 3 semester credits. ACE and NCCRS have over 2,100 cooperating colleges that will consider accepting credits; the final decision is with the universities.
How much does System Analysis and Design cost and what is included?
$250, paid once, with lifetime access: all 69 video lessons, a practice quiz after each, the graded work and final exam, and an official transcript when you finish. Students who want several courses choose UPI Study PRO instead.
Which universities accept UPI Study credits?
UPI Study has signed partner agreements with universities such as Thomas Edison State University, University of the People and Charter Oak State College, and works with universities such as Penn State, SNHU and SUNY. ACE and NCCRS have over 2,100 cooperating colleges that will consider accepting credits; the final decision is with the universities. Use "Find my college" on this page to check yours.
How long does System Analysis and Design take?
It is self-paced with no deadlines. The 69 lessons total about 9 hours of video; most students add reading and practice time and finish in a few weeks to a few months, on their own schedule.
How are the exams done?
Quizzes and assignments are online in the course. The final exam is taken online with proctoring; a person on the UPI Study team checks assignments, usually within two days.
How do my credits reach my college?
When the course shows 100% complete, request the official transcript from your dashboard. It is sent to the college you name, and you can send it to more than one. Check your college first with "Find my college" on this page, or ask Athena.

Ready for the full course? Earn 3 credits in System Analysis and Design.

69 video lessons, a quiz after each one, and the graded work that earns the credit. Recommended for credit by NCCRS.

Enroll in System Analysis and Design →Download the syllabusEvery course with PRO →
System Analysis and Design
3 credits · NCCRSEnroll →