Performed Student: Tran Thien Thach 8 1.3 Use case description Post condition - Actor login to the system successfully - The system records the successful login activity in the activity
User Requirements
Functional and Non-Functional Requirements
- Functional Requirements indicate what the program or site ought to have the option to accomplish
- Coming up next are a few instances of utilitarian necessities:
+ Client orders will be acknowledged utilizing the web-based application
+ The web application will actually want to handle an exchange
+ The web application ought to give a receipt that incorporates the client's name, the items bought, the expense of every thing, and the general sum
+ The web application will actually want to give deals information on a week by week, month to month, and yearly premise
- Non-practical necessities are the norms that the program or site is needed to meet Reaction time and dependability are instances of non-practical models
- Coming up next are some non-practical requirements for the vehicle shop application:
+ All staff, including agents and chiefs, should have the option to use the internet based application effortlessly
+ The online application will be accessible in an assortment of dialects
+ The web application ought to have the option to deal with a few deals simultaneously without forfeiting speed
Use-Case diagram
Performed Student: Tran Thien Thach 7
Figure 2 :Admin Use Case Diagram
Performed Student: Tran Thien Thach 8
Name Log in Code UC11
Description Allow the actor to log in to the system to use it
Actor Admin and User Trigger Actor presses log-in button
Pre-condition - User created an account
- The user's device is already connected to the internet before logging in Post condition - Actor login to the system successfully
- The system records the successful login activity in the activity log
Main Flow: Log out successfully
- Actor enters account and press Login button
2 - The system authenticates the login information and allows the actor to access and use it
- The system records successful logging in Activity Log Table 2 Activities
Message when the actor presses the Login button: