LUMOS: A Smart Solution for Classroom Automation

Software Requirement Specification

 LUMOS Software Requirement Specification

Document Issue Status

Document Issue Number:

Document ID: <Project Code>/SRS
Document Revision Number:

Prepared by Muhammed Saif C A 31/08/24

Sona MB

Sarin Shemmy

Jithin Devasia

Reviewed by Asst. Prof. Naveena <Reviewed Date>

Approved by <Name> <Approved Date>

Distribution list

Document Amendment Record

Sl. No. Issue No Revision No Date Pages Remarks

Corrected

Page 1
 LUMOS Software Requirement Specification

Contents
Contents......................................................................................................................................................2
1 Introduction.........................................................................................................................................3
1.1 Purpose........................................................................................................................................3
1.2 Scope...........................................................................................................................................3
1.3 Product / System Overview.........................................................................................................3
1.4 User Characteristics.....................................................................................................................3
1.5 Definitions, Acronyms & Abbreviations.......................................................................................3
1.6 Constraints...................................................................................................................................4
1.7 Assumptions and Dependencies..................................................................................................4
1.8 References...................................................................................................................................4
2 Functional Requirements.....................................................................................................................5
3 Non-Functional Requirements.............................................................................................................5
3.1 Performance Requirements.........................................................................................................5
3.2 Security Requirements.................................................................................................................5
3.3 Software System Attributes.........................................................................................................6
4 External Interface Requirements.........................................................................................................6
4.1 User Interfaces.............................................................................................................................6
4.2 Hardware Interfaces....................................................................................................................6
4.3 Software Interfaces......................................................................................................................7
4.4 Communication Interfaces...........................................................................................................7
5 User Acceptance Criteria.....................................................................................................................7

Page 2
 LUMOS Software Requirement Specification

6 Appendices..........................................................................................................................................7

Page 3
 LUMOS Software Requirement Specification

1 Introduction
1.1 Purpose

This SRS document defines the software requirements for LUMOS, a classroom automation
system designed to optimize energy management, enhance accessibility, and modernize
traditional classroom environments. The intended audience for this document includes
developers, project stakeholders, and academic advisors.

1.2 Scope

LUMOS aims to automate the control of classroom devices, such as lights and fans, using
IoT technologies. The system will offer features such as remote control, scheduling, voice
commands, and real-time energy monitoring. It will address inefficiencies in traditional
classrooms, enhance accessibility for differently-abled students, and promote sustainable
energy practices.

1. Hardware and software integration for automation of lighting, fans, and other electronic
devices.

2. Development of a user-friendly mobile app for authorized personnel (class

representatives, HODs, class advisors, and security personnel).

3. Implementation of accessibility features for disabled students.

4. Integration with existing classroom infrastructure and devices.

5. Energy monitoring and tracking of power consumption, with real-time data displayed on
an LCD display.

6. Display of device status (on/off) on the LCD display, allowing for easy monitoring.

1.3 Product / System Overview

● Automated Lighting Control: Adjusts lighting levels based on occupancy, time of day,
and ambient light availability.
● Energy Monitoring and Management: Tracks energy consumption, identifies areas of
inefficiency, and optimizes energy usage.
● Assistive Technology Integration: Seamlessly connects with assistive devices for
students with disabilities

Page 4
 LUMOS Software Requirement Specification

● Real-time Monitoring and Alerts: Provides instant notifications for maintenance, security,
or system errors.
● User-Friendly Interface: Offers an intuitive dashboard for teachers and administrators to
control and customize settings.
● Integration with Existing Systems: Compatible with various classroom technologies, such
as projectors and sound systems.
● Remote Access and Control: Allows authorized personnel to manage classroom settings
from anywhere.

1.4 User Characteristics

Primary Users:

1. Class Representatives: Students responsible for managing classroom resources and ensuring
smooth operations.

2. HODs (Heads of Department): Faculty members overseeing academic departments and

responsible for classroom allocations.

3. Class Advisors: Teachers or faculty members responsible for guiding students and managing
classroom activities.

4. Security Personnel: Staff responsible for ensuring campus security and monitoring classroom
access.

Secondary Users:

1. Students: Beneficiaries of the automated classroom environment, including those with

disabilities.

2. Facilities Managers: Staff responsible for maintaining classroom infrastructure and

troubleshooting technical issues.

Page 5
 LUMOS Software Requirement Specification

1.5 Definitions, Acronyms & Abbreviations

IOT: Internet Of Things:

The Internet of Things (IoT) refers to a network of physical objects embedded with sensors,
software, and other technologies, connected to the internet or other networks. These objects,
often referred to as "smart" devices, can collect, exchange, and act on data, enabling them to
interact with other devices, systems, and users.

BMS: Building Management System:

A Building Management System (BMS), also known as a Building Automation System (BAS),
is a comprehensive network of hardware and software designed to control and monitor various
building systems and services. These systems aim to enhance the operational efficiency, comfort,
and safety of a building while optimizing energy use and reducing operational costs

NodeMCU:
The NodeMCU is a popular development board that integrates the ESP8266 WiFi module,
designed for prototyping and developing IoT (Internet of Things) applications. Here’s a detailed
explanation of the NodeMCU and its features

· CPU: The core of the NodeMCU is the ESP8266 microcontroller, which features a 32-bit
RISC CPU running at 80 MHz or 160 MHz.

· Memory: It includes 64 KB of instruction RAM and 96 KB of data RAM.

· Storage: The ESP8266 has built-in flash memory (usually 4 MB) for storing firmware and data.

1.6 Constraints

Technical Constraints:

Page 6
 LUMOS Software Requirement Specification

- Hardware limitations:
- NodeMCU microcontroller capacity
- Sensor and actuator compatibility
- Integration with existing classroom infrastructure:
- Compatibility with various devices and systems
- Network connectivity and bandwidth limitations

Infrastructure Constraints:

- Classroom layout and environmental factors (e.g., lighting, temperature)

- Availability of power outlets and network connectivity

Other Constraints:

- Budget and cost limitations

- Time and scheduling constraints for implementation and training
- User acceptance and adoption of new technology

1.7 Assumptions and Dependencies

Assumptions:

1. Reliable WiFi network: The system assumes that a stable and secure WiFi network is available
in the classrooms for device communication. This means that the devices can consistently
connect to the network and transmit data without interruptions.

2. OpenAI Weather API availability: The system assumes that the OpenAI Weather API is
available and accessible for integrating weather data. This means that the API is functioning
correctly, and the necessary credentials are in place to retrieve weather data.
3. User adoption: The system assumes that users (students, teachers, staff) will adopt and use the
system as intended.
4. Maintenance and support: The system assumes that regular maintenance and support will be
provided to ensure continuous functionality.

Page 7
 LUMOS Software Requirement Specification

Dependencies:

1. Firebase for real-time data management: The system depends on Firebase as the primary
database for real-time data management. This means that Firebase is responsible for storing,
processing, and synchronizing data across devices, and the system's functionality relies on
Firebase's performance and availability.
2. NodeMCU for device control: The system depends on NodeMCU microcontrollers for
controlling and automating devices.
3. Sensor accuracy: The system depends on the accuracy and reliability of sensors for monitoring
environmental conditions.
4. Power supply: The system depends on a stable power supply for continuous operation.
5. Internet connectivity: The system depends on internet connectivity for remote monitoring and
control.
6. Software updates: The system depends on regular software updates for bug fixes, security
patches, and feature enhancements.

1.8 References

1. "IoT-based Classroom Automation System" by S. S. Rao et al. (2020)

2. "Smart Classroom: An IoT-based Approach" by A. K. Singh et al. (2019)

3. "Energy-Efficient IoT-based Automation System for Classrooms" by M. A. Hassan et al.

(2018)

4. Smart Buildings Market Report" by MarketsandMarkets (2022)

5. "IoT in Education Market Report" by ResearchAndMarkets (2022)

6. "Energy Efficiency in Buildings" by International Energy Agency (2020)

Page 8
 LUMOS Software Requirement Specification

2 Functional Requirements

2.1 Automated Appliance Control

● Remote Operation: Users can control lights and fans via the mobile app.
● Scheduling: Ability to schedule device operations based on time or events.
● Voice Control: Integration with voice assistants for hands-free operation.

2.2 Real-Time Energy Monitoring

● Usage Tracking: Monitor energy consumption of individual devices.
● Monthly Reports: Generate and send energy consumption reports.

2.3 User-Friendly Mobile Interface

● Customizable Dashboards: Users can personalize views in the app.
● Accessibility Features: Includes custom controls for differently-abled users.

Page 9
 LUMOS Software Requirement Specification

3 Non-Functional Requirements
.

3.1 Performance Requirements

● The system should support up to 50 simultaneous users.
● 95% of commands should be executed within 1 second under normal load.
3.2 Security Requirements
● Utilize encryption for data transmission between devices and the cloud.
● Implement access controls to restrict unauthorized usage of the system
3.3 Software System Attributes
● Usability: The mobile app should be intuitive and accessible.
● Scalability: The system should be scalable to manage additional classrooms.
● Reliability: The system must maintain 99.9% uptime.

Page 10
 LUMOS Software Requirement Specification

4 External Interface Requirements

4.1 User Interfaces

img 4.1 img 4.2 img 4.3

img 4.4 img 4.5

img 4.5

4.1 Hardware Interfaces

Page 11
 LUMOS Software Requirement Specification

Feature Specification

NodeMCU 2.4 GHz Wi-Fi (802.11 b/g/n, supporting

WPA/WPA2). · General-purpose input/output
(16 GPIO). · Inter-Integrated Circuit (I²C)

Delay Module Operating voltage: 6–30V DC

Delay time: 0.1 seconds–999 minutes
Output capability: DC 30V 5A or AC 220V 5A
Quiescent current: 20mA
Operating current: 50mA
Service life: More than 100,000 times
Working temperature -40°C–85°C

Temperature sensor Range:0°...100°C

Type:5 kOhm NTC-resistors Max. wire
resistance 3,3 Ohm

Breadboard Terminal strip, tie-point 630,Distribution strips,

tie-point 200,Solderless breadboard (MB-102)

4.2 Software Interfaces

Feature Specifications

Operating System Window 10 or higher, Mac OSX 10.11or

higher,linux-ubuntu

DataBase FireBase-Cloud function

FrameWork Flutter

Page 12
 LUMOS Software Requirement Specification

4.3 Communication Interfaces

1.Wi-Fi: The system uses Wi-Fi for wireless communication with devices and servers.

2.Bluetooth: The system uses Bluetooth for wireless communication with devices (optional)

5 Acceptance Criteria
1. Is the software being tested to make sure it works correctly?

● Yes.

2. Are there tests in place to check if the system meets all the requirements?

● Yes.

3. Are we checking the code to ensure it follows good practices?

● Yes.

4. Are users going to test the software before it is fully released?

● Yes.

5. Is the system tested under different conditions to make sure it performs well?

● Yes.

6.Are we making sure that the software is easy to use for everyone?

● Yes.

7. Is there a plan to fix any issues that users find during testing?

● Yes.

8. Will there be training available for users to help them understand the software?

● Yes.

Page 13