Detailing Use-Cases with Activity Diagrams and Object Views Workshop on Integrating Human Factors into Use Cases and OO Methods Nuno Jardim Nunes (DNNUNES@UMA.PT), João Falcão e Cunha (JFCUNHA @FE.UP.PT) 1 ABSTRACT This position paper discusses the role of detailing use-cases with activity diagrams and object views in the WISDOM approach. We briefly present WISDOM (Whitewater Interactive System Development with Object Models), a lightweight software engineering methodology and discuss how we extended the use-case concept to integrate HCI techniques. 2 WISDOM (WHITEWATER INTERACTIVE S YSTEM DEVELOPMENT WITH OBJECT MODELS) WISDOM (Whitewater Interactive System Development with Object Models) is the result of our experience working with SMEs [Nunes and Cunha 1998; Nunes et al 1998], aiding and facilitating their processes and techniques. Our initial studies about the way the people in these companies work and “think” software revealed a strong urge towards implementation. This urge ultimately leads them to chaotic tailored processes, also known as the Nike® (just do it) approach to software engineering. People working in small companies or within user organisations tend to focus their activity in what Grudin [Grudin 1991] described as in-house or custom development. This development context compromises a great focus on user interaction since it usually concerns developing (or adapting) small software systems to meet specific user needs not covered by large shrink-wrapped systems. Hence the raising importance of user-centered and participatory techniques, ultimately important to SMEs. These companies are typically closer to end-users and, due to their limited resources, increasingly dependent on the user interface efficiency to satisfy clients. Although we don’t claim WISDOM is a scalable methodology, we feel it can be used in other development contexts, like off-the-shelf and contract based. What we claim is that WISDOM can represent a good step towards a large-scale industry process like the Rational Unified Process (RUP) [Krutchen 1998]. WISDOM is strongly based on the UML and it uses several models and views that exist in large industrial processes like RUP. Thus an organization can start implementing WISDOM and then incrementally introduce new workflows, models and views using the UML, ultimately reaching an industry scale process like RUP. WISDOM is a lightweight software engineering methodology, lightweight in the sense that it can be learned and applied in a couple of days or weeks. WISDOM is object-oriented, it uses the UML to specify, visualize and document the artifacts of the development project. WISDOM is specially adapted to develop interactive systems, because it uses and extends the UML to support human- computer interaction techniques [Nunes 1999]. Finally WISDOM is evolutionary, in the sense that the