System Description and Implementation of Car Renting System

This document provides a detailed description and implementation of a car renting system, including system architecture, class diagram, activity diagram, sequence diagram, use-case diagram, and user interface design.

UNIVERSITY Name
COLLEGE Name---------------------------
BACHELOR OF -----------------------------------.
Course unit name-------------------------------
LECTURER -------------------------------------
No. NAME STUDENT
NUMBER
REGISTRATION
NUMBER
1.

Table of Contents
Section 1..........................................................................................................................................2
System Description........................................................................................................................2
Tiers of the system.........................................................................................................................3
Figure 1 below shows a three-Tier client-Server Architecture of car renting system.............3
Overall structure of the implementation.....................................................................................3
Section 2..........................................................................................................................................5
Class diagram.................................................................................................................................5
Figure 2 below shows a class diagram of Car renting system..................................................5
Activity diagram............................................................................................................................6
Figure 3 below Illustrates the Activity Diagram of Car Renting System.................................6
Sequence Diagram.........................................................................................................................7
Figure 4 below Illustrates the Sequence Diagram of Car Renting System......................................7
Use-Case Diagram.........................................................................................................................9
Figure 5 below illustrates the Use-Case Diagram of Car renting System................................9
User Interfaces design.................................................................................................................10
Figure 6 below shows a login page of Car renting system user interface design...................10
Figure 7 below shows a dashboard of car renting System user Interface design..................11
Section 3........................................................................................................................................11
Reference......................................................................................................................................13

Section 1.
System Description.
The system shall be able to register new customer on the system .The server shall be able to
verify registration details and send a confirmation to customer, if registration is complete
customer processed to login or when registration is incomplete a customer should enter correct
detail. The customer who already register can login then request to rent a car on system .The
customer is supposed to pay deposit first before proceeding with hiring. After deposit a customer
can hires a car and uses it until return time or date reaches. The customer returns the car on
return date .The system check for payment details of deposit and system bills charges for
customer to pay. A customer pays for charges and then process ends.
Tiers of the system.
According to Thomas Connolly and Carolyn Begg (1) the design has Three-Tier Client–Server
Architecture. The first Tier has customer and staff are the one interacting with system’s user
interface for example input data on the interface for example they register and login on system.
Second Tier is application server.
This tiers deals with manipulations of data input in system by customer or staff. It process data
and does some logic.
Third tier is Database server this deals with storage and data validation
Figure 1 below shows a three-Tier client-Server Architecture of car renting system.

Overall structure of the implementation.
All requirements shall be collected and analysed, modelling of data will be done using UML and
implementation will be done in java because it is use to model objects well.
Section 2.
Class diagram.
Figure 2 below shows a class diagram of Car renting system.
The figure 2 above has 5 class and each class contains attributes and methods. All attributes are
private and are not visible to anyone but methods are public. Class customer has attributes name,

email, age, customer id, sex, location and age .Its methods are renting car, paying deposit, pay
rental charges and registration. Class payment has following attributes payment ID, Name,
payment option, payment date, amount and its methods are pay deposits and pay rental charges.
Class car has the following attributes name, type, mode, manufacturer, color, mileage and status.
Its methods are rent car and car payment. Class rental has the following attributes rent date,
rentid, name, return date. Issue date, rental status and category and its methods are returning car,
issuing car and renting car. Class staff has the following attributes name, email, age, customer
id, sex, location and age. According to Lethbridge Timothy (3) stated that a full class diagram
should have attributes, methods and associations between classes
Activity diagram.
Figure 3 below Illustrates the Activity Diagram of Car Renting System.
Assumptions.
A customer has already account and a car is always available for hire.
Figure 3 has 3 swine lanes customer, Renting system and Staff. The first activity starts when
customer successfully logins in system and requests to hire a car .The activity ends when
customer returns a car and pays charges.

Sequence Diagram.
Figure 4 below Illustrates the Sequence Diagram of Car Renting System.
Figure 4 illustrates the customer is interacting on Car renting system..
1. Customer registers on car renting system.
2. Registration details are verified and customer gets confirmation of successful registration or in
case registration not allowed customer also gets notification of failure of registration.
3. Login customer enters username and password.
4. Verification of login details username and password are verified.
5. Validation valid login details are successful allowed to login and proceed to next sequence but
invalid logins .customer needs to input correct details in case customer forgot details he/she can
reset password or username name.
6. Customer pays deposits.
7. Car is issued to customer after paying deposit and verification of payment done.
8. After customer using a car or expiry date is over a customer returns a car.
9. Customer gets deposit on return of the car.
10. Customer pays charges.

Use-Case Diagram.
Figure 5 below illustrates the Use-Case Diagram of Car renting System.
Figure 1 illustrates customer interacting with car renting system as a primary actors. Secondary
actors are server and payment system.
User Interfaces design.
Figure 6 below shows a login page of Car renting system user interface design.

Figure 6 demonstrates a customer login in the system by inputting use name and password when
he or she is already registered on system and when a customer forgot password they can rest it
by clicking on forgot password link. In case a customer is not register he or she can click create
account and registers. Customer can register via email or Facebook.
Figure 7 below shows a dashboard of car renting System user Interface design.
Figure 7 illustrates a dashboard of Car renting system .A customer can click on any operation a
customer need to utilize for example he/she can choose to view cars or rent car by click on hire
menu and views all cars available. According to Pressman Simenon (2) stated that good user
interface are use friendlily, easy to use, easy to learn and memorize.
Section 3.
Robust.
The system design is robust because it accommodates and recovers from any attacks or failure on
system.
Fault tolerant.
System handles faults and continues to operate even if failures occurs and systems recoveries
from failures

Minimal recovery time.
Systems shall take few seconds in case it fails and recovers immediately. Recovery is important
because system is on demand and incase it take time to recovery the company will lose a lot of
finances.
Scalable.
The system shall be able to handle a big number of customer. System should be designed in a
way to handle a big number of transaction. So database should be able to store a lot of data.
Secure (Optional)
The two important aspect of security in architectures are immunity and resilience.
Immunity it is the prevention of attack from attacking system has firewall to prevent attacks.

Reference.
(1).Thomas M. Connolly and Carolyn E. Begg .Database systems a practical approach to
Design, implementation and management. 6th Ed, vol 3 .Harlow, Essex, England: Addison-
Wesley Pearson Education Limited, 2015, pp, 109 -111
(2).Pressman, Simenon .Software Engineering. Practitioner’s Approach. 8thEd vol 6. Inc., 1221
Avenue of the Americas, New York, McGraw-Hill, 2017.pp, 399-450.
(3).Lethbridge, M Timothy. Object-Oriented Software Engineering: Practical Software
Development Using UML and Java 3ndEd ,VOL 6. New York, McGraw-Hill.2016,pp, 200-300.