1. Introduction
 The VRRS (Vehicle Registration & Renewal
System) centralized database allows
information to be shared statewide, aiding
the fight against registering stolen
vehicles. The system also will provide
consistent name information, making sure
registrations and titles match owners'
names on their driver licenses. In the
initial phase of this project is implemented
in the Lahore zone which take six month
according to the plan and feasibility
report.

2. Purpose of Plan
 We plan, design, implement and
manage the automation of the
vehicles registration system. We
primarily provide and manage the
required resources so that the
automation plan will become
successfully done.

3. Project Goals and Objectives
 Accomplish project business goals and objectives within defined
budget and time parameters.
 A favorable and secure agreement between the VRRS Department
and the government.
 Minimizing of Risk Elements during the project
 To achieve Project Deliverables efficiently and effectively.
 To fulfill Organizational Demands
 To manage the Project team members and effective
Communication between them.
 Lower the cost of vehicle registration transactions
 Make vehicle owners accountable in case of unpaid registration
taxes.
 Ensure that all vehicles are regularly inspected to determine if
they are still fit to drive.
 Revoke registration of old vehicles that have been destroyed.
 Fight against registering stolen vehicles.
 Make it possible to link vehicles with their rightful owners.
 Identify and track the vehicles in circulation.
 Enhance the processing of vehicle registration system.
 Increase the efficiency and effectiveness of the registration
process.
 Make the system more reliable and unambiguous.

4. Project Definition
 Statement of requirement
 Stakeholder list
 Project brief
 Scope of work statement
 Work breakdown structure

5. Statement of Requirements
 Although the registration system
already exist but the work done
manually, through the IT
infrastructure in this sector, a lot of
work goes easy. In which we are
going to start the project of the
computerized registration of the
vehicles so that the system of
registration will work efficiently for
the betterment of the countrymen.

6. Opportunity statement
 The government of Punjab is
interested and will support the
implementation of the
computerization of this system. With
the development in the IT
infrastructure and globalization of
the world, the government is tried to
implement the IT infrastructure in
Pakistan also. So there is a great
opportunity to be a success of VRRS

7. Solution statement
 The new system will help not only
car owners but also law enforcement
agencies, financial institutions, auto
dealers and others who use the
state's registration and renewal
system.

8. Alignment to current strategy
 Technical feasibility
 Economic feasibility
 Operational feasibility

9. Business benefits
 Strategic Benefits
 Financial Benefits

10. Organizational benefits
 Through the implementation of the
VRRS, the progress of the
government will move in the positive
direction. By the development of the
IT infrastructure the people take an
interest in the IT field. The new
employment opportunity, especially
for IT professionals came, to work
for their country, ultimately the
county can grow.

11. Technology
 To implement Oracle, H/W from Sun
Solaris is required.. Providing
immediate and measurable return on
information technology investments,
Sunsolris products and services
prove quality, lower costs and
increase the speed at which systems
can be developed, implemented and
supported. Sunsolris is the world
leader in client/server development
technology.

12. Resource requirements
 Department building
 Computerized setup
 LAN/WAN facility
 Software
 Trained professional Staff
 Furniture & fixtures etc.

13. RISKS
• Estimated Project Schedule
• Team Size
• Situational Analysis
• Political risk
• Weaker Participation of Project Team
• Technical risk
• Recruiting risk
• Team member un-knowledgeable of the
importance of the success of VRRS
• Regulatory Risk

15. Risks Breakdown Structure
Project
Technical External Organizational Project Management
Requirements Subcontractor & Project Estimation
Suppliers Dependencies
Technology Regulatory Resources Planning
Complexity and Weather Prioritization Controlling
Interface
Performance & Communication
Reliability
Quality

16. Stakeholders List

17. Project Brief
 Project Title: Vehicle Registration & Renewal
System (VVRS)
 Project Manager: Mr. Tahir Aziz Khan
 Project Sponsor: Government of the
Punjab
 Background
 Existing System Process
 Drawbacks of the Existing System

18. Project Objectives
 Automates enforcement actions and violation processing for non-
compliant vehicles and outstanding violations.
 Increase compliance screening process efficiency and accuracy
 Enhance security and improve vehicle safety
 Reduce the number of uninsured vehicles
 Improve integrity of titling
 Lower the cost of vehicle registration transactions
 Make vehicle owners accountable in case of unpaid registration
taxes.
 Ensure that all vehicles are regularly inspected to determine if
they are still fit to drive.
 Revoke registration of old vehicles that have been destroyed.
 Fight against registering stolen vehicles.
 Make it possible to link vehicles with their rightful owners.
 Identify and track the vehicles in circulation.
 Enhance the processing of vehicle registration system.
 Increase the efficiency and effectiveness of the registration
process.
 Make the system more reliable and unambiguous.

19. Deliverables

20. Organizational Hierarchy

21. Organizational Structure

22. Software Development Introduction
 The developers use this document while working
through the different phases of Software
Development Life Cycle (SDLC). Documenting and
controlling the customer requirements is a
prerequisite for using them, as the basis for
planning, performing and tracking the software
project’s activities throughout the SDLC. This
Software Requirement Specification (SRS) will act
as a template for the proper design of the
application. The document will serve as template
for final approval of the system. The purpose of
this document is to define project requirements.

23. Overview software development
hierarchy
Software Product
Project Management Product Requirement Detail Design Construct Integration & Test
Planning Software Software Software Software
Meeting User Documentation User Documentation User Documentation User Documentation
Administration Training Program Training Program Training Program Training Program
Material

24.  Product Perspective:
• This system is fully independent and totally self-contained. There
are no interfaces to other system. The system will use its own
resources to give services to the End users.
 User Characteristics:
• Initially user will face problem to understand the system but he’ll
get familiarity with this system as he uses the system frequently.
Overall the users are technically able to manipulate the system.
Therefore the system has to be self –instructing.
 General Constraints:
• The user of this system can perform the operations specified for
them. They are not allowed to handle or update other users. For
this administrative rights are required. Each user of this system
has its own login ID and password to enter in the system.
 Assumption and Dependencies:
• For this system we have assumed that the administrator will be
provided with the list of vehicle categories their relating fee i.e.
Token fee, Income tax and P. tax. The system also provided the
list of vehicle owners who are defaulters.

25. Specific Requirements
 User inter face:
 The external user interfaces are given in reference
“appendix 4.4”
 Software Interfaces:
 Windows ME/NT 2000/XP: Windows is used
because it provides better Graphical User Interface
(GUI) and it is easy to operate than other operating
systems.
 IIS Server 5.0: IIS Server is used to interpret the
scripting code written in the files.
 SQL Server 7: SQL server is used to store data. It is
used because of better security and reliability than
other databases.

26. Process Description/Process Specification
(PSPECS): e.g.
 Name: Show Registered Vehicles.
 Description: Display the list of registered
specific category of vehicles.
 Input: Number.
 Output: Display list of Registered
Vehicles.
 Procedure:
 Open connection with database.
 Run query to get list of Registered
Vehicles.
 Show Display query.

28. Logical Diagram
S/W Software House Analysis
START Planning SPECIFICATION
Job Analysis Job Ad Test
Evaluation/Selection
Procurement Tender Ad Selection Interview
Approval/
Agreement
Skills Assessment
Receive Quotation Software Development
Terms of Payment
Training Design
Approve Tender S/W Installation
Testing
Training
Payment
Terms & condition
Evaluation
H/W Installation
FINISH

30. Work Breakdown Structure
(WBS)
Project
HR IT Procurement Operations

31. HR
Hiring Training
Ads Job analysis
Objectives Design Execution Evaluation
Newspaper Govt. Official Initial Screening
Website
Nawai-e
Waqt Completed Application
Dawn
Employment test
Comprehensive interview Conditional Job Offer
Background examination
Medical examinations
Permanent Job offer

32. IT
S/W H/W
VRRS Licensed S/W
Vendor, S/W application Mouse, Disk Microproces
Keyboard Storage sor
units
Oracle 9 i System S/W
External, Optical Hardl
USB examinati
MS Office XP Windows XP ons

33. Procurement
Purchases and Acquisition
Contract Closure
Contracting
Request Seller
Responses
Select Sellers
Contract Administration

35. Costing of the Project

38. Graphical representation

39. PROJECT VALUE

41. Communications Outreach
Monthly Status Reports
 The Project Manager shall provide
monthly written status report. The
reports shall include the following
information tracked against the
Project Plan:
 Summary of tasks completed in previous
month.
 Summary of tasks scheduled for completion
in the next month.
 Summary of issue status and resolutions.

42. THE END