Project Report

Poultry Farm Management System

A REPORT
SUBMITTED TO THE DEPARTMENT OF COMPUTER SCIENCE & IT
GHAZI UNIVERSITY DERA GHAZI KHAN
IN PARTIAL FULFILLMENT OF REQUIREMENTS FOR
THE DEGREE OF BS (INFORMATION TECHNOLOGY)

Submitted by

Muhammad Naveed Azeem

2018GU1915
Session 2018-2022

DEPARTMENT OF COMPUTER SCIENCE & IT

GHAZI UNIVERSITY DERA GHAZI KHAN
PAKISTAN
 FINAL APPROVAL

This is to certify that we have read this report submitted by Muhammad Naveed Azeem and it is my
judgment that this report is of sufficient standard to warrant its acceptance by Ghazi University, Dera
Ghazi Khan for the degree of BS (Information Technology)

Committee:

1. External Examiner
Dr Israr Hanif
Assistant Professor
Department of Computer Science
Bahaudin Zakariya University Multan

2. Supervisor
Dr. Muhammad Abubakar Siddique
Associate professor

Department of CS & IT
Ghazi University D G Khan

3. Head of Department
Dr. Hafiz Gulfam Ahmad Umar
Associate professor

Department of CS & IT

Ghazi University D G Khan

i
 DEDICATION

All my words dedicated with respect to

MY LOVING PARENTS & FRIENDS

Whose love and prays always accompanies me like a shining star
whenever I was in darkness and enable me to reach this stage.

MY PROJECT SUPERVISOR & MY TEACHERS

ii
 ACKNOWLEDGMENT

In the name of Allah, the Most Beneficent and the Most Merciful Alhamdulillah, all praises to Allah
for the strengths and His blessing in completing this project. Special appreciation goes to my
supervisor, Dr. Muhammad Abubakar Siddique , for his supervision and constant support. His vital
help of useful comments and suggestions during the tentative and project works have contributed to
the success of this project. My acknowledgement also goes to all the technicians and office staffs for
their co-operations. Heartfelt thanks to all my friends and to those who indirectly contributed in this
project report, your kindness means a lot.

Muhammad Naveed Azeem

iii
 PROJECT BRIEF

PROJECT NAME Poultry Farm Management System

UNDERTAKEN BY Muhammad Naveed Azeem

SUPERVISED BY Dr. Muhammad Abubakar Siddique

STARTING DATE 1 October 2021

COMPLETION DATE 25 August 2022

COMPUTER USED Intel(R) Core(TM) i3 CPU 3110M CPU @ 2.40GHz,

4GB RAM

OPERATING SYSTEM MS Widow 10 pro

SOURCE LANGUAGE(S) Web Technologies(HTML,CSS,PHP,MYSQL

JAVASCRIPT)

TOOLS/PACKAGES Xampp Server, Visual Studio

iv
 ABSTRACT

Present system is ledgers based and manual entry for each transaction is required, record of
eggs, quantity of birds as well as sales and expense record is calculated on separate ledgers.
Production percentage is calculated manually for everyday production. Feed consumption
per day, month is first written and them total is calculated. Sales and expense record as well
as profit and loss calculations require a lot of time to go through all transactions. Poultry Rec
is Poultry management software which will overcome all these problems and provide
additional functionalities we have measured the needs of poultry farmers through survey and
our software will fulfill all their needs. This project is designed to record all the transactions
and activities involved in a poultry farm specifically for layers, these solutions integrate
Flock Production, Egg Sales, Feed Consumption, Medicine Record, Employee Pay Record,
Eggs in Stock, Birds in Farms and Mortality. PFMS will cover almost all aspects of poultry
(layer needs).
Keywords:
Poultry Farm management system, poultry farm software, poultry software,
management system for poultry farm.

v
 Table of Contents

Chapter 1
Introduction

1 INTRODUCTION.........................................................................................................................1
1.1 Introduction...........................................................................................................................2
1.2 Statement of Problem.............................................................................................................3
1.1 Solution of proposed system..................................................................................................3

Chapter 2
Existing System

2.1 Related Technologies.....................................................................................................................5

Chapter 3
Tools and Techniques

3.1 Hardware used with technical specifications...............................................................................7

3.2 Software(s) used..........................................................................................................................7
3.2.1 Operating System Windows 10.............................................................................................7
3.2.2 Visual Studio Code...............................................................................................................7
3.2.3 XAMPP................................................................................................................................7
3.2.4 Browser.................................................................................................................................8
3.3 Technique....................................................................................................................................8
3.3.1 HTML...................................................................................................................................8
3.3.2 CSS.......................................................................................................................................8
3.3.3 PHP.......................................................................................................................................9
3.3.4 Bootstrap...............................................................................................................................9
3.4 Summary.....................................................................................................................................9

Chapter 4
Methodology

4.1 Design of Investigation........................................................................................................11

4.1.1 Use Case Diagram........................................................................................................12
4.1.2 Flowchart.....................................................................................................................20
4.1.3 Sequence Diagram.......................................................................................................21
4.1.4 Class Diagram..............................................................................................................22
4.1.5 Requirement Gathering Techniques.............................................................................25
4.1.6 Incremental Model.......................................................................................................25
1.1.6 Implementation Procedure...........................................................................................28
4.1.7 Details about Hardware................................................................................................28
4.1.8 Detail about System.....................................................................................................29
4.2 Verification of Functionality................................................................................................29
4.2.1 User Functionalities.....................................................................................................29
4.2.2 Nonfunctional Requirement.........................................................................................29

vi
 Chapter 5
System Testing

5.1 Objective Testing.................................................................................................................33

5.2 Usability Testing..................................................................................................................34
5.2.1 Content.........................................................................................................................34
5.3 Software Performance Testing.............................................................................................34
5.3.1 Testing performance types...........................................................................................34
5.4 Compatibility Testing..........................................................................................................35
5.4.1 Types of Compatibility Tests.......................................................................................35
5.4.2 How to do Compatibility Testing.................................................................................36
5.5 Load Testing........................................................................................................................36
5.6 Security Testing...................................................................................................................37
5.7 Installation Testing..............................................................................................................38
5.8 Test Cases............................................................................................................................38
5.9 Test Case of User.................................................................................................................39
5.10 Testing Results.....................................................................................................................40
5.11 Summary..............................................................................................................................41

Chapter 6
Conclusion

6.1 Conclusion...........................................................................................................................43

vii
 CHAPTER 1
4 INTRODUCTION
Chapter 1 Introduction

1.1Introduction
The system is needed because of the importance associated with adequately monitoring
the activities on a poultry farm. Poultry production provides cash in emergencies,
provides high-quality protein to a rapidly growing population, and contributes
significantly to food security, poverty reduction, and ecologically sound management of
natural resources—an essential livelihood for most rural communities.

Since there is a continuing rise in the cost of cattle, sheep, and goat meat production,
consumer preferences have shifted now for poultry meat (white meat) given the
ecological, economic, social, and health advantages over the other types of meat (red
meat). Poultry is the most capitalized of all the livestock agriculture practices. The types
of poultry commonly reared in India are chickens, ducks, guinea fowls, turkeys, pigeons,
and more. Those of commercial or economic importance are chicken, guinea fowls, and
turkeys, among which the chickens predominate.

For an astonishing number of years, information technology has been evolving. It has
become part of the world’s daily routine to involve information technology in
organization and operations. Due to information technology, the world has moved; digital
telecommunication networks have been constructed worldwide, and that is how far the
technology has gone. Electronic commerce is part of information technology, and it has
been around for over a decade, closing the gap between chicks and the internet. In the
current system work, transactions and payments are made manually. Still, in the new
system, all the poultry transactions are computerized using the software of the poultry
management information system. The major operation in the system includes registration
of customers, advertising the company products, storing the quality of the products sold,
and displaying the report of the ordered products.

Poultry Farm Management System 2

Chapter 1 Introduction

1.2 Statement of Problem

The current poultry management information system is paper-based, inefficient, tiresome,

hard to update, susceptible to errors, and time-wasting their transport to go and book at
the receptionist. Physically which is sometimes expensive, the online poultry
management information system will try to solve the query of manual registration,
making payments, advertisement of new company products, and booking chicks for
customers interested. Automation of the booking process whereby information moves
from various stakeholders in an orderly manner enables people to get products and
services fast. It is cheap and even puts less stress on the poultry.

1.3 Solution of proposed system

Poultry Farm management system is an Online system provides a solution to
reduce and optimize these expenses. This project will help in collecting the perfect
farming data in detail. The collection will be apparent, straightforward, and sensible in a
short time. So we are going to done all the work online that we can access anywhere at
any time using our mobile phone with high rate of accuracy.

Poultry Farm Management System 3

 CHAPTER 2
4 EXISTING SYSTEM
Chapter 2 Existing System

2.1 Related Technologies

In the system, everything is managed manually even if they try at the max level to save all
user very sincerely. The error in one or another way has the nearest possibility to face any
problem. Several activities are done in an unordered manner. The different type of record
such as feed detail, bird files, medicine details, expenditure detail, labor detail etc are all
related to each other. So it is therefore many problem wise during the manipulation of
such record in the existing system.
DIFFICULT IN REPORT GENERATING :
We require more calculation to generate the report .
MANUAL CONTROL : All the calculation to generate the report is done manually
so there is greater chance to get error.
TIME CONSUMING: Every work is done manually so we cannot generate report in
the of the session or as per requirement and its is very time consuming.
LOT OF PAPER WORK : Existing system required lot of Paper work. Loss of
even single register or record led to difficult situation because all the paper are needed to
generate the report.

Poultry Farm Management System 5

 CHAPTER 3
5 TOOLS AND TECHNIQUES
Chapter 3 Tools & Techniques

In this chapter we will discuss Tools and Technologies that we used. “Poultry Farm
Management System” is Web Application. There are a variety of tools and techniques to
build this type of application, but we have used techniques HTML, CSS, Bootstrap, JS,
PHP, and Jquery with visual studio code. Visual Studio Code is a free source code editor
developed by Microsoft for Windows, Linux and Mac OS.

3.1 Hardware used with technical specifications

 Processor: AMD A6-4400M
 Processor Speed: 2.7GHZ
 RAM: 8 GB RAM
 Hard Disk: 320 GB Storage

3.2 Software(s) used

The following software and tools are used to develop this application.
 Operating System Windows 10
 Visual Studio Code
 XAMPP
 Browser
3.2.1 Operating System Windows 10
An operating system (OS) is the program that, after being initially loaded into the
computer by a boot program, manages all of the other application programs in a
computer. The application programs make use of the operating system by making
requests for services through a defined application program interface. In addition, users
can interact directly with the operating system through a user interface such as a
command line or a graphical user interface.
3.2.2 Visual Studio Code
Visual Studio Code is a free source code editor developed by Microsoft for Windows,
Linux and Mac OS. Features include debugging, syntax highlighting, intelligent code
completion, fragmentation, code refactoring and support for embedded git.
3.2.3 XAMPP
XAMP stands for "Windows, Apache, MySQL, and PHP." XAMPP is a variation of
LAMP for Windows systems and is often installed as a software bundle (Apache,

Poultry Farm Management System 7

Chapter 3 Tools & Techniques

3.2.4 Browser
A web browser is a software application for accessing information on the World Wide
Web. When a user requests a web page from a particular website, the web browser
retrieves the necessary content from a web server and then displays the page on the user's
device.
3.3 Technique
 HTML.
 CSS.
 PHP.
 Bootstrap
3.3.1 HTML
Hypertext Markup Language (HTML) is the standard markup language for documents
designed to be displayed in a web browser. HTML describes the structure of a web page
semantically and originally included cues for the appearance of the document. HTML
elements are the building blocks of HTML pages. With HTML constructs, images and
other objects such as interactive forms may be embedded into the rendered page.
3.3.2 CSS
Cascading Style Sheets (CSS) is a style sheet language used for describing the
presentation of a document written in a markup language like HTML. CSS is a
cornerstone technology of the World Wide Web, alongside HTML and JavaScript. CSS is
designed to enable the separation of presentation and content, including layout, colors,
and fonts as shown in Figure 3.1

Poultry Farm Management System 8

Chapter 3 Tools & Techniques

Figure 3.1 CSS

3.3.3 PHP
PHP is a general-purpose scripting language that is especially suited to web development.
Danish-Canadian programmer Rasmus Lerdorf originally created it in 1994; The PHP
Group now produces the PHP reference implementation. PHP originally stood for
Personal Home Page, but it now stands for the recursive initialism PHP: Hypertext
Preprocessor. A PHP interpreter implemented as a module, a daemon or as a Common
Gateway Interface (CGI) executable usually processes PHP code on a web server.
3.3.4 Bootstrap
Bootstrap is a free and open-source CSS framework directed at responsive, mobile-
first front-end web development. It contains CSS- and (optionally) JavaScript-based
design templates
for typography, forms, buttons, navigation and other interface components. Simply put,
Bootstrap is a wide array of tools that rely on re-usable code so that you do not have to
develop the building blocks of a website from scratch.

3.4 Summary
In this chapter we discussed about the tools and the techniques we use to make the project
in the running form and which programing language is used for development of the
project and tools we use to run the project. Computer is the combination of two things
hardware and software so we use software to make the project as well as the hardware.

Poultry Farm Management System 9

 CHAPTER 4
METHODOLOGY
 Chapter 4 Methodology

Software development methodology is a process or series of processes used in software

development. The design of software is essentially a skill, but it usually requires a structure
which will provide a guide or a methodology for this task. A methodology can be defined as
the underlying principles and rules that govern a system. A method can be defined as a
systematic procedure for a set of activities. Thus, from these definitions, a methodology will
encompass the methods used within the methodology. Different methodologies can support
work in different phases of the system life cycle, for example, planning, analysis, design and
programming, testing and implementation. Svoboda (1990) developed the idea of a
methodology further by proposing that there should be at least four components:
 A conceptual model of constructs essential to the problem
 A set of procedure suggesting the direction and order to proceed
 A series of guidelines identifying things to be avoided
 Collection of evaluation criteria for assessing the quality of the product.
The conceptual model is needed to direct or guide the designers to the relevant aspects of the
system. The set of procedure provides the designer a systematic and logical set of activities to
begin the design task. The evaluation criteria provide an objective measurement of the work
done against some established standard or specifications. Methodologies are an integrated set
of the above tools and techniques. The methodologies should be well documented for
accomplishing the task or activity and provide a description of the process to be used.
A software design methodology can be structured as comprising of the software design
process component and the software design representation or diagrammatic component.
1 4.1 Design of Investigation

UI design review the site analysis document and create different pages for the complete
system starting from the home page. It pays special attention to checkout process and access
to support. At this stage you begin to see what your website will look like. This is the best
time to suggest changes to the system as this stage can accommodate any and every change
needed. The final is now converted to responsive cross device and platform compliant HTML
skin depending on the ecommerce platform suggested. This phase is very important as the

Poultry Farm Management System 11

Chapter 4 Methodology

HTML delivered will dictate how the site works, by ensuring the HTML is fully compliant
with web standards we speed up the process and avoid expensive mistake.
Project design is an early phase of the project where a project's key features, structure,
criteria for success, and major deliverables are all planned out. The point is to develop one or
more designs which can be used to achieve the desired project goals. Stakeholders can then
choose the best design to use for the actual execution of the project. The project design phase
might generate a variety of different outputs, including sketches, flowcharts, site trees,
HTML screen designs, prototypes, photo impressions. Following are some designs which
describe our system work flow and activity. By adding this design, it’s now easy to
understand the system and its working. In these designs, we have explained the system more
simply. In these designs include activity diagram, use cases of system and class diagram.

6.11 Use Case Diagram

Use case diagrams are considered for high level requirement analysis of a system. When the
requirements of a system are analyzed, the functionalities are captured in use cases. Use case
diagrams specify the events of a system and their flows. But use case diagram never
describes how they are implemented. Use case diagram can be imagined as a black box
where only the input, output and the function of the black box is known. These diagrams are
used at a very high level of design. Then this high-level design is refined again and again to
get a complete and practical picture of the system. So, we can say that use cases are nothing
but the system functionalities written in an organized manner. Now the second things which
are relevant to the use cases are the actors. Actors can be defined as something that interacts
with the system. The actors can be human user, some internal applications or may be some
external applications. So, in a brief when we are planning to draw a use case diagram, we
should have the following items identified in use case diagram:
 Functionalities to be represented as a use case
 Actors
 Relationships among the use cases and actors
1.1 Use Case Terminology

A use case describes a sequence of actions that provide something of measurable value to an
actor.

Poultry Farm Management System 12

Chapter 4 Methodology

 Actors
An actor is a person, organization, or external system that plays a role in one or more
interactions with your system.
 Associations
An association exists whenever an actor is involved with an interaction described by a
use case. Associations are modeled as lines connecting use cases and actors to one
another.
 System boundary
A rectangle around the use cases, called the system boundary, to indicate the scope of the
system.

Figure: 4.1 Use Case Diagram

Poultry Farm Management System 13

Chapter 4 Methodology

Use case Scenario’s

Usage Scenario 1:
Table 4.1 Login usecase scenario

Use case Scenario

Use Case Title Login
Use Case ID Uc-1
Actor User
Actions  The user will click on the
login button mention on the
home page.
 The user will go to the login
page.
 The user will provide an email
ID and password.
 Click on the login button.
 The user account page will be
open.
Description Users will provide the necessary
information (Email and Password)
to login into their exact accounts
Alternative path User can direct the login button for
registration.
Pre-condition The system should be connected to an internet then
user should be registered.
Post condition User will login successfully.

Poultry Farm Management System 14

Chapter 4 Methodology

Exception  The provided password is wrong.

 Allow the user to re-enter the password.

Author PFMS development members

Usage Scenario 2:
Table 4.2 Logout usecase scenario

Use case Scenario

Use Case Title Logout
Use Case ID Uc-2
Actor User
Actions  click the logout button then
logout
Description Admin, user can logout to this
web-application
Alternative path None
Pre-condition System and database connect to internet and web-
application should in running condition.
Post condition Action performed successfully.
Exception None
Author Agri Store development members

Usage Scenario 3:
Table 4.3 Registration usecase scenario

Use case Scenario

Use Case Title Registration

Poultry Farm Management System 15

Chapter 4 Methodology

Use Case ID Uc-3

Actor User
Actions  Click on the registration button.
 User fill complete form about require data for
registration (company name, Email, Password,
Address, City etc.)
 Click the submit button.
 Show message user register successfully.
Description This use case enable user to
register for manage safely.
Alternative path None
Pre-condition Internet connection should be available.
Post condition User has registered successfully.
Exception User has entered the invalid data.
Author PFMS development members

Usage Scenario 4:
Table 4.4 Add sales usecase scenario

Use case Scenario

Use Case Title Add sales
Use Case ID Uc-4
Actor User
Actions  Click the add sale tab.
 Fill the sales category
detail(Name, lorry number

Poultry Farm Management System 16

Chapter 4 Methodology

etc.).
 Save the category.
Description User will add the sales to manage the chicken/eggs
related to the specific category
Alternative path None.
Pre-condition User Should login.
Post condition Action Performed successfully.
Exception None
Author PFMS development members

Usage Scenario 5:
Table 4.5 Manage expenses usecase scenario

Use case Scenario

Use Case Title Manage expenses
Use Case ID Uc-5
Actor User
Actions  User will add his expenses detail to maintain the
record.
Description User will manage the expenses to add by providing
the expense type, amount and date.
Alternative path None
Pre-condition User Should first expense ledger and then will be
able to add this one.
Post condition Action Performed successfully.
Exception None

Poultry Farm Management System 17

Chapter 4 Methodology

Author PFMS development members

Usage Scenario 6:
Table 4.6 clients usecase scenario

Use case Scenario

Use Case Title Add Clients
Use Case ID Uc-6
Actor User
Actions  User will Add the clients and
manage them on further
require changes or delete the
clients.
Description Admin will add the client detail with proper name,
address, telephone and date paid.
Alternative path No
Pre-condition User will have to login for add client.
Post condition Action Performed successfully.
Exception If user can’t login not add clients properly.
.
Author PFMS development members

Poultry Farm Management System 18

Chapter 4 Methodology

6.12Flowchart

Figure 4.2 Activity diagram of User

Poultry Farm Management System 19

Chapter 4 Methodology

6.13Sequence Diagram
A sequence diagram simply depicts interaction between objects in a sequential order such as
the order in which these interactions take place. We can also use the terms event diagrams or
event scenarios to refer to a sequence diagram. Sequence diagrams describe how and in what
order the objects in a system function. UML has introduced significant improvements to the
capabilities of sequence diagrams. Most of these improvements are based on the idea of
interaction fragments. Objects calling methods on themselves use messages and add new
activation boxes on top of any others to indicate a further level of processing. If an object is
destroyed, an X is drawn on bottom of the lifeline, and the dashed line ceases to be drawn
below it. It should be the result of a message, either from the object itself or another.
A message sent from outside the diagram can be represented by a message originating from a
filled-in circle or from a border of the sequence diagram. Sequence diagram of admin and
user will be as shown in figure 4.3

Figure 4.3 Sequence Diagram

Poultry Farm Management System 20

Chapter 4 Methodology

6.14Entity Relationship Diagram

An Entity Relationship Diagram shows how entities such as people, objects or concepts etc.
relate to each other in a particular system. ERD can help users conceptualize abstract
elements in order to discuss and understand the relationship between different concepts. ER
(crowfoot) diagram as shown Figure

Figure 4.4 ERD (Crowfoot Diagram)

6.15Class Diagram

In software engineering, a class diagram in the Unified Modeling Language (UML) is a type
of static structure diagram that describes the structure of a system by showing the system’s
classes, their attributes, operations (or methods), and the relationships among objects.
A UML class diagram is made up of:
A set of classes
A set of relationships between classes

Poultry Farm Management System 21

Chapter 4 Methodology

1.13Class

A description of a group of objects all with similar roles in the system which
consists of Structural features (attributes) define what objects of the class
know.

 Represent the state of an object of the class

 Are descriptions of the structural or static features of a class Behavioral features define
what objects of the class can do
 Define the way in which objects may interact
 Operations are descriptions of behavioral or dynamic features of a class

1.2 Class Notation

A class notation consists of following parts.

 The name of the class appears in the first partition.

 Attributes are shown in the second partition. Class attributes contains
following parts
 The attribute type is shown after the colon.
 Attributes map onto member variables (data members) in code.
 Operations are shown in the third partition. They are servicing the class
provides.
 The return type of a method is shown after the colon at the end of the method
signature
 The return type of method parameters are shown after the colon following the
parameter name.
 Operations map onto class methods in code as shown in figure 4.5

Poultry Farm Management System 22

Chapter 4 Methodology

Figure 4.5 Class Diagram

The purpose of procedure analysis technique is to prepare for the implementation of selected
solution concepts, as a result of value stream reinvention, reengineering or redesign. Changes
in activity work flows almost always affect the policies and procedures which govern the
current way the activity is performed. This phase presents findings that include
recommended features and guidance on overall site structure. Implementation is the process
of building the web according to its design. This discusses deeply the implementation of the
system, highlighting the testing and some of the main component of the system’s Graphical
User Interface (GUI). It will give an output from the programming language and other tool
used to develop the system. Documentation in the new system provides adequate information
and instructions that enable the user to use the system effectively by reviewing and updating
the new system while the implementation has to do with the testing of the new system for its
functionality.

Poultry Farm Management System 23

Chapter 4 Methodology

1.14Requirement Gathering Techniques

A requirement can be defined as a condition or capability that must be processed by a

product or an application. Techniques that can be used for collecting requirements are as
follows:

 By questionnaire and survey

 By interview and observations
 Use of prototype

Figure 4.6 Data Gathering

1.15Incremental Model

In incremental model the whole requirement is divided into various builds. Multiple
development cycles take place here, making the life cycle a multi waterfall cycle. Cycles are
divided up into smaller more easily managed in this model, each module passes through the
requirements, design, and implementation and testing phases. It combines elements of linear
and parallel process flow. Each linear sequence produces deliverable increments of the
software. The first increment is often a core product with many supplementary features.
Users use it and evaluate it with more modifications to better meet the needs.

Poultry Farm Management System 24

Chapter 4 Methodology

1.17 Principle of Incremental Model

These principles are described through the step of incremental method engineering, and the
mechanism applied in each step.
 These steps deal with collecting experience, and refining a method for a current situation.
 These steps are lacking for one method approaches and together with a priori method
them from an iterative loop of incremental method.
 Throughout these steps we apply three mechanisms that seek to improve methods. These
mechanisms are based on analyzing the differences between an intended and actual use of
modeling techniques, on studying the role techniques in modeling object system, and on
understanding how they support problem solving.
 Construct a partial implementation of a total system.
 Then slowly add increased functionality.
 The incremental model prioritizes requirements of the system and then implements them
in groups.
 Each subsequent release of the system adds function to the previous release, until all
designed functionality has been implemented.

Figure 4.7 Incremental Model

Poultry Farm Management System 25

Chapter 4 Methodology

4.10.1 Advantages

 Generates working software quickly and early during the software life cycle.
 This model is more flexible and less costly to change scope and requirements.
 It is easier to test and debug during a smaller iteration.
 In this model customer can respond to each built.
 Lowers initial delivery cost.
 Easier to manage risk because risky pieces are identified and handled during its iteration.
The incremental model prioritizes requirements of the system and then implements them
in groups.
 Each subsequent release of the system adds function to the previous release, until all
designed functionality has been implemented.
 Develop high-risk or major functions first.
 Each release delivers an operational product.
 Initial product delivery is faster.

Figure 4.8 Incremental Model iteration

This approach allows the customer to interact and work with functioning software. At the end
of each iteration and provide feedback on it. This model can be used when the requirements
of the complete system are clearly defined and understood. Major requirements must be
defined; however, some details can evolve with it. There are some high-risk features and
goals. Risk, funding, schedule, program complexity, or need for early realization of benefits.

Poultry Farm Management System 26

Chapter 4 Methodology

Most of the requirements are known up-front but are expected to evolve over time. A need to
get basic functionality to the market early.

Figure 4.9 Steps of Incremental Model

1.18 Implementation Procedure

System implementation is very important phase of any website. It is the process that actually
yields the lowest level system element in the system hierarchy. System implementation uses
the structure created during architectural design and the result of system analysis to construct
system element that meet the stake holder requirements developed in the early life cycle
phases.

1.19 Details about Hardware

There is no official minimum for the hardware requirements that are needed to host the
Scavengers.com Web and android app. The hardware specifications will change under the
influence of different factors that should be taken into account to make the best estimation of
the hardware specifications for the web and database server. Table 4 . shows the hardware
detail approximation to install the project.
Table 4.8S Hardware Detail

Item Web Server Minimum Web Server &Database Server

Processor 1.6 GHz CPU 2*1.6GHz CPU

RAM 1.75 GB RAM 3.5 GB RAM
HDD 1 GB Free Space 1 GB Free Space

Poultry Farm Management System 27

Chapter 4 Methodology

Above we discuss how estimation can go. Now following are the general requirement of
hardware being used by us to develop the software. For the execution and deployment of this
website we need following hardware and specifications.
 Intel core i3 CPU 1.90GHz
 Installed Ram: 4.00 GB
1.19.1Detail about System
In order to use it effectively and efficiently, every system software need certain hardware
component or the software requirement to be made available on the computer. To ensure
proper installation and usability of the new system, the following must be taken into
consideration.

1.20 Verification of Functionality

This is used to check if your product is as per the specifications you intended for it as well as
the functional requirements you charted out for it in your developmental documentation.
1.20.1 User Functionalities
 Birds (Quantity, Mortality)

 Eggs Stock (Total Eggs)

 Medicine (Price, Consumption)

 Feed (Price, Consumption/Day)

 Employees (Their salary record)

 Sales Record

1.20.2 Nonfunctional Requirement

Functional requirements define the needs in terms of performance, design constraints,
Standards compliance.

Poultry Farm Management System 28

Chapter 4 Methodology

1.3 Availability

Availability is the ratio of time a system or component is functional to the total time it is
required or expected to function.
 Application must be responsive and available at every time.
 Application must be work on time efficiently.
1.4 Reliability

 System should be reliable.

 System should not produce an incorrect output.
1.5 Maintainability

Making changes or upgradeability in the site will not be that much difficult. By having some
knowledge of programming, some features of the application might be converted to a new
version.
 System should perform a successful action within a given time.
1.6 Performance

The product shall be based on web and has to be run from a web server. The product shall
take initial load time depending on internet connection strength which also depends on the
media from which the product is run. The performance shall depend upon hardware
components of the admin/user.
The Performance of our system is in the sense that:
 System should be fast.
 System should support the capability to use multi user environment.
 System must perform well.
1.7 Portability

 Easy to access anywhere any time.

Poultry Farm Management System 29

Chapter 4 Methodology

1.8 Consistency

 When an administrator is updating information, consistency must hold there.

1.21 Database Requirement

In this section, the database requirements for this website are mentioned: We use php
MyAdmin for the Database Management system. In this stage of the project coding of all the
processes is done and the backend database management tools are created.

1.22 Database Tables

This is our database named as agri which has many tables as shown in
Figure .

Figure 4.10 Database Tables

Poultry Farm Management System 30

 CHAPTER 5
2 SYSTEM TESTING
Chapter 5 System Testing

In this chapter, we will discuss the testing phase of developed application in different manner
to know that how much efficient and effective Website is. A process of performing as
application or program with the intention of finding errors and whether the website is
fulfilling user needs. It can also be defined as the ability of a program in meeting the required
or desired results.
System testing is a level of testing that validates the complete and fully integrated software
product. The purpose of a system test is to evaluate the end-to-end system specifications.
Usually, the software is only one element of a larger computer-based system. Ultimately, the
software is interfaced with other software/hardware systems. System Testing is actually a
series of different tests whose sole purpose is to exercise the full computer-based system.
Software testing is a process, to evaluate the functionality of a software application with an
intent to find whether the developed software met the specified requirements or not and to
identify the defects to ensure that the product is defect-free in order to produce a quality
product.
Software testing makes sure that the testing is being done properly and the system is able to
be used. Hence the system is ready for use. Testing gives good coverage of the software
being developed and good coverage means that the testing has been done to cover the various
areas of the software which includes functionality of the application, compatibility testing of
the application with the OS of the machines on which it is installed, performance testing to
test the performance of the application as per action performed and load testing to make sure
that the system is reliable and should not crash or there should not be any blocking issues
when software is being used
2 5.1 Objective Testing
Software Testing has different goals and objectives. Software Testing has different goals and
objectives. The major objectives of Software testing are as follows: Finding defects which
may get created by the programmer while developing the software. Gaining confidence in
user and providing information about the services of transport. An objective test is a test that
has user see different services and so it can send massage for any services. Objective tests are
popular because they are easy to achieve any services and provide a concrete result.

Poultry Farm Management System 32

Chapter 5 System Testing

3 5.2 Usability Testing

Usability testing is a method used to evaluate how easy a website is to use. The tests take
place with real users to measure how easy it is for users to reach their goals. Usability testing
refers to evaluating a service or serving by testing it with representative users. Typically,
during a test participant try to complete typical tasks while observers watch, listen and takes
notes. The goal is to identify any usability problem and determine the tester’s satisfaction
with the services and store the record. The primary purpose of a usability test is to gather the
data needed to identify usability issues and improve a website design. Even the best web
design and development teams can benefit from usability testing as the tests indicate trouble
spots for users and the areas where they are getting stuck or confused.
During a usability test we
 Find out how satisfied tester are with your website.
 Identify changes required to improve user maintenance and satisfaction.
 And analyze the performance to see if it meets your usability objectives
This system is user friendly and easy to use. Every person can use it easily. Some recipes are
sees and check the usability of the system.
4 Content
 Content should be easy to understand. There must no grammatically error and spelling
errors.
 Menus, buttons or Links to different pages should be consistent and visible to all pages.
5 5.3 Software Performance Testing
Performance testing is in general a testing practice performed to determine how a system
performs in terms of responsiveness and stability under a particular workload.
Performance testing, a subset of performance engineering, is a computer science practice
which strives to build performance standards into the implementation, design and
architecture of a system.
Testing performance types
 Load testing is the simplest form of performance testing. A load test is usually conducted
to understand the behavior of the system under a specific expected load.

Poultry Farm Management System 33

Chapter 5 System Testing

 Stress testing is normally used to understand the upper limits of capacity within the
system. This kind of test is done to determine the system's robustness in terms of extreme
load and helps application administrators to determine if the system will perform
sufficiently if the current load goes well above the expected maximum.
 Spike testing is done by suddenly increasing or decreasing the load generated by a very
large number of users, and observing the behavior of the system. The goal is to determine
whether performance will suffer, the system will fail, or it will be able to handle dramatic
changes in load.
 Rather than testing for performance from a load perspective, tests are created to
determine the effects of configuration changes to the system's components on the
system's performance and behavior. A common example would be experimenting with
different methods of load-balancing.
 Isolation testing is not unique to performance testing but involves repeating a test
execution that resulted in a system problem.
6 5.4 Compatibility Testing
Compatibility Testing is a type of Software testing to check whether your software is capable
of running on different hardware, operating systems, applications, network environments or
mobile devices. Compatibility Testing is a type of Non-functional testing.
Types of Compatibility Tests
 Hardware
 Operating Systems
 Software
 Network
 Browser
 Devices
 Mobile
 Versions of the software
Now look into compatibility testing types
 Hardware: It checks software to be compatible with different hardware configurations.

Poultry Farm Management System 34

Chapter 5 System Testing

 Operating Systems: It checks your software to be compatible with different Operating

Systems like Windows, UNIX, and Mac OS etc.
 Software: It checks your developed software to be compatible with other software. For
example, MS Word application should be compatible with other software like MS
Outlook, MS Excel etc.
 Network: Evaluation of performance of a system in a network with varying parameters
such as Bandwidth, Operating speed, Capacity. It also checks application in different
networks with all parameters mentioned earlier.
 Browser: It checks the compatibility of your website with different browsers like
Firefox, Google Chrome and Internet Explorer etc.
 Devices: It checks compatibility of your software with different devices like USB port
Devices, Printers and Scanners, Other media devices and Bluetooth.
 Mobile: Checking your software is compatible with mobile platforms like Android etc.
 Versions of the software: It is verifying your software application to be compatible with
different versions of the software. For instance, checking your Microsoft Word to be
compatible with Windows 7, Windows 7.
How to do Compatibility Testing
 The initial phase of compatibility testing is to define the set of environments or platforms
the application is expected to work on.
 The tester should have enough knowledge of the platforms/software/hardware to
understand the expected application behavior under different configurations.
 The environment needs to be set-up for testing with different platforms, devices,
networks to check whether your application runs well under different configurations.
 Report the bugs. Fix the defects. Re-test to confirm defect fixing.
The most important use of compatibility testing is to ensure whether developed software
works under different configurations (as stated in requirements documentation). This testing
is necessary to check whether the application is compatible with the client's environment.
7 5.5 Load Testing
Load testing is a type of non-functional testing. A load test is type of software testing which
is conducted to understand the behavior of the application under a specific expected load.

Poultry Farm Management System 35

Chapter 5 System Testing

Load testing is performed to determine a system’s behavior under both normal and at peak
conditions.
Load testing one among the different kinds of performance testing that determines the
performance of the system in real time load conditions. It is basically used to ensure that the
application performs satisfactorily when many users try to access or use it at the same time.
 Load testing can be done under controlled lab conditions to compare the capabilities of
different systems or to accurately measure the capabilities of a single system.
 Load testing involves simulating real-life user load for the target application. It helps you
determine how your application behaves when multiple users hit it simultaneously.
Load testing differs from stress testing, which evaluates the extent to which a system keeps
working when subjected to extreme workloads or when some of its hardware or software has
been compromised.
8 5.6 Security Testing
Security testing is a type of Software Testing that uncovers vulnerabilities, threats, risks in a
software application and prevents malicious attacks from intruders. The main goal of
Security Testing is to identify the threats in the system and measure its potential
vulnerabilities, so the threats can be encountered and the system does not stop functioning or
cannot be exploited. It also helps in detecting all possible security risks in the system and
helps developers to fix the problems through coding. There are seven main types of security
testing as per Open-Source Security Testing methodology manual. They are explained as
follows:
 Vulnerability Scanning: This is done through automated software to scan a system
against known vulnerability signatures.
 Security Scanning: It involves identifying network and system weaknesses, and later
provides solutions for reducing these risks. This scanning can be performed for both
Manual and Automated scanning.
 Penetration testing: This kind of testing simulates an attack from a malicious hacker.
This testing involves analysis of a particular system to check for potential vulnerabilities
to an external hacking attempt.

Poultry Farm Management System 36

Chapter 5 System Testing

 Risk Assessment: This testing involves analysis of security risks observed in the
organization. Risks are classified as Low, Medium and High. This testing recommends
controls and measures to reduce the risk.

9 5.7 Installation Testing

Installation testing is performed to check if the software has been correctly installed with all
the inherent features and that the product is working as per expectations. Also known as
implementation testing, it is done in the last phase of testing before the end user has his/her
first interaction with the product.
Few points need to check in the prior to Installation testing:
 Installation should be run at default location & it should present to user with default
location with user can able to change the default location.
 Verify that user should able to install software from different location like over network,
online installation.
 Verify to check is the Installer.exe is calculating the disk space needed to successfully
install the application prior to install the application.
 Verify the software installation on multiple platforms, before doing this need to confirm
the supported list of platforms.
 Verify that successful “Silent installation”. In the Silent installation messages in the
process of installation are not displayed on UI, all messages are added in log files and
based on messages occurred is used as input in the installation process.
 Verify if the Interactive installation, GUI screen presented to user & user needs to
provide input parameters in installation. This is majorly used in product installation.
 Verify that after successful installation of software is it working as per mention in
specification document & meet user needs.
 Upon un-installation of software application check for the all previously installed files
and registry entries are removed or not.
 Verify that is user able to uninstall or repair the software application.

Poultry Farm Management System 37

Chapter 5 System Testing

10 5.8 Test Cases

A test case is a set of actions executed to verify a particular feature or functionality of your
software application. A Test Case contains test steps, test data, precondition and post
condition developed for specific test scenario to verify any requirement. Test case is a
specification of the inputs, execution conditions, testing procedure, and expected results that
define a single test to be executed to achieve a particular software testing objective, such as
to exercise a particular program path or to verify compliance with a specific requirement as
shown Table 5.1
Table 5.1 Test Case of Login
Test Cases Objectives

1 To make sure the admin can easily manage user accounts.

2 Make sure the admin can easily get feedback from all users and website
visitors.
3 Make sure the site admin can assign proper resources/

4 To ensure that user rights are properly controlled.

5 To ensure that the admin can perform all your work.

6 Make sure admin can easily send reminder to users.

These are the test cases which we used in our website. Admin can make sure that user can
easily login in website. Also make sure all work of website and adding record and add other
authors/user and view record/services update profile of company like name, address etc.
11 5.9 Test Case of User
Admin must have login when it uses for change as shown Table 5.2
Table 5.2: user can login with System
Actor User
Preconditions User have login detail.
Actions User login with software application.
Expected Results Login failed due to incorrect information.
Result Login with system successfully.
When the user easily login then it adds new user for our website after login as shown
Table.5.3

Poultry Farm Management System 38

Chapter 5 System Testing

Table 5.3: User can Manage the purchase.

Actor User
Preconditions User have login detail.
Actions User will manage the purchase.
Expected Results User may fail for manage purchase.
Result Add resources with system successfully.
When the User easily login then it adds distributors for our website after login as shown
Table 5.4
Table 5.4: User Add distributors
Actor User
Preconditions User have login detail.
Actions User add the distributor detail on website.

Expected Results Distributor detail will add in system.

Result Add distributor with system successfully.

12 5.10 Testing Results

The test results are the result of the entire process of software testing life cycle. Such results
are created, offering an insight into the delivery of a software project, as a result of this
project, Table 5.5 has been shown as the results of key website testing in representing the
status of partners.
Table 5.5: Testing Results
Test Test Description Testing Test Case Name Test ID
Case # Environment Software
1 Check response when Test successful user login Pass
valid email and
password is entered
2 Records(manage Test successful Add, Edit, Delete Pass
purchase)
3 Manage bank transaction Test successful Add, Edit, Delete Pass
4 Performance Test successful User Right Pass

Poultry Farm Management System 39

Chapter 5 System Testing

13
14 5.11 Summary
In this chapter, we have tested the developed system. The testing is very important to ensure
the accuracy of the project. Software checks ensures that either the necessary functionality is
developed or not? Compatibility testing to test this project, purpose testing and many other
techniques are used. Finally, there are some test issues that are working properly or not. We
used White Box Testing Technology to test the internal code segment of the project.

Poultry Farm Management System 40

CHAPTER 6
CONCLUSION
Chapter 6 Conclusion

15 6.1 Conclusion
This project is a humble approach to solving the most important, rising, and mostly forgotten
part of farming: poultry farming. It is the most ignored business practice in our nation, still
done in a less efficient and very conservative manner. Our system is a gesture to help those
engaged in the sector with their day-to-day work, record keeping, etc. This system will help
them to increase their income and flourish their business

Poultry Farm Management System 42