Class Diagram

In computer science, class structure diagrams show the static structure of a system being modeled.  These focus on the relevant elements of a system, disregarding time.  The class diagram shows how different entities (people, things, information, phenomena, etc.) relate to each other. 

Different objects often have attributes in common.  For example, tigers, zebras, and skunks all have ‘stripes.’  Each of these creatures also has attributes that make them different.  As an analytic tool, the goal of the class diagram is to make an exhaustive inventory of relevant objects, classifying each  according to families, behaviors and attributes, to identify dependencies and relations within the system.  This drawing will expose relations, and expose possible opportunities for reorganizing a system, its hierarchies, or its expression.

How it could be useful.

Sports fields, parking lots, bicycle and running paths, street intersections - all inherit systems of graphic  markings on surfaces to inform use.  If these marks are an active ingredient that informs the way we interpet these spaces, then one can speculate about the power of graphic markings as a potential medium of design.

Similarly — toilet rooms, water fountains, bird baths, swimming pools, hockey rinks, irrigation systems, and fountains all depend on (inherit) water, and plumbing systems as an attribute.   If plumbing is an active ingredient contributing to the use or interpretation of these spaces, one could manipulate plumbing as medium of design.

Possible Tools

Hand Drawing, Adobe Illustrator
Astah free UML software (link)

References

IBM Class Diagram (link)

ChicagoParks to Reference:

Use any park in the list as a constraint or reference, exhausting the landscape, space by space, object by object,  

Try not to ‘overmine’, or ‘undermine’ the survey,  Objects contain objects.  Objects are contained by other objects.  Spaces contain spaces.  Spaces may be contained by spaces.