ACLC CLASSROOM BIOMETRIC SECURITY AND ENERGY SAVING SWITCH USING

ARDUINO

Version: Version: 1.0 Series of 2022

Berse, Jhon Ivan S.

Ebina, Frederick C.

Montejo, Aurelio B.

Approval date: March 10, 2022

Table of Contents

1 Overview 1
1.1 Scope 1
1.2 Identification 1
1.3 System Overview 1
1.3.1 Operational Concept 1
1.3.2 Computer Software Configuration Items 1
1.4 Relationship to Other Plans 1
2 Reference Documents 2
3 Overview of Software Development Planning 2
3.1 Requirements and Development 2
3.2 Project Documentation 2
3.3 System Life Cycle 2
3.4 Schedules and Resources 3
3.5 Training Requirements 3
4 General Software Development Activities 3
4.1 Development Process 3
4.2 Development Methods 3
4.3 Product Standards 3
4.4 Reusable Products 3
4.4.1 Incorporating Reusable Products 3
4.4.2 Developing Reusable Products 3
4.5 Critical Requirements 3
4.6 Computer Hardware Resource Utilization 4
5 Detailed Software Development Activities 4
5.1 Project Planning and Oversight 4
5.2 Establishing a Software Development Environment 4
5.3 System Requirements Analysis 4
5.4 System Design 5
5.5 Software Requirements Analysis 5
5.6 Software Design 5
5.7 Software Implementation and Test/Code and Unit Test 5
5.8 Software Integration and Testing 5
5.9 System Integration and Testing 6
5.10 System Acceptance Test 6
5.11 Preparing for Software Use 6
5.11.1 Preparing for Software Transition 7
5.12 Software Configuration Management 7
5.13 Software Product Evaluation 7
5.14 Software Quality Assurance 7
5.15 Corrective Action 8
5.16 Technical and Management Reviews 8
5.17 Other Software Development Activities 8
6 Schedules and Activity Network 8
7 Program Organization and Resources 8
8 User Definitions 9

List of Acronyms and Abbreviations

CDMPConfiguration and Data Management Plan

CM Configuration Management
CSCI Computer Software Configuration Item
FDOT Florida Department of Transportation
ITS Intelligent Transportation Systems
QA Quality Assurance
SDP Software Development Plan
SEMP Systems Engineering Management Plan
SIT Systems Integration and Testing
1 Overview

This project is about creating a classroom biometric security and energy saving
switch using Arduino. This switch will be used to control the lights, fans, and other
appliances in the classroom. The switch will use biometric authentication for security,
and will provide energy saving features to reduce electricity consumption and cost. The
system will consist of an Arduino controller, a biometric scanner, and a relay switch. The
Arduino will be used to read the user’s biometric information from the scanner,
authenticate the user, and then activate the relay switch to control the lights, fans, and
other appliances. The Arduino will also monitor the energy consumption and adjust the
settings accordingly to reduce electricity consumption. The system will be easy to install
and use, and will provide an extra layer of security in the classroom. It will also help
reduce costs by cutting down on electricity consumption. This project will be a great way
to promote energy efficiency and security in the classroom.

1.1 Scope

. This project is to design and develop a classroom biometric security and energy
saving switch system using Arduino. The system will use fingerprint recognition to
identify the user and provide access to the classroom. The user will be able to turn on
the lights when they enter the classroom and the lights will be switched off automatically
when they leave the classroom. The system will also include an energy saving feature
that will turn off the lights after a certain amount of time if the user has not left the
classroom. The system will be designed to be user friendly and secure. It will also be
designed in a way that it can be easily integrated into existing classrooms.

1.2 Identification

ACLC College of Bukidnon, Classroom biometric Security and Energy Saving Switch
using Arduino Uno
Version 1.0 Series of 2022
1.3 System Overview

The Classroom Biometric Security and Energy Saving Switch Using Arduino
System is a system that combines biometric security and energy conservation in order
to optimize the efficiency of classrooms. This system uses an Arduino Uno board and a
fingerprint scanner to detect a user’s identity, and then uses an energy saving switch to
activate or deactivate the power to the classroom’s lights, fans, and other electrical
systems. The system begins with a fingerprint scanner. This scanner is used to detect
the user’s identity, and the scanner is connected to the Arduino Uno board via the I2C
communication protocol. The Arduino Uno is programmed to detect the fingerprint and
compare it to the user’s identity stored in the system’s database. Once the user’s
identity is verified, an energy saving switch is used to activate or deactivate the power to
the classroom’s lights, fans, and other electrical systems. The energy saving switch is
connected to the Arduino board via a relay, and the relay is used to control the power to
the classroom’s lights, fans, and other electrical systems. When the switch is activated,
the Arduino board sends a signal to the relay, which then turns on the power to the
classroom’s lights, fans, and other electrical systems. When the switch is deactivated,
the Arduino board sends a signal to the relay, which then turns off the power to the
classroom’s lights, fans, and other electrical systems. The system also uses a light
sensor to detect the amount of natural light in the classroom, and the light sensor is
connected to the Arduino Uno board via the analog input port. The Arduino board is
programmed to detect the amount of natural light in the classroom and then adjust the
power to the classroom’s lights, fans, and other electrical systems accordingly. This
ensures that the classroom’s lights, fans, and other electrical systems are only used
when necessary. The system also uses a temperature sensor to detect the temperature
in the classroom, and the temperature sensor is connected to the Arduino Uno board
via the analog input port. The Arduino board is programmed to detect the temperature in
the classroom and then adjust the power to the classroom’s lights, fans, and other
electrical systems accordingly. This ensures that the classroom’s lights, fans, and other
electrical systems are only used when necessary. Finally, the system is connected to a
computer via a USB port. This allows users to monitor the system’s performance and
adjust accordingly. The system also allows users to add or delete users from the
system’s database and view reports on energy consumption. Classroom Biometric
Security and Energy Saving Switch Using Arduino System is an efficient way to ensure
the security of classrooms while also conserving energy. The system is easy to install
and maintain, and provides an effective way to ensure the safety and security of
classrooms.

1.3.1 Operational Concept

The operational concept of the Aclc Classroom Biometric Security and Energy
Saving Switch Using Arduino is to provide an automated security system and
energy saving switch that can be used in classrooms. The system will be
powered by an Arduino microcontroller and will use biometric technology to
provide secure access to the classroom. The system will also be equipped with
an energy saving switch that will allow the classroom to be powered down when
not in use, thus reducing energy use. The system will require individuals to
register their biometric data, such as fingerprints or facial recognition, in order to
gain access to the classroom. This data will be stored in the Arduino, and will be
used to verify the identity of the user. If the user is verified, the system will allow
access to the classroom. The energy saving switch will be connected to the
Arduino, and will be programmed to automatically turn off the power to the
classroom when not in use. This will help to reduce energy consumption by
ensuring that the classroom is not wasting energy when not in use. Overall, the
Aclc Classroom Biometric Security and Energy Saving Switch Using Arduino will
provide an automated security system and energy saving switch for classrooms,
making them more secure and efficient.
1.3.2 Computer Software Configuration Items
1. Arduino IDE
2. Arduino Libraries
3. Breadboard
4. Relay
5. Power Supply
 6. Biometric Scanner
7. Jumper Wires
8. LEDs
9. Resistors
10. Capacitors

1.4 Relationship to Other Plans

Program management plans

The project plan for the ACLC Classroom Biometric Security and Energy Saving Switch
using Arduino is related to the program management plans in that it establishes the
timeline, objectives, and budget for the project. Program management plans provide the
framework for the project, and the project plan provides specific details about the
implementation of the project. The project plan outlines the tasks, timeline, and budget
for the completion of the project, and the program management plan provides the
overall context for the project. The project plan also identifies any risks and any
potential challenges that the project may face.
.
Systems engineering management plans (SEMP)
The ACLC Classroom Biometric Security and Energy Saving Switch using Arduino
project is related to Systems Engineering Management Plans (SEMP) in that it requires
an organized approach to the design and development of the system. The SEMP
provides a framework for the project that ensures that the system is designed in a
structured way and that the development process is managed in a disciplined and
organized manner. The SEMP also provides guidance on how to perform testing and
validation of the system, as well as how to ensure that the system meets all the
requirements of the customer. The SEMP also provides guidance on how to ensure that
the system is secure and reliable. Finally, the SEMP provides guidance on how to
ensure that the system is cost effective and meets all the necessary safety and
environmental requirements.
Hardware development plans

The development of a biometric security and energy saving switch using an Arduino is
closely linked to hardware development plans. The Arduino board serves as the central
control unit for the biometric security system, and its programming language is used to
create the logic and functions necessary to operate the system. The hardware design of
the energy-saving switch must be tailored to the specific requirements of the biometric
security system and must be able to effectively detect various biometric characteristics
and provide the necessary security features. Additionally, the energy-saving switch
must also be designed to be energy-efficient and able to automatically detect when the
system is not in use and reduce power consumption. By utilizing the same hardware
platform, the Arduino board, for both the biometric security and energy-saving switch,
the development efforts will be more streamlined and the overall cost of the system will
be reduced.
Configuration and data management plans (CDMP)

The hardware components required for this system are Arduino board, motion
detector, light sensor, and a relay switch. The Arduino board will be used as the main
processor, which will be responsible for running the main program code. The motion
detector will be used to detect motion in the area and trigger the light sensor. The light
sensor will be used to detect the amount of light in the room and determine if the lights
need to be turned on or off. The relay switch will be used to control the lights based on
the light sensor’s reading.
2 Reference Documents

This section lists the number, title, revision, and date of all documents referenced in this
plan.
NUMBER TITLE REVISION DATE

FDOT 3 ACLC CLASSROOM BIOMETRIC ACLC College of Bukidnon September 20,

SECURITY AND ENERGY SAVING CLASSROOM BIOMETRIC
documents SWITCH USING ARDUINO
SECURITY AND ENERGY 2022
SAVING SWITCH USING
ARDUINO

Project plans 1

Operational 1
procedures

Engineering 1
instructions

3 Overview of Software Development Planning

The purpose of this software development planning is to develop a classroom

biometric security and energy saving switch using Arduino. The system will be designed
to provide a secure and energy efficient solution for classrooms. The system will be
designed to be user friendly and easy to maintain.
Project Goals:
• Design and implement a classroom biometric security and energy saving switch using
Arduino.
• Design and implement a user-friendly interface for the system.
• Design and implement a secure authentication system for the classroom.
• Design and implement an energy efficient solution for the classroom.
• Test the system for functionality and accuracy.
Development Process:
• Define Requirements: The initial step in the development process will be to define the
requirements of the system. This will involve gathering the necessary information from
stakeholders such as teachers, administrators, and students.
• Design: The next step in the development process will be to design the system. This
includes creating a user interface, creating a secure authentication system, designing
an energy efficient solution, and designing the system architecture.
• Implement: The implementation phase will involve programming the system using
Arduino. This will involve writing code, testing the code, and debugging any issues.
• Test: The testing phase will involve testing the system for functionality and accuracy.
This will involve using test cases to ensure that the system is working as expected.
• Deployment: The final step in the development process will be to deploy the system.
This will involve ensuring that the system is installed correctly and that it is running
properly.
Outcomes
The outcome of this software development planning is a secure and energy efficient
solution for classrooms. The system will be designed to be user friendly and easy to
maintain. Also, the system will provide a secure authentication system and an energy
efficient solution for the classroom.

3.1Requirements and Development

System and software requirements will be documented in the requirements

database. Software requirements will be derived from the system requirements and
allocated to computer software configuration items (CSCIs). Any additional system
constraints are documented in the project’s SEMP

3.2 Project Documentation

The tool(s) used to produce this project documentation are Microsoft Word its help you
organize and write documents more efficiently, second one is Microsoft Excel enables
users to format, organize and calculate data in a spreadsheet and PDF.
.

3.3 System Life Cycle

This section describes the Classroom Biometric Security and Energy Saving Switch
using Arduino

Requirment
Analysis

Implementatio
Designing
n

Software
Developemn
t Cycle

Testing Coding

● Requirement Analysis
• Classroom Biometric Security: The system should be able to detect and
verify the identity of a person entering the classroom and provide
appropriate access to the classroom.
• Energy Saving Switch: The system should be able to detect the
presence of people in the classroom and switch off the lights and other
appliances when the room is empty.
• Arduino: The system should be able to use an Arduino microcontroller to
control the biometric security feature and energy saving switch.
● Implementation/Coding
● In this stage the components will code all the necessary implementations
needed for the completion of the system. The database needed for the
 website will also be connected to the website for the security and record of
the website.

● Testing
For testing the classroom biometric security and energy saving switch using
Arduino, you should first check the power supply of the Arduino board. Ensure that it
is connected to a reliable power source and that the voltage is within the required
range. Next, connect the Arduino board to a PC and upload the code. Once the code
is uploaded, you should run the code and check if the biometric security system is
working correctly. For example, if you have set a certain threshold for authentication,
it should be successfully authenticated. Once the biometric security system is
working correctly, you can test the energy saving switch. First, connect the switch to
the Arduino board and upload the code. Then, you can test the switch by turning on
and off the power. Make sure that the switch is working correctly and that the energy
saving mechanism is activated when the switch is turned on. Finally, check if the
Arduino board is working correctly and that all connections are secure. Then, you
can test the entire system again to ensure that everything is working properly.
● Deployment
The deployment of a classroom biometric security and energy saving switch
using Arduino can be done in the following steps:

1. Setting up the Arduino board: The first step is to set up the Arduino board. This will
involve connecting the board to a power source, installing the necessary software, and
connecting the board to the network.

2. Setting up the biometric security system: The next step is to set up the biometric
security system. This will involve connecting the fingerprint reader and other biometric
components to the Arduino board.

3. Setting up the energy-saving switch: The third step is to set up the energy-saving
switch. This will involve connecting the switch to the Arduino board and programming it
to turn off the lights or other devices when the classroom is not in use.
4. Setting up the network: The fourth step is to set up a network connection between the
Arduino board and the classroom's computers. This will involve connecting the Arduino
board to the classroom's Wi-Fi router and configuring the router to allow the Arduino
board to access the classroom's computers.

5. Programming the Arduino board: The final step is to program the Arduino board with
the necessary code. This will involve writing the code to enable the biometric security
system and the energy-saving switch to work together.

3.4 Schedules and Resources

This section provides the detailed schedule for the project. The schedule depicts the
assigned personnel as well as the critical path and any critical dependencies.

Assigned Part of the Project Duration

John Ivan Berse System UI August to November 2022
Aurelio B Montejo Jr. System’s Multiple Functions November 2022
Ebina, Frederick C. Login/Registration November 13 to 27, 2022

John Ivan Berse Admin UI October To November 2022

Note: Still in the process

3.5 Training Requirements

This section defines the software development training requirements for the project
software engineers.
Software:
1. Python - it is a powerful programming language that is simple to learn. It has
efficient high-level data structures and an object-oriented programming
 technique that is simple but effective. Python will be used as the system's
backend language, assisting with hardware management.
2. React Native - is an open-source UI software framework. It allows developers
to use the React framework alongside native platform features to create apps
for Android, Android TV, iOS, macOS, tvOS, Web, Windows, and UWP.
React native will be used for the front end of the students’ mobile application
and the windows application for the faculty’s monitoring of classroom.
3. NodeJs - this is a JavaScript runtime that will act as the backend server and
is based on Chrome's V8 JavaScript engine. This will take care of sending
and receiving data to and from the database.
4. MySQL - is a relational database management system that is open-source.
This is where we store all the data collected.

Hardware:
1. Arduino uno - is a Microchip ATmega328P microcontroller-based open-
source microcontroller board. The board includes digital and analog
input/output pins that can be used to connect to expansion boards and other
devices. This is the main hardware of the system.
2. Fingerprint Sensor Module - these modules have FLASH memory to store
fingerprints and work with any TTL serial microcontroller or system. The
fingerprints will be registered and retrieved using this module.
3. TFT Touch Screen Display - is a combination device that includes a TFT LCD
display and a touch technology overlay on the screen. The device can both
display content and act as an interface device for the instructor to modify the
data for the information of the classroom.
4. Electrical Relay - are electrically operated switches that open and close the
circuits by receiving electrical signals from outside sources. This will be used
to attain an energy saving classroom.
 5. LCD - the liquid crystal display is an electrical display device that works by
changing the optical properties of a layer of liquid crystal by applying varied
electric voltage to it. This gadget creates the layout or interface for the big-
screen display of information about classrooms.
6. Personal Computer - it's a general-purpose computer whose size,
capabilities, and initial sale price make it suitable for individuals, and it's
designed to be operated directly by the end-user without the need for a
computer operator. The employees will utilize this to gain access to the data
and manipulate it.

4 General Software Development Activities

4.1 Development Process

This section describes the software development process to be used. It also identifies
planned software builds, their objectives, and the software development activities to be
performed in each build.
Specifically, the researchers aim the following objectives:

● To develop a system that will allow electronic conduct of SSC elections.

● To reduce the manual workloads and paper works involved during the election
process.
● To increase the security and reliability of the election.
● To ensure high accuracy and validity of results of the election.
● To eliminate human errors and biases during the election.
● To introduce a fast and fair election process.
● To evaluate the system in terms of user acceptability, effectiveness,
dependability, timeliness, and quality
\
4.2 Development Methods

This section identifies the software development methods (e.g., object-oriented

methodology, etc.) to be used. It includes descriptions of the manual, automated tools,
and procedures to be used in support of these methods.
Requirement
Analysis Design Coding Testing Operationa
Gatherimg

Close Chevron Process is used in software development processes. This project

is being created into two semesters. In the first semester We discussed the software
and hardware requirements for finishing this website in the first semester, as well as the
type of computer language we'll be using for this project. After determining the
requirements, we examine the system's flow to determine how we can make it
functional and user-friendly for all users. Then we go on to the design phase, where we
consider how the user interface (UI) will seem and whether it is clear to all users. The
usability of the website's features is also considered.

Coding, testing, and operations are all progressing in the second semester. The
coding is already underway at the start of the semester. At this point, the website's
design is complete, and its functionalities are being added. The languages utilized here
are JavaScript, CSS, and HTML. If any faults or errors are discovered during the testing
phase, the website will go through a re-coding step and be checked once more until the
intended result is obtained. The testing part of the process is when we test if there are
bugs and errors if it is deployed in the environment. Last but not least, the operation
phase, during which we will launch the website in a real-world setting for student use,
For the security of the data in the database, website maintenance is necessary after it
has been deployed.

4.3 Product Standards

This section provides reference to the standards to be followed for representing

requirements, design, code, test cases, test procedures, and test results.
 The goal of this product is to create a secure and energy efficient classroom
environment. This product will utilize biometric security and energy saving features to
ensure that the classroom environment is safe and secure. The product must meet the
following standards:
1. Security: The system must be able to accurately identify authorized users and
prevent unauthorized access. It must be able to detect any attempts to gain
unauthorized access and alert the appropriate personnel.
2. Energy Efficiency: The system must have the ability to detect when a classroom is
not in use and automatically turn off the lights, HVAC system, or other electrical
devices.
3. User Friendly: The system must be easy to use and understand. It should have a
user-friendly interface that is simple to navigate and use.
4. Reliability: The system must be reliable and able to function properly in all conditions.
It should not be subject to frequent breakdowns or malfunctions.
5. Durability: The system must be able to withstand frequent use and the inevitable
wear and tear of a classroom environment. It should be able to withstand any potential
damage or abuse that may occur in a classroom setting.

4.4 Reusable Products

The Arduino Uno is a microcontroller board based on the ATmega328P. It has 14

digital input/output pins (of which 6 can be used as PWM outputs), 6 analog inputs, a 16
MHz ceramic resonator, a USB connection, a power jack, an ICSP header, and a reset
button. It contains everything needed to support the microcontroller; simply connect it to
a computer with a USB cable or power it with a AC-to-DC adapter or battery to get
started. This project is to design an Arduino-based classroom biometric security and
energy saving switch.
 The goal of the project is to design a system that can control access to a classroom,
while also reducing energy consumption. The system will be based on a fingerprint
sensor along with an energy-saving relay switch that will be triggered when the user's
fingerprint is verified.
The fingerprint sensor will be connected to the Arduino Uno, and the Arduino will
be connected to the relay switch that will be used to control the power to the classroom
lights. The user's fingerprint will be scanned and compared with a database of stored
fingerprints. If the fingerprint matches the stored fingerprint, the relay switch will be
activated and the lights will be turned on or off as desired.

4.4.1 Incorporating Reusable Products

This section describes the approach to be followed for identifying, evaluating, and
incorporating reusable software products, including the scope of the search for such
products and the criteria to be used for their evaluation.

This project introduces a classroom security and energy saving switch using
Arduino, incorporating reusable products. The security aspect of the project involves a
biometric scanner integrated with a secure access control list (ACL). This biometric
scanner is used to authenticate the user, who is then given access to the classroom.
The energy saving aspect of the project is implemented by using an Arduino-based
programmable time switch, which can be programmed to turn off the lights and other
appliances when the classroom is not in use. The project also uses reusable
components such as a breadboard, a power supply module, a relay, and LED lights.

4.4.2 Developing Reusable Products

This section describes the approach to be followed for identifying, evaluating, and
reporting opportunities for developing reusable software products.
 The project proposes to develop a classroom biometric security and energy saving
switch using Arduino which will be a device that can be used to secure a classroom, as
well as save energy by switching off the lights and other appliances when the classroom
is not in use. The device will be designed and programmed using Arduino, and will
include a biometric scanner. The biometric scanner will be used to identify authorized
users and grant them access to the classroom. It will also be able to detect when the
room is empty and will switch off the lights and other appliances. The device will be
reusable and can be used in different classrooms with minimal setup time. It will be
powered by a rechargeable battery. The project has the potential to save energy,
reduce electricity bills and provide better security in classrooms.

4.5 Critical Requirements

This section describes the approach to be followed for handling requirements

designated critical. For example:

● Safety assurance
This project aims to develop a classroom biometric security and energy
saving switch using Arduino. The system will be designed to ensure the safety of
the students and staff in the classroom by using biometric authentication. It will
also be designed to save energy by automatically turning off the lights and other
electrical appliances when the classroom is not in use. Also provide a secure and
energy efficient classroom environment for students and staff. It will also help to
reduce the amount of energy consumed in the classroom, thus helping to reduce
the school’s utility bills.
● Security assurance
The proposed system is designed to provide a secure and energy efficient
classroom environment. The system uses a biometric security system to
authenticate users and a switch to control the energy consumption of the
classroom. The biometric security system uses an Arduino microcontroller to
read and store the biometric data of the user. The data is then compared with the
 stored data to authenticate the user. The switch is used to control the energy
consumption of the classroom. The switch is connected to the Arduino
microcontroller and is programmed to turn off the lights and other appliances
when the user leaves the classroom. This helps to reduce the energy
consumption and save energy. The system also provides a secure environment
as only authenticated users can access the classroom.

● Privacy assurance
should be provided to all users of the biometric security and energy saving
switch, informing them of their rights and responsibilities regarding the use of the
biometric data.
● Assurance of other critical requirements
In order to ensure the security and energy saving of the ACLC classroom
biometric security and energy saving switch using Arduino, the following critical
requirements must be met:
1. User authentication: The system must be able to authenticate the user and
verify their identity before allowing access to the classroom.
2. Data security: The system must be able to protect the data stored in the
system from unauthorized access.
3. Access control: The system must be able to control who has access to the
classroom and when they can access it.
4. Energy efficiency: The system must be able to reduce energy consumption by
automatically turning off lights and other appliances when not in use.
5. Reliability: The system must be reliable and able to withstand any
environmental conditions.
6. Maintenance: The system must be easy to maintain and troubleshoot.
7. User interface: The system must have an intuitive user interface that is easy to
use.
8. Cost-effectiveness: The system must be cost-effective and provide value for
money.
4.6 Computer Hardware Resource Utilization

This project aims to develop a classroom biometric security and energy saving
switch using Arduino. The system will be able to detect the presence of authorized
personnel in the classroom and will be able to control the lighting and other electrical
appliances in the classroom. The system will also be able to save energy by
automatically switching off the lights and other electrical appliances when the classroom
is empty.

5 Detailed Software Development Activities

1. Designing the system architecture: This involves designing the overall system
architecture, including the hardware and software components, and the communication
protocols between them.
2. Developing the user interface: This involves designing the user interface for the
system, including the user interface for the biometric authentication, the energy saving
switch, and the control panel.
3. Developing the biometric authentication system: This involves developing the
software for the biometric authentication system, including the algorithms for facial
recognition, fingerprint recognition, and iris recognition.
4. Developing the energy saving switch: This involves developing the software for the
energy saving switch, including the algorithms for detecting motion and controlling the
power supply.
5. Developing the control panel: This involves developing the software for the control
panel, including the algorithms for controlling the system and displaying the status of the
system.
6. Testing and debugging: This involves testing the system to ensure that it is working
properly and debugging any errors that may occur.
7. Deployment: This involves deploying the system in the classroom and ensuring that it
is working properly.
 5.1 Project Planning and Oversight

This section describes the approach to be followed for project planning and oversight.

● Software development planning

The development of this system will involve the following steps:
1. Designing the system architecture: This will involve designing the components
of the system, such as the Arduino microcontroller, the biometric reader, the
relay, and the power switch.
2. Developing the software: This will involve writing the code for the Arduino
microcontroller to control the biometric reader, the relay, and the power switch.
3. Testing the system: This will involve testing the system to ensure that it is
working correctly and that it is secure.
4. Deploying the system: This will involve installing the system in the classroom
and ensuring that it is working correctly.
5. Maintaining the system: This will involve monitoring the system and making
any necessary changes or updates to ensure that it is working correctly.
● Computer software configuration item test planning
Establish Test Environment The first step in creating a test plan for the ACLC
classroom biometric security and energy saving switch using Arduino is to
establish the test environment. This includes determining the hardware and
software requirements for the system, as well as the physical environment in
which the system will be tested. This will ensure that the system is tested in a
realistic environment that will accurately reflect how it will be used in the
classroom.
Develop Test Cases The next step is to develop test cases. These test cases
should cover all aspects of the system, including the biometric security, energy
saving switch, and Arduino programming. The test cases should be designed to
test the system's functionality, reliability, and security.
 Execute Tests Once the test cases have been developed, the next step is to
execute the tests. This includes setting up the test environment, running the
tests, and recording the results. The results should be analyzed to determine if
the system meets the requirements and performs as expected.
Analyze Results The results of the tests should be analyzed to identify any
issues or areas of improvement. If any issues are identified, they should be
addressed and the system should be re-tested to ensure that the issues have
been resolved. Document Results Finally, the results of the tests should be
documented. This includes documenting any issues that were identified, as well
as any changes that were made to the system. This documentation will be useful
for future reference and for troubleshooting any issues that may arise.
● System test planning
Test Environment: The test environment should include the following
components: • Arduino board
• Biometric reader
• Relay switch
• Power supply
• Computer
Test Plan: The test plan should include the following steps:
• Set up the Arduino board and connect it to the biometric reader, relay switch,
and power supply.
• Program the Arduino board to read the biometric data from the reader and
control the relay switch.
• Test the system by having a user enter their biometric data into the reader
• Verify that the system is able to read the biometric data and control the relay
switch accordingly.
• Test the system with multiple users to ensure that it is able to recognize
different biometric data and control the relay switch accordingly.
● Software installation planning
1.Install the Arduino IDE software on the computer.
2. Download the Arduino library for the biometric security and energy saving
switch.
3. Connect the Arduino board to the computer via USB.
4. Upload the Arduino code to the board.
5. Connect the biometric security and energy saving switch to the Arduino board.
6. Test the biometric security and energy saving switch to ensure it is working
correctly.
7. Update the Arduino code as needed.
8. Deploy the biometric security and energy saving switch in the classroom.
● Software transition planning
The transition to using a biometric security and energy saving switch in the
classroom can be a complex process. To ensure a successful transition, it is
important to plan ahead and create a timeline for the implementation process.

Step 1: Research and Select a Biometric Security and Energy Saving Switch The
first step in the transition process is to research and select a biometric security
and energy saving switch that meets the needs of the classroom. Consider
factors such as cost, features, and compatibility with existing systems.
Step 2: Install the Biometric Security and Energy Saving Switch Once a switch
has been selected, the next step is to install the switch. This may involve wiring
the switch, connecting it to the existing network, and configuring the settings.
Step 3: Train Staff and Students Once the switch has been installed, it is
important to train staff and students on how to use the switch. This may include
providing instructions on how to use the switch, as well as providing information
on the security and energy saving features of the switch.
 Step 4: Monitor and Adjust Once the switch is up and running, it is important to
monitor its performance and adjust settings as needed. This may involve making
changes to the security settings or energy saving features.
Step 5: Evaluate and Adjust Finally, it is important to evaluate the performance of
the switch and adjust as needed. This may involve making changes to the
security settings or energy saving features, or even replacing the switch if it is not
meeting the needs of the classroom.
● Following and updating plans, including the intervals for management review
1. Establish a timeline for the project, including the start date, end date, and any
milestones in between.
2. Identify the resources needed for the project, including personnel, materials,
and equipment.
3. Develop a budget for the project, including any costs associated with
personnel, materials, and equipment.
4. Create a project plan, including the tasks that need to be completed, the
order in which they should be completed, and the estimated time for each task.
5. Develop a risk management plan, including potential risks and strategies for
mitigating them.
6. Establish a communication plan, including who will be responsible for
communicating project updates to stakeholders.
7. Set up a system for tracking progress, including the metrics that will be used
to measure success.
8. Schedule regular management reviews of the project, including the intervals
at which they should take place.
9. Develop a plan for evaluating the success of the project, including any metrics
that will be used to measure success.
10. Develop a plan for transitioning the project to operational status, including
any steps that need to be taken to ensure a successful transition.
 5.2 Establishing a Software Development Environment

This section describes the approach to be followed for establishing, controlling, and
maintaining a software development environment.

● Software engineering environment

The software engineering environment for an ACLC classroom biometric
security and energy saving switch using Arduino would include the following
components:
1. Arduino IDE: This is the main software development environment used to write
and compile code for the Arduino board.
2. Biometric Sensor Library: This library contains the necessary code to interface
with the biometric sensor and read the user's biometric data.
3. Relay Library: This library contains the necessary code to interface with the
relay and control the switching of the energy saving switch.
4. Network Library: This library contains the necessary code to interface with the
network and send/receive data to/from the server.
5. Database Library: This library contains the necessary code to interface with
the database and store the user's biometric data.
● Software test environment
The software test environment for the ACLC Classroom Biometric Security
and Energy Saving Switch using Arduino should include the following
components:
Test Harness: This is the hardware component used to connect the Arduino
board, biometric sensor, relay switch, and power supply.
Test Scripts: This is the software component used to automate the testing
process. The test scripts should include a set of instructions that can be used to
test the functionality of the system.
 Test Data: This is the data used to test the system. The test data should include
a set of biometric data that can be used to test the accuracy of the biometric
sensor.
Test Results: This is the data generated from the test scripts. The test results
should include a set of results that can be used to evaluate the performance of
the system.
● Software development library
The Arduino platform provides a comprehensive software development
library to facilitate the development of applications using the Arduino board. This
library includes a set of functions and classes that can be used to interact with
the board’s hardware components, such as the LCD display, the biometric
sensor, and the energy saving switch. The library also provides access to the
board’s analog and digital I/O pins, as well as a range of communication
protocols, such as I2C, SPI, and UART. Additionally, the library includes a set of
functions for controlling the board’s power management and clock settings.
Finally, the library includes a set of example programs that demonstrate how to
use the board’s features.
● Software development files
This repository contains the software development files for the ACLC
Classroom Biometric Security and Energy Saving Switch using Arduino. The files
include the source code for the Arduino microcontroller, the circuit diagram, and
the user manual. The source code is written in the Arduino programming
language and is designed to be used with the Arduino Uno board. The circuit
diagram is a schematic representation of the circuit used to interface the Arduino
with the biometric security system and the energy saving switch. The user
manual provides instructions on how to assemble the circuit and use the
software.
 5.3 System Requirements Analysis

This section describes the approach to be followed in system requirement analyses.

System requirements analysis processes will be performed as described in the project
SEMP.

● Analysis of user input

The table below represents the structure of the information processing
program or other process within the system. Input is used to submit data to the system
to process information and the output is the system's response upon the process.
Input Process Output
Admin  The system lets  Admin login
 Login with the admin to successfully
username login username  Display date of
and password. pickup and
and password.
 View and meeting
 Set schedules of
manage User schedules.
pickup for
information data
certifications and
saved in the
meeting
database.
requests.

User  The system lets  User login

 Sign up first to the user to login successfully
login with with the set  View attached
username and username and information
password. password after saved in the
 Request forms signing up. database.
for certifications.  Provide user
information and
save in
 database.

● Operational concept
The operational concept of the ACLC classroom biometric security and
energy saving switch using Arduino is quite simple. The system consists
of an Arduino board, which is the main control unit, and a biometric
sensor, which is used to identify the user. The user will first place their
finger on the biometric sensor, which will then scan their fingerprint to
identify the user. If the user is recognized, the Arduino will then activate
the switch and allow the user to turn on or off the light or device connected
to it. The switch will remain active for a certain amount of time, and then
automatically shut off after that time has elapsed. This will help to
conserve energy and ensure that the classroom is secure. The Arduino
board will also be connected to a computer, which will allow the user to
access the system remotely. The user can then access the settings and
adjust the settings according to their needs. This will help to ensure that
the system remains secure and efficient.

● System requirements
• Hardware:
1. Arduino Uno Board
2. Fingerprint Sensor
3. Relay Module
4. DC 12V Adaptor
5. Push Button
6. LEDs
• Software:
1. Arduino IDE
 2. Processing Software (Optional)
3. Microsoft Office (Optional)

5.4 System Design

This section describes the approach to be followed for participating in system design.

● Systemwide design decisions

The goal of this project is to create a classroom biometric security and energy
saving switch using Arduino. The system should be designed with the following
systemwide design decisions in mind:
1. Security: The system should prioritize security by ensuring that only authorized
users are able to access the classroom and its energy saving features.
2. Scalability: The system should be designed to easily scale up and down
depending on the size of the classroom.
3. Reliability: The system should be designed to be reliable in order to ensure
that the biometric security and energy saving features are always working as
expected. 4. Maintenance: The system should be designed to be easy to
maintain and troubleshoot in order to ensure that the biometric security and
energy saving features are always working as expected.
5. Usability: The system should be designed to be user friendly in order to ensure
that users are able to easily use the biometric security and energy saving
features.
 ● System architectural design

The figure above is the activity diagram Fingerprint Sensor: The sensor is the first
block of the biometric system which collects all the important data for biometrics. It is
the interface between the system and the real world. Typically, it is an image
acquisition system, but it depends on the features or characteristics required that it
has to be replaced or not.
Pre-processing: It is the second block that executes all the pre-processing. Its
function is to enhance the input and to eliminate artifacts from the sensor, background
noise, etc. It performs some kind of normalization.
Feature extractor: This is the third and the most important step in the biometric
system. Extraction of features is to be done to identify them at a later stage. The goal
of a feature extractor is to characterize an object to be recognized by measurements.
Template generator: The template generator generates the templates that are used
for authentication with the help of the extracted features. A template is a vector of
numbers or an image with distinct tracts. Characteristics obtained from the source
groups come together to form a template. Templates are being stored in the database
for comparison and serve as input for the match.
Matcher: The matching phase is performed by the use of a match. In this part, the
procured template is given to a matcher that compares it with the stored templates
using various algorithms such as Hamming distance, etc. After matching the inputs,
the results will be generated.
6 Application device: It is a device that uses the results of a biometric system. The
Iris recognition system and facial recognition system are some common examples of
application devices.

5.5 Software Requirements Analysis

TYPE SPECIFICATION

Processor Intel(R) Core (TM) i3 @ 4.2 (GHz) CPU

RAM 4GB

Storage 20 GB

Graphics card DirectX9 with WDDM 1.0 driver (optional)

Display 800x600

Hardware Specifications

TYPE SPECIFICATION
 Operating System Windows 8 or later OS

System Type 64-bit OS, x64 based processor

Software Specifications

TYPE SPECIFICATION

Network 3G/4G/Wi-Fi

Internet Speed 15Mbps

• Classroom Biometric Security: The system should be able to detect and verify
the identity of a person entering the classroom and provide appropriate access to
the classroom.
• Energy Saving Switch: The system should be able to detect the presence of
people in the classroom and switch off the lights and other appliances when the
room is empty.
• Arduino: The system should be able to use an Arduino microcontroller to control
the biometric security feature and energy saving switch.

5.6 Software Design

This section describes the approach to be followed for software design. It also defines
the entrance and exit criteria for the software design process.

● Software architecture/preliminary design

Star Biometric Feature

Processing
t Sensor Extraction
Input
Fingerprin
t Database
Enrollment

Star
t Biometric
Feature Extraction
Sensor
Test
Fingerprin
Matching
t ID:1789
 Output

The Figure 5.6.1 above is the conceptual design of how using an Arduino Uno, the
system will be able to record and store an instructor's fingerprints. The data will be
linked to a database and used for biometric security. The database will reflect when
teachers and authorized users enter the classroom

● Software detailed design

Systems

Biometric

activates the
electricity inside
Unlocks Door the classroom

Manage Class
Info

● The system's detailed design is shown in the graphic above. Our actors are the
instructors, use biometrics to unlock doors, and assign class information to that
classroom. Students will view the information provided by the lecturer.
 5.7 Software Implementation and Test/Code and Unit Test

This section describes the approach to be followed for software code and unit testing. It
also defines the entrance and exit criteria for the software code and unit test processes.

● Software code
//This code is for the Arduino based ACLC classroom biometric security and
energy saving switch.
//Define the pins to be used int switchPin = 2; int ledPin = 13; int biometricPin = 3;
//Setup the Arduino void setup() { pinMode(switchPin, INPUT); pinMode(ledPin,
OUTPUT); pinMode(biometricPin, INPUT); }
//Main loop void loop() { //Read the switch state int switchState =
digitalRead(switchPin); //Read the biometric state int biometricState =
digitalRead(biometricPin);
//If the switch is on and the biometric is authenticated, turn on the LED if
(switchState == HIGH && biometricState == HIGH) { digitalWrite(ledPin, HIGH); }
//Otherwise, turn off the LED else { digitalWrite(ledPin, LOW); } }

● Unit testing preparations

Create a test plan: This should include a list of all the components that need to
be tested, the expected outcomes, and any special instructions or
considerations.
Gather the necessary materials: This includes the Arduino board, the
biometric security system, and any other components that will be used in the
project.
Set up the environment: This includes connecting the Arduino board to the
computer, setting up the biometric security system, and any other components
that need to be connected.
 . Write the test code: This should include code to test each component of the
system, as well as code to test the overall system.
Run the tests: This includes running the code on the Arduino board and
verifying the results.
Analyze the results: This includes reviewing the results of the tests and making
any necessary changes to the code or system.
Document the results: This includes documenting the results of the tests, any
changes that were made, and any issues that were encountered.
● Performing unit testing
Unit testing is a software testing method in which individual units or
components of a software program are tested to determine if they are fit for use.
Unit testing is usually done by the developers themselves and is the first level of
testing before integration testing. The purpose of unit testing is to validate that
each unit of the software performs as designed. Unit tests can also be used to
ensure that the code meets its design and behaves as expected. Unit tests are
typically written and run as part of the development process.
● Revision and retesting
Revision and Retesting: After the initial testing, the system will be revised
and retested to ensure that it is working properly. Any issues that are identified
during the testing will be addressed and the system will be retested to ensure
that it is working properly.
● Analyzing and recording unit test results

The first step in analyzing and recording unit test results is to determine the
objectives of the test. This will help to ensure that the test is designed to
accurately measure the performance of the system. Once the objectives are
established, the test should be designed to measure the performance of the
system in a variety of conditions. This will help to identify any potential problems
or areas of improvement. Once the test is designed, the results should be
recorded. This can be done by using a spreadsheet or other data collection tool.
 The data should include the test conditions, the performance of the system, and
any other relevant information. This data should then be analyzed to identify any
areas of improvement or potential problems. Finally, the results should be
compared to the objectives of the test. This will help to identify any areas where
the system is not meeting the desired performance goals. Once any potential
problems or areas of improvement are identified, corrective action can be taken
to improve the system.

5.8 Software Integration and Testing

This section describes the software integration activities that focus on integrating
all the software components into a software element that will be further integrated with
the other elements to form the systems.
● Preparing for integration and testing: This includes the preparation of the test
environment, the development of test plans, the selection of test cases, and the
preparation of test data.
● Performing integration and testing: This includes the execution of the test cases, the
comparison of the test results with the expected results, and the identification of any
discrepancies.
● Revision and retesting: This includes the revision of the software components to fix
any discrepancies, the retesting of the revised components, and the verification of the
revised components.
● Analyzing and recording integration and test results: This includes the analysis of the
test results, the identification of any issues, and the recording of the results.

5.9 System Integration and Testing

This section describes the approach to be followed for participating in system

integration and testing (SIT). System integration testing will be conducted in accordance
with the project SEMP. The software engineer(s) will be responsible for supporting the
testing activities. These activities will include assisting with the debugging process as
problems are uncovered and correcting any software related problems. Subtopics to be
addressed include:

Independence in SIT: The software engineer(s) should be independent from the

development team and should not be involved in the development process. This will
ensure that the software engineer(s) can provide an unbiased and objective
assessment of the system.
Testing on the Target Computer System: The software engineer(s) should test the
system on the target computer system. This will ensure that the system is tested in the
same environment in which it will be used.
Preparing for SIT: The software engineer(s) should prepare for SIT by gathering all of
the necessary test data and materials. This includes any test scripts, test cases, and
test data.
Performing SIT Dry Runs: The software engineer(s) should perform SIT dry runs to
ensure that the system is functioning as expected. This will help to identify any
problems before the actual SIT is performed.
Performing SIT: The software engineer(s) should perform SIT by executing the test
scripts and test cases. The test results should be recorded and analyzed. Revision and
Retesting: If any problems are uncovered during SIT, the software engineer(s) should
revise the system and retest it. This will ensure that the system is functioning as
expected. Analyzing and Recording SIT Results: The software engineer(s) should
analyze the SIT results and record them. This will help to identify any problems with the
system and ensure that the system is functioning as expected.

5.10 System Acceptance Test

This section describes the approach to be followed for participating in system

qualification testing. System acceptance testing will be conducted in accordance with
the project SEMP. The software engineer(s) will be responsible for supporting the
testing activities. These activities will include assisting with the debugging process as
problems are uncovered and correcting any software related problems. Subtopics to be
addressed include:
The system acceptance testing process will involve the following steps:
Independence in system acceptance testing: System acceptance testing will be
conducted by an independent third party. This will help ensure that the system meets
the requirements of the project SEMP and that the system is not biased towards the
software engineer(s).
Testing on the target computer system: System acceptance testing will be
conducted on the target computer system. This will provide a realistic environment for
testing the system’s functionality.
System acceptance test preparation: Prior to the commencement of system
acceptance testing, the software engineer(s) will prepare a test plan which will include a
listing of the test cases to be executed. The test plan will also include the details of the
testing environment and the expected results.
Performing system acceptance test dry runs: The software engineer(s) will run a
series of dry runs of the system acceptance test prior to conducting the actual testing.
This will help identify any problems prior to the commencement of the actual testing.
Performing system acceptance testing: The software engineer(s) will execute the
test cases included in the test plan. Any problems which are encountered during the
testing process will be documented and corrected.
Revision and retesting: The software engineer(s) will revise the system based on the
findings of the system acceptance testing. After the revisions are made, the system
acceptance testing process will be repeated until all problems have been corrected.
Analyzing and recording system acceptance test results: After the system
acceptance testing is complete, the software engineer(s) will analyze the results and
document any issues which were identified during the testing process.
 5.11 Preparing for Software Use

This section describes the approach to be followed for preparing for software
use.
Preparing the Executable Software This involves compiling the source code, creating
the executable and packaging it into a format that is suitable for distribution. This
includes creating an installation program, if necessary.
Preparing Version Descriptions for User Sites This involves creating a version
description that includes any changes made to the software, such as bug fixes, feature
additions, etc. The version description should also include instructions on how to install
and use the software.
Preparing User Manuals This involves creating user manuals that provide step-by-
step instructions on how to install and use the software. The user manual should also
include troubleshooting information and contact information for technical support.
Installing at User Sites This involves physically installing the software at the user
sites. This includes setting up the necessary hardware and any other required
components.

5.11.1 Software Transition

This section describes the approach to be followed for preparing for software transition.
Software transition consists of the preparation of all software files, including source and
executables, for delivery, and updating the final version descriptions. All files will be
identified and verified via recompilation and/or reference checking after that component
has successfully passed the required testing and been placed into controlled libraries
for inclusion in the software build.
● Preparing the executable software: The executable software must be tested and
verified according to the system requirements and the software requirements specified
in the software requirements specification. Any errors or discrepancies found should be
corrected and the executable software must be updated accordingly.
● Preparing source files: All source files associated with the software must be
identified, verified and stored in controlled libraries. Any discrepancies found should be
corrected and the source files must be updated accordingly.
● Preparing version descriptions for the support site: A version description must
be created and stored in the designated support site. This description must include the
version number, date, and the changes and/or improvements made to the software
since the last version.
● Preparing the “as-built” CSCI design and other software support information:
The “as-built” CSCI design must be prepared and stored in the designated support site.
This design should include all of the software components, their interfaces, and the
system architecture. Other software support information should also be prepared and
stored in the designated support site. This includes the software requirements, design
documents, test plans, and system diagrams.
● Updating the system design description: The system design description must be
updated to reflect the changes and/or improvements made to the software since the last
version.
● Preparing support manuals: The support manuals must be prepared and stored in
the designated support site. These manuals should include the software user manual,
installation guide, release notes, and other relevant information.
● Transitioning to the designated support site: The software must be transitioned to
the designated support site for storage and distribution. All files should be transferred to
the support site and the version description should be updated on the support site.

5.12 Software Configuration Management

This section describes the approach to be followed for software CM. The CM processes
and procedures are described in the CDMP.
Configuration Identification This process will be used to identify and document all
software components of the project. All components of the system and their versions
will be identified and documented to ensure that the configuration of the system is
known. Configuration Control Configuration control is used to ensure that changes to
the system are made in a controlled manner. This includes the review and approval of
all changes to the system. The change control process will be used to track and control
all changes to the system.
Configuration Status Accounting Configuration status accounting is used to keep
track of the changes that have been made to the system. This process will be used to
ensure that all changes are documented and tracked.
Configuration Audits Configuration audits are used to verify the accuracy of the
system configuration. Audits will be conducted to ensure that the system is following the
project requirements.
Packaging, Storage, Handling, and Delivery Packaging, storage, handling, and
delivery processes are used to ensure that the system is properly packaged and stored
for delivery. This process will be used to ensure that the system is properly handled and
delivered to the customer.

5.13 Software Product Evaluation

This section describes the approach to be followed for software product evaluation.
Software product evaluation will be accomplished according to the program schedules
established for the project.
In-process and final software product evaluation: In-process and final software
product evaluation will be conducted during the development and implementation of the
software product. The software product evaluation will be conducted by a team of
experts who are knowledgeable in the area of software development and security. The
evaluation will include a review of the software product requirements, design, code, and
documentation. The product will be evaluated for compliance with the security
requirements, performance, scalability, and usability.
Software product evaluation records: The software product evaluation will be
documented and stored in the project’s records. The records will include items such as
the evaluation team, criteria used for the evaluation, findings, and recommendations.
Independence in software product evaluation: The software product evaluation will
be conducted by a team of experts who are independent of the development team. The
evaluation team will have the necessary knowledge and experience required to evaluate
the software product. The evaluation team will be selected based on their experience
and qualifications.

5.14 Software Quality Assurance

This section describes the approach to be followed for software quality assurance (QA).
Software Quality Assurance (QA) is a process of ensuring that the software
developed meets the requirements and is of high quality. This process includes
software development, testing, and quality control. The main objectives of software QA
are to ensure that the software meets the customer’s requirements, is of high quality
and is defect free.
Software QA process involves the following:
● Identifying the requirements of the software
● Developing the software
● Testing the software
● Monitoring the software for defects
● Providing feedback to the developers
● Ensuring that the software meets the customer’s requirements
Product evaluations involve assessing the software to determine if it meets the
customer’s requirements, is of high quality, and is defect free. This process includes
analyzing the software’s design, functionality, usability, and performance.
Software QA records should include the following items:
● Product requirements
● Software design
● Test plans
● Test results
● Defects and their resolution

5.15 Corrective Action

This section describes the approach to be followed for corrective actions (i.e.,
problem/change reports, etc.).
1Problem/change reports should be submitted to the appropriate team leader or
supervisor.
2. The team should investigate the issue and conduct root cause analysis to
determine a corrective action.
3. The team should develop an action plan to address the issue and submit it to
the appropriate stakeholders for approval.
4. Once approved, the action plan should be implemented and monitored to
ensure effectiveness.
5. If the corrective action is not effective, the team should reassess the issue and
develop a new action plan.
6. The team should document all corrective action taken to ensure the issue is
resolved and to help prevent future occurrences.

5.16 Technical and Management Reviews

This section describes the approach to be followed for technical and management
reviews.
1. Technical Review: The technical review will involve a comprehensive review of
the design and implementation of the proposed system. This will include a review of the
hardware, software, user interface, system architecture, data access, and security. The
review will assess the system's ability to meet the requirements and objectives outlined
in the project and evaluate the system's performance and reliability.
2. Management Review: The management review will focus on the project's cost,
schedule, and quality objectives. This review will assess the project's progress in
meeting the objectives and determine the necessary resources and strategies to
achieve them. The review will also consider the project's risk management, resource
allocation, and cost/benefit analysis.

5.17 Other Software Development Activities

This section describes the approach to be followed for other software development
activities.
● Risk Management: Risk management is an essential part of any software
development. By performing a risk analysis and assessment, potential risks can be
identified and managed. This includes identifying known risks and corresponding
strategies to mitigate them.
● Software Management Indicators: Software management indicators are
important to evaluate the progress, performance and quality of the project. Some of the
indicators that can be used include complexity, size, errors, defects, development time,
cost, and user satisfaction.
● Security and Privacy: Security and privacy are extremely important when
developing a software application. The application should be designed to protect the
users’ data and to ensure that their privacy is respected.
● Subcontractor Management: Subcontractors can be used to outsource certain
tasks in order to save time and money. It is important to manage subcontractors
properly in order to ensure that the tasks are completed on time and with high quality.
● Interface with Software Independent Verification and Validation Agents:
Software independent verification and validation agents can be used to review the
software and ensure that it is functioning correctly.
● Coordination with Associate Developers: Coordination with associate
developers is essential in order to ensure that tasks are completed on time and with
high quality.
● Improvement of Project Processes: It is important to continually review and
improve project processes in order to ensure that the project is running smoothly. This
includes reviewing the software development process and identifying areas where
improvements can be made.
6 Schedules and Activity Network

This section presents the schedule information or refers to detailed software schedules
published for the project, including:
Activity Network: Activity
1: Develop Arduino 6 program and test Activity
2: Design and Implement Biometric Security and Energy Saving Switch Activity
3: Create and Test the Prototype Activity
4: Test and Validate the Performance Activity
5: Finalize the Documentation
Activity 1 → Activity 2 → Activity 3 → Activity 4 → Activity 5
Schedule: Activity Start Date End Date
1. Develop Arduino 6 program and test September 23 Oct 15, 2022
2. Design and Implement Biometric Security and Energy Saving Switch September 26
Oct 18 ,2022
3. Create and Test the Prototype November 6 November 21, 2022
4. Test and Validate the Performance November 28 November 29 2022
5. Finalize the Documentation January 5 January 6 2023
7 Program Organization and Resources

This section describes the project organization and resources to be applied in each
software build, increment, iteration, or prototype.

Table 1: Project Organization Chart

Project Manager Designer Programmer

Ebina, Frederick C. Montejo, Jr. Aurelio B. Berse, Jhon Ivan S .

Figure 1: Title
8 User Definitions

DOCUMENT REVISION HISTORY

Version
Approve Created/
Numbe Description of Change(s)
d Date Modified By
r
1.0 3/10/22 Project Tittle ALL
Berse, Jhon
Ivan S.
Montejo, Jr.
1.0 9/23/22 Features
Aurelio B.
Ebina,
Frederick C
1.0 10/21/22 Prototype