Rental Car Management System

Rental Car Management System

Independent University, Bangladesh CSC-445 Software Engineering Spring- 2016

1|Page Rental Car Management System

Final Project -CSC445

Submitted by:

M. Rashed Mahamaud ID: 1320156 Project lead Bachelor in Computer Science

Mir Noor-UL-Haque Pias ID: 1210168 Bachelor in Computer Science

Rayhan Sardar Tipu ID: 1330418 Bachelor in Computer Science & Engineering

Abdul Munim ID: 1621738 Masters in Software Engineering

Golam Rakib ID: 1621707 Masters in Software Engineering

Submitted to: Dr. Mahady Hasan Department of Computer Science & Engineering

2|Page Rental Car Management System

Final Project -CSC445

Table of Contents Overall operational concept of the system. ................................................................................................................ 5 Introduction ................................................................................................................................................................ 5 Currently available Systems ...................................................................................................................................... 5 Problem and difficulties in the current system........................................................................................................... 6 The need of improved distributed services ................................................................................................................ 6 Proposed Envisioned Distributed system with Rich picture .................................................................................. 7 Benefit of the Envisioned/proposed system ........................................................................................................... 8 Analyze the detail requirement and Develop functional and non-functional requirements ....................................... 8 Functional Requirement ......................................................................................................................................... 8 Reservation ........................................................................................................................................................ 8 Vehicle ............................................................................................................................................................... 9 Rent .................................................................................................................................................................... 9 Non-Functional Requirements ............................................................................................................................... 9 Usability ............................................................................................................................................................. 9 Security ............................................................................................................................................................ 10 Performance ..................................................................................................................................................... 10 Availability ...................................................................................................................................................... 10 Architectural design and evaluate benefits as well as liabilities .............................................................................. 10 Detailed description ............................................................................................................................................. 13 Advantages........................................................................................................................................................... 13 Liability ................................................................................................................................................................ 13 End to end Quality Control Process ......................................................................................................................... 13 Test Plan .............................................................................................................................................................. 13 Introduction .......................................................................................................................................................... 13 Project Name .................................................................................................................................................... 13 Project Leads:................................................................................................................................................... 14 Test Project Task.............................................................................................................................................. 14 Defect Tracking and reporting System ................................................................................................................ 14 Testing Synopsis .................................................................................................................................................. 15 Items to be tested Items .................................................................................................................................... 15 3|Page Rental Car Management System

Final Project -CSC445

Items not to be Tested ...................................................................................................................................... 16 Test Environment/System Requirements ............................................................................................................. 16 HARDWARE INTERFACE REQUIREMENTS ............................................................................................ 16 SOFTWARE INTERFACE REQUIREMENTS ............................................................................................. 16 COMMUNICATIONS INTERFACE REQUIREMENTS .............................................................................. 17 Standards/Reference material .......................................................................................................................... 17 Testing Scope ....................................................................................................................................................... 17 Unit Testing ..................................................................................................................................................... 17 Smoke Testing ................................................................................................................................................. 17 Feature level testing ......................................................................................................................................... 17 Functional Tests ............................................................................................................................................... 18 Integration Testing ........................................................................................................................................... 18 System Testing ................................................................................................................................................. 18 Security Testing ............................................................................................................................................... 18 Test Schedule and Resources ............................................................................................................................... 18 Major Activities Schedule:............................................................................................................................... 18 Test Phases and Completion criteria .................................................................................................................... 18 Issues and Risks ................................................................................................................................................... 19 Test Cases Functional .............................................................................................................................................. 19 Work Breakdown Structure of the Rental Car Management System....................................................................... 24 Critical Path ............................................................................................................................................................. 25 Gantt Chart of the Rental Car Management System ................................................................................................ 26

4|Page Rental Car Management System

Final Project -CSC445

Overall operational concept of the system. Introduction This chapter of the project document which provides a general introduction about the Rental Car Management system project. The chapter contains and describes about background of the organization, existing system functions and problems.

This chapter also describes about the proposed system, objective including the general and specific objectives of the project.

Currently available Systems Prime Car Rental (PRC) organization gives car rental service for both foreign and local customers. This organization carries out its daily work by providing; their service to the customers using manually system. The organization uses a manual system for reserving, renting, register and to keep record of all the rental activities and customer information. The detailed existing system functions are listed as follows: -

 During vehicle reservation the customers reserve a vehicle by making a phone call to the organization; otherwise he/she is expected to go to the organization to make reservation.  During renting a vehicle the customer personal information, payments status and rent agreements are filled in the car rent agreement form; in order to hold legal contract between the customer and organization for renting the vehicle.  The organization normal work time schedule is from 8:00am – 11:00pm; therefore the organization gives services for fifteen hours a day. The organization makes a general report about the rented vehicles once at the end of the month and generates a report.

5|Page Rental Car Management System

Final Project -CSC445

Problem and difficulties in the current system The existence system has a number of problems in the working procedure for the organization and customers. These problems are: 1. During reservation a customer reserve a vehicle on phone or expected to go to the organization for reserving. This has its own problem in the business sector.  The organization phone may be busy or may not work when customer is calling to make reservation.  It may be difficult to customers to get the phone number or the location of the organization.  The customers may be resulted to unnecessary extra expense and waste their time.  Their may accrue duplicated reservation of the same vehicle.  The organization may not be able to serve many customers.  The customers may not get service of the organization 24/7 ( twenty four hours a day and seven days a week).

2. During renting a vehicle, the customer information and contract made between them are filled in a form.  The contract form made between the customer and organization may be difficult to find incase of misplacing or disappearing due to massive collection of data. 3. During generating monthly report.  When generating report, it takes time and it may not be easy to manage and analysis the monthly work due to massive collection of data and the generated report may not be accurate.

The need of improved distributed services Following is the need of improved distributed services,  The new system is totally computerized system.  A new system provides features like time efficiency to show car details, user profiles and whatever the customer will give the feedback to the admin.  This system provides tourism and traveling facilities.  An inquiry is easily done by user in the system.  It is the most software application for managing online car rental business.

6|Page Rental Car Management System

Final Project -CSC445

Proposed Envisioned Distributed system with Rich picture

Proposed Envisioned Distributed system with Rich picture

7|Page Rental Car Management System

Final Project -CSC445

Benefit of the Envisioned/proposed system First of all it would be a growth-oriented car rental organization by efficiently serving value-conscious customers for all of their car rental occasions.

Secondly it will consistently deliver a quality product, friendly service and great value that make customers confident that Budget is their best car rental choice.

Analyze the detail requirement and Develop functional and non-functional requirements

Functional Requirement Functional requirements these are statements of services the system should provide, how the system should react to particular inputs, and how the system should behave in particular situations. It specifies the software functionality that the developers must build into the product to enable users to accomplish their tasks.

Reservation

1. 2. 3. 4. 5. 6. 7. 8. 9. 10.

The system must allow the customer to register for reservation. The system shall allow the customer to view detail description of particular vehicle. The system must notify on selection of unavailable vehicles while reservation. The system shall present an option for advanced search to limit the vehicle search to specific categories of vehicles search. E.g. By Brand, Type and Model. The system must view list of available vehicles during reservation. The system shall allow the customers to cancel reservation using reservation confirmation number. The system shall allow the employee to update reservation information. The system shall allow the employee to view reservations made by customers. The system must be able to provide a unique reservation conformation number for all successfully committed reservations. The system must be able to display reservation summary for successfully committed reservation.

8|Page Rental Car Management System

Final Project -CSC445

Vehicle 11. 12. 13. 14. 15. 16.

The system should allow staff to register new vehicles. The system shall allow staff to update information of the vehicle in need of modification. The system shall allow staff to display all lists of vehicle. The system shall allow staff to display all available vehicle. The system shall allow staff to display all rented vehicle. The system shall allow staff to display all off duty vehicles.

Rent 17. 18. 19. 20.

The system shall allow staff to register customers into rental list. The system shall allow staff to update about customer rent record details in the rental list. The system shall allow staff to display customers, who rent vehicles. The system must provide printable summary for successful committed rent.

Non-Functional Requirements Introduction Non-functional requirements, as the name suggests, are requirements that are not directly concerned with the specific services delivered by the system to its users. They may relate to emergent system properties such as reliability, response time, and store occupancy. Alternatively, they may define constraints on the system implementation such as the capabilities of I/O devices or the data representations used in interfaces with other systems. Non-functional requirements, such as performance, security, or availability, usually specify or constrain characteristics of the system as a whole.

Usability  The system provides a help and support menu in all interfaces for the user to interact with the system.  The user can use the system by reading help and support.

9|Page Rental Car Management System

Final Project -CSC445

Security  The system provides username and password to prevent the system from unauthorized access.  The staffs’ password must be greater than eight characters.

Performance  The system response time for every instruction conducted by the user must not exceed more than a minimum of 10 seconds.  The system should have high performance rate when executing user’s input and should be able to provide response within a short time span usually 50 second for highly complicated task and 20 to 25 seconds for less complicated task.

Availability  The system should always be available for access at 24 hours, 7 days a week. Also in the occurrence of any major system malfunctioning, the system should be available in 1 to 2 working days, so that business process is not severely affected.

Architectural design and evaluate benefits as well as liabilities Here we will use Three-tier architecture. Three-tier architecture is a client–server software architecture pattern in which the user interface (presentation), functional process logic ("business rules"), computer data storage and data access are developed and maintained as independent modules, most often on separate platforms.

10 | P a g e Rental Car Management System

Final Project -CSC445

Data services Master DB

Data warehouse

Primary

Slave

DB

DB

Sync Scheduler

DB cluster manager

OLAP providers

Data Provider Bus (DPS)

Agent Directory

Provider profile

Reservation

Vehicle profile

Local DB

Local DB

Local Reservation DB services

Local DB

Agent services

Provider services

Vehicle services

Enterprise System Bus (ESB)

Agent UI services

Provider portal services

Car rent providers Servers

Servers

Load balancer

Load balancer

Car rent providers

Agent 1

Agent 2

Agent 3

Local DB

Local DB

Local DB

11Agent | P1 acustomers ge

Agent Front end

Agent 1 customers

Agent 2 customer

Agent Front end

Agent 2 customers

Rental Car Management System

Agent Front end

Agent 3 customers

Final Project -CSC445

Agent 3 customers

12 | P a g e Rental Car Management System

Final Project -CSC445

Detailed description Central car rental system allows agents to plug-in to the system and allows agents to reserve, look-up, follow-up, track any vehicle associated with the agent. Agent system consumes core UI services for all functional requirements and allows agents create them on application on top of the enterprise stack. Individual providers are also provided with a portal to register and hire-out cars to agents. Provider portal uses core UI services in the ecosystem. Core UI services is loosely coupled in the enterprise stack and only loads the Façade component from enterprise service bus. Enterprise service bus is responsible to handle the downstream system and it only knows which component to consume and interact for certain functionality in the functional requirements. Downstream components i.e. Agent directory, provider profile, vehicle etc. are behind the enterprise system bus and they are loaded in the enterprise stack loosely within the container. Data provider bus encapsulates the data providers and data access are provided by services which only provides CRUD operations. OLAP cubes are created from DB by administrator and synchronized to OLAP cubes periodically.

Advantages     

Enterprise grade solution Very loosely coupled and allows components to be removed and plugged in easily New agents can consume exposed API and get connected to global car rental ecosystem. System designed to handle hundred thousands of requests. Properly designed to encapsulate functional requirement defined for each component.

Liability   

Requires extensive expertise to alter system architecture. Ecosystem is expensive to incorporate in the first phase. Infrastructure is not designed to multi-region and require significant changes to the system design.

End to end Quality Control Process This chapter of the project document provides end to end Quality Control Process.

Test Plan

Introduction Project Name Rental Car Management System 13 | P a g e Rental Car Management System

Final Project -CSC445

Project Leads: 1.1.1.

Project Manager: A. M. Rashed Mahamud

1.1.2.

Development Lead: Md. Golam Rakib

1.1.3.

Test Manager: Mir Noor-UL-Haque Pias

Test Project Task 1.1.4.

Test case design: Mir Noor-UL-Haque Pias

1.1.5.

Test personnel:

1.1.5.1.

1.1.6.

For manual tests: Mir Noor-UL-Haque Pias, Rayhan Sardar Tipu

Documentation reviews: A.M. Rashed Mahamud

Defect Tracking and reporting System 1.1.7. Defects will be tracked by using Black Box method. 1.1.8.

The Defect Tracking method will be accessible by all the members of project development team and test team.

1.1.9.

Unit test of each module will be done by developer and the unit test report will be shared with test team.

1.1.10.

The testing will be start middle of the development that means after develop some features/module we start testing till to end of the UAT according to the testing schedule.

1.1.11.

Bug fixing will be start from 7th April, 2016 and continue till end of the testing.

1.1.12.

Without fixing the bug of any particular module/feature testing will not be completed.

1.1.13.

All test cases will be prepared before start of the testing.

1.1.14.

Test manager review and approved the test cases.

1.1.15.

Test cases may be added during test conducted.

1.1.16.

System test will be performing after full development.

1.1.17.

Test environment, hardware and testable feature/module need to be ready before testing in the test server.

1.1.18.

Test report will be provided after end of the full testing in tracking method.

1.1.19.

If any changes are made to the requirements, design and schedule then immediately need to be informed to the test manager

14 | P a g e Rental Car Management System

Final Project -CSC445

Testing Synopsis Items to be tested Items

Reservation 1. 2. 3. 4. 5. 6. 7. 8. 9. 10. 11.

Customer to register for reservation. View description of particular vehicle. Notify on selection of unavailable vehicles while reservation. Advanced search E.g. By Brand, Type and Model. Select specific vehicle using different search category while reservation. List of available vehicles during reservation. Customers reservation cancel. Update reservation information. Viewing reservations made by customers. Their daily costs, and requests from customer. Displaying reservation summary for successfully committed reservation.

Vehicle

12. 13. 14. 15. 16. 17. 18. 19. 20. 21. 22.

Allow staff to register new vehicles. Allow staff to select vehicles in the list. Allow customer to select vehicles in the list. Allow staff to Search vehicles by specific record. Allow customer staff to Search vehicles by specific record. Allow staff to update information of the vehicle in need of modification. Allow staff to display all lists of vehicle. Allow staff to display all available vehicle. Allow customer to display all available vehicle. Allow staff to display all rented vehicle. Allow staff to display all off duty vehicles.

Rent

23. 24. 25. 26. 27. 28. 29. 30.

Allow staff to register customers into rental list. Allow staff to update about customer rent record details in the rental list. Able to save all changes made on the customer rent list. Allow staff to select customer rent record by specific search category. Allow staff to search rent record of customers using specific categories. Allow staff to display customers, who rent vehicles. Allow staff to display all customers rent record Provide printable summary for successful committed rent.

15 | P a g e Rental Car Management System

Final Project -CSC445

Items not to be Tested

Usability The system provides a help and support menu in all interfaces for the user to interact with the system. The user can use the system by reading help and support.

Security The system provides username and password to prevent the system from unauthorized access. The staffs’ password must be greater than eight characters.

Performance The system response time for every instruction conducted by the user must not exceed more than a minimum of 10 seconds. The system should have high performance rate when executing user’s input and should be able to provide response within a short time span usually 50 second for highly complicated task and 20 to 25 seconds for less complicated task.

Availability The system should always be available for access at 24 hours, 7 days a week. Also in the occurrence of any major system malfunctioning, the system should be available in 1 to 2 working days, so that business process is not severely affected.

Test Environment/System Requirements HARDWARE INTERFACE REQUIREMENTS ID #

Hardware Component

Requirement

HI-1

DMZ Server (for Public Interface / Web Server)

2 CPU, 8 GB Memory

HI-2

Internal Box (Service API, DB & Others)

2 CPU, 8GB Memory, 500 GB storage

HI-3

GP SIM or Test MSISDN

Several SIM or Test MSISDNs for testing the APIs & application.

SOFTWARE INTERFACE REQUIREMENTS ID #

Software Component

Requirement

SI-1

Java Development Kit (JDK)

Java SE 8

SI-2

Database Server

MySQL Community server 5.7

16 | P a g e Rental Car Management System

Final Project -CSC445

ID #

Software Component

Requirement

SI-3

Web Server

Glassfish 3.1

SI-4

Server Host OS

Windows 8.1

SI-5

Sandbox/Commercial terminal

Any open source Rest API Testing tool or need to develop for testing

SI-6

API load testing

Any open source Rest API load testing tool

COMMUNICATIONS INTERFACE REQUIREMENTS ID # CI-1

Communication Requirement

Windows Internet Explorer for Admin GUI

Standards/Reference material 1.1.20.

The followings are the Test deliverables/documents 1. 2. 3. 4.

Test Plan Test Cases. Reviewed/Revised copy of Test cases. Test Report and Defect Report.

Testing Scope Unit Testing The goal of unit testing is to isolate each part of the program and show that the individual parts are correct. A unit test provides a strict, written contract that the piece of code must satisfy. As a result, it affords several benefits. The test team take 5 to 10 minute to test a single module. Most of the test case are done by the unit testing method.

Smoke Testing This is a set of acceptance criteria—conditions that must be met before testing can begin. A smoke test should represent the bare minimum of acceptance testing. If any particular, specialized test cases listed in other test case document can be used here. The test manager done it he first lists down all the test case and he decided to which test case are doing and which tools are using for the test case.

Feature level testing The test case is on the same side or like same the functional test are the same kinds of test as like the nonfunctional test case are same. So the featured level testing is:

17 | P a g e Rental Car Management System

Final Project -CSC445

Functional Tests The test cases will be designed from requirements to test the functionalities with both positive and negative scenarios. Test team are doing their work in a big amount of time to functional tests. They take almost time of testing for functional tests.

Integration Testing All the components which are selected for testing. first of the test team are check those components for if there some are defected the test are not being done well.

System Testing All features will be tested to ensure that all elements of the integrated system function properly.

Security Testing Security must be ensured using HTTPS mechanism.

Test Schedule and Resources Major Activities Schedule: Activities

Start Date

End Date

Responsible

Deliverables

Ensure Test Environment

-

15/04/2016

Md.Abdul Munim

Test Server

Test plan

10/04/2016

12/04/2016

Rayhan Sardar Tipu

Test Plan

Test Cases Design

7/04/2016

13/04/2016

Mir Pias

Test Cases

Identify Additional testers

-

7/04/2016

Mir Noor-UL-haque Pias and Golam Rakib

Testing Conducted (1st cycle + 2nd cycle + system testing + bug fixing of all cycle)

8/04/2016

17/04/2016

1. Mir Noor-UL-haque Pias

Noor-UL-haque

Test Report

2.Rayhan Sardar Tipu

Test Phases and Completion criteria 1.2.

Planned Test cycles and Phases:    

Before testing any features / module developers will must finish unit testing Integration, system, load testing will be done for the features of every delivered testable component in each first cycle testing. Any blocker issue for a feature will be taken care of immediately before testing the next one. The testing of the modules will be completed when the defects are fixed and re-tested.

1.3.

The severity of found defects will be assessed and the priorities on resolving them will be set by collaborating with the developer(s), project managers and the system analyst on this.

1.4.

The criteria that must be fulfilled before each stage of testing can be considered complete are:

18 | P a g e Rental Car Management System

Final Project -CSC445

 

The Blocker, Critical, Major issues and Minor issues (according to point 2) will be fixed. The Known issues (if any) will be listed and notified to clients in release notes.

Issues and Risks 1.5.

Identify issues that have yet to be decided as of this draft of the plan. Note these as risks to the schedule, scope, or quality of the test effort.

1.6.

Identify other risks that may have an impact on the success of the plan. Use the risks outlined in the course book and the attached speaker notes as a guideline to identifying common risks. Eg:     

These are risks to the schedule, scope, or quality of the test effort: The feedback (issue fixing/not fixing) from developers on Test and defect report needs to be well communicated. If not, testing schedule may be hampered. Bug fixing and retesting part needs to be very interactive and well communicated among developers and testers. Otherwise there is risk to ensure bug density minimization. The same risk is there for Smoke test at the end (only one cycle of testing is planned). If planned/allocated resources are not available the functional test, retest and regression test may hamper.

Test Cases Functional

Test Case No.

Test Case Name

Purpose

Precondition

Test Steps

Expected Results

01

Register for reservation

Enable customer to register in the system

Customer has valid email id.

Click register button. Provide required information such as, name, email, phone no. Verify email provided by using verification link sent to email.

Customer will be registered in the system.

02

View vehicle description

Enable customer to view detailed description of

Customer is logged in the system

Click to see the vehicles of the company.

Detailed description of all vehicles in the

19 | P a g e Rental Car Management System

Final Project -CSC445

particular vehicle

Click on a particular vehicle. Detailed description of that vehicle will be displayed.

system are displayed upon request.

03

Notify selection of unavailable vehicle while reservation

Notify customer that selected vehicle is unavailable for reservation

Customer is logged in the system. Customer has attempted to reserve a vehicle.

Click on reserve vehicle. Get notification that vehicle is unavailable.

Notification is displayed for all unavailable vehicles in the system upon attempt of reservation.

04

Advanced search by vehicle category

Enable customer to limit search of vehicle by brand, type and model.

Customer is logged in the system.

Select advanced search. Select category of search. Result will be displayed according to the parameters set.

All available search parameters display appropriate results.

05

Display list of available vehicle for reservation

Enable customer to view the list of vehicles available for reservation

Customer is logged into the system

Click on the button available vehicles A list of vehicles available for reservation will be displayed

All vehicles available for reservation will be on the list.

06

Cancel reservation

Enable customer to cancel reservation of vehicle

Customer is logged in the system. Customer has a vehicle reserved

Select cancel reservation. Provide reservation confirmation number. Reservation confirmation number will be verified by the system. Notification of successful/failed cancelation will be displayed.

Customer will receive a notification of successful cancelation of reservation. If failed, show error message.

07

Update reservation information

Enable employee to update reservation information

Employee is logged in the system. Employee has clearance to update information

Select update reservation information Make necessary changes. Save changes

Updated information will be saved and displayed.

08

View list of reservations

Enable employee to view reservations made by customers

Employee is logged in the system. Employee has

Select reservations

List of reservations made will be displayed.

20 | P a g e Rental Car Management System

Final Project -CSC445

clearance to view reservations 09

Provide unique reservation number

Enable identification of reservations

Reservation has been made

Generate reservation number. Verify its uniqueness

Generate unique numbers for all reservations made

10

Display reservation summary

Enable customer to view a summary of a committed reservation

Customer is logged in the system Customer has made a successful reservation

Select view summary

Summary of reservation will be displayed.

11

User log in

Enable Users to log in to the system

User has required credentials to log in

Input username Input password Select user type (customer, manager, employee) Verify username, password and type

If verified, grant access to the system. If not, show error message.

12

Create new customer account

Enable new customers to use the system

Customer has valid email id

Click sign up button. Provide required information such as, name, email, phone no. Verify email provided by using verification link sent to email.

Customer will be registered in the system after verification.

13

Create new employee account

Enable manager to register employees in the system

Manager has required information of employee

Click register new employee button Provide required information such as, name, email, phone no. Verify email provided by using verification link sent to email.

Employee will be registered in the system after verification.

14

User log out

Enable user to log out of the system

User is logged in

Click log out button.

User will be logged out

15

Change password

Allow user to change password

User exists in the system

Click forgot password in log in page or change password in account settings. If forgot password, then recovery link will be sent to email. After clicking link, input new password, save password.

Log in credentials will be updated with new password.

21 | P a g e Rental Car Management System

Final Project -CSC445

If from account settings, input current password, input new password, save password. 16

Register new vehicle

Enable registration of new vehicle in the system

Employee is logged in Employee has clearance to register new vehicle

Input information of vehicle. Add picture. Save

New vehicle information will be saved and vehicle roster will be updated.

17

Update vehicle information

Enable employees to update vehicle information to current status

Employee is logged in Employee has clearance to update vehicle information

Select vehicle Make necessary changes to the information of vehicle. Save changes.

Updated information will be saved and displayed.

18

View vehicle list

Enable employees to view list of all vehicles

Employee is logged in

Select view all vehicles

List of all vehicles of the company will be displayed

19

View available vehicle list

Enable employees to view list of available vehicles

Employee is logged in

Select view available vehicles

List of vehicles available for reservation will be displayed

20

View rented vehicle list

Enable employees to view list of rented vehicles

Employee is logged in

Select view rented vehicles

List of vehicles currently rented will be displayed

21

View off duty vehicle list

Enable employees to view list of off duty vehicles

Employee is logged in

Select view off duty vehicles

List of off duty will be displayed

22

Register customer into rental list

Enable employee to register customer into rental list

Employee is logged in Employee has clearance to register customer into rental list

Open registration form. Input customer and vehicle information. Save records.

Rental list will be updated.

23

Update customer rent record details

Enable employee to rent record details in rental list

Employee is logged in Employee has clearance to update rent record details in rental list

Open rental list Select record to update. Make necessary changes. Save records.

Updated record details will be saved in the rental list.

24

Search rent records by

Enable employee to search rent

Employee is logged in

Select search by category.

Search result matching input

22 | P a g e Rental Car Management System

Final Project -CSC445

specific category

records by specified parameters

Employee has clearance to view rent records

Input desired category. categories will be displayed. If no such records exist, then error message will be displayed.

25

Display list of customers who rented vehicles

Enable employee to see which customers have rented vehicles

Employee is logged in Employee has clearance to view customer list

Open list of customers who rented vehicles.

A list of customers who rent vehicles will be displayed.

26

Display customer rent records

Enable employee to see rent records of customers

Employee is logged in Employee has clearance to view customer rent records

Select view customer rent records.

Rent records of that specific customer will be displayed. This will be true for all customers in the system

27

Print summary of successfully committed rent

Enable user to print a summary of successfully committed rent

User is logged in. User has clearance to print summary of successfully committed rent

Open summary of successfully committed rent. Click print

System will print the summary of successfully committed rent.

23 | P a g e Rental Car Management System

Final Project -CSC445

Work Breakdown Structure of the Rental Car Management System

24 | P a g e Rental Car Management System

Final Project -CSC445

Critical Path

25 | P a g e Rental Car Management System

Final Project -CSC445

Gantt Chart of the Rental Car Management System

26 | P a g e Rental Car Management System

Final Project -CSC445