KUKU BOX FLOCK

PRODUCTION MANAGEMENT
PLATFORM (SASS)
SOFTWARE ENGINEERING PROJECT
Prepared By: Eng. Mark Mayalla
 Background
KukuBox is an enterprise solution aimed at assisting production ( ock production being
the rst use case) through technological solutions (web portals, mobile apps, databases,
servers, e.t.c) so at to make it easy for the business owners to have a 360 degrees view of
their organisation.

Problem Statement
The main inspiration is the hardship a ock manager faces in managing the farms
considering no enough time for visiting the farms physically. The business owner will be
required to conduct multiple follow ups using normal communication medius such as
voice calls, chats and emails.

Brief
To solve the underlying problem the KukuBox platform, at its high lever has to provide
below solutions so as to solve its business goal of managing a complete ock production.
i. The platform must have a robust user management solution that can authenticate and
authorise di erent users at di erent ownerships
ii. The platform must have a robust and exible production manager solution that can
manage the production of di erent ock pro les with di erent products (meat, eggs,
etc) and by products (manure) at di erent locations (farms, houses) in di erent
batches
iii. The platform must have a robust accounting solution that can capture expenses and
income so as to generate accurate essential accounting reports
iv. The platform must have a robust inventory management solution so as to manage the
reception, distribution and reordering of inventory items so as to generate essential
reports
v. The platform must have a robust procurement management solution so as to conduct
the procurement requisition process whenever it is required to purchase di erent
items (stocks or assets) from di erent vendors. The procurement module must be
linked to the accounting module so as to automate the postings of nancial
transactions
vi. The platform must have a robust Administration Dashboard that can e ciently
manage the overall infrastructures suspend accounts, important con gurations,
customer support, billings and so much more.
vii. In addition but not compulsory the platform may have but not limited to the following
- Fleet management solution
- Payroll solution
- Human Resource (HR) Solution (Performance Reviews, Delegations and Leaves)
- Customer Relationship Management (CRM) Solution
fi
ff
ff
ff
ff
ff
fl
fl
fl
fi
ff
fl
fi
fi
ffi
ff
fl
ff
Architecture (Infrastructure and Channels)
The KukuBox solution must be available in the following Interactive Medias
i. Web Application
ii. IOS App
iii. Android Application
iv. Desktop Application

The platform must have the following essential parts for its architecture
i. API (Enables communication between the interactive medias and the database using strict
business logics)
ii. Database (The blueprint and warehouse of all the data generated and captured by the
platform)

The platform may contain di erent third party integrations for services such as
i. Communication (Calls, Emails and SMSs)
ii. Payment Processing
iii. Navigation (maps) and etc
ff
 METHODOLOGY
This section is aimed at describing the methodology that will be used to engineer this platform.
The methodology consists of ve steps.
i. Requirement Engineering
ii. System Design
iii. System Implementation
iv. Quality Assurance
v. Deployment and Maintenance

REQUIREMENT ENGINEERING
During this stage a software engineer and the product owner will tend to identify the
di erent stakeholders (system users) that will be using the system. After identifying all the
stakeholders required to use the system, the software engineer with an help of the
product owner will identify all the requirements of the stakeholder through a requirement
engineering technique called user stories.
The user stories will then be analysed by the software engineer and the team so as to
formulate the software requirements. These requirements will form the document called
the scope of work which stands as an agreement between the software engineer and the
product owner on what will be features of the system to be designed.

SYSTEM DESIGN
During this stage a software engineer and the team will work on the designs of the
following.
i. Data ow Diagrams
ii. Database Design
iii. Class Diagrams Design
iv. UI/UX Design

The purpose of design is to help the development process clear. Most of the key limitations and
obstacles that the system might have will be detected and settled in the design phase. The end of
this process provides an artefact that can be scaled.

SYSTEM IMPLEMENTATION
During this stage the software engineer and the development team will be working on the
designed software to develop each agreed requirement from the scope of work. At this stage is
where the actual coding and con guration is conducted. The end of this stage provides source
code that can be ready for deployment but may include di erent errors and bugs.

QUALITY ASSURANCE
During this stage multiple test are conducted for the developed software so as to detect
an x a number of bugs that will exist. This step will automated and manual processes.
The bellow are the automated tests that will be conducted so as to ensure the source
code of the software is clean from bugs.
i. Unit Tests
ii. Integration Tests
ff
fi
fl
fi
fi
ff
 iii. Feature Tests
After the software engineer and the team have written and conducted multiple test and
are con dent on the software its when a manual type of test will be conducted that is
called User Acceptance Test (UAT). UAT is conducted by the software engineer,
development team and the stakeholders. This test is aimed to determine if the users
accept the software and issues coming from UAT may not include mostly of technical
bugs instead they will be more of usability issues that will also be improved to make the
software user friendly.

DEPLOYMENT AND MAINTENANCE

During this stage the system my be handled to the internal IT team for deployment with
an assistance of our software development team. If the system will be deployed outside
then it could be done directly by our development team. The activities include server
con guration, security con guration, database setup and many more. The system will
also be tested on how it performs on the production server and a maintenance service
will be o ered for the newly deployed software
fi
fi
ff
fi
 DEVELOPMENT TIME AND COST ESTIMATION
S/N PROCESS DELIVERABLES TIME

1 Requirement Engineering - User Stories 2 week

- Scope of work
2 Software Design - Database Schema 4 weeks
- Data ow Diagrams
- Class Diagrams
- Web UI/UX Design
- Android UI/UX Design
- IOS UI/UX Design

3 Software Development - REST API 48 weeks (series time)

- Web Application
- Android Application
- IOS Application

4 Quality Assurance Unit Tests, Feature Test, 8 weeks

UAT

5 Deployment & Maintenance Server Con guration, 2 week

Live system

The estimated duration of the project is 64 weeks.

The time required for development is (64 weeks times 5 days/week) equals 320 days.
For each day 8 hours of work totals to 2560 hours
For each the cost of development is 25,000 TZS which totals to 64,000,000 TZS
fl
fi