NAME: SENUGA OLUWAKAYODE SAMUEL

MATRIC NUMBER: COS/7580/2020

TOPIC: DESIGN AND IMPLEMENTATION OF A POULTRY FARM
INFORMATION MANAGEMENT SYSTEM (A CASE STUDY OF
INDOMINIO FARMS LTD)

CHAPTER THREE

SYSTEM ANALYSIS AND DESIGN

3.1 Analysis of the Existing System

Indominio Farms Ltd currently relies on a largely manual and paper-based

system for its daily operations. Activities such as stock tracking, sales

recording, feeding schedules, vaccination logs, and mortality tracking are

documented using physical notebooks and logbooks. This approach depends

heavily on human effort and faces several limitations, including inconsistencies,

data loss, and challenges in data retrieval. A comprehensive analysis of the

existing system is necessary to identify its strengths and weaknesses and to

provide a solid justification for the development of the proposed Poultry Farm

Information Management System (PFIMS).

3.1.1 Architecture of the Existing System

The architecture of the existing poultry management system at Indominio Farms

Ltd is characterized by a fragmented, hybrid approach combining manual,

paper-based record-keeping with rudimentary digital tools.

 Manual Record-Keeping: Core operational data, including daily feed

consumption, water intake, mortality rates, egg production, and vaccination

schedules, are primarily recorded manually in physical ledgers, notebooks, or

on chalkboards within the farm sheds. This constitutes the primary data capture

mechanism for day-to-day activities.

 Spreadsheet-Based Management: For aggregation and basic analysis, some

data, particularly financial transactions (e.g., sales, expenses) and summarized

production figures, are periodically transferred to digital spreadsheets, such as

Microsoft Excel. These processes are supplemented by semi-digital components

that include Microsoft Excel spreadsheets for monthly summaries, basic

calculator applications for simple computations, mobile phone contacts for

customer information, and simple SMS notifications for basic communication .

These spreadsheets typically operate on standalone desktop computers, limiting

real-time access and multi-user collaboration.

 Rudimentary Automation: Certain physical processes within the farm may

incorporate basic automation. This includes automated feed and water

dispensers often controlled by simple timers or mechanical float valves, and

basic ventilation systems that might operate on preset schedules or manual

activation rather than dynamic environmental feedback.

 Limited Communication Channels: Communication among farm staff,

management, suppliers, and veterinary professionals primarily relies on verbal

exchanges, phone calls, or informal notes, lacking a centralized digital

communication platform.

Fig. 1: Architecture of the existing system

3.1.2 Advantages of the Existing System

 Low Initial Cost: The primary advantage is the minimal upfront financial

investment required. The manual system requires virtually no upfront capital

expenditure for technology. Instead of spending thousands of naira on

computers, servers, or software licenses, the farm can operate with basic

stationery supplies. This makes the manual system particularly attractive for

small to medium farms with limited start-up.

 Ease of Initial Setup: Setting up manual record-keeping requires no

specialized technical expertise or complex software installations. Farm staff can

immediately begin recording data with minimal training. Most farm workers in

Nigeria have grown up using pen and paper for record-keeping, whether in

school or previous jobs. This familiarity means there's no psychological barrier

or resistance to adopting the manual system. Workers can start contributing

immediately without feeling intimidated by unfamiliar technology capital or

those operating on tight budgets.

 Flexibility in Informal Adaptation: Manual systems can be informally

adapted quickly to unforeseen circumstances or unique farm-specific practices

without requiring software modifications or system reconfigurations. There are

no complex workflows, system requirements, or technical procedures to learn.

A new employee can understand the system within hours rather than weeks. The
recording process is straightforward: see something happen, write it down in the

designated book, and file the record appropriately.

 No Reliance on Connectivity: Manual records are not dependent on internet

connectivity or electricity, making them resilient in areas with unreliable

infrastructure, a common challenge in rural agricultural settings. Workers can

continue recording data during power cuts, and managers can review records

even when the electricity is off. There's no waiting for systems to boot up, no

network connectivity issues to resolve, and no dependency on

telecommunications infrastructure that might fail during critical periods.

 Complete ownership of data and processes: The farm owns all its records

outright - there's no dependency on cloud service providers, software

companies, or external data storage services. Management has complete control

over how data is organized, who can access it, and how long records are

retained. There's no risk of losing access to historical data if a software

company goes out of business or changes its terms of service.

3.1.3 Limitations of the Existing System

Despite some merits, the existing manual and semi-digital system at Indominio

Farms Ltd presents several significant limitations that hinder operational

efficiency, data integrity, and strategic decision-making:

 Data Inconsistency and Inaccuracy: Manual data entry is prone to

human error, omission, and duplication. Inconsistent recording standards

can result in conflicting records, making reliable analysis difficult.

 Loss and Damage of Records: Paper-based records are highly

vulnerable to physical deterioration, accidental loss, fire, water damage,

and pest attacks. There is no reliable backup or recovery mechanism in

place.

 Lack of Real-Time Data Access: Data collected is not readily available

for real-time decision-making. Staff must search through physical ledgers

or wait for manual compilation of reports, which can delay responses to

urgent situations like disease outbreaks or feed shortages.

 Fragmentation of Information: Different operational aspects such as

sales, stock, health records, and finances are managed separately and

often manually. This fragmentation prevents holistic analysis, limits

traceability, and impairs coordination between units.

 No Trend Analysis or Predictive Tools: The current system does not

support data analytics or historical trend analysis. As a result, decisions

are often reactive rather than proactive, increasing risk and reducing

operational foresight.

 Limited Security and Access Control: Paper records can be accessed or

altered by unauthorized personnel, and there is no audit trail to track

changes or hold individuals accountable for errors or fraud.

  Low Scalability: As the farm grows in size or complexity, the manual

system becomes increasingly cumbersome to manage. It lacks the

scalability to handle large datasets or support multiple simultaneous users

efficiently.

 Dependency on Memory and Informal Communication: Key

operational knowledge often resides with specific staff members, making

the farm vulnerable to information loss when employees leave or are

unavailable.

 Cumbersome Reporting: Generating summary reports or retrieving

specific records requires time-consuming manual compilation. This

delays insight generation and burdens administrative staff.

3.2 Analysis of the Proposed System

The proposed Poultry Farm Information Management System (PFIMS) is

envisioned as a comprehensive, web-based solution to address the operational

challenges identified in the current manual setup. It will streamline data

collection, automate reporting, ensure data integrity, and support informed

decision-making through centralized and real-time access to records. The

system is designed with user-friendly interfaces, offline capabilities, and

modular architecture to suit the practical realities of small to medium-sized

poultry operations like Indominio Farms Ltd.

3.2.1 Architecture of the Proposed System

The architecture of the proposed Poultry Farm Information Management

System (PFIMS) is designed to address the shortcomings of the existing system

while leveraging modern technologies to ensure scalability, reliability, and ease

of use. The architecture adopts a three-tier, web-based model consisting of:

1. Presentation Layer (Client Interface)

2. Application Layer (Business Logic)

3. Data Layer (Database Management)

This layered approach enables separation of concerns, streamlined maintenance,

and enhanced scalability.

1. Presentation Layer (front-End Interface)

This is the user-facing component of the system and is responsible for

interacting with end-users (farm staff, managers, and administrators). It is

designed with a focus on usability, responsiveness, and accessibility.

 Technologies Used:

o HTML5: For semantic page structure

o CSS3 and Bootstrap: For responsive and adaptive styling

o JavaScript: For interactivity and real-time feedback

o AJAX: For asynchronous data operations

 Devices Supported:

o Desktop browsers

o Tablets

o Mobile devices (via responsive web view or Android app)

 Features:

o Login page with role-based access

o Dashboards with visual summaries

o Forms for entering stock, sales, vaccination, and health data

o Dynamic reporting tools

2. Application Layer (Business Logic)

 This layer processes all user inputs and business rules before interacting

with the database. It handles authentication, validation, transaction

management, and reporting.

 Technologies Used:

o PHP (v8+): Server-side scripting language for backend logic

o RESTful API: Enables modular communication between front-end

and back-end

o JSON: For structured data exchange

 Functional Modules Include:

o Stock Management Module

o Sales and Expenses Module

o Health and Vaccination Tracker

o User Management and Role Control

o Report Generation and Analysis

3. Data Layer (Database Tier)

This is the backend storage system that maintains all farm records in a

structured, secure, and retrievable format.

 Technology Used:
 o MySQL (v8+): A relational database known for stability and

robustness

 Data Stored Includes:

o Poultry batches and production logs

o Feed and medication schedules

o Sales records and financial logs

o User activity logs

 Security Features:

o SQL injection prevention

o Encrypted sensitive fields (e.g., passwords)

o Regular backup and disaster recovery mechanisms

Fig 2.1 Architecture of the proposed system
Fig. 2.2 Architecture of the proposed system
 Fig 2.3: Architecture of the proposed system

3.2.2 Advantages of the Proposed System

The proposed Poultry Farm Information Management System (PFIMS) offers

several advantages over the existing manual system, including:

 Low Initial Cost: The primary advantage is the minimal upfront

financial investment required. The manual system requires virtually no

upfront capital expenditure for technology. Instead of spending thousands

of naira on computers, servers, or software licenses, the farm can operate

 with basic stationery supplies. This makes the manual system particularly

attractive for small to medium farms with limited start-up.

 Ease of Initial Setup: Setting up manual record-keeping requires no

specialized technical expertise or complex software installations. Farm

staff can immediately begin recording data with minimal training. Most

farm workers in Nigeria have grown up using pen and paper for record-

keeping, whether in school or previous jobs. This familiarity means

there's no psychological barrier or resistance to adopting the manual

system. Workers can start contributing immediately without feeling

intimidated by unfamiliar technology capital or those operating on tight

budgets.

 Flexibility in Informal Adaptation: Manual systems can be informally

adapted quickly to unforeseen circumstances or unique farm-specific

practices without requiring software modifications or system

reconfigurations. There are no complex workflows, system requirements,

or technical procedures to learn. A new employee can understand the

system within hours rather than weeks. The recording process is

straightforward: see something happen, write it down in the designated

book, and file the record appropriately.

 No Reliance on Connectivity: Manual records are not dependent on

internet connectivity or electricity, making them resilient in areas with

unreliable infrastructure, a common challenge in rural agricultural

 settings. Workers can continue recording data during power cuts, and

managers can review records even when the electricity is off. There's no

waiting for systems to boot up, no network connectivity issues to resolve,

and no dependency on telecommunications infrastructure that might fail

during critical periods.

 Complete ownership of data and processes: The farm owns all its

records outright - there's no dependency on cloud service providers,

software companies, or external data storage services. Management has

complete control over how data is organized, who can access it, and how

long records are retained. There's no risk of losing access to historical

data if a software company goes out of business or changes its terms of

service.

3.3 Methodology

This project adopts the Waterfall Software Development Model, which

involves the following stages:

1. Requirements Analysis

– Gathering functional and non-functional requirements through

interviews, observations, and document reviews.

 2. System Design

– Development of interface sketches, flowcharts, and ER diagrams.

3. Implementation

– Coding of the system using PHP, HTML, CSS, JavaScript, and

MySQL.

4. Testing

– Functional and integration testing conducted with simulated and real

farm data.

5. Deployment

– System installed on a local server or cloud platform.

6. Maintenance

– Future updates, feedback-driven refinements, and bug fixes.

3.4 Methods of Data Collection

To understand the requirements of the system, the following methods were

used:

 Interviews: Conducted with farm managers and staff to gather

information about current workflows and challenges.

 Observation: On-site observation of farm activities to assess how records

are managed.
  Document Review: Analysis of existing logbooks and spreadsheets used

for stock, health, and sales tracking.

 Questionnaires (optional): Simple surveys distributed to farm workers

regarding digital familiarity.

3.4.1 Dataset

Although the system does not rely on third-party datasets, simulated data was

generated using real examples from Indominio Farms’ logs, such as:

 Poultry batch records

 Vaccination dates

 Mortality logs

 Feed inventory

3.4.2 Data Preprocessing

Before testing, the data was cleaned and normalized:

 Standardization: Dates formatted consistently; numerical values

rounded.
  De-duplication: Redundant entries were removed.

 Validation: Entries checked for accuracy and completeness.

This ensures the system can handle real-world data effectively.

3.5 Design Specification

The design of PFIMS is guided by usability, efficiency, and scalability

principles.

3.5.1 Input / Output Specification

Input Source Format

User login credentials Staff/Admin Username, Password

Poultry batch information Farm supervisor Text/Dropdown

fields

Mortality and health updates Farmhand Numeric, Date

Feed usage logs Manager/Farmhand Numeric

 Sales records Sales officer Text/Numbers

Output Format Recipient

Dashboard summaries Visual/Graphical All users (filtered)

Mortality and feed usage Table and PDF export Manager/Admin

reports

Inventory alerts Text/Popup Manager

notifications

Vaccination reminders Email/SMS Farm staff

3.5.2 Process Design

A simplified process design is as follows:

1. User Login Process

 o Input: Username and password

o Validation: Check credentials

o Output: Redirect to role-based dashboard

2. Record Entry Process

o Input: Batch info, feed logs, sales

o Processing: Save to database

o Output: Confirmation message

3. Report Generation Process

o Input: Date range or batch ID

o Processing: Query database

o Output: Tabular/graphical report (view or download)

4. Reminder/Notification Process

o Trigger: Time-based or threshold-based

o Output: In-app message, email, or SMS

Fig 3.0System Flowchart of PFIMS
 fig 3.1: Use Case Diagram of Poultry Management System

fig 3.1.2: Administrator Use Case Diagram of Poultry Management System

fig 3.1.3: Farm Manager Use Case Diagram of Poultry Management System
fig 3.1.4: Farm Supervisor Use Case Diagram of Poultry Management System
fig 3.1.5: Farm Staff Use Case Diagram of Poultry Management System
fig 3.1.6: Farm Supervisor Use Case Diagram of Poultry Management System
fig 3.1.7: Sales Officer Use Case Diagram of Poultry Management System
fig 3.1.8: Veterinary Use Case Diagram of Poultry Management System
fig 3.9: Notification System Use Case Diagram of Poultry Management

System
Fig 4: Data Flow Diagram of Poultry Management System
Fig 5 - Sequence diagram for each of the use cases.
Fig 5.1- Sequence diagram for each of the use cases.
Fig 5.2 Sequence Diagram for Record Entry Process

Fig 5.3 Sequence Diagram for Report Generation Process

Fig 5.4 Sequence Diagram for Reminder/Notification Process