Group-16.pptx-hxl-css-mmmlmaocuoiia1tram

skilibitolet ....................

1. Architecture Design Project: Car rental app Mentor : Nguyen Manh Duc Project team : Group 16 Team members: Nguyen Hong Quan (100%) Huynh Tan Phat (90%) Thai Quang Hoa (70%) Nguyen Quang Doanh (40%)

2. MAIN CONTENT INTRODUCTION PROJECT STATEMENT ARCHITECTURE DRIVERS CONTRAINS HIGH LEVEL ARCHITECTURE

3. 1.Introduction 1.1 Purpose • Help dealers, shop owners or managers keep track of the number of rented tourist cars and how many have not been rented so that they can notify customers when they come to use the service. • Help customers rent a car conveniently and quickly • Ensure the database has high security and reliability.

4. 2. Project statement 2.1 Project Overview Project name: Car rental App Development team : Full name Position Nguyen Hong Quan Scrum Master Huynh Tan Phat Product Owner Thai Quang Hoa Scrum Member Nguyen Quang Doanh Scrum Member

5. 2. Project statement 2.2 Business Driver 2.2.1 Business Problems In today's time, the demand for transporting goods is increasing , but often there are many problems such as means, manpower or delivery time. Not much approach to delivery car rental owners. Small items are easy and fast to transport, but with many items, transportation is very difficult. And that usually takes a lot of time.

6. 2. Project statement 2.3 Project Goals When users use our car rental app, it can help: Help car renters save time, money, search for car rental houses Create an environment where tenants and tenants can communicate with each other

7. 2. Project statement 2.3 Business Driver 2.2.3 Business Need Customers need a freight car rental app to handle the follow: Search for transport vehicles Compare the price range with other vehicles Payment online Post car rental advertisements Vehicle management Invoice Management

8. 3 . Architecture Drivers 3.1 System Context

9. 3. Architecture Drivers The renter, they can: Booking Car Make contract renting car The car owner, they can: Upload , update, delete car Upload post , delete car Accept contract renting car System context description:

10. 3. Architecture Drivers 3.2 Architecture Driver Specification Use Case Entities ID E01 Title Renter Description Renter is a person who using the system Provides Assumptions Provide requests to the owner Requires Assumptions Already have a default account

11. 3. Architecture Drivers 3.2 Architecture Driver Specification Use Case Entities ID E02 Title Owner Description Owner is a person who using the system Provides Assumptions Provide person’s information (optional) Requires Assumptions Already have a default account

12. 3. Architecture Drivers 3.2 Architecture Driver Specification

13. Operational Use Cases ID UC01 Title Login Description User want to login into the system Entities Involved E01, E02 Preconditions Already have an account and activated Primary Flow 1. Navigate to /login in browser 2. Type user’s credentials to login form. 3. Submit form by pressing Enter key or Sign In Alternate Flows In step 1 of the Primary Flow, if the system has problem, it will show error message. In step 2, 3 of the Primary Flow, if the system has a problem, it will show error messages.

14. Operational Use Cases ID UC02 Title Register Description User is already register Entities Involved E01, E02 Preconditions User is not log in into system. Primary Flow 1. Navigate to /register in browser 2. Type user’s credentials to register form. 3. Submit form by pressing Enter key or Sign Up Alternate Flows - In step 1 of the Primary Flow, if [ Phone number ] is not match format or is exist. The system will prompt user “ Phone number is exist” or “not correct format”. -In step 2, 3 of the Primary Flow, if the system has a problem, it will show error messages.

15. Operational Use Cases ID UC03 Title Log out Description User want to log out the system Entities Involved E01, E02 Preconditions User is already logged in Primary Flow Navigate to / log out in the browser Submit button “Log out” Navigate to /log in in the browser Alternate Flows - In step 1 of the Primary Flow, if the system has problem, it will show error message. In step 2, 3 of the Primary Flow, if the system has a problem, it will show error messages.

16. Operational Use Cases ID UC04 Title Forgot password Description User want to forgot password Entities Involved E01, E02 Preconditions User is already logged out Primary Flow 1. Click the "forgot password" check box 2. Navigate to forgot password page 3. Enter phone number 4. Enter the OTP sent to your phone 5. Enter a new password 6. Confirm Password Alternate Flows - In step 1 of the Primary Flow, if the system has problem, it will show error message. In step 2, 3 of the Primary Flow, if the system has a problem, it will show error messages.

17. Operational Use Cases ID UC05 Title Search car Description Renter want to search car in the system Entities Involved E01 Preconditions Renter is already login Primary Flow 1. Enter the current address 2. Select vehicle items by price, size 3. Enter the address you want the car to go to 4. Submit button “ search ” Alternate Flows - In step 1 of the Primary Flow, if the system has problem, it will show error message. In step 2, 3 of the Primary Flow, if the system has a problem, it will show error messages.

18. Operational Use Cases ID UC06 Title Booking car Description Renter want to boo king car in the system. Entities Involved E01 Preconditions Renter is already logged in Primary Flow 1. Display the list of active vehicles 2. Select vehicle and press "View" button 3. Select payment method 4. Submit button "Place a car" Alternate Flows - In step 1 of the Primary Flow, if the system has problem, it will show error message. In step 2, 3 of the Primary Flow, if the system has a problem, it will show error messages.

19. Operational Use Cases ID UC07 Title Cancel car Description Renter want to cancel car in the system. Entities Involved E01 Preconditions Renter is already logged in Primary Flow 1. Navigate to the booked vehicle listing page 2. Click on the car you want to cancel 3. Write the reason why 4. Submit button "Cancel" Alternate Flows - In step 1 of the Primary Flow, if the system has problem, it will show error message. In step 2, 3 of the Primary Flow, if the system has a problem, it will show error messages.

20. Operational Use Cases ID UC08 Title Bank connection Description Renter want to bank connection link in the system Entities Involved E01 Preconditions Renter is already logged in Primary Flow 1. Navigate to/link in browser 2. Select the bank you want to link 3. Enter the OTP sent to your phone 4. submit button "Confirm" Alternate Flows - In step 1 of the Primary Flow, if the system has problem, it will show error message. In step 2, 3 of the Primary Flow, if the system has a problem, it will show error messages.

21. Operational Use Cases ID UC09 Title Payment Description Renter want to payment in the system Entities Involved E01 Preconditions Renter is already logged in Primary Flow 1. Navigate to / checkout in the browser 2. Method selection 3. Select the bank to pay 4. Navigate to/transfer information in the browser 5. Enter information 6. Confirm OTP 7. Booking confirmation Alternate Flows - In step 1 of the Primary Flow, if the system has problem, it will show error message. In step 2, 3 of the Primary Flow, if the system has a problem, it will show error messages.

22. Operational Use Cases ID UC10 Title Comment Description User want to comment in the system Entities Involved E01,E02 Preconditions User is already logged in Primary Flow 1. Navigate to the review page 2. Enter the information to be evaluated 3. Submit button "Send" Alternate Flows - In step 1 of the Primary Flow, if the system has problem, it will show error message. In step 2, 3 of the Primary Flow, if the system has a problem, it will show error messages.

23. Operational Use Cases ID UC11 Title Post car Description Owner want to post car in the system . Entities Involved E02 Preconditions Owner is already logged in Primary Flow 1. Navigate to/post car in browser 2. Enter vehicle information (price, address) 3. Upload pictures of the car 4. Submit button "Add" Alternate Flows - In step 1 of the Primary Flow, if the system has problem, it will show error message. In step 2, 3 of the Primary Flow, if the system has a problem, it will show error messages.

24. Operational Use Cases ID UC12 Title Delete car Description Owner want to delete car in the system . Entities Involved E02 Preconditions Owner is already logged in Primary Flow 1. Navigate to/manage cars in the browser 2. Select vehicle to edit 3. Enter the information to be corrected 3. Submit "Success" button Alternate Flows - In step 1 of the Primary Flow, if the system has problem, it will show error message. In step 2, 3 of the Primary Flow, if the system has a problem, it will show error messages.

25. Operational Use Cases ID UC13 Title Edit car Description Owner want to edit car in the system . Entities Involved E02 Preconditions Owner is already logged in Primary Flow 1. Navigate to /schedule/vote in browser 2. Click “final option” button Alternate Flows - In step 1 of the Primary Flow, if the system has problem, it will show error message. In step 2, 3 of the Primary Flow, if the system has a problem, it will show error messages.

26. Operational Use Cases ID UC14 Title Cancel booking car Description Owner want cancel booking car for some reason Entities Involved E02 Preconditions Owner is already logged in Primary Flow 1. Navigate to /order in browser 2. Select the vehicle to cancel 3. Enter the reason to cancel 4.Confirmation Alternate Flows - In step 1 of the Primary Flow, if the system has problem, it will show error message. In step 2, 3 of the Primary Flow, if the system has a problem, it will show error messages.

27. Operational Use Cases ID UC15 Title Feedback Description User want to feedback about service in the system Entities Involved E01,E02 Preconditions User is already logged in Primary Flow 1. Navigate to /feedback in browser 2. Enter the information that needs feedback 3. Submit button "Success" Alternate Flows - In step 1 of the Primary Flow, if the system has problem, it will show error message. In step 2, 3 of the Primary Flow, if the system has a problem, it will show error messages.

28. 3. Architecture Drivers 3.3 Quality Attributes

29. Performance: Scenario P1 Attribute concern The response time of inspection function Description When a car renter moves in looking for a car to move in, the list must appear in 7 seconds Stimulus: An action to find car to carry funiture Source of Stimulus: Car renter Environment: Normal activity system and network speed is stable Artifact: System Responses Less than 7 seconds Response Measure: Execution time

30. Performance: Scenario P2 Attribute concern The response time of inspection function Description When the user uses banking to pay, there will be an OTP code sent in 5 seconds Stimulus: User uses banking to pay Source of Stimulus: Car renter Environment: Normal activity system and network speed is stable Artifact: System Responses Less than 5 seconds Response Measure: Execution time

31. Performance: Scenario P3 Attribute concern System load capacity Description There are 1000 users accessing at the same time Stimulus: U ser access to system Source of Stimulus: User Environment: Normal activity system and network speed is stable Artifact: System Responses If more than 1000 people, there will be a queue waiting for the other person to disconnect, then add Response Measure: Wait notice

32. Performance: Scenario P4 Attribute concern The response time of inspection function Description When the user uses banking to pay, there will be an OTP code sent in 5 seconds Stimulus: U ser uses banking to pay Source of Stimulus: Car renter Environment: Normal activity system and network speed is stable Artifact: System Responses Less than 5 seconds Response Measure: Execution time

33. Reliability: Scenario P5 Attribute concern System responsiveness Description When the user uses banking to pay if the otp code is not used then die in 2 minutes Stimulus: U ser uses banking to pay Source of Stimulus: Car renter Environment: Normal activity system and network speed is stable Artifact: System Responses If the user enters the OTP code in 2p, the payment will be accepted, otherwise, the payment will be rejected Response Measure: Notice of acceptance or rejection

34. Security: Scenario P6 Attribute concern Accessibility of the system Description When users want to book a car, or upload a post, they must log in to the system Stimulus: Users use the system to interact Source of Stimulus: Renter, Owner Environment: Normal activity system and network speed is stable Artifact: System Responses If the user is logged in, they will be able to operate on the system, if not logged in, the system will respond to force the user to log in. Response Measure: Notice of acceptance or rejection

35. 4. contraints 4.1 Business Contrainst Project will be started on: 20 – April– 2020. Project will be finished on: 25 – July– 2020. Project will be finished in 100 days (hours ). 4.2 Technical Contraint Technology: Python (Django 3.9 Framework), Vue , HTML , CSS, Bootstrap. Environment: Operating System: Windows, Linux, macOS , any device used Web Browser. Source version control: Git ( Github ). Database : MySQL Database. Internet Connection.

36. 5 . High level architecture 5.1 Component and Connector view (C&C view)

37. 5 . High level architecture 5.2 Module view

38. 5 . High level architecture 5.3 Allocation view win 7, android 5.0 ,ios 7 request

39. Thank you for watching