GETGOING GARAGE

Get Going Garage

Project ID-00

Project Advisor: Ma’am Husnaina Akhter

Submitted By

Danyal Tariq ID-19517

Naqash Ahmed ID-19505

Haroon Arshad ID-19507

UNIVERSITY OF EDUCATION I
GETGOING GARAGE

Get Going Garage

MSC IN INFORMATION TECHNOLOGY-2019

A project submitted in partial fulfillment of the requirement for award of the

degree of MSC in Information Technology

PUNJAB GROUP OF COLLEGES

JHELUM CAMPUS

UNIVERSITY OF EDUCATION

LAHORE

UNIVERSITY OF EDUCATION II
GETGOING GARAGE

© Copyright Get Going Garage 2019

UNIVERSITY OF EDUCATION III

GETGOING GARAGE

“I hereby declare that I have read this project documentation and in my

opinion this project is sufficient in term of scope and quality for the
award of the degree of M.sc in Information technology.”

___________________
Project Primary Supervisor Project Examiner
Name: Ma’am Husnaina Akhtar Name:

Designation: Lecturer Designation:

University of Education University of Education

UNIVERSITY OF EDUCATION IV
GETGOING GARAGE

DECLARATION

I declare that this project title entitled “Get Going Garage” is the result of my own
research and development except as cited in the references. This project has not been
accepted for any degree and is not concurrently submitted in candidate for any other
degree. At any time if my statement is found to be incorrect even afterwards of MSC in
Information Technology, the university has the right to withdraw my MSC in IT degree.

Signature: __________________ Signature: _________________

Name: ___Danyal Tariq_ Name: ___Naqash Ahmed ___

Date: _____May 25, 2019______ Date: _____May 25, 2019____

Signature: __________________

Name: __Haroon Arshad_

Date: _____May 25, 2019______

UNIVERSITY OF EDUCATION V
GETGOING GARAGE

PLAGIARISM UNDERTAKEN

We solemnly declare that project work presented in this documentation entitles “Get
Going Garage” is solely our work with no significant contribution from any other
person. Small contribution/help wherever taken has been acknowledged and that
complete project has been written by us.

We understand that zero tolerance policy of the HEC and university of Education,
Lahore towards plagiarism. Therefore, we as authors of the above titled project declare
that no portion of my project documentation and any material used as referenced is
properly referred /cited.

We undertake that if we are found guilty of any formal plagiarism in the above titled
project even after award of MSC degree, the university reserve the rights to
withdraw/revoke our MSC degree and that HEC and the university has the right to
publish our name on the HEC/university website on which names of students are placed
who submitted plagiarized projects.

Signature: __________________ Signature: _________________

Name: ___Danyal Tariq _ Name: ___Naqash Ahmed ___

Date: _____May 25, 2019______ Date: _____May 25, 2019____

Signature: __________________

Name: __Haroon Arshad _

Date: _____May 25, 2019______

UNIVERSITY OF EDUCATION VI
GETGOING GARAGE

CERTIFICATE OF APPROVAL

This is to certify that the project work presented in this documentation entitled, “Get
Going Garage”, was conducted by “Danyal Tariq”, “Naqash Ahmed”& “Haroon
Arshad”, under the supervision of “Ma’am Husnaina Akhtar”. No part of this project
has been submitted anywhere else for any degree. This project is submitted to the
“Punjab Group of Colleges Jhelum” in partial fulfillment of the requirements of the
degree of MSC in Information Technology.

Signature: __________________ Signature: _________________

Name: ___Danyal Tariq _ Name: ___Naqash Ahmed ___

Date: _____May 25, 2019______ Date: _____May 25, 2019____

Signature: __________________

Name: __Haroon Arshad_

Date: _____May 25, 2019______

________________________
Project Primary Supervisor Project Examiner
Name: Ma’am Husnaina Akhtar Name:

Designation: Lecturer Designation:

University of Education University of Education

UNIVERSITY OF EDUCATION VII

GETGOING GARAGE

OFFICE OF CONTROLLER OF EXAMINATION

NOTIFICATION

No: Date:

It is notified for the nomination of all the concerned that Mr. DANYAL TARIQ,

Mr. NAQASH AHMED, Mr. HAROON ARSHAD MSC IT students of IT Department

of University of Education have completed all the requirements for the award of MSC
IT Degree in the discipline of Information Technology as per detail given below:

Cumulative Result

Cumulative
MSC in Information Technology Credit Hours: ____________
Grade Point
Registration Complete Course Project Total Average
No. Name work
(CGPA)

Project Title: GET GOING GARAGE

Name of Supervisor: Ma’am Husnaina

Signed by

Controller of Examination
UNIVERSITY OF EDUCATION VIII
GETGOING GARAGE

ACKNOWLEDGEMENT

We truly acknowledge the cooperation and help made by Ma’am Husnaina Akhtar,
Supervisor, Punjab Group of Colleges Jhelum. She has been a constant source of
guidance throughout the course of this project. We are also thankful to our friends and
families whose silent support led us to complete our project.

1. Mr. Zeeshan Anwar

2. Ma’am Husnaina Akhtar

Date:

UNIVERSITY OF EDUCATION IX
GETGOING GARAGE

ABSTRACT

Technology brought power back to the people. Today we are changing the world using
technology. We are living in the era where everyone wants ease in life. If we talk about
advancement, then today websites are the most widely known entities and every day
we want something new to entertain ourselves. Get Going Garage is a website that will
help purchase vehicles and car rental services of their choice while knowing price
comparison. It will provide the facility of purchasing vehicles via ease of conduct of
transaction & money transfer. Users can search, shop and can see their cars and their
relevant data through a specified view that is associated with a potential GUI. Car
rental, Car purchase & Car sale will be the modular services up for grabs. These features
are all in two-way mode which is for the ease of user. One for customer & second for
admin.

• Back Ground
Technology is enhancing the life of people, making it better day by day. The
same thing we thought to facilitate the people in order to save their time and
money. Get Going Garage is for the end customers, which can make the cars
visible to customer even if it is not present in the shop. Customers get the
vehicles rated after delivery & use. Further guidance to vehicles goodwill is
associated with the use & handling of similar entities.

• Objectives/Aim of the study

Goal of this project is to develop a website through which customers will be
able to purchase, sale, rent vehicles while comparing vehicle rates.
Companies will be able to advertise their vehicles simultaneously. The other
goal of the project is to provide the fast and efficient rental services. A
customer can visualize:
a) Vehicles comparison.
b) Advertise vehicles.
c) Auto-Mobile spare parts.
d) Rate rental vehicles.

UNIVERSITY OF EDUCATION X
GETGOING GARAGE

• Findings
We are living in the era where everyone wants ease in life. Today, websites are
a major part of online buying & selling through the internet. Get Going Garage
is a website that will help customers to visualize local market by sitting in
home or anywhere. It provides facility of visualizing all vehicles which are
present in a specific shop window. User can search, shop, see vehicles and
relevant data through this website. Services will include rental guidance,
purchasing & selling including old & new ones.

• Conclusions
Technology brought power back to the people. This website gives facility to
shopkeepers/sellers to upload their vehicle details, new offers. Customers can
see all shops vehicles and can rate vehicles.

• Implications
Today we would change in using technology. Over website is developing for
the mobile/laptop/desktop users. It only requires a system device with at least
an internet connection.

• Limitations
All the feature of the website consists of two approaches for the ease of the
user. 1st for customer& 2nd for admin.

UNIVERSITY OF EDUCATION XI
GETGOING GARAGE

1 Table of Contents
1. Gathering & Analyzing Information .......................................................... 1
1.1 Introduction .............................................................................................................. 2

1.2 Problem Statement ................................................................................................... 3

1.3 Project Goals & Objectives ...................................................................................... 3

1.4 High Level System Components ............................................................................. 4

2. Software Requirements Specification ......................................................... 5

2.1 Functional Requirements ......................................................................................... 6

2.2 Non Functional Requirements ................................................................................. 7

3. Analysis ( Use Case Description and Use Case Model ) ....................... 8

3.0 Car Rental Use Case Diagram ................................................................................. 9

3.1 Car Buying and Selling Use Case Diagram ........................................................... 10

3.2 Member Registration..............................................................................................11

3.3 Reservation of Car..................................................................................................12

3.4 Customers Feedback...............................................................................................13

3.5 Payment of Car.......................................................................................................13

3.6 Add a New Car.......................................................................................................14

3.7 Context Level Data Flow Diagram........................................................................14

4. Design ( With Description Of Earth Diagram ) .................................... 15

4.1 Project Product Scope ............................................................................................ 16

4.2 Project Product Costing ......................................................................................... 17

4.3 Critical Path ........................................................................................................... 18

4.4 AON Diagram ........................................................................................................ 19

4.5 Gantt Chart ............................................................................................................. 20

5. Graphical User Interfaces ............................................................................. 21

UNIVERSITY OF EDUCATION XII

GETGOING GARAGE

5.1 registration form..................................................................................................... 22

5.2 Login here .............................................................................................................. 22

5.3 Home Page 1 ......................................................................................................... 23

5.4 Home page 2 .......................................................................................................... 23

5.5categories………………………………………………………..................……...24

5.6 Car rental ...............................................................................................................24

5.7 Car rental form.......................................................................................................25

5.8 Buing & Selling Form............................................................................................25

5.9 Car buy form..........................................................................................................26

5.10 Car selling form....................................................................................................26

6. Testing ..................................................................................................................27
6.1 Testing....................................................................................................................28

6.2 Test Cases ..............................................................................................................28

6.3 Test plan.................................................................................................................30

6.4 User Interface Testing............................................................................................35

7. Conclusion And Future Work .....................................................................40

7.1 References ..............................................................................................................41

UNIVERSITY OF EDUCATION XIII

GETGOING GARAGE

CHAPTER NO. 1

Gathering & Analyzing Information

UNIVERSITY OF EDUCATION 1
GETGOING GARAGE

1.1 Introduction
It is digital age and world has turned into global village. Technology is enhancing
the life of people day by day. The same thing we thought to facilitate the people in order
to save their time and money. We thought to develop an all-rounder website
“Perfectstore.cf” for the end customers; so that customers can buy vehicles of their
choice by comparing rates & quality. At the same time, companies will be advertising
their vehicles and they will get the vehicles rating by users.

Project is divided into three parts.

Customer Side:

On customer side, customers can get access to the website through their mobile
numbers. They will make their profile there, after doing this they will be able to get
access to their desired city. In city, all categories of vehicles will be available like family
cars, luxury cars, vans etc. After selecting desired category, they will get list of all
vehicles lying in that category. From the list they will select specific vehicles and then
data of vehicles will be visible to them. They can get detail of vehicles and they can
rate the vehicles too. They can change the reviews & ratings of the vehicles in the same
way.

Admin Side:

As all the features that we have provided in the customer side, website can be
modified or maintained in Admin-side of the website. Admin can add new city, new
vehicles and new category. He will provide account to companies. He will upload new
policies & rules regarding the vehicles alongside vehicles authenticity. He will manage
the data regarding vehicles that are going to be uploaded soon.

UNIVERSITY OF EDUCATION 2
GETGOING GARAGE

1.2 Problem Statement.

This project aims to develop an online vehicle purchasing for customers with the
goal so that it is very easy to buy your loved vehicles from an extensive number of
online purchasing sites available on the web. With the help of this you can carry out an
online purchasing from your home or any place you are staying. Here is no compelling
reason to go to the purchasing centers in your daily rotten life or during festival seasons.
You simply require a PC, laptop or android mobile and one important payment sending
option to buy online.

1.3 Project Goals & Objectives

Goal of this project is to develop a website to facilitate users to compare the quality &
prices of vehicles, cars and to get benefit from the vehicle’s variety through category.
Companies can advertise their vehicles

• Companies can make advertisements of their vehicles

• Companies can manage according to their requirements
• Companies can get rating of their vehicles from customers
• Customers can visit market through website
• Customers can rate the vehicles

The other goal of the project is to provide the fast and efficient delivery of the
vehicles.

• Customers can choose from multiple options to get the vehicles delivered to
their doorstep.

Provides the facility to user to visualize:

e) Vehicles comparison.
f) Vehicles prices.
g) Auto mobile parts.
h) Rate vehicles.
UNIVERSITY OF EDUCATION 3
GETGOING GARAGE

1.4 High-level system components

We are going to present information about the main functional units of the entire
system. High level system components are a set of modules assembled together
to deliver a solution to a present problem. Our high-level components are:
• Sign-up
• Login
• Managing information
• Providing Services
• Providing Packages
• Providing maintenance
• Generating receipts
• Logout

1.5 Tools and technologies used with reasoning

Xampp server: Xampp is a regularly updated to the latest releases of Apache,
MariaDB, PHP and Perl.it also come with the number of other modules. XAMPP also
provide support for creating and manipulating database.

Microsoft Visio: Microsoft Visio is software designed to translate complex

information from text and table into diagrams.

Star UML: Star UML is an open source software modeling tool that supports UML
(Unified Modeling Language). It is based on UML version 1.4, provides eleven
different types of diagram and it accepts UML 2.0 notation.

Visual studio: Microsoft Visual Studio is an integrated development

environment (IDE) from Microsoft. It is used to develop computer programs, as well
as websites, web apps, web services and mobile apps.

Adobe Photoshop (interfaces): Adobe Photoshop is a raster graphics

editor developed and published by Adobe Inc. for Windows and macOS. It was
originally created in 1988 by Thomas and John Knoll.

UNIVERSITY OF EDUCATION 4
GETGOING GARAGE

CHAPTER NO.2

Software Requirements Specification

UNIVERSITY OF EDUCATION 5
GETGOING GARAGE

2.1 Functional Requirements

Requirement analysis is a software engineering technique that is composed of the

various tasks that determine the needs or conditions that are to be met for a new or
altered product, taking into consideration the possible conflicting requirements of the
various users.

Functional requirements are those requirements that are used to illustrate the internal
working nature of the system, the description of the system, and explanation of each
subsystem. It consists of what task the system should perform, the processes involved,
which data should the system holds and the interfaces with the user. The functional
requirements identified are:

a) Customer’s registration: The system should allow new users to register

online and generate membership card.
b) Online reservation of cars: Customers should be able to use the system to
make booking and online reservation.
c) Automatic update to database once reservation is made or new customer
registered: Whenever there’s new reservation or new registration, the system
should be able update the database without any additional efforts from the
admin.
d) Feedbacks to customers: It should provide means for customers to leave
feedback

UNIVERSITY OF EDUCATION 6
GETGOING GARAGE

2.2 Non-Functional Requirements

It describes aspects of the system that are concerned with how the system provides the
functional requirements. They are:

a) Security: The subsystem should provide a high level of security and integrity
of the data held by the system, only authorized personnel of the company can
gain access to the company’s secured page on the system; and only users with
valid password and username can login to view user’s page.
b) Performance and Response time: The system should have high performance
rate when executing user’s input and should be able to provide feedback or
response within a short time span usually 50 seconds for highly complicated
task and 20 to 25 seconds for less complicated task.
c) Error handling: Error should be considerably minimized and an appropriate
error message that guides the user to recover from an error should be provided.
Validation of user’s input is highly essential. Also, the standard time taken to
recover from an error should be 15 to 20 seconds.
d) Availability: This 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 the business process
is not severely affected.
e) Ease of use: Considered the level of knowledge possessed by the users of this
system, a simple but quality user interface should be developed to make it easy
to understand and required less training.

UNIVERSITY OF EDUCATION 7
GETGOING GARAGE

CHAPTER NO.3

Analysis
(Use Case description and Use Case Model)

UNIVERSITY OF EDUCATION 8
GETGOING GARAGE

3.0 Car Rental Use Case Diagram

UNIVERSITY OF EDUCATION 9
GETGOING GARAGE

3.1 Car Buying And Selling Use Case Diagram

UNIVERSITY OF EDUCATION 10
GETGOING GARAGE

3.2 Member Registration

UNIVERSITY OF EDUCATION 11
GETGOING GARAGE

3.3 Reservation of Car

UNIVERSITY OF EDUCATION 12
GETGOING GARAGE

3.4 Customers feedback

3.5 Payment of Car

UNIVERSITY OF EDUCATION 13
GETGOING GARAGE

3.6 Add a New Car

3.7 Context Level Data Flow Diagram

UNIVERSITY OF EDUCATION 14
GETGOING GARAGE

CHAPTER NO. 4

Design (With Description of Each Diagram)

UNIVERSITY OF EDUCATION 15
GETGOING GARAGE

4.1 Project/Vehicles Scope

This project traverses a lot of areas ranging from business concept to computing field,
and required to perform several researches to be able to achieve the project objectives.

The area covers include:

• Car rental industry: This includes study on how the car rental business is being done,
process involved and opportunity that exist for improvement.
• PHP Technology used for the development of the application.
• General customers as well as the company’s staff will be able to use the system
effectively.
• Web-platform means that the system will be available for access 24/7 except when
there is a temporary server issue which is expected to be minimal.

4.2 Project/Vehicles Costing

Project Cost Estimation by Function Point Analysis

No. of External Inputs: 30

No. of External Outputs: 35

No. of External Inquiries: 14

No. of Internal Logical Files: 6

No. of External Interface Files: 5

UNIVERSITY OF EDUCATION 16
 GETGOING GARAGE

Calculate Count-total:

Information Domain Value Low Avg. High Count FP Count

EI 10*3=30 10*4=40 10*6=60 30 130

EO 12*4=48 13*5=65 10*7=70 35 183

EQ 5*3=15 5*4=20 4*6=24 14 59

ILF 2*7=14 2*10=20 2*15=30 6 64

EIF 2*5=10 2*7=14 1*10=10 5 34

Count-Total = 470

Data Communication 5

Distributed Data Processing 5

Performance 5

Heavily Used Configuration 3

Transaction Rate 4

On-Line Data Entry 3

End User Efficiency 4

On-Line Update 5

Complex Processing 4

Reusability 4

Installation Ease 3

Operational Ease 3

Multiple Sites 3

Facilitate Change 4

Total = ∑ Fi 55

“Table. 1: Calculate Count-Total”

Calculate Function Point:

UNIVERSITY OF EDUCATION 17
GETGOING GARAGE

FP est. = Count Total * [0.65 + 0.01 * (Fi)]

= 470 * [0.65 + 0.01 * (55)]

= 470 *[1.2]

FP est. = 564

For our project

Productivity = 40.5 LOC/pm

Labor Rate = 20000 per month

Effort = FP est. / productivity

= 564/ 40.5

= 13.9 pm

Now,

Cost/FP = Labor Rate/prod

= 20000/40.5

= 494Rs/FP

Total Project Cost = FP est. * (Cost/FP)

= 470* (494) = 232,098 R

UNIVERSITY OF EDUCATION 18
GETGOING GARAGE

3.8 4.3 Critical Path

3.9 CPM - Critical Path Method

Activity Name Immediate Duration in Weeks

Predecessor

A Initiation None 1

B Requirement Gathering A 2

C Feasibility Study B 3

D Costing B, C 1

E Scheduling D 1

F Requirement Engineering B, E 2

G Design B, F 2

H Implementation G 6

I Testing H, G 3

J Deployment H, I 2

“Table. 2: C P M (Critical Path Method)”

4.4 AON Diagram

UNIVERSITY OF EDUCATION 19
GETGOING GARAGE

4.5 Gantt chart

Dec 2015 Jan 2016 Feb 2016 Mar 2016 Apr 2016 May 2016 Jun 2016 Jul 2016 Aug 2016 Sep 2016 Oct 2016 Nov 2016 Dec 2016
ID Task Name Start Finish Duration
6/12 13/12 20/12 27/12 3/1 10/1 17/1 24/1 31/1 7/2 14/2 21/2 28/2 6/3 13/3 20/3 27/3 3/4 10/4 17/4 24/4 1/5 8/5 15/5 22/5 29/5 5/6 12/6 19/6 26/6 3/7 10/7 17/7 24/7 31/7 7/8 14/8 21/8 28/8 4/9 11/9 18/9 25/9 2/10 9/10 16/10 23/10 30/10 6/11 13/11 20/11 27/11 4/12 11/12 18/12

1 A:Preliminary investigation 12/7/2015 1/29/2016 8w

2 B:System analysis 1/11/2016 3/15/2016 9w 2d

3 C:Project planning 2/1/2016 3/10/2016 5w 4d

4 D:System design 2/25/2016 4/25/2016 8w 3d

5 E:Logical design 3/28/2016 5/6/2016 6w

6 F:Physical design 4/15/2016 5/30/2016 6w 2d

7 G:User interface design 5/2/2016 6/10/2016 6w

8 H:Database design 5/20/2016 6/24/2016 5w 1d

9 I:Admin login module 6/10/2016 7/8/2016 4w 1d

10 J:Insert stock module 6/27/2016 7/27/2016 4w 3d

11 K:View stock module 7/11/2016 8/11/2016 4w 4d

12 L:Insert employe info module 7/27/2016 8/26/2016 4w 3d

13 M:View employe info 8/8/2016 9/8/2016 4w 4d

14 N:Delete employe info module 8/22/2016 9/22/2016 4w 4d

15 O:Integration 9/19/2016 10/19/2016 4w 3d

16 P:Testing 6/15/2016 10/20/2016 18w 2d

17 Q:Implementation 9/1/2016 11/2/2016 9w

18 R:Maintenace 11/2/2016 1/6/2017 9w 3d

“Diagram. 2 Gantt Chart”

4.6 Context Level Data Flow Diagram

UNIVERSITY OF EDUCATION 20
GETGOING GARAGE

CHAPTER NO. 5

Graphical User Interfaces

UNIVERSITY OF EDUCATION 21
GETGOING GARAGE

5.1 Registration Form.

5.2 Login here.

UNIVERSITY OF EDUCATION 22
GETGOING GARAGE

5.3 Home page 1

5.4 Home page 2

UNIVERSITY OF EDUCATION 23
GETGOING GARAGE

5.5 Categories.

5.6 Car Rental.

UNIVERSITY OF EDUCATION 24
GETGOING GARAGE

5.7 Car Rental Form.

5.8 Buying & Selling Form

UNIVERSITY OF EDUCATION 25
GETGOING GARAGE

5.9 Car Buy Form.

5.10Car Selling form.

UNIVERSITY OF EDUCATION 26
GETGOING GARAGE

CHAPTER NO. 6

Testing

UNIVERSITY OF EDUCATION 27
GETGOING GARAGE

6.1 Introduction:

This deliverable is based on the IEEE standard of software testing. IEEE Software
Testing is an internationally agreed. For software testing that can be used with in any
software development lifecycle. By implementing this standard, you will be adopting
the only internationally-recognized agreed standards for software testing, which will
provide your organization with a high-quality approach to testing that can be
communicated throughout the world.

6.2 Test Case Scenario Sample

Test Case ID: 01

Test Case Name: Registration

Test Priority: Medium/ High/ Low

Preconditions: The user must have registered his/her self.

Post Conditions:

1. The User will enter registration details in the system.

2. The user will have access to the login.

S. Action Inputs Expected Actual Test Te Test

N Outcomes Outputs Application st Comments
Re
sul
t

1 Load Website GETGOIN GETGOIN GETGOING Pa Haroon

Website G G GARAGE ss 03/08/2019
GARAGE GARAGE Launch
Registration Registration Successful
Page Page
2 Enter Enter Registered Registered GETGOING Pa Naqash
Registration required Successfully Successfully GARAGE ss 04/08/2019
Details registrati Launch
on details Successful

UNIVERSITY OF EDUCATION 28
GETGOING GARAGE

Test Case ID: 02

Test Case Name: Login

Test Priority: Medium/ High/ Low

Preconditions: The user must have valid account.

S. Action Inputs Expected Actual Test Test Test

N Outcomes Outputs Application Result Comments

1 Open Website GETGOING GETGOING GETGOING Pass Danyal

Website GARAGE GARAGE GARAGE 01/08/2019
Login Page Login Page Launch
Successful
2 Enter User Login Login GETGOING Pass Junaid
Correct valid id Success Success GARAGE 01/08/2019
Email & and Launch
Password password Successful

Test Case ID: 03

Test Case Name: book now

Test Priority: Medium/ High/ Low

Preconditions: The user must get feedback from admin.

S. Action Inputs Expected Actual Test Test Test

N Outcomes Outputs Application Result Comments

1 Book a Select a Car View Car GETGOING Pass Usama

Car Car Page Selected GARAGE 01/08/2019
Launch
Successful
2 Add to Car added Add to cart Add to cart GETGOING Pass Zeeshan
Cart in cart Successfully Successfully GARAGE 01/08/2019
Launch
Successful

UNIVERSITY OF EDUCATION 29
GETGOING GARAGE

Test Case ID: 04

Test Case Name: Log out

Test Priority: Medium/ High/ Low

Preconditions: The user may log out after visiting the website.

S.N Action Inputs Expected Actual Test Test Test

Outcomes Outputs Application Result Comments

1 Enter Add GETGOING GETGOING GETGOING Pass Danyal

Correct login GARAGE GARAGE GARAGE 01/08/2019
Email & details Login Page Login Page Launch
Password Successful
2 Log out User Log out Log out GETGOING Pass Naqash
may Successfully Successfully GARAGE 01/08/2019
click Launch
log out Successful
icon.

6.3 . Test Plan

3.10 6.3.1. Purpose.
The test plan is a process to assist in creating an overall test plan for the project. This
process does not address the creation of the specific test cases. The accepting should be
involved in the risk assessment and test prioritization activities. It describes the scope,
approach, resources, and schedule of the testing activities.

6.3.2. Outline
A test plan shall have the following structure:

• Test plan identifier

• Introduction
• Test items
• Features to be tested
• Features not to be tested
• Approach
• Item pass/fail criteria
UNIVERSITY OF EDUCATION 30
GETGOING GARAGE

• Suspension criteria and resumption requirements

• Test deliverables
• Testing tasks
• Environmental needs
• Responsibilities
• Staffing and training needs
• Schedule
• Risks and contingencies
• Approvals

6.3.2.1. Test Plan Identifiers

This is the test plan on "Get Going Garage". Our main purpose is to build a successful
system that help us to manage the purchasing, selling and rent records which is done
manually. We want to automate the system and shifting the whole record into the
computer for faster manipulation of records.

6.3.2.2. Introduction
This document is intended to give a complete planning of a systematic strategy for
software testing of “Get Going Garage”.

UNIVERSITY OF EDUCATION 31
GETGOING GARAGE

6.3.2.3. Test Items

In this section we will provide a list of all those components that has been identified as
test items. All of the items that constitute the "Get Going Garage" will be tested during
the system test to ensure that they work together to implement the user's requirements.

• Mange profile
• Mange information
• Mange vehicle categories
• Mange bill
• Mange services
• Mange customer info

The basic performance test:

The most critical performance measures to test are:

• Response time for Admin/customer login.

• Response time for inserting/updating information.
• Response time for requested records.

UNIVERSITY OF EDUCATION 32
GETGOING GARAGE

6.3.2.4. Features to Be Tested

The following is the list of features to be tested:

Features Priority Description

Add profile 1 Create profile for admin

Add stock 1 All stock record in the

system

Add vehicles of all categories 2 All detail about the

product

Generate bill 3 Detail about the bill

recorded in the system

Add / update sale 1 Detail about the sale

product

Add customer info 1 Add customer record in

the system

Login 1 Login as authenticate

user

Logout 1 Logout from the system

Delete info 2 Delete Information

UNIVERSITY OF EDUCATION 33
GETGOING GARAGE

6.3.2.5. Approach
We are following these test approaches which are given here under as:

(1) White Box Testing

In white box testing, the UI is bypassed. Inputs and outputs are tested directly at the
code level and the results are compared against specifications.

(2) Black Box Testing

Black box testing typically involves running through every possible input to verify that
it results in the right outputs using the software as an end-user would. We have decided
to perform Equivalence Partitioning and Boundary Value Analysis testing for the
website.

3.10.1 (1) Equivalence Class Partitioning

In considering the inputs for our equivalence testing, the following types will be used:

• Legal input values (Valid Input)–Test values with in boundaries of the

specification equivalence class.
• Illegal input values (Invalid Input)–Test equivalence classes outside the
boundaries of the specification.
Using these Valid and Invalid classes testing engineer will generate test
cases.

3.10.2 (2) Boundary Value Analysis

The acceptable range of values for this application was set by the development team.
At the time of testing developer will define the boundary value and generate test case
for performing the boundary value analysis.

• Integration Testing

Integration tests exercise an entire subsystem and ensure that as set of components
play nicely together.

UNIVERSITY OF EDUCATION 34
GETGOING GARAGE

• System Testing

The goals of system testing are to detect faults that can only be exposed by testing the
entire integrated system or some major part of it. Generally, system testing is mainly
concerned with areas such as performance, security, validation, load, and configuration
sensitivity. But in our case, we well focus only on Performance and load testing.

3.11 (a)Performance Testing

This test will be conducted to evaluate the fulfillment of a system with specified
performance requirements. It will be done using black-box testing method. And this
will be performed by:

• Storing the maximum data in the file and trying to insert, and observe how the
application will perform when it is out of boundary.
• Deleting data and check if it follows the right sorting algorithm to sort the
resulting data or output.

3.11.1 (b)Load Testing

The test will perform after executing a performance test. This will help to develop the
loading quality of the website. Tester will perform the test using visual studio and
generate a performance graph

6.4 User Interface Testing

User Interface (UI) testing verifies a user’s interaction with the software. The goal of
UI testing is to ensure that the UI provides the user with the appropriate access and
navigation through the function soft he target-of-test. In addition, UI testing ensures
that the objects within the UI function as expected and conform to corporate or industry
standards.

UNIVERSITY OF EDUCATION 35
GETGOING GARAGE

6.4.1.1 Item pass/fail criteria

The criteria for each phase of testing must be met before then next phase can commence.
Now the criteria for pass and failure given below.

• According to the given scenario the expected result needs to take place then
the scenario will be considered as pass otherwise that criteria should be failed.
• If an item tested 10 times, 9 times perfectly worked and single time do not
work properly then it will consider as fail case.
• System crash will be considered as fail case.
• After submitting a query in the system, if expected page won’t appear then it
will be considered as fail case.

6.4.1.2 Test deliverables

The following documents will be generated as a result of these testing activities:

• Test plan (this document)

• Test Design Specifications
• Test case specifications
• Test procedure specifications
• Test Item transmittal reports
• Test logs
• Test incident report.
• Test summary reports

UNIVERSITY OF EDUCATION 36
GETGOING GARAGE

6.4.1.3 Testing tasks

TASK ASSIGNED TO

Create Acceptance Test Plan Danyal

Create Integration Test Plan Naqash

Define Unit Test rules and Procedures Haroon

Define Turn over procedures for each level Danyal

Verify prototypes of Screens Haroon ,Naqash

6.4.1.4 Environmental needs

The following elements are required to support the overall testing effort at all levels
within the “Get Going Garage” project:

• Access to the Get Going Garage (web system).

• Access to the database.
• Access to the environments used by the Admin.
• Access to the environments used by the Customer.
• Systems functional structure created by Mind map.
• Use visual studio for performance and load testing.

6.4.1.5 Responsibilities
Identify groups responsible for managing, designing, preparing, executing, witnessing,
checking and resolving that will help the whole team to deliver a quality full web
system.

UNIVERSITY OF EDUCATION 37
GETGOING GARAGE

6.4.1.6 Staffing and training needs

This section outlines show to approach staffing and training the test roles for the project.
Staffing is fixed for the duration of this project. It is likely most of the staff will assume
some testing role.

The following roles are identified:

• Project Manager: Responsible form and aging the total implementation of the
Website.
• Test Manager: Responsible for developing the master test plan, reviewing the
test deliverables, managing the test cycles, collecting metrics and reporting
status to the Project Manager, and recommending when testing is complete.
• Test Engineer: Responsible for designing the tests, creating the test
procedures, creating the test data, executing tests, preparing incident reports,
analyzing incidents, writing automated test procedures, and reporting metrics
to the test manager.
• The test manager and test engineers should be familiar with the system
development life cycle methodology.

UNIVERSITY OF EDUCATION 38
GETGOING GARAGE

6.4.1.7 Risks and contingencies

Serial Risk List Contingencies Plan

No

1 Data can be destroyed Data can recover thorough the

software.

2 Unauthorized access Use the security process to make

the system secure

3 Hardware can be destroyed Use affecting protections to secure

the hardware and back up

4 System might be slow Use boost up clears for the fast

speed

UNIVERSITY OF EDUCATION 39
GETGOING GARAGE

CHAPTER NO.7

Conclusion and Future Work

UNIVERSITY OF EDUCATION 40
GETGOING GARAGE

CONCLUSION & FUTURE WORK

Car rental business has emerged with a new goody compared to the past experience
where every activity concerning car rental business is limited to a physical location
only. Even though the physical location has not been totally eradicated; the nature of
functions and how these functions are achieved has been reshaped by the power of
internet. Nowadays, customers can reserve cars online, rent car online, and have the
car brought to their door step once the customer is a registered member or go to the
office to pick the car.

The web-based car rental system has offered an advantage to both customers as well
as Car Rental Company to efficiently and effectively manage the business and
satisfies customers. On the other hand, our web site introduces to customers to buy
and sell car through our website

Reference

• https://www.youtube.com/playlist?list=PLshdtb5UWjSp0879mLeCsDQN6L73XBZTk
• Wikipedia.org
• www.w3schools.com

UNIVERSITY OF EDUCATION 41