Pattern: Maintain A Map
Pattern: Maintain A Map
| Summary |
|
||||
|---|---|---|---|---|---|
| Status | seed | Confidence | 1 | ||
| details... | Group | Planet team
|
|||
Problem
The problem is compound of tensions along three dimensions:- A tension between the higher level structure of a domain and the detail of specific elements of design
- A tension between the individual writer and a group reflecting on a shared practice
- A tension between writers and readers.
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

This work is licenced under a Creative Commons Licence.