RSI - A Structured Approach Use Cases and HCI Design

Following is an example of an interface use case being used to specify a report layout:
Format:
Bill for ,
Printed: dd/mm/yy
Item Date Value Balance__
cccccccccccccccccc dd/mm/yy #####.## ######.##
…
___________________ ________________________________
Total: ######.##
Functionality:
1. Lines within the report are filled in using '«query» get bill details'.
interface use case 'bill'
A full description of the requirement use case model for this system can be found in the
companion document to this paper on www.ratio.co.uk/rsi-info.htm.
4.5. Developing the service use case model
The service use case model is developed on a per increment basis.
The consolidated service use case model is comprised of the essential service use cases plus
additional query use cases mandated by interface design.
4.5.1. Inputs:
• requirement use case summary diagram;
• requirement use case textual descriptions;
• (optionally) conceptual domain object model;
• interfaces use case model (developed in parallel);
4.5.2. Outputs:
• service use case summary diagram (essential and full models);
• service use case textual descriptions (essential and full models);
• core specification model;
4.5.3. Sub-process:
• Consider the requirement use case model with users
We Know the Object