Professional Documents
Culture Documents
ON
RESENTED BY:
TANUJ BANSAL
ROBIN BANSAL
AKASH KUMAR
UNDER THE ABLE GUIDANCE OF
Er. MANJEET SINGH
I would like to express my greatest appreciation to the all individuals who have
helped and supported me throughout the project. I am thankful to “Er. MANJEET
SINGH” PROJECT GUIDE for his ongoing support during the project, from
initial advice, and encouragement, which led to the final report of this project. I
would also like to thank “Er. MANJEET SINGH” who was always there in our
computer lab for assistance.
A special acknowledgement goes to my classmates who helped me in completing
the project by exchanging interesting ideas and sharing their experience.
I wish to thank my parents as well for their undivided support and interest who
inspired me and encouraged me to go my own way, without whom I would be
unable to complete my project.
At the end, I want to thank my friends who displayed appreciation to my work and
motivated me to continue my work.
Sincerely
TANUJ BANSAL
ROBIN BANSAL
AKASH KUMAR
We hereby declare that the work which is being presented in the project, entitled
“VISITOR MANAGEMENT SYSTEM” is done by us and it is an authentic
work carried out by us.
The matter embodied in this project has not been submitted by us for the award of
any other diploma to the best of our knowledge and belief.
DATE:
AKASH KUMAR
Hardware Configuration
1.Pentium IV Processor
2.512 MB RAM
3.40GB HDD
Software Configuration
1. OS : Windows XP
2. WAMP SERVER.
3. XAMP SERVER
4. PHP (PHP5.6, MySQL, Apache, and PHPMyAdmin)
This system tracks the usage of a public office by gathering increasing amounts of
information. A visitor management system can record the usage of the facilities by
specific visitors and provide documentation of visitor’s whereabouts. Since a
visitor management system provides a record of office used and the person visited,
these systems are frequently used to complement office security systems and
access control systems.
STATEMENT OF PROBLEM
After carefully analysis of the project the researcher observed that the following
problems are mainly encountered by different organization.
OBJECTIVE OF STUDY
The aim of this project is to design and implement an online visitors management
system.
1. Visitors get high quality service: since the recording requires human
information, with use of computer more concrete information will be
provided.
2. It will be easier to generate overall report: comprehensive and relational
database will make the report generation easy and faster.
3. High Security Environments: Assign and print credentials for your visitors
like any other employee, define detailed access rights, specify visitor escorts,
and give your staff full control over access to your facilities.
4. It will provide efficient, effective and timely services,
5. It will reduce corruption,
6. It contributes to the entire organization security.
Method
1. The whole design and development of the VMS, including research strategy,
research method and the research process will be outline.
2. In general, each detail of the system design and development procedure will
be explained briefly as following.
3. it is necessary to identify the system requirement for the items that used in
this project.
4. The system requirement of the VMS is the configuration, functional and data
requirement as well as the quality constraint of the laptop and reader.
5. The objective of system requirement is to ensure the VMS is running
smoothly and efficiently so that it could make the registration process faster
and easier.
System Integration
System integration is an important step for every system especially VMS.
It is consisting of process that iteratively combines component sub-
systems into one system. Furthermore, it is also mainly implemented for
successive and compatible levels of the system hierarchy.
From this definition, it can be states that VMS should be integrated with
both graphical user interface (GUI) and database management system
(DBMS) as well as the access control panel. Hence, the whole system
should be combined when every single unit or parts of the VMS is
completed.
Unit Testing:
A level of the real-time testing process where each single unit, block
module and components of the system are examined. It means that
individual part of the VMS should be isolating and perform test to
validate each component is met with the desired functionality and
requirement. Integration Testing: A level of the real-time testing process
where individual parts are combined and integrated as a group in order to
evaluate if they work correctly together. By using this way, the fault or
error can be determined when the parts or components of the VMS are
interacting together.
System Testing:
Standards of Testing
Software testers know about the different sorts of Software Testing. In this
article, we have incorporated majorly all types of software testing which
testers, developers, and QA reams more often use in their everyday testing
life. Let’s understand them!!!
The black box testing is a category of strategy that disregards the interior
component of the framework and spotlights on the output created against
any input and performance of the system. It is likewise called functional
testing.
The white box testing is a class of testing method that considers the
inside component of a framework. It is likewise called glass box testing
and structural testing.
White box testing is regularly utilized for verification.
Unit Testing
Branch Testing
Integration Testing
The goal of the integration testing technique is to take unit tested parts
and manufacture a program structure that has been directed by the design.
In integration testing, a collection of components is consolidated to create
output.
Functional Testing
It is a type of that constructs its experiments with respect to the details of the software segment u
Regression Testing
Recovery Testing
Security Testing
Performance Testing
Performance testing is the testing system used to survey the speed and
adequacy of the framework and to ensure it is producing outcomes in a
Stress Testing
Smoke Testing
Acceptance Testing
Storage Testing
This type of software testing checks the software under test stores data
documents in the right directories and that it saves adequate space to keep
sudden termination because of an absence of space. It is generally done
by the testing group.
Parallel Testing
Usability Testing
This falls under the category of black box testing. Primarily, system
navigation is verified in the usability testing.
Alpha Testing
Beta Testing
The beta test is directed at one or more client websites by the end-user of
the product. This adaptation is launched for the few numbers of clients
for testing the real-time environment.
Beta testing is successful after the client affirms the software. Thus, end-
user really utilizes the software and gives the review to the company so
that the company can take the vital actions before the launch.
Gamma Testing
Gamma testing technique is used when the product is set for launch with
defined necessities. It is performed at the customer place. It is done
specifically by avoiding all the in-house testing exercises.
Non-Functional Testing
Stability Testing
Scalability Testing
This testing type is a part of the series of non-functional tests that tests a
product application for estimating its capacity to scale up – be it the
number of transactions, the client load supported, the data volume and so
forth. It is led by the performance engineers.
Volume Testing
Cross-browser Testing
Load Testing
Ad-Hoc Testing
Compatibility Testing
Vulnerability Testing
This is a type of testing which considers application security and has the
reason to avert issues which may influence the application stability and
integrity. It can be operated by the internal testing groups or outsourced
to specific organizations.
Static Testing
Qualification Testing
Operational Testing
Mutation Testing
Pair Testing
Positive Testing
The positive testing is a type of software testing used to figure out what
system is expected to do. It supports to check if the application is
verifying the necessities or not.
Negative Testing
Install/Uninstall Testing
Gorilla Testing
Example Testing
Component Testing
It is for the most part conducted by the developers after the finishing of
unit testing. Component testing is a testing technique that includes testing
a collection of units as code together in general as opposed to testing
singular functions strategies. Its goal is to recognize if any fault exists
subsequent to associating those numerous functionalities with each other.
End-to-end Tests
The end-to-end testing type hatches a user behavior with the product in
an entire application environment. It confirms that different flows of
users function as assumed and can be as straightforward as loading a site
page or signing in or considerably more unpredictable condition like
online payments, verifying e-mails etc.
End-to-end tests are extremely helpful, yet they’re costly to implement
and can be difficult to manage when they’re automated. They are
intended to be fast to execute, and their objective is to give you the
affirmation that the significant traits of your framework are functioning
as they should.
Active Testing
Accessibility Testing
Penetration Testing
Ramp Testing
Back-end Testing
API testing is a sort of testing that resemble unit testing. All of the Software
APIs are tested according to API term. This testing is majorly performed by
testing group unless APIs to be tested are complex and necessities broad
coding. It needs the understanding of API functionality and having great
coding abilities.
Agile Testing
Automated Testing
Age Testing
Benchmark Testing
The type of testing method that tests an executable application for portability
all over framework environments and platforms more often for affirmation
to an ABI designation. It is done by the team of testers.
The testing procedure that practices testing systems, for example, xUnit, that
permit the execution of unit tests to decide if different segments of the code
are working as assumed under different conditions. It is operated by the
development groups.
Conversion Testing
Exploratory Testing
Concurrency Testing
Destructive Testing
Destructive testing is a type of testing in which the tests are done to the
specimen’s breakdown, keeping in mind the end goal to comprehend a part’s
basic execution or material behavior under various loads.
Equivalence Partitioning
Dependency Testing
Domain Testing
Fuzz Testing
A mix of Black Box and White Box testing strategies: testing a bit of
program against its detail yet utilizing some learning of its inside workings.
It can be achieved by either testers or development groups.
The goal of this GUI testing is to approve the GUI according to the business
prerequisite. The normal GUI of the application is specified in GUI mockup
screens and Detailed Design Document.
Globalization Testing
This type of testing technique checks the best possible working of the
software with any of the culture settings utilizing each kind of international
information conceivable. It is done by a large group.
Monkey Testing
Sanity Testing
Keyword-driven Testing
Risk-based Testing
This testing includes testing of very critical functionality, that has the
greatest influence on business and in which the possibility of failure is really
huge. The priority determination relies upon the business prerequisites, so
when priority is fixed for all functionalities then test cases are performed
first served by medium functionalities and then low priority functionalities.
Conformance Testing
Interface Testing
Interface testing type is needed when a product offers help for at least one
interface like “Graphical UI”, or “Application programming interface” or
“Order Line Interface” to associate with its clients or other programs.
Interfaces fill in as the medium for a product to acknowledge data from a
client and offer an output to the client.
Localization Testing
Manual-Support Testing
The testing method that includes testing of each and every function executed
by the individuals while setting up the information and utilizing this
information from the automated framework. It is directed by the team of
software testers.
The utilization of Model-based design for executing and designing the vital
antiques to perform program testing. This testing is generally conducted by
software testing groups.
Path Testing
It is a standard white box testing which has the objective to fulfill scope
criteria for each logical path through the software. It is normally conducted
by the development group.
Retesting
Requirement Testing
The testing method which approves that the requirements are right,
unambiguous, complete, and logically reliable and permits planning a
fundamental and adequate arrangement of test cases from those necessities.
It is performed by QA team.
Statement Testing
Structural Testing
It is also a type of white box testing method which considers the inside
structure of a component or a framework and guarantees that every program
statement plays out its proposed work. It is generally done by the software
developers.
Documentation Testing
Loop Testing
Configuration Testing
Bucket Testing
Thread Testing
Reliability Testing
Installation Testing
Workflow Testing
Conclusion