SoftwarePractice.org: Home | Courseware | Wiki | Archive

Menu:

Module 2. Expressing requirements

The early phases of the Unified Process include workflows for capturing system requirements. In this subject, we are mostly focussed on the (later) design work, but nonetheless, it is still important to do some work on the requirements. Apart from helping you to build a better system, the system testing required later in the subject relies heavily on the work you do here. This module introduces usage scenarios, use cases, and paper prototypes. You will be expected to use UML use case diagrams to capture the relationship between users and use cases.

Lecture material

Tutorial

In the tutorial following on from the lecture, students will be given a short system description (a page or so). Based on this system description, they are expected to firstly identify stakeholders. Then, to write some short usage narratives (scenarios) to explore key functions and user expectations. Personas can be defined informally. Each narrative should be written on a single card.

During the first phase, they should also be encouraged to sketch out user interfaces, in order to explore their concept of what the system will do, from the user's point of view.

In the second phase, students are to define actors and to write a number of essential use cases. Each should be written on a single card. They should be able to do four or five. By the completion of the tutorial, they will also have a complete use case diagram.

Resources