Company Visitor Management System Report
Company Visitor Management System Report
MANAGEMENT SYSTEM
A PROJECT REPORT
Submitted by
GOVINDARAJ.R (610917104029)
ELUMALAI.S (610917104028)
HARISHKUMAR.V (610918104031)
ELANGOVAN.S (610918104027)
of
BACHELOR OF ENGINEERING
IN
SIGNATURE SIGNATURE
Mrs.M.R.SATHYA.,ME,B.ED., Mr.M.SURESH.,M.E,B.ED.,
carried out by me. It has not forward the part of any other thesis submitted for award
ELUMALAI.S (610918104028)
HARISHKUMAR.V (610918104031)
ELANGOVAN.S (610918104027)
We express my sincere gratitude to the people who extended their help during the
course of this project work.
We also thankful to all the faculty members of Department of Computer Science and
Engineering for their kind and valuable cooperation during the course of the project.
We would also like to thank my parents, friends and well-wishers who encouraged
me to do the project.
ABSTRACT
Company Visitor Management System deals with the security provided at company
premises from the unauthenticated or unwanted visitors.
Instead, Company Visitor Management System will assist you the professionalized
way in which you welcome your visitors. This software is a complete Visitor
Management service to improve the efficiency, productivity, security.
This is the project which keep records of visitors who visited in the company. CVMS
has one module i.e admin. Dashboard: In this sections, admin can briefly view how
many visitors visited in a particular period.
Visitors: In this section, admin adds new visitors by filling their information in add
visitors sections and also view and manage visitors records. Admin also put visitors
out time in the manage records section.
Search: In this bar, admin can search a particular person by their name and phone
number.
Reports: In this section admin can generate visitors reports between two dates. Admin
can also update his profile, change password and recover password.
TABLE OF CONTENTS
1. INTRODUCTION 7
1.1 Domain
1.2 Purpose
1.3 Scope
2. REQUIREMENT SPECIFICATION 8
3.1 Software Requirement
3.2 Hardware Requirement
2. ANALYSIS AND DESIGN 7
2.1 Analysis
2.2 Disadvantage of Present System
4. DESIGN INTRODUCTION 12
4.1 UML Diagram
4.2 USE CASE Diagram
4.3 Class Diagram
4.4 ER Diagram
4.5 ER Notation
4.6 MySQL Data Table
5. IMPLEMENTATION AND SYSTEM DESIGN 13
5.1 System Design
5.2 Unit Testing
5.3 Integration Testing
6. EVALUATION 67
7. CONCLUSION 24
8. REFERENCE 44
CHAPTER 1
INTRODUCTION
Introduction:
1. Dashboard: In this sections, admin can briefly view how many visitors visited
in a particular period.
2. Visitors: In this section, admin adds new visitors by filling their information in
add visitors sections and also view and manage visitor’s records. Admin also
put visitors out time in the manage records section.
3. Search: In this bar, admin can search a particular person by their name and
phone number.
4. Reports: In this section admin can generate visitor’s reports between two dates.
Admin can also update his profile, change password and recover password.
Purpose:-
Hardware Configuration :
Client Side:
Hard disk 10 GB
Server side:
RAM 1 GB
Hard disk 20 GB
Software Requirement:
Client Side:
Server Side:
Web Server APACHE
APACHE
The Apache HTTP Server Project is an effort to develop and maintain an open-source
HTTP server for modern operating systems including UNIX and Windows. The goal
of this project is to provide a secure, efficient and extensible server that provides
HTTP services in sync with the current HTTP standards.
The Apache HTTP Server ("httpd") was launched in 1995 and it has been the most
popular web server on the Internet since April 1996. It has celebrated its 20th birthday
as a project in February 2015.
PHP
✓ PHP stands for PHP: Hypertext Preprocessor.
✓ PHP is a server-side scripting language, like ASP.
✓ PHP scripts are executed on the server.
✓ PHP supports many databases (MYSQL, Informix, Oracle, Sybase, Solid,
Generic ODBC, etc.).
✓ PHP is an open source software .
MYSQL
http://localhost/phpmyadmin
CHAPTER 3
ANALYSIS AND DESIGN
Analysis:
In present all visitor work done on the paper. The whole year visitor is stored in the
registers. We can’t generate reports as per our requirements because its take more time
to calculate the visitors report.
➢ Not user friendly: The present system not user friendly because data is not
stored in structure and proper format.
➢ Manual Control: All report calculation is done manually so there is a chance
of error.
➢ Lots of paper work: Visitors maintain in the register so lots of paper require
storing details.
➢ Time consuming
CHAPTER 4
DESIGN INTRODUCTION
Design is the first step in the development phase for any techniques and principles for
the purpose of defining a device, a process or system in sufficient detail to permit its
physical realization.
Once the software requirements have been analyzed and specified the software design
involves three technical activities - design, coding, implementation and testing that are
required to build and verify the software.
The design activities are of main importance in this phase, because in this activity,
decisions ultimately affecting the success of the software implementation and its ease
of maintenance are made. These decisions have the final bearing upon reliability and
maintainability of the system. Design is the only way to accurately translate the
customer’s requirements into finished software or a system.
Design is the place where quality is fostered in development. Software design is a
process through which requirements are translated into a representation of software.
Software design is conducted in two steps. Preliminary design is concerned with the
transformation of requirements into data
UML Diagrams:
Actor:
A coherent set of roles that users of use cases play when interacting with the use
`cases.
Use case:A description of sequence of actions, including variants, that a system
performs that yields an observable result of value of an actor.
UML stands for Unified Modeling Language. UML is a language for specifying,
visualizing and documenting the system. This is the step while developing any
product after analysis. The goal from this is to produce a model of the entities
involved in the project which later need to be built. The representation of the entities
that are to be used in the product being developed need to be designed.
USECASE DIAGRAMS:
Use case diagrams model behavior within a system and helps the developers
understand of what the user require. The stick man represents what’s called an actor.
Use case diagram can be useful for getting an overall view of the system and
clarifying who can do and more importantly what they can’t do.
Use case diagram consists of use cases and actors and shows the interaction between
the use case and actors.
• The purpose is to show the interactions between the use case and actor.
• To represent the system requirements from user’s perspective.
• An actor could be the end-user of the system or an external system.
USECASE DIAGRAM:
Dashboard
Admin
Manage Visitors
(Update Details)
Ad
Generate Reports
Update Profile
Change Password
Password Recovery
Class Diagram:
ER Diagram:
• It maps well to the relational model. The constructs used in the ER model can
easily be transformed into relational tables.
• It is simple and easy to understand with a minimum of training. Therefore, the
model can be used by the database designer to communicate the design to the
end user.
• In addition, the model can be used as a design plan by the database developer to
implement a data model in specific database management software.
ER Notation
All notational styles represent entities as rectangular boxes and relationships as lines
connecting boxes. Each style uses a special set of symbols to represent the cardinality
of a connection. The notation used in this document is from Martin. The symbols used
for the basic ER constructs are:
▪ Entities are represented by labeled rectangles. The label is the name of the
▪ Relationships are represented by a solid line connecting two entities. The name
of the relationship is written above the line. Relationship names should be verbs
▪ Attributes, when included, are listed inside the entity rectangle. Attributes
which are identifiers are underlined. Attribute names should be singular nouns.
After all phase have been perfectly done, the system will be implemented to the
server and the system can be used.
SYSTEM DESIGN
The goal of the system testing process was to determine all faults in our project .The
program was subjected to a set of test inputs and many explanations were made and based on
these explanations it will be decided whether the program behaves as expected or not. Our
Project went through two levels of testing
1. Unit testing
2. Integration testing
UNIT TESTING
Unit testing is commenced when a unit has been created and effectively reviewed .In
order to test a single module we need to provide a complete environment i.e. besides
the section we would require
➢ The procedures belonging to other units that the unit under test calls
➢ Non local data structures that module accesses
➢ A procedure to call the functions of the unit under test with appropriate
parameters
➢ Testing admin login form-This form is used for log in of administrator of the
system. In this form we enter the username and password if both are correct
administration page will open otherwise if any of data is wrong it will get
redirected back to the login page and again ask the details.
➢ Report Generation: admin can generate report from the main database.
INTEGRATION TESTING
In the Integration testing we test various combination of the project module by
providing the input.
The primary objective is to test the module interfaces in order to confirm that no
errors are occurring when one module invokes the other module.
CHAPTER 6
EVALUATION
Login Page
Dashboard
Visitor Reports
Between Dates Reports
Admin Profile
Change Password
Forgot Password
Reset Password
CHAPTER 7
CONCLUSION:
The Application was designed in such a way that future changes can be
done easily. The following conclusions can be deduced from the development of the
project.
For PHP
➢ https://www.w3schools.com/php/default.asp
➢ https://www.sitepoint.com/php/
➢ https://www.php.net/
For MySQL
➢ https://www.mysql.com/
➢ http://www.mysqltutorial.org
For XAMPP
➢ https://www.apachefriends.org/download.html