Software Architecture COMP806 Milestone 1

Automated Waste Collection and Management

System
Software Architecture Document(SAD)

Table of Contents
Table of Contents .......................................................................................................... 1
1 Introduction ............................................................................................................. 2
1.1 System Overview ............................................................................................ 2
1.2 Purpose of this architecture ............................................................................ 2
1.3 Process for creating the architecture (like ADD) ........................................... 2
1.4 Organisational context .................................................................................... 2
1.5 Scope .............................................................................................................. 3
2 Architectural Drivers ............................................................................................... 3
2.1 Primary Functional Requirements .................................................................. 3
2.2 Technical Constraints ..................................................................................... 3
2.3 Business Constraints ...................................................................................... 3
2.4 Quality Attributes............................................................................................. 4
3 Views ...................................................................................................................... 6
3.1 Logical View .................................................................................................... 6
3.2 Process View .................................................................................................. 8
3.3 Physical View ................................................................................................ 11
3.4 Glossary ........................................................................................................ 12
4 Conclusions & Future Works ............................................................................... 12
Reference .................................................................................................................... 13

Jian Chen 20109091 1

Software Architecture COMP806 Milestone 1

1 Introduction
1.1 System Overview
The Automated Waste Collection and Management (AWCM) System can be designed for
several purposes, such as accuracy of sorting waste, efficiency of reusing resources, to
benefit work of environment protection. This system can help with several scale of business
use, either group or individual, save time on waste collection. As the world is overwhelming
with human needs on resources, most of waste can be recycled properly by a standard
system.

1.2 Purpose of this architecture

The Software Architecture Document(SAD) provides an overview of a sketched architecture
for the Automated Waste Collection and Management System. As the blueprint of the
system, the purpose of this architecture is mapping out the modules and components of this
software and showing the structure for any technical or non-technical person.

This SAD is produced according to the requirements as following:

• For individuals, the system can assist users to sort out waste in the right way and
generate reports for them during a certain period, as well as accumulate points for
future redemption.
• For groups, the system provides notifications for cleaners working at the
organisations as extra.
• For govern, the system can provide detailed data of waste collection and give people
a better view in waste management.

1.3 Process for creating the architecture (like ADD)

This architecture uses the Attribute Driven Design (ADD) as the design approach by using
BS ISO/IEC 25010 as the quality model. This helps address the primary quality attributes
which are usability, functional suitability, security and performance efficiency. According to
these four QAs, different QA scenarios are designed to cover functional requirements with
constraints considered. Philippe Kruchten’s the “4+1” View Model of Architecture is
referenced to document this software architecture.

1.4 Organisational context

Individual
This kind of users are the most common users of this system. They are private property
based, such as a family, flatmates sharing the same house. Each user can register to get an
account with their information for personal use.

Group
Rubbish bins will be provided at many public places. Public groups intend to contribute as an
environment friendly place, therefore, a reminder for cleaners can improve the efficiency.

Government
The government need data related to waste collection and management to get a better
sense in protecting the environment. It requires residents of the place to collaborate and
help with sorting out the waste.

Jian Chen 20109091 2

Software Architecture COMP806 Milestone 1

1.5 Scope
The scope of this SAD is to explain the architecture of the Automated Waste Collection and
Management System. It is briefly giving out major concerns which will be faced with system
design. The existed Waste Management Systems are used as references while producing
this SAD.

2 Architectural Drivers
2.1 Primary Functional Requirements
Waste Collection
The main function of this system is to sort out waste base on the input of waste info user
input to the app by connecting the smart bin with point-to-point communication such as NFC,
or scan unique QR code on bin. The system should process the user input data to smart bin
and trigger the smart bin built-in system to sort out the waste.

Notification of bin status

Each smart bin will have built-in sensor to check if the bin is filled or not, and the system
should extract data from sensor and pass it to cloud server. The information will be display
on user’s app. Also, if the smart bin is full, system will send reminder notification to users.

Report generated
This waste management system should generate waste report for different stakeholders
based on data collected from all devices. For government, data is provided for a strategic
use in waste management.

2.2 Technical Constraints

As requirements of using this system, it relies on point-to-point communication or scanning
the unique QR code on the smart bin to build connection. So it will require user to have
devices with at least one feature like NFC, Bluetooth or camera. To run a full functioning
system, internet connection is needed for any data uploading and downloading.

2.3 Business Constraints

To pervasive this system, it will require to replace all the current rubbish bins to renewed
bins with built-in of this system. Therefore, either individual users or business groups will
consider the cost as a restriction. Also, user has to own a smart device to communicate with
the smart bin. This possibly can be an obstacle to encourage people to use it.

For government, if the smart bins are not be placed for the whole area, then the data being
recorded will only be partial so it is not able to provide a full view report with accurate data.

Jian Chen 20109091 3

Software Architecture COMP806 Milestone 1

2.4 Quality Attributes

2.4.1 Stakeholder concerns
Individual Users Business Users Government Users
Performance The system should The system should
process user input notify the cleaner
data within a short with data of full bin
period. as soon as possible.
Usability User can use NFC
feature, scan the QR
code or input the bin
id to connect device
with bin.
Functional Suitability Reports will be Reports will be The system should
delivered delivered be able to generate
automatically. automatically. report based on user
requirements.
Reliability The system should The system should
keep connection be well connected to
between user device cloud server all the
and smart bin while time, so cleaner can
it’s using. check bin status
anytime and adjust
workflow.
Security Personal user data Organisational user Government user
should be kept data such as cleaner work data should be
securely in system. should be kept kept securely in
securely in system. system.

2.4.2 Quality Attribute Scenarios

The Quality Attribute Scenarios are designed based on the article Quality Attributes
Workshop(QAW)(Barbacci et al., 1995). The primary functional requirements, technical and
business constraints and stakeholder concerns are the architecture drivers for producing the
QAS and designing the system architecture. Compare to existing system, this AWCM
system can extend its performance to provide service to a large scale of users(Chowdhury &
Chowdhury, 2007). Then the security quality attribute has to be considered as the
requirements of keeping user data protected. Besides, the usability has to be measured as
the system should be easy to use by different users. Reports generate feature is an extra
function to be implemented to provide useful data that can lead action to get waste
management efficiently(Haastrup et al., 1998).

Scenario Waste sorted based on the data input from user

Relevant Quality Usability, Functional Suitability
Attribute(s)
Stimulus User device connects to bin and inputs waste data.
Stimulus Source AWCM Application
Response The system gives out instructions to users and sorts out the
waste. User will be notified to place the waste if sensor
recognized no waste placed.
Response Measure User input data will be sent to smart bin immediately, and
system should process it within 2 seconds.

Jian Chen 20109091 4

Software Architecture COMP806 Milestone 1

Scenario Real-time reminder to cleaner when sensor recognizes full

bin.
Relevant Quality Functional Suitability
Attribute(s)
Stimulus Smart bin is full and waste needs to be collected.
Stimulus Source AWCM Smart Bin System
Response Notification sent to cleaner and provide the location of
smart bin.
Response Measure Reminder will be sent to cleaner’s device once the smart
bin is full, and it will keep alerting every 15 minutes.

Scenario Different approach to connect smart bin to user device.

Relevant Quality Usability
Attribute(s)
Stimulus Features on user device are limited.
Stimulus Source AWCM Application
Response Smart bin can be connected by NFC or scanning QR code
displayed on bin surface. Once smart bin is well connected
to device, the app will notify user and the certain bin option
will appear on the app display.
Response Measure Both approaches should only take less than 10 seconds to
connect smart bin and user device.

Scenario Generating Waste Reports base on certain time range

Relevant Quality Functional Suitability, Performance Efficiency
Attribute(s)
Stimulus User checks their waste reports through the system,
especially for governors who use it as reference to make
decisions.
Stimulus Source AWCM System
Response The system can generate reports for users.
For governor users, the system can produce detailed
reports by extracting general data.
Response Measure Reports can be generated by weekly, monthly and yearly.
For government users, reports can be produced by time
range, suburb/city/area and waste details.

Scenario Data of Register User should be secure and saved on cloud

database server.
Relevant Quality Security
Attribute(s)
Stimulus User login to their accounts, save or redeem points by
using the AWCM app.
Stimulus Source AWCM Application
Response The system checks the user authentication, grant them the
access to their personal data.
Non-registered user will be notified to sign up first.
All the personal and general data are encrypted and saved
on cloud server.

Jian Chen 20109091 5

Software Architecture COMP806 Milestone 1

Response Measure Data collected by smart bin will be uploaded every hour.
User Data on user device will be uploaded once the device
has internet. The initial cloud database storage is 50TB with
scalability.

3 Views
3.1 Logical View
3.1.1 Primary Presentation
3.1.1.1 Use Case Diagram

3.1.1.2 Class Diagram

Jian Chen 20109091 6

Software Architecture COMP806 Milestone 1

3.1.2 Element Catalogue

Individual is user who use the system for personal purpose.

Business group is organisation that use the system to manage waste produced within the
business.
Government is the user group that use the system to access waste collection data and
report, so to make political decisions about waste management.
Input the info of waste is the activity that user has to apply when they place the waste into
smart bin.
Get points is the benefits of registered user. Each time they dump waste into the smart bin,
they can get points base on the waste quantity.
Login to User/Cleaner/Government system is the action required for user to access
protected data, such as personal data, and general data collected from all devices.
Data collected is a one of major function built in the system, after data analysis, customised
reports will be produced by the system.

Device represents the device user uses to connect to the smart bin. User can connect to
one or more bins and save the data on the device.
Smart Bin represents the system smart bin entity with data which contains its unique id and
bin status.
Sensor represents sensor that is built in the smart bin. It can check bin status and pass the
data cloud server, then cleaner can check it through cleaner system.
User represents the system user entity. Smart bin can connect with one or more users.
User Input represents the system user input entity. The smart bin built-in system can only
process one user input at the same time.
Report represents the report has been generated from collected. The smart bin built-in
system only saves reports made for the certain bin and uploaded all date to AWCM cloud
server.

3.1.3 Context Diagram

3.1.4 Variability Guide

The limitation of user device sometimes will be an obstacle when using the system. In this
case, to make it usable for most device, the method of connecting to smart bin can be vary,
such as NFC, scanning QR code and input smart bin id.

3.1.5 Architecture Background

This logical view is to provide coverage for functional requirements. One of the core feature
is to process waste collection automatically which does not require user to login(Chowdhury

Jian Chen 20109091 7

Software Architecture COMP806 Milestone 1

& Chowdhury, 2007). However, the other functions require user to login first and then can
access specific system parts. As for different users, there are a certain subsystem offered.
And all the data from subsystem will be collected by the main system.

3.2 Process View

3.2.1 Process of Report Generate
3.2.1.1 Primary Presentation

3.2.1.2 Element Catalogue

Receive Data: Data collected from smart bin system and user device is uploaded to cloud
server. It is stored in cloud server database.
Data Sorted: Receive data is sorted by AWCM system and passed to the next step.
All Data: All the raw data that is sent to cloud server database.
Save to cloud database: The raw data will be saved into cloud server database.
Data Analysis by AWCM system: The sorted data will be analysist automatically by AWCM
system for report purpose.
Report Generated: The report is made based on the data saved and it is the result of the
data analysis.
Report for individuals: Generated report for individual use.
Individual user app: AWCM app installed on personal device for individual use.
Report for Government: Generated report for government work use. It offers reference for
decision making.
Government user system: Functional subsystem of AWCM system which provide features
with manipulating waste data.

3.2.1.3 Context Diagram

Jian Chen 20109091 8

Software Architecture COMP806 Milestone 1

3.2.1.4 Variability guide

In current architecture, the data collected will be sent to AWCM cloud server first, and then
sorted. Alternative approach is introduced that data can be sorted on local device and then
delivered to cloud server. In this way, it requires all the subsystem to use same standard
sorting out data.

3.2.2 Process of Bin Status Notification

3.2.2.1 Primary Presentation

3.2.2.2 Element Catalogue

Receive Bin Status: Bin status sent by sensor built in to the cloud server, it will be received
and update by AWCM cloud server.
Status Data: Bin status data contains the bin space, network connection and battery.
Send to User app: Bin status data is sent to certain user’s app which are having the access
of maintenance.
Display status on app: Feature of the AWCM user app, once the bin status data has been
received, the app will show it on user interface
Full Bin Reminder: Feature of the AWCM user app, once the bin status tells the bin is full, it
will give out the full bin reminder.
Send notification to cleaner: The full bin reminder will be sent to cleaner’s app as a
notification.

3.2.2.3 Context Diagram

3.2.2.4 Variability guide

As within app notification is not going through properly sometimes, the full bin reminder can
be sent to cleaner by SMS or email. And internet connection is not compulsory in this case.
However, the telecommunication cost will be slightly higher.

Jian Chen 20109091 9

Software Architecture COMP806 Milestone 1

3.2.3 Process of User Login and Data Access

3.2.3.1 Primary Presentation

3.2.3.2 Element Catalogue

User: the common user of the system.
Interface: the display of the user app which is showed on user device.
Local Data: local app data and user data.
Authentication: the object of doing authentication check for user login and access to
personal data.
Cloud Server: AWCM cloud server for providing data process and store function

3.2.3.3 Context Diagram

3.2.3.4 Variability guide

User can access local data without login, however, any sensitive personal data will require
user to login. As the waste collection and management is run by government, so the user
database can be shared with government. For instance, in New Zealand, user can use their
RealMe account to login.

3.2.4 Architecture Background

The process view gives out the idea how this architecture perform some key functions. The
processes for three features are well displayed above, as they can provide the coverage of
security, usability, performance and functionality. To test the performance of the system, an
approach was introduced by Kallio et al which is test usability by testing the task execution
time(Kallio & Kaikkonen, 2005).

Jian Chen 20109091 10

Software Architecture COMP806 Milestone 1

3.3 Physical View

3.3.1 Primary Presentation

3.3.2 Element Catalogue

AWCM App: one subsystem of AWCM system which provide end-user functions
Local App Data: app data required when running the AWCM App
User Data: user personal data that allows user to check and update sensitive data, also get
and redeem points.
AWCM Cloud Server: server provide cloud side service. It can process data which need to
be store on cloud server.
AWCM Cloud Database: cloud database that is used to store all raw data collected from all
devices.
Built-in System: smart bin built-in system is one sub system of AWCM system. It offers the
capability of operating the smart bin and store the data.
Weight Sensor: Sensor built-in of smart bin, it checks the condition of the bin, and generate
data through system.

3.3.3 Context Diagram

3.3.4 Variability Guide

In the physical view, server and database of the AWCM system are built on cloud
service, which is a way to reduce cost of running the system. However, it also can be
set up at a local place physically, so the system can be maintained easily and
securely.

Jian Chen 20109091 11

Software Architecture COMP806 Milestone 1

3.3.5 Architecture Background

This view provides the solution to cover the functional suitability and performance efficiency.
In this View, server is built on cloud service which can be accessed any time as long as the
cloud service is provided. Data transfer is processed through cloud server to database
server. When the cloud system server is down, user and smart bin can still get and send
data from cloud database server. The study of Ray generated the conclusion that there is a
part called Service Oriented Architecture on IoT Architecture domain(Ray, 2018). In this
approach, components such as applications, data storage and data process are separated.
By this way, the architecture view solves the potential server breakdown issue and improve
the performance efficiency.

3.4 Glossary
Term/Acronym Description
AWCM Automated Waste Collection and Management
NFC Near-field Communication

4 Conclusions & Future Works

This software architecture document describes the high-level design of this AWCM system
which has several subsystems integrated together. This SAD can be well applied and
upgraded as waste management can be a good approach to protect the environment.
Currently the system still requires user to input the waste data, so that smart bin can sort out
waste automatically. For future works, the sensor built-in can be replaced by high
performance sensor and chips, it can check waste by scanning so to save user operation
and improve efficiency. Meanwhile, artificial intelligence can be deployed within the system
to help process the data collected in order to get more useful and accurate information.

Jian Chen 20109091 12

Software Architecture COMP806 Milestone 1

Reference
Barbacci, M., Klein, M. H., Longstaff, T. A., & Weinstock, C. B. (1995). Quality
Attributes Workshop. https://apps.dtic.mil/sti/pdfs/ADA307888.pdf

Chowdhury, B., & Chowdhury, M. U. (2007, 2-5 Dec. 2007). RFID-based real-time
smart waste management system. 2007 Australasian Telecommunication
Networks and Applications Conference, Christchurch, 2007, pp. 175-180.
https://doi.org/10.1109/ATNAC.2007.4665232

Haastrup, P., Maniezzo, V., Mattarelli, M., Mazzeo Rinaldi, F., Mendes, I., &
Paruccini, M. (1998, 1998/09/01/). A decision support system for urban waste
management. European Journal of Operational Research, 109(2), 330-341.
https://doi.org/https://doi.org/10.1016/S0377-2217(98)00061-7

Kallio, T., & Kaikkonen, A. (2005). Usability testing of mobile applications: A

comparison between laboratory and field testing. Journal of Usability studies,
1(4-16), 23-28. http://lib.tkk.fi/Diss/2009/isbn9789522481900/article6.pdf

Kruchten, P. B. (1995). The 4+1 View Model of architecture. IEEE Software, 12(6),
42-50. https://doi.org/10.1109/52.469759

Rawat, D. B., & Reddy, S. R. (2017). Software Defined Networking Architecture,

Security and Energy Efficiency: A Survey. IEEE Communications Surveys &
Tutorials, 19(1), 325-346. https://doi.org/10.1109/COMST.2016.2618874

Ray, P. P. (2018, 2018/07/01/). A survey on Internet of Things architectures. Journal

of King Saud University - Computer and Information Sciences, 30(3), 291-
319. https://doi.org/https://doi.org/10.1016/j.jksuci.2016.10.003

Sharma, A., Kumar, M., & Agarwal, S. (2015, 2015/01/01/). A Complete Survey on
Software Architectural Styles and Patterns. Procedia Computer Science, 70,
16-28. https://doi.org/https://doi.org/10.1016/j.procs.2015.10.019

Jian Chen 20109091 13