Pattern: Maintain A Map

Pattern: Maintain A Map

Summary In order to ensure coherence across cases and patterns, create a map of the domain and return to it at each step of the process.
Status seed Confidence 1
details... Group Planet team

Problem

The problem is compound of tensions along three dimensions:

  1. A tension between the higher level structure of a domain and the detail of specific elements of design
  2. A tension between the individual writer and a group reflecting on a shared practice
  3. A tension between writers and readers.
In terms of (1), the process of analysing practice is by definition concerned with decomposition, partitioning complex domains into compact units. The more refined the unit of analysis, the more it looses the "big picture".

In terms of (2), each groups collaboratively reflecting on shared practice is composed of individuals with personal agendas. The process of collaborative reflection needs to balance and synchronise these personal agendas to a coherent whole.

In terms of (3), the writer or writers of a pattern collection have an internal representation of the domain structure. A reader who is not involved in the writing process does not have it, and will therefore find the outcome impenetrable unless provided with a lucid map.

Context

Individuals or groups engaged in a process of reflecting on and abstracting from practice, with a commitment to communicating a coherent representation of design knowledge in the domain of practice to an external audience. For example, a group of authors producing a design language intended to be used by a wider community.

Solution

Create a functional map of the domain at project inception.

For each entity produced in the process:

  • place it on the map
  • note any discrepencies it raises
  • when done with the entity, update the map

Related Patterns

list other patterns related to this one, under categories such as component, assisting, conflicting, uses this, etc.

Support

* Source and Additional Supporting Cases

      Source Case (chosen from Case Studies)

      Other Cases (chosen from Case Studies)

      Links to External Case Stories & Examples


* Rationale (theoretical justification)

Theoretical justification.


* Verification (Solutions that were derived from this pattern)

Scenarios / solutions which were developed using this pattern.


Notes, Links and References

Liabilities, potential risks, extensions, expected side-effects

Licensing

Creative Commons License
This work is licenced under a Creative Commons Licence.

UML Diagram- Text representation

Tags:
Created by Yishay Mor on 2009/05/06 17:03
Last modified by Yishay Mor on 2009/05/06 18:03

This wiki is licensed under a Creative Commons 2.0 license
XWiki Enterprise 2.0.24043 - Documentation