The given images are an example of Usecase templates for delete information. Create the same usecase template for Sign up, Login , View profile as An admin, confirm order, cancel order. (for an application where we are trading with any product online.) I mean to say our project is to create an application work like same as Daraz etc. So
remove Use case ID: 001 Use case Name: Delete Information Priority Medium // Choose one among Low/medium/ bigh Primary Actor: User Other Participating Actors: None // Write if other actors are invlolved along with the primary actor, in case of no actor involved simply write 'None". Source: Requirement - FR-01 // REQ CAN BE 1 OR MORE THAN 1 Requirement - FR-02 Use Case Summary Deleting information allows the user to permanently information from the system. Deleting information is only possible when the information has not been used in the system. Pre-condition: Information was previously saved to the system and a user needs to permanently delete the information. Normal Course of Events Alternate Path 1. The use case starts when the user wants to delete an entire set of information such as a user, commission plan, or group. 2. The user selects the set of information that he/she would like to delete and directs the system to delete the information. - Exception2a, 2b 3. The system responds by asking the user to confirm deleting the information. 4. The user confirms deletion. 4a 4a: If the user does not confirm deletion, the information does not delete. 4b: Uses: Cancel Action 5. A system responds by deleting the information and notifying the user that the information was deleted from the system. 6. Uses: Record Transaction 7. This use case ends. // Make a habit of writing a proper ending line. Conclusion This use case concludes when the user receives confirmation of information deletion. // output of system for the actor Word Post Conditions The information is no longer available anywhere in the system. Implementation constraints and specifications Use case must be available to the user 24 * 7. This use case must support up to 100 concurrent members. // think of constraint NFR's Use Case Cross References Includes Record Transactions, Cancel Action Extends None // Always mention includes and extends, in case of no use case being included write "None" Exceptions // will be thrown by the system 2a. The system will not allow a user to delete information that is being used in the system. 2b. The system will not allow a user to delete another user that has subordinates. remove Use case ID: 001 Use case Name: Delete Information Priority Medium // Choose one among Low/medium/ bigh Primary Actor: User Other Participating Actors: None // Write if other actors are invlolved along with the primary actor, in case of no actor involved simply write 'None". Source: Requirement - FR-01 // REQ CAN BE 1 OR MORE THAN 1 Requirement - FR-02 Use Case Summary Deleting information allows the user to permanently information from the system. Deleting information is only possible when the information has not been used in the system. Pre-condition: Information was previously saved to the system and a user needs to permanently delete the information. Normal Course of Events Alternate Path 1. The use case starts when the user wants to delete an entire set of information such as a user, commission plan, or group. 2. The user selects the set of information that he/she would like to delete and directs the system to delete the information. - Exception2a, 2b 3. The system responds by asking the user to confirm deleting the information. 4. The user confirms deletion. 4a 4a: If the user does not confirm deletion, the information does not delete. 4b: Uses: Cancel Action 5. A system responds by deleting the information and notifying the user that the information was deleted from the system. 6. Uses: Record Transaction 7. This use case ends. // Make a habit of writing a proper ending line. Conclusion This use case concludes when the user receives confirmation of information deletion. // output of system for the actor Word Post Conditions The information is no longer available anywhere in the system. Implementation constraints and specifications Use case must be available to the user 24 * 7. This use case must support up to 100 concurrent members. // think of constraint NFR's Use Case Cross References Includes Record Transactions, Cancel Action Extends None // Always mention includes and extends, in case of no use case being included write "None" Exceptions // will be thrown by the system 2a. The system will not allow a user to delete information that is being used in the system. 2b. The system will not allow a user to delete another user that has subordinates
