Workshop aim: Typical design documentation merely describes the results of the process: a snapshot of the final product, with little insight into how these results were achieved. An alternative approach, which grew out of Rittel’s 1970s work on an Issue-Based Information System (IBIS), is to attempt the additional capture of the rationale behind the design. This includes the decisions required; all the alternatives evaluated; the reasoning behind the choice of one alternative over another; and the dependencies between earlier and subsequent decisions. This information can be useful in many ways, such as for redesign, reuse, maintenance, learning, documentation, collaboration and project management. Despite there being widespread acceptance of the potential usefulness of Design Rationale (DR) repositories, they are still not in general use. One obstacle has been the widely hel
To submit an update or takedown request for this paper, please submit an Update/Correction/Removal Request.