Pir Mehr Ali Shah

Arid Agriculture University Rawalpindi

University Institute of Information Technology

FYP I – Comprehensive Survey Report

Project Title: Blockchain Integrated System for iPhone Parts Authenticity

Supervisor: Dr Rubina Ghazal Project No:

Sr. Registration No. Student Name

No.
1 21-Arid-730 Muhammad Bilal Mirza
2 21-Arid-769 Qandeel Hassnain
3 21-Arid-731 Inbsaat Zainab

a. Project Features:

The UIIT Waste Segregation System automates waste detection and classification using
CNN and OpenCV, ensuring efficient segregation into predefined categories like plastic,
paper, and organic. It features smart bins installed exclusively in the UIIT department,
managed through an admin-controlled mobile application. The system provides real-time
waste detection, secure database storage, and insightful analysis of waste disposal patterns.
Users interact with the bins for disposal, while the admin oversees operations via the app.

1. Waste Detection and Classification

 Utilizes CNN for high-accuracy waste type classification.

 Employs OpenCV for real-time image processing of waste.
 Detects and categorizes waste into predefined types like plastic, paper, and organic.
 Provides quick and efficient waste detection in under 2 seconds per item.

2. Smart Bin Integration:

  Smart bins equipped with cameras for waste image capture.
 Operates within the UIIT department for centralized waste management.
 Automatically logs waste data for analysis and monitoring.
 Ensures smooth operation with minimal user intervention.

3. Admin-Controlled Mobile Application:

 Allows admin to monitor the status of all bins in real time.

 Facilitates secure login for managing system configurations and logs.
 Enables access to detailed waste disposal reports and usage patterns.
 Provides options for system updates and performance checks.

4. Data Management and Insights:

 Stores waste data securely in a MySQL database for future use.

 Analyzes waste disposal trends to provide actionable insights.
 Offers efficient data retrieval for waste tracking and reporting.

b. Stakeholders:

1. Primary Stakeholders:

 UIIT Department Management: Responsible for overseeing the overall

implementation and success of the system, ensuring it aligns with the department's
goals for waste management.
 Admin: The key operator of the system who manages bin configurations, monitors
waste disposal logs, and ensures system performance.

2. Secondary Stakeholders:

 Students and Staff: Regular users of the smart bins for waste disposal, benefiting from
an automated and efficient waste management process.
3. Operational Stakeholders:

 System Developers: Responsible for maintaining and updating the software, ensuring
smooth operation of CNN, OpenCV, and database integrations.
 Maintenance Team: Manages the physical upkeep of the smart bins and ensures
hardware functionality.

c. Functional Requirements:

1. Waste Detection and Classification

 The system shall detect and classify waste items into predefined categories, such as
plastic, paper, and organic, using CNN and OpenCV.
 The system shall capture images of waste in real time using camera-equipped smart
bins.
 The classification process shall provide results within 5 seconds of waste disposal.

2. Admin Mobile Application

 The system shall provide a secure login interface for the admin to access and manage
the system.
 The admin shall have access to real-time bin status, including waste levels and
classification reports.
 The app shall allow the admin to update system configurations and view analytics on
waste disposal trends.
 The app shall enable the admin to retrieve and export reports from the MySQL
database for analysis.

3. Data Management

 The system shall log waste type and disposal time for every detected item in a
centralized MySQL database.
 The system shall allow the admin to search, filter, and retrieve records based on
specific criteria.
 The database shall support historical data storage for trend analysis and decision-
making.

4. System Scalability

 The system shall support 4 bins within the UIIT department.

 It shall allow future integration of additional waste categories without significant
software modifications.

d. Non-Functional Requirements:

1. Performance

 The system shall achieve an accuracy rate of 95% or higher in waste classification.
 Waste detection and classification processes shall not exceed 2 seconds per item.

2. Usability

 The mobile application shall have an intuitive and user-friendly interface requiring
minimal training for admin users.

 The system shall provide clear, error-free feedback for classification results and bin
statuses.

3. Security

 Admin login credentials shall be encrypted to ensure system access security.

 Waste data stored in the database shall be protected against unauthorized access through
robust security protocols.

4. Reliability

 The system shall operate without failure for 99.9% uptime, ensuring continuous service
for users.

 The database shall have regular backup protocols to prevent data loss.

5. Scalability and Flexibility

 The system shall accommodate increasing waste data volume and additional bins without
performance degradation.

 The system shall allow future upgrades to improve detection algorithms and add new
features.

6. Maintainability

 The system shall include modular code for easy updates to the CNN model and OpenCV
configurations.

 Logs and error reports shall be available to assist in troubleshooting and system
maintenance.

7. Accessibility

 The system shall be accessible on devices with a modern web browser or a compatible
mobile operating system.
  The admin interface shall be compliant with accessibility standards for ease of use.

e. Constraints:

1. System Constraints

 Location-Specific Installation:
The system is limited to bins installed exclusively within the UIIT department and
cannot be deployed in other departments or external locations.

 Detection Categories:
The waste classification system is designed to recognize and categorize specific types
of waste (e.g., plastic, paper, organic). Expansion to other waste types would require
additional model training.

 Hardware Limitations:
The smart bins require camera sensors and sufficient processing power for real-time
waste detection, restricting their deployment to locations with adequate infrastructure.

2. Technological Constraints

 Algorithm Dependency:
The system relies heavily on CNN for classification and OpenCV for image
processing. Poor training data or improper algorithm configurations may affect
detection accuracy.

 Database Dependency:
The system uses MySQL for data storage, which may limit scalability if the data
volume or number of bins increases beyond the predefined capacity.

 Network Requirements:
The mobile application and real-time waste detection require a stable internet
connection to ensure seamless communication between the bins and the admin
application.

3. Operational Constraints

 Admin-Only Control:
Only the admin has access to the mobile application and its features. Regular users
cannot interact with the system beyond waste disposal.

 Bin Maintenance:
Regular maintenance is required to ensure cameras and sensors in the bins are
functioning correctly, as hardware failure could disrupt the entire system.

 Processing Speed:
The system must classify waste within 2 seconds of disposal to maintain efficiency and
user satisfaction.
4. Financial Constraints

 Limited Budget:
The project is confined to a specific budget, which restricts the use of advanced
hardware or expansive infrastructure.

 Maintenance Costs:
Ongoing maintenance of bins, software updates, and hardware replacement may be
constrained by funding availability.

5. Environmental Constraints

 Indoor Deployment:
The bins are designed for indoor use within the UIIT department. Outdoor deployment
would require additional weatherproofing and durability considerations.

f. Functionality Classification:

Core Functionalities

These are essential features that enable the system's primary purpose of waste segregation and
management:

 Waste Detection and Classification:

 The system detects waste in real-time using a camera and classifies it into
categories such as plastic, paper, and organic using CNN.
 Real-Time Processing:
 The classification process is completed within 5 seconds to ensure a seamless
user experience.
 Data Logging:
 All detected waste data is stored in a centralized MySQL database for further
analysis.
 Smart Bin Operation:
 The system automatically processes the waste type and updates the bin status.

2. User Interaction Functionalities

These features define how users (admin and staff) interact with the system:

 Admin Mobile App Control:

 The admin can log in securely to monitor bin statuses and manage waste logs.
  Bin Status Monitoring:
 The system updates the admin on waste levels in bins, ensuring timely
emptying and maintenance.
 Alerts and Notifications:
 Real-time notifications are sent to the admin for critical updates, such as bin
overflows or system errors.

g. Traceability:

1. Definition of Traceability:

 Data Traceability: Tracks and logs waste detection data, including waste type,
disposal time, and bin ID.
 System Activity Traceability: Maintains logs of admin interactions, bin statuses, and
system updates for monitoring and troubleshooting.

2. Goals of Traceability:

 Accountability: Ensure the system records every waste item detected for monitoring
purposes.
 Optimization: Identify inefficiencies in waste disposal processes through historical
data analysis.
 Transparency: Provide clear records of waste segregation and disposal for
stakeholders..

3. Traceability Features:

 Unique Identification for Waste Items:

 Each waste detection instance is logged with a unique ID, including metadata such as
detection time, category, and bin ID.

 Lifecycle Tracking:

 Monitors the entire lifecycle of waste, from detection to its transfer or disposal.

 Admin Activity Logs:

 Records actions performed by the admin, such as login timestamps, system updates,
and report generations
h. Use Case Diagram:

i. Expanded Use Case:

 Login Usecase

Use Case ID: UC-1.0

Use Case Name: Login App
Actors: Admin
Description: Admin will login using valid credentials to access the system.
Trigger: The login process is triggered when the admin attempts to access the
system by providing credentials.
Preconditions: 1. Admin must be on the login page.
2. Admin must have valid login credentials (username and password).
Postconditions: Admin logged in successfully with admin credentials and granted access to
the system.

Normal Flow: 1. Admin enters login credentials (username and password).

2. Clicks the login button
3. The system verifies the credentials.
4. If credentials are correct, admin is logged in and directed to the home
page.
Exceptions: 1. If the credentials are incorrect, admin will receive an error message and
will not be able to log in.
2. Admin can retry entering the correct credentials or use forget password
option.

Register Usecase

Use Case ID: UC-1.1

Use Case Name: Register App
Actors: Admin
Description: Admin will create his/her account on the mobile app.

Trigger: The admin actives the app and selects the "Register" option to create a new
account.
Preconditions: The admin must be on Register page.
Postconditions: 1.Admin receives a message of “Your account has been created
successfully.”
2.The app navigates to login page

Normal Flow: 1.The admin actives the app and selects the "Register" option.
2.The system displays a registration form with required fields
 Name
 Email
 Phone
 Password
 Confirm Password
3.The admin fills in the form with valid information.
4.The admin submits the registration form.
5.The system validates the provided details.
6.If the details are valid, the system creates a new admin account and
displays a success message.
7.The admin is redirected to the login screen to log in with the newly
 created account.
Exceptions: 1.If the email is invalid, the system prompts for correction.
2.If the password is weak, the system asks for a stronger one.
3.If the email is already registered, the system asks to use a different one or
log in.
4.If required fields are missing, the system alerts to fill them in.
5.If there's a server error or database issue, the system asks to try again
later.

Monitor bin status Usecase

Use Case ID: UC-2.0

Use Case Name: Monitor bin status
Actors: Admin
Description: Admin uses the app to check the fill levels of the bins.

Trigger: The admin logins the app or refreshes the bin status view to check the
current fill levels of the bins.
Preconditions: 1. The admin must be logged into the system.
2. The system is operational, and sensors are working to monitor bin fill
levels.
Postconditions: The admin is informed of the current status of all bins.
Normal Flow: 1.The admin opens and logins the app.
2.Admin navigates to the home page
3.The app fetches bin status data from the system.
4.The bin status (e.g., empty, partially full, full) is displayed on the app
interface.

Exception: 1,The app fails to connect to the system due to network or server issues.
2,One or more sensors fail to report accurate data due to hardware issues.

Calculate bin status Usecase

Use Case ID: UC-2.1

Use Case Name: Calculate bin status
Actors: Ultrasonic sensor
Description: Ultrasonic sensors placed in the bins will calculate the filled level of the
respected bin in the form of percentage %.
Trigger: Filled level of the bins is calculated in the form of percentage and shown
on the app
Preconditions: 1.The ultrasonic sensors are installed and operational in the bins.
2.The system is powered on and functional.
3.The app is able to communicate with the ultrasonic sensors to retrieve
data.
Postconditions: 1.The bin’s filled level is calculated as a percentage (e.g., 0% for empty,
100% for full).
 2.The app displays the calculated percentage for each bin.
Normal Flow: 1.The ultrasonic sensor detects the distance between the sensor and the
top of the bin, based on the material inside the bin.
2.The sensor sends the distance measurement data to the system.
3.The system processes the distance data to determine the remaining
empty space in the bin
4.The system calculates the fill level of the bin by comparing the measured
distance to the total height of the bin. This gives the percentage of the bin
that is filled.
5.The calculated fill percentage is sent to the app.
6.The app displays the bin’s fill percentage on the interface (e.g., 70% full,
90% full).
Exceptions: 1.The ultrasonic sensor fails to measure the distance correctly (due to dirt,
misalignment, etc.).
2.The system fails to communicate with the sensor due to network or
hardware issues.

Alarm Notification usecase

Use Case ID: UC-3.0
Use Case Name: Receive alarm notification
Actors: Admin
Description: Admin will get an alarming notification when a bin will be 100% filled

Trigger: The app generates an alarm when a bin is full or when a malfunction is
detected.
Preconditions: 1.The bin status monitoring system is active.
2.Sensors and app notifications are configured correctly.

Postconditions: The admin is aware of the issue and can take corrective action.
Normal Flow: 1.A bin reaches its maximum capacity (100%) or a malfunction is detected.
2.The system triggers a notification to the app.
3.The app receives the notification and processes it.
4.The app generates an alarm (sound or visual) to alert the admin.
5.The admin acknowledges the alarm or takes necessary action.
Exceptions: 1. If the system fails to send a notification, the app displays an error
message.
2. If the alarm doesn't trigger, the system logs the issue and notifies the
admin.
3. If the admin doesn't acknowledge the alarm, the app repeats it at
intervals.
4. If the app doesn't receive the notification, it retries and alerts the admin
once successful.

Detection Waste Material Usecase

 Use Case ID: UC-4.0
Use Case Name: Detect waste material
Actors: Waste segregation system
Description: Sensors detect the type of waste (e.g., paper, plastic, glass) using OpenCV.

Trigger: A waste item is placed near the sensor, initiating the detection process. The
system captures and processes the material properties to identify the
waste type.
Preconditions: 1.Sensors and OpenCV are configured and calibrated correctly.
2.The waste material is placed in the detection area.

Postconditions: The waste type is identified and ready for sorting.

Normal Flow: 1.A waste item is placed near the sensor, either manually or automatically,
within the detection area.
2.The main lid is opened.
3..The sensors capture the material properties (e.g., color, texture, shape).
4. The OpenCV (Open Source Computer Vision) software processes the
captured data by applying algorithms to detect and classify the material
type, such as distinguishing between paper, plastic, metal, or other
materials based on visual characteristics.
5.The system sends the detected material type for further processing and
sorting.
6.The main lid is closed.
Exceptions: If the material type cannot be identified , the system labels it as
"unrecognized" and redirects it to a default bin.

Sort waste Usecase

Use Case ID: UC-4.1

Use Case Name: Sort waste into bin
Actors: Waste segregation system
Description: Based on the detected material type, the corresponding bin's lid opens, and
 the motor moves the material into the correct bin.
Trigger: The system detects the waste type and triggers the sorting process to
move it into the correct bin.
Preconditions: 1.The waste type is already identified by the system.
2.Motors and bin lids are functioning.

Postconditions: The waste is successfully sorted into the correct bin..

Normal Flow: 1.The system receives the detected waste type (e.g., paper, plastic, or
glass).
2.The corresponding bin lid is opened.
3.The motor moves the waste item into the correct bin.
4.The bin lid closes after the operation.
5.The material is sorted.
Exceptions: If the bin is full, the system generates an alarm and redirects the waste to a
backup bin.

Logout App

Use Case ID: UC-1.2

Use Case Name: Logout App
Actors: Admin
Description: Admin will logout from the mobile app.

Trigger: The admin logs out of the app to ensure the security of the system.

Preconditions: 1.The admin is logged into the app.

2.The app is functioning normally.

Postconditions: 1.The admin is logged out, and the app is secured.

2.Any sensitive data from the session is cleared from the device.
Normal Flow: 1.The admin navigates to the settings or menu in the app.
2.The admin selects the "Log Out" option.
3.The system terminates the current session and redirects the admin to the
login screen.
Exceptions: If the admin closes the app without logging out the system automatically
logs the admin out after a predefined period of inactivity.

Calculate bin filling time

Use Case ID: UC-2.2

Use Case Name: Calculate bin filling time
Actors: Waste segregation system
Description: The system calculates the time taken for each bin to reach its maximum
 capacity.
Trigger: The system detects a change in the bin fill level or when a bin is full.

Preconditions: 1.The system is operational, and bins are actively collecting waste.
2.Sensors are accurately detecting the level of waste in each bin.

Postconditions: 1.The system successfully calculates the time taken for the bin to fill
completely.
2.The calculated filling time is stored in the database for future reference.
3.The admin app displays the filling time for each bin for monitoring and
analysis.
Normal Flow: 1.The system records the time when the bin starts collecting waste.
2.Sensors periodically update the fill level of the bin.
3.When a bin reaches its maximum capacity, the system records the time.
4.The system calculates the total time taken for the bin to fill completely.
5.The calculated filling time is stored in the database and displayed on the
admin app for monitoring.
Exceptions: 1.If the sensor fails to detect changes in the bin fill level, the system logs
the issue and alerts the admin.
2. If the time calculation process encounters an error, the system retries or
notifies the admin.

Allocate free bin to most speedly filling bin

Use Case ID: UC-5.0

Use Case Name: Allocate free bin
Actors: Waste segregation system
Description: During specific times when the plastic bin fills faster, the system
dynamically assigns a secondary bin to collect plastic waste.
Trigger: The most speedly filling bin reaches 90% capacity during the specified
period.
Preconditions: 1.The system is operational and monitoring bin fill levels.
2.At least one free bin is available for reassignment.

Postconditions: 1.A free bin is successfully assigned as a secondary bin for primary waste.
2.The admin app displays the updated bin allocation and statuses.
3.The system ensures continuous collection of primary waste without
overflow during the specific time period.
Normal Flow: 1.The system detects the high fill rate of the a bin during a specific time.
2.The system checks for an available free bin to assign as a secondary bin
for the bin which is 90% full.
3.secondary bin's lid is reconfigured to accept plastic waste.
4.The system updates the admin app with the new bin allocation and fill
status.
5.The primary and secondary bins continue collecting plastic waste until
reallocation is no longer required..
Exceptions: 1.If no free bin is available for reassignment, the system notifies the admin
to resolve the issue manually.
2.If reconfiguration of the secondary bin's lid fails, the system retries or
 alerts the admin.

j. Block Diagram

k: System Sequence diagram:

Actor
 Register

Mobile App

Admin
Actor

Opens Mobile App( )

Display login page

Click create Account( )

Navigate to register account page

Enter validinfo(string name, string email, number phone,string

password , string confirm password)

get admin information

Click createAccount( )

Save all valid information in database

Recieve success message( )

Navigate to login page

 Logout

Mobile App

Actor
Admin

Login (strimg username , string password)

Login successful mesage popup and navigate to home page

Click on menu icon( )

Shows side Menu bar

Select logout( )

Pop up sure to logout message

Click confirm to logout( )

logout and navigate to login page

 View bin status in App

Mobile App

Actor
Admin

Open mobileApp( )

display login page

login(string username, string password)

Login successful mesage popup and navigate to home page

View bin status( )

show filled bin status in percentage

 Recieve alarm notification through App

Mobile App

Actor
Admin

Active mobileApp( )

App working in mobile properly

Recieve alarm notification on 100% filling of bin( )

Generate beep sound on alarm

Click recieve notification( )

end beep sound

Emptybin()

Reset the bin status

 Detect Waste material

System

Actor system
Waste segregation

Open main lid( )

Main lid half opened

Close the opened main lid( )

Detect the recieved material type through OpenCV

Detect material against(paper, glass,plastic,organic)

Match material with the saved dataset of CNN

End detection( )

start sorting
 Sort waste into bin

System

Waste segregation system

Actor

Open main lid( )

Main lid half opened

Complete detection( )

start sorting the waste

Start sorting (detected material)

Check detection result

Rotate motor towards respected bin( )

Open small lid of that particular bin

Through waste in bin (detected wastematerial)

close the small lid of that bin

Update bin status( )

Updation on app and in database and end sorting

 Calculate bin status

System

Ultra sonic sensors

Actor

Sort waste material( )

Update bin status on app and in database

Calculate bin status( )

Calculate the filled status of the bin in percentage

Update status (percentage value)

Edit previous status on app and in database

Display new status( )

End calculation
 Calculate bin filling time

System

Waste segregation system

Actor

Sort waste( )

end sorting

Update bin status( )

end updation

Start timer( )

Calculate time until a bin filled

Bin filled alarm( )

Save calculated time in database

Stop timer( )

Dsiplay total time on admin app

 Allocate Free Bin

System

Actor
Waste segregation system

Calculate bin filling time ( )

Save record in database

Monitor speedy filling bin( )

Notifies on app

Allocate free bin( )

Allocate secondary bin to primary waste

Notify secondary bin on app( )

End notification ( )