Appendix A - Recommended Practice
Published online by Cambridge University Press: 05 June 2012
Summary
The following is a collection of user requirements, each of which describes the required behavior of a system. Except where otherwise specified for each of the requirements, apply the bridge process to reach a full-fledged design in terms of a use case model, object model, and subsystem model. Apply traceability at all stages.
WEDDING LIST
A software for a wedding agency provides a gift reservation facility for couples who would like to have a wedding list, and a gift purchase facility for people who would like to send gifts. The software keeps information on couples and their corresponding wedding lists. Users can access the system to create or update, cancel, view their own wedding list, or to buy certain items from a specific wedding list. Users can also get help on how to use the system without the trouble of contacting employees at the wedding agency. Employees at the agency will administrate the system operations. Employees can delete, update, or add items to inventory. Any complaints or suggestions that the client may have could be sent to the agency and stored in a complaint database. To ensure secure access to the system couples and employees have personal logins and passwords.
- Type
- Chapter
- Information
- UML by Example , pp. 235 - 240Publisher: Cambridge University PressPrint publication year: 2004