Home > Claims > Rationale in SE and rationale in UE–what’s the difference?

Rationale in SE and rationale in UE–what’s the difference?

The question of the difference between design rationale in software engineering and usability engineering came up at my UC Boulder talk last week. It’s something that I’ve been thinking about for a while, and more recently as I’ve been reading about design rationale from a software engineering perspective (Burge, McCall, Schneider, etc.).

The big difference seems to be in the certainty embedded in the rationale. Design rationale in software engineering seeks to establish a position of truth, rooted in the functionality of the computer (compared to the nature of physical artifacts, as seen in other fields). The preface and introduction of Burge’s Rationale-based Software Engineering book do a good job of distinguishing design rationale in software engineering from design rationale in other fields.

In contrast, design rationale in usability engineering (and even more so in HCI) seeks to provide pointers toward the right directions–through methods, approaches, or lessons learned. Even a repository of web design patterns like van Duyne’s Design of Sites is lauded not because it preaches HCI truths but because it discusses how to design (e.g., how to promote e-commerce, how to settle on a page layout, how to customize for mobile devices). It includes checklists and is rooted in context, allowing the reader to decide what’s relevant.

This is why I feel claims (or something like them) are the future of design rationale in UE/HCI. They are meant to be hypothetical, subject to change based on changes in context, advances in knowledge, and retargeting of product design. They are more flexible than design rationale methods from software engineering and other fields, reflecting the flexible nature of the field of HCI. But that then makes the creation of claims libraries or other reuse repositories much more difficult–one must balance correctness with hypothesis, permanence with flexibility.

  1. September 20, 2011 at 8:53 pm

    In relation to the Nelson comments, I re-read Dan Russell’s HCI Remixed essay on Ted Nelson, titled “Deeply Interwingled”, in which he points to Nelson’s vision to augment intellect through hypertext as a formative work early and often in his career. While he acknowledges the incompleteness of the Web in reflecting Nelson’s vision, he points to search engines as providing the “concept-chunk-finding and reference-following” that better support digestible chunking of knowledge. And he acknowledges that the growing collection of cross-linked content creates a continuum of knowledge–from brilliant to absurd–for which it can be difficult to distinguish where a chunk may lie.

  1. No trackbacks yet.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s

%d bloggers like this: