Just Eats - Customer Registration Process Design Document Report

This document presents a design report for the customer registration process of the Just Eats website. It begins with a business process overview and a use case diagram illustrating the process. An activity diagram further details the workflow, followed by a detailed use-case description outlining the scenario of customer registration. The report identifies key classes, including CUSTOMER, LOGIN_DETAILS, PHONE, and ADDRESS, and their attributes, responsibilities, and collaborations. Class, sequence, and state machine diagrams visually represent the system's structure and behavior. A CRUDE analysis is conducted to examine the interactions between actors and the system's data. References to relevant literature are also provided. This report offers a comprehensive analysis of the customer registration process, covering various aspects from conceptual design to implementation considerations.

JUST EATS
Design document – Customer Registration Process Report
[Name]

Just Eats - Customer registration process
Table of Contents
Business process........................................................................................................................2
Use case diagram......................................................................................................................2
Activity diagram........................................................................................................................3
Use-Case description.................................................................................................................4
Classes and CRC.......................................................................................................................4
Class diagram............................................................................................................................7
Sequence diagram......................................................................................................................8
State machine diagram..............................................................................................................9
CRUDE analysis........................................................................................................................9
References................................................................................................................................10
1

Just Eats - Customer registration process
Business process – Customer registration process
Use case diagram
2

Just Eats - Customer registration process
Activity diagram
3

Just Eats - Customer registration process
Use-Case description
(Kimmel, 2005)
Classes and CRC
Following are key classes in the customer registration process:
 Customer
Class Name: CUSTOMER ID: 1
Description: The details of customer are
managed.
Associated use case: -
UC001 - Register
Responsibilities: Collaborators –
4
Use Case Register customer
Scenario Create new customer
Triggering Event A customer wants to create an account on the site.
Description Customer will be able to access services of the Just Eats
site
Actors Customer
Related Use Case N/A
Stakeholders 1. Customer
Pre-Condition Customer is able to access register URL on the site.
Post-Condition A new customer may be created.
Flow of activities
Actor System
1) Customer clicks the
“Register” link.
3) Customer enters data and
submits the form.
2) A form is displayed having fields – name, email,
address, username, password and phone.
4) System displays a unique customer number (A1).
Alternate Course of Action 2.1 If a customer having the entered username is already
existing then an error message is displayed.

Just Eats - Customer registration process
Add customer
Delete customer
Update customer
Validate customer
Class
Attributes:
customerNo (number)
firstName (date)
lastName (text)
phoneNo (number)
address (number)
Generalization: - NA
Aggregation: - NA
Other Association: - NA
 LoginDetails
Class Name: LOGIN_DETAILS ID: 2
Description: The login details of
registered customers are stored.
Associated use case: -
UC001 - Login
Responsibilities:
Add login details
Update password
Login
Change account
Cancel account
Collaborators –
Class
Attributes:
username (String)
password (String)
Generalization: - NA
Aggregation: - NA
Other Association: - NA
 Phone
Class Name: PHONE ID: 3
Description: The phone numbers of the Associated use case: -
5

Just Eats - Customer registration process
registered customer are stored.
UC001 - Register
Responsibilities:
Create Phone
Maintain Phone
Get Phone
Edit Phone
Delete Phone
Save Phone
Collaborators –
Class
Attributes:
phoneID (number)
phoneNumber (number)
phoneType (char)
Generalization: - NA
Aggregation: - NA
Other Association: - NA
 Address
Class Name: ADDRESS ID: 4
Description: The address of the registered
customer is stored.
Associated use case: -
UC001 - Register
Responsibilities:
Create address
Get address
Edit address
Delete address
Save address
Collaborators –
Class
Attributes:
streetNo (String)
streetName (String)
suburb (String)
postcode (String)
state (String)
Generalization: - NA
6

Just Eats - Customer registration process
Aggregation: - NA
Other Association: - NA
Class diagram
(Fontoura, Pree & Rumpe, 2002)
7

Just Eats - Customer registration process
Sequence diagram
8

Just Eats - Customer registration process
State machine diagram
CRUDE analysis
Customer
Actor
Delivery
Boy
Actor
Restaurant
Actor
Order Customer Restaurant Payment Delivery
Customer
Actor
C, R,
U, D,
E
C, R, U,
E
C, R
Delivery
Boy Actor
R, E
Restaurant
Actor
C, R, U,
D, E
E
Order
Customer
Restaurant
Payment
Delivery
9

Just Eats - Customer registration process
References
Fontoura, M., Pree, W., & Rumpe, B. (2002). The UML profile for framework
architectures(2nd ed., pp. 12-14). Boston: Addison-Wesley.
Kimmel, P. (2005). UML demystified (1st ed., pp. 34-36). Emeryville, Calif.:
McGraw-Hill/Osborne.
10