Group project software project management (co3011) project urban waste collection syste

About the relevant stakeholders: Back officers -Operate a central system to create working routine, coordinate front collectors and janitors Janitors -Collect the garbage from Ma

HO CHI MINH CITY NATIONAL UNIVERSITY

HO CHI MINH CITY UNIVERSITY OF TECHNOLOGIES

GROUP PROJECT

SOFTWARE PROJECT MANAGEMENT (CO3011)

PROJECT: URBAN WASTE COLLECTION SYSTEM

CC01 - SEMESTER 232

Instructor: Nguyén Cao Tri

Group project: Task defined and estimation

I Project definition

1.1 Introduction

Nowadays, many countries focus on development and economic growth, which leads to an increase in solid waste and makes the management of solid waste cost more and ineffective So the most important point is to improve the Sustainable Development Goal (SDG) This project is created to simplify waste management and make it easier for stakeholders to track the waste collection routine With the improvement in UWC 1.0, the project aims to upgrade this system, using their own database to create the UWC 2.0 with more functionalities and handle the large number

of collecting points

Recently, waste collection companies only use paper to store their work and don’t have a particular system to manage the waste collection For example, employees have

to come to their workplace to receive the task and check in or check out The manager has to have a secretary to write down the work and doesn't have a particular system to communicate with the staff So the program will help all the waste collection systems work smoothly by only using the web page It helps improve communication between staff and provide better management on waste collection

About the relevant stakeholders:

Back officers -Operate a central system to create working routine,

coordinate front collectors and janitors

Janitors -Collect the garbage from Major Collecting points

(MCPs) Collectors -Drive different type of vehicles to MCPs

About the stakeholders current needs:

Back officers -Information about the janitors and collectors

-Information about the vehicles and technical

-Contact with janitors and collectors to give information about their task or if there are any changes in there routine

Janitors and collectors

-Information about the working routine -Information about their tasks on a daily and weekly basic

-Contact with others employees to know about their routine

-Contact with Back officers to have information about their schedule if there are any problems

About the stakeholders current problems:

Back officers -Cannot control the schedule of the janitors and

collectors

-Cannot communicate with the janitors and collectors

-Do not know the updated overview of an the capacity

of the MCPs

-Have to calculate the best routine to collect the trash by hand

Janitors and collectors -Do not know the schedule and the tasks on a

daily/weekly basis

-Cannot communicate with the back officers and other Janitors and collectors

-Do not have the system to check in and check out

-Do not get notification when there is any changes in tasks and schedule

Back officers -Can have the work schedule of janitors and collectors

-Can have the update information and capacity of MCPs -Easy way to communicate with janitors and collectors about changes in their schedule

-Create the optimize routine to collect the waste

Janitors and -Have an overview of their schedule

-Know their daily and weekly task

-Receive a message from back officers and others janitors, collectors

-Can check attendance

-Be notified if the MCPs is fully loaded

1.2 Functional and Non-functional requirements:

FUNCTIONAL REQUIREMENT:

Functional requirements for applications describe what specifically needs to be implemented in a particular system or product and what actions users have to take to interact with the software They determine what the system should do In other words, functional requirements are product features or functions that developers must implement to enable users to accomplish their tasks So, it’s important to make them clear both for the development team and the stakeholders Generally, functional requirements describe system behavior under specific conditions

Back officers:

Number Functional requirements of UWC 2.0

1 Interface gives information about janitors and collectors

2 Interface gives information about janitors and collectors “work calendar

3 Interface gives information about vehicles and their technical details (weight, capacity, fuel consumptions, )

4 Back officers can check real-time MCPs and information about their capacity(updated from MCPs every 15 minutes with the availability of

at least 95% of their operating time)

5 Back officers can assign vehicles to janitors and collectors, janitors and collectors to MCPs

6 Back officers can create a route for each collector(the route which is optimized in term of fuel consumption and travel distance)

7 Facilitating contact information between back officers and collectors and janitors

Collectors and janitors:

Number |Functional requirement of UWC 2.0

1 Interface gives information about janitors and collectors’ working calendar

2 Collectors and janitors a detail view of their task on a daily and weekly basic

3 Collectors and janitors check in / check out task every day

4 Collectors and janitors are notified about the MCPs if they are fully loaded

NON-FUNCTIONAL REQUIREMENT:

As a rule, the non-functional requirements primarily include various product quality attributes determining system quality features, most often as examples below: Availability: Ensure the overall efficiency of the UWC web from 7am to 6pm(When lots of people access the system)

Performance: Web’s performance delay within 2 seconds, the data shared among users within 3 seconds, web response to multiple requests and manipulations within 1 second, capable of updating MCPs concurrently

Reliability: App behavior in case of cyber attack (automatic shut down within

10 seconds, immediately send notification to administrator and operation recovery) Ease of use: within 4 operations of a function, furthermore, employees can

Scalability: Expand the database and avoid adversely affected performance (UWC 2.0 is expected to import and use the existing data from UWC 1.0), to be more specific, the database can store the information of at least 100 employees

Robustness: The time for restarting the system below | second when data corrupted

Security: Delete the data of administrator accounts after 5 attempts, warning if other IP tries to break the firewall

Usability: UWC 2.0 system interfaces should be in Vietnamese, with an opportunity to switch to English in the future All important information should be displayed in one view (without scrolling down)

Extensibility: Task Management to be interoperable with the UWC 1.0 as much as possible The system should be able to handle real-time data from at least

1000 MCPs at the moment and 10.000 MCPs in five years

Multi-platform: Can be used efficiently in multiple operating systems of mobile phone(Android, IOS), personal computer or laptop(Windows, Linux, Mac) and multiple browsers( Chrome, Firefox, Opera, )

Maintainability: Clean structure and architecture, which is easily maintained

or updated to new versions after long-time operation

II Gantt chart

Ses REAN WASTE COLLECTION OMPANY NAME

Ba Tin

a

12 Make a initial plan 1902/2024 38/02/2024 week (We

Des

a ‘System Modeling 110392024 70372024 | week om m

24 Architecture Design 1103/2024 24/03/2024 2weeke oe EERE

sd [Deploy the web app to prod ection ets itonmet 4/5/2024 13/5/2024 1wek tặc

First, we will use the Cocomo model to estimate the overall in the very beginning Then, we will use the Gantt chart to calculate it in a more detailed way

First, for the Cocomo model:

COCOMO, which stands for Constructive Cost model, is a widely used technique in software engineering for estimating the cost, effort, and schedule of

a software project The model provides a structured approach to estimating project parameters based on various factors

There are three main variants of the COCOMO model:

- Basic COCOMO: This variant is primarily used for early-stage estimates when the requirements and design of the software are not yet fully defined Basic COCOMO estimates effort in person-months based on the size of the software product

- Intermediate COCOMO.: This variant extends Basic COCOMO by incorporating additional factors that influence software development efforts It considers more factors and uses a more complex equation to estimate effort and schedule

- Detailed COCOMO: This variant provides a more detailed estimation by considering a broader range of project attributes and characteristics It breaks down the software development process into various stages and estimates the effort and schedule for each stage separately

By providing estimates of effort and schedule, the COCOMO model assists us

in setting realistic expectations and identifying potential risks early for our project We should initially utilize a Basic model since our project's

requirements and design haven't been fully specified yet

Basic COCOMO equation:

- Effort Applied (FE) = a(KLOC y (man-months)

- Development Time (D) =c (Effort Applied)’ (months)

- People required (P) = Effort Applied / Development Time (count)

be calculated using the following formulas:

© KLOC = FunctionPoint (FP) * LOC_per_ FP / 1000

o LOC = Language Factor * FP

© FP = Unadjusted Function Points (UFP) * Technical Complexity Factor (TCF)

o TCF=0.65 + 0.01 * DI (Degree of Influence)

© UFP = Unadjusted Function Point count (UFC) * Weight Factor

e@ Coefficients a, b, c, and d are given as follows:

Similarly, Basic Model shall be applied by following these steps:

Step 1: In this step, to calculate the Functional Point, we need to identify UFC according to a list of categories:

- 2user inputs: places need to collect, resources to works

- 2 user outputs: list of tasks, list of resources

- 3 user requests: find a calendar of work, assign resources

- 2 internal files: list of places, list of resources

- 0 external file

Step 2: Multiply UFC with Weight Factor based on the table below to have UFP

simple average complex

users inputs

users Outputs

users requests

files

external interfaces

UFP = (2*4) + (2*5) + (3*4) + (2*10) + (0*7) = 50

3

|

3

7

5

1

5

1

10

7

6

7

6

15

10

Step 3: Calculate the total TCF (Technical Complexity Factor) by assigning 0-5

- Distributed data processing: |

- Performance criteria: 4

- Heavily Utilized Hardware: 2

- High Transaction Rates: 3

- Online Data Entry: 4

- Online Updating: 4

- End-user Efficiency: 3

- Complex computations: 3

- Reusability: 2

- Ease of installation: 0

- Ease of Operation: 3

- Portability: 4

- Maintainability: 3

Step 4: Add all points in step 3 to have DI (Degree of Influence)

DI = 39

Step 5: Calculate TCF based on DI in step 4

TCF = 0.65 + 0.01 * 39 = 1.04

Step 6: Calculate FP = UFP * TCF

FP= 50 * 1.04 =52

Step 7: Calculate KLOC = FP * LOC_per FP/ 1000 Depending on the programming language, this formula calculates LOC based on the table below Relation between LOC and FPs

Based on the googling, the LOC/FP is around 35 for Javascript So:

KLOC = 52 * 30/1000 = 1.56

So, we can have the effort, duration, and resource number based on the type of this project which is Semidetached mode:

- E=3.0* (1.56 * 1.12) =4.94 (man-months)

- D=2.5 * (4.94% 0.35) = 4 37 (months)

- P=4,94/4.37 = 1.13 (people)

Based on the Gantt Chart:

DURATIO BASELINE

1 Identify the project

Choose the topic, define

LỊ project's goal and scope | week 10h

1.2 Make an initial plan 1 week 10h

1.3 Identify stakeholders 1 week 10h

2 Analysis and Design

specification

22 Use-case Diagram, Use-case | week 10h

description

2.4 Architecture Design 2 weeks 20h

3 Development

31 Set up version control and | week 10h

development environment

3.2 Code backend functionality 3 weeks 30h

34 Integrate frontend and backend | week 10h

41

42

43

5.1

6.1

6.2

6.3

6.4

IV Estimated human resources

TASK ID

1

12

13

14

Develop unit test cases for

individual modules

Execute unit tests, fix defects,

and perform code reviews

Address integration issues,

update documentation

Deployment

Deploy the web app to

production environment,

monitor, and resolve immediate

issues

Summary

Review frontend

Review backend

Review system

Write report

TASK TITLE

Identify the project

Choose the topic, define

project's goal and scope

Make an initial plan

Identify stakeholders

Domain Context

Human Resources

Identify Technology

Analysis and Design

Project requirements

1 week 10h

1 week 10h

1 week 10h

1 week 10h

1 week 10h

1 week 10h

1 week 10h

2 weeks 20h

TASK OWNER

Trần Huy Nam Hưng, Vũ Việt Hưng, Võ Trung Kiên, Tran Gia Linh, Phan Mai Tan Lợi, Phạm Quỳnh Trân, Lê Bá Tân Trần Gia Linh, Phạm Quỳnh Trân, Lê Bá Tân

Trần Huy Nam Hưng

Vũ Việt Hưng

Trần Huy Nam Hưng

Võ Trung Kiên

Trần Huy Nam Hưng, Vũ Việt Hưng, Võ

2,2 >

2,6

32

3,3

3,4

41

42

43

5,1

6,3

Use-case Diagram, Use-case

description

System Modeling

Architecture Design

Database Design

UI Design

Development

Set up version control and

development environment

Code backend functionality

Implement frontend

Integrate frontend and

backend components

Testing

Develop unit test cases for

individual modules

Execute unit tests, fix

defects, and perform code

reviews

Address integration issues,

update documentation

Deployment

Deploy the web app to

production environment,

monitor, and resolve

immediate issues

Summary

Review frontend

Review backend

Review system

Lé Ba Tan

Vũ Việt Hung

Võ Trung Kiên, Phan Mai Tấn Lợi

Vũ Việt Hưng, Trần Huy Nam Hưng Phạm Quỳnh Trân, Trần Gia Linh

Trần Huy Nam Hưng, Vũ Việt Hưng, Võ Trung Kiên, Tran Gia Linh, Phan Mai Tan Lợi, Phạm Quỳnh Trân, Lê Bá Tân

Vũ Việt Hưng, Trần Huy Nam Hưng Phạm Quỳnh Trân, Trần Gia Linh, Võ Trung Kiên

Lê Bá Tân, Phan Mai Tấn Lợi

Võ Trung Kiên, Trần Huy Nam Hưng, Vũ

Việt Hưng

Lê Bá Tân, Phan Mai Tấn Lợi

Phạm Quỳnh Trân, Trần Gia Linh

Võ Trung Kiên, Trần Huy Nam Hưng, Vũ

Việt Hưng

Phạm Quỳnh Trân, Trần Gia Linh Trần Huy Nam Hưng, Vũ Việt Hưng

Lê Bá Tân, Võ Trung Kiên, Phan Mai Tân