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.