PROJECT

PROPOSAL
Project Title: Fisheries Automation System
Team Name: Nexus_Trio

Submitted by:
Zahidul Islam Preetul (2022831049)
Dipto Panday (2023831038)
Ahmad Amin (2022831044)

Submitted to:
Dr. Ahsan Habib
Associate Professor,
Institute of Information and Communication Technology,
Shahjalal University of Science and Technology, Sylhet.
Business Requirement Specification
Fisheries Automation System

Authors

Name Registration Number Signature

Zahidul Islam Preetul 2022831049

Dipto Panday 2023831038

Ahmad Amin 2022831044

Stakeholders

Name Designation Signature

Shailen Haldar Fish Pond Owner

 Introduction

Traditional fish farming often relies on manual monitoring of water conditions, feeding schedules, and fish health
tasks that are time-consuming, error-prone, and inefficient. In many cases, delayed detection of poor water quality or
disease leads to high fish mortality, reduced yield, and economic losses.

As demand for fish increases globally, there is a growing need for intelligent systems that can continuously monitor
environmental parameters, automate routine tasks, and support data-driven decisions.

The proposed Fisheries Automation System (FAS) aims to bring modern automation and IoT (Internet of Things)
technologies into aquaculture. By integrating sensors for water quality (e.g., temperature, dissolved oxygen, pH,
ammonia), automated feeders, cameras, and a centralized dashboard, the system will enable real-time monitoring
of fish ponds/tanks, timely detection of health issues, and efficient management of feeding, water conditions, and
mortality tracking.

This approach reduces manual workload, improves fish survival and growth rates, and enhances profitability.

Moreover, such automation supports sustainable aquaculture: optimized feeding reduces waste, controlled water
conditions reduce disease risks, and better record-keeping improves transparency and repeatability. With this system,
fish farmers can operate more efficiently, respond faster to crises, and scale operations with confidence.
 Purpose

The purpose of this Business Requirements Specification (BRS) document is to explain what the Fisheries
Automation System will do and the problems it will solve. This document will be a common understanding between
development team and the client.

By reviewing and approving this document, the client confirms that the requirements described here accurately
represent their expectations.

Problem Statement

The current system is guess-based. The workers cannot precisely measure feed quantity. The feed has to be manually
given by someone. Which also takes physical labor and time.

The workers cannot identify the specific problem why water quality has gone wrong. And solving the problem is also
guess-based. For example, low oxygen related problems that cause fish to get up and open mouth, waste material
increase in pond water.

Determining fish sickness is also very slow and inefficient in the current system. The workers has to identify sick
fishes and then take those to experts or bring experts to diagnose the specific disease and explain the cure process.
This is costly and time consuming.
 Objectives

General Objective:

To develop an Automation System that continuously monitors pond/tank conditions, automates feeding, and
tracks fish health and mortality enhancing productivity, reducing losses, and enabling remote farm management.

Specific Objectives:

Gather detailed functional and non-functional requirements from stakeholders, observe current fish-farming
workflows, and analyze user needs to ensure that the system design aligns with real-world farming practices and
operational challenges.

Implement real-time monitoring of water quality parameters (temperature, dissolved oxygen, pH, ammonia,
etc.) and generate alerts when values deviate from safe ranges.

Automate feeding schedules and integrate fish-health and mortality tracking (including recording unusual
behavior, disease symptoms, and deaths).

Provide a centralized dashboard and reporting system to manage multiple ponds/tanks offering historical logs,
analytics, and insights for decision-making.
 Scope

The following features and activities are included in the Fisheries Automation System:

Monitoring of water quality parameters such as temperature, dissolved oxygen, pH, and ammonia.

Automated control of fish feeding based on predefined schedules.

Recording and tracking of fish health conditions, disease symptoms, and mortality data.

Real-time alerts and notifications when water conditions become unsafe or unusual events occur.

Stakeholders

The following people are connected with this project:

1. Fish Farmer
He owns the pond and takes care of the fish every day.

2. Farm Manager (if any)

He helps with feeding fish and other daily work.

3. System Admin
He looks after the system and keeps it working.

4. Project Manager
He checks the work and makes sure everything is going well.

5. Developers
They build the system based on the given needs.
 User Stories

Daily Routine:

The pond owner has multiple ponds. He has hired some people to work on the ponds. The workers go to the pond at
morning and inspect the water, smell, color etc. They mainly give feed not by measuring precisely, but keep some sort
of measurement by a small pot and give the feed by hand. They come to check the pond again at evening. Some days
they give feed some days they don’t. They keep track of fingerlings, feed cost in a small notebook which they give to
the pond owner regularly to check. The pond owner is troubled by the sudden death of fishes for unknown reasons.
They determine the time of catching the fishes by generally looking at fish size. They don’t keep track of profit or loss
from each pond. The pond owner mentioned, they face the most risk in rainy season. Flash floods cause pond water to
mix with flood water and fish flow away.

The Timeline of Buying Fingerling to Selling Fish:

First they empty the pond, renewing pond water, cleaning mud etc. They don’t measure precisely, only based on
previous experience and assumptions. They buy fingerling from hatchery. The amount depends on which fish they’re
farming. Usually 500-700 fingering at a time. Fingerlings die if the water becomes too hot. Water changes are required
rarely. Occasional catching and inspecting sizes determines whether fish size is appropriate for selling. Sometimes
additional fertilizers (Urea, Oxygen tablet, limestone) are required to balance oxygen, carbon di-oxide, ammonia etc.
water quality factors. Usually after 15-20 days.
 Story List

1. Automatic Feeding

As a fish farmer, I want the system to feed the fish automatically so that feeding is consistent and not forgotten.
As a farmer, I want to set feeding times and amounts so I can control the feeding schedule easily.
As a farmer, I want to get alerts if the feeder stops working so I can fix issues quickly.

2. Water Quality Monitoring

As a farmer, I want sensors to measure temperature, DO, pH, and ammonia so I can track water health at all times.
As a farmer, I want instant alerts when any water-quality value goes out of range so I can take action immediately.
As a farmer, I want to see daily and weekly water-quality graphs so I can notice changes over time.

3. Fish Health & Disease Tracking

As a farmer, I want to record symptoms when fish look sick so the system keeps a disease history.
As a farmer, I want the camera to detect floating dead fish so I can remove them quickly.
As a farmer, I want the system to warn me when sensor patterns indicate possible disease so I can prevent
outbreaks early.

4. Mortality Tracking

As a farmer, I want the system to automatically log when dead fish are detected so I don’t miss any incidents.
As a farmer, I want to manually input dead fish counts so the system keeps accurate records.
As a farmer, I want mortality reports so I can understand which ponds have more problems.

5. Pond/Tank Management

As a farmer, I want every pond/tank to have its own dashboard so I can manage them individually.
As a farmer, I want to track total fish count, species, and growth rate for each pond so I always know stock status.
As a farmer, I want to receive reminders for cleaning, water change, or harvesting.

6. Real-Time Alerts & Notifications

As a farmer, I want to get instant notifications (SMS/app) during emergencies so I can respond immediately.
As a farmer, I want different alert levels (warning, critical) so I know the urgency.

7. Camera Monitoring

As a farmer, I want a live camera view of each pond so I can check fish behavior remotely.
As a farmer, I want photo uploads saved during disease events so I can compare with previous cases.

8. Reporting & Analytics

As a farmer, I want monthly reports showing feed usage, water quality, fish growth, and mortality so I can
understand performance.
As a farmer, I want the system to show trends that help prevent problems before they occur.
9. User & Role Management

As a manager, I want to create accounts for workers so they can access the system with limited
permissions.
As a worker, I want a simple interface to record daily tasks like feeding, cleaning, and checking ponds.

10. Automation & Control

As a farmer, the system to automatically turn on aerators when dissolved oxygen drops so fish don’t suffocate.
As a farmer, I want it to pause feeding if ammonia gets too high so water doesn’t get worse.
As a farmer, I want manual override options so I can control devices myself when needed.
 Functional Requirements

The system should help the farmer keep basic information about the pond.

The system should help the farmer note down when and how much feed is given.

The system should help the farmer remember feeding times.

The system should allow the farmer to note any fish problems or sickness.

Non-Functional Requirements

The system should be easy for anyone to use.

The system should not be slow.

The system should work smoothly most of the time.

The system should keep personal information private.

The system should not stop working suddenly.

The system should be usable whenever needed.

The system should show clear and correct information.

 Assumptions

The user has a phone or a computer to use the system.

The user knows how to use a phone or simple apps.

Internet is usually available.

The fish farmer is interested in using the system.

The user gives true information.

Fish farming work is done in the usual way.

Constraints

The system will not work without internet.

Big changes later may not be possible.

Budget is limited.
 Methodologies for Achieving Each Objective

Objective 1: Requirement Collection & Analysis

Conduct stakeholder interviews with fish farmers, farm managers, workers, and technical experts to understand
their challenges, current workflows, and expectations from an automated system.

Observe on-site operations to identify key points in feeding, water monitoring, disease detection, and record-
keeping, ensuring the system reflects real farm conditions.

Collect functional and non-functional requirements through questionnaires, checklists, and direct discussions,
then prioritize them based on feasibility, user importance, and system value.

Analyze all gathered requirements to create clear use cases, user stories, and process flows that accurately
represent the needs of different types of users.

Review and validate these requirements with stakeholders to ensure completeness, correctness, and alignment
with the project’s goals.

Objective 2: Water Quality Monitoring & Alerts

Deploy appropriate sensors (e.g., temperature probes, DO sensors, pH sensors, ammonia/chemical sensors) in
each pond/tank.

Use a microcontroller or IoT device to collect sensor data at regular intervals (e.g., every few minutes).

Transmit data to a cloud or local server database.

Implement threshold-based alert logic: when any parameter crosses a safe limit, trigger notifications (app, SMS,
or dashboard alert).

Log all sensor readings in a time-series database for trend analysis and historical review.
 Methodologies for Achieving Each Objective

Objective 3: Automated Feeding & Health/Mortality Tracking

Install automated feeders controlled by the system (scheduled feed times, amount per session).

Use cameras or image-based monitoring to observe fish behavior and detect anomalies (e.g., lethargy, abnormal
swimming, visible lesions). Optionally, allow manual input of observed symptoms by farm staff.

Maintain a record-keeping module: for each pond/tank, store entries of disease signs, treatment history, and
mortality counts.

When mortality or symptoms are recorded (automatic via camera or manual input), flag the pond/tank and
generate alerts for inspection or intervention.

Objective 4: Dashboard, Reports & Analytics for Multi-Pond Management

Develop a web or mobile-based dashboard that shows live data from all sensors, feeding status, health logs, and
mortality statistics per pond/tank.

Build reporting functionality: daily/weekly/monthly summaries water quality trends, feed usage, mortality rate,
disease incidents, fish growth (if weight/size tracking is added).

Provide historical data visualization (graphs, charts) to help the farmer recognize patterns or recurring problems.

Optionally include user-role management so that farm owners, operators, and technicians have appropriate access
rights.
 Expected Outcomes

Increased Productivity and Yield

Precise management of the farm environment and fish health is expected to increase overall yield through improved
growth rates, reduced stress, and preemptive disease management

Significant Operational Cost Savings

Automation of feeding, monitoring, and maintenance will reduce reliance on manual labor. Optimized feeding alone
can cut the largest cost center.

Enhanced Sustainability

Precise feeding and waste management will minimize nutrient runoff and environmental impact. Reduced disease
outbreaks will lower the need for antibiotics and chemicals. Improved resource efficiency will contribute to a smaller
carbon footprint per unit of production
 References

Norway's Automated Salmon Aquaculture: Norway, as the world's largest farmed salmon producer, is a global
leader in integrating automation. Industrial-scale farms employ thousands of sensors, AI-driven feeding systems,
and underwater drones for inspection and cleaning. Research institutions like SINTEF Ocean and NTNU are at
the forefront, developing autonomous robotic systems for net repair and advanced AI models for feed
optimization.

The TEFIMO Project (EU): This research initiative, co-funded by the European Union, is explicitly developing
AI and environmental DNA (eDNA) methods for automated fisheries monitoring. Its goal is to support sustainable
management by enabling fully documented catches and holistic ecosystem assessments, aligning closely with the
monitoring objectives of FAS.

Industry Adoption of Management Platforms: Technology providers like Folio3 AgTech and Farmonaut offer
commercial aquaculture management software and platforms. These solutions integrate IoT data, provide analytics
dashboards, and incorporate traceability features, demonstrating the market viability and existing adoption of the
core components that FAS aims to synthesize into a seamless system.
 Task List with Time Estimation
Task Duration
Task Name Description
ID (Weeks)

Requirement analysis and validation based on user

T1 Requirements Analysis 3
stories

T2 System Architecture Design Overall system architecture and database design 2

UI/UX design for dashboards, alerts, and data

T3 UI/UX Design 2
visualization

Automatic feeding system implementation with

T4 Auto Feeding System 3
scheduling and failure detection

Water quality monitoring module (temperature,

T5 Water Quality Monitoring 2
DO, pH, ammonia) with real-time alerts

Fish health and disease tracking module with

T6 Fish Health Tracking 3
symptom logging and pattern analysis

Camera-based monitoring and dead fish detection

T7 Camera Monitoring System 3
system

Mortality tracking system with automatic logging

T8 Mortality Management 2
and manual input support

Pond/tank management module including stock,

T9 Pond Management 2
growth, and maintenance reminders

Real-time alert and notification system with priority

T10 Alert & Notification System 3
levels

Automation and control module (aerator control,

T11 Automation & Control 3
feeding pause logic)

Reporting and analytics module with trends and

T12 Reporting & Analytics 2
monthly performance reports

System integration, testing, deployment, and

T13 Integration & Deployment 3
documentation

The task list shows all major activities required to develop the Fisheries Automation System. It includes
requirements analysis, system design, module development, monitoring and automation features, testing, and
deployment. This table helps in planning, organizing, and managing the overall project work efficiently.
 Dependency Table

Task
Task Name Duration (Weeks) Depends On
ID

T1 Requirements Analysis 3 None (starting task)

T2 System Architecture Design 2 T1

T3 UI/UX Design 2 T1, T2

T4 Auto Feeding System 3 T2, T3

T5 Water Quality Monitoring 2 T2, T3

T6 Fish Health Tracking 3 T5

T7 Camera Monitoring System 3 T2

T8 Mortality Management 2 T6, T7

T9 Pond Management 2 T4, T5, T8

T10 Alert & Notification System 3 T4, T5, T6

T11 Automation & Control 3 T5, T10

T12 Reporting & Analytics 2 T4, T5, T8, T9

T1, T2, T3, T4, T5, T6, T7,

T13 Integration & Deployment 3
T8, T9, T10, T11, T12

The dependency table shows the relationships between different tasks in the Fisheries Automation System project. It
identifies the duration of each task and the tasks that must be completed before starting the next one. This table helps
in understanding task sequence, managing dependencies, and creating an effective project schedule.
 Gantt Chart

Task w w w w w w w w w w w w w w w w w w w w w
Task Name
ID 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21

T1 Requirements Analysis

T2 System Architecture Design

T3 UI/UX Design

T4 Auto Feeding System

T5 Water Quality Monitoring

T6 Fish Health Tracking

T7 Camera Monitoring System

T8 Mortality Management

T9 Pond Management

T10 Alert & Notification System

T11 Automation & Control

T12 Reporting & Analytics

T13 Integration & Deployment

The Gantt chart presents a visual timeline of all project activities for the Fisheries Automation System. It shows the
start and end weeks of each task based on their dependencies and duration. This chart helps in tracking project
progress, identifying parallel tasks, and ensuring timely completion of the overall system.
Attribute List of Requirement Analysis

Task ID : T1
Task Name : Requirements Analysis
Duration : 3 Weeks
Type : Initial / Planning Phase Task
Dependency : None (Starting Task)
Input : User needs, stakeholder requirements, existing system data
Output : Software Requirement Specification (SRS) document
Responsible Role : Business Analyst / System Analyst
Priority : High (Foundation of the project)

Use Case of Requirement Analysis

Use Case Name : Gather and Define System Requirements

Actor(s) :
Client / Stakeholders
System Analyst
Description : The system analyst collects, analyzes, and documents functional and non-functional
requirements from stakeholders. These requirements are validated and finalized to ensure clarity
and completeness.
Precondition : Project scope is defined and stakeholders are available.
Postcondition : A validated SRS document is prepared and approved for system design phase.
Attribute List of System Architecture Design

Task ID : T2
Task Name : System Architecture Design
Duration : 2 Weeks
Type : Design Phase Task
Dependency : T1 (Requirements Analysis)
Input : Approved SRS document
Output : System Architecture Diagram, Database Design, Technical Design Document
Responsible Role : System Architect / Software Engineer
Priority : High (Defines system structure)

Use Case of System Architecture Design

Use Case Name : Design System Architecture

Actor(s) :
System Architect
Development Team
Description : The system architect designs the overall structure of the system, including modules,
components, database schema, and communication between subsystems. The design ensures
scalability, performance, security, and maintainability.
Precondition : Requirements are finalized and approved.
Postcondition : A complete architecture design is prepared and ready for implementation.
Attribute List of UI/UX Design

Task ID : T3
Task Name : UI/UX Design
Duration : 2 Weeks
Type : Design Phase Task
Dependency : T1 (Requirements Analysis), T2 (System Architecture Design)
Input : Approved requirements and system architecture
Output : Wireframes, Mockups, UI Prototypes, Design Specifications
Responsible Role : UI/UX Designer
Priority : High (Ensures usability and user satisfaction)

Use Case of UI/UX Design

Use Case Name: Design User Interface and Experience

Actor(s):
UI/UX Designer
End User (for feedback)
Description:
The UI/UX designer creates wireframes and visual layouts for dashboards, monitoring panels, alerts, and reports. The
design focuses on usability, accessibility, and smooth user interaction. Feedback is collected and incorporated to
improve the user experience.
Precondition:
System requirements and architecture are finalized.
Postcondition:
Approved UI design and prototypes are ready for development.
Attribute List of Auto Feeding System

Task ID : T4
Task Name : Auto Feeding System
Duration : 3 Weeks
Type : Core Functional Module
Dependency : T2 (System Architecture Design), T3 (UI/UX Design)
Input : Feeding schedule settings, sensor data, system configuration
Output : Automated feeding operations, feeding logs, failure alerts
Responsible Role : Software Developer / Embedded System Engineer
Priority : High (Core automation feature)

Use Case of Auto Feeding System

Use Case Name: Automate Fish Feeding

Actor(s):
Fish Farm Operator (User)
System Controller
Description:
The user sets feeding schedules and quantity through the system interface. The system automatically activates the
feeding mechanism at scheduled times. It monitors feeding status and detects failures or malfunctions. Notifications
are generated if issues occur.
Precondition:
System is configured and feeding schedule is set.
Postcondition:
Fish are fed automatically according to schedule, and feeding activity is recorded.
Attribute List of Water Quality Monitoring

Task ID : T5
Task Name : Water Quality Monitoring
Duration : 2 Weeks
Type : Core Monitoring Module
Dependency : T2 (System Architecture Design), T3 (UI/UX Design)
Input : Sensor data (temperature, pH, dissolved oxygen, ammonia levels)
Output : Real-time water quality data, alerts, monitoring logs
Responsible Role : Software Developer / IoT Engineer
Priority : High (Critical for fish survival)

Use Case of Water Quality Monitoring

Use Case Name: Monitor Water Parameters

Actor(s):
Fish Farm Operator
Water Quality Sensors
System
Description:
The system continuously collects data from water quality sensors. It displays real-time parameter values on the
dashboard and compares them with predefined threshold levels. If any parameter exceeds safe limits, the system
generates alerts and notifications for corrective action.
Precondition:
Sensors are installed and properly calibrated.
Postcondition:
Water conditions are continuously monitored, and alerts are triggered when abnormal conditions are detected.
Attribute List of Fish Health Tracking

Task ID : T6
Task Name : Fish Health Tracking
Duration : 3 Weeks
Type : Core Monitoring & Management Module
Dependency : T4 (Auto Feeding System), T5 (Water Quality Monitoring)
Input : Health observations, sensor data, feeding records, disease symptoms
Output : Health status reports, disease alerts, health history logs
Responsible Role : Software Developer / System Analyst
Priority : High (Ensures productivity and loss prevention)

Use Case of Fish Health Tracking

Use Case Name: Track and Monitor Fish Health

Actor(s):
Fish Farm Operator
System
Description:
The operator records fish health conditions, symptoms, or unusual behavior in the system. The system analyzes
related data such as water quality and feeding patterns to detect possible health risks. It maintains health records and
generates alerts if abnormal conditions are identified.
Precondition:
Monitoring systems are active and data collection is ongoing.
Postcondition:
Fish health data is stored, analyzed, and available for decision-making and preventive action.
Attribute List of Camera Monitoring System

Task ID : T7
Task Name : Camera Monitoring System
Duration : 3 Weeks
Type : Monitoring & Surveillance Module
Dependency : T2 (System Architecture Design), T3 (UI/UX Design)
Input : Live video feed from pond cameras
Output : Real-time video monitoring, activity analysis, abnormal behavior alerts
Responsible Role : Software Developer / IoT Engineer
Priority : Medium–High (Supports monitoring and safety)

Use Case of Camera Monitoring System

Use Case Name: Monitor Fish Activity via Camera
Actor(s):
Fish Farm Operator
Camera Device
System
Description:
The system captures live video feed from installed pond cameras. The operator can view real-time footage through the
dashboard. The system may analyze fish movement patterns and detect unusual behavior such as low activity or dead
fish. Alerts are generated if abnormal conditions are detected.
Precondition:
Cameras are installed and connected to the system.
Postcondition:
Live video is available for monitoring, and abnormal activities are recorded and reported.
Attribute List of Mortality Management

Task ID : T8
Task Name : Mortality Management
Duration : 2 Weeks
Type : Management & Record-Keeping Module
Dependency : T6 (Fish Health Tracking), T7 (Camera Monitoring System)
Input : Mortality reports (manual entry or camera detection), health data
Output : Mortality records, statistics, alerts, loss analysis reports
Responsible Role : Software Developer / Farm Operator
Priority : High (Loss tracking and decision-making)

Use Case of Mortality Management

Use Case Name: Record and Manage Fish Mortality

Actor(s):
Fish Farm Operator
System
Description:
The operator records dead fish manually or confirms system-detected mortality cases. The system stores mortality
data, calculates loss statistics, and analyzes trends. Reports are generated to help identify causes and reduce future
losses.
Precondition:
Fish health and monitoring systems are active.
Postcondition:
Mortality data is recorded, analyzed, and available for management decisions.
Attribute List of Pond Management

Task ID : T9
Task Name : Pond Management
Duration : 2 Weeks
Type : Operational Management Module
Dependency : T8 (Mortality Management)
Input : Stock data, growth records, feeding logs, water quality data
Output : Pond status reports, stock tracking data, operational updates
Responsible Role : Farm Operator / System Administrator
Priority : High (Overall farm management control)

Use Case of Pond Management

Use Case Name: Manage Pond Operations

Actor(s):
Fish Farm Operator
System
Description:
The operator manages pond-related information including fish stock levels, growth rates, maintenance activities, and
operational records. The system stores and organizes this data to provide an overall view of pond performance and
productivity.
Precondition:
Monitoring and management modules are active.
Postcondition:
Updated pond data is stored, and performance insights are available for decision-making.
Attribute List of Alert & Notification System

Task ID : T10
Task Name : Alert & Notification System
Duration : 3 Weeks
Type : Development / Functional Module Task
Dependency : T4 (Auto Feeding System), T5 (Water Quality Monitoring), T6 (Fish Health Tracking)
Input : Feeding events, water quality data, fish health data, predefined alert thresholds
Output : Real-time alerts, notification messages, alert history logs
Responsible Role : System Developer / System Analyst
Priority : High (Supports monitoring and automated response)

Use Case of Alert & Notification System

Use Case Name : Monitor Events and Send Notifications

Actor(s) :
• System
• Farm Manager / End User
• Administrator
Description : The system continuously monitors data from the Auto Feeding System, Water Quality Monitoring, and
Fish Health Tracking modules. When predefined thresholds or abnormal conditions are detected, the system generates
alerts and sends notifications to the farm manager or administrator via configured channels. All alert activities are
recorded for tracking and future analysis.
Precondition : T4, T5, and T6 modules are implemented and operational; alert rules and notification preferences are
configured.
Postcondition : Relevant users receive notifications, and alert records are stored in the system database.
Attribute List of Automation & Control

Task ID : T11
Task Name : Automation & Control
Duration : 3 Weeks
Type : Development / Control Module Task
Dependency : T5 (Water Quality Monitoring), T10 (Alert & Notification System)
Input : Water quality data, alert signals, predefined control rules, system thresholds
Output : Automated control actions (e.g., feeder control, aerator activation), control logs
Responsible Role : System Developer / Control System Engineer
Priority : High (Ensures real-time automated system response)

Use Case of Automation & Control

Use Case Name : Execute Automated Control Actions

Actor(s) :
• System
• Farm Manager / Administrator
Description : The system continuously evaluates water quality data and alert notifications. Based on predefined
automation rules and control parameters, it automatically triggers control actions such as activating aerators, adjusting
feeding schedules, or regulating water pumps. The system ensures optimal pond conditions without requiring constant
manual intervention, while allowing administrators to override settings when necessary.
Precondition : T5 (Water Quality Monitoring) and T10 (Alert & Notification System) modules are fully functional;
automation rules and control parameters are configured.
Postcondition : Required control actions are executed automatically, and all actions are recorded in the system logs.
Attribute List of Reporting & Analytics

Task ID : T12
Task Name : Reporting & Analytics
Duration : 2 Weeks
Type : Development / Analytical Module Task
Dependency : T4 (Auto Feeding System), T5 (Water Quality Monitoring), T8 (Mortality Management), T9 (Pond
Management)
Input : Feeding data, water quality records, mortality data, pond management data
Output : Analytical reports, performance dashboards, trend analysis charts
Responsible Role : System Developer / Data Analyst
Priority : Medium (Supports monitoring, evaluation, and decision-making)

Use Case of Reporting & Analytics

Use Case Name : Generate Performance Reports and Analysis

Actor(s) :
• Farm Manager / End User
• Administrator
Description : The system collects and analyzes data from the Auto Feeding System, Water Quality Monitoring,
Mortality Management, and Pond Management modules. It generates detailed reports, summaries, and visual
dashboards to help users evaluate farm performance, identify trends, and make informed decisions. Users can filter
reports by date range, pond, or specific parameters for deeper analysis.
Precondition : T4, T5, T8, and T9 modules are implemented and storing accurate data.
Postcondition : Requested reports and analytical summaries are generated and made available for viewing or
download.
Attribute List of Integration & Deployment

Task ID : T13
Task Name : Integration & Deployment
Duration : 3 Weeks
Type : Implementation / Final Phase Task
Dependency : T1 (Requirements Analysis), T2 (System Architecture Design), T3 (UI/UX Design), T4 (Auto
Feeding System), T5 (Water Quality Monitoring), T6 (Fish Health Tracking), T7 (Camera
Monitoring System), T8 (Mortality Management), T9 (Pond Management), T10 (Alert &
Notification System), T11 (Automation & Control), T12 (Reporting & Analytics)
Input : Completed system modules, tested components, deployment plan, system configuration files
Output : Fully integrated and deployed system in production environment
Responsible Role : System Integrator / DevOps Engineer / Project Manager
Priority : High (Final delivery of the complete system)

Use Case of Integration & Deployment

Use Case Name : Integrate Modules and Deploy System

Actor(s) :
• System Integrator
• DevOps Engineer
• Administrator
Description : The system integrator combines all developed modules into a single unified system according to the
defined architecture. Integration testing is performed to ensure compatibility and proper data flow between modules.
After successful testing and validation, the system is deployed to the production environment. Final configuration,
user setup, and system verification are completed before handing over to stakeholders.
Precondition : All modules (T1–T12) are completed, tested individually, and approved. Deployment environment is
prepared and configured.
Postcondition : The fully integrated system is successfully deployed, operational in the production environment, and
ready for end-user access.