ASSIGNMENT SOLUTION
Faculty of Engineering and Technology
Ramaiah University of Applied Sciences
Department Computer Applications Programme MCA
Semester/Batch 01 / 2025
Course Code CAC514A Course Title Software Engineering
Course Leader Dr. A. Abdul Rasheed / Mr. Hari Nyshadam
Register No. 25ETCA172020
Name of the Student DELWIN K. N
1. Determine functional and non-functional requirements for the
10
1 system.
Marks
Requirements:
A requirement is a statement that defines the actions that a system is
expected to perform. A requirement is the basis for the development of a
system. It consists of a statement that defines a constraint that a system
must work under.
Functional Requirements (AWSCMS)
Functional Requirements specify what system should do. And describes
what are Functional Requirements included in AWSCMS.
1. Users Authentication:Allows Citizens and Administrators to register
and login to the System.
2. AI Waste Classification:Uses Camera and Image recognition to
classify waste into organic, recyclable and in hazardous types of waste.
3. Sensor Monitoring:IOT Sensors in smart bins measure fill
levels,temperature and in emergency conditions.
4. Real Time Bin Status:Updates bin condition dynamically as
empty,partially full or fully based on sensor data.
5. Alert Generation:Sends automatic alerts to municipal authorities
when bins are full or hazardous situations occur.
6. Route Optimization:Optimizes garbage truck routes according to real
time bin data to reduce fuel and time wastage.
7. Citizen Mobile App:It offers citizens information on location of bins
and garbage collection schedules.
8. Admin Dashboard:Provides analytical data on heat maps,efficiencies
and other operations.
9. Notification Service:The service provides alerts concerning
segregation and changes in the timetable.
Non-Functional Requirements (AWSCMS)
Non-Functional Requirements specify how well the system must work.
They define how the system must work. NFR included in AWSCMS are:
1. Performance: The system must be able to handle the speed of the
system it must process the request in very short time.
2. Scalability: It must be able to handle thousands of bins and users as
the system expands into various cities.
3. Security: The main thing in the system must be of the security it must
keep the privacy of citizen information and data.
4. Reliability: The System should operate with minimal failure incidents.
5. Availability: The Should be always available to administrators and
citizens.
6. Usability: The Interface should be very simple so that the users can
use the system properly.
7. Maintainability: System Components such as AI and Sensor software
should be easy to maintain.
8. Interoperability: The System should interact with maps, existing city
infrastructure and third-party services.
9. Safety: System must be able to sense fire danger or heating bins.
1. Select an appropriate SDLC model and justify its use.
5
2 Marks
Agile SDLC Flow for AWSCMS
[Link] Gathering and planning:
It collects and analyze requirement by engaging with municipalities,
citizens and waste collector the main work of the collector to understand
their needs challenges and expectation,
[Link] (Sprint Planning):
It defines the architecture for the specific agile model which we
implemented for SDLC model flow for AWSCMS. It mainly for AI, IOT, mobile
app and dashboard.
[Link] (Incremental Builds):
The main important development is to build modules in iteration for
example. The waste classification is developed to bin monitor and route
optimization.
[Link] (Continuous):
It checks the validate artificial intelligence accuracy, and also checks the
sensor integration and few app usability which mainly used test the access
control of the testing process
[Link] (Sprint Releases):
It launches an initial pilot version for the system to control, real-world
environment to test the core features and functionality. This iterative
refinement ensures the system becomes more reliable, user-friendly, and
ready for full-scale deployment.
[Link]:
Its continuous monitoring the system control and manages the system test
process it also fixes the bugs that as occurs during the requirements
gathering and planning and even during deployment and AI retraining, and
feature enhancements.
7. Feedback Loop:
In this process we give the feedback about the particular updates that the
system needs to make the changes according to the citizens requirements.
It can be mobile app issues where there the system should keep on
updating the particular dashboards.
Prepare the following UML diagrams:
a. Use Case Diagram
1.3 20
b. Class Diagram
Marks
c. Sequence Diagram
d. Activity Diagram
1.3. Use Case Diagram
a 5 Marks
1. Citizen: View bin locations, get segregation tips, check schedules,
report issues, receive notifications.
2. Waste Collector: View optimized routes, update status, check fill
levels, navigate to bins.
3. Municipal Admin: View dashboard/analytics, monitor bins, generate
reports, manage users, configure alerts, view heatmaps.
4. Advanced Features: AI waste classification, sensor monitoring
(fill/temp/fire), automated route optimization enhance core functions.
1.3. b Class Diagram
5 Marks
1. User Roles: User class has three types - Citizen (reports issues),
Waste_Collector (collects waste), Administrator (manages system).
2. SmartBin: Contains Sensor (monitors fill level) and AI_Module (classifies
waste into categories).
3. Collection: collectionRoute optimizes paths and generates Alerts for
collection needs.
4. Integration: Citizens create Reports, AI classifies waste, collectors
follow routes, and alerts notify all users automatically
1.3. Sequence Diagram 5
c
Marks
1. Waste Classification & deposit: Citizen deposits waste, SmartBin
opens, Camera captures image, AIModule classifies waste type and directs
to correct compartment.
2. Monitor level: SmartBin requests Sensor to measure fill level, data is
sent to Database for tracking.
3. Alert Trigger (>80%): Database checks if collection needed. If >80%
full,alert is generated and sent to Admin via AlertSystem.
4. Route Assignment & Optimization: Admin requests RouteOptimizer
to calculate best route, schedule is updated, and task is assigned to
Collector who accepts it.
5. Reset & Collection: Collector travels to location, empties bin, marks as
collected. Fill level resets. If <80%, system continues normal monitoring.
1.3. Activity Diagram
5
d Marks
[Link] Sorting: Citizen deposits waste, the smart bin opens,
camera captures the waste image, and AI identifies and sorts it into the
correct compartment.
2. Normal Monitoring: Sensors continuously check the bin's fill normal
after each deposit.
3. Decision Point: System checks if bin is more than 80% full to
determine next action.
4. Collection Triggered: If >80% full, an alert is generated, route is
optimized, collector is assigned, waste is collected, and system updates.
5. Normal Mode: If <80% full, system continues monitoring without
triggering collection.
1. System architecture, database design, and user-interface
15
4 Marks
System Architecture
1. Edge IOT (Layer 1): Smart bins with edge computing and
communication modules collect and transmit waste data.
2. Networking (Layer 2): IoT Gateway and Message Broker (Kafka)
handle data routing and communication between system components.
[Link] (Layer 3): Core services for waste classification, bin
monitoring, route optimization, alerts, user management, analytics, and
geospatial processing.
[Link] Management (Layer 4): PostgreSQL for structured data,
MongoDB for unstructured data, and Data Warehouse for massive datasets
and analytics.
[Link] & AI Layers (Layer 5-6): User interfaces (Citizen,
Collector, Admin) powered by AI/ML models for waste classification and
predictions, secured by TLS encryption and monitored via Prometheus with
DevOps tools (Kubernetes, Docker) for deployment
[Link] and Monitoring: In this layer the system security, system
monitoring and develops and CICD (Docker).
Database design
1. User Management: USER table stores user information (id, name,
phone, role) and connects to NOTIFICATION table for alerts and messages.
2. Smart Bin System: SMART_BIN table tracks bin location, waste type,
and fill level. WASTE_DATA table logs waste deposits with timestamps
linked to bins.
3. Collection Scheduling: COLLECTION_SCHEDULE table manages pickup
schedules by linking bins and drivers with date, time, and status
information.
4. Driver Management: DRIVER table stores driver details (id, vehicle
number, name) for assignment to collection routes.
5. Relationships: Foreign keys connect tables - notifications to users,
waste data to bins, and schedules to both bins and drivers, creating an
integrated waste management system.
User-Interface
1. Bin ID:
Displays specific bin ID (ID-001) for tracking which smart bin the citizen is
viewing.
2. Waste Type:
Shows the type of waste accepted at this bin (DRY waste), helping citizens
properly segregate their waste.
3. Fill Level Indicator:
Displays current bin capacity at 80%, informing citizens if the bin is nearly
full before they visit.
4. Collection Time:
Shows next scheduled pickup time (TODAY 6PM), so citizens know when
the bin will be emptied.
5. User Actions:
Provides buttons for viewing notifications and reporting issues directly from
the dashboard for quick communication.
1. Testing Strategy and sample test cases
5
5 Marks
Testing Strategy:
Testing ensures the system works correctly and reliable, Different testing
methods used check individual components and the complete system.
•Unit testing: Here individual components of the systems are tested
separately like waste classification, sensor dada reading, alert system.
•Integration Testing :Date from bins reaches the serves correctly. AI
result Are shared properly with mobile apps and dashboards.
•System Testing: Full bin detection and alert generation. Route updates
for drivers. Real-time monitoring for administrators.
•Security Testing :Login and authentication mechanisms. Role-based
access for citizens, drivers, and administrators.
Marks
Sectio
Part
First
Max.
Marking Scheme Moderat
Examine
ns
or
r
1.1 Requirements analysis 5
Part -1
1.2 SDLC model 5
1.3 UML Diagrams 20
1.4 Architectural Diagram, Databases 15
1.5 Test Cases 5
Total Marks 50