Ooad Design Specifications

ooad

Restaurant All-in-one Management System (RAMs)
Design Specification with UML

by

Leung Chun Kit and Leung Ting Fong
03011720 and 03011739
(Group 22)

COMP 2221
Lecturer: Prof. Jiming Liu
December 4, 2004 I. Table of Content

I. Table of Content 1

II. Graphical Notion Used 2

Notation of Use Case Diagram 2 Notation of Class Diagram 2 Notation of Sequence Diagram 3

1. Use Case Diagram 4

1.1. Use Case Diagram of End User Acting with the RAMsystem 4

2. Class Diagram 5

2.1. Class Diagram of RAMsystem 5

3. Sequence Diagram 6

3.1. Sequence Diagram of staff 6 3.2. Sequence Diagram of manager 8 3.3. Sequence Diagram of administrator 9
II. Graphical Notion Used

Notation of Use Case Diagram
[pic]

Notation of Class Diagram
[pic]
Notation of Sequence Diagram
[pic]
1. Use Case Diagram

1. Use Case Diagram of End User Acting with the RAMsystem
Description:
End users(administrator, manager, staff) can perform ordering, editing ,checking and management function insider the RAMsystem. End user can use food ordering function and food editing function only bill had been created by user. Only manager can manage the duty roaster. No one can edit the database or checks the password database execpt the administrator.

[pic]
2. Class Diagram

1. Class Diagram of RAMsystem
Description:
All user and database of RAMsystem is created by the administrator. Administrator can modify any of the data in the RAMsystem. Staff and manager can create or edit bill but only manager can edit duty roaster. Bill has id, date and cost. Each bill has a unique id. User can be categorized into 3 types, administrator, manager and staff. All users have their own unique id and password. Both the administrator and the other user can change their own password. However, administrator can change the password everyone.

[pic]
3. Sequence Diagram

1. Sequence Diagram of staff
Description:
Staff can only add order,