Final 622 Presentation

EU – Rent Car Rentals

Group 4Padmini Chilappagari

Sayali JaitpalShikinah Dekkapaty

George Mason University

INFS 622Dr. Larry Kerschberg

CONTENTS INTRODUCTION EXISTING SYSTEM PROBLEMS IDENTIFIED IN EXISTING SYSTEM PROPOSED SYSTEM MAJOR REQUIREMENTS IDENTIFIED COST ANALYSIS STAKEHOLDERS, RESPONSIBILITIES AND DEPENDENCIES CLASS DIAGRAM USE CASE DIAGRAM SEQUENCE DIAGRAM FOR A MAJOR USE CASE OBJECT STRUCTURING DIAGRAM SYSTEM ACQUISITION STRATEGY ALTERNATIVE MATRIX RECOMMENDED SYSTEM ARCHITECTURE DESIGN HARDWARE AND SOFTWARE SPECIFICATION USER INTERFACE DESIGN AND EVALUATION PROGRAM DESIGN DATA STORAGE DESIGN

INTRODUCTION

The EU Car Rentals is a car rental agency that earlier had a manual system to reserve and rent vehicles.

This posed several complications to the users.

Hence based on the problems and the requirements it has been decided that employing an Online Reservation System would be a more efficient mechanism for the customers to make reservations.

This project consists of all the designing aspects that have been involved in developing this system.

EXISTING SYSTEM

EU-Rent Car Rentals provides car rental services for customers across the globe.

The rental company uses a manual system for renting, registering and to keep record of all the rental activities, database updates and customer information.

PROBLEMS IN EXISTING SYSTEM

The customer has to personally visit the branch for making a reservation which would waste his/her resources such as time and money.

The branch may not be able to manage many customers at a given time.

The customers may not get access to the branch 24 hours and 7 days a week.

The customer history and reservation information may get misplaced and will be difficult to locate in case of huge collection of data.

It would be difficult for the manager/booking clerk to monitor the status of vehicles manually due to heavy load of reservations.

There is a chance of human errors due to manual record maintenance.

PROPOSED SYSTEM

A completely automated system wherein reservations can be done online through the company website.

A customer can register for a vehicle from anywhere around the globe.

The payments can be done online.

The customer can have access to the website 24 hours and 7 days a week.

As the system is completely online, it can handle up to 500 simultaneous customers.

There is lesser chance of misplacing the customer and reservation records due to automation of the system database.

Lesser chances of human errors.

Monitoring the reservations would be easier.

MAJOR REQUIREMENTS IDENTIFIED

User requirements:

• The customer must create a username and password before accessing the system.• The customer must specify the branch from which the pickup is expected.• The customer must specify the date and time of car reservation for pickup.• The customer must specify the duration for which the car will be rented.• The customer can make multiple reservations of cars.

Functional requirements:

• The system must allow the customer to register for making a vehicle reservation.• The system must allow the customer to view detail description of vehicles.• The system must check for the branch selected whether it has an availability of the car in the particular

car group that the user asks for in the particular time period.• The system should notify if a particular vehicle requested is not available.• The system should not allow booking of a car more than once in a day.

Non-functional requirements:

• The system will run on Windows or Mac OS.• The system will run on Google chrome, Firefox, Safari, Opera and Internet Explorer.• The system must provide help guidelines to assist the users in navigating the web application.• Any interaction between the user and the system should not exceed 5 seconds.• The system should be available for use 24 hours, 365 days per year.

Business requirements:

• The overall budget of the company should not exceed 15 million dollars.• The company should give high priority to customer satisfaction.• Each branch should try to reach the performance targets at the end of every 6 months.• If the performance targets are not met, control action such as changing resources, responsibilities or

operational guidance must be taken.

COST ANALYSISBenefits 2015 2016 2017 2018 2019 Increased reservations & sales 4809000 4951000 5352000 5420000 Reduced maintenance costs 50000 50000 50000 50000 Reductions in inventory 60000 60000 60000 60000 Reductions in IT costs 10000 8000 7000 70000Total Benefits 4929000 5069000 5469000 5600000Costs Development Costs Purchase of cars 10,125,000 0 0 0 0 Office premises and eqipment 100000 0 0 0 0 Building an online system 15000 0 0 0 0 Salary to employees 600000 0 0 0 0 Total Development Costs 10,840,000 0 0 0 0Operational Costs Communication charges 0 10000 10000 10000 10000 Employee salaries 0 400000 400000 400000 400000 Website maintenance 0 1000 1000 1000 1000 Acquiring new cars 0 50000 60000 64000 66000 Total Operational Costs 0 461000 471000 475000 477000Total Costs 10,840,000 461000 471000 475000 477000Total Benefits-Total Costs 10,840,000 4468000 4598000 4994000 5123000Cumulative Net Cash Flow -10840000 -6362000 -1764000 3230000 8353000Return on Investment (ROI) 66%Break-even Point 2+(0.35)=2.35 years

STAKEHOLDERS, RESPONSIBILITIES AND DEPENDENCIES

CLASS DIAGRAM

USE CASE DIAGRAM

SEQUENCE DIAGRAM FOR A MAJOR USE CASE

OBJECT STRUCTURING DIAGRAM

SYSTEM ACQUISITION STRATEGY

Chosen strategy Custom Application development (PHP)

Alternatives:

• Custom Application Development using Java• Packaged Software- Eclipse

Criteria Considered:

• Developing In- house skills• Prior experience• Budget• Customization• Time

ALTERNATIVE MATRIX Evaluation Criteria Relative

ImportanceAlternative 1:

Custom Application using

Java

Score Weighted score Alternative 2: Custom

Application using PHP

Score Weighted score Alternative 3:Packaged

Software Product-Mobile Application

Score Weighted score

Technical Issues:                    Develops In-house

skills20 Developed in Java.

So would help in developing In-

house skills

4 80 Developed using PHP. Helps in developing in-

house skills

5 100 Developed using Eclipse. Not very

helpful in developing In-

house skills

3 60

Integration with existing systems

10 Sends confirmations through email.

4 40 Uses database management to keep record of

orders

4 40 Email and database 4 40

Prior Experience 20 Well experienced 4 80 Well experienced 5 100 Not very well experienced

3 60

Economic Issues                    Budget 20 $5000 initialfee+

$2000/yr2 40 $4000 initial cost+

$2000/yr4 80 $2000 initial cost +

$500/yr5 100

Organizational Issues

Customizable Interface

15 yes 3 45 Yes, easy 4 60 Yes and very easy 5 75

Time 15 Does not take much time

4 60 Takes little tome 4 60 Takes very little time

5 75

                     Total 100     345     440     410

RECOMMENDED SYSTEM ARCHITECTURE DESIGN

Thin Client-Server architecture Highly useful for web based applications as only a small portion of application logic resides on the

client. Amazon Relational Database Service – database implementation. RDS provides six familiar database engines to choose from.

Steps in designing architecture:

Refine non functional requirements into more functional requirements.

Operational requirements:

-> Technical requirements: Web based system, Compatible with different OS.-> System Integration requirements: Frequent code changes during integration->Portability requirements: Portable on other OS, change in programming language->Maintainability requirements

Performance requirements:

->Speed requirements: Minimal load time, response time , SSD-backed storage - RDS->Capacity Requirements: Estimated number of users, AWS Data storage architecture ->Availability and Reliability Requirements: 24*7 availability, Failure recovery – RDS

Security requirements:

->System Value Requirements No system outages, crashes->Access Control Requirements: Restricted database access->Encryption and Authentication Requirements: Data encryption

Cultural/Political Requirements

->Multilingual Requirements->Customization Requirements: Flexible to custom changes->Making Unstated Norms Explicit: Stating norms – tool in different laguages->Legal Requirements: Encryption of state id details, Amazon Virtual Private Cloud -RDS

HARDWARE AND SOFTWARE SPECIFICATION

USER INTERFACE DESIGN AND EVALUATION

• Web Application and a Mobile Application.

• Software Used: Web App: Moqups Mobile App: UI Design: Android Studio• Evaluation strategy: Heuristics Evaluation

Web App Interface

INTERFACE STRUCTURE DIAGRAM

PROGRAM DESIGN

Human machine boundaries

PROGRAM DESIGN

Structure chart diagram

DATA STORAGE DESIGN

REFERENCES

A. Dennis, B. H. Wixom, and R. M. Roth. Systems Analysis and Design. 6th ed. John Wiley & Sons, n.d.Hassan Gomaa. Software Modeling and Design, n.d.“Reference for information on Amazon RDS,” n.d. https://aws.amazon.com/rds/Video for Amazon Architectures, n.d. https://www.youtube.com/watch?v=jOhbTAU4OPI&list=PL4ePDvEWFtXgD5QgImq1x23sImUL26OjN.“Reference for Understanding Client Server Architecture,” n.d. https://en.wikipedia.org/wiki/Thin_client.“Tool Link Used for Creating Interface Structure Diagrams (ISD),” n.d. http://logomakr.com/1dfVDO.“Tool Link Used for Creating Interface Structure Diagrams (ISD),” n.d. https://moqups.com/