Documente Academic
Documente Profesional
Documente Cultură
DECLARATION
I, Johnson Joseph, do hereby declare that the project titled E - COP : ONLINE
COMPLIANT REGISTRATION PORTAL is a record of work carried out under the
guidance of Ms Jissa Maria Jose, Assistant Professor, Department of Computer Applications,
Christ College, Puliyanmala as per the requirement of the curriculum of Bachelor of
Computer Applications program of Mahatma Gandhi University, Kottayam. Further, I also
declare that this report has not been submitted, full or part thereof, in any University /
Institution for the award of any Degree / Diploma.
ACKNOWLEDGEMENT
The success of any project depends largely on the encouragement and guidelines of
many others. I would like to take this opportunity to express my gratitude to those people
who have been instrumental in the successful completion of this project.
First and foremost, I give all glory, honour and praise to God Almighty who gave me
wisdom and enabled me to complete the project successfully.
I also express sincere thanks, from the bottom of my heart, to my parents for their
encouragement and support in all my endeavours and especially in this project.
Words are inadequate to express my deep sense of gratitude to Rev. Dr. Alex Louis
CMI, Principal, Christ College, Puliyanmala for allowing me to utilize all the facilities of
our college and also for his encouragement.
I own a particular debt of gratitude to my internal project guide, Ms. Jissa Maria
Jose, Department of Computer Science, Christ College, Puliyanmala for all the necessary
help and support that she has extend to me. Her valuable suggestions, corrections and the
sincere efforts to accomplish my project even under a tight time schedule were crucial in the
successful completion this project.
I extend my sincere thanks to all of our teachers and non-teaching staff of Christ
College, Puliyanmala for the knowledge they have imparted to me over the last two years.
I would also like to express my appreciation to all my friends for their comments, help
and support.
TABLE OF CONTENTS
1. Introduction……………..………………………………………………………….06
1.1 Project overview…………………………………………………….07
2. System analysis………………………………………………………………….08
2.1 Preliminary analysis………………………………………………09
2.2 Existing system………………………………………………………09
2.3 Proposed system……………………..………………………….….10
2.4 Feasibility study………………………………………………….….10
2.4.1 Economical feasibility…………….,.….…………….12
2.4.2 Technical feasibility…………………………………….13
2.4.3 Behavioural feasibility………………………………..14
2.4.4 Operational feasibility…………………………….....15
2.5 Advantages of proposed system……………………………16
3. System specification……………………….………………………………… 17
3.1 Software specification…………………………………… 18
3.2 Hardware specification…………………………………. 18
3.3 About the developing tools...………………………… 19
4. System design………………………………………………………………………21
4.1 Architectural design…………………………….………… 25
4.2 Input design…………………………………….……………… 25
4.3 Modules and description…………………………………26
4.4 Output design…………………………………………………. 28
4.5 Database design……………………………………………… 28
4.6 User interface design……………………………………… 29
5. Database design…………………………………………………………………...30
5.1 Tables………………………………………………………….…….31
5.2 Data flow diagrams………………………………………… 33
6. System testing………………….…………………………………………………. 44
6.1 Unit Testing………………………………………………………46
6.2 Integration Testing……………………………………………47
6.3 Validation Testing…………………………………………… 48
6.4 System Testing…………………………….……………………49
6.5 User Acceptance Testing………………………………… 50
7. System implementation…………………………………………………………51
7.1 Implementation…………………………………………………. 52
7.2 Problem statement………………………………………………52
7.3 Problem description……………………………………………52
7.4 Feature of project………………………………………………. 52
8. Future enhancement……………………………………………………………… 53
10. Conclusion…………………………………………………………………………….55
11. Bibliography………………………………………………………………………….57
11. Appendix……………………………………………………………………………...59
a. Sample Screens…………………………………………………… 60
b. Coding……………………………………………………………….....66
ABSTRACT
INTRODUCTION
The Online Compliant Registration System can be entered using a username and a
password. It is accessible to all the users. They can add the data into the database. The data
can be retrieved easily.
This system has the following objectives: to maintain simple database, to maintain
easy user interface that is user friendly and attractive and to maintain the speed of system
functionality.
SYSTEM ANALYSIS
In order to design the proposed system, the requirements should be known and
arranged in such a way that the designing become easier. System Analysis is the process in
which the requirements for the proposed system is collected, corrected, and organized in an
effective manner. In System Analysis, the analyst collects the requirements from the Users
and carefully studies them. After that the skeleton-the structure and the way of development
is produced. Care must be taken while analysing the existing system as well as the proposed
system. Understand the needs and requirements is very important, because the proposed
system is evaluated based on the analysis phase. The system must satisfy the requirements in
the analysis phase. The requirements are fulfilled by computerized method.
All projects are feasible when given unlimited resources and infinite time. It is both
necessary and prudent to evaluate the feasibility of a project at the earliest possible time. A
feasibility study is not warranted for systems in which economic justification is obvious,
technical risk is low, few legal problems are expected and no reasonable alternative exists.
An estimate is made of whether the identified user needs may be satisfied using current
software and hardware technologies. The study will decide if the proposed system will be
cost effective from the business point of view and if it can be developed in the given existing
budgetary constraints. The feasibility study should be relatively cheap and quick. The result
should inform the decision of whether to go ahead with a more detailed analysis.
Economic Feasibility
Technical Feasibility
Behavioural Feasibility
Operational Feasibility
This project aims at reducing time, effort and cost. The system is developed under
optimal expenses with the hardware and software. The developed system is available free of
cost. Anybody can get the benefit of the system by simply using it as a service. There is no
additional cost for using or implementing the system. It can be used in windows based
system, and need not alter the current system configurations. This makes the system feasible
economically. Besides it is good economic to insist in such a kind of software from the
project manager’s point of view as the benefits over weighs the cost. The resources needed to
run the above project should be less in cost, easily available and highly reliable. This is a cost
effective project because of its accuracy, speed and user friendly nature.
A study of function, performance and constraints may improve the ability to create an
acceptable system. Technical feasibility is frequently the most difficult area to achieve at the
stage of product engineering process.
Considering that are normally associated with the technical feasibility include
Development risk, Resource availability, Technology. Technical feasibility study deals with
the hardware as well as software requirements. The scope was whether the work for the
project is done with the current equipment and the existing software technology has to be
examined in the feasibility study. The outcome was found to be positive.
Project requirement system must be functional and multi user one should be based on
specific technology the system under study must be practical and platform independent. It
should be compactable with all kind of existing system in industry and should not provide
any overhead to user. Implementation of existing system does not require changing of the
existing configure of the system. The platform what is needed for development is easily
available. So the new system is technically feasible.
An estimate should be made of how strong a reaction the user staff is likely to have
toward the development of a computerized system. It is common knowledge the computer
installations have something to do understandable that the introduction of a candidate system
requires special effort to educate, sell and train the staff on new ways of considering business.
The behaviour of the system plays an important role in the number of users accessing the
software. This is due to the fact that is a simple software is very easy and convenient to use.
Anyone with the basic knowledge of computer can easily use the system and get its
benefits. Additional training is not required to work with it. This means that the system is
feasible behaviourally.
The present system is easily understandable. The maintenance and working of the new
system requires less human effort and is beneficiate to the organization. Our software is
based on the requirement specification given by the user and is user friendly, based on the
requirement specification given by users. The operation of this software is very simple.
The system excludes the use of paper work by managing all the book information
electronically.
This web application allows the user to deal with the great ease of environment.
Automation.
SYSTEM SPECIFICATION
RAM: 8 GB
HYPERTEXT PREPROCESSOR
Introduction
PHP is a computer scripting language originally designed for producing dynamic web pages.
It is for sever side scripting but can be used from command line interface or in standalone
graphical applications. While PHP was originally created by Rasmus Lerdorf in 1995, the
main implementation of PHP is now produced by the PHP group and servers as the defector
standard for PHP as there is no formal specification. Released under PHP License, the free
software Foundation considers it to be free software.
PHP is a widely-used general purpose scripting language that is especially suited for web
development and can be embedded into HTML. It generally runs on a web server, taking
PHP codes as its input and creating web pages as output. It can be deployed on most web
servers and on almost every operating system and platform free of charge. PHP is installed on
more than 20 million website and 1 million web servers. It is also the most popular Apache
module among computers using Apache as web server. The most recent major release of PHP
was version 5.2.6 on May 1, 2008.
Microsoft SQL Server 2008 provide following new features for database developers.
Increase the precision of storing and managing DATE and TIME information.
Store semi-structured and sparsely populated sets of data efficiently, using Sparse
Columns.
Create large User-Defined Types and User-Defined Aggregates greater than 8 KB.
Pass large amounts of data easily to functions or procedures using new Table-
Value Parameters.
Model hierarchical data, such as org charts, or files and folders, using the new
Hierarchy Id data type.
Manage files and documents efficiently with full SQL Server security and
transaction support, using the powerful new FILESTREAM data type.
Experience faster queries and reporting with Grouping Sets through powerful
ANSI standards-compliant extensions to the GROUP BY clause
SYSTEM DESIGN
SYSTEM DESIGN
Design phase is the phase in which the detailed design of the system selected in the
study phase is accomplished and the user oriented performance specifications is converted in
to technical specifications. The design of a system is correct if a system builds according to
the requirements of that system. The purpose of the design phase is to produce the current
designs. The normal procedure is to define the output required from the system based on the
user requirements. Once this is defined, in details, the input is worked back and appropriate
codes are designed for easy handling of various types of files. Design goes to logical and
physical system of development. Logical Design reviews present physical system, prepares
input and output specifications, make edit, security, control specifications and the detail of
the implementation. A software design is a meaningful engineering representation of some
software product that is to be built. A design can be traced to the customer's requirements and
can be assessed for quality against predefined criteria. In the software engineering context,
design focuses on four major areas of concern: data, architecture, interfaces and components.
The main aim of a system design is to identify the modules that should be in the system, and
the specification of these modules and how they interact with each other to produce the
desired results. Various design specification models are:
Data design – Created by transforming the analysis information model (data dictionary
and ERD) into data structures required to implement the software. Part of the data
design may occur in conjunction with the design of software architecture. More detailed
data design occurs as each software component is designed.
Architectural design - Defines the relationships among the major structural elements
of the software, the “design patterns” than can be used to achieve the requirements that
have been defined for the system, and the constraints that affect the way in which the
architectural patterns can be applied. It is derived from the system specification, the
analysis model, and the subsystem interactions defined in the analysis model (DFD).
Interface design - Describes how the software elements communicate with each other,
with other systems, and with human users; the data flow and control flow diagrams
provide much of the necessary information required.
1. The design process should not suffer from tunnel vision – A good designer should
consider alternative approaches. Judging each based on the requirements of the problem,
the resources available to do the job and any other constraints.
2. The design should be traceable to the analysis model – because a single element of the
design model often traces to multiple requirements, it is necessary to have a means of
tracking how the requirements have been satisfied by the model.
3. The design should not reinvent the wheel – Systems are constructed using a set of design
patterns, many of which may have likely been encountered before. These patterns
should always be chosen as an alternative to reinvention. Time is short and resources are
limited! Design time should be invested in representing truly new ideas and integrating
those patterns that already exist.
4. The design should minimise intellectual distance between the software and the problem
as it exists in the real world – That is, the structure of the software design should
(whenever possible) mimic the structure of the problem domain.
5. The design should exhibit uniformity and integration – a design is uniform if it appears
that one person developed the whole thing. Rules of style and format should be defined
for a design team before design work begins. A design is integrated if care is taken in
defining interfaces between design components.
6. The design should be structured to degrade gently, even with bad data, events, or
operating conditions are encountered – Well-designed software should never “bomb”. It
should be designed to accommodate unusual circumstances, and if it must terminate
processing, do so in a graceful manner.
elements of the design have been addressed before worrying about the syntax if the
design model.
8. Design is not coding, coding is not design – Even when detailed designs are created for
program components, and the level of abstraction of the design model is higher than
source code. The only design decisions made of the coding level address the small
implementation details that enable the procedural design to be coded.
When these design principles are properly applied, the design exhibits both external
and internal quality factors. External quality factors are those factors that can readily be
observed by the user, (e.g. speed, reliability, correctness, usability). Internal quality factors
relate to the technical quality (which is important to the software engineer) more so the
quality of the design itself. To achieve internal quality factors, the designer must understand
basic design concepts.
Methods for performing input validations and steps to follow when error occur.
The input screens are displayed in a way that the user can understand entries very
easily. Proper validation and controlling of input data will reduce the chance of errors. All
major operations are done only after checking the results of confirmation messages. This
makes the system more reliable and user friendly.
1. LOGIN MODULE
The registered user (admin/police/public) can login to the system.
2. REGISTER MODULE
This module is used for entering details.
3. ADD DISTRICT MODULE
This module is used for adding districts.
4. ADD STATION MODULE
This module is used to add station details.
5. ADD COMPLAINT MODULE
In this module, the public can register their complaint.
6. COMPLAINT DETAILS MODULE
In this module, all the complaint details can be viewed .The admin and
police can give review for the corresponding complaint.
7. REVIEW DETAILS MODULE
This module is used to give response to the complaint that have been
registered.
When designing output, the system analyst must accomplish things like, to determine
what information to be present, to decide whether to display or print the information and
select the output medium to distribute the output to intended recipients. External outputs are
those, whose destination will be outside the organization and which require special attention
as the project image of the organization. Internal outputs are those; whose destination is
within the organization. It is to be carefully designed, as they are the user’s main interface
with the system. Interactive outputs are those, which the user uses in communication directly
with the computer.
DATABASE DESIGN
5.1 TABLES
LOG IN (adminlog)
Field Name Datatype Constraints
adid int primary key
username varchar(50) not null
pwd varchar(20) not null
role varchar(20) not null
DISTRICT (district)
Field Name Datatype Constraints
did int primary key
dname varchar(50) not null
REGISTER DETAILS(register)
Field Name Datatype Constraints
regid int primary key
fname varchar(50) not null
lname Varchar(50) not null
adds Varchar(80) not null
place Varchar(80) not null
pin int not null
dis Varchar(20) not null
ph Bigint(10) not null
gen Varchar(10) not null
uid int not null
email Varchar(50) not null
A DFD shows what kinds of information will be input to and output from the system,
where the data will come from and go to, and where the data will be stored. It does not show
information about the timing of processes or information about whether processes will
operate in sequence or in parallel. It is common practice to draw the context-level data flow
diagram first, which shows the interaction between the system and external agents which act
as data sources and data sinks. On the context diagram the system's interactions with the
outside world are modelled purely in terms of data flows across the system boundary. The
context diagram shows the entire system as a single process, and gives no clues as to its
internal organization.
This context-level DFD is next "exploded", to produce a Level 1 DFD that shows
some of the detail of the system being modelled. The Level 1 DFD shows how the system is
divided into sub-systems (processes), each of which deals with one or more of the data flows
to or from an external agent, and which together provide all of the functionality of the system
as a whole. It also identifies internal data stores that must be present in order for the system to
do its job, and shows the flow of data between the various parts of the system. Data flow
diagrams were proposed by Larry Constantine, the original developer of structured design,
based on Martin and Estrin's "data flow graph" model of computation.
The lower level diagrams are called ‘First Level DFDs’, ‘Second Level DFDs’, and so
on. Because the nature complexity of system varies, a specific number of levels of DFDs
cannot be fixed. Very complex data flow diagrams cause difficulty to understanding hem. On
the other hand, if they are under exploded, errors or mission could occur.
DATA FLOW
Data in a system move direction that is from origin to destination. The data flow is a
packet of data indicating the movements of data within the system. Data flow must be inputs
to or outputs from processes. They must contain data and all data flows should be labeled
indicating what data is flowing.
PROCESS
EXTERNAL ENTITIES
DATA STORE
Data store can be considered as the memory of the system. Any place that data
accumulate is the data store. Data flow diagrams do not specify the type of physical storage.
The data in the data store are stored or referenced by a process in the system. The data store
must have a label, which is placed between the two parallel lines, which should clearly
identify what the data store contains as a class object.
SYSTEM TESTING
SYSTEM TESTING
Software testing is a critical element of software quality assurance and represents the
ultimate reviews of specification, design and coding. Testing presents an interesting
anomaly for the software. Testing is vital to the success of the system. Errors can be injected
at any stage during development. System testing makes a logical assumption that if all
the parts of the system are correct, the goal will be successfully achieved.
During testing, the program to be tested is executed with set of test data and
the output of the program for the test data is evaluated to determine if the program
is performing as expected. A series of testing are performed for the proposed system
before the system is ready for user acceptance testing. Another reason for system testing
is its utility as a user-oriented vehicle before implementation.
TYPES OF TESTING
Integration Testing
Validation Testing
System Testing
On the other hand, some software developers do not use testers for their program
rather developers get normal and intended users to test their program. They do not just
implement the program to everyone though, they implement the program in restricted
manner so that they can monitor to software’s performance and make the necessary
adjustments even before the software is released for general public. The testing stage even
expands to the idea of implementing the software in beta testing just to make sure it can
withstand multiple users at the same time.
SYSTEM IMPLEMENTATION
7.1 IMPLEMENTATION
Implementation includes placing the system into operation and providing the users
and operation personnel with the necessary documentation to use and maintain the new
system. Implementation includes all those activities that take place to convert from the old
system to the new. The new system may be totally new, replacing an existing system. Proper
implementation is essential to provide a reliable system to meet the organizational
requirements. Successful implementation may not guarantee improvement in the
organization using the new system, as well as, improper installation will prevent. There are
four methods for handling a system conversion. Parallel approach: The old system is operated
with the new system. Direct cut over method: The old system is replaced with the new
system. Pilot approach: Working version of the system is implemented in one part of the
organization based on the feedback, changes are made and the system is installed in the rest
of the organization by one of the other methods. Phase-in-method: Gradually implements the
system across all users. We have used the direct cut over method in our implementation.
FUTURE ENHANCEMENT
FUTURE ENHANCEMENT
We can modify the existing system by adding new features that are required in that
period.
This system can be modified to a web based software so that, it can connect different
parts of an organization and make access easy.
Considering this important factor , the system is designed in such a way that
provisions can be given for future enhancement without affecting the system presently
developed.
Increase security.
CONCLUSION
CONCLUSION
This System has remained devoid of web technology, with most works being carried out on a
pen and paper basis. This traditional method is prone to delays and inefficiency. This paper
proposes to simplify and speed up the process of compliant registration and tracking. With
the advancement and incorporation of internet and web technology into the Indian Police
System, it will definitely boost up the proceedings. This paper aims to help the public and the
police officers alike.
BIBLIOGRAPHY
REFERENCES:
1. Michael Otey “Microsoft SQL Server 2008 Database Design and Implementation”,
2010, Second Edition.
2. The Joy Of PHP Programming : A Beginner’s Guide – by Alan forbes.
3. PHP & MYSQL Web Development – by Luke Welling & Laura Thompson.
4. PHP :A Beginner’s Guide – by Vikram Vaswani.
5. https://www.udemy.com/
APPENDIX
a. SAMPLE SCREENS
Home
Register
Login
Compliant Registration
Compliant Details
Review Details
Compliant Details
Add Station
Add District
User Details
Compliant Details
b.CODING