{"id":3085,"date":"2017-12-11T10:03:46","date_gmt":"2017-12-11T10:03:46","guid":{"rendered":"https:\/\/www.threesl.com\/blog\/?p=3085"},"modified":"2017-12-11T10:03:46","modified_gmt":"2017-12-11T10:03:46","slug":"holistic-view-context-diagram","status":"publish","type":"post","link":"https:\/\/www.threesl.com\/blog\/holistic-view-context-diagram\/","title":{"rendered":"A Holistic View – The Context Diagram"},"content":{"rendered":"

Context Diagram – the world around our project<\/h2>\n

A context diagram aids visualisation of where a project sits in relation to its external interactions. We don’t want to model those external systems, but we do want to know how they interact with our system.<\/p>\n

Automatic wipers for a car don’t need to know how the weather works, but they do need to sense the presence of water on the windscreen. The context would, therefore, include the weather as an external influence with ‘rain’ or ‘rain present’ being signalled to our system. If our company only produces the wiper element the actual car is outside our scope. However, this is where we get our power from and it’s where we will install them so the car is part of our context. The interactions with the car such as ’12v supply’ and ‘user control signal’ are likely to show a part of the holistic context.<\/p>\n

Data Flow Diagram (DFD)<\/h3>\n

In terms of functional analysis and design the DFD shows the external elements with which our main system interacts on the context diagram. This usually has only one process on it, and that is our system of interest.<\/p>\n

\"an
Context Diagram – DFD<\/figcaption><\/figure>\n

Taken from the Cradle demonstration project this diagram shows our system of interest is operating the aircraft. The externals that we interact with form the context within which the project operates. This includes the booking system, the fuel suppliers, the control tower and so on.<\/p>\n

When the design and analysis are broken down at lower levels, the passenger details or navigation information will have to be handled by parts of the target system. If there is anything that does not balance at the lower levels, then a function must be missing. It implies that we have an input stimulus or an expected output and have nothing to handle or provide it.<\/p>\n

Block Definition Diagram (bdd)<\/h3>\n

Context diagram notations are not restricted to Yourdon, a SysML bdd is also used to describe the context. Information gathered from the use cases and operational scenarios can be used to build a holistic view.<\/p>\n

\"Context
Context Diagram – bdd<\/figcaption><\/figure>\n

Visual<\/h3>\n

Whilst not necessary, adding images to your context can aid communication to your stakeholders and customers. They don’t really have to understand the notation to visualise the ‘Passenger’ as a person interacting with the flight. In Cradle, images can be added to the diagram as standalone images<\/a>, or can actually replace the symbol<\/a> on the diagram. (The image in the latter will follow all the rules and have the underlying specification of the real diagram element).<\/p>\n