CCS Delivery Person, Manager, and User Stories

This document covers the roles of CCS delivery person and manager, user stories, functional and non-functional requirements, context diagram, use case diagram, entity-class diagram, state diagram, ER diagram, and tables with primary keys.

Cover page

Contents
Task 2..........................................................................................................................................................3
Task 3..........................................................................................................................................................4
Task 4..........................................................................................................................................................9

Task 2
Q3) Scenario
CCS Delivery person
As a CCS delivery person I log in into the system and check if they are any pending orders that are
waiting to be delivered. If there are any orders I accept to take on the orders that I want to deliver in the
system. I go to the restaurant and pick the contents of the orders. For each order, I make the delivery to
the member or group that made the order and update the status of the order.
CCS Manager
As the CCS manager, I log in into the system and check if any members or groups have made a request
for an event. If there is a request I check the details of the event to make sure the event is not
conflicting with any other event in terms of venue and time. If the event is not conflicting with any other
event, I create the event. If the request conflicts or is not valid I deny the request. I also check for any
claims made by members who have booked an event for example a claim for schedule conflict. I manage
the schedule conflict and update the two events. For any client that raises the cancel event request, I
accept the request and change the status of the event.
Q4) user stories
 As a student I would like to register as a CCS member.
 As a staff I would like to register as a CCS member
 As a student I would like to register as a delivery person.
 As a delivery person I would like to view orders that are available for delivery.
 AS a CCS manager I would like to view any new requests made for event booking.
Q5) Functional requirements
 A staff should be able to register as a CCS member.
 A student should be able to register as a CCS delivery person.
 A CCS manager should be able to view new requests made for event booking.
Q6) Non-Functional requirements
 Availability- The system should be available at all times to make sure that users can access the
system and perform actions within their scope at any time.
 Performance- The system should be able to perform all actions using the least amount of time
possible. For example the registration as a CCS member for a staff or student should not take
more than 5 seconds after the user submits the login form.
 Security- The system should be secure to ensure the information provided by the users is not
accessed by unauthorized users.

Task 3
Q7) Context diagram (Level O DFD)
Q8) Use case diagram

The added use cases for the CCS delivery person are;
 View pending deliveries- This use case enables the CCS delivery person to view deliveries that
are pending to be delivered
 Change availability status- This use case enables the CCS delivery person to update his
availability status where he or she can change it from available to unavailable or viceversa.
Q9) Use case description
The selected use case is register as a member
Use Case ID: UC1
Use Case Name: Register as a member
Actor: Student, Staff
Description: A student or a staff registers to be a CCS member
Preconditions: The student must be a valid student in the university and the staff

must be a valid staff in the university
Priority: High
Frequency of Use: Very frequent
Normal Course of Events: 1. User opens the register as a member page
2. System displays the page
3. User fills in the form and submits
4. System validates the user data
5. System sends a validation request to MQAuthServer
6. System creates an account for the user.
7. System displays a success message to the user
Alternative Courses: 5. System sends a validation request to MQAuthServer
5.1 System receives a failed validation from the server
5.2 System displays an error message
5.3 System takes the user back to step 2.
Exceptions: None
Includes: MQAuthServer validation
Special Requirements: The system must be should be able to send and receive requests
and data to MQAuthServer.
Assumptions: Both the system and MQAuthServer are running on the same
network
Q10) Sequence diagram

Q11) Entity-class diagram

Q12) State diagram
State diagram for the member class

Task 4
Q13) ER Diagram

Q15) Tables with primary keys
Member (MemberID, firstName, lastName, type)
PK (MemberID)
Restaurant (restaurantID, name, location)
PK (RestaurantID)
Order (orderID, date_time, memberID, restaurantID)
PK (orderID)
FK (memberID) references member (memberID)
FK (restaurantID) references restaurant (restaurantID)
Item (itemID, name, type)
PK (itemID)
Order_line ( orderID, itemID, quantity)

PK (orderID, itemID)
FK (orderID) references Order (orderID)
FK (itemID) references item (itemID)
DeliveryPerson (deliveryPersonID, name , available)
PK (deliveryPeronID)
Delivery (deliveryID, deliveryPersonID, orderID, date, status)
PK (deliveryID)
FK (deliveryPersonID) references deliveryPerson (deliveryPersonID)