System Analysis and Design

profileCaasey@98
DFWAIRPORTVALETAPP.docx

DFW AIRPORT VALET APP

FINAL REPORT

GROUP 1

08/03/2021

GROUP MEMBER:

KAMAL JOSHI

DEELIP CHHETRI

SAURAV THAPA

PUJA PARAJULI

SAGAR GURUNG

Table of Contents

Category:

Part 1: Planning

1.1 Introduction……………………………………………………………………………….

1.2 System Request……………………………………………………………

1.3 Feasibility Analysis……………………………………………………………………….

1.4 Requirements Definition……………………………………………………

Part 2: Analysis

2.1 Activity Diagram…………………………………………………………………………..

2.2 Use Case Diagram………………………………………………………………………..

2.3 Use Case Descriptions………………………………………………………………….

2.4 Class Diagram……………………………………………………………………..

2.5 Sequence Diagrams………………………………………………………………………..

Part 3: Design

3.1 Final Class Diagram………………………………………………………………………..

3.2 Package Diagram……………………………………………………………………………

3.3 Database Design…………………………………………………………………………….

3.4 Data Access and Manipulation Design……………………………………………

Introduction

It is an advantage to have the option to simply drive up to the curbside, leave your vehicle and catch a flight and when you return your vehicle is all set for you. This paper has presented a smart solution for valet customer can stop in an airport terminal where the intention is to drop your car in the terminal where your flight is a departure and when you return your car is ready to pick up whichever terminal your flight is landed.

Through this app, the client can do the reservation and get a confirmation email with clear instructions. They can scan the barcode or provide a ten-digit reservation number which is provided in the email. They can also show the QR code through the DFW airport valet apps while check-in process.

In this system, when customer do a reservation, they need to provide your name, phone number, vehicle information such as make, model, color, and license plate number. They also need to provide a departing and arrival flight number as well as a date and time. For the existing customer, the app will track them through their license plate number. Also through this app, the customer can easily update or cancel their reservation.

The app will track and monitor the record of the customer flight information and when the customer arrives at the requested terminal, the valet staff will take the vehicle of the customer to the respected terminal. Finally, when the transaction is completed, the app will automatically send the email receipt to the customer’s email.

System Request – DFW Airport Valet APP

Project Sponsor – Sam Smith Jr.

Business Need – This project will create a smart solution for the DFW airport customer to use a valet service.

Business Requirement: Customers can do a reservation for DFW Airport valet through this app. They can choose the terminal to drop off their vehicle. The customers, as well as the administrator, can access the system.

For Users:

· Availability of parking spots

· Reserve with DFW airport valet.

· Rate per day

· Insurance Policy

· Car wash options

· Vehicle servicing

For Admins:

· Allow admin to update the customer information as required.

· Allow admin to track the flight information of the customers.

· Allow admin to track the number of incoming and outgoing customers.

· Provide detailed information for drop-off pick up the vehicle. 

Business Value:

· If convenience is your top priority or if you want a covered protected environment, valet is the right option.

· Safe and secure airport parking by using this service. 

· Save customer time by providing fast and excellent service.

· Keeps the customer’s information confidential.

· Provide other facilities to the customers such as car washes, detailing, and maintenance, etc.

· Provide a smoother entry and exit for convention customers. 

Special Issues or Constraints:

· Damage car of the customer will go through inspection and maintenance. 

· Potential lags and glitches in the valet apps.

· The valet server may be down causing a login issue.

Dfw valet feasibility Analysis executive summary

Our development team including our project sponsor Sam Smith Jr. has created a feasibility analysis summary of the DFW Airport valet app. Below are the following key points of the feasibility analysis:

Technical feasibility:

· The app is friendly on both iOS and android.

· Our DFW valet app is based on java programming and database SQL. 

· The IT department has strong experience in coding and app developments.

·  Determines whether the app is stable and establish.

· Functionality and interoperability areas for applicable customers and security for unauthorized users.

· The analyst determines whether current technical resources can be upgraded and fulfill the new requirements.

Management experience:

· There are 7 team members in the management fields and currently, there are 50 employees. As the business rises, the employee also will be added.

· Our marketing team has good experience with the marketing major and different marketing strategies are introduced.

· Technical analysts are handled by our Computer Science major team 

Economic feasibility:

· A cost-benefit analysis was done by researching other valet company’s sales data. 

· There is potential to turn out the business to profit, and it is economically feasible by doing the analysis and research. 

· There is a great possibility of profitable business because the rates of our valet service are low in comparison to the other valet companies.

Identifying Costs and benefits:

Development and operational cost - Hardware and software, data conversion cost, Team salaries, hardware, and software upgrades cost.

Intangible benefits - High-quality services, excellent customer services, increased brand recognition, and knowledgeable staff.

Organizational feasibility: 

· Our project has very little risk. The main objective of this project is to provide valet service to the DFW airport customers by the good lineup with the top senior management’s goal. 

· Valet application is used in Android / iOS that helps in marketing goals.

· The team has assigned a specific deadline and the goal for the project to be finished and follows the regular feedback from the teams.  

· Our project sponsor Mr. Sam Smith Jr. has support with the time and resources and provides the full knowledge to the senior management team when required.  

· The customers and the user of this application appreciate the benefits of the valet services.

·

Requirements Definition

Nonfunctional requirements: 

1. Operational Requirements:

· Customers can operate this app on iOS and Android.

· The apps will store the data and information of all the customers in the system (e.g., name, phone number, reservation number, flight information, vehicle information, price, etc.) 

2. Performance Requirements:

· Multiple requests will handle by the server of the application.

· The application should respond to new reservation detail of customers within 3 seconds or less. 

· 95% of the response time should be less than 3 seconds or less. 

· The application should be able to help to get real-time customer feedback. 

 

3. Security Requirements:

· The system of this application will be tested once a week. 

· The authorized person can only access the data and services of the system. 

· The system will automatically detect the interference of unauthorized persons.

· The system will keep the confidential data private.

· The system will not disturb the security process during maintenance.

 

4. Cultural and Political Requirements:

· No special cultural and political requirements are anticipated. 

Functional requirements:

1. Search App:

· For quick and easy service customers will search the valet app and download it on their iOS and Android devices. 

· The app will provide basic information about the system and service of the valet. 

2. Create Account:

· The system will allow the user to create an account by using their email and phone number. 

· The registration system will help the customers to fill up their information and click the submit button. 

· The system will send the verification code to the respective email or phone number for the verification process.

 

3. Login:

· The user will log in by using their email address or phone number as a username and password. 

· The system will allow the user to reset their password by click on “forgot password” and receiving a link to their verified email. 

· The user will fill up the required information such as name, phone number, email address, etc. 

 

4. Check-In:

· The customers will show their reservation number or barcode. 

· If they don’t have their reservation number they can give their last name or license plate number and the system will pull out the reservation details.

 

5. Drop Off

· The customer will hand over the key and the vehicle. 

· The system will generate the claim ticket with the barcode which will help the customer to receive their car while checking out. 

 

6. Check Out

· The customer will show the claim ticket to receive their vehicle. 

· The system will automatically calculate and charge the total due amount for the service they used.

· After the payment is processed the customer will get their key and the vehicle.

Analysis

Activity Diagram

The diagram shown below is the first part of our analysis. When user access with the app, they can login. When they login with the app, the system checks the account if the account is valid or not. Then, the customer can do the reservation or update or cancel the reservation. If the customers do the reservation, then they have to set a drop off date and then set a pickup date. The customer has to put the credit card information so that we can do the reservation.

Diagram  Description automatically generated

USE CASE DIAGRAM

For the system we use 6 cases, and they are as follows:

· Login

· Create account

· Search for detail

· Select drop off date

· Select pickup date

· Checkout

Diagram  Description automatically generated

USE CASE DESCRIPTION

Use-case Name: Login

ID: 1 Importance Level: High

Primary Actor: Customer

Use case type: Detail, essential

Stakeholders and interests:

Customer - wants to login

Brief Description:

This use case describes about how the customer login to the system for valet parking.

Trigger:

The user clicks the “Login” button.

Type:

External

Relationships:

Association:

Include: Select drop off date, Select pick up date, Check out

Extend: Create Account

Generalization:

Normal flow of Events:

1. The customer clicks on the “Login” button in home page.

2. The customer enters their login username and password.

3. The username and password are verified in the Customer detail.

4. If account is valid, they can move forward.

5. The customer can now search available parking.

6. The customer clicks the logout button.

7. The customer returns to the homepage.

Sub Flows:

Alternate/exceptional flows:

3a1: The username or password is not valid.

3a2: The system shows an error page.

3a3: The customer returns to the homepage.

3a4: The system shows to create account and customer taken to create account page.

Use-Case Name: Create Account

ID: 2

Importance Level: High

Primary Actor: Customer

Use Case Type: Detail, essential

Stakeholders and Interests:

Customer – wants to create a new account

Brief Description:

This use case describes how the Customer create an account

Trigger:

The customer clicks on the “Create account” button

Type:

External

Relationships:

Association:

Include:

Extend:

Generalization:

Normal Flow of Events:

1. The customer access to the system.

2. The customer clicks on “Create account” button.

3. The customer sees some blanks to type their account information.

4. The customer need to put in required information.

5. The customer clicks on “Submit” button.

6. The customer information is verified.

7. The new account is added to customer detail and show off “Success” message.

8. The customer is taken to login page.

Sub flows:

Alternate/Exception Flows:

5a1: Not all blanks are filled

5a2: Customer will see a page showing error

5a3: Customer is returned to previous page and continue to fill the missing information.

Use-Case Name: Search for Details

ID: 3

Importance Level: High

Primary Actor: New Customer

Use Case Type: Detail, essential

Stakeholders and Interests:

New Customer - To search for valet detail

Brief Description:

This use case describes how New Customer can search for the parking.

Trigger:

New Customer clicks the “Search parking info” button

Type:

External

Relationships:

Association:

Include:

Extend:

Generalization:

Normal Flow of Events:

1. The new customer access the site and “search parking info” button.

2. The new customer look for the parking place if it is in the parking details.

3. If the parking is not available, it takes the customer back to the homepage.

4. If parking is available, the parking is searched from the parking details.

5. Now the parking availability is show off to the new customer.

Sub flows:

Alternate/Exceptional Flows:

3a1: The searching information can not be found in detail.

3a2: New customer will see a page showing error.

3a3: New customer will return to the search details page.

Use-Case Name: Select drop-off date

ID: 4

Importance Level: High

Primary Actor: Customer

Use Case Type: Detail, essential

Stakeholders and Interests:

Customer – wants to drop-off the vehicle

Brief Description:

This use case describes when the customers will come to drop off their vehicle while flying from the airport.

Trigger:

The user clicks on the “Select drop-off date” button

Type:

External

Relationships:

Association:

Include:

Extend:

Generalization:

Normal Flow of Events:

1. Customer asked to select a drop-off date.

2. Customer see the policies and time limits in the system.

3. Then customer enters payment information for the checkout process.

4. Once order is finalized dispatcher will be able to see the flight details.

5. Customer can choose to return to home page.

Sub flows:

Alternate/Exceptional Flows:

3a1: Payment can be invalid.

3a2: Customer will see a page showing error.

3a3: Customer need to put their payment information correctly.

3a4: Customer can choose to return to home page.

Use-Case Name: Select pick-up Date

ID: 5

Importance Level: High

Primary Actor: Customer

Use Case Type: Detail, essential

Stakeholders and Interests:

Customer – want to pick-up the vehicle

Brief Description:

This use case describes that when the customer lands at the airport they will receive their vehicle in designated valet area.

Trigger:

The customer clicks on the “Select pick-up date” button

Type:

External

Relationships:

Association:

Include:

Extend:

Generalization:

Normal Flow of Events:

1. Customer asked to select a pickup date.

2. Customer see the policies and time limits in the system.

3. Then customer enters payment information for the checkout process.

4. Once order is finalized dispatcher will be able to see the flight details.

5. Customer can choose to return to home page.

Sub flows:

Alternate/Exceptional Flows:

3a1: Payment can be invalid.

3a2: Customer will see a page showing error.

3a3: Customer need to put their payment information correctly.

3a4: Customer can choose to return to home page.

Use Case Name: Checkout

ID: 6

Importance: High

Primary actor: Customer

Use case detail: Detail, Essential

Stakeholders and Interest:

Customer - want to check out the vehicle

Brief Description:

This use case describes how the customer go through the checkout process.

Trigger:

The user clicks on the “Check out” button.

Type:

External

Relationship:

Association:

Include:

Extend:

Generalization:

Normal Flow of Events:

1. Customer will receive a reservation bar code.

2. Customer will check all the details of the provided reservation.

3. Customer clicks on the “Submit” button for the final process.

4. The customer is asked to enter their debit/credit card information.

5. After the customer card is approved they will receive the confirmation e-mail.

Sub Flows:

Alternate/Exceptional flows:

1a1: The inputted card number can’t be found in database.

1a2: Customer will see a page showing error.

INITIAL CLASS DIAGRAM

In the initial case diagram, we have produced 6 classes for our project which is shown below:

Logindetail and vehicledetail class is used to connect the system with the detail it needed.

Customer class is used to store the information of the customers.

Reservationdetail class is used to store the details of the customers needed for the reservation.

Paymentdetail class is used to store the payment information.

Diagram  Description automatically generated

SEQUENCE DIAGRAMS

Diagram  Description automatically generated

Diagram  Description automatically generated

Diagram  Description automatically generated

Diagram  Description automatically generated

Diagram  Description automatically generated

Diagram  Description automatically generated

Final class diagram

The final class diagram is slightly different than the initial one.

A connection has been made from VehicleDetail to ReservationDetail class. There is also connection between Reservation and VehicleDetail, also there is a connection between Reservation and PaymentDetail.

Diagram  Description automatically generated

Package Diagram

The Package diagram is shown below

The User, Customer and LoginDetail is packaged together to the User Package. The Reservation, VehicleDetail and ReservationDetail class is packaged together to the ReservationPackage. The PaymentDetail is packaged to the PaymentPackage.

Diagram  Description automatically generated

Database Design

The database design is shown below.

As shown in the diagram below, the ReservationDetail Table is used to be the association table with Reservation Table and VehicleDetail Table.

The Reservation Table contains about the reservation, such as the customer ID, dropoff date, pickup date, total due amount etc. The VehicleDetail Table contains the vehicle type, vehicle make and model, vehicle color, etc. ReservationDetail Table contain about the detail customer reservation.The Customer Table contains the customer information such as User name,User address User email, etc. The Payment Table contain information about the payment card detail.

Diagram  Description automatically generated

Data Access and Manipulation Design

Diagram  Description automatically generated

1

image4.png

image5.png

image6.png

image7.png

image8.png

image9.png

image10.png

image11.png

image12.png

image13.png

image14.PNG

image15.PNG

image16.png

image17.png

image18.png

image19.png

image20.png

image21.png

image22.png

image23.PNG

image24.PNG

image1.PNG

image2.PNG

image3.PNG