Crime File abstract.pdf (Size: 89.84 KB / Downloads: 972)
Crime File System is a system used to report crimes. This project will be done using VB 6.0 as front end, and MS Access as back end. It can used to report crime. This project is mainly useful for police stations. This system will help to manage all the activities in a police station using computers. Currently all the works are done manually, by computerizing all the activities inside a police station can be managed easily and effectively.
The modules involved in this project are:
Â¢ Login for user and admin
Â¢ Complaint registration
Â¢ View complaint status
Â¢ Criminal register management
Â¢ FIR Management
Â¢ Case History Details management
Â¢ Managing Postmortem details
Â¢ Prisoners register management
Â¢ Manage list about most wanted criminals
This includes Administrator and User login. There will be a username and password to login into the system to use all the facilities.
2. COMPLAINT REGISTRATION
This module helps to register the details about the crime. This is done by entering some details, such as incident details, Victim details, crime details etc
3. VIEW COMPLAINT STATUS
This module allows us to view the status of the complaint that you have registered earlier.
4. CRIMINAL REGISTER MANAGEMENT
Here we can have the facility to view the details of the criminals. The administrator can add new criminal's details and save it in a database. This can be done by entering details such as criminal number, age, occupation, type of crime etc.
5. FIR MANGEMENT
This module allows viewing the First Information Report of all the crimes that took place at recent years. The administrator can enter FIR information and save it in a database.
1. CASE HISTORY DETAILS MANAGEMENT
Here we can view the details of the case, date of occurrence, the type of crime and place of occurrence etc..
7. MANAGING POSTMORTEM DETAILS
This module helps to view the postmortem details of a person. The details such as date of death cause of death, name of the doctor etc.
8. PRISONER REGISTER MANGEMENT
This module helps the administrator as well as the user to store, view and manage the details of the past and present prisoners.
9. MANAGE THE LIST OF MOST WANTED CRIMINALS
This is an additional feature added to this Software, which helps us to make a quick search about the most wanted criminals. This helps to always keep track of and identify a person quickly, who is a most wanted criminal.
2. SYSTEM ANALYSIS
2.1 Introduction to System Analysis
System analysis is a process of gathering and interpreting facts, diagnosing problems and the information to recommend improvements on the system. It is a problem solving activity that requires intensive communication between the system users and system developers. System analysis or study is an important phase of any system development process. The system is studied to the minutest detail and analyzed. The system analyst plays the role of the interrogator and dwells deep into the working of the present system. The system is viewed as a whole and the input to the system are identified. The outputs from the organizations are traced to the various processes. System analysis is concerned with becoming aware of the problem, identifying the relevant and decisional variables, analyzing and synthesizing the various factors and determining an optimal or at least a satisfactory solution or program of action.
A detailed study of the process must be made by various techniques like interviews, questionnaires etc. The data collected by these sources must be scrutinized to arrive to a conclusion. The conclusion is an understanding of how the system functions. This system is called the existing system. Now the existing system is subjected to close study and problem areas are identified. The designer now functions as a problem solver and tries to sort out the difficulties that the enterprise faces. The solutions are given as proposals. The proposal is then weighed with the existing system analytically and the best one is selected. The proposal is presented to the user for an endorsement by the user. The proposal is reviewed on user request and suitable changes are made. This is loop that ends as soon as the user is satisfied with proposal.
Preliminary study is the process of gathering and interpreting facts, using the information for further studies on the system. Preliminary study is problem solving activity that requires intensive communication between the system users and system developers. It does various feasibility studies. In these studies a rough figure of the system activities can be obtained, from which the decision about the strategies to be followed for effective system study and analysis can be taken.
2.2 Existing System
Â¢ Lack of security of data.
Â¢ More man power.
Â¢ Time consuming.
Â¢ Consumes large volume of pare work.
Â¢ Needs manual calculations.
Â¢ No direct role for the higher officials.
2.3 Proposed System
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.
Â¢ Security of data.
Â¢ Ensure data accuracy's.
Â¢ Proper control of the higher officials.
Â¢ Minimize manual data entry.
Â¢ Minimum time needed for the various processing.
Â¢ Greater efficiency.
Â¢ Better service.
Â¢ User friendliness and interactive.
Â¢ Minimum time required.
2.3.1. FEASIBILITY STUDY
Feasibility study is made to see if the project on completion will serve the purpose of the organization for the amount of work, effort and the time that spend on it. Feasibility study lets the developer foresee the future of the project and the usefulness. A feasibility study of a system proposal is according to its workability, which is the impact on the organization, ability to meet their user needs and effective use of resources. Thus when a new application is proposed it normally goes through a feasibility study before it is approved for development.
The document provide the feasibility of the project that is being designed and lists various areas that were considered very carefully during
the feasibility study of this project such as Technical, Economic and Operational feasibilities. The following are its features:
A. TECHNICAL FEASIBILITY
The system must be evaluated from the technical point of view first. The assessment of this feasibility must be based on an outline design of the system requirement in the terms of input, output, programs and procedures. Having identified an outline system, the investigation must go on to suggest the type of equipment, required method developing the system, of running the system once it has been designed.
Technical issues raised during the investigation are:
> Does the existing technology sufficient for the suggested one
> Can the system expand if developed
The project should be developed such that the necessary functions and performance are achieved within the constraints. The project is developed within latest technology. Through the technology may become obsolete after some period of time, due to the fact that never version of same
software supports older versions, the system may still be used. So there are minimal constraints involved with this project. The system has been developed using Java the project is technically feasible for development.
B. ECONOMIC FEASIBILITY
The developing system must be justified by cost and benefit. Criteria to ensure that effort is concentrated on project, which will give best, return at the earliest. One of the factors, which affect the development of a new system, is the cost it would require.
The following are some of the important financial questions asked during preliminary investigation:
> The costs conduct a full system investigation.
> The cost of the hardware and software.
> The benefits in the form of reduced costs or fewer costly errors.
Since the system is developed as part of project work, there is no manual cost to spend for the proposed system. Also all the resources are already available, it give an indication of the system is economically possible for development.
C. BEHAVIORAL FEASIBILITY
This includes the following questions:
Â¢ Is there sufficient support for the users
Â¢ Will the proposed system cause harm
The project would be beneficial because it satisfies the objectives when developed and installed. All behavioral aspects are considered carefully and conclude that the project is behaviorally feasible.
3. SYSTEM DESIGN
Introduction to System Design
Design is the first step into the development phase for any engineered product or system. Design is a creative process. A good design is the key to effective system. The term "design" is defined as "the process of applying various techniques and principles for the purpose of defining a process or a system in sufficient detail to permit its physical realization". It may be defined as a process of applying various techniques and principles for the purpose of defining a device, a process or a system in sufficient detail to permit its physical realization. Software design sits at the technical kernel of the software engineering process and is applied regardless of the development paradigm that is used. The system design develops the architectural detail required to build a system or product. As in the case of any systematic approach, this software too has undergone the best possible design phase fine tuning all efficiency, performance and accuracy levels. The design phase is a transition from a user oriented document to a document to the programmers or database personnel.
System design goes through two phases of development: Logical and Physical Design.
3.1 Input design
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:
o What data should be given as input o How the data should be arranged or coded o The dialog to guide the operating personnel in providing input. o Methods for preparing input validations and steps to follow when error occur.
3.2 Output Design
A quality output is one, which meets the requirements of the end user and presents the information clearly. 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 system's 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.
3.4 Database Design
A database is an organized mechanism that has the capability of storing information through which a user can retrieve stored information in an effective and efficient manner. The data is the purpose of any database and must be protected.
The database design is a two level process. In the first step, user requirements are gathered together and a database is designed which will meet these requirements as clearly as possible. This step is called Information Level Design and it is taken independent of any individual DBMS.
In the second step, this Information level design is transferred into a design for the specific DBMS that will be used to implement the system in question. This step is called Physical Level Design, concerned with the characteristics of the specific DBMS that will be used. A database design runs parallel with the system design. The organization of the data in the database is aimed to achieve the following two major objectives.
Normalization is the process of decomposing the attributes in an application, which results in a set of tables with very simple structure. The
purpose of normalization is to make tables as simple as possible. Normalization is carried out in this system for the following reasons.
Â¢ To structure the data so that there is no repetition of data , this helps in saving.
Â¢ To permit simple retrieval of data in response to query and report request.
Â¢ To simplify the maintenance of the data through updates, insertions, deletions.
Â¢ To reduce the need to restructure or reorganize data which new application requirements arise.
RELATIONAL DATABASE MANAGEMENT SYSTEM (RDBMS):
A relational model represents the database as a collection of relations. Each relation resembles a table of values or file of records. In formal relational model terminology, a row is called a tuple, a column header is called an attribute and the table is called a relation. A relational database consists of a collection of tables, each of which is assigned a unique name. A row in a tale represents a set of related values.
RELATIONS, DOMAINS & ATTRIBUTES:
Â¢ A table is a relation. The rows in a table are called tuples. A tuple is an ordered set of n elements. Columns are referred to as attributes. Relationships have been set between every table in the database. This ensures both Referential and Entity Relationship Integrity. A domain D is a set of atomic values. A common method of specifying a domain is to specify a data type from which the data values forming the domain are drawn. It is also useful to specify a name for the domain to help in interpreting its values. Every value in a relation is atomic, that is not decomposable.
Table relationships are established using Key. The two main keys of prime importance are Primary Key & Foreign Key. Entity Integrity and Referential Integrity Relationships can be established with these keys. Entity Integrity enforces that no Primary Key can have null values. Referential Integrity enforces that no Primary Key can have null values.
Â¢ Referential Integrity for each distinct Foreign Key value, there must exist a matching Primary Key value in the same domain. Other key are Super Key and Candidate Keys.
Â¢ Relationships have been set between every table in the database. This ensures both Referential and Entity Relationship Integrity.
As the name implies, it denoted putting things in the normal form. The application developer via normalization tries to achieve a sensible organization of data into proper tables and columns and where names can be easily correlated to the data by the user. Normalization eliminates repeating groups at data and thereby avoids data redundancy which proves to be a great burden on the computer resources. These includes:
Normalize the data.
Choose proper names for the tables and columns.
Choose the proper name for the data.
First Normal Form:
The First Normal Form states that the domain of an attribute must include only atomic values and that the value of any attribute in a tuple must be a single value from the domain of that attribute. In other words 1NF disallows "relations within relations" or "relations as attribute values within tuples". The only attribute values permitted by 1NF are single atomic or indivisible values.
The first step is to put the data into First Normal Form. This can be donor by moving data into separate tables where the data is of similar type
in each table. Each table is given a Primary Key or Foreign Key as per requirement of the project. In this we form new relations for each nonatomic attribute or nested relation. This eliminated repeating groups of data.
A relation is said to be in first normal form if only if it satisfies the constraints that contain the primary key only.
Second Normal Form:
According to Second Normal Form, For relations where primary key contains multiple attributes, no nonkey attribute should be functionally dependent on a part of the primary key.
In this we decompose and setup a new relation for each partial key with its dependent attributes. Make sure to keep a relation with the original primary key and any attributes that are fully functionally dependent on it. This step helps in taking out data that is only dependant on apart of the key.
A relation is said to be in second normal form if and only if it satisfies all the first normal form conditions for the primary key and every non-primary key attributes of the relation is fully dependent on its primary key alone.
Third Normal Form:
According to Third Normal Form, Relation should not have a nonkey attribute functionally determined by another nonkey attribute or by a set of
nonkey attributes. That is, there should be no transitive dependency on the primary key.
In this we decompose and set up relation that includes the nonkey attributes that functionally determines other nonkey attributes. This step is taken to get rid of anything that does not depend entirely on the Primary
A relation is said to be in third normal form if only if it is in second normal form and more over the non key attributes of the relation should not be depend on other non key attribute.
4 SYSTEM IMPLEMENTATION
4.1 About Language The Control Properties
Before writing an event procedure for the control to response to a user's input, you have to set certain properties for the control to determine its appearance and how it will work with the event procedure. You can set the properties of the controls in the properties window or at runtime. Handling some of the common controls
The Text Box
The text box is the standard control for accepting input from the user as well as to display the output. It can handle string (text) and numeric data but not images or pictures. String in a text box can be converted to a numeric data by using the function Val(text). The following example illustrates a simple program that processes the input from the user.
10. IMPLEMENTATION AND TESTING
Testing is a process of executing a program with the interest of finding an error. A good test is one that has high probability of finding the yet undiscovered error. Testing should systematically uncover different classes of errors in a minimum amount of time with a minimum amount of efforts. Two classes of inputs are provided to test the process
1. A software configuration that includes a software requirement
specification, a design specification and source code.
2. A software configuration that includes a test plan and
procedure, any testing tool and test cases and their expected results.
Testing is divided into several distinct operations:
1. Unit Testing
Unit test comprises of a set tests performed by an individual program prior to the integration of the unit into large system. A program unit is usually the smallest free functioning part of the whole system. Module unit testing should be as exhaustive as possible to ensure that each representation handled by each module has been tested. All the units that makeup the system must be tested independently to ensure that they work as required.
During unit testing some errors were raised and all of them were rectified and handled well. The result was quiet satisfactory and it worked well.
2. Integration Testing
Integration testing is a system technique for constructing the program structure while at the same time conducting tests to uncover errors associated with interfacing. The objective is to take unit tested modules and build a program structure that has been dictated by design. Bottom-up integration is the traditional strategy used to integrate the components of a software system into functioning whole. Bottom-up integration consists
of unit test followed by testing of the entire system. A sub-system consists of several modules that communicated with other defined interface.
The system was done the integration testing. All the modules were tested for their compatibility with other modules .They test was almost successful. All the modules coexisted very well, with almost no bugs. All the modules were encapsulated very well so as to not hamper the execution of other modules.
3. Validation Testing
After validation testing, software is completely assembled as a package, interfacing errors that have been uncovered and corrected and the final series of software test; the validation test begins. Steps taken during software design and testing can greatly improve the probability of successful integration in the larger system. System testing is actually a series of different tests whose primary purpose is to fully exercise the compute -based system.
4. Recovery Testing
It is a system that forces the software to fail in a variety of ways and verifies that the recovery is properly performed.
5. Security Testing
It attempts to verify that protection mechanisms built into a system will in fact protect it from improper penetration. The system's security must of course be tested from in vulnerability form frontal attack.
6. Stress Testing
Stress tools are designed to confront programs with abnormal situations. Stress testing executes a system in a manner that demands resources in abnormal quantity and volume.
7. Black Box Testing
Black box testing is done to find out the following information as shown in below:
1. Incorrect or missing functions.
2. Interface errors.
3. Errors or database access.
4. Performance error.
5. Termination error.
The mentioned testing is carried out successfully for this application according to the user's requirement specification. 8. Test Data Output
After preparing test data, the system under study is tested using the test data. While testing the system using test data, errors are again uncovered and corrected by using above testing and corrections are also noted for future use.