Professional Documents
Culture Documents
Chapter IV
Chapter IV
Chapter IV
This chapter delves into the design and methodologies. employed to bring the “Smart
Waste Management System: Income Generating IoT Project” to life. This comprehensive chapter
lays the foundation for understanding the development process, data gathering approach, and
Considering the potential for evolving requirements and the Importance of user Feedback
in this research. Agile Methodology appears to be the most suitable and potential Software
Development Cycle (SDLC) for this research project. It offers flexibility, adaptability, and user-
centric approach, allowing for ongoing refinement based on research findings & user feedback.
During this phase the researchers are expected to define research objectives and clearly
outline the research goals related to optimizing waste collection, promoting responsible disposal,
and generating income. Researchers will form a cross-functional team with developers, co-
expected to list all project features and functionality as user stories, prioritizing them based on
importance and user needs. Moreover, researchers will conduct early user testing with prototypes
or mockups to gather feedback and refine the design before the development begins. Finally,
finalize the design elements and system’s design, including user interface, functionality
specifications, and technical architecture, ensuring alignment with research objectives and user
needs.
During this phase the researchers break down the design elements and divide the
functionalities into smaller, achievable tasks for iterative development. During the short
development cycles (iterations), the team focuses on building specific functionalities based on
the design plan. To ensure user satisfaction, the researchers integrate user feedback through
various methods to continuously test and fine the system during iterations. Lastly, conduct unit
testing and integration testing throughout development to ensure individual components and their
After the testing phase is completed, the researchers proceed to the development phase
and initially deploy a Minimum Viable Product with core functionalities in a designated area
within the Provincial Capitol Compound. The researchers must gather feedback from the
stakeholders and users through various methods. Finally, the researchers must analyze the
gathered feedback to identify areas for important and potential new features.
Based on the analysis of user feedback and research findings, the researchers must
prioritize new features or improvements in the product. In addition, based on the feedback and
analysis, plan for future development cycles (iterations) to address identified needs and
opportunities. After the refinement and further user testing, the researchers may launch the
finalize system within the Provincial Capitol Compound for broader use.
Maintenance
Once all the previous phases are completed, the researchers will continuously monitor the
system’s performance, including data collection, functionality, and user engagement. The
researchers must address any identified issues, bugs, or performance problems promptly. Lastly,
based on ongoing user feedback and research insights, the researchers must consider
A context diagram provides a high-level view of a system and its interactions with
external entities, it is a visual representation that depicts the interactions between a system and its
external entities, providing a high-level overview of the system's boundaries and its relationships
with outside elements. In the study " Smart Waste Management System: Income Generating IoT
Project," the context diagram is used to illustrate the Smart Waste Management System as the
central component, interacting with various stakeholders such as system administrators, waste
management service providers, and waste generators. This diagram helps clarify the flow of
information and actions, highlighting how commands, updates, notifications, and waste disposal
activities are managed within the system. By presenting these interactions clearly, the context
diagram aids in understanding the system's architecture and operational dynamics, facilitating
energy initiatives.
Here is an explanation of the provided context diagram for the "Smart Waste Management
Key Components:
Smart Waste Management System: Income Generating IoT Project: This is the central system
that manages waste disposal and provides income-generating opportunities through IoT (Internet
of Things) technologies.
External Entities:
System Administrator:
Sends Commands to the System: The administrator can control and manage the system
Receives Data on System Performance: The system provides performance data back to
Updates Waste Generator’s Accounts & Points: The service provider updates the
accounts and points of waste generators based on their waste disposal activities.
Provides Notifications and Updates: The system sends notifications and updates to the
Waste Generators:
Dispose Waste: Waste generators (likely individuals or businesses) dispose of their waste
Receive Notification & Coupon: Waste generators receive notifications and possibly
Interactions:
Commands to the System: The administrator sends operational commands to the system.
System Performance Data: The system sends back performance metrics to the administrator for
evaluation.
Notifications and Updates: The system provides real-time updates and notifications to the service
Account Updates: The provider updates the waste generators' accounts and points in the system.
Notifications and Coupons: The system sends notifications and possibly coupons to encourage
The diagram illustrates the interactions between the smart waste management system and its
primary stakeholders. It highlights the flow of information and actions among system
administrators, waste management service providers, and waste generators, showing how the
system operates to manage waste effectively and incentivize participation through IoT
technology.
data model, showing entities (like waste bins, users), their attributes (like bin fullness, location),
and the relationships between them (like a bin belonging to a specific location). This research
likely doesn't directly use an ERD, as its focus is on revenue models and citizen engagement, but
an ERD could be a helpful tool during development to design the system's data structure and
different entities in a database. In this ERD for a Smart Waste Management System, there are
four main entities: Bin, WasteGenerators, Wastedisposal_event, and Coupon. Each entity has
specific attributes and relationships with other entities. Below is a detailed explanation of each
component:
Bin:
BinID (INT, PK): Primary Key, unique identifier for each bin.
Type (VarChar 50): The type of bin (e.g., recycling, general waste).
WasteGenerators:
WasteGenID (INT, PK): Primary Key, unique identifier for each waste generator.
Name (VarChar 250): Name of the waste generator (e.g., individual or business).
Wastedisposal_event:
EventID (INT, PK): Primary Key, unique identifier for each waste disposal event.
BinID (INT, FK): Foreign Key, links to BinID in the Bin entity.
entity.
Coupon:
CouponID (INT, PK): Primary Key, unique identifier for each coupon.
EventID (INT, FK): Foreign Key, links to EventID in the Wastedisposal_event entity.
Bin and Wastedisposal_event: Each bin can be associated with multiple waste disposal
waste disposal events. This relationship is represented by the Foreign Key WasteGenID
Wastedisposal_event and Coupon: Each waste disposal event can generate multiple
coupons. This relationship is represented by the Foreign Key EventID in the Coupon
Usage
This ERD is used to design and understand the database structure for a Smart Waste
Management System. By clearly defining the entities and their relationships, it helps in the
efficient organization and retrieval of data related to waste management activities. This structure
supports various functions such as tracking waste disposal events, managing bins, and rewarding
waste generators with coupons, thereby facilitating effective waste management and
DFD stands for Data Flow Diagram. It maps out the flow of data within a system,
focusing on the processes that transform data and the data stores involved. While this research on
revenue models doesn't directly utilize a DFD, creating one during system development would
be beneficial. It would help visualize how data on waste levels, collection routes, and user
behavior would be processed within the smart waste management system to generate revenue
Below is a detailed explanation of the provided DFD for the "Smart Waste Management System:
Key Components:
External Entities:
Waste Management Service Provider: The entity responsible for managing and collecting
waste.
Processes:
Smart Waste Management System: Income Generating IoT Project (Level 0): The central
system that manages waste disposal events, coupon issuance, and data related to bins and waste
generators.
Data Stores:
Bin: Stores data related to bins such as location, type, fill level, and last collection date.
WasteGenerators: Stores data about waste generators, including their identification and
account details.
Coupon: Stores information on issued coupons, including their value points, expiry dates,
and QR codes.
Data Flows:
The system stores data on this event in the Wastedisposal_event data store.
The system retrieves data from the Wastedisposal_event and Bin data stores as needed.
Generators.
The system stores data about issued coupons in the Coupon data store.
The system retrieves data from the Coupon and WasteGenerators data stores to manage
The Waste Management Service Provider sends notifications about bin fill levels.
The system retrieves bin fill level data from the Bin data store.
Usage
This DFD provides a clear and concise overview of the interactions and data flow within
the Smart Waste Management System. It helps stakeholders understand how waste disposal
events are tracked, how points and rewards are managed for waste generators, and how the
system interfaces with waste management service providers. By detailing the processes and data
stores, the DFD facilitates the design, analysis, and improvement of the system, ensuring
A use case diagram is a visual representation of the interactions between users (waste
generators, waste management service) and a system (smart waste management system). It
shows the functionalities the system offers and how users interact with it to achieve specific
goals (like reporting a full bin or receiving a coupon). This research on revenue models likely
wouldn't directly use a use case diagram, but it would be helpful during system development to
identify user interactions and functionalities relevant to features like generating revenue reports
or offering incentives.
Diagram 4.4 Use Case Diagram
A use case diagram is a visual representation that depicts the interactions between various
actors and a system, illustrating the different ways the system can be used to achieve specific
goals. The provided use case diagram is for a "Smart Waste Management System: Income
Generating IoT Project." Here's an explanation of the components and their interactions:
Actors:
System Administrator:
the system.
The entity responsible for the actual waste collection and management.
Uses the system to optimize routes, report issues, and generate reports.
Waste Generators:
Use Cases:
The system monitors the fill levels of waste bins to ensure timely collection.
Manage Users:
Dispose Waste:
The system generates optimized routes for waste collection to improve efficiency.
Generate Reports:
Generating various reports related to waste management for analysis and decision-
making.
Reporting any issues or problems with the system to ensure they are addressed promptly.
Interaction Summary:
The System Administrator plays a crucial role in monitoring bin fill levels, managing
users, generating reports, optimizing collection routes, and reporting system issues.
The Waste Management Service Provider focuses on operational aspects like monitoring
bin levels, disposing of waste, optimizing collection routes, generating reports, and
reporting issues.
Waste Generators primarily interact with the system for the purpose of disposing of
waste.
The diagram effectively outlines the responsibilities and interactions of each actor with the
smart waste management system, highlighting the system's functionalities and the roles required
Activity Diagram
An activity diagram illustrates the flow of activities within a system, showing the
sequential steps involved in a specific process. It depicts actions, decisions, and potential
alternate paths. While the revenue model research likely doesn't directly utilize an activity
diagram, creating one during development could be beneficial. It would help visualize the step-
by-step processes involved in generating revenue reports, like data collection, processing, and
report generation, or how waste collection routes are optimized based on real-time bin fill data.
An activity diagram is a type of UML diagram that represents the workflow of activities
and actions in a system. It is used to illustrate the dynamic aspects of a system by modeling the
sequence of activities and their flow of control. The provided activity diagram below for a
"Smart Waste Management System: Income Generating IoT Project" illustrates the process from
waste disposal to the collection and rewards mechanism. Here's an explanation of the diagram
components:
Roles:
Waste Generators:
Individuals or entities that produce waste and use the system to dispose of it.
The central system that handles waste management processes, including detection,
Summary
The waste generator's actions are focused on disposing of waste and receiving rewards.
The smart system handles real-time monitoring, analysis, and updating of waste data.
The waste management service provider responds to notifications for waste collection.
This activity diagram efficiently maps out the workflow and interactions between the waste
generators, the smart waste management system, and the waste management service provider,
demonstrating how the system manages waste collection and rewards participants.
HIPO (Hierarchy, Input, Process, Output) is a structured analysis and design technique
The research on revenue models likely wouldn't directly use HIPO, as it's more
concerned with the economic aspects of the system. However, during system development,
HIPO could be a valuable tool to define the functionality of different modules within the smart
waste management system. It would help break down complex processes like data processing for
revenue generation or optimizing collection routes into smaller, clearly defined steps.
Diagram 4.6 HIPO (Waste Management Service Provider)
The provided image above shows a Hierarchy Input Process Output (HIPO) diagram for the
"Smart Waste Management System: Income Generating IoT Project." The HIPO diagram
illustrates the structure and functionality of the system by breaking down its components into
inputs, processes, and outputs. This diagram is divided into two main sections: the admin
webpage and the waste disposal conceptual prototype. Each section demonstrates the hierarchical
Overview:
Smart Waste Management System: The main system interface after login.
Components:
WasteGenerators:
Process: Delete
Output: View
Wastedisposal_Event:
Input: Add
Process: Delete
Bin:
Input: Update
Process: Delete
Report:
Output: View
Coupon:
Output: View
Collection Vehicle:
Input: Add
Process: Delete
Overview:
Smart Waste Management System: The main system interface for waste disposal.
Components:
Sensor Data:
Input: Add
Color Legend:
Input (Blue): Represents the actions or data that are entered into the system.
Process (Red): Represents the operations or computations performed within the system.
Admin Webpage:
Once logged in, the admin can manage various components such as Waste Generators,
Wastedisposal Events, Bins, Reports, Coupons, Waste Collection Routes, and Collection
Vehicles.
Each component has specific input, process, and output actions. For example, Waste
The main system interface involves several subprocesses related to waste disposal.
Sensor Data is added and used for real-time fill level calculations, which then trigger the
collection process.
Display Notifications are an output process to inform relevant parties about the system
status.
This HIPO diagram provides a detailed breakdown of the system's hierarchical structure,
depicting how different components interact through inputs, processes, and outputs. It helps in
understanding the workflow and functionality of the smart waste management system from both
Gantt Chart
A Gantt chart is a bar chart that visually depicts project tasks, their durations, and
scheduling. It's useful for project planning and tracking progress. A Gantt chart could be used to
plan and schedule the development tasks, such as designing the system architecture, coding
different functionalities, and testing the system. This helps ensure the project stays on track and
meets deadlines.
Diagram 4.7 Gantt Chart