Sign in/ Sign out
Use Case ID: | UC-1 | ||||
Use Case Name: | Sign In / Sign Out | ||||
Actors: | Administrator | ||||
Description: | Admin will be able to Sign In / Sign Out to use the application. | ||||
Trigger: | Admin clicks on Sign In / Sign Out button | ||||
Preconditions: | None | ||||
Normal Flow: | 1. | User will open the application. | |||
2. | User will click on sign up button. | ||||
3. | User will enter his / her credentials and details. | ||||
4. | User will click on register. | ||||
Exceptions: | In step 3 of the normal flow, if user enters wrong credentials | ||||
3a. System will prompt user to re-enter his credentials. | |||||
VIEW CLIENT / ADD CLIENT / MODIFY CLIENT
View Client / Add Client / Modify Client
Use Case ID: | UC-2 | |
Use Case Name: | View Client / Add Client / Modify Client | |
Actors: | Administrator | |
Description: | Admin will be able to View Client / Add Client / Modify Client to the | |
application. | ||
Trigger: | Admin clicks on View Client / Add Client / Modify Client | |
Post conditions: | A successful View Client / Add Client/ Modify Client will take admin | |
to main dashboard. | ||
Normal Flow: | 1. | Admin will open the application. |
2. | Admin will enter username and password. | |
3. | Admin will click on sign in button. | |
Alterntive Flows | None | |
Exceptions | In step 3 of normal flow, if admin enters wrong username or password | |
3a. System will prompt admin to re-enter login information. | ||
Delete Client / Delete Invoices / Delete Services / Delete Shop Items Table 4.3.3 Delete Client / Delete Invoices / Delete Services / Delete Shop Items
Use Case ID: | UC-3 | ||||
Use Case Name: | Delete Client / Delete Invoices | ||||
Actors: | Administrator | ||||
Description: | Admin will be able to Delete Client / Delete Invoices the system. | ||||
Trigger: | Admin clicks on Delete Client / Delete Invoices | ||||
Preconditions: | Admin is Delete Client / Delete Invoices | ||||
Post conditions: | Notice is added successfully. | ||||
Normal Flow: | 1. | Admin will open manage notices. | |||
2. | Admin will click on add notice. | ||||
3. | Admin will enter description of the notice. | ||||
Alternative Flow | None | ||||
MODIFY ENG. / ADD ENG. / VIEW ENG Table 4.3.4 Modify Eng. / Add Eng. / View Eng.
Use Case ID: | UC-5 |
Use Case Name: | Modify Eng. / Add Eng. / View Eng. |
Actors: | Administrator |
Description: | Admin will be able to Modify Eng. / Add Eng. / View Eng. From the |
system. | |
Trigger: | Admin clicks on Modify Eng. / Add Eng. / View Eng. |
Preconditions: | Admin is Modify Eng. / Add Eng. / View Eng. |
Post conditions: | Notice is Modify Eng. / Add Eng. / View Eng. |
VIEW SHOP ITEM / ADD SHOP ITEM / MODIFY SHOP ITEM
View Shop Item / Add Shop Item / Modify Shop Item
Use Case ID: | UC-7 | ||||
Use Case Name: | View Shop item / Add Shop item / modify Shop item | ||||
Actors: | Administrator | ||||
Description: | Admin will be able to View Shop item / Add Shop item / modify Shop | ||||
item to the system. | |||||
Trigger: | Admin clicks on View Shop item / Add Shop item / modify Shop item | ||||
Preconditions: | Admin is Signed In, Notice is already added. | ||||
Post conditions: | Notices are View Shop item / Add Shop item / modify Shop item | ||||
successfully. | |||||
Add Services / View Services / Modify Services
Add Services / View Services / Modify Services
Use Case ID: | UC-8 |
Use Case Name: | Add Services / View Services / Modify Services |
Actors: | Administrator |
Description: | Admin will be able to add a new Add Services / View Services / |
Modify Services to the system. | |
Trigger: | Admin clicks on Add Services / View Services / Modify Services |
button | |
Preconditions: | Admin is Add Services / View Services / Modify Services |
Post conditions: | Event is Add Services / View Services / Modify Services successfully. |
VIEW INVOICES / ADD INVOICES / MODIFY INVOICES
View Invoices / Add Invoices / Modify Invoices
Use Case ID: | UC-9 | ||||
Use Case Name: | Modify Invoices / Add Invoices / View Invoices | ||||
Actors: | Administrator | ||||
Description: | Admin will be able to modify an Modify Invoices / Add Invoices / | ||||
View Invoices news from the system. | |||||
Trigger: | Admin clicks on Modify Invoices / Add Invoices / View Invoices | ||||
button | |||||
Preconditions: | Admin is Modify Invoices / Add Invoices / View Invoices | ||||
Post conditions: | Event is Modify Invoices / Add Invoices / View Invoices successfully. | ||||
More helping material of Automobile workshop Project
- SRS Document of Online Automobile workshop Management system Final Year Project
- Functional Non-Functional Requirements of Automobile workshop Management system
- ERD of Online Automobile workshop Management system [Entity relationship diagram]
- Component diagram of Automobile workshop Management system
- Class diagram of Automobile workshop Management system
- Use Case Descriptions of Automobile workshop Management system
- Download Full code of PHP Source code of Automobile workshop Management system