Metropolitan Service System (MV)

7/23/2019 Metropolitan Service System (MV)

1/52

METROPOLITAN SERVICE SYSTEM

(MV)

FINAL PROJECT

Virtual University

Submitted By:

MC070400829

Nooruddin Charania

Department of Management Sciences,Virtual University of Pakistan

1


2/52

Dedication

This project is dedicated to my Virtual University teachers who

worked very hard in providing a good quality education, to my

friends, to my work colleagues and all who has given me ideas,

suggestion and motivation in completing this project on time.

2


3/52

Acknowledgement

I want to acknowledge this project to Metropolitan Service System

User, Stakeholders, Operator, Administrator and all who

segregated to work in order to achieve the objectives as a whole.

My theory is with new era of devices and social networking

systems should be enhanced. The major breakthrough of

successful implementation of this project will be on hypothetical

testing on removing skill deficiencies and overhead cost by

innovation of new technologies from the field of IT

3


4/52

Preface

About this project, I must say that now city Govt should focus on

migration from old legacy to new one as all other provinces has

already been moved to new one My project is just a beginning.

Nooruddin Charania, 30-12-2012, Karachi

4


5/52

Table of Contents

Table of Contents .................................................................................................... 5

CHAPTER 1:

Background and Introduction ..................................................................................... 8

BACKGROUND

................................................................................................................................ 9

Metropolitan Service System (Motor Vehicle) ....................................................... 9

How to maintain a good REPO on the Project ....................................................... 9

INTRODUCTION

TO ORGANIZATION AND PROJECT .......................................................................... 10

About Organization ............................................................................................ 10

Features of the Project ....................................................................................... 10

CHAPTER 2:

Software Requirement Specification ......................................................................... 11

SCOPE OF THE PROJECT ..................................................................................... 12

Introduction ........................................................................................................ 12

Objectives .......................................................................................................... 12

Software Breakdown Structure ........................................................................... 13

REQUIREMENTS ..................................................................................................... 14

Functional Requirements .................................................................................... 14

Non-Functional Requirements ............................................................................ 17

USE CASE DIAGRAMS ............................................................................................ 18

Actors ................................................................................................................. 18

Actors Goal........................................................................................................ 19

Use Case Diagram .............................................................................................. 20

5


6/52

USAGE SCENARIOS ................................................................................................ 22

Maintain Registration Record ............................................................................ 22

Issues a Number Plate ........................................................................................ 23

Update Vehicle List ............................................................................................. 23

Charge/Fees and Taxes ...................................................................................... 24

Letter of Clearance ............................................................................................. 25

AFR Number Plate .............................................................................................. 25

Registered Number Plate ................................................................................... 27

Application For Registration ............................................................................... 27

Verification ......................................................................................................... 30

Update Information ............................................................................................ 30

CHAPTER 3:

Designing the Project ............................................................................................... 32

OVERVIEW: .......................................................................................................... 33

Project Schedule: ............................................................................................ 33

Quality Assurance .............................................................................................. 34

DATA FLOW DIAGRAM: ........................................................................................ 35

The Context Diagram ......................................................................................... 35

Level 1 Diagram ................................................................................................. 36

.............................................................................................................................. 38

SEQUENCE DIAGRAM:........................................................................................... 39

CHAPTER 4:

Project Analysis ........................................................................................................ 46

SOFTWARE/PROJECT BENEFITS: ............................................................................ 47

Overcoming Limitation ...................................................................................... 47

Critical Success Factors .................................................................................... 48

6


7/52

CONCLUSION: ....................................................................................................... 51

Help Sindh Government ................................................................................... 51

RECOMMENDATION:............................................................................................ 52

Cloud Computing Virtualization ....................................................................... 52

7


8/52

CHAPTER 1:

Background and Introduction

8


9/52

BACKGROUND

Metropolitan Service System (Motor Vehicle)

The project is on the improvisation of better, efficient and customer

oriented motor vehicle registration system. Ensuring right information

will reach within time to assist customer in registering of new vehicle

either local or imported. Better scalability in providing efficientverification through helpdesk as well as new technologies such as

mobile, web interfaces and prompt action against stolen or lost vehicle

which were neglected by previous system

How to maintain a good REPO on the Project

There are various techniques to maintain the MV registration process.

Step by step approach to migrate data from old software to new. Rapiddevelopment as civic sales and purchase department using a

computerize system. Better connectivity through cisco router, switches

and VOIP Phones. Risk management techniques to mitigate risk in

designing phase to save time and cost.

9


10/52

INTRODUCTION

TO ORGANIZATION ANDPROJECT

About Organization

Karachi is a metropolitan city. But the registration of Motor Vehicle

authorities lies with the jurisdiction of the Sindh Government. Only

Federal Govt. issues number plates for foreign diplomats(red), the

military, police and department(green).

In Sindh, Plates start with alphabets followed by a string of numbers.

Features of the Project

Manages motor vehicle and owner data

Management of number plates

Add/update Lost and Stolen Car

Status check on inspection of vehicle

Record of payment of all levied taxes

10


11/52

CHAPTER 2:

Software RequirementSpecification

11


12/52

SCOPE OF THE PROJECT

Introduction

Metropolitan Service System is a city services system. Which is huge

and gigantic? Due to limited time frame this software project will only

cover an integral part i.e. Motor Vehicle (MV) . From here after Motor

Vehicle will be refer as MV

Objectives

Any project either big or small needs clearly defined objectives that are

specific, measurable, achievable, relevant and time-bound. The

software project will be broken down into three categories

Main Objectives: The primary purpose of the project is to cover areas

of MV registration; Issuance of Number Plate, provide inquiries relating

to MV; Proper documentation which includes identification proof of the

owner; and any other entity which has direct relationship with MV

System.

Additional Objectives: The secondary purpose of the project is to cover

areas of Civic Sales and Purchase office of MV, Mark Stolen or illegal

Cars, and entertain Police Inquiries relating to MV.

Non Objectives: This part will give clarity to scope; It set boundaries

that beyond the area of MV and its related entities no other service

12


13/52

sector will be used in this project. This has to be done to avoid any

ambiguity.

Software Breakdown Structure

Based on our scope we can now define Software Breakdown Structure.

This only deals in MV Services. Specifically, wheeled land vehicle such

as cars, motorcycles, busses,

off- highway vehicles, light trucks, light duty trucks, heavy

construction equipment and off-road vehicles.

13

Metropolitan Services System

Water StreetsTranspo

rt

Transpo

rt

Foods

Inspectio

n

Fire

Departmen

t

Police Ambulance

Health

Departmen

t

School

InfrastructureMotor

VehicleOperations


14/52

REQUIREMENTS

Functional Requirements

A functional requirement is a set of inputs, the behavior which includes

calculations, technical details, data manipulation and processing and

other specific functionality that define what a system is supposed to

accomplish.

Software Size Estimation: is a method of determining the relativephysical size of the application software to be developed. Its estimation

can be used to guide the allocation of resources and to judge the time

and cost required for its development. There are two methods to

determine estimation size of software. Based on our MV Project we will

use Source Line of Code (SLOC) only.

Function Point Analysis: are a measure of the size of an information

system based on the number and complexity of inputs, outputs, files,interfaces and queries. There are two steps involved in our MV Project.

First, computing the metrics. Second, by using equation in a manner

analogous to SLOC we can easily derived cost, schedule, productivity

and quality metrics.

14


15/52

Technical Details

Hardware:-

Desktop

Processor Intel Pentium 4 Processor, 2.4 Ghz, 3.0 Ghz I

Memory 333- and 400 Mhz DDR SDRAM

Video Integrated Intel Extreme Graphics 2

Drives DVD Drive, 1 TB SATA Hard Drive, 32 GB USB Flash

Drive

Connectors Serial, Network Adaptor, USB 2 (2 Front Pannel and 4

Back Pannel),

Power 250 W, Fix Voltage Power Supply 100 to 120 W

Weight 10.4 Kg

Backup

Battery

3B CR2032 Lithenium Coil

Tablets (Windows)

Processor Intel Atom Processor 2760

Slots MicroSD,

Wifi 802.11n

InbuiltStorag

e

64GB eMMC

Bluetooth Above 3

Weight 600 grams

Backup

Battery

Upto 9 hours

15


16/52

Other Optional Hardware:

Bar Code

Reader

optional

Printer Optional

Software:-

Development Software:

Database SQL Server

GUI Refactoring Class Browser

Programming MS Visual Studio,

Others Software:

OS Windows Vista or Higher

Letters MS Office Word

Presentation MS Office Power Point

Graphical

Stat

MS Office Visio

Time

Schedule

MS Project

Proof of Concept: is based on the result that the hardware and

software requirement fully met the system requirement for

16


17/52

development and for this purpose only. After ward this will again be

used for the implementation of software. A prototype will be tested.

Non-Functional Requirements

Configuration Management: is important because software is subject to

ongoing changes both during and after development

Change Management: Request for Change (RFC) Document if any

changes occur during the software project development should be

used.

Documentation: Manual for the user as well as guidelines for future

developer

Security: Authentication and PINS for any updates in the system. As

well as password protected login to authorize personnel only.

Price: This project is for the purpose of evaluating knowledge on how

to develop software. It will be an open source project.

Computer-Aided Software Engineering: a substantial amount of the

application development effort involves translating the information into

program logic and code for subsequent testing, modification and

implementation. It is divided into three categories. In this case we will

use UPPER Case

**UPPER CASE: describe and document application requirement,

include DFD, CASE, CLASS, Process and relationship between them.

17


18/52

USE CASE DIAGRAMS

Use cases are very good In providing functional views from an actors

perspective.

A description of sequence of actions, including variants that a system

performs that yield an observable result of value to an actor

-Boochet, 1999 UML Guide

Actors

Not all Actors in use case diagrams are user, can be system. In our

case of MV, the following are the actors.

Registered Owners

Registered Vehicle

Sales and Purchase Office

Local Distributor (supplier)

Inspector General Police

Karachi Port Trust

Federal Govt.

Municipality Office

Information Desk18


19/52

Actors Goal

It is the value that the actor expects from the system. In our case,

Registered Vehicle, which has a valid plate number to run in the city .

However, the Sales and Purchase Office, is the one who uses the

system most.

Registered Owner

o Application for Registration

o Pay MV taxeso Pay Tariff on Imported Vehicle

o Pay Municipality Taxes

o Pay WHT to Fed Govt.

o Receive Delivery Order Plate

o Receive Notification

Registered Vehicle

o Letter of Clearance

o AFR Number Plate

o Registered Number Plate

Sales and Purchase Office

o Maintain Registration Records

o Issue a License Plate

o Receives New Car List

o Send Notification

o Update Informationo Help Desk

Local Distributor ( Supplier)

o Sales Local Produce Cars

o Provide Delivery Order

19


20/52

o Pay Sales Tax.


o Routine Inquire about MV

Karachi Port Trust

o Charges Tariff for Imported Vehicle

Federal Govt.

o Receives WHT tax .

Municipality Office

o Parking charges

Information Desk

o Provide info to owners

o Provide information to Sales and Purchase

Office

Anti Car Lifting Cell

o Verification

Now, we have to draw our actor and their behavior pertaining to MV

System. Which will include extra Actor, due to time restraint we will

focus on our objectives/ scope of the project?

Use Case Diagram

20


21/52

21


22/52

USAGE SCENARIOS

It is not obvious from the diagram the Owner fills in a registration formand gives it to the Sales and Purchase Dept for registration of his

vehicle. Addition to the insertion of taxes, and any other vehicle

information from the Perspective of the Actor

Maintain Registration Record

Actor : Sales and Purchase OfficeLevel : User Goal

Description : Sales and Purchase Office register a Vehicle

Precondition: The application form contains the correct information

Main Flow : 1) This use case start with the Sales and Purchase

Office select Maintain Registration Record from

the main menu

2) The Sales and Purchase Office enter Name,

Address, CNIC, MV Chassis Number and other

details from Registration Form.

3) The System records the registration details.

4) The Office than Issue a Number Plate

Post The System recorded the Registered Vehicle details

Alternate

Flows :

From 3) , if the Registered Vehicle exist, the system

respond with Vehicle Already Registered

22


23/52

Issues a Number Plate

Actor : Sales and Purchase Office

Level : User Goal

Description : Sales and Purchase Office Issues a Number PlatePrecondition: Registered Vehicle exits


Office select Issue a Number Plate from the

main menu

2) Sales and Purchase Office gets the next

number from the database based on the category

selected.

3) Sales and Purchase Office enter owner CNIC

number and Plate Number etc.

4) The System records the Number plate.Post The System recorded the Number plate number

Alternate

Flows :

From 3), if this is a duplicate issue of plate number

the Sales and Purchase Office gets the old plate

details and if there are taxes or fees outstanding,

than these taxes and fees need to be reassigned to

the duplicate issued plate. The License history will be

transferred to the duplicate issued plate

Update Vehicle List


Level : User Goal

Description : Sales and Purchase Office Update Vehicle List

Precondition: Charges/Fees and Taxes exits


Office select Update Vehicle List from the main

menu

2) Sales and Purchase Office gets the next

number from the database.

3) Sales and Purchase Office enter Vehicle Name,

Categories either Private or Commercial, type etc

and

4) The System records the new Vehicle.

23


24/52

Post The System recorded the new vehicle details

Alternate

Flows :

From 3), if Vehicle name already exist the Sales and

Purchase Office gets the message The Vehicle

already in Database.

Charge/Fees and Taxes


Level : User Goal

Description : Sales and Purchase Office Insert Tax rates

Precondition: None


Office select Charge/Fees and Taxes from the

main menu2) Sales and Purchase Office will be asked to

insert CC ID.

3) Sales and Purchase Office enter CC ID, Charges

details, Taxes Details and Fees with Categories

Private and Comm. if any

4) The System records Charge/Fees and Taxes

Value

Post The System recorded the new vehicle details

AlternateFlows :

From 3), if CC ID already exist the Sales andPurchase Office gets the message CC ID Already

Exist, Do you want to Update.

Sales and Purchase Office will View the details of the

Same ID If Press Yes and If Press No he will taken

back to Main Menu.

Secondly, Registered MV will first go with inspection from the

representative of Sales and Purchase Office before in order to be

cleared from any defect or vulnerabilities. Registered MV will beinspected by the competent engineer based on the standards provided

by the Govt. Although this will be not a part of MV System. But, It is

necessary for the Registered MV. Once the certification of clearance

will be issued, The System will be shown with the status of Fitness,

Taxes and Other Charges paid. It will be inspected with regular time

24


25/52

interval when any transaction of Sales and Purchase will be made and

Also for monitoring of Tax Receipt Payment. The following information

is again from the Perspective of the Actor

Letter of Clearance

Actor : Registered MV

Level : System Goal

Description : Registered MV will get Letter of Clearance Status in

Precondition: After Issuance of Plate


Office select Letter of Clearance from the main

menu2) Sales and Purchase Office will be asked to

insert Plate ID.

3) Sales and Purchase Office will be shown the

status of Letter of Clearance, if any dues

remaining, fitness etc

4) The System shows all information about

Vehicle.

5) Sales and Purchase Office will use to deliver

the Plate to the OwnerPost

Condition :

The System Generate notification about Letter of

Clearance and send to Owner.

Alternate

Flows :

From 3), if Status of Clearance does shows dues

remaining and other fees and taxes. It will ask Sales

and Purchase Office to Print Copy or Send

Notification. Than the System will act accordingly.

AFR Number PlateActor : Registered MV

Level : System Goal

Description : Owner will get AFR Number Plate

Precondition: After Letter of Clearance

25


26/52


Office select AFR Number Plate from the main

menu

2) Sales and Purchase Office will be asked to

insert Plate ID.

3) Sales and Purchase Office will be shown the

date of Delivery of Actual Plate, and time.

4) Sales and Purchase Office will use to deliver

AFR the Plate to the Owner

Post

Condition :

The System print delivery order and AFR Number

Plate Details

Alternate

Flows :

From 3), if system not shown the date of delivery.

Vehicle is not have letter of clearance It will ask Sales

and Purchase Office to Print a Notification. Than the

System will act accordingly.

26


27/52

Registered Number Plate

Actor : Registered MV

Level : System Goal

Description : Owner will get Delivery Order for Number PlatePrecondition: After Letter of Clearance


Office select Registered Number Plate from the

main menu


insert Number Plate ID.

3) Sales and Purchase Office will shown the

details of registered number plates and delivery

date and any particular therein

4) Sales and Purchase Office will use this

information to update clients

Post

Condition :

The System will get result of query relating to

registered number plates

Alternate

Flows :

From 3), if system not shown any detail. Vehicle is

not been registered. Sales and Purchase Office will

check the AFR Number Plate to see if the owner has

received the delivery or else if cant see any thing

than also check Letter of Clearance.

Third, Owner of Registered MV will go to Sales and Purchase Office for

any inquiry relating to his vehicle. Owner will be asked to provide

Letter of Clearance. Owner is not integral part but it is connected to

Registered MV and also for the payment of any taxes, charge levied on

Registered MV. The following information is again from the Perspective

of theActor

Application For Registration

Actor : Registered Owner

27


28/52

Level : System Goal

Description : Owner will get Registration Number on System

Precondition: After Maintain Registration Record


Office select Application for Registration fromthe main menu


insert CNIC Number


details fetch from Maitain Registration Record

and ask for additional information regarding taxes

owner details, from where vehicle is purchased

etc, categories imported or local etc

4) Sales and Purchase Office will store information

PostCondition :

The System will get result of query relating toregistered owners

Alternate

Flows :

From 3), if system not shown any detail. Owner is

not registered. He will be registered in the system

through Maint Registration Record. Afterwards The

information will be available on this screen.

It may be obvious, that if owner is not the first owner of the

RegisteredMV. We need to provide provision in Maintain RegistrationRecord to add as a Current Owner which will be from Date Period. It

will be enhance user experience and helps finding out details of owners

of the Number Plate.

Fourth, Other Provisions in system such as Local or Imported Vehicle

will be based on the Application of Registration of MV. As we have set

boundary to deal in MV only we will be limited to it. Although we can

provide queries relating to taxes and other Fees, payments, charges

etc. and Additionally where the vehicle is imported but this will not

cover our functional requirement at this moment. There are other

departments in Transport Sector of Metropolitan Service System other

than MV can handle such queries

28


29/52

At, Last we have made Inspector General Police involvement to send

us queries which will be deal by Anti Car Lifting Cell and after their

verification Sale and Purchase Office will mark MV as Stolen/Illegal in

the system. The following information is again from the Perspective of

the Actor

29


30/52

Verification

Actor : Anti Car Lifting Cell

Level : User Goal

Description : Inquire about stolen vehiclesPrecondition: After Registered Number Plate

Main Flow : 1) This use case start with Anti Car Lifting Cell

select Verification from the main menu

2) Anti Car Lifting Cell will be asked to insert CNIC

Number, Car Chassis Number, Plate Number

3) Anti Car Lifting Cell will shown the details fetch

from Maintain Registration Record and

Application for Registration It will also be from

where vehicle is purchased etc, categories

imported or local etc

4) Anti Car Lifting Cell will view the information

Post

Condition :

The System will get result of query relating to

registered owners

Alternate

Flows :

From 3), if system not shown any detail. Either

Vehicle is not registered with the region, or fake

number plate is in use

On behalf to stop selling and purchasing of Stolen/Illegal car we have

to make certain adjustment in the system. On the Request of Anti Car

Lifting Cell, the Sales and Purchase Office will update the status of

Registered MV. Through Update Information. The additional

information is again we will see from the Perspective of the Actor

Update Information

Actor : Sales and Purchase Dept

Level : User Goal

Description : To Mark Stolen/Illegal Cars/ Status

Precondition: After Registered Number Plate

Main Flow : 5) This use case start with Sales and Purchase

Office select Update Information from the main

30


31/52

menu


insert CNIC Number, Car Chassis Number, Plate

Number


details fetch from Maintain Registration Record

and Application for Registration It will also be from

where vehicle is purchased etc, categories

imported or local etc, can be edit. They will mark

Stolen/Illegal Check.

8) This will update the information on Registered

MV and send notification to Registered Owner

through email or by post

Post

Condition :

The System will get the status updated

Alternate

Flows :

From 3), if system not shown any detail. Either

Vehicle is not registered with the region, or fake

number plate is in use/ or information provided is

incorrect.

Lastly, Introducing Information desk. It can provide information to

owners about their registration charges, taxes, tariff and taxes onimported cars. And It will be in our system.

31


32/52

CHAPTER 3:

Designing the Project

32


33/52

OVERVIEW:

Project Schedule:

33


34/52

Quality Assurance

There is ongoing plan to check the quality of system during the overall

project designing phase. So, that the proposed system should satisfy

all requirements of a capability maturity model integration.

It is very important to analyze and assess the risk during the

development of the project. The above technique to analyze risk must

be followed in each phase of design documentation and the cycle of

risk analysis will be continued until and unless the customers or users

accept the outcome.

34


35/52

DATA FLOW DIAGRAM:

The Context Diagram

It is the highest level of graphical representation of a system. It

simplifies the entire system as one single process and identifies

sources and sink

35


36/52

Level 0 Diagram

Level 1 Diagram

36


37/52

37


38/52

ENTITY RELATIONSHIP

DIAGRAM:

38


39/52

SEQUENCE DIAGRAM:

39


40/52

40


41/52

41


42/52

42


43/52

DATABASE DESIGN:

43


44/52

TEST CASES:Test Case No. 1:

Testing the Form Load SuccessfullyPreconditions Main Menu Should be Open

Actions Click the all icons in menu one by one: check

Expected Successfully New form loaded with the

Tested By: Nooruddin

Result Pass

Test Case No. 2:Testing the Data Input Check

Preconditions Click to open any one form from main

Actions Open update vehicle list form

Expected Successfully insertion of record


Result Pass

Test Case No. 3:Testing the Validation of data input

Preconditions Open any one from randomly

Actions Insert data on Charges/Fee and Taxes Form

Expected Form give error on incorrect data types.


Result Pass

Test Case No. 4:Testing for the bug

Preconditions Form Maintain Registration Record Open

Actions Click simultaneously all icons to open

Expected All open will display in side bar.

44


45/52


Result No Result (on user acceptance)

Test Case No.5:Testing the Validation of data input 4

Preconditions Form Maintain Registration Record Open

Actions Insert Address field : AAAA as long as it takes

Expected

Results

It should take uptill the specify value.

After which a beep sound in the system


Result Pass

Test Case No.6:Testing the Security Menu

Preconditions Icon on desktop

Actions After password main menu should open

Expected

Results

Segregation of duties; icons not pertaining

to user should be deactivated.


Result Pass

45


46/52

CHAPTER 4:

Project Analysis

46


47/52

SOFTWARE/PROJECT BENEFITS:

Overcoming Limitation

New system will overcome the limitation and helps in updating vehicle

population, transfer of ownership , receiving fees and taxes through

different channels, tracking crime through coordination with Anti Car

Lifting Cell, helps general public in realizing the worthiness of effective

and efficient working of Sales and Purchase Department without any

long ques. The system will give benefits to the following stakeholders.


Helps police in investigating crimes through ownership details, road

taxes, vehicle fitness certification, permit route for vehicle

Ministry of Petroleum

Helps ministry through data relating to fuel consumptions, classes and

categories of vehicle, planning and making policy decision in setting

fuel price and fullfiling the demand

47


48/52

Central Board of Revenue

Helps CBR through owner information and broadening their long term

objectives of the tax base structure

City Development Authority

For ensuring the better road transport system, new infrastructures,

routes, management of bus stops

Environmental Protection Agencies

For having access to vehicle make, model, engine type, statistics on

average fuel consumption of each vehicle, and imposing penalty onvehicle not suitable for

Critical Success Factors

Productivity

By sampling the rupees spend on per user training and number of data

enter/per month. We can easily compute the productivity of our new

proposed system in financial terms through Functional Point Analysis

Measurement

Parameter/entry

Count Weighting Factor(bytes)

Simple

x6

Average

x20

Comple

x50

Result

s

Number of owner

details

5 1x6=6 2x20=4

0

2x50=1

00

146

Number of vehicle

details

31 23x6=1

38

9x20=1

80

318

Number of purchases 12 7x6=42 2x20=4

0

3x50=1

50

232

48


49/52

Number of additional

details

28 13x6=7

8

10x20=

200

5x50=2

50

528

1.19k

b

To calculate productivity = FP/owner-month; in our case of sampling

we assume around 80,000/ month owners have successful registration

of vehicle, including sales and purchase, transfer, queries, updating

records etc.

It can be easily sample as FP/owner-year = 960,000/1.19kb = 806,722

(787Mb/year) around 0.787(GB) of data size per year. With the project

span life of around 20 year we can find out that requires minimum of

15 GB of efficient performance until the data size increase depending

on population.

We can easily compute that data storage cost is minimum but its

maintenance, specialize skill personnel salaries, licenses software,

antivirus protection, security, another factor will be increase the cost

portion depend on the budget allocated to the sector.

Cost

The cost associated with system must be outsourced to reduce

expenses other wise with the following estimation the project in not

feasible

Cost Factors Period Avg in Rs Total / year

Rs

Salaries Individual Monthly Rs.

40,000

480,000

Training

Cost/Workshop

(Total Quality

Management, New

Technologies)

Quarterly Rs.

75,000

300,000

Maintenance Cost Monthly Rs.225,00 2,700,000

49


50/52

(Fuel Genset, Chillers,

Server Preventive

Maintenance, Cleaners,

Technical Persons)

0

License Software(new releases, bugs,

patches)

Yearly 500,000 500,000

3,980,000

Now to calculate the cost based on productivity we can find that

3,980,000/960,000 = Rs 4.14 and for our project Cost = Rs/FP =

4.14/1.19 = 3.47. The difference is the benefit drive from the system.

Which is 4.14-3.47 = 0.67 or in broad sense Rs 643,200/year? Very low

Efficient Customer Service

The system helps in decreasing turnaround time for customers

questions and answer. helps in effective communication through new

technologies, as well as cellular service. It also helps in internal

communication between different sectors of the Metropolitan Service

System.

50


51/52

CONCLUSION:

Help Sindh Government

In making reforms on vehicle registration

Helps in wider framework and decision making

Help consolidate with other provinces as they are already having

new vehicle registration system.

Helps laws and enforcement agencies in dealing with lost and

stolen car promptly

Through latest technologies such BYOD(bring your own devices)

general public can keep in touch with their records

With embed chips, easily track down vehicle. Help in making

Karachi a better traffic rules and regulation following city

Helps in gaining budget for the sector on efficient working.

51


52/52

RECOMMENDATION:

Cloud Computing Virtualization

With the cost and effort, it is feasible to go on cloud computing.

Servers are allocated centralized in vary areas. Software as a Service,

will definitely achieve end objectives and efficient MV system. The

following feature of cloud such as

Service Delivery

Cloud Governance

Monitoring and Review of Third party Services

Managing Changes to Third party Services.

The project is a try approach, it can further be analyzed. I have done

my best effort in drafting my idea on MV system.

Metropolitan Service System (MV)

Documents

Transcript of Metropolitan Service System (MV)