Before diving into the complex inner workings of a system, we first need to understand its place in the world. A Level 0 Context Diagram gives us this high-level, bird's-eye view. It treats the entire Dairy Management System as a single, central process and focuses on how it interacts with the outside world. Think of it as a map showing the major highways leading into and out of a city, without detailing every single street inside.

Our city is the 'Dairy Management System'. The highways are the data flows, and the neighbouring towns are the external entities—the people and organisations that send information to or receive information from our system.

For our Dairy Management System, the main external entities are straightforward. They represent the key touchpoints in the milk procurement and distribution lifecycle.

• Farmers: The source of the primary raw material. They supply milk and need to be paid for it.
• Customers: These are typically retailers or distributors. They order finished products and receive invoices.
• Quality Control Labs: An independent or internal body that tests milk samples and provides quality reports. For a context diagram, we treat it as external because it provides a distinct data input.
• Government Regulatory Body: This entity ensures the dairy complies with food safety and industry standards. It receives reports from the system.

This diagram clearly defines the system's boundaries. Everything inside the circle is 'our system'. Everything outside is not. The arrows represent the crucial data exchanges. Farmers provide Raw Milk Details, which must include quantity and quality metrics like Fat/SNF Content for pricing. In return, the system generates Payment Vouchers.

Defining the system scope is one of the most critical steps. For example, should the Government Regulatory Body truly be external? One could argue that compliance checks are an integral part of the dairy's operations. However, for a Level 0 diagram, treating it as an external entity is the correct approach.

The reason is simple: the system's primary purpose is managing the dairy supply chain, not performing regulatory functions. The government body is a recipient of information, a 'sink' for data. The process of generating the Compliance Report is internal to the system, but the entity consuming it is external. If we were to include the regulatory body inside our system, the scope would expand dramatically, and the diagram would lose its clarity. At Level 0, we stick to the core function.

With our context diagram established, we have a stable foundation. We've defined the system's boundaries, identified its interactions with the outside world, and agreed on the project's scope. This is the starting point from which we can begin to break down the central process into more detailed, lower-level diagrams.