slide 7 : system overview
let's now take a closer look at the system architecture of our air quality monitoring solution. This slide
provides a visual representation of how data flows between various entities or users within the system."
The sensor, which collects air quality data, is connected to the micro-controller."
"The micro-controller facilitates communication with the web server, allowing for the exchange of data."
"The administrator interacts bidirectionally with the web server, managing system settings and accessing
data."
"The web server delivers data to the webpage, providing a user-friendly interface for data visualization."
"Finally, the webpage communicates unidirectionally with the end user, presenting air quality
information in an accessible format."
slide 8: Use case diagram
Next, we'll explore the use case diagram of our air quality monitoring system. This diagram illustrates the
various interactions between system entities and the functionalities they can perform."
The use case diagram depicts interactions between four sensor entities, a microcontroller entity, a web
server with a database entity, an administrator entity, an end user entity, and the system itself."
"Each entity is associated with specific use cases or functionalities within the system."
"For example, sensors are responsible for collecting air quality data, while the microcontroller facilitates
data transmission to the web server."
"The administrator entity can perform tasks such as system configuration and data management."
"End users interact with the system to access air quality information and visualization tools."
slide 9: entity relational diagram
Moving on, let's examine the entity relationship diagram of our air quality monitoring system. This
diagram illustrates the relationships between key entities within the system and their respective
attributes."
"The diagram includes three tables: sensor_unit, administrator, and data."
"There's a one-to-many relationship between the sensor_unit and the data tables, indicating that each
sensor unit can generate multiple data entries."
"Similarly, there's a one-to-many relationship between the administrator and the sensor_unit tables,
indicating that each administrator can oversee multiple sensor units."
"These relationships help organize and structure the data within our system, facilitating efficient data
management and system administration."
slide 10: wiring diagram
"Now, let's take a look at the wiring diagram of our air quality monitoring system. This diagram illustrates
how the hardware components are connected and configured to collect air quality data."
In this diagram, we have an ESP32 microcontroller, a breadboard, and three sensors: a BME680 sensor,
an Adafruit PMSA003I PM2.5 sensor, and an MQ-2 sensor."
"Each sensor is connected to the ESP32 microcontroller via the breadboard, with specific wiring
configurations to ensure proper data acquisition."
"The wiring diagram provides a visual guide for assembling the hardware components and establishing
the necessary connections for collecting air quality data effectively."
slide 11 : tools and resources
Now, let's discuss the tools and resources that have been instrumental in the development and
implementation of our air quality monitoring system. This slide provides an overview of the key tools and
technologies used throughout the project lifecycle."
For project management, we utilized Notion for project organization and GitHub for collaboration,
enabling seamless coordination among team members."
"In designing the user interface, we relied on Figma for prototyping and the React framework for
frontend development, ensuring an intuitive and responsive user experience."
"For software development, we utilized the Arduino IDE and Visual Studio Code as our integrated
development environments (IDEs), streamlining the coding process for the microcontroller and web
application."
"Our web server and database infrastructure were powered by Nginx and MySQL, providing robust
hosting and data management capabilities."
"For hosting services, we leveraged AWS (Amazon Web Services) to deploy and scale our application,
ensuring reliability and scalability."
"Lastly, in writing reports and documentation, we utilized LaTeX for its powerful typesetting capabilities,
enabling us to produce professional-looking documents."
