Car Dealership Management System

Software Engineering Concepts

Instructor Yella Mehroze

Project Name Car Dealership Management System

Section FA18-BCS-D
Submission Date 17-05-2020

Sr. Reg. No Name CGPA Email Phone No Signature

No ID
1. FA18- Sayed 3.04
BCS-016 Muhamma
d Ali Akhtar
2. FA18- Hamza Rauf 3.15
BCS-020
3. FA18- Usman 2.89
BCS-064 Mazhar
Bhatti
4. FA18- Arslan 3.34
BCS-080 Saleem
5. FA18- Syed Ali 3.12
BCS-116 Mehdi

Comsats University Islamabad Lahore Campus

 Problem Statement:
As we see the technology is progressing very rapidly and fast and there is a need of technology
in almost each field of life. With the help of technology, our life has become easier. As now here
we are concerned about the Car’s Saling and Purchasing. So, there is a need of an application
system which can overcome these all things. Our Car Dealership Management System will
surely play a vital role.

Introduction:
 Background Information:
The main goal of this project is designing and developing an interactive Car Dealership
System. These details are routinely maintained depending on the numerous inputs and the
changes made in the systems database. The alterations in the database can happen
spontaneously, for example, after the system performs calculations on the direct inputs.
This system essentially works on input-output entry mechanism. The Car Sales System
follows closely with other developed Information Systems focusing on achieving better
transactions and more customer satisfaction.

 Project Description:
Today, the management of car details by computer systems has been popularized in
many franchises. However, there are still many problems to develop and configure full Sales
system transactions. It is required to maintain every Franchise has to develop own software.
It takes lesser time this days to build and develop information systems according to user
needs. The module, which is developed here, consists of some basic template of all
Information systems.

Purpose:
The purpose of the system and also the cause of the development of this system includes
the following points:
1. To overcome the need of technology in dealing of cars through application.
2. To provide the best platform to both buyer and seller.
3. To provide consistency in dealing of automobiles.
4. To provide both the admin and the user easily manageable platform in order to
maintain the records.
5. The main purpose of the development of this system is to manage and maintain
different clients on the basis of unique ID’S hence differentiating them without
being having the conflicts of same name.
6. The purpose of development of this system is to inform the administrator about
the user login via electronic-mail.
 Scope:
The Scope of our Car Dealership Management System comprises of the points:
1. The main goal of this project is designing and developing an interactive Car
Dealership System. These details are routinely maintained.
2. The main scope of this system is covering the vital use of application
management systems almost in each field.
3. It has a lot of scope in future in covering the advances of automobiles
management systems.
4. System follows closely with other developed Information Systems focusing on
achieving better transactions and more customer satisfaction.
5. The main scope of this system is in future in bettering some old systems of sales,
purchases of automobiles.
6. This system also highlights its importance on other systems thus bettering them
because of having vital scope.

Overview:
This Project leads to the development of an interactive Car Sale System. Development of an
interactive car sale system which lets a customer to find a car and its details is the main
objective of this project. Both the user and the administrators can access enter the details of
every car. Administrators are responsible of maintaining the details of vehicles like the system’s
main functions include:

 Signing in and log in functionality.

 Customers can look up various cars listing with details included.
 User may select and add products to shopping Cart.
 Sale application Users can also view the information of vehicle purchased and their
particulars. Menu’s and toolbars are part of the excellent user interface

The main goal of this project is designing and developing an interactive Car Dealership System.
These details are routinely maintained depending on the numerous inputs and the changes
made in the systems database. The alterations in the database can happen spontaneously, for
example, after the system performs calculations on the direct inputs. This system essentially
works on input-output entry mechanism. The Car Sales System follows closely with other
developed Information Systems focusing on achieving better transactions and more customer
satisfaction.
Today, the management of car details by computer systems has been popularized in many
franchises. However, there are still many
Confidential problems to develop and configure full Sales system transactions. It is required to
maintain every Franchise has to develop own software. It takes lesser time these days to build
and develop information systems according to user needs. The module, which is developed
here, consists of some basic template of all Information systems.

Gantt Chart:

Functional Requirements:

FR01-01 The system shall Provide User with Complete Login System

FR01-02 The system shall allow the user to sign-up if he doesn’t have login already.

FR01-03 The system shall enable the user to select from registered car(s) (in the
available stock) and to place request to cancel one or more than one car(s). The
system shall also allow the users to cancel their actions.

FR01-04 The system shall allow the user to submit his cancellation requests.

FR01-05 The system shall display a message to the user once his/her
confirming/cancellation request has been submitted. The message shall state
that the decision on acceptance or rejection of request would be
communicated back in next 48 hours.

FR01-06 The system shall allow the user to select the car of his own choice from a list
available by the manager.

FR01-07 The system shall enable the manager to view all the cars
 confirming/cancellation requests sent to him by the users. The request should
be accepted if that car is available in the stock.

FR01-08 The system shall enable to display the message if the selected car is out of the
stock.

FR01-09 The system shall facilitate the manager to watch the requests forwarded for
confirmation/cancellation of the booking. The request should display the user’s
all details to the Manager.

FR01-10 The system shall allow the Manager to mark the cars request to be “Approved”.

FR01-11 The system shall allow the Manager to mark the cars request to be
“Disapproved”.

The system shall allow user to customize selected car’s features as provided by
company.
FR01-12

FR01-13 The system shall allow the Manager to send “Booking Approved” message to
the respective user if his car is in stock and his request is accepted.

FR01-14 The system shall enable the Manager to send “Booking not Approved” message
to the respective user in case the car is out of stock and his request is not
accepted.

FR01-15 The system shall allow users to buy their product online through credit cards.

FR01-16 The system shall allow the user to logout of their accounts.

FR01-17 The System will be able to provide the total bill after getting some discounts if
customer is eligible for the discounts
The System shall allow the Employee to check and balance the items by clicking
FR01-18
the item icon on the app.

The system shall allow the user to ‘Forgot Password’ if they don’t remember.
FR01-19

The system shall display the message “Congratulations your purchase has been
FR01-20
done.” when the user fills all the details of account and credit card.
 Non-Functional Requirements:
NFR01: Performance
NFR01-01 Average load time of the starting page of the system must be less than 5
seconds.

NFR01-02 Average processing time taken by the system to complete a transaction/request

should be less than 20 seconds.

NFR01-03 System Mean Time to Failure should not be more than 1(One) Minute within
168 hours of use.

NFR01-04 Average system response time should not be greater than 10 seconds.

NFR01-05 System must successfully run on a client machine with 1 GB RAM or above.

NFR01-06 50 users should be able to simultaneously access the system and update
the database with response time not more than 10 seconds.

NFR01-07 System must re-load certain features with time to ensure stable
performance.

NFR01-08 System should be able to recognize and suspend an expected buggy

input from user to avoid crashes.

NFR02: Security
NFR02-01 System must provide access to authorized users only that enter through the
login module.

NFR02-02 System must not provide access to ANY user EXCEPT the designated user to
update the database.

NFR02-03 No user can view data of any other user through any report or views
provided by the system.

NFR02-04 After the end of a user Session, no information must be saved anywhere on the
client machine.

NFR02-05 System should be able to suspend enormous traffic from certain IP-addresses to
ensure DDOS protection.

NFR03: Defect Maintenance

 NFR03-01 System should be able to suddenly report the defect which arose due to any
reason.
NFR03-02 Admin of the system should have the right to grant and install update for
maintenance.
NFR03-03 System should be able to repair the defect and ensure the best quality for
future use.
NFR03-04 System should be able to able to send the defect report to both the admin and
user so that user ensure its data integrity.
NFR03-05 System should be able to manage the defect reports and all their respective
updates in the database for future.
NFR03-06 System should be able to recover data in case of defect before attempting
repairs.
NFR03-07 System should warn user regarding use of an affected feature.
NFR03-08 System should be able to resolve defect without complete re-implementation.
(Modular Approach in Design)

NFR04: Documentation
NFR04-01 System should have the minimal problem’s solution’s in its documentation in
case any problem occurs.
NFR04-02 System should have a comprehensive document and covering all the main
aspects of the system.
NFR04-03 System’s documentation should be stored in the database so that it can be
used by admin in case of problem.
NFR04-04 System’s documentation should be in the favor of both admin and user.
NFR04-05 System’s documentation should also comprise of entity relationship diagrams
for better understanding.
NFR04-06 System’s documentation should be done in a user-friendly approach.
NFR04-07 System’s documentation should follow Modular approach. (Feature by
Feature Description)

NFR05: Compatibility
NFR05-01 System software should be compatible to each type of operating system.
NFR05-02 System should display same abstracted view on each operating system.
NFR05-03 System should be compatible to both admin and the user in a way that there
 will be no difficulty in operating on both sides.
NFR05-04 System also ensures compatibility in a way that both the work of user and
admin should maintain its integrity.
NFR05-05 System should be able to produce health report each month which
compatibility to both user and admin.

NFR06: Disaster Recovery

NFR06-01 System should be in its perfect state after disaster recovery.
NFR06-02 System should have the complete disaster report in its database.

NFR06-03 System’s admin section should be enough powerful to recover from each sort
of disasters and problems.
NFR06-04 System should ensure its best performance after recovery and should provide
each facility like it was before the disaster.
NFR06-05 System should be provided with an efficient backup procedure.

Business Rules:

ID Rule Definition Type of Rule Static or Dynamic Source

BR-1 Only Authenticated and Authorized Fact Static System-Admin

Users are allowable to enter the system.
BR-2 User should be issued an identification Fact Static System-Admin
number on logging on to the system.
BR-3 Manager should generate the monthly Constraint Dynamic System-
report of the users which log on to the Manager
system.

BR-4 Only manager has the right to add, Constraint Static System-
delete and or modify the cars in system. Manager
BR-5 System should provide the receipt to Constraint Static System-
user on his purchase. Manager

BR-6 User should be given the discount of Computation Dynamic System-Admin

10% on the purchase greater than
50,00,000.
BR-7 User should be given the membership Computation Static System-Admin
card if he desires on his purchase of
50,00,000

BR-8 In case of Online purchase, if payment is Inferences Static System-Admin

not received within 2 days then legal
court action should be taken against
user.
BR-9 System should hold only 60 cars in stock Constraint Static System-
at a time. Manager

BR-10 If a car’s insurance is becoming out of Action- Static System-

date, then manager should request and Enabler Manager
grant the insurance for that car from
insurance company.
BR-11 Only Admin is granted access to manage Constraint Static System-
the all databases. Manager

BR-12 Each car sale should have the unique Fact Static System-Admin
code identifier.

Context Diagram:
 Cash Management
Payroll Processing
Customer Finance
Requests Response Department
Confirmation
Customer Reciept

Send Feedback Transaction Details

Send Requests
Car Dealership Login-Signup Details
Requests Approval Management System Provides Cars Details
Record Management

Provides Instrusion Detection

Login Confirmation
Customer Authentication Requests
Database
Manager
Departmental Management Administration

Login and
Signup System

Data Flow Diagram:

 Login Status Getting New user on Signup

1.0
User Admin Manager
Login Info Signup and Store Login Data
Login
Getting User

Car͛s Info
2.1
Login Info D1 Users File
Updating User͛s Managing
2.0 1.1 User͛s File

View Car Managing Process Info

Details Car͛s Process Sending Sales Info

Getting Car͛s Info D2 Car͛s File Upadting Car͛s File

3.0
1.2
Car Dealership Work Order Info
Managing
Updating Processes
Process Processes Managing Invoice͛s

D3 Process Info
Stores Process Info
File

4.0

Purchase Stores Car͛s Sales

Order Process 1.3

Updating Sales Managing
D4 Car͛s Sales Sales
Customer Reciept
File

5.0
Generating Storing Invoice Info
Invoice
Process
2.3
Updating Invoice File Managing
D5 Invoice File
Invoice File

Entity Relationship Diagram:

Use Case Diagrams and Case Descriptions
 Use Case Name: Login

Actors: Customer

A User must be provided with a forum where he can enter his unique
Summary identity details registered with company in order to have access to
dashboard and perform relevant operations.
The customer must not already be logged into Web/Software of
Pre-Condition
Company and customer must have signed up before login.
The customer must be able to view car details, select cars and items,
Post-Condition select payment options and proceed to payment and logout.
Customer must first Sign up, the login, the view cars and items, then
Normal Course of
select required, then choose payment options, then proceed to
Events
payment, then logout.
If the customer doesn’t login, he will not be able to view cars and
Exceptions items, select cars or payment options and proceed to payment.

Use Case Name: Signup

Actors: Customer
 A customer must signup using authentic identity information onto
Summary company’s Web/Software in order to login to perform desired
operations.
The customer must not already be signed up into Web/Software of
Pre-Condition
Company.
The customer must be able to login with details provided earlier
Post-Condition during sign up, view car details, select cars and items, select payment
options and proceed to payment and logout.
Customer must first Sign up, the login, the view cars and items, then
Normal Course of
select required, then choose payment options, then proceed to
Events
payment, then logout.
If the customer doesn’t signup, he will not be able to proceed any
Exceptions further.

Use Case Name: View Car Details

Actors: Customer

A customer must be able to view all the cars, models, relevant details
Summary
and parts or items in stock after he has logged in.
The customer must login in to his account first in order to view all
Pre-Condition
relevant stuff for purchases.
Customer must be able to select desired cars, models or parts and
Post-Condition should be able to select payment options and proceed to payment or
logout.
Customer must first Sign up, the login, the view cars and items, then
Normal Course of
select required, then choose payment options, then proceed to
Events
payment, then logout.
If the customer doesn’t login, he will not be able to view car details.
Exceptions

Use Case Name: Select Car and Items

Actors: Customer

A customer now can view all the cars, models, relevant details and
Summary
parts or items in stock after he has logged in.
 Pre-Condition The customer must be logged in to his account.

The customer must be able to select payment options, and proceed

Post-Condition to payment calculation
Customer must first Sign up, the login, the view cars and items, then
Normal Course of
select required, then choose payment options, then proceed to
Events
payment, then logout.
If the customer doesn’t signup, he will not be able to proceed any
Exceptions further.
Select Payment Method.
Includes

None.
Extends

Use Case Name: Select Payment Method

Actors: Customer

A customer must be able to select one of the payment options

Summary
available after he has selected desired products.
The customer must have selected some products in order to select
Pre-Condition
payment method.
The customer must be able to proceed to payment calculation.
Post-Condition

Customer must first Sign up, the login, the view cars and items, then
Normal Course of
select required, then choose payment options, then proceed to
Events
payment, then logout.
If the customer doesn’t select any payment method, he will not be
Exceptions able to proceed any further.
Calculate Payment.
Includes

None.
Extends

Use Case Name: Calculate Payment

 Actors: Customer

After the customer has selected the payment method and proceeded
Summary
to payment, they payment shall be calculated and verified.
The customer must have selected some products in order to select
Pre-Condition
payment method.
The customer must be able to proceed to payment calculation.
Post-Condition

Customer must first Sign up, the login, the view cars and items, then
Normal Course of
select required, then choose payment options, then proceed to
Events
payment, then logout.
If the customer doesn’t select any payment method, he will not be
Exceptions able to proceed any further.
None.
Includes

None.
Extends

Use Case Name: Logout

Actors: Customer

The customer must be able to logout from his account when he has
Summary
performed desired operations.
The customer must have logged into his account in order to logout of
Pre-Condition
it.
Customer will need to login in again in order to use software /
Post-Condition Website.
Normal Course of The customer who has logged in will click logout button when
Events needed to successfully logout.
If internet disconnects, then logout button will not work.
Exceptions

None.
Includes

None.
Extends
 Use Case Name: Login

Actors: Administrator

An Administrator must be provided with a forum where he can enter

Summary his unique identity details registered with company in order to have
access to dashboard and perform relevant operations.
The Administrator must not already be logged into Web/Software of
Pre-Condition
Company.
The Administrator must be able access his dashboard after login.
Post-Condition

Normal Course of Administrator shall enter his details and log in to dashboard.
Events
None.
Exceptions
 Use Case Name: View Sales Purchase

Actors: Administrator

An Administrator must be provided with a forum where he can view

Summary the sales and purchases of organization and view general reports of
profit / loss.

Pre-Condition The Administrator must be logged into Web/Software of Company.

The Administrator must be able to generate specific reports based on

Post-Condition data analysis.
Normal Course of Administrator shall enter his details and log in to dashboard and
Events from there select the tab of sales/purchases.
None.
Exceptions

Use Case Name: Manage Inventory

Actors: Administrator

An admin shall be provided with a dashboard where he can manage

Summary inventory. This includes addition, editing and deletion of inventory
stock.

Pre-Condition The Administrator must be logged into Web/Software of Company.

The Administrator must be able to add, edit and delete specific stock
Post-Condition items based on need.
Normal Course of Administrator shall enter his details and log in to dashboard and
Events from there select the tab of inventory management.
None.
Exceptions

Use Case Name: Manage Customers

 Actors: Administrator

An admin shall be provided with a dashboard where he can manage

Summary customers. He must be able to see accounts and their transaction
details, pending payments etc.

Pre-Condition The Administrator must be logged into Web/Software of Company.

The Administrator must be able to generate specific reports based on

Post-Condition customer data.
Normal Course of Administrator shall enter his details and log in to dashboard and
Events from there select the tab of customer management.
None.
Exceptions

Use Case Name: Logout

Actors: Administrator

The Administrator must be able to logout from his account when he

Summary
has performed desired operations.
The Administrator must have logged into his account in order to
Pre-Condition
logout of it.
Administrator will need to login in again in order to use software /
Post-Condition Website.
Normal Course of The Administrator who has logged in will click logout button when
Events needed to successfully logout.
If internet disconnects, then logout button will not work.
Exceptions

None.
Includes

None.
Extends
 Use Case Name: Login

Actors: Manager

A manager must be provided with a forum where he can enter his

Summary unique identity details registered with company in order to have
access to dashboard and perform relevant operations.
The manager must not already be logged into Web/Software of
Pre-Condition
Company.
The manager must be able access his dashboard after login.
Post-Condition

Normal Course of Manager shall enter his details and log in to dashboard.
Events
None.
Exceptions

Use Case Name: View Database

Actors: Manager

A manager must be provided with a forum where he can view the

Summary
database of organization and view general reports.
 Pre-Condition The manager must be logged into Web/Software of Company.

The manager must be able to generate specific reports based on

Post-Condition database analysis.
Normal Course of Manager shall enter his details and log in to dashboard and from
Events there select the tab of database.
None.
Exceptions

Use Case Name: Manage Sales Purchases

Actors: Manager

An admin shall be provided with a dashboard where he can manage

Summary sales and purchases. This includes addition, editing and deletion of
sales purchases.

Pre-Condition The manager must be logged into Web/Software of Company.

The manager must be able to add, edit and delete specific entries
Post-Condition based on need.
Normal Course of Manager shall enter his details and log in to dashboard and from
Events there select the tab of sales purchases management.
None.
Exceptions

Use Case Name: View Stock

Actors: Manager

A manager must be provided with a forum where he can view the

Summary stock items of organization and view general reports of availability of
stock items.

Pre-Condition The manager must be logged into Web/Software of Company.

 The manager must be able to generate specific reports based on
Post-Condition analysis.
Normal Course of Manager shall enter his details and log in to dashboard and from
Events there select the tab of stock view.
None.
Exceptions

Use Case Name: Logout

Actors: Manager

The Manager must be able to logout from his account when he has
Summary
performed desired operations.
The Manager must have logged into his account in order to logout of
Pre-Condition
it.
Manager will need to login in again in order to use software /
Post-Condition Website.
Normal Course of The Manager who has logged in will click logout button when needed
Events to successfully logout.
If internet disconnects, then logout button will not work.
Exceptions

None.
Includes

None.
Extends

Activity Diagrams:
1) Admin Login Activity Diagram:
2) User Login Activity Diagram:
3) Signup Activity Diagram:
4) View Cars Details Activity Diagram:
5) Car Purchase Activity Diagram:
6) Manager Login Activity Diagram:
7) Manage Cars Activity Diagram:
8) Inventory Management Activity Diagram:
9) Manage Reports Activity Diagram:
10) Sales Record Activity Diagram:
11) Admin Managing Databases

Login to System

Homepage

View Database

Manage Database

Add Record Remove Record Validate record

Saving
12) Manager Managing Car Models

Login to System

Homepage

Manage Models

Add Models Validate Models Remove Models

Saving in Database
13) Manager Managing Users

Login to System

Homepage

Manage Users

Providing
Add/Remove Users Validate Users
Verification ID

Saving in Database
14) Manager Requests Approval

Login to System

Homepage

View Requests

Fetching From
Database

Requests Not Approved Return to User

Requests Approved

Stroing in Database
15) User Car Registration

Login To System

Homepage

Car-Registration

Enter Engine No. Enter Chasis No.

Verification

Incorrect Details Not Registered

Correct Details

Successfully
Registered
16) User Forget Password

Enter User
Credentials

Verification

Record Not Found Record Found

Get Authentication
ID

ID Found ID Not Found

Successfully Login

Providing User Display ID Error

Credentials Message
17) User Payment Type

Login to System

Homepage

Payment

Payment Type

Payment Type not

Not Accepted
Accepted
Accepted

Proceed to Payment
 Sequence Diagrams:
1. Admin Login

:Admin :LoginPage :Verification :Database :AdminHomePage

Accesstologinppage()

AdminCredentials() Validate Details()

Fetchingadmindetails()

Details Provided
Accesstohomepage()
Successfully Login

Logout
 2. Admin Managing Sales Record

:Manage
:Admin :Homepage :View Sales :Database
Sales

Logintopage()

Viewsalesdetails()

Managesales()
ValidateSales()

Add/edit/deleteSales()

Sentinfo()
Sales Updated

Logout
 3. Manager Generating Reports

:Generate
:Manager :Homepage :Database
Report

Logintosystem()

Fetchingdetails()

Details Provided
ValidatingDetails()

Sendingdetails() WordProcessing()

Sendtodmin()

Report Generated and Sent

Logout
4. Manager Managing Inventory

:Inventory
:Manager :Homepage :Database
Management

Login()

ManageInventory()

Add/edit/delete Inventory()

Inventoryinfosent()

Inventory Updated

Logout
 5. Manager Login

:Manager :LoginPage :Verification :Database :HomePage

Accesstologinppage()

ManagerCredentials() Validate Details()

FetchingManagerdetails()

Details Provided
Accesstohomepage()
Successfully Login

Logout
 6. Manager Managing Cars

:Insurance
:Manager :Car's Page :Manage Cars :Database
Company

Logintocar'spage()

ManageCar's() Add/edit Cars

Delete Cars

Insurancerequest()
Cars Updated
Insurance Granted
Sentinfo()
Logout

7. User Viewing Car Details

:User :Car's Page :Car Details :Database

Logintocar'spage()

SelectedcarRequest()

Fetchingdetails()

Details Provided

Logout
8. User Car Purchasing

:Car's :Purchasing
:User :Database
Homepage Process

Logintocarspage()

Requestforpurchase()

Purchase Method Approved

Thanks for shopping

Sentpurchasedetails()

Logout
 9. User Login

:User :LoginPage :Verification :Database :HomePage

Accesstologinppage()

UserCredentials() Validate Details()

Fetchinguserdetails()

Details Provided
Accesstohomepage()
Successfully Login

Logout
 10.User Signup

:User :SignupPage :Registeration :Database :LoginPage

Accesstosignuppage()

Userdetails() Validate Details()

Sendtodatabase()

User Registered
Accesstologin()

Logout
11.Admin Managing Databases

:Admin :Homepage :View Databases :Manage Databases

Login()

Checkingdetails()

Details Provided Validating Databases()

ManageDatabases() EditingDatabases()

Saving()

Databases Updated

Logout
12.Manager Managing Car Models

:Manager :Homepage :Car Models :Database

Login()

ManageModels()

ValidateModels()

InsertModels()

RemoveOutdated()

Models Updated
Sentinfo()

Logout

13.Manager Managing Users

 :Manage
:Manager :Homepage :Database
Users

Login()
ManageUsers()
Add/RemoveUsers()

AssignVerificationId()

ValidateUsers()

SentInfo()
Users Updated

Logout
14.Manager Requests Approval

:View
:Manager :Homepage :Database :Purchased
Requests

Login()
ViewRequests()

FetchingRequests()

Requests Provided

RequestApproved()

RequestsNotApprovedSentToUser()

SentInfo()

Logout
15.User Car Registration:

:Car
:User :Homepage :Database
Registration

Login()
CarRegistration()
EnterEngine/ChasisNo.()

VerifyInfo()

Successfully Registered Correct Info

Logout
16.User Forget Password

:User :Login Page :Verification :Database :Homepage

AccesstoLoginPage()
EnterCredentials()

CredentialsSent()

FetchingDetails()

Info Provided
Details Not Found

Enter Authentication ID

AuthenticationID()

Providing Details

EnterDetailsAgain()
Login()

Successfully Login

Logout
17.User Payment Type

:User :Homepage :Payment :Database

Login()

SelectPaymentType()

SentInfo()

Payment Type Accepted

ProccedtoPayment()

Logout
 Class Diagram:

User Class Admin Class Manager Class

-User_ID:int -Admin_name:String -Manager_Name:String
-User_Name:String -Admin-ID:int -Manager_ID:String
-User_Age:int +salesManagement() +inventoryManagement()
-User_Email:String +databaseManagement() +userManagement()
+addUser() +carsManagement()
+deleteUser()
+editUser()

Car Class Sale Class Permission Class

-Car_ID:int -Car_Name:String -Permission_ID:int

-Car_name:String -Car_Category:String -Permission_Name:String
-Car_model:String -Permission_Description:String
+salePrice()
-Car_Category:String +grantPermission()
+addCar() +discardPermission()
+editCar()
+deleteCar()

Record Class

-User_ID:int
-Car_Category:String
-Car_Name:String
+addRecord()
+editRecord()
+deleteRecord()
 Prototypes:
1. Login Prototype:

It asks the user to enter its credentials and after verifications gives user the access to the
system.
2. Signup Prototype

It gets the info from new user and stores it in the database and marks the user as
registered.
 3. Homepage Prototype:

From here, User can review the requested Cars being available in stock and then proceeds
towards the payment in case of purchase.
4. Admin Dashboard Prototype

Gives Admin the access to make changes in the system.

5. Manager Dashboard Prototype

Gives the access to manager to make changes in the system.

 6. User Receipt Prototype:

User fills the receipt form in order to make car purchase and its registration.
7. Car Registration Prototype:
 Change Request Log:

Architecture Diagram and Description:

Anything that describes the form and its structure is called its architecture. It is the first stage in
the software design process, Architectural design is a creative process of a system which helps
us to understand how our system is organized and designing of its structure. It will satisfy the
FR’s and NFR’s.
The style which reasonably satisfies our system is Layered Architecture. It consists of a set of
layers and every layer provides set of services to the “above” layer. It behaves as a client to the
layer “below” it. In its development takes place incrementally. It provides separation and
independence for the components. The outer layer is independent of inner layer. Outer layer
can only be changed if interface is changed.

 Block Diagram:

 Explanation:
The Car Dealership System also consists of layers. Its components can be deployed
independently and can be updated or maintained at any time schedule by authorized
authorities. In it more than one user can work at a time means it allows parallel working to its
members. The communication or interaction occurs between the layers. This communication
takes place by the suitable communication protocol. Information can flow from higher to lower
(Requests) or vice versa (Answers). Every layer of it is secure it does not allow anyone except
authorized people to get access to private data. We can use any layer’s data or this layer’s data
can be modifiable.

Test Cases:
Test Case 1:

Project Name: Car Dealership Management System

Module Name: Login

Created By: Sayed Muhammad Ali Akhtar

Reviewed By: Arslan Saleem

Date of Creation: 16-05-2020

Date of Review: 17-05-2020

Test Test Test- Pre- Test Test Expected Post Test

Case-ID Scenario Case Condition Steps Data Result Condition Result:
Pass/Fail
TC_Login Testing Enter Need a valid Enter <Valid Successfully Homepage Pass
-001 the Login Valid Authenticati Valid User Login is shown
Function Userna on-ID to User Name>
ality me access Name
and
Enter <Valid
Passw
Valid Passwor
ord
Passwo d>
rd
Click
Login
Button

TC_Login Testing Enter Need a valid Enter <Valid Show Fail

-002 the Login Valid Authenticati Valid User Message:
Function Userna on-ID to User Name> “Username
ality me access Name or Password
and Invalid”
Enter <Invalid
Invalid
valid Passwor
Passw
Passwo d>
ord
rd
Click
Login
Button

TC_Login Testing Enter Need a valid Enter <Invalid Show Fail

-003 the Login Invalid Authenticati Valid User Message:
Function Userna on-ID to User Name> “Username
ality me access Name or Password
and Invalid”
Enter <Valid
Passw
valid Passwor
ord
Passwo d>
rd

Click
Login
Button
TC_Login Testing Enter Need a valid Enter <Invalid Fail
-004 the Login Invalid Authenticati Valid User
Function Userna on-ID to User Name>
ality me access Name
and
Enter <Invalid
Invalid
valid Passwor
Passw
Passwo d>
ord
rd
Click
Login
Button
 Test Case 2:

Project Name: Car Dealership Management System

Module Name: Signup

Created By: Sayed Muhammad Ali Akhtar

Reviewed By: Arslan Saleem

Date of Creation: 16-05-2020

Date of Review: 17-05-2020

Test Test Test- Pre- Test Test Expected Post Test Result:
Case-ID Scenario Case Condition Steps Data Result Condition Pass/Fail

TC_Sign Testing Enter Need User Enter <Valid Successfu Login Pass
up-001 the Signup Valid Credential Usern Usernam lly Page is
Functional User’s s ame e> registere shown
ity Credenti d
Enter <Valid
als
Passw Passwor
ord d>

Enter <Valid
E-mail Email>

TC_Sign Testing Enter Need User Enter <Invalid Show Fail

up-002 the Signup Invalid Credential Usern Usernam Message:
Functional User’s s ame e> ”Invalid
ity Credenti Credentia
Enter <Invalid
als ls”
Passw Passwor
ord d>
 Enter <Valid
E-mail Email>

TC_Sign Testing Enter Need User Enter <Valid Show Fail

up-003 the Signup Invalid Credential Usern Usernam Message:
Functional User’s s ame e> ”Invalid
ity Credenti Credentia
Enter <Invalid
als ls”
Passw Passwor
ord d>

Enter <Valid
E-mail Email>

TC_Sign Testing Enter Need User Enter <Valid Show Fail

up-004 the Signup Invalid Credential Usern Usernam Message:
Functional User’s s ame e> ”Invalid
ity Credenti Credentia
Enter <Valid
als ls”
Passw Passwor
ord d>

Enter <Invalid
E-mail Email>

TC_Sign Testing Enter Need User Enter <Invalid Show Fail

up-005 the Signup Invalid Credential Usern Usernam Message:
Functional User’s s ame e> ”Invalid
ity Credenti Credentia
als Enter <Invalid ls”
Passw Passwor
ord d>

Enter <Invalid
E-mail Email>
 Test Case 3:

Project Name: Car Dealership Management System

Module Name: Searching Cars

Created By: Arslan Saleem

Reviewed By: Sayed Muhammad Ali Akhtar

Date of Creation: 16-05-2020

Date of Review: 17-05-2020

Test Case- Test Test- Pre- Test Test Expected Post Test
ID Scenario Case Condition Steps Data Result Condition Result:
Pass/Fail

TC_Search Testing the Enter User Enter <Valid Car Car Details Pass
-001 Search the must be the Car’s Car Details provided to
Functionality Car’s Logged in name name> Found User
name

TC_Search Testing the Enter User Enter <Invali Car Fail

-002 Search the must be the Car’s d Car Details
Functionality Car’s Logged in name name> Not
name Found
 Test Case 4:

Project Name: Car Dealership Management System

Module Name: Logout

Created By: Arslan Saleem

Reviewed By: Hamza Rauf

Date of Creation: 16-05-2020

Date of Review: 17-05-2020

Test Case- Test Test- Pre- Test Test Data Expected Post Test
ID Scenario Case Conditio Steps Result Conditio Result:
n n Pass/Fai
l
TC_Logout Testing the Clickin User Clickin Show Login Pass
-001 Logout g the must be g the Message: Page is
Functionalit Logout Logged in Logout “Successfull shown
y Button Button y Logout”

TC_Logout Testing the Clickin User Clickin <Purchasin Not Fail

-002 Logout g the must be g the g in Successfully
Functionalit Logout Logged in Logout Process> Logout
y Button Button
 Test Case 5:

Project Name: Car Dealership Management System

Module Name: Car Registration

Created By: Hamza Rauf

Reviewed By: Arslan Saleem

Date of Creation: 16-05-2020

Date of Review: 17-05-2020

Test Case- Test Test- Pre- Test Test Expected Post Test
ID Scenario Case Condition Steps Data Result Con Result:
ditio Pass/Fail
n

TC_Registr Testing the Enter User must Enter <Valid Successfu Car Pass
ation-001 Car Car’s have Engine. Engine. lly Car Regi
Registration Credenti unregister No No> Registere ster
Functionality als ed car d ed
Enter <Valid
Chasis. Chasis.
No No>

Enter
Price
Enter <Valid
Car Model>
model

TC_Registr Testing the Enter User must Enter <Invalid Not Fail
ation-002 Car Car’s have Engine. Engine. Successfu
Registration Credenti unregister No No> lly Car
Registere
Enter <Valid
 Functionality als ed car Chasis. Chasis. d
No No>

Enter
Price
Enter <Valid
Car Model>
model

TC_Registr Testing the Enter User must Enter <Valid Not Fail
ation-003 Car Car’s have Engine. Engine. Successfu
Registration Credenti unregister No No> lly Car
Functionality als ed car Registere
Enter <Invalid
d
Chasis. Chasis.
No No>

Enter
Price
Enter <Valid
Car Model>
model

TC_Registr Testing the Enter User must Enter <Invalid Not Fail
ation-004 Car Car’s have Engine. Engine. Successfu
Registration Credenti unregister No No> lly Car
Functionality als ed car Registere
Enter <Invalid
d
Chasis. Chasis.
No No>

Enter
Price
Enter <Invalid
Car Model>
model
 Test Case 6:

Project Name: Car Dealership Management System

Module Name: Car Purchase

Created By: Hamza Rauf

Reviewed By: Sayed Muhammad Ali Akhtar

Date of Creation: 16-05-2020

Date of Review: 17-05-2020

Test Test Test- Pre- Test Steps Test Data Expected Post Test
Case-ID Scenari Case Conditi Result Condition Result:
o on Pass/Fail
TC_Purch Testing Enter User Enter Car <Valid Show Receipt Pass
ase-001 the Car’s must name Car Message: generated
Purchas Creden have name> “Congratula and given
ing tials viewed tions your to user
Enter <Valid
Process Car’s purchase
Transmissi Transmiss
details has been
on ion>
and done”
must Enter <Valid
be Model Model>
registe
Select
red
Payment
Type
TC_Purch Testing Enter User Enter Car <Invalid Show Fail
ase-002 the Car’s must name Car Message:
Purchas Creden have name> “Invalid
ing tials viewed Buyer
Enter <Valid
Process Car’s Credentials”
Transmissi Transmiss
details
on ion>
and
must Enter <Valid
 be Model Model>
registe
Select
red
Payment
Type
TC_Purch Testing Enter User Enter Car <Valid Show Fail
ase-003 the Car’s must name Car Message:
Purchas Creden have name> “Invalid
ing tials viewed Buyer
Enter <Invalid
Process Car’s Credentials”
Transmissi Transmiss
details
on ion>
and
must Enter <Valid
be Model Model>
registe
Select
red
Payment
Type
TC_Purch Testing Enter User Enter Car <Valid Show Fail
ase-004 the Car’s must name Car Message:
Purchas Creden have name> “Invalid
ing tials viewed Buyer
Enter <Valid
Process Car’s Credentials”
Transmissi Transmiss
details
on ion>
and
must Enter <Invalid
be Model Model>
registe
Select
red
Payment
Type
 Test Case 7:
Project Name: Car Dealership Management System
Module Name: Add to Cart

Created By: Syed Ali Mehdi

Reviewed By: Hamza Rauf

Date of Creation: 16-05-2020

Date of Review:

Test Test Test- Pre- Test Test Expected Post Test

Case-ID Scenario Case Condition Steps Data Result Condition Result:
Pass/Fail
TC_Cart Testing the Select User Select <Valid> Car must Add to Cart Pass
-001 Add to Cart Car must be Car be added Page opened
Functionality and logged in to cart and proceed
Click on
Click to payment
Add to
Add
Cart
to
Cart

TC_Cart Testing the Select Select Car Select <Invalid Car must Fail
-002 Add to Cart Car and Click Car > not be
Functionality and Add to added to
Click on
Click Cart Cart
Add to
Add
Cart
to
Cart
 Test Case 8:
Project Name: Car Dealership Management System
Module Name: Manage Users

Created By: Syed Ali Mehdi

Reviewed By: Sayed Muhammad Ali Akhtar

Date of Creation: 16-05-2020

Date of Review: 17-05-2020

Test Test Test- Pre- Test Test Expected Post Test

Case-ID Scenario Case Condition Steps Data Result Condition Result:
Pass/Fail
TC_Users Testing the Click on Manager Click on Users Users Pass
-001 functionality Manage must be manage Database report sent
of managing Users logged in Users must be to admin
users managed
Add, edit <Valid
and
or delete Users>
updated
users
Save in
database

TC_Users Testing the Click on Manager Click on Users Fail

-002 functionality Manage must be manage database
of managing Users logged in Users must not
users be
Add, edit <Invalid
updated
or delete Users>
users

Save in
database
 Test Case 9:
Project Name: Car Dealership Management System
Module Name: Manage Cars

Created By: Usman Mazhar Bhatti

Reviewed By: Hamza Rauf

Date of Creation: 16-05-2020

Date of Review: 17-05-2020

Test Test Test- Pre- Test Test Expected Post Test

Case-ID Scenario Case Condition Steps Data Result Condition Result:
Pass/Fail
TC_Cars- Testing the Click on Manager Click on Cars Cars report Pass
001 functionality Manage must be manage Database sent to
of managing Cars logged in cars must be admin
cars managed
Add, edit <Valid
and
or delete cars>
updated
cars
Save in
database

TC_Cars- Testing the Click on Manager Click on Cars Fail

002 functionality Manage must be manage database
of managing Cars logged in Cars must not
cars be
Add, edit <Invalid
updated
or delete cars>
Cars

Save in
database
002 functionality Manage mustTest
be Case 10:
manage message:
of managing Sales logged in Sales “Sales
Sales database
Add, edit <Invali
not
or delete d
updated”
Sales Sales>

Save in
database