We have borrowed this term from civil engineering to denote a set of drawings
that describe a sociotechnological system to be implemented.
The primary set of drawings consists of the following:
- Class Diagram (CL) - for an overview of how active objects, passive objects,
processes and process states relate to each other
- Organization-Resource structure Diagram (ORG) - to specify an active object
hierarchy and to characterize them through availability, cost, skills,
- Task Details Diagram (TD) - to characterize an activity that is part
of a business process, including which active objects perform it, duration,
attributes, triggering conditions, predecessor and successor tasks,
- Business Process Diagram (BP) - to show the sequence of tasks in
performing an activity, including which events or conditions trigger a task,
which passive objects are produced by a task, etc.
- Passive Object Diagram or Data Definition Diagram (DD) - to specify the structure and attributes of a
The following are specifically tailored for software systems:
- Entity Relationship Diagram (ER) - primarily for software systems - to
specify data or passive object relationships
- Graphical/Alphanumeric Screen Form (GSF/ASF) - for software systems only - to specify
the user interface
- Process Diagram (PD) - primarily for software systems - to specify program
logic with incoming and outgoing passive objects or messages
There are a number of diagrams and tables that can be generated from the
primary drawings and are part of a system blueprint set, such as the data dictionary,
event table, attributes table, transfer object table, communicating objects diagram, etc.