Islamabad Traffic Police

(ITP system)

Developed By

Mohsin Raza
(12-ARID-1987)

Tahir Abbas
(12-ARID-2061)

Supervised By
Mr. Hameed Ulla Khan Niazi
A PROJECT SUBMITTED IN THE PARTIAL
FULFILLMENT OF THE REQUIREMENTS OF THE
DEGREE OF
BACHELORS OF SCIENCE IN COMPUTER SCIENCE (BS (CS))

University Institute of Information Technology

PMAS ARID AGRICULTURE UNIVERSITY

RAWALPINDI
2016

DEDICATED
To

Our Mother
A strong and gentle soul who taught me to trust in ALLAH,
Believe in hard work and that so much can be
done by a little.

Our Father
For earning an honest living for us and supporting
and encouraging us to believe in ourselves.

PROJECT IN BRIEF

Project Title:

Islamabad Traffic Police

Organization:

University Institute of Information Technology

Undertaken By:

Mohsin raza (12-ARID-1987)

Tahir Abbas (12-ARID-2061)

Supervised by:

Mr. Hameed Ulla Khan

Date Started:

22nd Feb, 2016

Date Completed:

21st July, 2016

Technology Used:

HTML, CSS, Android

Operating System:

Windows 8

System Used:

Dell Ci7, 700 GB HDD, 4 GB RAM

ACKNOWLEDGMENT

ALLAH THE ALMIGHTY, who gave us the strength to work to complete this project
on time and with the best possible quality and our family and friends who supported
us in every step of life and mostly the past four years of university life.

We would like to thank and sincerely acknowledge the help of our supervisor Mr.
Hameed Ulla Khan whose complete guidance, support and encouragement gave us a
real motivation in doing this project.

We would like to thank all the volunteers who helped us out while testing of this
application.

Lastly, we would like to thank all the faculty members of UIIT department for their
help, time, and support that was gladly given to us on the time of need.

Mohsin Raza
(12-ARID-1987)

Tahir Abbas
(12-ARID-2061)

DECLARATION

We hereby declare that this project, neither whole nor as a part has been copied out
from any source. It is further declared that we have developed this project and
accompanied report entirely on the basis of our personal efforts. If any part of this
project is proved to be copied out from any source or found to be reproduction of
some other. We will stand by the consequences. No Portion of the work presented has
been submitted of any application for any other degree or qualification of this or any
other university or institute of learning.

Mohsin Raza
(12-ARID-1987) / BSCS

Tahir Abbas
(12-ARID-2061) / BSCS

CERTIFICATION

It is certified that the contents and form of the project entitled Islamabad Traffic
Police submitted by Tahir Abbas (12-arid-2061) and Mohsin Raza (12-arid-1987) has
been found satisfactory for the requirements of

PMAS Arid Agriculture University, Rawalpindi

For the award of the degree of

BACHELOURS OF COMPUTER SCIENCES (BSCS)

Supervisor:
Mr. Hameed Ulla Khan

Examiner 1:

Examiner 2:

Director: Dr. Mobushir Riaz Khan

ABSTRACT
Traffic Police is one of the important departments of country. They play very
important role in maintaining the flow of traffic on the roads. As they play an
important role so the facilities provided to them should also be according to modern
technology. After the completion of this project this department will have a proper
website and there will also be and android application.
Islamabad Traffic Police is an android app as well as a website. Visitors can visit the
website and they can get all kind of information required related to Islamabad Traffic
Police. While the android app is for traffic wardens. Wardens will have their own
usernames and passwords. They can chat with each other and also they can leave
message for others. They can generate an alert for other wardens related to traffic or
any VIP movement. Website will have one admin and admin will have its own
username and password. Admin can add wardens and also can update or delete. He
has the complete record of wardens and officers. He can change their duty plans.

TABLE OF CONTENTS
Project in Brief............................................................................................................
Acknowledgment.......................................................................................................
Certification..............................................................................................................
Table Of Contents..............................................................................................IV-VII
Chapter 1:Introduction............................................................................................
1.1.

Brief.................................................................................................................

1.2.

Scope of the project

1
1.2.1 Relevance To Course Modules........................................................................
1.3.

Project Background.........................................................................................

1.4.

Literature Review...........................................Error! Bookmark not defined.

1.5.

Analysis From Literature Review....................................................................

1.6.

Lifecycle For This Project...............................................................................

1.6.1. Rationale Behind Selected Methodology........................................................

Chapter 2: Problem Definition................................................................................
2.1.

Problem Statement...........................................................................................

2.2.

Proposed

Solution.

.5

2.3.

Deliverables And Development Requirements................................................

2.3.2

Development Requirements......................................................................................

Chapter 3: Requirement Analysis...........................................................................

3.1.

Functional Requirements..............................................................................

3.2.

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

3.2.1 Usability.........................................................................................................

3.2.2 Reliability......................................................................................................
3.2.3 Integrity..........................................................................................................
3.2.4 Performance...................................................................................................
3.3.

Design Constraints...........................................................................................

3.4.

Software Requirements..................................................................................

3.5.

Hardware Requirements.................................................................................

3.6.

Use Cases (Fully Dressed).............................................................................

3.6.1

User

Search

for

job

or

careed

in

ITP..12
3.6.2 User

search

for

information

about

driving

license.12
3.6.3 User search for rules in ITP..13
3.6.4 User search about fine for violating rule..13
3.6.5 Warden login..................................................................................................
3.6.6 Admin login...................................................................................................
3.6.7 Admin use system for managing warden details...........................................
3.6.8 Managing Challan..........................................................................................
3.6.9 Manage

Laws

17
3.6.10 Manage Reports...17,18
3.6.11 Warden stop the rule violator and puts penalty on him/her......................18,19
Chapter 4: Design And Architecture.....................................................................
4.1.

System Design...............................................................................................

4.1.1 Use Case Diagram....................................................................................20,21

4.1.2 Class Diagram................................................................................................
4.1.3 Sequence Diagrams..................................................................................23-30

4.1.4 Activity Diagrams.31-42

Chapter

5:

Implementaion..43
5.1

Java Development Kit....................................................................................

5.1.1 Developer Productivity..................................................................................

5.1.2 Improved Performance..................................................................................
5.1.3 System Requirements for Eclips IDE............................................................
5.2.

User Interface.................................................................................................

Chapter 6: Testing And Evaluation.......................................................................

6.1.

Verification...45

6.1.1 Functional Testing...45-47

6.2

Static Testing..................................................................................................

6.3

Validation.......................................................................................................

6.4

Usability Testing............................................................................................

6.5

Module / Unite Testing..................................................................................

6.6

Integration Testing.........................................................................................

6.7.

System Testing...............................................................................................

Chapter 7: Conclusion And Future Work............................................................

7.1.

Conclusion.....................................................................................................

7.2.

Future Work...................................................................................................

Chapter 1

INTRODUCTION
My project titled, as Islamabad Traffic Police System is basically an android based project. As Islamabad
is capital of Pakistan so here the facilities should also according to the new technology. So we have decided
to make an app so that the Islamabad traffic police can be facilitated. This app will contain the registered
user i.e. traffic wardens. Duty officer can assign the duty location to the wardens and wardens can check
their location by signing in. There will be online challan system and victim can pay on the spot if he/she
wants to. There will be confirmation SMS to the victims mobile. If traffic is struck in some place, then the
warden on that place can leave a message for other wardens and can ask them to lower the flow of traffic so
that he can control the situation. If a warden wants a leave, then he/she can submit an application to duty
officer.
The system is developed to provide a solution to manual work of Islamabad traffic police. In this
project we will manage the traffic wardens / officers data and duty position and Challan. We will also have
generated duty reports, commission and history of Challan.

1.1

BRIEF

This project includes website and android app. Our system will help the mobile users to install the mobile
app and search on through the app rather than searching through web browser.

1.2

SCOPE OF THE PROJECT

The scope of our project is to build an Android application and website for Islamabad Traffic Police. There
is no android app for this department up till now. So this project is to facilitate those persons who want any
information related to Islamabad Traffic Police. Mobile users can use android app and while who want to
visit the website through browser they can also visit the website and fetch the required information. In the
admin panel there will be one admin and there will be information about wardens i.e. their name, there
email, their salary, their address, infect there will be every required information related to wardens and other
duty officers. There will be information of total regions and also the total number of wardens in every
region. Admin will also have the record of wardens who are absent and also the record of those who are on
duty.
RELEVANCE TO COURSE MODULES
Course helped me in developing this project is mentioned below:

1.3

Software Engineering: The course helped in designing and documentation of the project.
Object Oriented Programming: Helped how to work in object oriented approach and classes.
Database Concepts: Helped in using internal database concept.
Web: Helped me in development of website.

PROJECT BACKGROUND

Our motivation comes from a research that there is no such work done on this important department related
to IT. There are many people who dont know the traffic rules and also who dont have the knowledge about
how to get driving license. They have to travel to traffic police offices in order to fetch required information.
In order to solve this problem, we have decided to develop an android app for mobile users and also a
website. Wardens will register first and will get their unique username and password. They will enjoy the
extra features of android app. They can chat with one another and also they can leave a message for all the
wardens related to traffic blockage or related to VIP movement. Admin panel will have a admin and he will
have access for all the things related to website and app. He will be responsible for uploading the messages
of authority and he will also be responsible for keeping the data up to date. He will have access to the data of
all the wardens i.e. their name, their address, their email, their salary etc. admin will receive the news related
to Islamabad Traffic Police and he will publish those and also he will receive the queries from the users and
also admin will help them.
1.4 LITERATURE REVIEW
1.4.1 Study about Department of Islamabad Traffic Police
As Traffic Police is one of the important department of our country because they are responsible for
maintaining the traffic on the roads. So we decided to start a project related to this department. We started
research about this department and came to know that there is no android app related to this department and
also there is no proper website where the users can get all the related information. Mostly the people have to
travel towards the Traffic Police offices in order to get the information. If people want information about the
driving license or how to apply for driving license, then they have to go to traffic police offices for the
information but after the completion of this project everyone will able to get almost every kind of
information in one place. There will be updates about the jobs in ITP and also all the current news related to
ITP. If there will be any VIP movement or any road which is blocked for any reason, there will be update
news on the app and website as well.

1.4 ANALYSIS FROM LITERATURE REVIEW

As it is clear from literature review that there is need of improvement in the Islamabad traffic Police
especially there is need of improvement in their website and also there should be and android app in order to
facilitate the people. As we have discussed in the literature review that we will develop an android app and
2

also a website which will have all the information related to Islamabad Traffic Police. They will have the
updated news about the traffic condition of roads or condition of traffic on the roads. There will be alert on
the website about the road where traffic is blocked or where the road is blocked for VIP movement. This will
be a great advantage for the people.

1.6

LIFECYCLE FOR THIS PROJECT

Waterfall method is selected by us for the development of this project and in this framework of software
development, development proceeds in a sequence through a series of phases. These phases are system
requirements analysis, product release, and maintenance. So, the progress can be conclusively identified
through the use of milestones.

1.7.1

Rationale Behind Selected Methodology

Waterfall method is selected by us for the development of our system as it has many advantages for
developers. The progress in this methodology can be identified through the use of milestones.
In this method, there is emphasis on requirements and design before implementation which reduces the time
wastage and schedule slippage in development process as we thoroughly analyze the requirements feasibility
before implementing them. It also improves the quality of the developed system.
Finally, as we analyzed the requirements and end up with formal specification before implementation so it is
easy to work in team as requirements can easily be divided after analysis. In this method, there is emphasis
on requirements and design before implementation which reduces the time wastage and schedule slippage in
development process as we thoroughly analyze the requirements feasibility before implementing them. It
also improves the quality of the developed system.

Chapter 2

PROBLEM DEFINITION
In this chapter, we will provide problem statement, deliverables of our system and current systems present in
market for fall detection.

2.1.

PROBLEM STATEMENT

We want to develop a better website and also an android app which will facilitate the people of Islamabad
and also the people who are outsiders and they are travelling towards Islamabad. They can get alerts about
the traffic conditions of Islamabad. If any road is blocked for any reason, then the duty warden will notify
the admin about the condition and admin will generate an alert on the website and also on the android app.
Also another problem we want to solve that there should be one place where each and every information
should be available about Islamabad Traffic Police.

There should a website where people can get the information about the jobs in Islamabad Traffic Police and
also there should be a proper information about how to get driving license for those who dont know how to
get license.
PROPOSED SOLUTION
We will develop an android app and also a website for Islamabad traffic Police. Traffic wardens and officers
will have their unique username and password. Through this they can leave a message for the admin. And
also public can also have the updated news about the jobs in Islamabad Traffic Police.
2.3

DELIVERABLES AND DEVELOPMENT REQUIREMENTS

2.3.1

Deliverables

Project Report
A complete project report which includes Software Requirement Specification, Software Design
Specification, Test Cases, Mockups, Experiments Performed and other major tasks performed.
CD Package
A CD package which include, APK file, documentation, presentation and poster.

2.3.2 Development Requirements

Following requirements are necessary for running this system

Operating System:
Android 2.3.3 or higher versions
Device:
Android version 2.3.3 or higher
4

Minimum Space To Execute:

30.0 MB(approximate)
Network:
Wi-Fi Internet or cellular Network

Chapter 3

REQUIREMENT ANALYSIS
We develop an android application and also a website that will contain every information about Islamabad
traffic Police that will be required by public. There are two parts of our project. One will be the website and
other is android application. Website is for the users who will use web browsers in order to access our
website and android app is for the wardens.
Traffic wardens will have their unique username and passwords. Through this they can login and will have
access to some extra functions. If someone violates the rule, then the wardens can issue them challan by
using the android app. Violator can pay at the spot. And if he doesnt want to pay on the spot then he will be
issued a printed slip, later on he will have to pay his fine in the bank. Through this process the data which is
entered in android app by the warden will automatically be stored.

There are two subsets or types of requirements of our system:

Core requirements: To meet the acceptance criteria our system fulfills all the functional

requirements.
Non-core requirements: We implemented these requirements as well at the end of our
implementation phase like send SMS alert also on rule violators number and also store his data
automatically.

FUNCTIONAL REQUIREMENTS
Functional requirements in our system are as follows:
FUNC-REQ1:
Description:
Manage duty officers/wardens data.
Stimulus/ Response Sequence:
Input: Admin will login and select the manage duty officers/wardens data.
Output: System will display the complete data of all the duty officers/wardens and there will be option of
add, update and delete data.
FUNC-REQ2:

Description:
Duty officer/warden login/logout.
Stimulus/ Response Sequence:
Input: Duty officer/warden will enter their unique username and password.
Output: Login successful and main window will appear.
FUNC-REQ3:
Description: Manage duty points/position.
Stimulus/ Response Sequence:
Input: Admin will login and he will select the option of manage duty positions/point. He will assign the
duty position or points to the wardens on daily basis.
Output: System will update the duty points or positions.

FUNC-REQ4:
Description:
Manage Challans. Warden will enter the complete information of the person who is caught while violating
the rules. His/her complete data will be entered by the warden.
Stimulus/ Response Sequence:
Input: Warden or duty officer will enter the complete information of the rule violator.
Output: A fine slip will be printed and issued to the violator.
FUNC-REQ5:
Description:
Manage Commission. When the warden will issue a challan to rule violator then his data will also be stored
with the details of rule violator. And on the end of month warden will get a certain amount of money with
respect to number of challans he/she has issued.
Stimulus/ Response Sequence:
Input: Traffic wardens will issue challans to rule violators and their detail will be stored.
Output: on the end of month system will generate total amount with respect to total challans.

FUNC-REQ6:
Description:
7

Manage Fine details. The complete details of fine paid by the violator will be generated on the daily basis.
Stimulus/ Response Sequence:
Input: complete details of fine will be stored.
Output: report will be generated on the daily basis.

3.2

NON-FUNCTIONAL REQUIREMENTS

There are a number of attributes of system that can serve as requirements. It is important that required
attributes must be specified so that their achievements lead to better performance of the system. These
required attributes are also known as quality attributes as they increase the quality of a product.
In our system, we implemented following quality attributes or non-functional requirements:

3.2.1

Usability

USAB-REQ 1: The system's interface is user-friendly and is easy to get familiar with.
USAB-REQ 2: The system provides an easy-to-use graphical interface as the other existing systems so that
the users do not have to learn a new style of interaction.
USAB-REQ 3: The interface of the system is intuitive and easily understandable so that the users are able to
understand the menu and options provided by our system i.e. android based Islamabad traffic Police system.
And the interface of our system is based on android user interface guidelines.
USAB-REQ 4: The system does not require any special training and normal users who knows android
operating system are able to use our system.

3.2.2

Reliability

REL-REQ 1: The system is available 24/7. The system never crashes or hang, other than as a result of an
operating error. The system is reliable and works accordingly having less percentage of error, if any error is
detected than system automatically clear errors and restart by itself.
REL-REQ 2: The sys output will be more reliable and efficient.
REL-REQ 3: The system is able to recover from hardware failures, power failures, and other natural
disaster/failure and rollbacks its state to most recent valid state.

3.2.3

Integrity

INTG-REQ 1: Only system developer has a right to make any changes to the system.
8

3.2.4

Performance

PERF-REQ 1: The system responds in real time.

3.3 DESIGN CONSTRAINTS

Each function is tested on android phone.

3.4 SOFTWARE REQUIREMENTS

For developing the application, the following are the software requirements:
Operating System: Windows
Language: Java
Database: SQLite
Tools: Eclipse IDE, Android Plug-in for Eclipse, Android SDK
Technologies Used: Java, SQLite, XML,
For running application following are the software requirements:
Operating System: Android 2.3.3 or higher versions
Network: Wi-Fi Internet or cellular Network

3.5 HARDWARE REQUIREMENTS

For developing application following are the hardware requirements:
Processor: P IV or higher
RAM: 256 MB
Space On Disk: minimum 512 MB
For running application following are hardware requirements:
Device: Android version 2.3.3 or higher
Minimum Space To Execute: 30.0 MB

3.6 USE CASES (FULLY DRESSED)

3.6.1

User search for Job or career in ITP

Actors: User
Purpose: To get the information about Job or career in ITP.
Overview: User selects Information and then in information menu he/she selects the
option of Job or career.
Type: Primary & Secondary.
Typical Course Of Events:
Actor Action
1. The use case begins when the user

System Response
2. System initialize.

launch application.
3. User selects Information.

4. System displays the Information

window.

5. User selects Jobs and Career

option in Information window.

3.6.2

6. System displays the Jobs and

Career page.

User search for information about driving license

Actors: User
Purpose: To get the information about Driving License in ITP.

Overview: User selects Information and then in information menu he/she selects the
option of Driving license.
Type: Primary & Secondary.
Typical Course Of Events:

10

Actor Action

System Response

1. The use case begins when the user

2. System initialize.

launch application.
3. User selects Information.

4. System displays the Information

window

5. User selects Driving license

option in Information window.

3.6.3

6. System displays the Driving

license page

User search for rules in ITP

Actors: User
Purpose: To get the information about rules in ITP.

Overview: User selects rules in the main window.

Type: Primary & Secondary.
Typical Course Of Events:
Actor Action
1. The use case begins when the user

System Response
2. System initialize.

launch application.
3. User selects rules.

4. System displays the Rules window

5. User selects Driving license

option in Information window.

6. System displays the Driving

license page

3.6.4

User search for fine for violation the rule

Actors: user
Purpose: user visit the website in order to search the fine for violating the rules.
Overview: user selects fine for violating rules in rules and fine for violation.
Type: Primary & Secondary.
Typical Course Of Events:
Actor Action
1. The use case begins when the user

System Response
2. System initialize.
11

launch application.
3. User selects Rules.

4. System open the rule window.

5. User selects the fine for violation.

6. System open fine for violation page.

3.6.5

Warden login.

Actors: warden
Purpose: warden open the system to login.
Overview: warden enters his username and password for login and to use required
features.
Type: Primary & Secondary.
Typical Course Of Events:
Actor Action

System Response

1. The use case begins when the user

2. System initialize.

launch application.
3. Warden opens login panel.
5. Warden

enters

username

4. Login panel is opened.

and

6. Login

password.

3.6.6

successful

and

main

window is displayed.

Admin login

Actors: Admin
Purpose: Admin open the system to login..
Overview: warden enters his username and password for login and to use required
features
Type: Primary & Secondary.
Typical Course Of Events:
Actor Action
1. The use case begins when the user

System Response
2. System initialize.

launch application.
3. User open login panel.

4.

Login panel is opened.

12

5. Admin

enters

username

and

6. Login successful.

password.

3.6.7

Admin uses system for managing wardens details.

Actors: Admin.
Purpose: Admin uses the system for managing the details i.e. add details, update or
delete.
Overview: admin will login for performing any function on wardens details.
Type: Primary & Secondary.
Typical Course Of Events:
Actor Action

System Response

1. The use case begins when the user

2. System initialize.

launch application.
3. User selects Login panel.
5. Admin

enters

username

4. Login panel opened.

and

6. Login successful.

password.
7. Admin opens managing warden

8. Wardens detail window is opened.

panel.

3.6.8

Managing Challan

Actors: Admin
Purpose: Admin uses system to perform function on managing challan field.
Overview: Admin will open the managing challan portion in order to see the history or
total challans.
Type: Primary & Secondary.
Typical Course Of Events:
Actor Action
1. The use case begins when the user

,System Response
2. System initialize.

launch application.
3. Admin selects Login.

4. System displays the Login panel.

13

5. Admin

enters

username

and

6. System displays the main page.

password.
7. Admin opens Manage challan
window.
9. Admin performs required function.

3.6.9

8. System opens the managing

challan window.

10. Action successful.

Manage Laws

Actors: Admin
Purpose: Admin uses system for addition, updating or deletion of any law.
Overview: Admin will use the system in order to change in the laws. This change can be
in the shape of adding new law or updating old one or may be deletion of any law.
Type: Primary & Secondary.
Typical Course Of Events:
Actor Action

System Response

1. The use case begins when the

2. System initialize.

Admin launch application.

3. User selects Login panel.
5. User

enters

4. System Open login window.

username

and

password.
7. User open manage laws option.
9. User

performs

the

required

function. Which can be addition of

6. Login successful.

8. Manage laws window is opened.

10. Action performed successful.

new law, updating or may be

deleting the old one.

14

3.6.10

Managing Reports.

Actors: Admin
Purpose: Admin uses system to generate reports.
Overview: Admin will receive the messages for other wardens or officers and he will
publish it according to their requirements.
Type: Primary & Secondary.
Typical Course Of Events:
Actor Action

System Response

1. The use case begins when the user

2. System initialize.

launch application.
3. User selects Login panel.
5. User

enters

username

4. Login panel opened.

and

6. Login successful.

password.
7. User opens reports window.

8. System

opens

the

window

successfully.
9. Admin will read all the messages

10. Action performed successfully.

and the one which should be

published on the website will be
published.

3.6.11

Warden stops the rule violator and puts a penalty on him.

Actors: Warden.
Purpose: Traffic warden/officer will catch the rule violator and charge him according to
his crime.
Overview: Traffic warden will use the app so that he can enters the details of the rule
violator and issue him ticket.
Type: Primary & Secondary.
15

Typical Course Of Events:

Actor Action

System Response

1. The use case begins when the user

2. System initialize.

launch application.
3. User open Login panel.
5. User

enters

username

4. Login panel displayed.

and

6. Login successful.

password.
7. User opens issue ticket window.

8. Page displayed successfully.

9. User enters all the details and

10. Ticket
printed
and
performed successfully.

press enter.

3.6.12

16

action

Chapter 4

ESIGN & ARCHITECTURE

SYSTEM DESIGN
Once the features implemented and architecture drafted, system design is also needed to implement the
application. The following are the four diagrams that are used to implement and test the application.

Use Case Diagram

Class Diagram
Sequence Diagrams
Activity Diagrams

4.1.1

Use Case Diagram

A use case diagram captures the actors and the role or functions they perform in system. There is only one
actor in case of our project which is the person who use our application.

17

Class diagram

18

4.1.2
4.1.2.1

Sequence Diagrams
Warden Login

Figure 4.1.2.1: Sequence Diagram (Warden Login)

4.1.2.2

Issue Challan

Figure 4.1.2.2: Sequence Diagram (Issue Challan)

19

4.1.2.3

Admin Login.

Figure 4.1.2.3: Sequence Diagram (Admin Login)

4.1.2.4

Manage Challan

Figure 4.1.2.4: Sequence Diagram (Manage Challan)

4.1.2.5

Manage Wardens

20

4.1.3.6

Add Wardens

Figure 4.1.3.6: Sequence Diagram (Add new warden)

4.1.2.7

Delete wardens details

Figure 4.1.2.7: Sequence Diagram (Delete Wardens Details)

21

4.1.2.8

Update details of wardens

.
Figure 4.1.2.8: Sequence Diagram (Update details of wardens)
4.1.2.9

Manage laws

Figure 4.1.2.9: Sequence Diagram (Manage laws)

4.1.2.10

Update law

22

Figure 4.1.2.10: Sequence Diagram (Update law)

4.1.3.11

Delete law

Figure 4.1.2.11: Sequence Diagram (Delete law)

4.1.3.12

Add law

23

4.1.2.13

4.1.2.14

Traffic rules

Job Information

24

4.1.3 Activity Diagrams

4.1.3.1

Admin Login

25

4.1.3.2

Manage Challan

26

4.1.3.3

Adding new warden

27

4.1.3.4

Delete wardens details

28

4.1.3.5 Updating wardens details.

29

4.1.3.6 Add new law

4.1.3.7 Delete law

4.1.3.8 Update law

30

4.1.3.9 Warden Login

4.1.3.10 Challan Activity

31

4.1.3.11 Rules information activity

32

4.1.3.12 Fine violation activity

33

4.1.3.13 Reports activity

34

Chapter 5
35

IMPLEMENTATION
Fall Detection application is designed from user point of view and user friendly design of our application
helps the user in accomplishing their task with ease. We have made attempts to keep design simple and easy
to understand.
The screens were designed in XML and the business logic was written in Java and android internal database
is used to store templates.

5.1.

JAVA DEVELOPMENT KIT (JDK)

5.1.1

Developer Productivity
JDK 8.0 is used to develop this application. Java Development Kit (JDK) is a program development

environment for writing java applications. It consists of runtime environment that sits on top of the
operating system layer as well as the tools and programming that developers need to compile, debug and run
applications written in java language.

5.1.2

Improved Performance
It provides better performance by taking advantage of early binding, just in time compilation, native

optimization and caching services right out of the box. All processes can be created in their place, which
helps to keep the application constantly available to handle requests therefore performance is improved.

5.1.3

System Requirements for Eclipse IDE

Processor:

2.8 Mhz or above

RAM

1 GB

Hard Disk

Dedicated drive for improved performance and storage

5.2.

USER INTERFACE

The system is user friendly.

Interface of the system is easily understandable.
The system is reliable for any software producing company.
User need not take any additional effort to understand the functionality and navigation in our

application.
The colors are chosen in such a way that user can easily understand where the input has to be given.

36

Chapter 6

TESTING AND EVALUATION

We have adopted industry best practices for testing and evaluation phase and brief description of all these
are listed below:

6.1.

VERIFICATION

After completion of each phase verification was done. To verify the requirements the completed phase was
fully tested. Against the requirements all the units were found to be completely satisfactory. As the system
should be verified at each stage of the software process using documents produced during the previous stage
therefore we started verification with requirements reviews and continued through design and code reviews
to product testing. This is an activity to verify whether we have built the system right or not in the
development life cycle.

6.1.1

Functional Testing

Below are some of the test cases to verify the system functional abilities.
Test Case 1
Test Case Id

TC1

Objectives

Enter Personal Information

Environment

Android

Process

User enters his or her name, age and choose login.

Expected Result

User's profile will be maintained by system.

Actual Result

Pass

Test Case 2

37

Test Case Id

TC2

Objectives

Warden register

Environment

Android

Process

User enter his complete information and register.

Expected Result

System will store the information.

Actual Result

Pass

Test Case 3
Test Case Id

TC3

Objectives

Website running

Environment

Web

Process

Open website and check whether it is running or not.

Expected Result

Everything is working correctly.

Actual Result

Pass

Test Case 4
Test Case Id

TC4

Objectives

Issue Challan

Environment

Android

Process

Warden enters the complete information.

Expected Result

Complete information will be stored in database and challan

is issued.

Actual Result

Pass

38

Test Case 5

Test Case Id

TC5

Objectives

Assign duty points

Environment

Android

Process

Enter complete information and assign duty points.

Expected Result

Our system take complete info required and will assign

duties.

Actual Result

Pass

Test Case 6

Test Case Id

TC6

Objectives

New alerts

Environment

Web

Process

Alerts will be generated on website.

Expected Result

System will generate alerts on website.

Actual Result

Pass

6.2

STATIC TESTING

For any types of syntax errors and other logical ones, software coding was checked. System's stable
condition was satisfied and our system will alert the user if he or she performs any action whose prerequisite
is not performed and our system will not fail in any process. So, the results of this testing were successful.

6.3

VALIDATION

At the end of development process of each module validation was done. To make the validation process
successful, the modules were nicely merged to form up the required end-product which was actually
required. As the system should be validated at each stage of the software process using documents produced
during the previous stage therefore we started validation with requirements reviews and continued through
39

design and code reviews to product testing. This testing was done to validate that we have built the right
product that is according to requirements and testing results are successful.

6.4

USABILITY TESTING

It was also done at the end of development of each module. As users were able to complete basic tasks
easily, and quickly and usage of standards made it possible for the users to make minimal mistakes, so the
results were successful. Users were very confident about the tasks completed and the users were able to
recall the process easily.

6.5

MODULE / UNIT TESTING

Each method is tested during its coding stage and every method has some functionality and it is tested
during its creation. For any sort of bugs left in the code, all the units were individually tested. We found
during this process few bugs and removed those bugs. The testing was done recursively until no bug was
found. The tests were successful.
As we said that in unit testing, various modules have been tested individually. To test if the expected result is
actually seen on the screen, unit testing has been done manually.

6.6

INTEGRATION TESTING

Various units after successful development were integrated together and their working and behavior was
tested. This test was also successful.

6.7

SYSTEM TESTING

With various test cases, the system as a whole was tested. For each and every mode of the software's
operation, the tests were carried out which was fruitful.

40

Chapter 7

CONCLUSION AND FUTURE WORK

In this chapter we will first provide conclusion of our project and then we will provide a way to extend this
project which will mention in section 7.1. Conclusion and in section 7.2. Future Work respectively.

7.1.

CONCLUSION

By doing this project we just conclude that ITP is a vast field to research and one can done a meaningful
study by using more resources.
We also realized that to make ITP system for a specific group of users, real fall data from the targeted users
should be used. For our own system, we have not assumed any targeted group of users because we limited
our focus of research to investigating.
We concluded that making mobile application of ITP it is easy to spread to anyone with mobile phone. And
now as we developed our system in Android then to translate this application to other platforms should not
be a difficult task.
As our system is not configured for different users so we were not able to test the adaptability of system for
different users. But we have set the sensitivity level for our user. So, the system provide a way to user to
prevent false positives,
As effectiveness of a system is what system does after sensing a fall so, in our case system after sensing a
fall used built in communication means like Phone call and SMS.
We also concluded that our system has high market value due to high market value of Android as these are
not very expensive phones.
Our system will help the elder people as well as the young people suffering from different diseases. It will
solve a major problem of a society at very less cost. Because we provided this approach, so, anyone can
easily afford this.

7.2.

FUTURE WORK

As we have only used and tested 4 specific acceleration-based algorithms implemented in a smart phone.
Our literature review section provides other concrete acceleration based algorithms like partition of signal
method that can be tested and implemented in a smart phone. One can further use these algorithms as it is or
can just use them as a basis for an improved algorithm. We are now focusing to do it in future.

41

Also, in this study, we just used the accelerometer sensor of smart phone but a smart phone equipped with
other sensors as well. So, in future gyroscope sensor to detect the angular rotation and magnetometer sensor
to detect the change in position can be used to improve the fall detection system.
As suggested by our project supervisor one can look at if sending a photo and audio recording as part of
outgoing alert message which would provide better way to assess the situation of user and see the severity of
fall.
There could be another way to improve the fall detection which is that as one can perform a more advanced
machine learning algorithm in the PC if user is indoors and if user goes outdoors then the mobile device
shifts to a more resource saving system in the mobile phone itself.

42

Chapter 8

REFERENCES
REFERENCES
i.

www.java.net-tutorial.com

ii.

www.eclips.org

iii.
iv.
v.
vi.

www.lifelinesys.com
www.tutorialspoint.com/java
www.fampra.oxfordjournals.org/content/17/6/490.abstract
www.dis.ijs.si/mitjal/documents/Fall_detection_and_activity_recognition_with_machine_learningInformatica-09.pdf

*******

43