LAB LOGGER SYSTEM

MINI PROJECT REPORT SUBMITTED TO MAHATMA GANDHI UNIVERISITY,

IN PARTIAL FULFILMENT OF THE REQUIREMENTS FOR THE DEGREE OF
BACHELOR OF SCIENCE IN COMPUTER APPLICATIONS

BY,
ANITA ANTONY
Register Number:210021087249

DEPT. OF COMPUTER SCIENCE

B.V.M HOLY CROSS COLLEGE
CHERPUNKAL, KOTTAYAM 686 584
October 2023
 Department of Computer Science

BVM HOLY CROSS COLLEGE CHERPUNKAL

CERTIFICATE

Certified that the report entitled LAB LOGGER SYSTEM is a bonafide

record of the mini project work done by Ms.ANITA ANTONY (reg
no:210021087249) under our Guidance and supervision and is submitted
in partial fulfillment of the Bachelor degree in Computer
Applications,awarded by Mahatma Gandhi University, Kerala.

Mr.BINU M.B
Mrs.DITHY MARY THOMAS Head Of the Department
Project Guide Computer Science

Submitted for Project Evaluation on:

External Examiner
1.
2.
 DECLARATION

I hereby declare that the mini project work entitled LAB LOGGER
SYSTEM submitted in partial fulfillment of the requirements for the
award of the Bachelor of degree in Computer Applications from BVM
Holy Cross College, Cherpunkal , is record of bonafide work done under
the guidance of Mrs. DITHY MARY THOMAS(Ass. Prof. Department
of Computer Science) .

Name: ANITA ANTONY

Reg.No:210021087249

Place: Cherpunkal
Date:
 ACKNOWLEDGEMENT

Dedicating this mini project to the Almighty God whose

abundant grace and mercies enabled is successful completion,
we would like to express our profound gratitude to all the people
who had inspired and motivated us to make this mini project a
success. We express our heartfelt thanks to our principal Rev.
Dr. Baby Sebastian Thonikuzhy for his warming support and
suggestions in accomplishing our project. We would like to
place our deep sense of gratitude to Mr. Binu M.B (Head of the
department of Computer Applications) for his guidance in
carrying out this project work. We are profoundly grateful to
Mrs.Dithy Mary Thomas (Assistant professor of Computer
Applications department), Project guide for his valuable
guidance, suggestions and assessment throughout the project.
We also extend our sincere thanks to all other faculty members
of the department of Computer Applications for their assistance
and encouragement throughout the project. Last, but not least
we would like to thank our friends for their co-operation and
encouragement.
 ABSTRACT

The project LAB LOGGER SYSTEM helps the user organize

the records and information in a systematic way .This helps the
user to add member, update user details, searching user id, in a
simple easy manner.In the existing system ,all sorts of records
and information are related to the lab management are done
manually.The informations are recorded using pen, paper, files
etc.When it comes to access an user record it very difficult to
retrieve the data and their many drawbacks for the system as
well.

• more time is consumed

• data access is difficult
• chances of occurring errors are high
• updating and editing are difficult
 CONTENT
Page.No

1. Introduction 1
1.1. Project Overview 2
1.2. Organizational Profile 3

2. System Configuration 4
2.1. Hardware Specification 5
2.2. Software Specification 5

3. System Analysis 6
3.1. Preliminary Investigation 7
3.2. Existing System 7
3.3. Proposed System 8
3.4. Feasibility Analysis 9
3.5. Advantages of Proposed System 10
3.6. Requirement Specification 10

4. System Design 12
4.1. Introduction 13
4.2. System Flowchart 13
4.3. Database Design 16
4.4. Data Flow Diagram 22
4.5. Input Design 27
4.6. Output Design 27

5. System Development 29
5.1. Introduction 30
5.2. Menu Level Description 31
5.3. Process Specification 33
6. System Testing 35
6.1. Testing Methods 36
6.2. Test Plan Activities 39
6.3. Screen Layouts 42

7. System Implementation 47

8. Conclusion and Scope for Future Enhancement 50

9. Bibliography 53
1. INTRODUCTION

1
1.1 PROJECT OVERVIEW

The project entitled LAB LOGGER SYSTEM is a vital

tool designed to efficiently manage and monitor computer lab
operations. This software provides real-time monitoring, user
authentication, and comprehensive reporting features to enhance
resource utilization and security within the lab environment.
Key features include secure login mechanisms, resource
allocation management, remote assistance, and usage analytics.
Administrators can effectively control access, track user
activities, and receive alerts for critical events. The system
promotes accountability and compliance with regulatory
standards by recording user actions and ensuring data security.
With a scalable architecture and integration capabilities with
user directories, the software ensures optimal performance and
seamless user management. Overall, the Computer Lab Logger
System Software streamlines administrative tasks, promotes
resource efficiency, and maintains a secure and organized
computing environment in educational or research-focused
computer labs.

1.2 ORGANIZATION PROFILE

Organization Name: BVM Holy Cross College

Location: Cherpunkal, Kottayam, Kerala, India
Year of Establishment: 1995
Type of Institution: Self-financing college
Affiliation: Mahatma Gandhi University, Kottayam
Management: Holy Cross Forane Church, Cherpunkal

Vision: To be a leading institution of higher education that empowers

students to become responsible citizens and ethical professionals.

Mission: To provide quality education that promotes academic excellence,

holistic development, and social commitment.

2
Core Values:

• Academic Integrity
• Student - Centric Approach
• Social Responsibility
• Inclusiveness
• Excellence in All Endeavors

Contact Information:

• BVM Holy Cross College

• Cherpunkal, Kottayam, Kerala - 686529
• Phone: 04822 - 267520, 9446640157
• Email: [email protected]
• Website: https://bvmcollege.com/

3
2. SYSTEM CONFIGURATION

4
2.1 HARDWARE SPECIFICATION

Processor: Intel i3 11th gen

RAM: 4GB
Hard Disk: 500GB

2.2 SOFTWARE SPECIFICATION

Operating System: CentOS 7

Browser: Firefox
Front-End: HTML5, CSS 3, JavaScript ES6
Back-End: PHP 5.5.9 Database: MySQL 5.6.16
Server: XAMPP 1.8.3 -3

XAMPP 1.8.3-3

XAMPP version 1.8.3-3 is a free and open-source cross-

platform web server solution stack package developed by
Apache Friends. It includes essential components for web
development and testing, making it an ideal choice for
developers working with PHP and MySQL-based applications.

5
3. SYSTEM ANALYSIS

6
3.1 PRELIMINARY INVESTIGATION
The preliminary investigation is a problem-solving activity
that requires intensive communication between the system users
and the system developers. It does various feasibility studies. In
those studies, a rough figure of the system activities can be
obtained from which the decisions about the strategies to be
followed for effective system study and analysis can be taken.
In the preliminary investigation an initial picture about the
system working is got from the information got from the study,
the data collection methods were identified. Right from the
investigation about the system many existing drawbacks of the
system could be identified, which helped a lot the later stages of
more rigorous study and analysis of the manual system.
The most critical phase of managing system projects is
planning. To launch a system investigation, we need a master
plan detailing the steps to be taken, the peoples to be questioned
and the outcome expected. The scope of preliminary
investigation may vary from a brief one-person effort to an
extensive series of activities requiring the participation of many
individuals.
Here in the project, a detailed study of the existing system
is carried along with all the steps in the system analysis. An idea
for creating a better project was carried and the next steps were
followed.

3.2 EXISTING SYSTEM

Usually,all sorts of records and information related to lab
management are done manually, various operation such as
adding user, updating user details, searching user details,
accessing user history etc are done manually.The details of the
user are recorded using pen,paper,pencils and files. When it
comes to searching an user’s records ,the authorized peoples
handling the record storage have a hectic job of searching
manually. It is time consuming and tedious.

7
Drawback Of Existing System
 Various operation and time consuming.
 Chances of occurring error are high.
 High scale of redundancy of record.
 Often, less accurate and loss of data integrity.
 Updating or editing record is difficult.

3.3 PROPOSED SYSTEM

The main aim of this project is to computerize the
operations regarding computer lab administration. The proposed
system is a package that suits various need of computer lab
registration. The project is developed using SQL with HTML,
CSS, JavaScript as front-end. The proposed system stores
necessary information inserted through keyboard and mouse in
the hard disc of the computer and process them as and when
required for necessary output.
The difficulty of storing large amount of manual data, the
tedious work involved in extracting the desired information
from the manual file leads to the development of a
computerized system which is free from the above drawbacks of
the manual system.
In the proposed system the users have data entry screens
which are user friendly. Error in the data entry is minimized
through validation checks and message displayed whenever
necessary. The accessed time and processed time required by a
computer is very less compared to manual system. Thus the
speed of the calculation can also be increased. Accurate decision
making is also possible by the timely receipt of the required
information. Thus the cost can reduce. Since all the details are
stored in the computer, searching becomes easier. Preparation of
reports can be done easily. We can keep the information more
secretly since the computerized system is more secure, as a
result all these efficiency increases.

8
3.4 FEASIBILITY ANALYSIS
Feasibility study is performed to choose the system that
meets the performance requirements at least cost. The most
essential task performed by the feasibility analysis is the
identification description of the new system, evaluation of the
new system and selection of the best new system. In general
feasibility study of a new system proposed is practically
possible or not.
Many feasibility study are desirable for both users and
analyst. First, the study often opposes that when the feasibility
document is being prepared, the analyst is in the position to
evaluate the solution. Second the most studies to overlook the
confusion inherent in the system development.

In feasibility analysis, there are three key consideration

and they are follows:

1. Economic Feasibility: Economic feasibility is the most

frequently used method for evaluating the effectiveness of a
new system. The more commonly known as cost/benefit
analysis, the procedure is to determine the benefits and
savings that are expected from a candidate system and
compare them with the costs.

2. Technical Feasibility: Technical feasibility is performed to

check whether the proposed system is technically feasible or
not .Technical feasibility centers all existing computers .
This proposed system is technically feasible. All data are
stored in the database tables.

3. Operational Feasibility: Operational feasibility is done to

check whether the system is operationally feasible or not.
Using command button throughout the application program
enhances operation feasibility. So maintenance and
modification found to be easier.

9
3.5 ADVANTAGES OF THE PROPOSED SYSTEM
 Quick and easy to retrieve information.
 More accurate.
 Data integrity in maintained.
 Redundancy is reduced.
 More security of information.
 More efficient and reliable system.
 User friendly.

3.6 REQUIREMENT SPECIFICATION

Software Requirement Specification (SRS) is the
requirements document that provides the technical specification
for the design and development of the software. This document
enhances the system's quality of formalizing communication
between the system developer and the user and provides the
proper information for accurate documentation. A description of
each function required to solve the problem is presented in the
functional description. The behavioral description section of the
specification examines the operation of the software as a
consequence of external events and internally generated control
characteristics. Validation criteria is perhaps the most important
and ironically most often neglected section of the SRS
Specification of validation criteria acts as an implicit review of
all other requirements. The proposed system has the following
requirements:

Functional Requirements:
 System allows to store information about user.

 The system should allow user to log in with a secure

username and password.

10
 Monitor the progress of ongoing experiments.

 Access and review data logged by students for their

experiments.

 System can update and delete the record.

 System allows the user to enter new login and record details.

Non-Functional Requirements:
 Be user-friendly and accessible to all stakeholders.
 The lab logger system should be capable of integrating with
other laboratory tools or systems.

11
4. SYSTEM DESIGN

12
4.1 INTRODUCTION
System design is the process of defining the architecture,
components, modules, interface and data for a system to satisfy
specified requirements. It is a solution to an approach compared
to system analysis which is translates these “what is” orientation.
System requirements into way of making them operational. The
design phase focuses on detailed implementation of the system
recommended in the feasibility study. Planning of system or to
replace or complement an existing system. But before this,
planning should be done. It must be thoroughly understood
about the old system and determine how computers can make its
operations more effective. The importance of system design is
the quality. Design is the place where quality is fostered in the
software development. Design representation of software
provides us with that can be accessed for quality. System design
is a transaction from a user-oriented documents to a programmer
or database personal.it is creative in both art and technology.

4.2 SYSTEM FLOWCHART

The classical system flowchart approach to describing and
documenting a system will be presented. These system
flowcharts are also used in the structured approach that is, form
the general to detailed, of the system development life cycle.
Because they have been used to describe system for many years,
they are still common in many businesses.

Basic Flow chart Symbols:

Process

13
Input - Output

Connector

Off page Connector

Data Flow

14
 Start

Lab Logger System

Register
False
login

True

Admin Student
Teacher

View & add View & add

View
users details
student
details

View & delete View & add

users View login
works
details

View & update View & analyze

Search tasks
users tasks

Delete tasks

Update tasks

Logout

Stop
15
4.3 DATABASE DESIGN
The most important aspect of building an application is
the design of tables or the database schema. The data stored in
the tables must be organized in some manner,which is
meaningful. The overall objective in the process of table design
has been to treat data as an organizational, resource and as an
integrated whole. The organization of data in a database aim to
achieve three major objectives, which are given below:

 Data integration
 Data abstraction
 Data independence

Several degrees of normalization have to be applied during

the process of table design. The major aim of the process of
normalization is to reduce data redundancy and prevent losing
data integrity. Data integrity has to be converted at all levels.
Pure normalization can access problem related to storage and
retrieval of data. During the process of normalization,
dependence’s can be identified which cause serious problems
during deletion and updating. Normalizing also hope in
simplifying the structure of table. The theme behind a database
is to handle information as an integrated whole thus making
access to information easy, quick, inexpensive and flexible for
users.The entire package depends on how the data are
maintained in the system.Each table has been designed with a
perfect vision. Minor tables have been treated which through
takes much space facilitates the process of querying fast and
accurate.

PRIMARY KEY
The key which is to identify records. Also uniquely notify
the not null constraints.

16
FOREIGN KEY
The key which references the primary key, is the data
inserted in the primary key column of the table.

NORMALIZATION
Normalization is the process of efficiently organizing data
in a database. There are two goals of the normalization process:
eliminating redundant data (for example,storing the same data
in more than one table) and ensuring data dependencies make
sense (only storing related data in a table). Both of these are
worthy goals as they reduce the amount of space a database
consumes and ensure that data is logically stored.

First normal form (1NF) sets the very basic rules for an
organized database:

 Eliminate duplicative columns from the same table.

 Create separate tables for each group of related data and

identify each row With a unique column or set of
columns (the primary key).

Second normal form (2NF) further addresses the concept of

removing duplicative data:

 Meet all the requirements of the first normal form.

 Remove subsets of data that apply to multiple rows of a table

and place them in the separate tables.

Third normal form (3NF) goes one large step further:

 Meet all the requirements of the second normal form.

17
 Remove columns that are not dependent upon the primary
key.

Database Name: lab_logger

Files in relational database are called Tables. Columns of
tables represent data and rows represent the records in
conventional technology. The table design is shown below:

TABLES

Table 1 : teacher

Field Name Datatype Width Description

teacherId varchar 10 Teacher’s ID

teacherName varchar 30 Teacher’s

Name
password varchar 30 Password to
login
teacherContact decimal 10,0 Teacher’s
contact
number
email varchar 30 Email address

teacherDepartment varchar 25 Department

name

Primary Key : teacherId

18
Table 2 : student

Field Name Datatype Width Description

AdmissionNumber varchar 10 Student

admission
number
studentName varchar 30 Student name

password varchar 25 Password to

login
studentContact decimal 10,0 Student
contact
number
email varchar 30 Email address

studentCourse varchar 25 Course elected

by the student

Batch varchar 5 Batch of the

student
Year varchar 10 Course
duration of the
student
(20XX -20XX)

Primary Key : AdmissionNumber

19
Table 3 : admin

Field Name Datatype Width Description

name varchar 20 Name of

admin
email varchar 20 Email address

password varchar 8 Password to

login

Primary key: email

Table 4 : stddetails

Field Name Datatype Width Description

AdmissionNumber varchar 10 Student

admission
number
Login time 10 Login time

Date date 15 Login date

Day varchar 10 Day of login

Language varchar 15 Programming

language
Teacher varchar 30 Teacher
assigned
Logout time 10 Logout time

Foreign Key : AdmissionNumber

20
Table 5 : tasks

Field Name Datatype Width Description

no int 5 Default
number for
table
AdmissionNumber varchar 10 Student
admission
number
programno int 8 Serial number
of the
program
date date 10 Date when
the program is
executed
day varchar 10 Day when the
program is
executed
programname varchar 50 Name of the
program

language varchar 15 Programming

language

teacher varchar 25 Teacher

assigned

Primary Key : no
Foreign Key : AdmissionNumber

21
4.4 DATA FLOW DIAGRAM
A Data Flow Diagram (DFD) is a graphical representation
of the “flow” of data through an information system. A data
flow diagram can also be used for the visualization of data
processing. Data Flow Diagram is a common practice for a
designer to draw a context-level Data Flow Diagram first which
shows the interaction between the system and outside entities.

A Data Flow Diagram is a network that describes the flow

of data and processes that change, or transform, data throughout
the system. This network is constructed by using a set of
symbols that do not imply a physical implementation. It is a
graphical tool for structured analysis of the system requirements.
DFD models a system by using external entities from which data
flows to a process, which transforms the data and creates, output
data-flows which go to other processes or external entities or
files. Data in files may also flow to processes as inputs.

There are various symbols used in a DFD. Bubbles

represent the processes. Named arrows indicate the data flow.
External entities are represented by rectangles and are outside
the system such as venders or customers with whom the system
interacts. They either supply or consume data are called sinks.
Data are stored in a data store by a process in the system. Each
component in a DFD is labelled with a descriptive name,
Process names are further identified with a number.

The Data Flow Diagram shows the logical flow of a

system and defines the boundaries of the system. For a
candidate system, it describes the inputs(source), all in a format
that meet the user’s requirements. The main merit of DFD is that
it can provide an overview of system requirements, what data a
system would process, what transformations of data are done,
what files are used, and where the results flow.

22
In the normal convention a DFD has four major symbols:

It represents a processor

It represents data source or destinatiion

It represents data flow

It represents data store

LEVEL 0 - CONTEXT LEVEL

Admin

Request Response

Request Request
Lab
Teacher Student
Logger System
Response Response

23
LEVEL 1 - ADMIN

1.1 Admin

Edit admin
Admin
profile

1.2 User details

Add user teacher

User details

1.3 Teacher details

Manage teacher
Login teachers Teacher details

1.4 Student details

Manage student
Student details
Students
admin

1.5
Login details
Manage
stddetails
Login Login details
details

24
LEVEL 1 - TEACHER

2.1 Student details

Manage student
Student Student details

2.2 view details

View student student
Details view details

Login

2.3 Login details

View login
stddetails
Details Login details

teacher

2.4 Task details

View tasks tasks
details Task details

25
LEVEL 1 - STUDENT

3.1 Login details

Add login stddetails
Details Login details

3.2 Task details

Add new tasks
Tasks Task details

3.3 Login details

View login stddetails
Login details Login details

3.4 Task details

View tasks tasks
Details Task details
Student

1.5
Manage Task details
tasks
Tasks details Task details

26
4.5 INPUT DESIGN
1. Student :
• Personal Information: Name, Student ID, Batch, Contact
details,email.

• Login Details: Login & logout time,Date,Teacher,Language.

• Task Details: Program name,Language,Teacher- in-charge.

• Students: Updation & deletion of the task details .

2. Teacher :
• Student Information: View student details.

• Login Details: View student login details.

• Task Details: View the program record of each student.

Admin :
• User Management: Add, edit, or delete student and teacher
profiles.

• Admin Management: Edit the admin profile.

4.6 OUTPUT DESIGN

1. Student:
• Login Status: View login details of student.

• Program Records: View all the tasks done by the student.

27
2. Teacher:
• Student List: Display of students in the course.

• Login Details: Display the login details of the students.

• Task Records: Display the program list of the students.

4. Admin
• User Management: Confirmation of user additions or
modifications.

• Login Details: Display the login &logout details of the

students.

28
5. SYSTEM DEVELOPMENT

29
5.1 INTRODUCTION
System development is the process of defining, designing,
testing and implementing a new software application or program.
The Assignment Submission and Evaluation System
undertaking encompasses meticulous steps, starting with
requirement gathering and data collection, ensuring a systematic
approach to achieving data consistency throughout the entire
system development process.

1. Requirement Gathering:
❖ Stakeholder Collaboration:
• Engaging with key stakeholders, including students,
teachers, and administrators, to understand their unique needs
and expectations.
• Conducting interviews, surveys, and workshops to gather
insights into the desired functionalities and features.

❖ Functional and Non-Functional Requirements:

• Identifying both functional requirements (features and
capabilities) and non-functional requirements (performance,
security, and usability).
• Prioritizing requirements based on criticality and impact
on the user experience.

❖ Use Cases and User Stories:

• Developing detailed use cases and user stories to capture
the system's interactions from different user perspectives.
• Ensuring that every requirement aligns with the
overarching goals of the Assignment Submission and Evaluation
System.

2. Data Collection and Preparation:

❖ Data Sources Identification:

30
 • Identifying the sources of data, including student
information, assignment details, and grading criteria.
• Collaborating with existing educational databases or
integrating with external systems for seamless data flow.

❖ Data Schema Design:

• Designing a comprehensive data schema that reflects the
relationships between different entities, such as students,
assignments, grades, and user roles.
• Ensuring normalization to eliminate redundancy and
maintain data consistency.

❖ Data Validation and Cleansing:

• Implementing robust validation mechanisms to ensure the
accuracy and integrity of the collected data.
• Incorporating data cleansing processes to handle
inconsistencies or errors in the initial dataset.

3. Ensuring Data Consistency:

❖ Referential Integrity:
• Enforcing referential integrity constraints to maintain the
consistency of relationships between tables in the database.
• Preventing orphaned records and ensuring that each
piece of data has a valid relationship.

5.2 MENU LEVEL DESCRIPTION

The Menu Level Description for the Lab Logger System
includes the following hierarchy:

1. Student Menu:
Homepage:
• Main landing page for student to access various system
features, including enter login details, tracking.

31
New Login Details:
• Page for the student to enter the new login details when he
uses the system.
• Option to view the login details of the student.

Task Details:
• Page to enter the program list after the successful
compilation of a program.
• Options to modify the program records entered by the
student such as search,update,delete.

2. Teacher Menu:
Homepage:
• Main landing page for the teachers to view the student
details,login details,task list of the student.

Student Details:
• Option to view the student details and login details of a
particular student.
• Options to view the program records entered by the
particular student.

3. Admin Menu:
Admin Dashboard:
• Overview of the total number of registered teachers and
students.
• Quick access to user management and the details.

User Management:
• Add, edit, or delete student and teacher profiles.
• Manage user access levels and permissions.

32
5.3 PROCESS SPECIFICATION

Process specification is a method used to document,

analyse and explain the decision-making logic and formulas
used to create output data from process input data. Its objective
is to flow down and specify regulatory/engineering
requirements and procedures. High-quality, consistent data
requires clear and complete process specifications .

1. User Authentication:
Step 1: Users (students, teachers, administrators) authenticate
their identity through secure login credentials.

2. Lab Access and Activity Logging:

Step 1: Users log in to the system.
Step 2: System logs entry and exit times, tracking user activities
within the lab.

3. Incident Reporting:
Step 1: Users can report incidents or issues within the lab
environment.
Step 2: Incident details are logged, and administrators are
notified.
Step 3: Administrators can review and resolve reported incidents.

5. Security Measures:
Step 1: Continuous monitoring for unauthorized activities.
Step 2: Integration of advanced authentication methods for
enhanced security.
Step 3: Regular updates to address emerging
cybersecurity threats.

6. User Privileges:
Step 1: Admins manage user profiles (students, teachers).
Step 2: Configurable access levels for different user roles.

33
7. System Maintenance:
Step 1: Regular updates and maintenance for optimal
performance.
Step 2: Integration of new features and technologies for
continuous improvement.

34
6. SYSTEM TESTING

35
6.1 TESTING METHODS
The purpose of system testing is to identify and correct
errors in the candidate system. Testing is an important element
of the software quality assurance and represents the ultimate
review of specification, design and coding. The increasing
visibility of the software as a system element and the costs
associated with a software failure are motivated forces for well
planned, through testing. Different levels of testing were
employed for software to make an error free, fault free and
reliable.

UNIT TESTING
Unit testing focuses verification effort on the smallest unit
of software designs the module. To check whether each module
in the software works properly so that it gives desired outputs
to the given inputs. All validations and conditions are tested in
the module level in the unit test. Control paths are tested to
ensure the information properly flows into, and out of the
program unit and out of the program unit under test. In
conclusion, all error handling paths are tested. The test data was
given to each and every module in all respects and got the
desired output. Each module has been then tested to check if it
functions properly.

INTEGRATION TESTING
After testing all small units, all the small units are
integrated and then the testing process is repeated. The major
concerns of integration testing are developing an incremental
strategy that will limit the complexity of the entire actions
among components as they are added to the system. Developing
components as they are added to the system, developing an
implementation and integration schedules that will demonstrate
the viability of the evolving system. Though each program woks
individually, they should work after linking them together. This
is also referred to as interfacing. Integration testing is a
systematic technique for constructing program structure while at
the same time; it is also a conducting test to uncover errors
36
associated with interface. In the testing, the programs
are constructed and tested in small segments.

VALIDATION TESTING
The validation test can be defined by the following simple
definition, that validation succeeds when the software functions
in a manner that can be reasonably accepted by the customer.
After validation test have been conducted one of the two
possible condition exists.

 The function or performance characteristics are accepted and

confirmed to specification.
 A deviation from specification is uncovered and defining list
is created.

System validation checks the quality of the software in

both simulated (test data) and live environments (live data). First
the software goes through a phase called alpha testing, in which
errors and failures based on simulated user requirements are
verified and studied. In this system, validator fields are there in
each and every form. Validators such as Required field validator,
compare validator, Regular expression validator etc. are set in
this system and thus validation testing is conducted successfully.
Validation testing is done in almost all forms. That is, in
customer form, registration from, there are many fields where
we have to provide only numerical values. Such fields are tested
with codes which restrict the entry of characters. Also, there are
some fields where numbers should not be entered. Such fields
are also provided with code which restricts the entry of
numerical values or symbols.

SYSTEM TESTING
The important and essential part of the system
development phase, after designing and developing the software
is system testing. Theoretically, a newly designed system should
have all the parts or sub systems are in working order, but in

37
reality, each sub-system into one pool and test the whole system
to determine whether it meets the user requirements. This is the
last change to detect and correct errors before the system is
installed for user acceptance testing. The purpose of testing is to
consider all the likely variations to which it will be subjected
and then push the system to its.

VERIFICATION TESTING
Verification testing is the method to ensure that the
product satisfies the conditions those were imposed at the
starting of the development phase. It is the process of evaluating
the intermediary work products of a software development life
cycle such as verification of documents, design, code and
program to check if the developers are in the right track of
creating the final product. It is generally done before validation
testing and is done without executing the software. It uses static
testing techniques or manual activities like inspections, reviews,
breakthroughs, and Desk- checking etc. and is a low-level
exercise. When verification tests whether the product is built in
the right way, validation tests whether the product being built is
the right one.

USABILITY TESTING
This testing technique verifies the ease with which a user
can learn to operate, prepare inputs for, and interpret outputs of
a system or component. This testing process is usually
performed by end users. It includes the testing of input and
output forms. This Cyber spy was given to end users and the
software was found to be user friendly.
REGRESSION TESTING
Regression testing is the repeated testing of an already
tested program, after modification, to discover any defects
introduced or uncovered as a result of the change. It is essential
for software to be re-tested from time to time, just to make sure
that new fixes don't destroy some other part of the system.

38
Cyber spy has undergone regression testing with every
modification and bugs introduced due to changes were removed.

TESTING ENVIRONMENT & TOOLS

Debugging (Black Box Testing & White Box Testing)
Debugging helps to avoid bugs in the program. It helps to
ensure that the system produces the desired output and also
helps to identify the cases when undesired outputs are produced
so that the developers can decide how the unexpected outputs or
exceptional cases must be handled. Debugging can be done
using two testing strategies namely Black Box Testing and
White Box Testing.

Black Box Testing

Black box testing is the Software testing strategy used to
test the software without knowing the internal structure of code
or program. This means that implementation knowledge is not
required to carry out Black Box Testing. This type of testing is
carried out by testers. It is also referred to as functional test or
external testing.

White Box Testing

White box testing is the software testing strategy in which
internal structure is being known to the person testing the
software. Generally, this type of testing is carried out by
software developers. Implementation Knowledge is required to
carry out White Box Testing. It is also referred to as structural
test or interior testing.

6.2 TEST PLAN ACTIVITIES

Testing commences with the test plan and terminates with
acceptance testing. A test plan is a general document for the
entire project that defines the scope, approach to be taken and
the schedule of testing as well as identifies the items for the
entire testing process and the personal responsibilities for the

39
different activities of testing. The test planning can be done in
parallel with coding and designing activities. The inputs for
formatting a test plan are

 Project plan
 Requirements document
 System design documents

The project is needed to make same that the data plan is

consistent with the overall quality plan for the project and
testing schedule matches with that of the project plan. The
requirements documents and the design documents are the basic
documents used for selecting the text units and deciding the
approaches to be used during testing.

A test plan should contain the following activities:

 Test unit specification
 Features to be tested
 Approach for testing
 Test deliverables
 Personal allocation
One of the most important activities of the test plan is to
identify the test units. A test unit is a set of one or more modules,
together with associated data, that form a single computer
program and that are the object of testing. Test units can occur
at any level and contain from a single module to the entire
system. Thus, the test unit may be used during the testing
activity. The levels are specified in the test plan by identifying
the test units for the project. Different units are specified for unit
integration and system testing.

Features to be tested include all software features and

combinations of features that should be tested. Software may

40
include functionality, design constraints and attributes. The test
plan, if it is a document separate from the project management
plan, typically specifies the schedule that includes the amount of
time and effort to be spent on different activities of testing. This
schedule should be consistent with the overall project schedule.

41
6.3 SCRREEN LAYOUTS

Landing Page

User Login Page

42
Admin Login Page

Admin Dashboard

43
Teacher Homepage

Student Homepage

44
Student Dashboard

Login Details

45
New Program

46
7.SYSTEM IMPLEMENTATION

47
 System implementation is the process of taking a
software system from the design phase to a fully functional and
operational state. The following are common activities involved
in system implementation:

1. Installation: This activity involves installing the software

system on the hardware environment where it will be used.

2. Configuration: This activity involves configuring the

software system to meet the specific requirements of the
organization or end-users.

3. Data Migration: This activity involves transferring data

from the old system to the new system.

4. Testing: This activity involves testing the software system to

ensure that it functions as expected and meets the requirements
and specifications.

5. Training: This activity involves training end-users and

administrators on how to use the new system.

6. Documentation: This activity involves creating

documentation for the new system, including user manuals,
technical documentation, and support materials.

7. Deployment: This activity involves deploying the new

system in the production environment.

8. Maintenance: This activity involves ongoing maintenance

and support of the system to ensure that it continues to function
properly.

9. Monitoring: This activity involves monitoring the system to

identify and resolve any issues that arise.

48
10. Upgrades: This activity involves upgrading the system to
new versions or releases as they become available.

11. Support: This activity involves providing ongoing support

to end-users and administrators to address any issues that arise
and ensure the system is functioning as intended.

Successful system implementation requires careful

planning, effective project management, and collaboration
among all stakeholders. It is critical to ensure that the system
meets the requirements and specifications, is reliable and secure,
and is easy to use and maintain.

49
8. CONCLUSION AND SCOPE
FOR
FUTURE ENHANCEMENT

50
CONCLUSION
In conclusion, the Lab Logger System stands as a pivotal
tool in ensuring the efficient and secure management of
computer labs in educational institutions. By implementing
robust user authentication and comprehensive activity tracking,
this software promotes accountability among lab users and
mitigates potential security risks. The detailed reports generated
by the system offer valuable insights into lab utilization patterns,
enabling administrators to optimize resource allocation and
promptly address any irregularities. The real-time monitoring
feature further enhances the system's effectiveness, allowing for
proactive intervention in the event of unauthorized activities.
Overall, the Lab Logger System contributes significantly to the
creation of a controlled, organized, and conducive computing
environment. Its deployment empowers administrators with the
tools needed to enhance user experience, safeguard resources,
and maintain a seamless operation of computer labs, ultimately
fostering a more productive learning and research environment
within educational institutions.

SCOPE FOR FUTURE ENHANCEMENT

The Lab Logger System, while currently robust, presents
promising avenues for future enhancements. Firstly, integration
with advanced biometric authentication methods can further
strengthen user identity verification, adding an extra layer of
security. Incorporating machine learning algorithms may enable
the system to analyze user behavior patterns, helping identify
anomalies and potential security threats in real-time.
Additionally, expanding compatibility to include cloud-based
storage solutions can enhance data accessibility and scalability.
The integration of IoT devices could provide insights into the
physical state of computer equipment, allowing for predictive
maintenance and minimizing downtime. Collaborative features,
such as virtual collaborative spaces and integrated
communication tools, can transform the system into a holistic

51
platform that supports both individual and group activities.
Lastly, continuous updates to address emerging cybersecurity
threats and evolving technologies will ensure that the Computer
Lab Logger System remains at the forefront of providing a
secure and efficient computing environment in the ever-
changing landscape of educational technology.

52
9. BIBLIOGRAPHY

53
1. OpenAI: "GPT-3: Language Models for Text Generation."
https://www.openai.com

2. GeeksforGeeks: "Computer Science Portal."

https://www.geeksforgeeks.org

3. YouTube: “Various Tutorials and Educational Content."

https://www.youtube.com

54