Dealing With Rationale Challenges

In addition to supporting rationale tasks, an RMS must deal with the limitations discussed in Sect. 1.5. In particular, strategic decisions made during the rationale goal definition and rationale identification tasks can significantly impact the selection and tailoring of the …

Approaches to Solving the Capture Problem

Traditionally, DR literature has emphasized that devising the right schema, i.e., one that captures the right information and structures it correctly, is the way to solve the problems of DRR usage. Yet designers’ resistance to DR capture exists regardless of …

Supporting Future Changes

The most commonly mentioned reason for using DR in SE is to support future changes in software, a problem that is perhaps more pressing in this field than in any other design or engineering field. This does not necessarily require …

Increasing Consistency of Decisions

Often it is only by making rationale explicit that consistency can be achieved. For example, it is not uncommon in large projects for the same decision tasks to be done by different groups within the design team. Recording rationale makes …

Generating DR from Data and Models

Gruber and Russell [23] argue that argumentative schemas do not include all the rationale that designers use, because all of them are prescriptive about what information is relevant. No collection of DR, they claim, could answer all of the questions …