CHAPTER THREE

AIU POULTRY FARM INFORMATION

MANAGEMENT SYSTEM.
SYSTEM ANALYSIS PHASE.

3.1 Introduction to System Development

Systems development refers to all the activities that go into producing
an information systems solution to an organizational problem or
opportunity. Systems development is a structured kind of problem
solving with distinct activities consisting of: -
A. Systems analysis
B. Systems design
C. Programming
D. Testing
E. Conversion
F. Production and maintenance.

FIGURE 3.1
The Systems development process building a system can be broken
down into six core activities.
Systems analysis involves defining the problem, identifying its causes,
specifying the solution, and identifying the information requirements
that must be met by a system solution. System analysis also involves
a feasibility study used to determine whether the proposed solution is
achievable, from a financial, technical, and organizational standpoint,
given the organization's resources and constraints. One of the most
challenging task of the systems analyst is to define the specific
information requirements that must be met by the system solution
selected. 
Information requirements of a new system involve identifying who
needs what information, where, when, and how. The systems design is
the overall plan or model that shows how the system will meet its
information requirements. Like a blueprint of a building or house, a
system design consists of all the specifications that give the system its
form and structure. The system designer details the systems
specifications that should address all of the managerial, organizational,
and technical components of the system solution. User information
requirements drive the entire system building effort, so information
system design often demands a very high level of end-user participation.
During the programming stage, system specifications that were
prepared during the design stage are translated into software program
code. Thorough testing must be conducted to confirm that the system
produces the right results. Testing an information system involves three
types of activities: -
A. Unit testing tests each program separately in the system.
B. System testing checks the information system as a whole to
determine if it works as intended.
C. Acceptance testing results in user and management final
certification that the system is ready to be used in a production
setting.
To ensure that all aspects of testing are as comprehensive as possible,
the development team works with users to devise a systematic test plan.

3.2 System Analysis Phase

System Analysis: - is the process of investigating a system, identifying
problems and using the information to recommend improvements to the
system. Systems analysis is the process by which an individual (s)
studies a system such that an information system can be analyzed,
modeled, and a logical alternative can be chosen. Systems analysis
projects are initiated for three reasons: -
A: Problems.
B: Opportunities.
C: Directives.
The people involved include systems analysts, sponsors, and users. The
process by which systems are developed can be described by the systems
development life cycle. The tasks, techniques, and tools used by the
systems development life cycle can be referred as a methodology. CASE
tools are automated tools that support specific methodologies (1).
There are three classifications of the methodologies: -
A: Traditional.
B: Information engineering.
C: Object-oriented.

3.2.1 System Analyst (software application)

System analyst in an IT organization is a person, who analyzes the

requirement of proposed system and ensures that requirements are
conceived and documented properly & correctly. Role of an analyst
starts during Application Software Analysis Phase of SDLC. It is the
responsibility of analyst to make sure that the developed software meets
the requirements of the client. System Application Analysts have the
following responsibilities: -

A. Analyzing and understanding requirements of intended software.

B. Understanding how the project will contribute in the organization
objectives.
C. Identify sources of requirement & Validation of requirement.
D. Develop and implement requirement management plan.
E. Documentation of business, technical, process and product
requirements.
F. Coordination with clients to prioritize requirements and remove &
ambiguity.
G. Finalizing acceptance criteria with client and other stakeholders.

3.3 Current (AIU PFPE) System Description

Under system study, AIU Poultry Farm Production project team
ensured that it collected more Accurate data information on the current
1
:- https://www.sciencedirect.com/topics/computer-science/system-analysis
Traditional system. Thus, we carried out interviews, questionnaires,
including some observation in order to understand the existing system
functionalities & complete weaknesses (SWOT Analysis). In addition,
AIU Poultry Farm Production project team performed the feasibility
study to guarantee the project is realistic & Effective.
3.3.1 Analysis of the Existing System

The current AIU poultry Farm management information management

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 Desktop-App
for poultry Farm management information system will try to solve the
query of Customer, Vendor manual registration, and booking chicks for
customers interested.

Automation of the booking process whereby information moves from

various stakeholders in an orderly manner enables Customers to get
products and services fast. It is cheap and even puts less stress on the
poultry Farm.

In the existing system, poultry management information are manually

Recorded in a booklet and later on into MS Excel Spread sheet.
Records are kept on each and every purchases of birds (All Species),
feeding of birds (All Species). In the case of Medication, Vaccination of
birds (All Species), Drugs & Manure were not always recorded and
documented. The booklet where the Information records are kept is
referenced when poultry Farm Information is needed.

3.4 Problem of the Existing System

After an intensive & In-depth investigation and analysis of the present
Existing system, there are so many problems & Difficulties encountered
by the Stock Inventory Managements, which are: -

A. Cost of materials like books & pen etc.

B. Some documents are not properly documented.
C. Human error in computation is common.
D. Time wastage & Consumption is always a problem Over All
Activities.
E. Lack of Medication, Vaccination & Maintenance Information records.
F. Improper Manure Information Records.
G. Financial transactions errors etc.

3.5 Proposed System Description

3.5.1 Purpose of the New System (solutions)
A. To provide a system that can facilitate the update of a poultry farm
records (Information).
B. The system makes the overall result much easier, flexible,
Sufficient & Updates.
C. Fast amount of data can be stored in a least amount of time
(Flexibility & Efficiently).
D. It provides high level of security using different protocols like VB
Desktop APP.
3.5.2 Analysis of the Proposed System
The proposed system is such that poultry Farm Information is captured
via an interface of a software system Front-end (VB.NET) as the GUI
and saved in a database as the Back-end (MYSQL DB) for future
reference. Information records is now kept concerning new breeds (All
Species), feeding of the birds (All Species) Medication, Vaccination,
Maintenance, Sales, Purchases, Expenses & Manure sold is also
documented etc.
3.5.3 Advantages of the Proposed System
For the best of some abilities & benefits, Advantages of the proposed
system deployment in AIU Poultry Farm Production Enterprises
includes; it will bring about easy management and mining of the poultry
farm by aiding presentation of reports concerning the poultry Farm
activities (Production, Sales & Purchases). In order to achieve the
objectives mentioned earlier, we used the ASSDM/waterfall model and
techniques of structured analysis.
3.5.4 Dis-advantages of the Proposed System
A management information system is an approach where a company
uses when making various business decisions. Business owners and
managers are responsible for operational, technical and strategic
decisions. Using an information system helps these individuals gather
pertinent documents that will help them make the best decision possible.
While these systems were manual in previous decades, business
technology allows companies to implement electronic systems. Some
disadvantages can exist when using a management information system
in a company.

Common problems include failure to strategize, meeting organizational

needs, hiring and retaining good employees, staying current and
integrating all your technologies.

3.5.5 Justification of the Newly Proposed System

A. The new system will enhance a better communication between the
Board of Admins as Integrated System.
B. Decision making would be made faster and prompt because accurate
information is provided & Future Forecast.
C. Easy manipulation and retrieval of record (Data), thus reducing the
time spent in searching Stock Inventory Information records.
3.5.6 Proposed System Users Analysis
Based on the outcomes from the Proposed system study, the users,
functional and non-functional requirements of the Poultry farm
information management system were evaluated as follows: -
6.1 System User Requirements: -
From the system study, four users of the system were recognized. These
are: -
A: - System Administrator,
B: - Sales Manager (Cashier),
C: - Purchase supervisor and
D: - Product Manager.

Their requirements in the system include the following: -

A. Systems Administrator: -
The administrator is the person that manages the computer systems in
the organization. His requirements in the system include: -
1: - User registration (setup and maintain account).
2: - Maintain system (Report).
3: - Verify that peripherals are working properly.
4: - Monitor System Performance.
5: - Install software.
6: - Create a backup and recovery policy.
7: - Password and identity management.

B. Sales Manager (POS Cashier): -

The Sales manager is the person that is responsible for designing and
implementing a strategic business plan that expands company’s
customer base and ensure its strong presence. Owns recruiting,
objectives setting, coaching and performance monitoring of sales
repetitively. His requirements in the system are as follow: -
1: - Able to account for daily farm activities.
2: - Able to view stock.
3: - Able to view sales report.
4: - Able to view stock report.
5: - Able to register new employee.
6: - Able to view customer details.

C. Production Manager: -
The Production manager is a person that is responsible for the technical
management, supervision and control of the company’s production
processes (Hatching, Rearing, Feedings, Vaccination & Medication,
etc.) as well as Manure Management. His requirements are as follows: -
1: - Able to view daily activity programs.
2: - Able to view stock Inventory.
3: - Able to register (CRUD) products (End Produce).
4: - Able to view (Retrieve) products.

D. Purchase Manager: -
The Purchase manager is a person dealing with Vendors (Suppliers), and
is responsible for buying hygienic food, Medication & Protection to the
Husbandry Animals (Birds), the best quality equipment, goods and
services, at the most competitive prices, to enable a company to operate
at Optimism.
1: - Able to register supplier details.
2: - Able to view supplier details.
3: - Able to register stocks & Vendors (Suppliers).
4: - Able to view products details.
5: - Able to view purchase report.
6: - Able to view stock.

3.6 The Proposed System Objectives

To create a poultry Farm Information management system that will
improve the poultry farm system and other poultry products by distant
clients. The specific objectives of the study are: -

A: - To design & Implement a new system.

B: - To collect and analyze data from the existing system
C: - To implement the integrated system.
D: - To test and validate the integrated system.

3.6.1 PFIMS Project Scope

This project will help in collecting the perfect Poultry farming

Information (data) in detail. The collection will be apparent,
straightforward, and sensible in a short time. It will help the user know
the disease trend, Medication & Vaccination, which will help them save
their poultry’s life (Animal Husbandry), otherwise getting victims of
sudden diseases like bird flu. It will also help manage the current works
of the Poultry farmer (Activities), Cashiering of both Incomes &
Expenses of every transaction that took place, contractual or hired staff,
etc. It will help manage, track, and collect feedback from the Poultry
farm, like the health of their stock (Bird Species), if they are eating well,
if they are getting good nutrients, etc. Feedback is the leading block that
aids in course correction and provides a better environment. The
project’s main scope is to provide a fully automatic environment for
performing day-to-day activities. Some of the aspects of automation are:
-

A: - Filling up various forms and the number of copies needed to be

filled is reduced and streamlined.
B: - Creating the manifest is no longer necessary; instead, it can be
printed, saving more time.
C: - It helps in efficiently utilizing resources by increasing productivity.
D: - It made it easier to recall any data that had been entered & Easy to
operate.
E: - Feedback and any action taken can be tracked in a perfectly
streamlined manner.
F: - The system is expandable & User-friendly (User Interface).
G: - Security, this system is secure from all types of tempering
(Intruders).
H: - Can recommend solutions to the framer via previous encounters.

3.7 The Proposed System Plan (Gantt Chart)

A Gantt chart, named after the designer, Henry Gantt, is an easy-to-use

graphical tool that helps operations managers determine the status of
projects. Let us say that you are in charge of making the “hiking bear”
offered by the Toronto Teddy Bear Company.
What is a Gantt Chart?
A Gantt chart, commonly used in project management, is one of the
most popular and useful ways of showing activities (tasks or events)
displayed against time. On the left of the chart is a list of the activities
and along the top is a suitable time scale. Each activity is represented by
a bar; the position and length of the bar reflects the start date, duration
and end date of the activity. This allows you to see at a glance: -
A. What the various activities are.
B. When each activity begins and ends.
C. How long each activity is scheduled will last?
D. Where activities overlap with other activities, and by how much.
E. The start and end date of the whole project.

To summarize, a Gantt chart shows you what has to be done (the

activities) and when (the schedule) (2).

Below is a Gantt chart for the PFIMS Project Research Operation

describing Chapters over task conducted. As you can see, it shows that
several Chapters & activities are to be completed before the Supervisor
attention is addressed. Our Gantt chart tells us that by 2022/12/20, all

2
: - https://www.gantt.com/
Project Chapters & Task Operations will have been made (done). As a
project, you will have to pay close attention to the progress of the
research operations to ensure that tasks are finished & ready for
submission by their scheduled date.

Figure 3.2: The Proposed PFIMS Project Gantt Chart

3.7.1 Project Operations Scheduling

To control the timing of all operations, AIU PFPE managers set up

schedules: - they select jobs to be performed during the production
process, assign tasks to workgroups, set timetables for the completion of
tasks, and make sure that resources will be available when and where
they are needed. There are a number of scheduling techniques.

3.7.2 The Project & team Descriptions.

A. AIU PPFMS Project.

 Bello Roba Aminu
Conducted by: -
Naziru Abubakar Muhammad
Poultry Farm Information Management
Project Name
System
Research Year  2022-1443.
App Platform  VB.Net (Visual Basic) v15.
Programming
 Visual Basic (Front-end).
Language
Database  MYSQL Database (Back-end).
Project Platform  desktop Application (Database App).
 Dr. Muhammad Fathi Al-Rahman.
Supervisor
B. Project Team Members Task
 PROJECT TASK
MEMBERS
Is responsible on the entire Programming aspect, the
1: - Aminu VB.NET (Front-end).

 MYSQL Database implementation (Back-end),

2: - Nazir &
ensures successful communication between the GUI
Aminu
& DB.
3: - Nazir  Project documentation, ERD, DFD, UMLs etc.
4: - Supervisor  Dr. Abdallah Fathi Al-Rahman.

3.7.3 The Project Duration.

The duration of a project defines how much time it takes to deliver the
project, based on the resources and effort used. It is essentially the
period of time (Weeks) from the start date when a project is initiated till
its completion date. Project duration is estimated in hours, days, weeks,
& months. PFIMS project’s time duration equal to 3 months or 12
working weeks.
3.7.4 The Project Funding (Sponsorship)
In the context of a project finance transaction, one or more substantial
entities who own the ultimate equity interests in a project. The AIU
Poultry Farm Production Enterprises is the project sponsor, is
experienced in carrying out projects and in addition to their equity
holding are often involved in some aspect of the project, such as
providing the construction or operational services or playing a role in the
offtake arrangements. They are responsible for promoting, developing
and managing the project and are usually required to contribute a certain
amount of equity into the project (3).
3.8 Proposed System Architecture
A software architecture is a set of principles that define the way software
is designed and developed. An architecture defines the structure of the
software system and how it is organized. It also describes the
relationships between components, levels of abstraction, and other
aspects of the software system. An architecture can be used to define the
goals of a project, or it can be used to guide the design and development
of a new system.
3.8.1 Architectural Designs of the System
The architectural design gives a high-level view of the new system with
the main components of the system and services they provide as well as
how they communicate. The system using a three-tier architecture that
encompasses of user interfaces, process management and DBMS as
illustrated below. This structure ensures that users’ interaction with the
system is independent of storage consideration.

3
: - https://uk.practicallaw.thomsonreuters.com/w-010-6945?
transitionType=Default&contextData=(sc.Default)&firstPage=true
 Figure 3.3: PFIM System Architecture
3.8.3 Process Modeling
In process modeling, the Sequence diagram was used to model the flow
of logic within the proposed system in visual manner. It shows the major
sub-processes identified in the Poultry Management information system.
3.8.4 Data Modeling
The data modeling of the system was done by ascertaining the data
requirements, entities and their related attributes that make up the
system. Modeling of the relationships between the entities was designed
with an enriched entity relationship diagram for the system.
A. Data Requirements Details
1. Purchase: This stores information about purchases made. The
information stored includes the purchase ID, purchase date,
Employee_id,quantity, transaction mode and remarks.
2. Product: This stores information about products. The information
stored includes product ID, employee_id, name,quantity, date in,
expiry date and cost
3. Customer: This stores information about customer. The
information stored includes name, contact and address
4. Employee: This stores information about employees. The
information stored includes first name, middle name, last name, role,
address and email.
5. Order: This stores information about customer’s order. The
information stored includes customer_id, employee_id, Order_id,
order date and product_id
6. Inventory: This stores information about Stock Inventory
Informations.
AIU-PFIMS-Context Diagram.

Figure 3.4: PFIMS Context Diagram.

3.9 Feasibility Study

A feasibility study is carried out when there is a complex problem or

opportunity. It is considered the primary investigation which emphasizes
the “Look before You Loop” approach to any project. A Feasibility
study is undertaken to determine the possibility of either improving the
existing system or developing a completely new system. Remote
management is one of the core use cases for the vault.

Today, many organizations have credentials hardcoded in source code,

littered throughout configuration files and configuration management
tools, and stored in plain text in version control, wikis, and shared
volumes. It provides a central place to store these credentials, ensuring
they are encrypted, access is audit logged, and exposed only to
authorized clients. The challenge after centralization is that services are
often shared the same.

Credentials. This has been a standard practice for applications, but most
security organizations would have a panic attack if it were proposed that
all human users share the same login credentials. If those credentials
leak, it is very challenging to identify the source of the compromise or
leak. Updating or rotating credentials creates a coordination problem, as
there are many users of the credential.

3.9.1 Why we need a Feasibility Study

A: - When we have a new project with a new concept

B: - When we are not confirmed about the resources and time
C: - To suggest a possible alternative solution
D: - To provide management with enough information to know
E: - Whether the project can be done.
F: - Whether the final product will benefit its intended users.

3.9.2 AIU PFPE Feasibility Study and Critical Features

Poultry Farming is one the most important sector of agriculture industry
in Nigeria by providing employment to 3.5 million people. Broiler meat
is the cheapest source of animal protein available in Nigeria by
contributing 5.81% in agriculture growth and 10.84% in Livestock
growth. According to Industry sources there is capacity of 5,000
Environmental Control Houses in Nigeria and currently 4,500 houses are
working, out of which 15% (87) are in Kaduna State and remaining 85%
(725) are in other provinces.

3.9.3 PFIMS Feasibility Analysis.

A feasibility Analysis is a set of system proposal according to its
workability, impact on the organization, ability to meet user needs and
affective use of resources. The objective of Feasibility study is not to
solve the problem. However, to acquire a sense of its scope. During the
study, the problem definition is crystallized and aspects of problem to be
included in the system are determined. Consequently, costs and benefits
are estimated with greater details at this stage.

The result of feasibility study is a system formal proposal. This is simply

a form of documenting or detailing the nature and scope of the proposed
solution. The proposed summarizes what is known and what going to be
done. The key consideration involved in the feasibility analysis are
technical, economic and operational.

A. Technical Feasibility.
Technical Feasibility is the most important of all types of feasibility
analysis. Technical feasibility deals with hardware as well as software
requirements. An idea from the Outline design to system requirements in
terms of inputs, outputs, files and procedures is drawn and type of
hardware, software, and the methods required for running the system are
analyzed and subsequently approved.

B. Economical Feasibility.

Economic analysis is the most frequently used method for evaluating

the effectiveness of the software application development (Desktop App
development). More commonly known as the cost/benefit analysis. The
procedure is to determine the benefits and savings that are expected from
a specific candidate system and compare them with benefits & costs. If
the benefits outweigh cost. The decision is made to design and
implement the New-system; otherwise further alternatives must be made
for modification & Evaluations. Here it is seeming that, no new tools
(hardware or software) are needed for the development of the system.

C. Schedule Feasibility.

Schedule Feasibility is concerned with the completion of the project

development, which is conducted by the AIU Poultry Farm Project
team within the fixed time span. It is an important factor as it can affect
other factors like machine availability, tools, cost development and delay
in the development of the other system. By the way, this project is
assigned to the AIU PFPE Projection team, at the same one of its
member’s is a student at IUA Khartoum Sudan. The project is assign
as an academic exercise to be completed within a fixed period and to
have been defended.

D. Operational feasibility.

The purpose of the operational feasibility study is to determine whether

the new (Proposed) system could be useful if it is developed,
implemented & deployed? Will there be any resistance from the users
that will undermine the possible application benefits? From the outputs
(Outcomes) of the meeting & research methodology method, the types
of questionnaire adopted, that was held with the system users (AIU
Admins), it was found that all of them support the development of new
Proposed-system. The positive responses from the Enterprises
Administrators encouraged the AIU Poultry Farm Project Team in
building such a New-system.

E.Behavioral Feasibility

The AIU Poultry Farm Information Management system task

operation process is quite easy to use and learn due to its simplicity and
attractive interfaces. Users (Admin) requires no special training for
operating the system. They can easily work and operate this new-system
sufficiently, effectively & successfully.

F. Legal feasibility
Legal feasibility study is to know if the proposed project confirms the
legal and ethical requirement.  It is important that the project or business
is following the requirements needed to start a business or a project
including business licenses, certificates, copyrights, business insurance,
tax number, health and safety measures, and many more.
There are some things to consider in legal feasibility study including
ethical issues and some social issues. These issues are the privacy,
nepotism, and accountability. A proposed system should determine if it
has a conflicts with a legal requirements like for example if the data
processing system is complying with the local Data Protection Act (4).
3.10 Poultry Farm Information Management System UML
diagrams.
The Unified Modeling Language (UML) is a standard visual language
for describing and modelling software (Desktop Application) blueprints.
The UML is more than just a graphical language. Stated formally, the
UML is for: - Visualizing, Specifying, Constructing, and Documenting.
The artifacts of a software-intensive system (particularly systems built
using the object-oriented style). In AIU UML diagrams, there are four
diagrams available to model the dynamic nature of the proposed system.
A. Use Case Diagram: -
To model a system, the most important aspect is to capture the dynamic
behavior. Dynamic behavior means the behavior of the system when it is
running/operating. the use case diagram is dynamic in nature, there
should be some internal or external factors for making the interaction.
These internal and external agents are known as actors. Use case
diagrams consists of actors, use cases and their relationships.
The diagram is used to model the system/subsystem of an application. A
single use case diagram captures a particular functionality of a system (5).

4
: - http://sampleproposal.net/feasibility-study/legal-feasibility-study/
5
: - https://www.tutorialspoint.com/uml/uml_component_diagram.htm
 Figure 3.5: PFIMS, UML USECASE DIAGRAM.
A1. Use Case Specification: - A use case specification captures the
requirements, typically of a system, in the form of a use case that
contains the descriptive requirements steps in a logical sequence so that
document specification can be understood by users to obtain sign-off of
their requirements and for testers and developers to understand what is
needed by the system to test and build the system functionality detailed
in the system use case. Use cases and use case specifications were
popular in the unified modelling language (UML) and is still used in
some corporate environments.
A2. Use Case Tables
1. Login
2. User registration
3. Assign Roles
4. Module Class Permission
5. Manage production
 6. Manage purchases
7. Manage User Access & Full Application.
8. Manage Customer_Order (Sales).
9. Manage Employees CRUD.
10. Manage Stock Inventory information’s.
11. Logout.

B. Sequence Diagrams: – 
A sequence diagram simply depicts interaction between objects in a
sequential order i.e. 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. These diagrams are widely used by
businessmen and software developers to document and understand
requirements for new and existing systems (6).

Figure 3.6: PFIMS, UML SEQUENCE DIAGRAM.

C. Activity Diagram: -
Activity diagram is another important diagram in UML to describe the
dynamic aspects of the system. Activity diagram is basically a flowchart
to represent the flow from one activity to another activity. The activity

6
: - https://www.tutorialspoint.com/uml/uml_component_diagram.htm
can be described as an operation of the system. The control flow is
drawn from one operation to another.
This flow can be sequential, branched, or concurrent. Activity diagrams
deal with all type of flow control by using different elements such as
fork, join, etc (7).

Figure 3.7: PFIMS, UML ACTIVITY DIAGRAM.

D. Class Diagram: -
Class diagram is a static diagram. It represents the static view of an
application. Class diagram is not only used for visualizing, describing,
and documenting different aspects of a system but also for constructing
executable code of the software application.
7
: - https://www.tutorialspoint.com/uml/uml_component_diagram.htm
Class diagram describes the attributes and operations of a class and also
the constraints imposed on the system. The class diagrams are widely
used in the modeling of object oriented systems because they are the
only UML diagrams, which can be mapped directly with object-oriented
languages.
Class diagram shows a collection of classes, interfaces, associations,
collaborations, and constraints. It is also known as a structural diagram
(8).

Figure 3.8: PFIMS, UML CLASS DIAGRAM.

3.11 PFIMS Data Dictionary

3.11.1 Definition

8
: - https://www.tutorialspoint.com/uml/uml_component_diagram.htm
A data dictionary describes the data stored in a database. In simple
terms, it provides information and insights about your database, in other
words, a data dictionary is a documentation for all the data assets in a
database. A data dictionary provides complete information about an
organization’s data assets. This information can include: -
A. Column description
B. Distinct values, missing values, and frequency of each value within a
column
C. Data type
D. Classification and glossary terms.

A data dictionary is a centralized repository of information about data

such as meaning, relationships to other data, origin, usage, and formats.
Software in which metadata is stored, manipulated and defined – a data
dictionary is normally associated with a tool used to support software
engineering.

3.11.2 AIU PFIMS Data Dictionary

Below are the descriptions of all the design objects used in the system
development of AIU Poultry Information Management System.
These objects include: -
A. Processes
B. Data stores, and
C. The External Entities involved in the system.

Table 3.1: - Description of Process (Operations)

SN Process Description
1 User Registration Allows the Product Manager, Sales
Manager and Purchase Manger
(Staff) to insert their details into the
system.
2 Authentication Allows the system to authenticate
registered users and provide an
Authentication response.
3 Add Product Allows the Product manager and the
purchase manager to register and
view products in the system
respectively.
4 Purchases (Customer Order) It Processes customer orders and
allows the sales manager to allocate a
product to a customer.
5 View Customer-Order (Sales) Generates a sales reports on products
report sold to customers.
6 View Suppliers Report Generates a supplier report.
7 Add Purchases Allows the purchase manager to add
purchases and also view registered
purchases.
8 View Purchase Report Generates a purchase report.
9 Employee Registration Allows the System Admin Manager
(Staff) to insert Employee records &
their details profile into the system.
10 Stock Inventory Information Allows the Purchase Manger (Staff),
items, Machines, tools, Equipment’s
record to be inserted their details into
the system.

Table 3.2: Description of Data Stores (Database_Tables).

S/N Data Stores Description
1 Login Stores details of login records
(User_Name & Password) into the
system.
2 Roles Stores details of Role played records
of any Registered User into the
system.
3 Permission Stores details of Permission Access to
any class module of any Registered
User records in the system.
4 Registered User Stores details of registered users in the
system
5 Registered Products records Stores details of registered products
6 Registered customer records Stores details of registered customers.
7 Cutomer_Order (Sales) Stores registered sales records of the
 records products
8 Purchase Records Stores registered Purchases.
9 Stock Inventory records Stores registered item, tools, machines
& Utensils.
10 Registered Employee Profile Stores details of registered Employees.

Table 3.3: Description of External Entities

S/ External Entity Description
N
1 Sales Manager (Cashier) or Staff The Sales manager is responsible
for entering and updating Sales,
Order_Purchases,
Customer_Order details, views
product report, sales report and
registration of new customers into
the system.
2 Production Manager or Staff The Production manager is
responsible for registration of the
Poultry Farm products, viewing
registered products report, Sales
& Stock Inventory from the
system.
3 Purchase Manager of Staff The Purchase Manager is
responsible for registration of all
purchases made, recording
supplier details, recording &
viewing stock Inventory report
respectively, supplier (Vendor)
report and purchases report.

3.11.3 Database Implementation, Structure & Relationships

Table 3.4: User Registration Table Structure.

Field name Data type Size Constraint Description
User_id Int 5 Not null Primary key
User_role_id Int 5 Not null Foreign Key
User _Name Varchar 45 Not null
E-mail Varchar 45 Not null
Phone Varchar 45 Not null
DOB Varchar 45 Not null
Address String 20 Not null

Table 3.5: Login Table Structure.

Field name Data type Size Constraint Description
Login_id Int 5 Not null Foreign Key
Role_id Int 5 Not null Foreign Key
Use_name Varchar 45 Not null
Password Varchar 45 Not null

Table 3.6: Roles Table Structure.

Field name Data type Size Constraint Description
Role_id Int 5 Not null Primary Key
Role_name Int 5 Not null
Role_discription String 45 Not null

Table 3.7: Permission Table Structure.

Field name Data type Size Constraint Description
Per_id Int 5 Not null Primary Key
Per_Role_id Int 5 Not null Foreign Key
Per_Mode Varchar 45 Not null
Per_Name Varchar 45 Not null

Table 3.8: Purchase Table Structure.

Field name Data type Size Constraint Description
Purchase_id Int 5 Not null primary key,
auto increment,
Quantity Varchar 45 Not null
Price Varchar 45
Purchase_date Date Not null
Cost_Price Varchar 45
Transaction_mode Enum(Cash,Bank) Not null
Cutomer_id int 5 Foreign key
REFERENCES
Customer
Customer_id)
Supplier_name Varchar 45 Not null
Employee_id Int 5 Not null Foreign key
REFERENCES
Employee
(Employee_id)

Table 3.9: Product Table Structure

Field name Data type Size Constraint Description
Product_id Int 5 Not null, Auto
increment,
primary key
Name Varchar 45 Not null
Cost_Price Varchar 45 Not null
Quantity Varchar 45 Not null
Date_in Date Not null
Expiry_date Date Not null
Employee_id Int 5 Not null, Foreign key
REFERENCES
Employee
(Employee_id)

Table 3.10: Customer Table Structure

Field name Data type Size Constraint Description
Customer_id Int 5 Not null, Auto
increment,
primary key
Name Varchar 45 Not null
Address Varchar 45 Not null
Phone, Mobile Varchar 45 Not null
Contact Varchar 45 Not null
E-mail Varchar 45 Not null
Table 3.11: Employee Table Structure
Field name Data type Size Constraint Description
Employee_id Int 5 Not null, Auto increment,
primary_key
Name Varchar 45 Not null
User_name Varchar 45 Not null
Password Varchar 45 Not null
Address Varchar 45 Not null
Phone, Mobile Varchar 45 Not null
Contact Varchar 45 Not null
E-mail Varchar 45 Not null

Table 3.12: Customer_Order Table Structure

Field name Data Size Constraint Description
type
Order_id Int 5 Not null, Auto
increment,
Primary_key
Order_date Date Not null
Quantity Int 5 Not null
Cost_Price Int 5 Not null
Status text
Product_id Int 5 Not null, foreign key
REFERENCES
Product
(product_id)

Customer_id Int 5 Not null, Foreign_key

REFERENCES
Customer
(customer_id)
Employee_id Int 5 Not null, Foreign_key
REFERENCES
Employee
(Employee_id)
3.12 Security Analysis.

3.12.1 Definition : The protection of information systems against

unauthorized access to or modification of information, whether in
storage, processing or transit, and against the denial of service to
authorized users, including those measures necessary to detect,
document, and counter such threats (9).
This role is responsible for the analysis and development of the
integration, testing, operations, and maintenance of systems security.
Personnel performing this work role may unofficially or alternatively be
called (10):-

A. Information Assurance Security Officer.

B. Information Systems Security Engineer.
C. Information Systems Security Manager.
D. Information Systems Security Officer (ISSO).
E. Information Security Analyst / Administrator.
F. Security Analyst.

3.12.2: Information System Security: - As computers and other digital

devices have become essential to business and commerce, they have also
increasingly become a target for attacks. In order for a company or an
individual to use a computing device with confidence, they must first be
assured that the device is not compromised in any way and that all
communications will be secure. These are the fundamental concepts of
information systems security and discuss some of the measures that can
be taken to mitigate security threats.

9
: - https://csrc.nist.gov/glossary/term/information_systems_security
10
: - https://pressbooks.pub/bus206/chapter/chapter-6-information-systems-security/
 The Security trial
Figure 3.9
3.12.3: The Information Security Triad: - CIA

A. Confidentiality: - When protecting information, we want to be able

to restrict access to those who are allowed to see it; everyone else should
be disallowed from learning anything about its contents. This is the
essence of confidentiality.
B. Integrity: - Integrity is the assurance that the information being
accessed has not been altered and truly represents what is intended. Just
as a person with integrity means what he or she says and can be trusted
to consistently represent the truth, information integrity means
information truly represents its intended meaning.
C. Availability: - Information availability is the third part of the CIA
triad. Availability means that information can be accessed and modified
by anyone authorized to do so in an appropriate timeframe. Depending
on the type of information, appropriate timeframe can mean different
things.

3.12.4: Tools for Information Security

In order to ensure the confidentiality, integrity, and availability of
information, organizations can choose from a variety of tools. Each of
these tools can be utilized as part of an overall information-security
policy, which will be discussed in the next section.
A. Authentication: - The most common way to identify someone is
through their physical appearance, but how do we identify someone
sitting behind a computer screen or at the ATM? Tools for
authentication are used to ensure that the person accessing the
information is, indeed, who they present themselves to be. the most
common form of authentication today is the user ID and password. In
this case, the authentication is done by confirming something that the
user knows (their ID and password).
B. Access Control: - Once a user has been authenticated, the next step is
to ensure that they can only access the information resources that are
appropriate. This is done through the use of access control. Access
control determines which users are authorized to read, modify, add,
and/or delete information. Several different access control models exist.
Here we will discuss two: the access control list (ACL) and role-based
access control (RBAC).

C. Encryption: - Many times, an organization needs to transmit

information over the Internet or transfer it on external media such as a
CD or flash drive. In these cases, even with proper authentication and
access control, it is possible for an unauthorized person to get access to
the data. Encryption is a process of encoding data upon its transmission
or storage so that only authorized individuals can read it. 

3.13: System Specification Requirements.

The below listed materials will create room for computerized efficiency
in the system operation of the security techniques.
A. Software Requirement
1. A windows XP or higher version operating system (8/8.1/10/11).
2. MYSQL Server
3. Internet explorer/Chrome/Fire fox
4. MYSQL Connector.
5. XAMPP/WAMPP.

B. Hardware Requirement
1. Processor: - Dual core and above
2. RAM: - 1 GB and above
3. Hard Disk Utilization: - 40 GB and above
4. Input Devices: - Mouse, Keyboard, etc.
5. Output Devices: - Monitor, Printer, etc.

C. Non-functional Requirements

Requirements, which are not related to functional aspect of software, fall

into this category. They are implicit or expected characteristics of
software, which users make assumption of. Non-functional
requirements include: -

1. Security.
2. Logging.
3. Storage.
4. Configuration.
5. Performance.
6. Cost.
7. Interoperability.
8. Flexibility.
9. Disaster recovery.
10. Accessibility.