Presentation on project

CrimeFile

INTRODUCTION
The project titled as Online Crimefile Management is a web based application. This software provides facility for reporting online crimes, complaints, missing persons, It also shows the most wanted person details. Mailing as well as chatting can be done. Any Number of clients can connect to the server. Each user first makes their login to the sever to show their availability. The server can be any Web Server. An SMTP Server must be maintained for temporary storage of emails and chat jar files for enable the chatting facilities

DAY - 1

Four Project Dimensions

People Process Product Technology

Trade-off Triangle
Fast, cheap, good. Choose two.

Trade-off Triangle
Know which of these are fixed & variable for every project

People
Its always a people problem Gerald
Weinberg, The Secrets of Consulting

Developer productivity: 10-to-1 range - Improvements:

- Team selection - Team organization Motivation

People 2
Other success factors
Matching people to tasks Career development Balance: individual and team Clear communication

Process
Is process stifling? 2 Types: Management & Technical Development fundamentals Quality assurance Risk management Lifecycle planning Avoid abuse by neglect

Process 2
Customer orientation Process maturity improvement Rework avoidance

Product
The tangible dimension Product size management Product characteristics and requirements Feature creep management

Technology
Often the least important dimension Language and tool selection Value and cost of reuse

Planning
Determine requirements Determine resources Select lifecycle model Determine product features strategy

Tracking
Cost, effort, schedule Planned vs. Actual How to handle when things go off plan?

Measurements
To date and projected
Cost Schedule Effort Product features Earned value analysis Defect rates Productivity (ex: SLOC) Complexity (ex: function points)

Alternatives

Technical Fundamentals
Requirements Analysis Design Construction Quality Assurance Deployment

Project Phases
All projects are divided into phases All phases together are known as the Project Life Cycle Each phase is marked by completion of Deliverables Identify the primary software project phases

Lifecycle Relationships

Seven Core Project Phases

Project Phases A.K.A.

Phases Variation
Concept Exploration System Exploration Requirements

Design

Implementation

Installation

Operations and Support

Maintenance

Retirement

Technical Fundamentals
Requirements Analysis Design Construction Quality Assurance Deployment

DAY - 2

DIFFERENT MODULES OF PROJECT

Visitors
View Hot news: This module help the visitor to see the latest hot news which
can updated by the admin. View most wanted: Here, the visitor can also view the photo of wanted people Get registered: The visitor can also get registered with our web-site.

Registered Users
Add Complaint: This module help the user to report online complaints. Add Crime report: This module help the user to report online crimes. Add Missing person: This module help the user to report online missing persons details also we have to add photos of missing person using heterogeneous database. View Missing persons: This module help the user to view all the missing person details. View Most wanted persons: This module help the user to view all most wanted persons which can be given by the administrator. Edit Complaint: This module help the user to edit his complaint details. Edit Account: This module help the user to update his or her profile.

Registered Users
all complaint that you have posted earlier.

(continued)

View complaint status: This module allows us to view the status of

View crime status: This module allows us to view the status of the all crimes that you have posted earlier. Add and View feedback: This module helps the user to add and view feedbacks Chat: This module help the user to chat with the administrator or

with other registered users

Mail: This module helps the user to send mail to the administrator.

Administrator
View and reply user complaint: This module helps the admin to view

and reply users complaint details

View and reply user crimes: This module helps the admin to view and reply users crimes details New admin: This module used for add new admin Add and delete latest hotnews: This module helps the admin to add and delete latest hotnews. View and delete users feedback: This module helps the amin to add and delete users feedback Add, delete and view mostwanted persons: This module helps the amin to add, delete and view mostwanted person details

Administrator

(continued)

Add, delete and view missing persons: This module helps the administrator to add, delete and view missing person details Add and view Criminal registration: This module helps the administrator to add and view criminal registrations.

Add and view FIR: This module helps the administrator to add and view Fir
reports Add and view history sheet: This module helps the administrator to add and view history reports. View and delete all complaint reply: This module helps the administrator to view and delete complaint reply.

Administrator

(continued)

Add and view prisoner report: This module helps the amin to add and

prisoner Online Crimefile Management 6 reports

Change password: This module helps the amin to update his or her password Chat: This module help the admin to chat with the administrator or with other registered users Mail: This module helps the user to send mail to the user.

OBJECTIVE
Major objective of our project CrimeFiles: is : To make it easy for the general public to file complaints related to missing persons, theft or any other miss-happening. To make it easy for people to get an update on the status of complaints made by them. To see the status of the crime or complaint report. Make people aware of major crimes, wanted criminals etc. To interact with the officials through mails. To discuss on hot issues, or give suggestions and views in chat rooms.

DAY - 3

PROJECT CATEGORY

INPUT
The input design is the link between the information system and the user. It comprises
the developing specification and procedures for data preparation and those steps are necessary to put transaction data in to a usable form for processing can be achieved by inspecting the computer to read data from a written or printed document or it can occur by having people keying the data directly into the system. The design of input focuses on controlling the amount of input required, controlling the errors, avoiding delay, avoiding extra steps and keeping the process simple. The input is designed in such a way so that it provides security and ease of use with retaining the privacy. Input Design considered the following things: What data should be given as input? How the data should be arranged or coded? The dialog to guide the operating personnel in providing input. Methods for preparing input validations and steps to follow when error occur.

Input in our project

In out project well be taking input form: Visitors in the form of comments. Registered users in the form of: Complaint report Crime report Mails Chat Comments Feedback Missing persons details Editing his/ her account information. Administrator in the form of: Reply to complaints Reply to crime reports Reply to mails Reply to chats Reply to comments

OUTPUT
A quality output is one, which meets the requirements of the end user and presents the information clearly. In any system results of processing are communicated to the users and to other system through

outputs. In output design it is determined how the information is to be

displaced for immediate need and also the hard copy output. It is the most important and direct source information to the user. Efficient and intelligent output design improves the systems relationship to help user decision-making. Designing computer output should proceed in an organized, well thought out manner; the right output must be developed while ensuring

that each output element is designed so that people will find the system
can use easily and effectively. When analysis design computer output, they should Identify the specific output that is needed to meet the requirements.

Select methods for presenting information. Create document, report, or other formats that contain information produced by the system.

The output form of an information system should accomplish one or more of the following objectives. Convey information about past activities, current status or projections of the Future. Signal important events, opportunities, problems, or warnings. Trigger an action. Confirm an action.

Output in our project

In our project well be displaying the output based on: Displaying the photographs of missing persons on the website. Displaying the photographs of the most wanted criminals on the website. Updating the website continuously with latest news. Administrator can view the complaint sent to him/her Administrator can view the crime report sent to him/her Administrator can view the feedback given by registered member Registered member can view the response sent to him by the administrator to his complaint or crime report. Registered member can view the mails sent to him/her.

PROPOSED SYSTEM

Expected Advantages of Proposed System

CrimeFiles our online police station reaches citizens in their offices and homes. Proposed system will make the process of making complaints easy and comfortable for the users. Users can complaint about the crime with an assurance of identity not being leaked out. More crime complaints will be made and citizens would have a ready knowledge of new crimes There would be an increase in the level of interaction between the user and the managing authority. Searching of missing/wanted people would become more easier as the message can be spread to a wider area.

Description of the Project

Description of the Project

The aim of proposed system is to develop a system of improved facilities. The proposed system can overcome all the limitations of the existing system. The system provides proper security and reduces the manual work. The existing system has several disadvantages and many more difficulties to work well. The proposed system tries to eliminate or reduce these

difficulties up to some extent. The proposed system will help the user to
reduce the workload and mental conflict. The proposed system helps the user to work user friendly and he can easily do his jobs without time lagging.

MY MODULE

Administrator Login
View & reply user complaints. View & reply to user crimes. Create new administrator. Add & delete latest Hot News. View & delete users feedback. Add, view & delete most wanted persons. Add, delete & view missing persons. Add & view criminal registration. Add & view FIR. Add & view history sheet. View & delete all complaint reply. Add & view prisoners report. Change password. Chat. Maii.

Visitors Login
View Hot News. View most wanted people photos Get registered

Registered user login

Add complaint. Add crime report. Add missing person. View missing persons. View most wanted persons. Edit complaint. Edit account. View crime status. Add & view feedback. Chat Mail

DAY - 4

Database Tables

Login
This table shall store general information of the users. It contains following fields.

Field name username Password

Data type Varchar Varchar

Constraint/Descri ption Primary key Null

Status

Varchar

Null

Registration
This table shall store information of users. It contains following fields.

Field name name username Secretquestion Answer Address Pin Phone Email Village Taluk District State

Data type Varchar Varchar Varchar Varchar Varchar Int Int Varchar Varchar Varchar Date Varchar

Constraint/Descri ption Primary Key Null Null Null Nul Null Null Null Null Null Null Null

Complaintreg
This table shall store information related to complaints registered by the users. It contains following fields.

Field name Userid Detailsuspect Description Datc Typeofcrime

Data type Varchar Varchar Varchar Varchar varchar

Constraint/Descri ption

Primary Key

crimereport
This table shall store information related to complaints of Crimes registered by the users. It contains following fields.

Field name
userid ninformant addressinf detailssuspect description datec

Data type
varchar varchar Varchar Varchar Varchar Date

Constraint/Descri ption Primary key

complaintstatus
This table store information related to the reply by the administrator to the complaints registered by the users. It contains following fields.

Field name complaintno viewstatus

Data type Varchar Varchar

Constraint/Descri ption NULL Null

Adminregisteration
This table shall store information related to the administrator. It contains following fields.

Field name username question Answer Name Designation Oficialaddress Phonen Residentialaddress Pincode Phone

Data type Varchar Varchar Varchar Varchar Varchar Varchar Int Varchar Int Int

Constraint/Descri ption Null

prisonerregister
This table shall store information about the prisoners. It contains following fields.

Field name Prisonerno Chargesheetno Nickname Typeofcrime Familymembers Identificationmarks Height Weight Colour

Data type Varchar Varchar Varchar Varchar Varchar Varhar Varchar Varchar int

Constraint/Descri ption
Primary key

criminalregister
This table shall store information about the prisoners. It contains following fields.

Field name

Data type

Criminalno Name Nickname Agae Occupation Crimetype Address Mostyesorno

Varchar Varchar Varchar varchar

Varchar Varchar Varchar

Constraint/Descri ption Primary Key

FIR
This table shall store information about the prisoners. It contains following fields.

Field name District Datc Time Typeofoinformation Placeofoccurance Foreignlocal Act Firno Section Diaryrefno Informantadd Passportno Informationrec Distancefrompolst

Data type Varchar date Varchar Varchar Varchar Varchar Varchar Varchar Varchar varchar Varchar Varchar Varchar varchar

Constraint/Description

Data Flow Diagrams

Context Diagram

ASPECTS OF IMPLEMENTATION

Design Patterns

Design Patterns
:: What is a Design Pattern?

Each pattern describes a problem which occurs over and over again in our environment, and then describes the core of the solution to that problem, in such a way that you can use this solution a million times over, without ever doing it the same way twice. [1] [Christopher Alexander] Design patterns capture the best practices of experienced object-oriented software developers. Design patterns are solutions to general software development problems.

DATA ACCESS OBJECTS (DAO)

Data Access Objects (DAOs) : can be used in a large percentage of applications - anywhere data storage is required. hide all details of data storage from the rest of the application. act as an intermediary between your application and the database. They move data back and forth between Java objects and database records. allow ripple effects from possible changes to the persistence mechanism to be confined to a specific area.

ADVANTAGES OF DAO
Enables Transparency Enables Easier Migration Not Useful for Container-Managed Persistence

Adds Extra Layer

Needs Class Hierarchy Design

Pattern: Singleton
a class that has only one instance

Restricting object creation

problem: sometimes we will really only ever need one instance of a particular class
examples: keyboard reader, bank data collection we'd like to make it illegal to have more than one, just for safety's sake

why we care:
creating lots of objects can take a lot of time extra objects take up memory it is a pain to deal with different objects floating around if they are essentially the same

Singleton pattern
singleton: an object that is the only object of its type ensures that a class has at most one instance provides a global access point to that instance takes responsibility of managing that instance away from the programmer (illegal to construct more instances) provide accessor method that allows users to see the (one and only) instance possibly the most known / popular design pattern! (this should tell you something)

Restricting objects, continued

One way to avoid creating objects: use static methods instead
Math, System, JOptionPane is this a good alternative choice? Why or why not?

Problem: lacks flexibility Example: static methods can't be passed as an argument to a method, nor returned Problem: cannot be extended Example: static methods can't be subclassed and overridden like a singleton's could be

Implementing Singleton
make constructor(s) private so that they can not be called from outside declare a single static private instance of the class write a public getInstance() or similar method that allows access to the single instance
possibly protect / synchronize this method to ensure that it will work in a multi-threaded program

Singleton sequence diagram

Singleton example
consider a singleton class RandomGenerator that generates random numbers
public class RandomGenerator { private static RandomGenerator gen = new RandomGenerator(); public static RandomGenerator getInstance() { return gen; } private RandomGenerator() {}

public double nextNumber() { return Math.random(); }

}

possible problem: always creates the instance, even if it isn't used

Singleton example 2
variation: don't create the instance until needed
// Generates random numbers. public class RandomGenerator { private static RandomGenerator gen = null; public static RandomGenerator getInstance() { if (gen == null) gen = new RandomGenerator(); return gen; } }

What could go wrong with this version?

Singleton example 3
variation: solve concurrency issue by locking
// Generates random numbers. public class RandomGenerator { private static RandomGenerator gen = null; public static synchronized RandomGenerator getInstance() { if (gen == null) gen = new RandomGenerator(); return gen; }

Is anything wrong with this version?

Singleton example 4
variation: solve concurrency issue without unnecessary locking
// Generates random numbers. public class RandomGenerator { private static RandomGenerator gen = null; public static RandomGenerator getInstance() { if (gen == null) { synchronized (RandomGenerator.class) { // must test again -- can you see why? if (gen == null) gen = new RandomGenerator(); } } return gen; }

Singleton example
consider a class RandomGenerator that generates random numbers
public class RandomGenerator { private static RandomGenerator gen;

public static RandomGenerator getInstance() { return gen; } private RandomGenerator() {}

public double nextNumber() { return Math.random(); }

:: How does it Work?

The Factory pattern returns an instance of one of several possible classes depending on the data provided to it.

Here, x is a base class and classes xy and xz are derived from it. The Factory is a class that decides which of these subclasses to return depending on the arguments you give it. The getClass() method passes in some value abc, and returns some instance of the class x. Which one it returns doesn't matter to the programmer since they all have the same methods, but different implementations.

The Factory Pattern

:: The Base Class

Let's consider a simple case where we could use a Factory class. Suppose we have an entry form and we want to allow the user to enter his name either as firstname lastname or as lastname, firstname. Lets make the assumption that we will always be able to decide the name order by whether there is a comma between the last and first name.

class Namer { //a simple class to take a string apart into two names protected String last; //store last name here protected String first; //store first name here public String getFirst() { return first; //return first name } public String getLast() { return last; //return last name } }

The Factory Pattern

:: The First Derived Class
In the FirstFirst class, we assume that everything before the last space is part of the first name.

class FirstFirst extends Namer { public FirstFirst(String s) { int i = s.lastIndexOf(" "); //find sep space if (i > 0) { first = s.substring(0, i).trim(); //left is first name last =s.substring(i+1).trim(); //right is last name } else { first = // put all in last name last = s; // if no space } } }

The Factory Pattern

:: The Second Derived Class
In the LastFirst class, we assume that a comma delimits the last name.

class LastFirst extends Namer { //split last, first public LastFirst(String s) { int i = s.indexOf(","); //find comma if (i > 0) { last = s.substring(0, i).trim(); //left is last name first = s.substring(i + 1).trim(); //right is first name } else { last = s; // put all in last name first = ""; // if no comma } } }

The Factory Pattern

:: Building the Factory
The Factory class is relatively simple. We just test for the existence of a comma and then return an instance of one class or the other.

class NameFactory { //returns an instance of LastFirst or FirstFirst //depending on whether a comma is found public Namer getNamer(String entry) { int i = entry.indexOf(","); //comma determines name order if (i>0) return new LastFirst(entry); //return one class else return new FirstFirst(entry); //or the other } }

The Factory Pattern

:: Using the Factory
NameFactory nfactory = new NameFactory(); String sFirstName, sLastName; . private void computeName() { //send the text to the factory and get a class back namer = nfactory.getNamer(entryField.getText()); //compute the first and last names using the returned class sFirstName = namer.getFirst(); sLastName = namer.getLast(); }

The Factory Pattern

:: When to Use a Factory Pattern

You should consider using a Factory pattern when: A class cant anticipate which kind of class of objects it must create. A class uses its subclasses to specify which objects it creates. You want to localize the knowledge of which class gets created. There are several similar variations on the factory pattern to recognize: The base class is abstract and the pattern must return a complete working class. The base class contains default methods and is only subclassed for cases where the default methods are insufficient. Parameters are passed to the factory telling it which of several class types to return. In this case the classes may share the same method names but may do something quite different.

The Abstract Factory Pattern

:: How does it Work?

The Abstract Factory pattern is one level of abstraction higher than the factory pattern. This pattern returns one of several related classes, each of which can return several different objects on request. In other words, the Abstract Factory is a factory object that returns one of several factories. One classic application of the abstract factory is the case where your system needs to support multiple look-and-feel user interfaces, such as Windows, Motif or Macintosh: You tell the factory that you want your program to look like Windows and it returns a GUI factory which returns Windows-like objects. When you request specific objects such as buttons, check boxes and windows, the GUI factory returns Windows instances of these visual interface components.

The Abstract Factory Pattern

:: Consequences of Abstract Factory

One of the main purposes of the Abstract Factory is that it isolates the concrete classes that are generated. The actual class names of these classes are hidden in the factory and need not be known at the client level at all. Because of the isolation of classes, you can change or interchange these product class families freely. Since you generate only one kind of concrete class, this system keeps you for inadvertently using classes from different families of products. While all of the classes that the Abstract Factory generates have the same base class, there is nothing to prevent some derived classes from having additional methods that differ from the methods of other classes.

DAY - 5

APPLICATION ARCHIETECTURE
N-TIER ARCHITECTURE

WHAT IS N-TIER ARCHIETECTURE

Firstly, what is n-Tier architecture? N-Tier architecture refers to the architecture of an application that has at least 3 "logical" layers -- or parts -- that are separate. Each layer interacts with only the layer directly below, and has specific function that it is responsible for.

Presentation Tier

Caching Service Tier

Application Server Tier

Integration Service Tier

Data Tier (Back-end Services)

WHY N-TIER ARCHIETECTURE

Because each layer can be located on physically different servers with only minor code changes, hence they scale out and handle more server load. Also, what each layer does internally is completely hidden to other layers and this makes it possible to change or update one layer without recompiling or modifying other layers.

Project Design Pattern

HARDWARE AND SOFTWARE

HARDWARE

SOFTWARE

Software Interface
FRONT END
We have implemented JavaScript for all the Client side validations. Client side JavaScript is designed to reside inside HTML document & ensure they run properly. It is object based, event driven, platform independent. These are important parts of any Web application to implement Client side Validations and the invalid data is not submitted. The form is not submitted until user fills in correct data. It is extremely useful to restrict

mistakes by user.

BACK END
We have used My SQL. MySQL provides solution for major database tech. - Large database and space management. - Many concurrent database users. - High transaction processing requirement - High Availability efficient/effective

- Industry accepted standards

- Manageable security - Portability

LIMITATIONS

LIMITATIONS
The most notable features which were not implemented in the system are table

management and a more intuitive order item notes interface.

These features were not implemented because of time constraints. The process of removing features from software when time is running out is known as feature cutting. A drawback of removing features at such a late stage in the project is that some time will probably have already been wasted on the design or partial implementation of these features.

FUTURE SCOPE

FUTURE SCOPE
The future of this project depends on whether the author has enough spare

time over the next few months to continue with the development. The author
feels that those last few remaining features would round off the system. If the author was to try to sell this system then more system testing would have to be done, in particular a more comprehensive real-world testing environment would have to be adopted along with some real-world usage. Multiple concurrent users would be common in real-world usage but have been difficult to test for considering there was only one tester involved in this project.

This type of system would benefit from being sold via Software as a Service
(SaaS). SaaS would allow support would be provided for the hardware in case of a system failure and for the software in case of newly found bugs, in return for a subscription fee.

Screen Shots

HOME

User Register

Login

User Home Page

Complaint Report

Crime Report

Missing Person

View Missing Persons Details

Chat

Chat Start

Admin Home Page

Criminal Report

All Complaint Report

Mail

Most Wanted Person

Upload Photos

View & Delete missing Person

View & delete most wanted persons

View & Delete Hot News

View User Complaint