Group-16.pptx-hxl-css-mmmlmaocuoiia1tram

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%)

MAIN CONTENT
1. INTRODUCTION
2. PROJECT STATEMENT
3. ARCHITECTURE DRIVERS
4. CONTRAINS
5. HIGH LEVEL ARCHITECTURE

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.

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

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.

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

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

3.1 System Context

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:

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

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

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.

ID UC02
Title Register
Description User is already register
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
error messages.

ID UC03
Title Log out
Description User want to log out the system
Preconditions User is already logged in
Primary Flow 1. Navigate to / log out in the browser
2. Submit button “Log out”
3. Navigate to /log in in the browser
Alternate Flows - In step 1 of the Primary Flow, if the
message.
error messages.

ID UC04
Title Forgot password
Description User want to forgot password
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
message.
error messages.

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”
message.
error messages.

ID UC06
Title Booking car
Description Renter want to booking car in the
system.
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"
message.
error messages.

ID UC07
Title Cancel car
Description Renter want to cancel car in the
system.
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"
message.
error messages.

ID UC08
Title Bank connection
Description Renter want to bank connection link in
the system
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"
message.
error messages.

ID UC09
Title Payment
Description Renter want to payment in the system
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
message.
system has a problem, it will show error
messages.

ID UC10
Title Comment
Description User want to comment in the system
Entities Involved E01,E02
Primary Flow 1. Navigate to the review page
2. Enter the information to be
evaluated
3. Submit button "Send"
message.
error messages.

ID UC11
Title Post car
Description Owner want to post car in the system.
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"
message.
error messages.

ID UC12
Title Delete car
Description Owner want to delete car in the system.
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
message.
messages.

ID UC13
Title Edit car
Description Owner want to edit car in the system.
Primary Flow 1. Navigate to /schedule/vote in
browser
2. Click “final option” button
message.
messages.

ID UC14
Title Cancel booking car
Description Owner want cancel booking car for
some reason
Primary Flow 1. Navigate to /order in browser
2. Select the vehicle to cancel
3. Enter the reason to cancel
4.Confirmation
message.
messages.

ID UC15
Title Feedback
Description User want to feedback about service in
the system
Entities Involved E01,E02
Primary Flow 1. Navigate to /feedback in browser
2. Enter the information that needs
feedback
3. Submit button "Success"
message.
messages.

3.3 Quality Attributes

• 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

• Performance:
Scenario P2
Attribute concern
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
Environment:
speed is stable
Artifact: System

• Performance:
Scenario P3
Attribute concern System load capacity
Description
There are 1000 users accessing at the
same time
Stimulus: User access to system
Source of Stimulus: User
Environment:
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

• Performance:
Scenario P4
Attribute concern
function
Description
When the user uses banking to pay,
there will be an OTP code sent in 5
seconds
Environment:
speed is stable
Artifact: System

• 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
Environment:
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

• 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:
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

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.

5.1 Component and Connector view (C&C view)

Group-16.pptx-hxl-css-mmmlmaocuoiia1tram

5.2 Module view

5.3 Allocation view
win 7, android
5.0 ,ios 7
request

Group-16.pptx-hxl-css-mmmlmaocuoiia1tram

More Related Content

Similar to Group-16.pptx-hxl-css-mmmlmaocuoiia1tram (20)

Recently uploaded (20)

Group-16.pptx-hxl-css-mmmlmaocuoiia1tram