Major Project Report

On

THIRD EYE
Submitted by:

Tanay Choubey [19100BTIT06623]

Utsav Maloo [19100BTIT06632]
Maghvendra Singh Panwar [1910DMTIT05970]

Under the guidance of

GUIDE: - Mr. Rahul Choudhary

Co – GUIDE: - Mrs. Jagrati Nagdiya

DEPARTMENT OF INFORMATION TECHNOLOGY

SHRI VAISHNAV INSTITUTE OF INFORMATION TECHNOLOGY

SHRI VAISHNAV VIDYAPEETH VISHWAVIDYALAYA, INDORE

JULY - DEC 2022

 THIRD EYE

SHRI VAISHNAV INSTITUTE OF INFORMATION TECHNOLOGY,

INDORE

DEPARTMENT OF INFORMATION TECHNOLOGY

DECLARATION

We here declare that work which is being presented in the project entitled “THIRD EYE” in
partial fulfillment of degree of Bachelor of Technology is an authentic record of our carried out
under the supervision and guidance of Mr. Rahul Choudhary. The matter embodied in this
project has not been submitted for the award of any other degree.

Date:

Tanay Choubey [19100BTIT06623] Signature

Utsav Maloo [19100BTIT06632] Signature
Maghvendra Singh Panwar [1910DMTIT05970] Signature

2
 THIRD EYE

SHRI VAISHNAV INSTITUTE OF INFORMATION TECHNOLOGY,

INDORE

DEPARTMENT OF INFORMATION TECHNOLOGY

PROJECT APPROVAL SHEET

Following team has done the appropriate work related to the “THIRD EYE” in partial
fulfillment for the award of Bachelor of Technology of SHRI VAISHNAV VIDYAPEETH
VISHWAVIDYALAYA, INDORE and is being submitted to SHRI VAISHNAV INSTITUTE
OF INFORMATION TECHNOLOGY, INDORE.

Team:

1. Tanay Choubey [19100BTIT06623]

2. Utsav Maloo [19100BTIT06632]
3. Maghvendra Singh Panwar [1910DMTIT05970]

Internal Examiner External Examiner

Date:

3
 THIRD EYE

SHRI VAISHNAV INSTITUTE OF INFORMATION TECHNOLOGY,

INDORE

DEPARTMENT OF INFORMATION TECHNOLOGY

CERTIFICATE

This is to certify that Tanay Choubey, Utsav Maloo and Maghvendra Singh Panwar working
in a team have satisfactorily completed the project entitled “THIRD EYE” under my guidance
in partial fulfillment of degree of Bachelor of Technology awarded by SHRI VAISHNAV
VIDYAPEETH VISHWAVIDYALAYA, INDORE during the academic year 2021-22.

Project Guide: Head of Department:

Mr. Rahul Choudhary Dr. Jigyasu Dubey

4
 THIRD EYE

ACKNOWLEDGEMENT

We are grateful to a number of persons for their advice and support during the time of complete
our project work. First and foremost, our thanks go to Dr. Jigyasu Dubey Head of the
Department of Information Technology and Mr. Rahul Choudhary the mentor of our project
for providing us valuable support and necessary help whenever required and also helping us
explore new technologies by the help of their technical expertise. His direction, supervision and
constructive criticism were indeed the source of inspiration for us.

We would also like to express our sincere gratitude towards our Director Dr. Anand Rajavat for
providing us valuable support.

We are really indebted to Prof. Rahul Choudhary, project coordinator for helping us in each
aspect of our academic’s activities. We also owe our sincere thanks to all the faculty members
of Information Technology Department who have always been helpful.

We forward our sincere thanks to all teaching and non-teaching staff of Information
Technology department, SVVV Indore for providing necessary information and their kind co-
operation.

We would like to thanks our parents and family members, our classmates and our friends for
their motivation and their valuable suggestion during the project. Last, but not the least, we thank
all those people, who have helped us directly or indirectly in accomplishing this work. It has
been a privilege to study at SHRI VAISHNAV VIDYAPEETH VISHWAVIDYALAYA,
INDORE.

5
 THIRD EYE

ABSTRACT

Nowadays, we usually say that we live in an open world, where everything is clear and no isolation
among all countries all over the world. I think that the technology revolution is opening the world. We
use the Internet everywhere every awhile; we cannot live without it. You do not have to travel away to
know new technologies, you can learn over the Internet. Internet became our real world that shapes our
social networks. Right now, we cannot drive without traffic and navigation apps that keep us in touch
with new roads status. In this project, we target using the Internet to communicate with our homes, or
our offices by observing whatever happening. When we talk about security of any place, then Video
Surveillance Cameras are the most popular equipment for this purpose.

6
 THIRD EYE

LIST OF FIGURES

Figure No. Description Page No.

1 Use case diagram 24

2 DFD Level 0 30

3 DFD Level 1 31

4 DFD Level 2 31

5 DFD Level 3 32

6 Activity Diagram for Monitor 34

7 Activity Diagram for Identify 35

8 Activity Diagram for In /Out 36

9 Class diagram 37

10 Sequence Diagram 38

11 Component Diagram 40

12 Home Page UI 41

13 Monitor Page UI 41

14 Identify Page UI 42

15 Record Page UI 42

16 IN /Out Page UI 43

17 In Page Output 43

18 Out Page Output 44

19 Record Page Output 44

20 Monitor Page Output 45

21 Identify Page Output 45

22 Coding Page 1 46

7
 THIRD EYE

23 Coding Page 2 46

24 Coding Page 3 47

25 Coding Page 4 47

26 Result Test Case 1 51

27 Test Case 2 52

28 Result Test Case 2 52

29 Test Case 3 53

30 Result Test Case 3 54

31 Result Test Case 3 54

32 Test Case 4 55

33 Result Test Case 4 55

34 Result Test Case 5 56

8
 THIRD EYE

TABLE OF CONTENT

Title Page Number

Declaration 2

Project Approval Sheet 3

Certificate 4

Acknowledgement 5

Abstract 6

List of Figures 7-8

1. CHAPTER 1 – INTRODUCTION 12-13

• Introduction

• Problem Statement

• Need for the new System

• Objective

• Application

2. CHAPTER 2 – LITERATURE SURVEY 14-15

• Work done by other

• Benefits
• Proposed Solution
• Technology used
➢ Software Requirement
➢ Hardware Requirement
9
 THIRD EYE

3. CHAPTER 3 – SOFTWARE ENGINEERING APPROACH 16-25

• Software Engineering paradigm applied

➢ Description
➢ Advantages and Disadvantages
➢ Reason for use
• Requirement Analysis
➢ Software Requirement Specification
➢ Glossary
➢ Supplementary Specifications
➢ Use Case Model

4. DESIGN 26-38

• Design Concept
• Design Technique
• Modeling
➢ DFD Model Level 0 and 1
• UML Diagram
➢ Activity Diagram
➢ Class Diagram
➢ Sequence Diagram

5. IMPLEMENTATION 39-47

• Functional programming
• Component Diagram
• UI Screenshots
• Coding Screenshots

6. TESTING OBJECTIVE 48-56

• Testing Objectives

10
 THIRD EYE

• Types of Testing
➢ Unit Testing
➢ System Testing
➢ Integration Testing
• Testing Approach
➢ Black Box Testing
➢ White Box Testing
• Validation
• Limitations
• Result
• Test Plans
➢ Test Case Pass/Fail Criteria
➢ Test Cases

7. LIMITATION OF PROJECT 57

8. FUTURE ENHANCEMENT 58

9. CONCLUSION 59

10. REFERENCES 60

11
 THIRD EYE

CHAPTER 1 – INTRODUCTION

• Introduction

Nowadays, we usually say that we live in an open world, where everything is clear and no isolation
among all countries all over the world. I think that the technology revolution is opening the world.
We use the Internet everywhere every awhile; we cannot live without it. You do not have to travel
away to know new technologies, you can learn over the Internet. Internet became our real world
that shapes our social networks. Right now, we cannot drive without traffic and navigation apps
that keep us in touch with new roads status. In this project, we target using the Internet to
communicate with our homes, or our offices by observing whatever happening. When we talk
about security of any place, then Video Surveillance Cameras are the most popular equipment for
this purpose.

• Problem Statement

1. Traditional video surveillance was based on analog technology closed circuit television
(CCTV), and then recorded on video tapes.
2. Analog technology at one time served a purpose for security monitoring.
3. The advantage of a digital system over an analog is clear because of better picture quality and
the key feature to see exactly what is happening in the moment.
4. After any crime taken place, it takes a long time to analyze hours of videos.
5. It is a time-consuming procedure and costs the concerned authority valuable time to take quick
action.
6. It is difficult to keep monitor and keep track of people who may enter a restricted place.

• Need for the new System

1. This system simply recorded in the moment activity for future access. It relied on human
monitoring reliability and changing the tapes regularly.
2. Now digital CCTV is revolutionizing security measures and technology has evolved to
allow for a more diverse security monitoring system.
12
 THIRD EYE

3. The advantage of a digital system over an analog is clear because of better picture quality
and the key feature to see exactly what is happening in the moment.
4. There should be a way that can alert the authority when something like this happens.

• Objective
The main objective behind this project is to promote security on different places. When we talk about
security of any place, then Video Surveillance Cameras are the most popular equipment for this
purpose. It has gained immense popularity as an effective security measure. In the near future, most
institutions and organizations will have surveillance cameras installed. Consequently, this will reduce
burglary incidents and enhance social stability.

• Application

This system simply recorded in the moment activity for future access. It relied on human monitoring
reliability and changing the tapes regularly. There should be a way that can alert the authority when
something like this happens. Recording only of suspicious events will be an option in order to reduce
the required storage capacity.

KEY FEATURES

▪ Monitor – allow to detect what thing is stolen from frame

▪ Identify – Finds the family members (it has to be trained first)

▪ Recording – record the area continuously.

▪ In Out – Finds who entered and gone from room.

13
 THIRD EYE

CHAPTER 2 – LITERATURE SURVEY

• Work done by other

There are many CCTV systems available, the traditional ones, but the advanced versions available
uses PIR (Passive Infrared) motion sensor, which is the most widely used motion sensor in home
security systems, that detects body heat (infrared energy). When your system is armed, motion
sensor is activated indicating Intrusion detected. However, for a PIR sensor to work well most of
the time, they are designed with certain limitations. A PIR sensor cannot detect a stationary or very
slowly moving body and if the sensor were set to the required sensitivity, it can be activated by the
cooling of a nearby wall in the evening.

• Benefits
o This system simply recorded in the moment activity for future access. It relied on human
monitoring reliability and changing the tapes regularly.
o The advantage of a digital system over an analog is clear because of better picture quality and the
key feature to see exactly what is happening in the moment.
o Recording only of suspicious events will be an option in order to reduce the required storage
capacity.
o There should be a way that can alert the authority when something like this happens.

• Proposed Solution
o This system simply recorded in the moment activity for future access. It relied on human

monitoring reliability and changing the tapes regularly.

o Now digital CCTV is revolutionizing security measures and technology has evolved to allow for

a more diverse security monitoring system.

o The advantage of a digital system over an analog is clear because of better picture quality and the

key feature to see exactly what is happening in the moment.

14
 THIRD EYE

o There should be a way that can alert the authority when something like this happens.

o We are going to discuss the smart form of security, and with camera system monitoring service,

you can rest assured that any suspicious activities are reported and dealt with quickly.

o Recording only of suspicious events will be an option in order to reduce the required storage
capacity

• Technology used
➢ Software Requirement
▪ Windows/Linux/Mac OS any version, hence it can run on any platform.
▪ Python3, it need python to be installed in your system to run this successfully.
▪ Packages in python -
1. OpenCV
2. Skimage
3. Numpy
4. Tkinter

➢ Hardware Requirement
o System: Multimedia PC
o Processor: Pentium 4 or above
o Memory: 2GB RAM
o Hard Disk: 80GB or above
o Webcam with drivers installed
o Flashlight/ LED if using this at night.

15
 THIRD EYE

CHAPTER 3 – SOFTWARE ENGINEERING APPROACH

• Software Engineering paradigm applied

We have used an Agile SDLC Model for building our project.

➢ Description

Agile model believes that every project needs to be handled differently and the existing methods need
to be tailored to best suit the project requirements. In Agile, the tasks are divided to time boxes (small
time frames) to deliver specific features for a release.

Iterative approach is taken and working software build is delivered after each iteration. Each build is
incremental in terms of features; the final build holds all the features required by the customer.

The Agile thought process had started early in the software development and started becoming popular
with time due to its flexibility and adaptability

The two main programming approaches are top-down approach and bottom-up approaches. Here while
doing the software, we use the bottom-up approach

In bottom-up method, the sub modules are designed and developed and these are assembled together to
get the main system. The individual modules are coded and debugged with example data given checks
ready for the minor project design. This project also followed the bottom-up design. The sub modules
are prepared very keenly, and minute notations are made.

In the art street, the sub modules are designed first, these sub modules are integrated into main
modules. Other modules also designed in the same fashion. Each module is tested at the beginning
when they are integrated with the sub-modules.

These checked and corrected modules are integrated to make the main system.

16
 THIRD EYE

➢ Advantages
o Customer satisfaction by rapid, continuous delivery of useful software.
o Working software is delivered frequently (weeks rather than months).
o Face-to-face conversation is the best form of communication.
o Close, daily cooperation between businesspeople and developers.
o Continuous attention to technical excellence and good design.
o Regular adaptation to changing circumstances.
o Even late changes in requirements are welcomed

o Disadvantages
o In case of some software deliverables, especially the large ones, it is difficult to assess the
effort required at the beginning of the software development life cycle.
o There is lack of emphasis on necessary designing and documentation.
o The project can easily get taken off track if the customer representative is not clear what final
outcome that they want.
o Only senior programmers are capable of taking the kind of decisions required during the
development process. Hence it has no place for newbie programmers, unless combined with
experienced resources.

➢ Reason for use

The sub modules are designed and developed, and these are assembled together to get the main system.
The individual modules are coded and debugged with example data given checks ready for the minor
project design., the sub modules are designed and developed, and these are assembled together to get
the main system. The individual modules are coded and debugged with example data given checks
ready for the minor project design. the online admission system, the sub modules are designed first,
these sub modules are integrated into main modules. Other modules also designed in the same fashion.
Each module is tested at the beginning when they are integrated with the sub-modules.

17
 THIRD EYE

• Requirement Analysis

Requirements Analysis is the process of defining the expectations of the users for an application that is
to be built or modified. Requirement’s analysis involves all the tasks that are conducted to identify the
needs of different stakeholders. Therefore, requirements analysis means to analyze, document, validate
and manage software or system requirements. High-quality requirements are documented, actionable,
measurable, testable, traceable, helps to identify business opportunities, and are defined to a facilitate
system design. Requirement’s analysis process:

The requirements analysis process involves the following steps:

o Eliciting requirements

The process of gathering requirements by communicating with the customers is known as eliciting
requirements.

o Analyzing requirements

This step helps to determine the quality of the requirements. It involves identifying whether the
requirements are unclear, incomplete, ambiguous, and contradictory. These issues resolved before
moving to the next step.

o Requirements modeling

In Requirements modeling, the requirements are usually documented in different formats such as
use cases, user stories, natural-language documents, or process specification.

o Review and retrospective

This step is conducted to reflect on the previous iterations of requirements gathering in a bid to
make improvements in the process going forward.

18
 THIRD EYE

a) Functional Requirement

R 1: - START

Description: - The existing user will be able to start the system using the Third EYE

application.

R 1.1: - User View

Here user can view monitoring images and videos captured by applications.
Input: - User run the application on his system.
Output: - Application start.

R 1. 1. 1: - Monitoring
Input: - Here you can click the Monitor Button.
Output: - Now camera start to monitor the whole room.

R 1. 1 .2: - View Photos

Input: - Here system targets to detect suspicious behavior in a specific area.
Output: - The system captured the Moment and stored in local file.

R 2: - IDENTIFY

Description: - This module recognition the identical person and non-identical person.

Input: - Here you can click the Identify Button.

Output: - Two option are there “Start with know” and “Add Member”.

R 2.1: - Add Member

Input: - Here you can enter the name and Id of person.

Output: - Person successfully added in your system.

R 2. 2: - Start With know

Input: - Here you can click the Button.

Output: - Now camera start to spotting the authentic person in a frame.

19
 THIRD EYE

R 3: IN/OUT

Description: - This is the feature which can detect if someone has entered in the room or

gone out.

R 3. 1: - IN

Input: - Here you can click the IN / OUT Button.

Output: - The system captured the Moment when person IN the room and stored in
local IN name folder with date and time.

R 3. 2: - OUT

Input: - Here you can click the IN / OUT Button.

Output: - The system captured the Moment when person OUT the room and stored
in local OUT name folder with date and time.

R 4: - RECORD

Description: - It start the recording and stored in your system.

Input: - Here you can click the Record Button.

Output: - The webcam or camera start the recording.

R 4.1: - View Recorded Video

Input: - Go to your system and click on recording folder.

Output: -Here you can view all the recording.

R 5: - END

Description: - End means to end access to a computer system and end the current session.

b) Non-Functional Requirement

Non-functional requirements will describe how a system should behave and what limits there are on its
functionality, generally specify the system's quality attributes. Factors like these comes under Non-
Functional Requirements
20
 THIRD EYE

3.2.1 Performance

1.Average load time of the start page of website should be less than 5 seconds.

2.Average response time of the system should be less than 10 seconds.

3.Our system should easily accessible on the system having minimum internet speed

of1MB/s

3.2.2 Reliability

There will be a maximum of 1 bug/KLOC.

3.2.3 Supportability

All code will be written as specified by the Hungarian Naming Convention.

3.2. Security

Users’ information will be secure and he will be able to access only their own personal
information

➢ Software Requirement Specification

The objective of this SRS document is to specify software requirements of the Online Admission for
the college. It is intended to be a complete specification of what functionality the admission provides.
The main purpose of the system is to automate the task carried out by different peoples in the
organization to perform the student admission. Specific design and implementation details will be
specified in a future document.

Overview of SRS

SRS will include two sections.

o Overall Description will describe major components of the system, interconnection and
external interfaces.
o Specific Requirements will describe the functions of actors, their role in the system and
constraints.

21
 THIRD EYE

Overall Description

The SRS document will give further details on the overall product description, including the hardware,
software, and communications interfaces, product functions, user characteristics, and any assumptions
that will be made.

Specific Requirements

The SRS document will also include the specific requirements needed. These will include the
functions, performance, design, and software attributes. This document is organized in a logical
manner and is easy to follow. Readers should refer to the table of contents, appendices, or index if
looking for something in specific. Otherwise, reading this document from start to finish will start with
a vague description and get more specific and detailed as changing sections and reading further.

Feasibility Study

o Economic Feasibility

Economic analysis is most frequently used for evaluation of the effectiveness of the system. More
commonly known as cost/benefit analysis the procedure is to determine the benefit and saving that
are expected from a system and compare them with costs, decisions is made to design and
implement the system.

This part of feasibility study gives the top management the economic justification for the new
system. This is an important input to the management because very often the top management does
not like to get confounded by the various technicalities that bound to be associated with a project
of this kind. A simple economic analysis that gives the actual comparison of costs and benefits is
much more meaningful in such cases.
Economic analysis is most frequently used for evaluation of the effectiveness of the system. More
commonly known as cost/benefit analysis the procedure is to determine the benefit and saving that
are expected from a system and compare them with costs, decisions is made to design and
implement the system.

22
 THIRD EYE

o Technical Feasibility

Technical feasibility centers on the existing manual system of the test management process and to
what extent it can support the system. According to feasibility analysis procedure the technical
feasibility of the system is analyzed and the technical requirements such as software facilities,
procedure, inputs are identified. It is also one of the important phases of the system development
activities It is technically feasible, since the whole system is designed into the latest technologies
like PYTHON which are the most recent technologies.

The system offers greater levels of user friendliness combined with greater processing speed.
Therefore, the cost of maintenance can be reduced. Since processing speed is very high and the
work is reduced in the maintenance point of view management convince that the project is
operationally feasible.

o Operational Feasibility

It is Operational feasible, since the system is providing an attractive GUI interface to the
operator/end user, so he feels very easy to work onto it. Response to operator/end user is very fast
and very good. Since, as we mentioned above that it requires much less amount of cost, it uses
computer work, so it is very fast to operate, and it is very easy for user to work on it.

➢ Glossary

The final output is the requirements specification document (SRS). For smaller problems or problems
that can easily be comprehended; the specification activity might come after the entire analysis is
complete. However, it is more likely that problem analysis and specification are done concurrently. All
the information for specification activity as following the analysis activity.

Analysis of Factual Data

Analysis of data is a process of inspecting, cleaning, transforming, and modeling data with the goal of
highlighting useful information, suggesting conclusions, and supporting decision making. Data
analysis has multiple facets and approaches, encompassing diverse techniques under a variety of
names, in different business, science, and social science domains.
23
 THIRD EYE

➢ Use Case Model

A use case diagram is a dynamic or behavior diagram in UML. Use case diagrams model the
functionality of a system using actors and use cases. Use cases are a set of actions, services, and
functions that the system needs to perform. In this context, a system is something being developed or
operated, such as a web site. The actors are people or entities operating under defined roles within the
system.

Fig 1: Use case diagram

24
 THIRD EYE

DESCRIPTION: -

1. USE CASE: -a. Start

b. Monitor
c. View Image
d. Identify
e. Add Member
f. Start with Know
g. IN /OUT
h. Recording
i. End
j. View Recording

2. ACTOR: - USER

25
 THIRD EYE

CHAPTER 4 – DESIGN

Software design is the process of conceptualizing the software requirements into software
implementation. This is the initial phase within the software development life cycle (SDLC) shifting
the concentration from the problem to the solution.

When conceptualizing the software, the design process establishes a plan that takes the user
requirements as challenges and works to identify optimum solutions. The plan should determine the
best possible design for implementing the intended solution.

• Design Concept
➢ System Design

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 first step in system designing is to
determine how the output is to be produced and in what format. In the second step, input data and
master files are to be designed to meet requirement of the proposed output. The processing phases are
handled through program construction and testing, including a list of the programs needed to meet the
system's objectives and complete documentation.

System design is the solution to the creation of a new system. This phase is composed of several
systems. This phase focuses on the detailed implementation of the feasible system. It emphasis on
translating design specifications to performance specification. System design has two phases of
development logical and physical design.

During logical design phase the analyst describes inputs (sources), outputs (destinations), databases
(data stores) and procedures (data flows) all in a format that meats the uses requirements. The analyst
also specifies the user needs and at a level that virtually determines the information flow into and out
of the system and the data resources. Here the logical design is done through data flow diagrams and
database design.

26
 THIRD EYE

The physical design is followed by physical design or coding. Physical design produces the working
system by defining the design specifications, which tell the programmers exactly what the candidate
system must do. The programmers write the necessary programs that accept input from the user,
perform necessary processing on accepted data through call and produce the required report on a hard
copy or display it on the screen.

• Design Technique
➢ Logical Design

Logical design of an information system shows the major features and also how they are related to one
another. The first step of the system design is to design logical design elements. This is the most
creative and challenging phase and important too. Design of proposed system produces the details of
the state how the system will meet the requirements identified during the system analysis that is, in the
design phase we have to find how to solve the difficulties faced by the existing system. The logical
design of the proposed system should include the details that contain how the solutions can be
implemented. It also specifies how the database is to be built for storing and retrieving data, what kind
of reports are to be created and what are the inputs to be given to the system. The logical design
includes input design, output design, and database design and physical design.

➢ Physical Design

The process of developing the program software is referred to as physical design. We have to design
the process by identifying reports and the other outputs the system will produce. Coding the program
for each module with its logic is performed in this step. Proper software specification is also done in
this step.

➢ Input Design

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
into a usable form for processing data entry. The activity of putting data into the computer for

27
 THIRD EYE

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 errors, avoiding delay, avoiding extra steps
and keeping the process simple.

The system needs the data regarding the asset items, depreciation rates, asset transfer, physical
verification for various validation, checking, calculation and report generation. The error raising
method is also included in the software, which helps to raise error message while wrong entry of input
is done. So, in input design the following things are considered:

o What data should be given as input?

o How the data should be arranged or coded?
o Methods for preparing input validations and steps to follow when error occur
o The samples of screen layout are given in the appendix.

➢ Output Design

Computer output is the most important and direct information source to the user. Output design is a
process that involves designing necessary outputs in the form of reports that should be given to the
users according to the requirements. Efficient, intelligible output design should improve the system's
relationship with the user and help in decision making. Since the reports are directing referred by the
management for taking decisions and to draw conclusions, they must be designed with almost care and
the details in the reports must be simple, descriptive and clear to the user. So, while designing output
the following things are to be considered:

o Determine what information to present.

o Arrange the presentation of information in an acceptable format.
o Decide how to distribute the output to intended receipts.
o Depending on the nature and future use of output required, they can be displayed on the
monitor for immediate need and for obtaining the hardcopy. The options for the output reports
are given in the appendix.

28
 THIRD EYE

• Modeling

System modeling is the process of developing abstract models of a system, with each model presenting
a different view or perspective of that system. System modeling has now come to mean representing a
system using some kind of graphical notation, which is now almost always based on notations in the
Unified Modeling Language (UML). System modeling helps the analyst to understand the
functionality of the system and models are used to communicate with customers.

➢ DFD Model Level-0 & 1

A Data Flow Diagram termed as DFD, graphically representing the functions, or processes, which
capture, manipulate, store, and distribute data between a system and its environment and between
components of a system. The visual representation makes it a good communication tool between User
and System designer. Structure of DFD allows starting from a broad overview and expand it to a
hierarchy of detailed diagrams. DFD has often been used due to the following reasons:

o Logical information flow of the system

o Determination of physical system construction requirements
o Simplicity of notation
o Establishment of manual and automated systems requirements

Data flow diagrams can be divided into logical and physical. The logical data flow diagram
describes flow of data through a system to perform certain functionality of a business. The physical
data flow diagram describes the implementation of the logical data flow.

DESCRIPTION: -

1. Circle: A circle (bubble) shows a process that transforms data inputs into data outputs.
(Third EYE)
2. Source or Sink: Source or Sink is an external entity and acts as a source of system inputs or
sink of system outputs.
External Entity: - (User; Camera)
3. Data Flow: A line shows the flow of data into or out of a process or data store.

29
 THIRD EYE

Fig 2: DFD level 0

DESCRIPTION: -

1. Circle: A circle (bubble) shows a process that transforms data inputs into data
outputs.
(7 Process in upper diagram)
2. Source or Sink: Source or Sink is an external entity and acts as a source of system
inputs or sink of system outputs.
External Entity: - (User; Camera)
3. Data Flow: A line shows the flow of data into or out of a process or data store.
4. Data Store: A set of parallel lines shows a place for the collection of data items. A
data store indicates that the data is stored which can be used at a later stage or by the
other processes in a different order. The data store can have an element or group of
elements.

Database: - (a. Capturing Image Database

b. Identify Member Database
c. Database of IN / OUT
d. Recording Database)

30
 THIRD EYE

Fig 3: DFD level 1

Fig 4: DFD level 2

31
 THIRD EYE

Fig 5: DFD level 3

32
 THIRD EYE

• UML Diagram

The UML diagrams are categorized into structural diagrams, behavioral diagrams, and also interaction
overview diagrams.

Structural diagrams depict a static view or structure of a system. It is widely used in the documentation
of software architecture. It embraces class diagrams, composite structure diagrams, component
diagrams, deployment diagrams, object diagrams, and package diagrams. It presents an outline for the
system. It stresses the elements to be present that are to be modeled.

Behavioral diagrams portray a dynamic view of a system or the behavior of a system, which describes
the functioning of the system. It includes use case diagrams, state diagrams, and activity diagrams. It
defines the interaction within the system.

➢ Activity Diagram

An activity diagram is used to model a large activity's sequential workflow by focusing on action
sequences and respective action initiating conditions. The state of an activity relates to the performance
of each workflow step.

An activity diagram is represented by shapes that are connected by arrows. Arrows run from activity
start to completion and represent the sequential order of performed activities. Black circles represent
an initial workflow state. A circled black circle indicates an end state. Rounded rectangles represent
performed actions, which are described by text inside each rectangle.

A diamond shape is used to represent a decision, which is a key activity diagram concept. Upon
activity completion, a transition (or set of sequential activities) must be selected from a set of
alternative transitions for all use cases. Synchronization bars indicating the start or completion of
concurrent activities are used to represent parallel sub flows.

33
 THIRD EYE

➢ Monitoring Diagram

Fig : Activity Diagram for Monitor

34
 THIRD EYE

➢ Identification Diagram

Fig 7: Activity Diagram for Identify

35
 THIRD EYE

➢ In / Out Diagram

Fig 8: Activity Diagram for In /Out

36
 THIRD EYE

➢ Class Diagram

A class diagram is primarily designed for developers to provide the conceptual model and architecture
of the system being developed. Typically, a class diagram consists of more than one class or all the
created classes for a system. It is a type of structure diagram and looks similar to a flow chart having
three main parts illustrated in rectangular boxes. The first or top part specifies the class name, the
second or middle specifies attributes of that class and the third or bottom section lists the methods or
operations that specific class can perform.

Fig 9: Class Diagram

37
 THIRD EYE

➢ Sequence Diagram

The sequence diagram represents the flow of messages in the system and is also termed as an event
diagram. It helps in envisioning several dynamic scenarios. It portrays the communication between any
two lifelines as a time-ordered sequence of events, such that these lifelines took part at the run time. In
UML, the lifeline is represented by a vertical bar, whereas the message flow is represented by a vertical
dotted line that extends across the bottom of the page. It incorporates the iterations as well as branching.

Fig 10: Sequence diagram

38
 THIRD EYE

CHAPTER 5 – IMPLEMENTATION

In the process of coding, the lines of code keep multiplying, thus, size of the software increases.
Gradually, it becomes next to impossible to remember the flow of program. If one forgets how
software and its underlying programs, files, procedures are constructed it then becomes very difficult
to share, debug and modify the program. The solution to this is structured programming. It encourages
the developer to use subroutines and loops instead of using simple jumps in the code, thereby bringing
clarity in the code and improving its efficiency Structured programming also helps programmer to
reduce coding time and organize code properly.

• Functional Programming

Functional programming is style of programming language, which uses the concepts of mathematical
functions. A function in mathematics should always produce the same result on receiving the same
argument. In procedural languages, the flow of the program runs through procedures, i.e., the control
of program is transferred to the called procedure. While control flow is transferring from one
procedure to another, the program changes its state.

In procedural programming, it is possible for a procedure to produce different results when it is called
with the same argument, as the program itself can be in different state while calling it. This is a
property as well as a drawback of procedural programming, in which the sequence or timing of the
procedure execution becomes important.

Functional programming provides means of computation as mathematical functions, which produces

results irrespective of program state. This makes it possible to predict the behavior of the program

39
 THIRD EYE

• Component Diagram

Fig 11: Component Diagram

40
 THIRD EYE

• UI Screenshots

Home Page/ User View

Fig 12: Home Page

Monitor Page

Fig 13: Monitor Page

41
 THIRD EYE

Identify Page

Fig 14: Identify Page

Record

Fig 15: Record Page

42
 THIRD EYE

In/Out

Fig 16: In/OUT Page

IN Output

Fig 17: In Results

43
 THIRD EYE

Out Output

Fig 18: Out Results

Record Output

Fig 19: Record Results

44
 THIRD EYE

Monitor Output

Fig 20: Monitor Results

Identify Output

Fig 21: Identifier Results

45
 THIRD EYE

Coding Screenshots

Fig 22: Coding 1

Fig 23: Coding 2

46
 THIRD EYE

Fig 24: Coding 3

Fig 25: Coding 4

47
 THIRD EYE

CHAPTER 6 - TESTING OBJECTIVE

Software testing is a critical element of the software development cycle. The testing is essential for
ensuring the Quality of the software developed and represents the ultimate view of specification,
design and code generation. Software testing is defined as the process by which one detects the defects
in the software. Testing is a set of activities that work towards the integration of entire computer-based
system. A good test case is one that has a high probability of finding an as-yet undiscovered error. A
successful test is one such uncovers or finds such errors. If testing is conducted successfully, it will
uncover errors in the software. It also demonstrates that software functions are being performed
according to specifications and also behavioral and performance requirements are satisfied. For this,
test plans have to be prepared. The implementation of a computer system requires that test data has to
be prepared and that all the elements in the system are tested in a planned and efficient manner.
Nothing is complete without testing, as it is vital success of the system.

• Testing Objectives

There are several rules that can serve as testing objectives. They are:
o Testing is process of executing a program and finding a bug.
o A good test case is one that has a high probability of finding an undiscovered.
o A successful test is one that uncovers an undiscovered error.

If testing is conducted successfully according to the objectives as stated above, it would uncover errors
in the software. Also testing demonstrates that software functions appear to the working according to
the specification, that performance requirements appear to have been met.

• Types of Testing
➢ Unit Testing

Unit testing is carried out screen-wise, each screen being identified as an object. Attention is diverted
to individual modules, independently to one another to locate errors. This has enabled the detection of

48
 THIRD EYE

errors in coding and logic. This is the first level of testing. In this, codes are written such that from one
module, we can move on to the next module according to the choice we enter.

➢ System Testing

In this, the entire system was tested as a whole with all forms, code, modules and class modules.
System testing is the stage of implementation, which is aimed at ensuring that the system works
accurately and efficiently before live operation commences. It is a series of different tests that verifies
that all system elements have been properly integrated and perform allocated functions. System testing
makes logical assumptions that if all parts of the system are correct, the goal will be successfully
achieved. Testing is the process of executing the program with the intent of finding errors. Testing
cannot show the absence of defects, it can only show that software errors are present.

➢ Integration Testing

This testing strategies combines all the modules involved in the system. After the independent modules
are tested, dependent modules that use the independent modules are tested. This sequence of testing
layers of dependent modules continues until the entire system is constructed.

Though each module individually, they should work after linking them together. Data may be lost
across interface and one module can have adverse effect on another. Subroutines, after linking, may
not do the desired function expected by the main routine. Integration testing is a systematic technique
for constructing program structure while at the same time, conducting test to uncover errors associated
with the interface. In the testing the programs are constructed and tested in the small segments.

• Testing Approach
➢ White Box Testing

White box testing is the detailed investigation of internal logic and structure of the Code. To perform
white box testing on an application, the tester needs to possess knowledge of the internal working of
the code. The tester needs to have a look inside the source code and find out which unit/chunk of the
code is behaving inappropriately.

49
 THIRD EYE

➢ Black Box Testing

The technique of testing without having any knowledge of the interior workings of the application is
Black Box testing the tester is oblivious to the system architecture and does not have access to the
source code. Typically, when performing a black box test, a tester will interact with the system's user
interface by providing inputs and examining outputs without knowing how and where the inputs are
worked upon.

• Validation

All the levels in the testing (unit, integration, system) and methods (black box, white box) are
implemented on our application successfully and the results obtained as expected.

• Limitation
The execution time for support vector machine is more so that the user may not receive the result fast.

• Test Result

The testing is done among the team members and by the end users. It satisfies the specified
requirements and finally we obtained the results as expected.

• Test Plans
The test plan covers the details of the testing process of the project, i.e., “Third EYE”. It deals with all
the testing needs for our project that are required at present.

➢ Test Case Pass/Fail Criteria

Test Case Pass/Fail criteria for our project clearly states that:
o If the function takes input and provides the exact required output, “Test case Pass”.
o If required output is not obtained, “Test case Fail”.

50
 THIRD EYE

➢ Test Cases

Test case ID TC01

Test Case name Main

System Third Eye

Action Expected System Response Pass/fail

Starting the main application GUI should be visible Pass

Fig 26: Result of Test Case 1

51
 THIRD EYE

Test case ID TC02

Test Case name monitor

System Third Eye

Action Expected System Response Pass/fail
Click on Monitor Button Camara should open and detect motion and object Pass

Fig 27: Test Case 2

Fig 28: Result of Test Case 2

52
 THIRD EYE

Test case ID TC03

Test Case name In-Out

System Third Eye

Action Expected System Response Pass/fail
Camara should open and detect the
Click on In-Out Button Pass
motion in left or right direction

Fig 29: Test Case 3

53
 THIRD EYE

Fig 30: Result of Test Case 3

Fig 31: Result of Test Case 3

54
 THIRD EYE

Test case ID TC04

Test Case name identify

System Third Eye

Action Expected System Response Pass/fail

Click on identify button New GUI for add and identify member appears Pass

Fig 32: Test Case 4

Fig 33: Result of Test Case 4

55
 THIRD EYE

Test case ID TC05

Test Case name record

System Third Eye

Action Expected System Response Pass/fail

Click on record button Camera will open and start recording Pass

Fig 34: Result of Test Case 5

56
 THIRD EYE

CHAPTER 7 - LIMITATION OF PROJECT

o User cannot get alert message.

o Modules needs to be operated by user manually.

o No backup option is available since all the images are stored in local drive

57
 THIRD EYE

CHAPTER 8 -FUTURE ENHANCEMENT

o Improvements can be appended by changing the existing modules or adding new modules. One

important development that can be added to the project in future is file level backup, which is

presently done for folder level.

o We can use this script and can integrate it with Arduino or raspberry pi board.

58
 THIRD EYE

CHAPTER 9 – CONCLUSION

This survey has explored almost all published fraud detection studies. It defines the adversary, the types

and subtypes of fraud, the technical nature of data, performance metrics, and the methods and

techniques. After identifying the limitations in methods and techniques of fraud detection, this paper

shows that this field can benefit from other related fields. Specifically, unsupervised approaches from

counterterrorism work, actual monitoring systems and text mining from law enforcement, and semi

supervised and game-theoretic approaches from intrusion and spam detection communities can

contribute to future fraud detection research. However, Fawcett and Provost (1999) show that there are

no guarantees when they successfully applied their fraud detection method to news story monitoring

but unsuccessfully to intrusion detection.

59
 THIRD EYE

CHAPTER 10 - REFERENCES

1) https://docs.python.org/3.12/

2) https://pypi.org/project/opencv-python/

3) https://ijrest.net/downloads/volume-4/issue-4/pid-ijrest-44201715.pdf

4) Introduction of security camera system with privacy protection into a residential area

https://pdf.sciencedirectassets.com/

60