Top-level context diagram

This example of a Top Level Context Diagram for an information system management process was redesigned from the Wikipedia file: IDEF Top-Level Context Diagram.jpg. [en.wikipedia.org/ wiki/ File:IDEF_ Top-Level_ Context_ Diagram.jpg]
"Graphical notation.
IDEF0 is a model that consists of a hierarchical series of diagrams, text, and glossary cross referenced to each other. The two primary modeling components are:
(1) functions (represented on a diagram by boxes), and
(2) data and objects that interrelate those functions (represented by arrows).
... the position at which the arrow attaches to a box conveys the specific role of the interface. The controls enter the top of the box. The inputs, the data or objects acted upon by the operation, enter the box from the left. The outputs of the operation leave the right-hand side of the box. Mechanism arrows that provide supporting means for performing the function join (point up to) the bottom of the box.
The IDEF0 process.
The IDEF0 process starts with the identification of the prime function to be decomposed. This function is identified on a “Top Level Context Diagram,” that defines the scope of the particular IDEF0 analysis. ... From this diagram lower-level diagrams are generated." [IDEF0. Wikipedia]
The IDEF0 diagram example "Top-level context diagram" was created using the ConceptDraw PRO diagramming and vector drawing software extended with the IDEF0 Diagrams solution from the Software Development area of ConceptDraw Solution Park.

"As a discipline, task management embraces several key activities. Various conceptual breakdowns exist, and these, at a high-level, always include creative, functional, project, performance and service activities.
Creative activities pertain to task creation. In context, these should allow for task planning, brainstorming, creation, elaboration, clarification, organization, reduction, targeting and preliminary prioritization.
Functional activities pertain to personnel, sales, quality or other management areas, for the ultimate purpose of ensuring production of final goods and services for delivery to customers. In context these should allow for planning, reporting, tracking, prioritizing, configuring, delegating, and managing of tasks.
Project activities pertain to planning and time and costs reporting. These can encompass multiple functional activities but are always greater and more purposeful than the sum of its parts. In context project activities should allow for project task breakdown, task allocation, inventory across projects, and concurrent access to task databases.
Service activities pertain to client and internal company services provision, including customer relationship management and knowledge management. In context these should allow for file attachment and links to tasks, document management, access rights management, inventory of client & employee records, orders & calls management, and annotating tasks.
Performance activities pertain to tracking performance and fulfillment of assigned tasks. In context these should allow for tracking by time, cost control, stakeholders and priority; charts, exportable reports, status updates, deadline adjustments, and activity logging.
Report activities pertain to the presentation of information regarding the other five activities listed, including graphical display." [Task management. Wikipedia]
The example "Project tasks dashboard" was created using the ConceptDraw PRO diagramming and vector drawing software extended with the Status Dashboard solution from the area "What is a Dashboard" of ConceptDraw Solution Park.

"A data flow diagram (DFD) is a graphical representation of the "flow" of data through an information system. It differs from the flowchart as it shows the data flow instead of the control flow of the program. A data flow diagram can also be used for the visualization of data processing (structured design). Data flow diagrams were invented by Larry Constantine, the original developer of structured design, based on Martin and Estrin's "data flow graph" model of computation.
It is common practice to draw a context-level Data flow diagram first which shows the interaction between the system and outside entities. The DFD is designed to show how a system is divided into smaller portions and to highlight the flow of data between those parts. This context-level Data flow diagram is then "exploded" to show more detail of the system being modeled" [Data model. Wikipedia]
The DFD (Yourdon and Coad notation) example "Model of small traditional production enterprise" was created using the ConceptDraw PRO diagramming and vector drawing software extended with the Data Flow Diagrams solution from the Software Development area of ConceptDraw Solution Park.

"Data flow diagrams are one of the three essential perspectives of the structured-systems analysis and design method SSADM. The sponsor of a project and the end users will need to be briefed and consulted throughout all stages of a system's evolution. With a data flow diagram, users are able to visualize how the system will operate, what the system will accomplish, and how the system will be implemented. The old system's dataflow diagrams can be drawn up and compared with the new system's data flow diagrams to draw comparisons to implement a more efficient system. Data flow diagrams can be used to provide the end user with a physical idea of where the data they input ultimately has an effect upon the structure of the whole system from order to dispatch to report. How any system is developed can be determined through a data flow diagram model.
In the course of developing a set of levelled data flow diagrams the analyst/ designers is forced to address how the system may be decomposed into component sub-systems, and to identify the transaction data in the data model.
Data flow diagrams can be used in both Analysis and Design phase of the SDLC.
There are different notations to draw data flow diagrams (Yourdon & Coad and Gane & Sarson), defining different visual representations for processes, data stores, data flow, and external entities." [Data flow diagram. Wikipedia]
The DFD (Yourdon and Coad notation) example "Process of account receivable" was created using the ConceptDraw PRO diagramming and vector drawing software extended with the Data Flow Diagrams solution from the Software Development area of ConceptDraw Solution Park.