Beruflich Dokumente
Kultur Dokumente
FINAL PROJECT
Virtual University
Submitted By:
MC070400829
Nooruddin Charania
2
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
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.
4
Table of Contents
CHAPTER 1: Background and Introduction................................................................................................11
BACKGROUND........................................................................................................................................12
About Organization............................................................................................................................13
Introduction.......................................................................................................................................15
Objectives..........................................................................................................................................15
REQUIREMENTS.....................................................................................................................................17
Functional Requirements...................................................................................................................17
Non-Functional Requirements...........................................................................................................20
Actors.................................................................................................................................................21
Actor’s Goal.......................................................................................................................................22
USAGE SCENARIOS.................................................................................................................................25
5
Update Vehicle List............................................................................................................................26
Letter of Clearance.............................................................................................................................27
Verification........................................................................................................................................31
Update Information...........................................................................................................................31
OVERVIEW:............................................................................................................................................34
Project Schedule:...............................................................................................................................34
Quality Assurance..............................................................................................................................35
Level 0 Diagram.................................................................................................................................37
Level 1 Diagram.................................................................................................................................38
SEQUENCE DIAGRAM:...........................................................................................................................40
DATABASE DESIGN.................................................................................................................................44
6
CHAPTER 4: Project Analysis......................................................................................................................47
SOFTWARE/PROJECT BENEFITS:.............................................................................................................48
Overcoming Limitation......................................................................................................................48
CONCLUSION:........................................................................................................................................52
RECOMMENDATION:.............................................................................................................................53
7
CHAPTER 1:
Background and Introduction
8
BACKGROUND
9
INTRODUCTION
TO ORGANIZATION AND PROJECT
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).
10
CHAPTER 2:
Software Requirement Specification
11
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
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 sector will be used in this project.
This has to be done to avoid any ambiguity.
12
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
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 relative physical 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
Technical Details
Hardware:-
Desktop
Connectors Serial, Network Adaptor, USB 2 (2 Front Pannel and 4 Back Pannel),
Weight 10.4 Kg
Tablets (Windows)
Slots MicroSD,
Wifi 802.11n
Bluetooth Above 3
Printer Optional
Software:-
Development Software:
Others Software:
Proof of Concept: is based on the result that the hardware and software requirement
fully met the system requirement for development and for this purpose only. After ward
this will again be used for the implementation of software. A prototype will be tested.
16
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.
**UPPER CASE: describe and document application requirement, include DFD, CASE,
CLASS, Process and relationship between them.
17
USE CASE DIAGRAMS
Use cases are very good In providing functional views from an actor’s perspective.
A description of sequence of actions, including variants that a system performs that yield
an observable result of value to an actor
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 Desk
18
Actor’s 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 taxes
o 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
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
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?
20
21
USAGE SCENARIOS
It is not obvious from the diagram the Owner fills in a registration form and 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
22
Issues a Number Plate
Actor : Sales and Purchase Office
Level : User Goal
Description : Sales and Purchase Office Issues a Number Plate
Precondition: Registered Vehicle exits
Main Flow : 1) This use case start with the Sales and Purchase 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 Condition : The System recorded the Number plate number details
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
23
Charge/Fees and Taxes
Actor : Sales and Purchase Office
Level : User Goal
Description : Sales and Purchase Office Insert Tax rates
Precondition: None
Main Flow : 1) This use case start with the Sales and Purchase Office select
“Charge/Fees and Taxes” from the main menu
2) 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 Condition : The System recorded the new vehicle details
Alternate Flows : From 3), if CC ID already exist the Sales and Purchase 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 be inspected 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 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 system
Precondition: After Issuance of Plate
24
Main Flow : 1) This use case start with the Sales and Purchase Office select
“Letter of Clearance” 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 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
Owner
Post 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.
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.
25
Registered Number Plate
Actor : Registered MV
Level : System Goal
Description : Owner will get Delivery Order for Number Plate
Precondition: After Letter of Clearance
Main Flow : 1) This use case start with the Sales and Purchase Office select
“Registered Number Plate” from the main menu
2) Sales and Purchase Office will be asked to 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 can’t
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 the Actor
26
Main Flow : 1) This use case start with the Sales and Purchase Office select
“Application for Registration” from the main menu
2) Sales and Purchase Office will be asked to insert CNIC Number
3) Sales and Purchase Office will shown the 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
Post Condition : The System will get result of query relating to registered 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 Registration Record 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
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
27
Verification
Actor : Anti Car Lifting Cell
Level : User Goal
Description : Inquire about stolen vehicles
Precondition: 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 menu
6) Sales and Purchase Office will be asked to insert CNIC Number,
Car Chassis Number, Plate Number
7) Sales and Purchase Office will shown the details fetch from
28
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 on imported cars. And It will be in our system.
29
CHAPTER 3:
Designing the Project
30
OVERVIEW:
Project Schedule:
31
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.
32
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
33
Level 0 Diagram
Level 1 Diagram
34
35
ENTITY RELATIONSHIP DIAGRAM:
36
SEQUENCE DIAGRAM:
37
38
39
40
DATABASE DESIGN:
41
TEST CASES:
Test Case No. 1:
Testing the Form Load Successfully
Preconditions Main Menu Should be Open
Actions Click the all icons in menu one by one: check status
Expected Results Successfully New form loaded with the Entry Screen
Tested By: Nooruddin
Result Pass
42
Tested By: Nooruddin
Result No Result (on user acceptance)
43
CHAPTER 4:
Project Analysis
44
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
45
Central Board of Revenue
Helps CBR through owner information and broadening their long term objectives of the
tax base structure
For ensuring the better road transport system, new infrastructures, routes, management
of bus stops
For having access to vehicle make, model, engine type, statistics on average fuel
consumption of each vehicle, and imposing penalty on vehicle not suitable for
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
1.19kb
46
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.
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
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
47
drive from the system. Which is 4.14-3.47 = 0.67 or in broad sense Rs 643,200/year?
Very low
The system helps in decreasing turnaround time for customer’s 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.
48
CONCLUSION:
Help Sindh Government
In making reforms on vehicle registration
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
49
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
The project is a try approach, it can further be analyzed. I have done my best effort in
drafting my idea on MV system.
50