Use case Description of Online rental system

Use case Description

		Use Case 1

Use Case Number	01

Use Case Name	Register Account

Actors	Customer, Owner.

Description	Users to have their account and use the website.

Pre-condition	Must provide all information required for sign-up.

Postcondition	Users become the members of the web application and use the
	web application

Basic course of	1.	The user wants to have an account.
action A	2.	The web application has to sign up button on the login screen.
	3.	The user clicks sign up button.
	4.	The graphical user interface (GUI) entries displayed.
	5.	Users fill in all the necessary data.
	6.	The user clicks on the registered account.
	7.	Saves the data in the database.
	8.	Use case end

Alternative course	If the user does not fill all the necessary data
of action A	A4: The graphical user interface (GUI) entries are displayed.
	A8: Use case ends.

Use case Description 2

		Use Case 2

Use Case Number	02

Use Case Name	Manage Account

Actors	Customer, Owner.

Description	Enables Customer and Owner to manage their accounts.

Pre-condition	The Customer and Owner must be the member of the web
	application and have a Customer / Owner account.

Postcondition	Account of the Customer/ Owner altered (updated)

Basic course of
action A	1.	The Web application asks you to enter your email and password.
	2.	The Customer / Owner enters their email and password.
	3.	Customer / Owner click on the login button.
	4.	Checks the email and password in the database.
	5.	The login controller verifies email and password.
	6.	The home screen is displayed.
	7.	Customer / Owner taps on the profile screen.
	8.	The profile screen is displayed.
	9.	Customer / Owner changes the necessary data.
	10. Profile updated is displayed.
	11. Use case ends.

Alternative course	If the Customer / Owner enters the wrong email and password.
of action A	A4: The Customer / Owner does not proceed to the home screen.
	A9: The Customer / Owner does not change anything.

Use case Description 3

		Use Case 3

Use Case Number	03

Use Case Name	Login

Actors	Customer / Owner

Description	Allows users to log in to their accounts.

Pre-condition	The users (Customer / Owner) must have a user account.

Postcondition	Users log in and use the respective functions of the system.

Basic course of
action A	1.	User’s wishes to login.
	2.	The system displays the Login page that asks the user to enter
	email and password.
	3.	The user submits their email and password to login to the
	system.
	4.	The user of the system clicks Login button.
	5.	The login controller checks the email and password from the
	data base.
	6.	The controller verifies email and password.
	7.	The system displays access page for the respective user.
	8.	Use case end.

Alternative course	If the user does not enter the correct email and password.
of action A	A1: The application asks you to enter the correct email and password.
	A5: The application does not display an access page for the
	respective user.
	A6: use case end.

Use case Description 4

		Use Case 4

Use Case Number	04

Use Case Name	Find product

Actors	Customer / Owner

Description	The customer should have an account.

Pre-condition	The caller should have an account.

Postcondition	The owner checks all booking requests from customers.

Basic course of
action A	1.	The Caller wants to Find a paramedic.
	2.	Taps the Find Paramedic button on the home screen.
	3.	Application posts his request in the database.
	4.	Application checks for available Paramedics.
	5.	The paramedic accepts the request.
	6.	Application show details of the Paramedic to the caller.
	7.	Use case end.

Alternative course	If the customer did not allow the Web Application permissions for
of action A	Contact.
	A2: The Applications Shows a message that tells the Customer to
	allow permissions.
	A5: The Caller cannot contact with the product owner. A6: Use case
	end.

Use case Description 5

		Use Case 5

Use Case Number	05

Use Case Name	Report

Actors	Customer / Owner

Description	Enables Customer / Owner to report a customer or an Owner.

Pre-condition	Customer / Owner must be a member of the web application.

Postcondition	Customer / Owner is reported.

Basic course of	1.	The customer requests an Owner.
action A	2.	Owner accepts.
	3.	Details of the owner are shown on a screen.
	4.	The customer taps on the report button to report the owner.
	5.	Enters the reason to report.
	6.	Reported successfully,
	The message is shown.
	7.	Use case end

Alternative course	The customer doesn’t request contact.
of action A	A4: Does not report the caller.
	A7: Use case end

More helping material of Online rental system (Final Year Project – FYP)

Hopefully, this final year project (FYP, Capstone project, Software project, semester project, degree project) will well helpful for the students of BSCS, BSSE, BSIT, BCS (Software engineering, information technology, computer engineering and computer science) studying in a college, institute, and university.

Use case Description of Online rental system

More helping material of Online rental system (Final Year Project – FYP)

Related Posts:

Leave a Comment Cancel Reply