Use case Description of Beauty Parlour/Salon Management system

3.5 Use Cases
Table 1: Use Case 1
Use Case		Login

Actor		Users, Parlor ,Admin

Description		The Use case is start when the actors sign in.
	1.		User wishes to login.
	2.		The system displays the login page that asks the
			actor to enter email and password.
Basic course of	3.		The actor submits their email and password to login
action A			the system
	4.		The actor of the system click login button.
	5.		The actor control checks the email and password
			from the database.
	6.		The controller verifies email and password.
	7.		The system displays the access page from the
			respective actor.
	8.		Use case end.
Alternative course of		A1: if the actor doesn’t enter the correct email and
Alternative course of		password.
action A		password.
action A		A5: the application asks to enter the correct email and
		A5: the application asks to enter the correct email and
		password.
		The application doesn’t display access page for the
		respective user.
		A6: use case end

Pre-condition		The login exists
		The actor logged in.

Post-condition		The login is successful.

Table 2: Use Case 2
Use Case		Registration

Actor	User, Parlor

Description	The Use case is start when the actors signup.
	1.	The application has a sign up button on the login
		screen.
	2.	The actor clicks signup button.
	3.	The graphical user interface entries displayed.
	4.	Actor fill all the necessary data.
	5.	The actor click on register account.
	6.	Save the data into database.
	7.	Use case end.

Pre-condition	The signup exists

Post-condition	The signup in successful

Table 3: Use Case 3
Use Case	Search Parlor

Actor	User

Description	The use case is start when the actor search
	1. Actor can search Parlor by name.
	2. Actor can search Parlor by location.

Pre-condition	Parlor must exist.

Post-condition	Parlor searched successfully.

Table 4: Use Case 4
Use Case	View Report

Actor	Parlor

Description	The use case is start when the actor will be Login and
	access to view the report.
	1. View Report of employee which employee attend
		more clients.
	2. View the quantity of client they attend services.

	3.	Case end.

Pre-condition	The actors logged in.

Post-condition	The report view successfully.

Table 5: Use Case 5
Use Case	Manage Services

Actor	Parlor

Description	The use case is start when the actor will be Login and
	access to manage the services.
	1.	Only the Parlor can add the services they offer.
	2.	After adding services actor can update the
		services.
	3.	Actor can change the price of current service.
	4.	After adding new service or updating services
		successful message showed.
	5.	Case end.

Pre-condition	The actors logged in.

Post-condition	The services add/update successfully.

Table 6: Use Case 6
Use Case	Manage Appointments

Actor	User, Parlor

Description	The use case is start when the actor will be Login and
	access to manage appointments.
	1.	The user can take appointment according to their
		required services.
	2.	Parlor can accept and reject the appointment
		according to their own easiness.
	3.	User can see the status of appointment either it is
		accepted or rejected.
	4.	User also cancel the appointment if user change

		their mind
	5.	Use case end.

Pre-condition	The actors logged in.

Post-condition

Table 7: Use Case 7
Use Case	Contact Parlor

Actor	User

Description	The use case is start when the actor will be Login and
	access to contact parlor.
	1.	The user can contact parlor to get information if
		they need.
	2.	Parlor can answer the user queries.
	3.	Use case end.

Pre-condition	The actors logged in.

Post-condition	User successfully connected with parlor.