context diagram

<< project name >>

SYSTEM (CODE)NAME

<< approved stereotypes >> NAME OR USER ROLE

or USER GROUP

<< approved stereotypes >> NAME OF DATA STORE { technology properties}

NAME OF SENSOR,

MACHINE OR DEVICE (optional

technology tags}

<< approved steretypes >> NAME OF

INTERFACING SYSTEM { technology properties }

<< approved stereotypes >> NAME OF NET INPUT

USER INTERFACE DATA FLOW {technology properties}

<< approved stereotypes >> NAME OF NET OUTPUT

USER INTERFACE DATA FLOW { technology properties }

<< approved stereotypes >> NAME OF NET OUTPUT

SYSTEM INTERFACE DATA FLOW

{ technology properties }

<< approved stereotypes >> NAME OF NET INPUT SYSTEM INTERFACE

DATA FLOW { technology properties }

<< read, or batch import >> NAME OF NET DATA READ

{ technology properties }

<< create, update, delete, or batch export >> DESCRIPTION OF NET DATA CHANGED

{ technology properties }

<< approved stereotypes >> NAME OF COMMAND

or INSTRUCTION { optional technology properties }

<< approved stereotypes >> NAME OF SENSED CONDITION { optional technology properties}

Note: technology property tags are not relevant to this shape

Note the semantic use of black to reinforce that context diagrams illustrate the system concept of “black box” thinking

CNIT 385 and 581: UML PROFILE FOR CONTEXT DIAGRAMS