Use Case Descriptions of SHOPPING MALL MANAGEMENT SYSTEM Project

Use Case Descriptions of SHOPPING MALL MANAGEMENT SYSTEM Project

SHOPPING MALL MANAGEMENT SYSTEM Project

If you are interested to read the SRS of the project, then click here for the details case study.

Use CaseRegister
ActorCustomer
DescriptionThe use case begins when the actor indicates the intent to login to the system. It ends when the actor is logged in or cancels login.
Pre-ConditionThe login exists.
Post-ConditionThe actor logs in successfully.

 

Use CaseLogin
ActorAdministrator/User
DescriptionThe use case begins when the actor indicates the intent to login to the system. It ends when the actor is logged in or cancels login.
Pre-ConditionThe login exists
Post-ConditionThe actor logs in successfully.

 

Use CaseView Shops
ActorCustomer/User
DescriptionThe use case begins when the actor indicates the intent to view Shops record. It ends when the actor closes the Shops form.
Pre-Condition1-The Shops record exists for view.

2-The actor is logged in

Post-ConditionThe Shops record is Viewed.

 

Use CaseBooking for Shops
ActorCustomer/User
DescriptionThe use case begins when the actor indicates the intent to Book the shops. It ends when the actor closes the Shops Apply form.
Pre-Condition1-The Shops record exists for Booking.

2-The actor is logged in

Post-ConditionThe actor easily books shops.

 

Use Case Payments details
ActorCustomer/User
DescriptionThe use case begins when the actor indicates the intent to add payment details for shops. It ends when the actor closes payment form.
Pre-Condition1-The shops record exists for booking.

2-The actor is logged in.

Post-ConditionThe actor easily gives information related to accounts.

 

Use Case Receives Payments  Receipts
ActorCustomer/User
DescriptionThe use case begins when the actor indicates the intent to get payment receipts details for shops. It ends when the actor closes the payment form.
Pre-Condition1-The shop’s record exists for booking.

2-The actor is logged in.

Post-ConditionThe actor easily gets receipts related to accounts.

 

Use CaseView shops  Records
ActorAdministrator
DescriptionThe use case begins when the actor indicates the intent to view or edit Monthly record. It ends when the actor closes the form.
Pre-Condition1-The shops record exists for editing/view.

2-The actor is logged in.

Post-ConditionThe Record viewed successfully.

 

 

 

 

Use CaseAdd shops  Records
ActorAdministrator
DescriptionThe use case begins when the actor indicates the intent to add or edit record. It ends when the actor closes the add form.
Pre-Condition1-The shops record exists for editing/Adding.

2-The actor is logged in.

Post-ConditionThe Record added successfully.

 

Use CaseDelete shops  Records
ActorAdministrator
DescriptionThe use case begins when the actor indicates the intent to Delete or edit a record. It ends when the actor closes the delete form.
Pre-Condition1-The shop’s record exists for editing/Deleting.

2-The actor is logged in.

Post-ConditionThe Record Deleted successfully.

 

Use CaseUpdate shops  Records
ActorAdministrator
DescriptionThe use case begins when the actor indicates the intent to update or edit the record. It ends when the actor closes the update form.
Pre-Condition1-The shops record exists for editing/updating.

2-The actor is logged in.

Post-ConditionThe Record updated successfully.

 

Use CaseView accounts records
ActorAdministrator
DescriptionThe use case begins when the actor indicates the intent to view the Transaction’s record. It ends when the actor closes the Ledgers form.
Pre-Condition1-The Transaction record exists for view.

2-The actor is logged in.

Post-ConditionThe account record is viewed successfully.

 

Use CaseView Clients records
ActorAdministrator
DescriptionThe use case begins when the actor indicates the intent to view the clients’ record. It ends when the actor closes the Clients form.
Pre-Condition1-The clients’ record exists for view.

2-The actor is logged in.

Post-ConditionThe client record is viewed successfully.

 

Use CaseView Clients records
ActorAdministrator
DescriptionThe use case begins when the actor indicates the intent to delete the clients’ record. It ends when the actor closes the Clients form.
Pre-Condition1-The clients’ record exists for delete.

2-The actor is logged in.

Post-ConditionThe client record is deleted successfully.

If you are interested to read the SRS of the project, then click here for the details case study.

Add a Comment