Draw a system boundary and identify stakeholders and flows.
Reading tools
Please sign in to use all the tools
Once you sign in, the reading tools are yours: larger or smaller text, typeface, line spacing, focus mode, highlighting and bold, and notes saved to your account and gathered in My study.
The system of interest is not everything visible in a situation. It is the set of elements we intend to design or change for a defined purpose, with explicit interfaces to what remains outside. Elements may include software, people, procedures and equipment. The boundary depends on the decision being studied. For a maintenance booking service, the request store, dispatch logic and operator screen may sit inside; a municipal communications network and contractor vehicles may remain in the environment. External does not mean irrelevant: each crossing still needs an owner and an observable contract. SEBoK introduces the system's purpose, boundary, environment and stakeholders as connected concerns across its life cycle. Our diagram is therefore a decision tool, not a drawing of every technology in the city.
Start with a purpose statement that can be challenged: enable residents to report pump faults and route a usable work order to a maintenance team. Ask who uses the result, who operates the service, who suffers when it fails, and who supplies an input the service does not control. Draw a box for the system and one directed arrow for each boundary crossing. An arrow should name an observable item, such as a report with location and time or a work order with an acknowledgement state. The word data alone hides too much. Assign an owner to both ends. A request database can be inside the boundary while a notification provider is an enabling system outside it. We still design and test our side of the delivery interface; we do not claim to design the provider's entire network.
Do not treat a stakeholder's proposed feature as the final requirement. A resident may ask for a large red button but actually need to report an urgent fault quickly from a phone with poor connectivity. A field supervisor may ask to block every incomplete report because a crew cannot travel without a location. Those two statements point to different needs and a conflict. Keep their reasons visible, then ask what minimum information permits safe initial triage and how missing details can be obtained. The next lesson converts needs into verifiable requirements. Here the task is to identify the owner, use context, information gap and tradeoff before one designer silently chooses for everyone.
A context diagram becomes useful when discussion moves from application names to flows and responsibilities. In this case the interface between reporting and case storage carries a unique identifier, a location that may be absent, a follow-up state and an entry time. Unknown location must not be encoded as zero coordinates that look valid. The dispatcher sends a work order only after the location has been verified, and the field team returns an acknowledgement or a reason for refusal. Missing acknowledgement is not successful delivery. Keep the order pending and investigate the gap. These details belong at the system boundary because they define what our service guarantees and what it requests from another party. They also provide concrete inputs for interface requirements and verification later in the program.
Lesson summary
Draw the reporting-service boundary, identify stakeholder needs and calculate how rejecting incomplete reports affects residents and crews.