Modeling Activity Develop Effective Diagrams (Drawing Techniques)

Description

A diagram is a means of visualizing data and, of course, clarifying some aspect of the business (why a diagram is itself sometimes called a "model"). However, if a diagram is itself unclear - e.g. cluttered, busy, unreadable font, clashing colours, vast tranches of "dead space", full of what Edward Tufte calls "chart junk", so complicated it looks like spaghetti - then the very purpose of diagramming is undermined.

It is, therefore, to apply effective drawing techniques to your diagrams, taking into consideration:

- The purpose of the diagram (e.g. accuracy and fidelity are often the enemy of clarification and simplicity)

- The intended audience (e.g. a simple flow chart for business stakeholders vs a complex BPMN diagram for programmers)

- The media and context in which it will be consumed (e.g. pinned up onto a workshop wall, or targeted at users using a tiny mobile screen)

You then need to understand the functionality and interface of the Casewise diagrammer, including shape regions and Styles, in order to implement these design considerations in your actual diagrams. In other words, Casewise Modeler is not Visio or PowerPoint; you need other skills and ways of working to construct an effective diagram.

Capabilities (that this Activity helps deliver)

02 Data Capture, Diagramming, & Model Development

Appears on

Capability-Activity Diagram Set-up and Manage an Enterprise Architecture Modeling Environment
Concepts Diagram 02 Data Capture, Diagramming, & Model Development

zzz1

zzz2

Concepts (Key Casewise Concepts)

Diagram Types (e.g. Flow, Scope, Data Model)
Diagrammer Interface & Behaviour
Diagramming
Diagram-only (non-reusable) Objects
Diagrams & Views
Drawing Principles & Techniques
Drawing Principles (Aesthetics & Communication)
Objects on diagrams exist independently of that diagram

Modeling Activity Develop Effective Diagrams (Drawing Techniques)