Page 1

Smart Waste Management

System
Software Engineering

Project Report

Submitted by: Supervisor:

Shanu kumar Singh 17507
Parag Dudeja 17511 Kavita Rastogi

2019

Department of Computer Science

Shaheed Sukhdev college of Business Studies
University of Delhi 

Page 2

Problem Statement............................................................................................................... 4

Process Model..................................................................................................................... 4

1. Software Requirement Specification.......................................................................... 4

1.1 Overall Description................................................................................................ 4

1.1.1 Product Functions............................................................................................ 4

1.1.2 User Characteristics.......................................................................................... 5

1.1.3 General Constraints.......................................................................................... 5

1.1.4 Assumptions and Dependencies....................................................................... 5

1.2 External Interface Requirements............................................................................. 6

1.2.1 User Interfaces................................................................................................. 6

1.2.2 Hardware Interfaces......................................................................................... 6

1.3 Functional Requirements........................................................................................ 6

1.3.1 FR 1................................................................................................................. 6

1.3.2 FR 2................................................................................................................. 6

1.3.3 FR n................................................................................................................. 6

1.4 Performance Requirement...................................................................................... 7

1.5 Data Flow Diagram................................................................................................ 7

1.6 Data Dictionary...................................................................................................... 7

2. Estimations................................................................................................................. 9

2.1 Function Points...................................................................................................... 9

2.2 Efforts.................................................................................................................... 10
Page 3
3. Scheduling................................................................................................................. 8

4. Risk Management.................................................................................................... 10

5. Design...................................................................................................................... 11

5.1 System Design..................................................................................................... 11

5.2 Data Design.......................................................................................................... 11-13

6. Coding..................................................................................................................... 14-15

7. Testing..................................................................................................................... 16

8. References................................................................................................................ 17

Page 4
Problem Statement

Smart Waste Management System is a mobile application helps in managing solid waste
effectively by automating certain stages of waste management ( collection, transportation,
recycling) , using divide and conquer approach to tackle large amount of solid waste,
efficient processing of solid waste ( waste to wealth), promoting go green campaign by
providing recycled goods at low prices to the houses that generate less solid waste( mainly
non-recyclable).

Process Model

The model chosen for our project is Prototype Model. Since this concept is fairly new,
requirements are not well defined and may get changed accordingly if needed.

Users would be actively involved to understand the requirements.

Since in this methodology a working model of the system is provided, the users get a
better understanding of the system being developed. Quicker user feedback is available
leading to better solutions and errors/changes can be identified early.

1. Software Requirement Specifications

This section gives a scope description and overview of everything included in this SRS document.
Also, the purpose for this document is described and a list of abbreviations and definitions is
provided.

1.1 Overall Description

Smart waste management system provides an easy solution to households for waste disposal and
for scrap dealers to collect and recycle waste by automating certain stages of waste collection and
then redirecting collected wastes for further treatment.

This System can also be used to promote Go-Green campaign by setting up retail units for selling
recyclable items to households on discounted prices.

1.1.1 Product Functions

To provide households , hospitals and SSI an easy solution for waste disposal
Automate waste collection process by setting up POC and providing scrap dealers with mobile
app to collect and store the details of waste collected.
Segregate collected waste and then treat them accordingly. (On the basis of their biodegradability
or recyclability
Automate the transportation of recyclable waste to nearest recycling station.
Provide franchisee owners with a billing system to give discounts to households generating less
non-recyclable waste.
Analyse the amount of waste generated per year area wise by storing data collected from POC’s
so that significant steps can be taken to minimise generation of non-recyclable,
non-biodegradable and hazardous waste.

1.1.2 User Characteristics

Page 5

The users of the online shopping application, based on their roles, are scrap dealers and local
shopkeepers (users) and the Administrator (owner).
1. Admin: The administrator is the person who handles this smart waste management application.
One must have a basic understanding of computers and the internet as well as prior knowledge for
operating Java and Swift programming languages. The administrator is responsible for maintaining
all the documents required for the system. The administrator can perform the following functions:
View the list of registered and logged-in users.

2. Users: The users of this smart waste management would be scrap dealers and local shopkeepers.
These users are anyone with a license from the respective authorities . The users should be able to
perform the following functions using this system: Sign-in/login using a username and password.
Give star rating as per the amount of non-recyclable waste and recyclable waste collected(in case of
scrap dealers). Order for stock (in case of local shopkeepers) Place the order by completing the
order form

1.1.3 General Constraints

Hardware Limitations: The minimum hardware requirement for the system is 512 MB of Ram and
a 32-MB free space in internal flash storage.
Accessibility: Initially, the software should be available as a mobile application for a small set of
users to test.
Others: The application should be built using Java(Android) and Swift(iOS), and it should,
initially, be accessible through the Android Studio and XCode, which would be later published on
App Store/Play Store when the application passes the test from small set of users.

1.1.4 Assumptions and Dependencies

Scrap dealers and the franchise holders would require training to use the mobile application.
We assume that system users adhere to the system’s minimum software and hardware requirements.
Scrap Dealers - People who are assigned the task of setting of POC’s, transporting waste,
collecting data and then feeding them into the database through the mobile app
POC - Point of Collection
SSI- Small Scale Industries
Retailers - Franchise owners who are selling recycled products.
Page 6

 1.2 External Interface Requirements

1.2.1 Use Interfaces :

The users will work on a graphical user interface. All the required steps for the user to perform must
me specified on each page so that it is easy for users to understand the procedure to perform.
The steps must be brief so that the content is not a trouble. There must be a search bar on every
page for basic queries. Limited feedbacks and reviews should be there on main page.
The screen should be formatted in such a way so that instructions and messages always get
displayed in a general area. The user must not be taken forward without correcting the error.
The system user should never get any operating system failure or any fatal error.
 
1.2.3 Hardware Interfaces:
Hardware requirements for insurance on internet will be same for both parties
which are as follows:
Processor:Dual Core
 
RAM:1 GB
Flash Storage Space:8 GB

1.3 Functional Requirements

FR1:

Description: The application shall provide login facility to the scrap dealers, households and
shopkeepers selling green products
Input: Phone number and password
Output: User profile is opened

FR2:

Description: Record the quantity of non recyclable waste collected by a scrap dealer from a housing
society
Input: Quantity of non recyclable waste
Output: Rating on a scale of 1 to 5 and a discount percentage associated with each rating point

FR3:
Description: Households view the rating given to their housing society

FR4:
Description:  Shopkeeper shall be able to view the products available

Input: Item name

Output: List of items matching the search phrase to some extent
Page 7
FR5:
Description: Shopkeeper shall be able to add products to his cart
Input: Select items to be added
Output: Add items to cart

FR6:
Description: Shopkeeper shall be able to remove products
Input: Select items to be removed
Output: Remove items to cart

FR7:
Description: Shopkeeper shall be able to place order
Input: Item name and fill up order form
Output: Order placed for selected items

FR8:
Description: The administrator shall be able to add items to the list of green products
Input: Items to be added
Output: Items added

1.4 Performance Requirements

1. The home screen after login should show up in less than  5 seconds 90% of the time.


2. Record of non recyclable waste collected a by scrap dealers should be added in less than 7
seconds 95% of the time.


3. Orders placed by shopkeepers must be processed in less than 8 seconds 90% of the time.


4. Households must be able to view their rating score in less than 5 seconds 95% of the after
request is received.


1.5 Data Dictionary

1. Login = Phone_No + Password


2. Housing Society = Name_of_soc + Area+ Number_of_houses


3. Scrap dealer = Name_of_Name_of_scrap_dealer + Address + Phone_No + Total_workforce


4. Hospital = Hospital_Name +Address +Bed_Capacity + Phone_No


5. Small Scale Industry = Name_of_company+ Area +Annual_turnover + Phone_No


6. House  =House_ID + Name_of_family_head +Address+ Phone_No


7. Shopkeeper =License_No + Shop_Name + Location +Address+ Annual_Turnover


8. Green product= Item_Code+ Item_name +Type+ Quantity_available+ Price_per_unit

Page 8
3. Scheduling
Page 9

2 Estimation
2.1 Function Points
Function Point Worksheet

Weighting Factor

Measurement parameter Count Simple average omplex Choice

# of user inputs 15 X 3 4 6 4 = 60

# of user outputs 8 X 4 5 7 5 = 40

# of user inquiries 10 X 3 4 6 4 = 40

# of files 7 X 7 10 15 10 = 70

# of external interfaces 3 X 5 7 10 7 = 21

Count-total = 231

Rate each factor on a scale of 0 to 5: 0 - No Influence 1 - Incidental 2 - Moderate

3 - Average 4 - Significant 5 - Essential

1. Does the system require reliable backup and recovery? 5

2. Are data communications required? 5

3. Are there distributed processing functions? 2

4. Is performance critical? 3

5. Will the system run in an existing, heavily utilized operational environment? 5

6. Does the system require on-line data entry? 5

7. Does the on-line data entry require the input transaction to be built over multiple screens or
0
operations?
8. Are the master files updated on-line? 5

9. Are the inputs, outputs, files, or inquiries complex? 2

10. Is the internal processing complex? 1

11. Is the code designed to be reusable? 2

12. Are conversion and installation included in the design? 5

13. Is the system designed for multiple installations in different organizations? 3

14. Is the application designed to facilitate change and ease of use by the user? 5

sum of Fi = 48

Funtion Point Metric = count-total * [.65+.01*sum Fi]

= 261.03
Page 10

2.2 Efforts
Assume that the past data shows that the complexity for these types of systems is 15 function point
per month. Assume burdened labour cost of 18,000 , the cost per fp is
Rs 2000.
 Estimated project cost =2000*261.03 =522060
 Estimated effort = 261.03/15 = 17.402

4 . Risk Management

Risk table
Risks Category Probabilit Impact
y

1 Server failure Technical 10% Marginal

risk

2 Size estimation may be Project Size 40% Critical

significantly low. Risk

3 Technology will not meet Technical 30% Catastroph

expectations Risk ic

4 Change of requirements Project Size 80% Critical

Risk

Since this concept of smart waste management is fairly new, the requirements may
change frequently. Detailed RMMM plan for this risk is mentioned below.

RISK MITIGATION, MONITORING AND MANAGEMENT

Mitigation
Page 11
The cost of the project would rise up too much if the requirements are changed after the subsequent
steps have commenced. To mitigate this risk we would want to:
• Make sure the data collected is authentic and as extensive as possible.


• Put forward a deadline for proposing changes  after which charges would be levied for each
subsequent change proposed

Monitoring

While working on the SRS, we should conduct multiple reviews to make sure the requirements are
understood well and does not have to be changed much later.

Management

In case there is no other option but to make a change in the SRS, the development team must cease
their work until the change in the requirements is done and negotiated. Since prototype model is
used in the initial stage, this change must be flexible and thus the project could be continued
without much hiatus.

5. Design

5.1 System Design

5.2 Database Design

Housing_Societies_Info

ATTRIBUTE DATA TYPE CONSTRAINTS

SOCIETY_ID INTEGER PRIMARY KEY
NAME_OF_SOCIETY VARCHAR NOT NULL
AREA VARCHAR NOT NULL
NUMBER_OF_HOUSES INTEGER NOT NULL

Hospitals

ATTRIBUTE DATA TYPE CONSTRAINTS

HOSPITAL_ID INTEGER PRIMARY KEY
HOSPITAL NAME VARCHAR NOT NULL
ADDRESS VARCHAR NOT NULL

BED_CAPACITY INTEGER NOT NULL

PHONE_NO INTEGER NOT NULL
Page 12

ScrapDealer

ATTRIBUTE DATA TYPE CONSTRAINTS

NAME_OF_SCRAP_DEALER VARCHAR PRIMARY KEY

ADDRESS VARCHAR PRIMARY KEY

TOTAL_WORKFORCE INTEGER NOT NULL

AVAILABLE_LAND DECIMAL NOT NULL

PHONE_NO INTEGER NOT NULL

SmallScaleIndustry

ATTRIBUTE DATA TYPE CONSTRAINTS

COMAPNY_ID INTEGER PRIMARY KEY

COMPANYy_NAME VARCHAR NOT NULL

AREA VARCHAR NOT NULL

ANNUAL_TURNOVER INTEGER NOT NULL

PHONE_NO INTEGER NOT NULL

House_data

ATTRIBUTE DATA TYPE CONSTRAINTS

HOUSE_ID INTEGER PRIMARY KEY

NAME_OF_FAMILY_HEAD VARCHAR NOT NULL

ADDRESS VARCHAR NOT NULL

SOCIETY_ID INTEGER FOREIGN KEY(REFERENCES

SOCIETY_ID IN
HOUSING_SOCIETY)

PHONE_NO INTEGER NOT NULL

Page 13

Shokpkeeper_Data

ATTRIBUTE DATA TYPE CONSTRAINTS

LICENSE_NO INTEGER PRIMARY KEY

SHOP_NAME VARCHAR NOT NULL

ADDRESS VARCHAR NOT NULL

ANNUAL_TURNOVER DECIMAL NOT NULL

PHONE_NO INTEGER NOT NULL

Green_products_stock

ATTRIBUTE DATA TYPE CONSTRAINTS

ITEM_CODE INTEGER PRIMARY KEY

ITEM_NAME VARCHAR NOT NULL

TYPE VARCHAR NOT NULL

QUANTITY_AVAILABLE INTEGER NOT NULL

PRICE_PER_UNIT INTEGER NOT NULL



Page 14

6 Coding
Page 15
Page 16

7. Testing

Number of nodes (N) = 15

Number of Edges(E) = 18
Cyclomatic complexity V(G) :-
V(G) = E — N + 2
= 18 — 15 + 2
= 5

Independent paths:-
1. 1-->2-->3-->1
2. 1-->2-->4-->5-->6
3. 1-->2-->4-->5-->7-->12-->13-->14-->12
4. 1-->2-->8-->9-->10
5. 1-->2-->8-->9-->11-->12-->13-->14-->15
Page 17

Graph Matrix

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15

1 A

2 D E C

3 B

4 F

5 G H

7 N

8 I

9 K J

10

11 L

12 M

13 O

14 P

15 Q