Crime Investigation

Crime Investigation System
CHAPTER 1
Gathering & Analyzing Info
The Islamiya University of Bahawalpur RYK Campus Page 1

1.1 INTRODUCTION
Crime Investigation Reporting System is used to map the reported crime to identify the crime
clusters’ have designed a mobile lead solution where users from the each of 4 Police station’s
in Rahim yar khan can geo-tag the crime location, nature of the crime, date and time when
crime was committed along with a snapshot from the location.
Connecting the data from the Android lead reporting to the web dashboard, the crime
investigation authorities can now see the patterns of crimes, strongholds of street crimes or
customized reports on the rise of a specific kind of crime in any specific area/range. Based on
the heat map, the authorities are then taking serious steps to curb the strongholds of the
criminals and take necessary steps. This also helps the senior police officers monitor and
inquire about the progress of the police stations of the critical areas in the light of the up to
date crime database.
1.2 INTRODUCTION TO TECHNOLOGY USED

CodeIgniter is an Application Development Framework a toolkit for people who build web
sites using PHP. Its goal is to enable you to develop projects much faster than you could if
you were writing code from scratch, by providing a rich set of libraries for commonly needed
tasks, as well as a simple interface and logical structure to access these libraries. CodeIgniter
lets you creatively focus on your project by minimizing the amount of code needed for a
given task.
CodeIgniter is right for you if:
 You want a framework with a small footprint.
 You need exceptional performance.

 You need broad compatibility with standard hosting accounts that run a variety of
PHP versions and configurations.
 You want a framework that requires nearly zero configuration.
 You want a framework that does not require you to use the command line.
 You need clear, thorough documentation.
1.3 PROJECT OVERVIEW

The software is assisting the police to record daily crimes on their online repository through
their mobile application. The officer and/or the witness record the crime through the
web application from the place of incident with a picture location on the Google Map
along with date of incident and the sections of law applicable. Daily reporting on the
software creates crime patterns across Rahim yar khan identifying the crime pockets,
the high time of increased crime rate and the areas that are hotspots. Further, the online
data warehouse has not only enabled the investigation teams to nab down the culprits
involved but police has also been able to improve their traditional techniques and
strategies to protect the citizens from various street crimes. Thus, the crime mapping
software has benefited in monitoring and eliminating the growth of overall crime to a
great extent. Moreover, by creating an online data warehouse, the software team has
reduced the corruption and stigmatization of the law enforcement agencies in Rahim
yar khan.
1.4 Actor Catalogue
Administrator
Administrator will Make all types of changing’s.

Admin will be able to change and delete record.
Admin will Keep track of all changes.
Admin will allocate the rights to the users.
Admin will access all activities and view all reports.
DPO

DPO will be able to check all map view.

DPO will be able to see all information of crime on map.
DPO will be able to see charts and graphs.
SHO
SHO will be able to see the crime record of his own police station
SHO will be able to see the crimes on map of his police station
Field Officer
Field Officer will be able to add all record of crime committed.

Field officer will be able to see his record
1.5 USE CASES DIAGRAM
Administrator:

DPO:

SHO:

Field Officer:


System Diagram:

1.3 Usage Scenarios
Scenario No 1:
Project Name : Online Crime Investigation System
Use Case Id : Use Case # 2
Use Case Name : DPO
Primary Actor : DPO
 DPO will be able to check all map view.

 DPO will be able to see all information of crime on map.
 DPO will be able to see charts and graphs.
Pre-Condition
 Open DPO Dashboard,
Flow of Events  View Map,

 See All latest entry,

 Connection fails and provide null values

Exception :  Connection time out
 Link down
Scenario No 2:
Use Case Name : Administrator
Primary Actor : Admin
 Should be able to add user and his role,

 Should be able to update user and his role,
 Should be able to delete user and his role,
Pre-Condition
 Should be remaining consistency,
 Should be able to refresh record,
 Must Login,
 Check Constraints.

 Saved Successfully,
Post –Condition  Update Successfully,

 Delete Successfully,
 Refresh Successfully.
 Open main Dashboard,
Flow of Events  Register Users,

 Update existing data,
 Delete existing data,
 Refresh data.

Scenario No 3:
SHO
Use Case Name :
Primary Actor : SHO
 Should be able to see crime reports of his own police station.

 Should be able to see all map views.
Pre-Condition
 Open Dashboard,
 View crimes related reports of his police station on map,
Flow of Events
 See All latest entry,
Exception :  Connection fails and provide null values

 Connection time out
 Link down
Scenario No 4:
Use Case Name : Field Officer
Primary Actor : Field Officer
 Should be able to add crime location where the crime was

committed and all information related to that crime.
Pre-Condition  Should be able to see his entry on map.
Successfully Inserted.
Post-Condition
 Open Field Officer view,

 View all crimes reports of his police station on map,
Flow of Events
 See All his latest entry,
Exception :  Connection fails and provide null values

 Connection time out
 Link down
1.6. Functional Requirements & Non Functional requirements

1.6.1. FUNCTIONAL REQUIREMENTS
1.6.1.1. DPO
 DPO should be allowed to sign in for the system as a DPO to perform the
activities.
 DPO should be allowed to visit all maps view to a visitor or guest.
 DPO should be allowed to filter all crime category on map.
1.6.1.2. Administrator:
 Administrator should be allowed to Register/Manage users.
 Administrator should be allowed to access all features of the web
application.
 Administrator should be allowed to edit entry of field officer.
 Administrator should be able to allocate the role of each user.
1.6.1.3. SHO
 Should be able to see crime reports of his own police station.
 Should be able to see all map views.
1.6.1.4. Field Officer:
 Should be able to add crime location where the crime was committed and
all information related to that crime.
 Should be able to see his entry on map.
1.6.2. NON FUNCTIONAL REQUIREMENTS

Additional specifications imprison requirements that are not included in the use cases. These
are usually called non functional requirements. Requirements which are necessary for the
software to run or work properly are described here.
1.6.2.1. Usability:
Website should be use with customer satisfaction. It should have simple and independent
code that can be reused if needed. Simple GUI should be used.
It must be user friendly.
1.6.2.2. Reliability:
The reliability of the proposed system will be high due to the above functional reasons. The
reason for the increased reliability of the system is that now there would be proper storage of
information. The system shall be available all the time.
1.6.2.3 Performance:
The performance is at its best if stored locally, as the response time will be much faster. If the
product accessed via Internet, the performance is limited by the connection speed. The only
foreseen limitation is that of web server response. The system shall give responses in 1
second after checking the Customer’s or web information.
1.6.2.4 Security:
Any user who uses the system shall have a Login ID and password. Any modification (Insert,
delete and update) for the site shall be synchronized and done only by the administrator.
Registered Users shall only be able to view all information and the information as they are
permitted to do anything.
1.6.2.5 Maintainability:
The system shall provide the capability to back-up the Data. The system shall keep a log of
all errors.

CHAPTER 2
Envisioning the Solution
2.1 MODULES OF THE SYSTEM

2.1.1 Registration
Users can registered by the admin. Each user is signed in to the web application by using his
unique id and password associated by the system.
2.1.2 Role Management

Each User has Different Role and each role has different access criteria.
2.1.3 Crime Mapping

All crime locations are drawn on map with using markers with crime detail.
2.1.4 Crime Category Filter

All crimes using crime category filter is filtered on map.
2.1.4 Chart Management

Through the up to date reporting mechanism, the progress of all crime reporters is
available live and this has helped the Police Department to improve the performance of the
staff with strong checks on the nature of reporting, meeting deadlines and reduction of false
reporting.
2.2 SCOPE OF THE SYSTEM

The scope of a system means that which areas are being covered by the system. The scope
clearly defines the boundaries of the system. The functional area of this application in which
through the up to date reporting mechanism, the progress of all crime reporters is available
live and this has helped the Police Department to improve the performance of the staff with
strong checks on the nature of reporting, meeting deadlines and reduction of false reporting.
In-depth reporting available to the stakeholders brings different analysis of the crime pattern
and reveals very key information which is hard to dig from the meetings of the 4 Police
Stations and sharing the information in written or verbal form of communication. With a few
clicks, the power users can see what crime is tending in a certain locality and also in a
specific time frame.
2.3 PROJECT OBJECTIVES

The objectives of the project describe that what is to be ultimately achieved from the
development of the project. It is always essential and helpful for designing a computer based
system, to understand all the objectives and the requirements that the computer based system
is expected to satisfy in addition, the relative importance of each objective should also be
understood. The system is required to fulfill the following objectives.
1. To assure the availability of the right information at the right time.
2 .To make the information storage, processing and retrieval efficient.
3. To provide a system with a user-friendly interface which is simple to
Understand and efficient to use.
4. To provide a system which can easily modified for the future enhancement.
2.4 MAIN FEATURES OF THE PROPOSED SYSTEM

The proposed system has the following main features.
2.4.1 Efficiency
Efficiency of any system is concerned with the minimum processing time as well as the
optimal use of system resources in designing the proposed system; the efficiency factor has
been taken well into consideration.
2.4.2 User Friendly Interface
The interface of the system will be user friendly. The data retrieval, insertion, editing, and
deletion will be made easy and simple, so that a common user can handle the database
efficiently.
2.4.3 Minimum Redundancy

In the proposed system all the master data is stored in unique tables and other tables can
access this data through list of values. So, there is minimum chance of redundancy.
2.4.4 Facilitated Data Input

The simple to use data entry forms will be provided to facilitate the user to enter the data in
the databases. The powerful data entry controls have been provided to view, add, modify and
delete the fields of a record.
2.4.5 Data Security and Integrity

MYSQL Server is used for the back-end as a database. Which is a true relational Database
tool, so all requests to insert data in a table, or to update, delete or view data in a table must
be routed through RDBMS engine only. Direct calls for data, cannot be made through tables
themselves. Since there is a single point of control for data manipulation, therefore it provides
excellent data security.
2.5 FEASIBILITY STUDY

The main purpose of feasibility study is to consider the proposed system with a view to
decide whether the development of the proposed system is feasible for the organization in the
underlying circumstances. It is considered that whether the proposed system will meet all the
requirements of the organization with lesser cost and with improved efficiency than the
existing system if exists.
The feasibility of a system is considered from the following three aspects.
l. Financial feasibility
2. Operational feasibility
Each of the above is briefly explained below.
Financial Feasibility
1. Sublime Text 3
2. MYSQL Server
3. Codeignitor (PHP)
For which the organization has to purchase the license and no other expensive development
tools, Software or Hardware is used, so the project is very much feasible economically and
financially.
Operation Feasibility
The proposed system will be operationally feasible because it will be efficient, accurate and
reliable and will provide more facilities than other existing systems. The proposed system
will be user friendly and easy to understand, so average person would be able to understand
and use this system easily, no high computer knowledge would be required for it.

CHAPTER 3
Planning the Solution
3.1 FUNCTIONAL SPECIFICATION

In functional specification declare all functions and needs of software as that given below.
3.1.1. Business Requirements:

The organization was to want produce like that students that fulfill all our country
requirements and they have enough knowledge of circuit making gates, laws and functions.
They must have theoretical as well as practical knowledge of hardware and it is possible only
when they have such any system.
3.1.2. User Requirements:
All users it mean teacher and students need a proper channel for best understanding internally
working of Circuits Such as teacher wants to deliver his lecture in such way his students can
easily understand his lecture and give a good response And students want to understand
everything about circuits making, and wants to see graphically working anything about it that
make them able. They raise the image of their institute.
3.1.3. Operations Requirements:
For operational requirements it is necessary for software engineer that he take a good view
about that what the necessities are for make such software that fulfill the needs the needs of
user requirements. For this purpose I when I take a deep view of user requirements so decide
I will make a system that show graphically internal working of gates or functions that are
using in inside the circuits. So I select Visual Studio and SQL server because I find it suitable
for my software requirements, and I start working on it.
3.1.4. Conceptual Design
DESIGN:
I divided this phase into two steps:
 Logical Design
 Physical Design
3.1.5. Logical Design:

In this part of third phase I made the specifications about the design of the UML
design.
The considerations Ire:
 Number of pages
 Layouts
 Sketches allocation of data to relevant pages.
By considering all the options I made layouts on the paper. This stage was totally on
hard paper. After having made all the layouts I get it checked from the client and by
having a compliment from their side I proceeded to next part of the design phase.
3.1.6. Physical Design:
In this stage I converted all the logical design that was on the paper to computer and
made a soft copy of it. After matching the specified pages. I defined their relevant
features, wording and pictures that made it more attractive. By having it approved
from my client I started for the development phase.
Logical Design




3.2 MASTER PROJECT PLAN:
In master plan of my project I want to develop complete system software that solve all
electronics students problem as graphical point of view and they could easily use
every functions that I mention and develop in my project and they give input for every
function and could view every function output as graphically and it is interesting for
them they use good looking software for their work.
3.3 RISK MANAGEMENT (RM):
This document provides a reliable approach to the important matter of risk

management and assessment.
Purpose of RM:
When managing projects, one of the first steps is to evaluate the risk attaching to the
project and then managing that risk. Risk tends to be high early in a project when
expenditures are low. Conversely, risk tends to be low later in a project when
expenditures are high. Accordingly, it is important that an early effort be made to
minimize project risk. This must be done early in the project when expenditure is low,
rather than later when the expenditure is high. In other words, risk should be dealt
with during the project initiation phase and then shifted “upstream” into the later
project stages. Frequency of reporting should be highest when risk is highest.
The objective of this document is to identify, contain and eliminate risks on a project.
Also to ensure that risks are identified and assessed as early as possible in the project
which allows the project manager to make informed decisions as to the direction of
the project so that it may lead to a successful conclusion?
The Major Risk is covering the sales Record, Purchase Record or main is Product
Available in Record.

CHAPTER 4
Development

4.1. Project Development plan:
4.1.1. Project Life Cycle
Project life cycle consists of number of phases for that, there to exit some theories. According
to David I. Cleland and William Richard king, that phase of effective product management
include,
 Conceptual Phase
 Definition Phase
 Production Phase
 Operational Phase
 Divestment Phase
4.1.2. Conceptual Phase:
The conceptual phase is when the design team is working with the customer to determine the
overall requirements for the product and potential deficiencies of existing processes and
products. The initial: One example would be the recent development of super fast partial BDS
system. Conceptual these systems were conceived many years ago but only recently have
become a reality. The reason is that the available technology could not support it. Now that
computer has multiple gigabyte memory available these calculations can be completed
directly in the active memory core without incurring the slowdown of the reading and writing
to the hard device.
In the conceptual phase the project team provides the answer to
What will the product cost?
When the product will available?
What will the product do?
How can the product be integrated into the exists system?
The overall design and production approach is determined during this phase and an initial
statement of work is prepared for the further detail in the definition phase.

4.1.3. Definition Phase:
The definition phase is when detail plain is prepared that determine the realistic cost,
Schedule and performance requirement for human and other critical resources. A good
Project manager will also identify those areas that risky or cause for concern. These areas are
then further detailed for recovery and contingency plan. This is very difficult than the
traditional BDS system environment where the teachers teach students their as usual way
they not show any graphical environment. In the traditional BDS environment the assumption
is that everything will worked exactly as planned.
In the definition phase the detailed statement of works is developed and broken down to the
necessary level for control purposes. An effective statement of works (SOW) should be
clearly define the objectives for the project and how success will be measured. The statement
of work should include cost and schedule target as well as quality target and usually become
the contractual statement of work.
Since revenue is directly related to the statement of work it is very important to have
agreement with the customer on the definition of keywords.
Once statement has been define and approved the work began on the work breakdown
structure. A graphical representation of work breakdown into structure.
4.1.4. Production Phase:

The production phase of a project begins with the verification of the product production
specification and the beginning of the production of the unit.
The final preparation and dissemination of document is incorporate in this phase including
the development of technical and service manuals and other traceability that is required by
the products.
Many companies are moving to release this information on CD-ROM due to the cost of
preparing this essential document format. The product id tested to ensure that the
specification defined in the definition phase have been achieved BDS can be used to bridge
the information of gates that are used inside the circuits. Timely status feedback is essential
this phase is to provide an early warning of any part of the project that may not support the
required completion.

4.1.5. Operational Phase:

The operational phase of the project is when the project has been delivered to the students
and teacher. This can be a time when the teacher may be intimately involved the installation
or the training for the development of website
During the operational phase, the realized costs are compared with the Build costs.
To determine whether or not the system has been delivered at a profit.
1. Budgeted cost of work schedule
2. Actual cost of work schedule
3. Budgeted cost of work performed
4. Schedule Variance
5. Cost Variance
4.1.6. Divestment Phase:

The divestment phase of a project manufacturer is the phase where the project team is
transitioned from one project to the next. Some institutes will dedicated personal hundred
percent to a particular System. When this system has been completed it is essential to
recognize the organization and cost implications of having another system ready to start if the
project team does not see another system for development available on the horizon there
could be tendency to stretch the current project as long as possible; this can contribute to cost
overruns on the current project and adversely impact the profit for this Superior Goods
Transport Management System.
This divestment phase is critical time that must be managed effectively so the organization
can take the lessons learned on the previous system and apply them to next system.
Unfortunately many people experience overall project

4.2 ACTIVITY DIAGRAMS
4.2.1. Admin
Login
Invalid
valid
Manage/Register Manage Crime Manage Crime View Simple Map View pie View Line
User Detail Category and heat map charts Graph
Logout

4.2.2. Crime Report Activity:
Field Officer
Login
Add Crime Report view report of crime

and location on map
Save
Logout

4.2.3. DPO Activity:
DPO
Login
Select police
view map Filter Crimes view charts view graphs
station
Logout

4.3. Sequence Diagram:
4.3.1. Sequence Diagram of Administrator:
Admin System Database
Login
Verify
Logi n successfull Response
Add/ Edit
Police offi cer's
detail's stored
details
Details Stored
Successfully Response
Add/ Edit
Police-stations Detail stored
detai ls
Response
Details stored
successfully
Show Request
-
all feedback response
Logout
Logout
successfull

4.3.2. Sequence diagram of field officer:
Field officer System Database
Login Verify
Login Succesfully Response
Enter crime Location Request
Location entered Response
Crime detail
Request
Stored Succesfully Response
Logout
Logout Succesfully

CHAPTER 5
Stabilizing

5.1. Test Plan

The test plan describes specific or overall strategy for integration. Testing is divided into like
those ways that address specific functional and behavioral characteristics of software For
Superior Goods Transport Management System for these points testing required I discuss this
in detail as below.
5.2. Objective
This document describes the plan for testing Inventory System. This Test Plan document
supports the following objectives:
 Identify that system is now error free.
 Program fulfills our customer requirements.
 Identify the software components that should be tested.
 Recommend and describe the testing strategies to be employed.
 Identify that all covered functions of BDS working properly.
5.3. Scope
This test plan applies to the integration and system tests that will be conducted on
procurement of DLD learning system. It is assumed that unit testing already provided through
black box testing through extensive coverage of source code and testing of all functions of
interfaces.
5.4. Test Strategy:

5.4.1. Test Requirements:
The listing below identifies use cases, functions requirements that have been identified as
target of testing. This list represents what will be tested.
5.4.2. Verification Testing:

In verification testing test that when user login system check user name or password then
give him permission for login.
5.4.3. Validation Testing:
In this testing check user have a valid input or it is in form of digital.
5.4.4. System testing (i.e. Functional Testing)
Manage User Login Use Case

Manage System Use Case
5.5. User Interface Testing
Verify ease of navigation through a sample set of screens.

Verify sample screen confirm GUI standards.
The system shall be easy to use.
Each feature of procurement of Atomized System that help the user to understand every step
easily.
5.6. Performance Testing:
The system shall support the maximum simultaneous against the Atomized System at any
given time.
5.7. Load Testing:
Verify system response when loaded with maximum users.

The system shall support no of simultaneous user against the Atomized system at any given
time.

5.8. Stress Testing:
Verify system response during maximum user logins.
5.9. Security and Access Control Testing:
Verify login from a remote PC.

Verify login security through username and password mechanisms.
5.10. Test Strategy:
The test strategy presents the recommended approach to the testing of the software
applications. The previous section of Test requirements describes what will be tested; this
describes how it will be tested.
The main considerations for the test strategy are the techniques to be used and the criterion
for knowing when the testing is completed.
In addition to the considerations provided for each test below, testing should only be executed
using known, controlled system, in secured environments.

5.1.1 Testing Types
System Testing:
Testing of the application should focus on any target requirements that can be traced directly
to use cases (or business functions), and business rules. The goals of these tests are to verify
proper data acceptance, processing, and the retrieval, and the appropriate implementation of
the business rules. This type of testing is based upon black box a technique that is verifying
the application (and its internal processes) by interacting with the application via the GUI and
analyzing the output (results). Identified below is an outline of the testing recommended for
each application?
User Interface Testing:
User interface testing verifies a user’s interaction with the software. The goal of UI Testing is
to ensure that the User Interface provides the user with the appropriate access and navigation
through the functions of the applications. In addition, UI Testing ensures that the objects
within the UI function and expected and conform to corporate or industry standards.
Performance Testing:
Performance testing measures response times, transaction rates, and other time sensitive
requirements. The goal of Performance testing is to verify and validate the performance
requirements have been achieved. Performance testing is usually executed several times, each
using a different “background load” on the system. The initial test should be performed with
a “normal” load, similar to the normal load experienced (or anticipated) on the target system.
A second performance test is run using a peak load.

Load Testing:
Load testing measures subjects the system under test to verifying workloads to evaluate
system’s ability to continue to function properly under these different workloads. The goal of
load testing is to determine and ensure that the system functions properly beyond the
expected maximum workload. Additionally, load testing evaluates the performance
Characteristics (response times, transaction rates, and other time sensitive issues).
Stress Testing:
Stress testing is intended to find errors due to low resources and competition for resources.
Low memory or disk space may reveal defects in the software that are not apparent under
Normal conditions. Other defects might results from competition for shared resource.

Verify that the system and software function properly and

without error under the following stress conditions:
Little or no memory available on the (server)
Test objective:
Maximum (actual or physical capable) number of clients
connected (for simulated)
Multiple users performing the same function
Use tests developed for Performance Testing.

To test limited resources, Test should be run on single
machine; RAM on server should be reduced (or limited).
Technique:
For remaining stress tests, multiple clients should be used,
either running the same tests or complementary tests to
produce the worst case transaction volume/ mix.
All planned tests are executed and specified system limits are
Completion Criteria: reached/exceeded without the software or software failing ( or

conditions under which system failure occurs is outside of the
specified conditions).
Stressing the network may require network tools to load the
Special Considerations: network with messages/packets.

The DASD used for the system should temporarily be reduced
to restrict the available space for the database to grow.

5.2 Test Cases
Test Case: 01_Login

User enters particular information in the registration form to get registered with Crime
Investigation System
S.N Scenario Expected Output System Output Status/Comments
o
1 User enters invalid user name Displays Invalid Username Information

or password left blank. corresponding and password entered is invalid
error or tells some
field has been left
blank.
2 User enters correct information User is User is displayed No error
in the login form. successfully login. the Dashboard.
Test Case: 03_Add Crime Detail

User wants to add crime detail report.

o
1 User wants add whole crime All Corresponding This information None
report and all information about category of crime is displayed on
the particular crime committed. is displayed. map.

Test Case: 04_Invalid Area

.
S.No Scenario Expected Output System Output Status/Comments
1 User adds an invalid Area. System does not Error is displayed Information
accept an invalid according to the entered is invalid
area. case. or field is empty.
2 User enters correct information. Update Information No error

successfully. Update
successfully.
Test Case: 5_Logout

User wants to Logout from system.

o
1 User clicks on logout from the User successfully User successfully Nil
system. logout. logout.

CHAPTER 6
Deployment

6.1. Screenshots:

6.2. APPENDIX
Activity:
A unit of work that a worker may be asked to perform.
Actor (instance):
Someone or something outside the system or business that interacts with the system or
business.
Actor class:
A class that defines a set of actor instances in which each actor instance playa the same role
in relation to the system or business.
Architectural pattern:
A description of an archetypal solution to a recurrent design problem that reflects well-
proved design experience.
Artifact:
A piece of information that is produced, modified, or used by a process, defines an area of
responsibility, and is subject to version control. An artifact can be a model, a model element,
or a document.
Actor:
Anything with behavior such a person, computer system or organization. The third phase of
Unified Rational Process, in which the software is brought from an executable architectural
baseline to the point at which it is ready to be transitioned to the user community.
Design:
The part of the software development process whose primary purpose is to decide how the
system will be implemented. During design, strategic and tactical decisions are made to meet
the required functional and quality requirements of a system.
Design model:
An object model that describes the realization of use cases; serves as an abstraction of the
implementation model and its source code.
Development Case:

The software engineering process used by the performing organization. It is developed as a

configuration or the customization of the Rational Unified Process product and adapted to the
project’s needs.
Framework:
A micro-architecture that provides an incomplete template for applications within a specific
domain.
GUI:
Graphical User Interface
Inception:
The first phase of the Rational Unified Process, in which the initial impetus for developing
software an idea, a prototype, a request for proposal (REF), an evolution over a previous
generation is brought to the point of being funded (at least internally) to enter the elaboration
phase.
Prototype:
Working model of proposed system.
Risk:
Anything that may hinder the achievements of goal.
S.S.D:
System Sequence Diagram
Stakeholder:
Anyone who has interest in system.
Milestone:
The point at which iteration formally ends; corresponds to a release point.
Model:
A semantically closed abstraction of a system. In the Rational Unified Process, a complete
description of a system from a perspective “complete” meaning that you don’t need
additional information to understand the system from that perspective; a set of model
elements.
Object:
An entity with a well- defined boundary and identity that encapsulates state and behavior.
State is represented by attributes and relationships, and behavior is represented by operations
and methods. An object is an instance of a class.

Object model:
An abstraction of a system’s implementation.
6.3. REFERENCES
Online References
http://www.google.com
http://www.maps.google.com
http://www.developers.google.com/maps/
http://www.stackoverflow.com
http://www.codeignitor.com
http://www.getbootstrap.com
http://www.wikipedia.com


Crime Investigation

Caricato da

Informazioni sul documento

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

Crime Investigation

Caricato da

Copyright:

Formati disponibili

Crime Investigation System

The Islamiya University of Bahawalpur RYK Campus Page 1

1.2 INTRODUCTION TO TECHNOLOGY USED

CodeIgniter is right for you if:

 You want a framework with a small footprint.

 You need exceptional performance.

1.3 PROJECT OVERVIEW

The Islamiya University of Bahawalpur RYK Campus Page 2

1.4 Actor Catalogue

Administrator will Make all types of changing’s.

The Islamiya University of Bahawalpur RYK Campus Page 3

DPO will be able to check all map view.

Field Officer will be able to add all record of crime committed.

1.5 USE CASES DIAGRAM

The Islamiya University of Bahawalpur RYK Campus Page 4

The Islamiya University of Bahawalpur RYK Campus Page 5

The Islamiya University of Bahawalpur RYK Campus Page 6

The Islamiya University of Bahawalpur RYK Campus Page 7

The Islamiya University of Bahawalpur RYK Campus Page 8

The Islamiya University of Bahawalpur RYK Campus Page 9

1.3 Usage Scenarios

Project Name : Online Crime Investigation System

Use Case Id : Use Case # 2

Use Case Name : DPO

Primary Actor : DPO

 DPO will be able to check all map view.

 Open DPO Dashboard,

Flow of Events  View Map,

The Islamiya University of Bahawalpur RYK Campus Page 10

 Connection fails and provide null values

Project Name : Online Crime Investigation System

Use Case Id : Use Case # 2

Use Case Name : Administrator

Primary Actor : Admin

 Should be able to add user and his role,

The Islamiya University of Bahawalpur RYK Campus Page 11

Post –Condition  Update Successfully,

 Open main Dashboard,

Flow of Events  Register Users,

The Islamiya University of Bahawalpur RYK Campus Page 12

Project Name : Online Crime Investigation System

Use Case Id : Use Case # 3

Primary Actor : SHO

 Should be able to see crime reports of his own police station.

Exception :  Connection fails and provide null values

Project Name : Online Crime Investigation System

Use Case Id : Use Case # 4

Use Case Name : Field Officer

Primary Actor : Field Officer

 Should be able to add crime location where the crime was

 Open Field Officer view,

Exception :  Connection fails and provide null values

1.6. Functional Requirements & Non Functional requirements

The Islamiya University of Bahawalpur RYK Campus Page 14

1.6.1. FUNCTIONAL REQUIREMENTS

1.6.1.4. Field Officer:

 Should be able to see his entry on map.

1.6.2. NON FUNCTIONAL REQUIREMENTS

The Islamiya University of Bahawalpur RYK Campus Page 15

The Islamiya University of Bahawalpur RYK Campus Page 16

2.1 MODULES OF THE SYSTEM

The Islamiya University of Bahawalpur RYK Campus Page 17

2.1.2 Role Management