SCHOOL OF INFORMATION SCIENCE AND TECHNOLOGY

DEPARTMENT OF COMPUTING SCIENCE

ANITTAH FRUIT MANAGEMENT SYSTEM.

BIT 302 BUSINESS SYSTEM APPLICATION

By

ANNE WANGECI KIRAGU

INP17/00002/19

SUBMITTED TO
DEPARTMENT COMPUTING SCIENCE
KISII UNIVERSITY
KISII, KENYA

IN PARTIAL FULLFILMENT FOR THE REQUIREMENT OF THE AWARD OF BACHELOR OF

SCIENCE IN INFORMATION TECHNOLOGY

i
Declaration

I declare that this project is my original work and has never been submitted for the award of Bachelor of
Science in information technology in any institution of higher learning.

Name Signature Date

STUDENT ........................ ……..………

This project documentation has been submitted for the examination and as per the requirement of
Information Technology Business System Application course.

Name signature Date

SUPERVISOR …….................. …......…........

ii
iii
Abstract

ANITTAH Fruit Management System is a software comprises several modules. These modules include
Stock module and Sales module. Stock management module will help in stock record keeping, Sales
module will ease and streamline selling process and finance module will help to keep track manage the
profits.

Objectives of the System is to improve accuracy and to enhance safety and efficiency in running Fruit
business. Also ease the use because the system interface is designed such a way its user friendly and
simple to use.

This system is used for management of fruit product. Through this system not only maintain records of
products but also maintaining sales record, suppliers’ and their payment records, customers’ and their order
record, employee’ and generates daily & monthly report.
This system automatically update admin on decreasing of product and stock quantity and manage the whole
process of order and processing...
After successful interviews with entrepreneurs running Fruit business and through observations, I
noticed they needed a good software to streamlines the business process

iv
Table of Contents
DECLARATION......................................................................................................................................................... ii
ABSTRACT................................................................................................................................................................ iii
CHAPTER ONE INTRODUCTION....................................................................................................................... 1
1.0 Introduction.................................................................................................................................................. 1
1.1 Background Information......................................................................................................................... 1
1.2 Problem Statement.................................................................................................................2
1.3 Objectives....................................................................................................................................................... 2
1.4 Constraints.................................................................................................................................................... 2
1.5 Characteristic Of Proposed System..................................................................................................... 2
1.6 Scope................................................................................................................................................................ 3
1.7 Definitions of Terms and Abbreviation Meanings......................................................................... 3
CHAPTER TWO LITERATURE REVIEW......................................................................................................... 4
2.0 Introductions................................................................................................................................................ 4
2.1 Existing Systems.......................................................................................................................................... 7
2.2 Proposed System......................................................................................................................................... 7
2.3 Functions and Specificatons................................................................................................................... 7
CHAPTER THREE ANALYSIS AND DESIGN.................................................................................................. 8
3.0 Introduction.................................................................................................................................................. 8
3.1 System Analysis........................................................................................................................................... 8
3.1.1 Analysis Of Proposed System........................................................................................................... 8
3.2 Requirements Definitions...................................................................................................................... 8
3.2.1 Methods of Infromation Gathering.................................................................................................. 9
3.3 System Design............................................................................................................................................. 9
3.4 System Modelling........................................................................................................................................ 9
3.5 System Fowchart........................................................................................................................................ 9
3.5.1 Structure Chart...................................................................................................................................... 10
3.5.2 System Flowchart Diagram.............................................................................................................. 11
3.5.3 Use Case Model...................................................................................................................................... 12
3.6 Usecase Descriptions.............................................................................................................................. 14
3.7.1 Level ‘O’ DFD........................................................................................................................................... 20
3.7.2 Level ‘1’ DFD........................................................................................................................................... 21
3.7.2 Entity Relationship.............................................................................................................................. 22
3.8 Database Design........................................................................................................................................ 24

v
CHAPTER FOUR METHODOLOGY................................................................................................................. 26
4.0 Introduction............................................................................................................................................... 25
4.1 System Development Methodology.................................................................................................. 25
4.1.1 Extreme Programming....................................................................................................................... 25
4.1.2 Extreme Programming Features.................................................................................................... 25
4.1.3 Illustration of Extreme Programming System.......................................................................... 25
4.1.4 System Development in Life Cycle................................................................................................ 27
4.1.5 Why Extreme Programming............................................................................................................ 29
4.2 Assumptions .............................................................................................................................................. 29
CHAPTER FIVE PROJECT TIMELINE AND BUDGET............................................................................... 30
5.0 Gant Chart................................................................................................................................................... 30
5.1 Gant Chart for the Development of SBMS....................................................................................... 31
5.2 Budget........................................................................................................................................................... 32
CHAPTER SIX SYSTEM IMPLEMENTATION............................................................................................. 33
6.0 Introduction............................................................................................................................................... 33
6.1 Choice Of Programming Language.................................................................................................... 33
6.2 System Testing and Debugging........................................................................................................... 33
6.3 System Documentation.......................................................................................................................... 34
6.4 Hardware Requirements....................................................................................................................... 34
6.5 Software Requirements......................................................................................................................... 34
6.6 Database Specifications......................................................................................................................... 34
6.7 System Architecture................................................................................................................................ 35
6.8 Module Description................................................................................................................................. 36
6.9 System Mainetance.................................................................................................................................. 49
CHAPTER SEVEN CONCLUSION AND RECOMMEDATIONS................................................................50
7.0 Summary...................................................................................................................................................... 50
7.1 Recommedations...................................................................................................................................... 50
7.2 Conclusion................................................................................................................................................... 51
References.......................................................................................................................................................... 50
Appedix................................................................................................................................................................ 50

vi
 CHAPTER 1
INTRODUCTION

1.0INTRODUCTION

Business is an organization or economic system where goods and services are exchanged for one another
or for money. Every business requires some form of investment and enough customers to whom its
output can be sold on a consistent basis in order to make a profit.
Small business is an independently owned and operated company that is limited in size and in revenue
depending on the industry. A local bakery that employs 10 people is an example of a small business. A
manufacturing facility that employees less than 500 people is an example of a small business.
Small businesses are privately owned corporations, partnerships, or sole proprietorships that have fewer
employees and/or less annual revenue than a regular-sized business or corporation

This system is used for management of fruit product. Through this system not only maintain records of
products but also maintaining sales record, suppliers’ and their payment records, customers’ and their
order record, employee’ and generates daily & monthly report.
This system automatically update admin on decreasing of product and stock quantity and manage the
whole process of order and processing.
The system allows the users to keep all the records of all products that are in the store. The system will
give reports of the sales that have been made daily and it will also give the exact information about
products that are in the shop. It also involves manual entry upon arrival of new products.

1.1 Background
Business has become the source of income for many people and source of employment to unemployed
youths therefore many people have started investing in business hence the need for system to manage
and run it. Business is a backbone for every nation economy, hence the important to use technology to
boost and streamline the business processes.

1
1.2 Problem Statement

Fruit Businesses they are in need of a system to manage the inventory of their store. They have an
extremely limited budget, and do not want to purchase an expensive software suite in such a risky
economic environment. Also, they have always experienced problems with keeping data and security.
Meaning a very large record on papers will be tedious and difficult to keep track of products in the store,
quality of products that are available in the store based on their categories and functions.

1.3 Objectives
The aim of this project is to develop software will be able to achieve the following objectives:

 To investigate problems facing fruit business and existing systems used.

 To analyze the existing manual systems and system requirements used in fruit business
 To design and develop Desktop –based ANITTAH Fruit management system.
 To implement ANITTAH Fruit management system.
1.4 constraints
 Duration – this is the time schedule for the project, limited duration
 Economic problems such as use of money in buying internet bundles
 Limited resources such as internet resources

1.5 Characteristic of the Proposed System

 User Friendly: - The proposed system is user friendly because the retrieval and storing of data is
fast and data is maintained efficiently
 Reports are easily generated: reports can be easily generated in the proposed system so user can
generate the report as per the requirement (monthly) or in any day.
 Very less paper work: The proposed system requires very less paper work. Moreover, work
become very easy because there is no need to keep data on papers.

1.6 Scope

The scope involves of adding new fruits products, category and quantity when received from suppliers,
selling of products and viewing of sales. Also recording of suppliers and customer’s record into database
and producing of reports.

2
1.7 DEFINITION OF TERMS AND ABBREVIATION MEANINGS

System: Is the complex purposeful collection of interrelated components that work together to take some
objective.

AFMS: Abbreviation of ANITTAH Fruit Management System.

SQL-Standard query language

SQLite: is an in-process library that implements a self-contained, zero-configuration, server less, transactional SQL
database engine. The source code for SQLite exists in the public domain and is free for both private and commercial
purposes.

SQLite Manager-is a powerful database management system for SQLite databases, it combines an easy to use
interface with blazing speed and advanced features.

DFD-Data Flow Diagram

3
 CHAPTER 2
LITERATURE REVIEW
2.0INTRODUCTION
The use of technology in business has taken a sudden but remarkable upsurge in the history of man. In
the old times, business took a slow pace, thanks to the lack of tools that would allow for faster business
transactions. Everything was done with the help of some mechanical tools and the bare hands, which
made it unthinkable to do business instantly.

A short course in the history of technology in business would allow one to see the radical yet dramatic
shift from the old business procedures to the innovative approaches as seen today. In addition, it would
also give one a better understanding of how important the use of technology in business is.

In the earliest days of shop keeping, merchants wrote down purchases, or they looked at how many units
were gone at the day's end and then did their best to forecast future needs. Experience and intuition were
key skills, but it remained an inexact method, even when applied to operations that were quite small by
today's standards.

Luckily, in 1889 a man named Herman Hollerith invented the first punch card that could be read by
machines. By feeding sheets of paper that have little holes in specific places, people could record complex
data for a variety of purposes from census taking to clocking in and out of work. This was basically the
precursor to computers that can read data in tiny microchips. And Hollerith’s company even went on to
form the world’s first computer company, IBM.

After the Industrial Revolution, efficiency and mass production became the main goals of businesses,
along with an improved customer experience at the point of sale. Harvard University took Hollerith’s idea
in the 1930s and created a punch card system for businesses. Companies could tell which products were
being ordered and also record some inventory and sales data based on punch cards customers would fill
out for catalog items. Unfortunately, Harvard’s order management system cost too much and was too
slow to keep up with rising business challenges.

Merchants knew they needed a better system, and researchers created the forerunner of the modern bar-
coding system in the late 1940s and early 1950s. It used ultraviolet light-sensitive ink and a reader to
mark items for sale. Again, the system was too cumbersome and lacked the computing power needed to
make it work. Technology had yet to catch up with their ideas.

The development of affordable laser technology in the 1960s revived the concept. Lasers allowed smaller,
faster and cheaper readers or scanners. The modern bar code, or the Universal Product Code (UPC), was
born and caught on just before the 1970s. As computing power became better, the power of UPC codes to
help track and manage inventory improved exponentially.

During the mid to late 1990s, retailers began implementing modern inventory management systems,
made possible in large part by advances in computer and software technology. The systems work in a
circular process, from purchase tracking to inventory monitoring to re-ordering and back around again.

4
Business technology by definition, is the ever-increasing reliance on information technology by
businesses of all types to handle and optimize their business processes, applies current knowledge for
some useful purpose.
Anigbogu (2000) defined a computer as an electronic device capable of accepting data and instructions,
processing the data based on the instructions to generate results or output in such a manner that is yet to
be equaled by any other known machine to mankind. Since the computer is capable of accepting data and
instructions, store this data and generate an Output, it is therefore necessary that we harness this quality
and use it to our advantage.

The origin of business accounting software which is related to Small Business Management System can be
traced back to 1959 when IBM developed “9PAC”, a first report generation “language”, which allowed
users to store and access structured data from relational databases from their computers (Scott 2015).
The companies started to invest in the development of proprietary business systems designed to specific
requirements, as jobs were done in batches. As computers advanced in capability, ideas to develop
generalized accounting systems with flexible functionalities became feasible in 1973, with development
of SAP RF that handled a wide range of business operations for faster financial decision processes with
limited intermediaries.

Emmanuel and Choji (2012) stated that the introduction of computer into information technology has
massively improved small business sector. According to Ngoma (2009), systems used to manage Small
Business Data have been referred to in various ways: Transaction Processing System, Management
Information System, Stock Management System, Inventory Management System and accounting software.

Management information systems (Lucey, 1989, Thierauf, 1984). The system is capable of converting the
collected data from the routine user and machine interactions in to the effective information which later
on is used by the decision makers to make efficient decisions. The specialized systems that are being used
for decision making for the management at all levels are generally known as management information
systems (Thierauf, 1984). Information systems are of significant importance in any type of organization,
generally, it is really impossible for any organization to operate without any sort of information system.
These information systems are developed by focusing the needs and requirements of the particular
organization which are unique for every other organization.

Technological Boom

Innovations in technology started to rise in the nineteenth century. If you come to think about it, these
inventions are rather simple, but their impact on business caused it to transform to what it is today. With
a steady rise in the number of patents issued by the United States Patent Office, multiple segments of the
economy revolved to gain benefits.

Some of the past innovative products and methods that helped to shape the face of business and economy
are the barbed wire, cattle farming, railroad air brakes, sleeping cars, the camera, the carpet sweeper, and
the typewriter. All of these had influenced the way people worked and led their daily lives. When these
innovations were combined, they formed a powerful army that gave way to the massive use of technology
in business.

5
Electricity and Communications

Industrial processes rely on sources of energy for them to be fully functional. Before electricity was
utilized for this purpose, other natural sources such as coal and water were used. This is rather an
unconventional way of fueling up factories because the said energy sources are not readily available for
industrial use. With the discovery of the incandescent bulb by Thomas Edison, a series of other
discoveries and inventions gave way for instant sources of energy.

Electric utilities were ushered in during the late 1800? s. Although these utilities had a low transmission
range and limited power, wide residential use became possible. These utilities were further developed by
George Westinghouse that made it possible to supply both residential homes and power-hungry
industries the energy that they needed to perform daily business tasks.

Communications, on the other hand, was revolutionized with the invention of the telephone by Alexander
Graham Bell. It was indeed a giant leap for communication, which ultimately affected the business world
in many aspects. A necessary item in any business office, the telephone has certainly bridged the gap
between many people and as far as business is concerned, it brought better relationships and
opportunities from clients and customers.

Current Developments

The things that the past brought for the benefit of business using technology did not stop there.
Typewriters were replaced by word processors, telephones have gone mobile, and every manual
business transaction is being automated with various applications and software. The use of technology in
business is innumerable and widespread. Even a short history of this would suffice for one to understand
how revolutionary the changes have been.

Still, technology is always evolving as it continues to grow not only for business use, but also for the
growth and utilization of other fields. Therefore, coping with change is imperative for one to reap the
advantages of the use of technology in business.

6
2.1 EXISTING SYSTEM
Some on the problems of these existing systems:
Inadequate software performance - This refers to slow system response times and transaction
throughput rates
Software that is difficult to use - Many people have experienced first-hand the frustration of using
software that is cumbersome, difficult to navigate, and requires several steps to perform simple tasks.
This problem relates to a lack of understanding of how humans interact with computers and is also the
result of a history of modifications that are not planned and coordinated to account for ease of use. For
example, the addition of numerous workarounds over a period of time in legacy systems can have the
overall effect of convoluting the original system design.
Obsolete software - Software that no longer works due to new hardware or support software changes -
This refers to software that is based on functions found in older versions of databases and operating
systems. An example of this can be found in old COBOL code that will not compile on new compilers due
to the use of verbs that are no longer supported in the compiler. Many vendors try to make new releases
of support software upwardly compatible, but there are usually cases where one minor area of non-
support from the base system can cause a major revision of the system. The only other option is not to
upgrade the support software. This decision can be justified for the short-term, but a point is usually
reached where the software must either be replaced or modified

2.2 PROPOSED SYSTEM

The proposed system will be designed to provide the following benefits;
 The system would enhance management services and improve productivity.
 The system would enhance easier and friendly User/System interface.
 The system would be cost effective.
 The system will be able to run several businesses.
 Reduced paper work

2.3 FUNCTIONS AND SPECIFICATIONS

The proposed system will perform the following functions:

 Add new product category

 Add product Name
 Manage stock
 Records keeping –products records, suppliers, customers and sales records
 Produce reports any time they are needed
 Produce receipt

7
 CHAPTER 3
ANALYSIS AND DESIGN

3.0. INTRODUCTION

Software analysis and design includes all activities, which help the transformation of requirement
specification into implementation. System is a collection of an interrelated components that works
together to achieve a purpose. System analysis is the systematic examination or detailed study of a
system in order to identify problems of the system, and using the information gathered in the analysis
stage to recommend improvements or solution to the system.
System design is an abstract representation of a system component and their relationship and which
describe the aggregated functionality and performance of the system. System design is also the overall
plan or blueprint for how to obtain answer to the question being asked. The design specifies which of the
various type of approach.

3.1 SYSTEM ANALYSIS

System analysis is the study of sets of interacting entities, including computer systems analysis. This field
is closely related to requirements analysis or operations research. It is also "an explicit formal inquiry
carried out to help someone identify a better course of action and make a better decision than he might
otherwise have made. System Analysis is a methodology that involves the application of systematic
approaches to collects facts about an existing system with the aim of improving it or replacing it with
more efficient system within the context of the available resources. In other words, System analysis can
also be viewed as the process of investigating a system, identifying problems and using the information to
recommend improvements to the system.

3.1.1 Analysis of the Proposed System

The proposed ANITTAH Fruit Management System started with project planning by determining the
users of the system, aims and objectives of the project. After these, extensive research was done to
determine how to design an effective system, as well as to review the current system. Then, the design
was with an initial prototype of the system, and then refined it based on their suggestions. Phases of
analysis, design and implementation were performed iteratively until users and designers agreed on a
final system specification.

3.2 REQUIREMENT DEFINITIONS

Preliminary investigation plays an important role in developing a satisfactory requirement. Its’ as a result
of thorough investigation of how the current or the existing system works using the facts gathered at the
preliminary investigation that leads to focusing on the possibility of replacing the existing system or
improving the existing system. This task involves information gathering.

8
3.2.1 METHODS OF INFORMATION GATHERING

Collection of data is the act of getting and gathering information from various sources in order to be able
to compose the project. Data used for designing the system were gathered through various means and
methods and they include:
 Collecting and analyzing existing materials on the project topic, written by different expert.
 Studying the present system in detail and the organizational style.
 Understanding the input and output processes of the related existing system.
 Interviews: A qualitative form of interview was conducted at KISII to some business people
running small business to understand the problems they face, and the mode of operation of the old
system.
 Primary data: This source has to do with the text book contacted for the development of this
project.
 Observations

3.3 SYSTEM DESIGN

System design is the process of defining the architecture, components, modules, interfaces, and data for a
system to satisfy specified requirements through system modeling. One could see it as the application of
systems theory to produce development. The design of this system will be user friendly. It shall be
designed in such a way that employees will be able to navigate easily through the information supplied
on the system.

3.4 SYSTEM MODELLING

During the system requirements and design activity, systems may be modeled as a set of components and
relationships between these components. These are normally illustrated graphically in a system
architecture model that gives the reader an overview of the system organization. System modeling helps
to give more detailed system specifications which are in form of graphical representations that can
describe problem to be solved or the system to be developed. Because of the graphical representations
used, models are often more understandable than detailed natural language description of the system
requirements.
The ANITTAH Fruit Management System is based different model view to represent the system in
understandable way such as in flowcharts, use case models, object models and Activity diagrams

3.5 SYSTEM FLOWCHAT

System flowchart used to represent an algorithm or process, showing the steps as boxes of various kinds,
and their order by connecting these with arrows. This diagrammatic representation can give a step-by-
step solution to a given problem. Process operations are represented in these boxes, and arrows
connecting them represent flow of control. Flowcharts are used in analyzing, designing, documenting or
managing a process or program in various fields. Different symbols are used in the flowchart to represent
input, output, decision, connectors and process.

9
3.5.1 STRUCTURE CHART

SELECT MENU

ADMIN USER
LOGIN LOGIN

ADMIN
MENU USER MENU

ADD PRODUCT
CATEGORY
ADD PRODUCT

ADD PRODUCT

ADD CATEGORY

MANAGE STOCK

MAKE SALES
MAKE SALES

MANAGE STOCK
VIEW SALES

VIEW
CUSTOMER RECORDS
Add User

VIEW RECORDS

VIEW REPORTS

10
3.5.2 SYSTEM FLOWCHART

START

SELECT LOGIN

YES
LOGIN
AS ADMIN
ADMIN

NO

YES
LOGIN
AS USER
USER

NO

NO

EXIT

STOP

11
3.6 USE CASE MODEL

Add
Product <
<
Add
category

Manage
stock

Make
Sales
<<include all>> Login to the
System
View
Sales

Administrator
Manage
users

View
Reports

Change
Password

Logout

Exit

Figure 3.6.1 Use Case Diagram

12
 Product
<
<
Add
category

Manage
stock <<Include all>>

Make
Sales
Login to the
System
View
Records

Staff
Logout

Exit

Figure 3.6.2 Use Case Diagram

3.6 USE CASE MODEL DESCRIPTION

3.6.1 Use case description for Login to System
13
 Use case name Login to System
Summary System validates the user
Actor the System Administrator
Precondition the login page must be displayed
Main sequence:
1. The Administrator goes to the login menu and click on it.
2. System prompts the user for username and password
3. The administrator inserts username and password to the fields.
4. System checks the username and password.
5. If the input were valid value, then system will display general system of the ANITTAH Fruit
management system.
Alternative sequence:
6. Step 5: if the username or password is not correct, the System displays an Error message. And
prompts for the correct username and password.
7. Step 1-4: if the user clicks on back, the system will go on the welcome page.
8. Post condition: username and password of the user is Validated.

3.6.2 Use Case Description for Product Entry

Use case name Add products

Summery successfully record products name ,selling, Buying price
Actor System Administrator
Dependency include login into the system
Flowof event
1. The Administrator login into the system.
2. Go to the system home page and menus and Select on Stock management menu options
3. The system display insert button on the form if clicked it will open another form.
4. Then administrator fills the form.
5. Then save.
6. System checks the data entered whether correct or not
7. If the data’s input were correct then system saved it into the disks.

3.6.3 Use Case Description for Stock

14
 Use case name Manage Stock
Summery successfully record Stock quantity
Actor System Administrator
Dependency include login into the system
Flowof event
1. The System Administrator login into the system.
2. Go to the system home page and menus.
3. Select Stocks
4. The system display menu item, if clicked it will open the stock form.
5. Then administrator fills the form.
6. Then save.

3.6.4 Use Case Description for Sales

Use case name Make Sales

Summery Record sales and Produce Receipt for the buyer

Actor System Administrator

Dependency include login into the system

Flowof event
1. The administrator login
2. The administrator opens Make sales form from the menu.
3. The system displays new sales form
4. The administrator fills the details in the form
5. The administrators fill both forms use options save and print.
6. If the administrator press on these options
7. System checks weather the input data were correct or not
8. If it is correct the system saves into the disks and produces receipt

Alternative sequence:
Step 7: If the input data is not correct then system displays error message.
15
 Step 1-8: if the user enters cancel the ANITTAH Fruit management system will stop the operation.
Entry condition . The administrator system must be on process and logged in to the system.

Quality Requirements. The transaction must be processed less than two seconds.

3.6.5 Use Case Description for View Sales

Use case name View Sales

Summery gives summarized report about sold products any day.

Actor System Administrator

Dependency include login into the system

Flow of event
1. The Administrator login to the system

2. The Administrator use option of the “view sales”.

3 Press on View records.

4. The system displays the summarized document which can be printed.
Entry condition The Administrator system must be on process and login to the system.

Exit condition The Administrator making trans-action could not be processed.

Quality Requirements. The transaction must be processed less than two seconds.

3.6.6 Use Case Description for Product Entry

Use case name Product Entry

16
Summery successfully updates, deletes and new products

Actor System Administrator & User

Dependency include login into the system

Flowof event
1. The Administrator login into the system.

2. Go to the system home page and menus.

3. Select Product Entry

4. The system display the available products that is recorded before

5. Then the administrator add new product based on the category, selects the product he/she wants to

Update or delete or add quantity

6. Then press submit or update or delete button from available options.

7. The system checks whether the data entered is correct or not.

8. If data’s input is correct then system save it into the disks.

Entry condition The Administrator system must be on process and login to the system.

Exit condition . The Administrator making transaction could not be processed.

Quality Requirements. The transaction must be process less than two seconds.

3.6.7 Use Case Description for Product Category

Use case name Add Category

17
Summery successfully adds and deletes Product category details.

Actor System Administrator

Dependency include login into the system

Flowof event

1. The Administrator login into the system.

2. Go to the system home page and menus.

3. Select on add category option.

4. The system display the available categories that have been recorded before

5. Then the administrator selects add or delete.

6. Then press add or delete from available options.

7. System checks the data entered whether correct or not

8. If the data’s input is correct then system saved it into the disks.

Alternative sequence

Step 1-10: if the user enters cancel the ANITTAH Fruit management system will
Stop the operation.
Entry condition The Administrator system must be on process and logged in to the system.

Quality Requirements. The transaction must be process less than two seconds.

3.6.8 Use Case Description for User Management

Use case name Add Staff

Summery successfully record new staff member data
18
 Actor System Administrator
Dependency include login into the system
Flowof event
1. The Administrator login into the system.
2. Go to the system home page and menus.
3. Select on User management option.
4. Then the administrator fills the form with staff’s details.
5. Then save the staff data that is filled in step 4.
6. System checks the data entered whether correct or not
8. If the data’s input were correct then system saved it into the disks.

Alternative sequence
Step 7: If the input form has error the system displays the errors

Step 1-7: if the user enters back or cancel the ANITTAH Fruit management system will
Stop the operation.
Entry condition the administrator system must Be on process and logged in to the system.

Quality Requirements. The transaction must be process less than two seconds.

3.7 Data Flow Diagram

19
A data flow diagram (DFD) is a graphical representation of the flow of data through an information system. A
data flow diagram illustrates the processes, data stores, and external entities in a system and the connecting data
flows.

This is the zero level DFD of ANITTAH Fruit management system. It’s a basic overview of the whole
ANITTAH Fruit management system or process being analyzed or modeled. it’s designed to be at glance
view of stock, inventory showing the systems as a high-level process with its relationship to external
entities of suppliers, savings and sales.

Order
Management
Sales Management
Stock
Management

ANITTAH
Fruit
Management
System

Savings
Management
Supplier Customer
Management Management

Figure: 3.7.2 DFD level 0(Context Diagram)

Level 1
20
 Product Product details

Admin

Supplier details
Supplier Sales

Login

Sales details

Staff details
Staff Report
registration
analysis

User
User Details
Manage
ment

Generate
report

Figure: 3.7.3 DFD level 1

21
 Entity Relationship Diagram For the Proposed System

Comprises of entities, attributes and relationships of the system.

Manage

ADMIN

Manage Suppliers

Supply

Register
staff

Stock

Staff
Make sales

Purchase

Customers

Figure .3.7.4: Entity Relationship Diagram

22
Figure: 3.7.5 Entity Relationship Diagram

23
3.8 DATABASE DESIGN
Users Table

Stock Information Table

Customer Table

24
Supplier Table

Sales Table

25
 CHAPTER 4

METHODOLOGY

4.0 INTRODUCTION

Methodology is a term used to describe a process, technique or manner in which an action is performed.
Under the development a system, a methodology refers to the process that was taken to ensure that a
system is effectively and efficiently developed

4.1 SYSTEM DEVELOPMENT METHODOLOGY

The systems development methodology is used to describe the process for building systems, intended to
develop systems in a very deliberate, structured and methodical way.
Extreme programming was used as the methodology of choice in developing this ANITTAH Fruit
Management System.

4.1.1 Extreme Programming (XP)

Extreme programming is a software development methodology which is intended to improve software

quality and responsiveness to changing customer requirements. As a type of agile software development,
it advocates frequent "releases" in short development cycles. This is intended to improve productivity
and introduce checkpoints where new customer requirements can be adopted. The main goal of XP is to
lower the cost of change in software requirements.

4.1.2 Extreme Programming Features

Extreme programming has the following features/ core practices

 Fine scale feedback which involves, Test driven development, Planning game, Whole team and
Pair programming
 Continuous process rather than batch. This also involves, Continuous Integration, Design
Improvement, and Small Releases
 Shared understanding including Simple design, System metaphor, Collective code ownership and
Coding standards or coding conventions And Programmer welfare that involves Sustainable pace
that is forty-hour week.

26
4.1.3 Illustration of Extreme Programming System Development Process

Figure 4.1.3 Extreme programming

4.1.4 System Development Life Cycle

In developing this System, the following steps were taken;

i. Planning
Planning provides the basis for acquiring the resources needed to achieve a solution. This phase ensured
that the problem solved was the one that needed to be solved and that the initial description was
complete and consistent.
Under the planning phase of the project, a project timeline, work plan and Budget were developed. Under
this phase;
 The project team is formed and a project leader appointed
 The system flowcharts prepared
 The characteristics of the proposed system are defined and identified

27
ii. Analysis
At this point, the system in place is analyzed to determine system errors and attempt to solve it. This step
involves breaking down the system in different pieces to analyze the situation, analyzing project goals,
breaking down what needed to be created and attempting to engage users so that definite requirements
could be defined.

Under analysis, Requirement gathering is the most crucial aspect as many times communication gaps
arise in this phase and this leads to validation errors and bugs in the software program. Therefore, the
following techniques were used to gather information

Under analysis, the following data collection techniques were used.

a) Semi-structured interviews

Semi-structured interviews are conducted with a fairly open framework which allow for focused,
conversational, two-way communication. They can be used both to give and receive information. In the
process of developing the system, interview was done to obtain specific quantitative and qualitative
information from the interviewees, obtain general information relevant to development of ANITTAH
Fruit management system.
b) Direct (Reactive) Observation
Direct Observation is a method in which a researcher observes and records behavior / events /
activities / tasks / duties while something is happening. This was used in correspondence to interviewing
in order to gain a more holistic view of the current system. Direct observation was used as a research
methodology of choice in designing this system because; Observations give additional, more accurate
information on behavior of people than interviews or questionnaires. They can also check on the
information collected through interviews especially on sensitive topics.
c) Using available information
This is a data collection method that involves the process of examining and evaluating already existent
literature material to obtain facts and data regarding a specific subject. Locating these sources and
retrieving the information can help in data collection.

iii. Design
In system design the design functions and operations was described in detail, including interface layouts,
process diagrams and other documentation. The output of this stage described the new system as a
collection of modules or subsystems.
Design elements described the desired system features in detail, and generally included functional
hierarchy diagrams, screen layout diagrams, flowcharts and a complete case diagrams with Data Flow
diagram with a full data dictionary.

iv. Implementation phase

Here all the iterations were brought together and integrated to make one working system. Modular and
subsystem programming code was accomplished during this stage. Unit testing and module testing was
done in this stage.

28
4.1.5 Why Extreme Programming (Advantages)

Extreme Programming emphasizes teamwork. Managers, customers, and developers are all equal
partners in a collaborative team. Extreme Programming implements a simple, effective environment
enabling teams to become highly productive. The team self-organizes around the problem to solve it as
efficiently as possible.
Extreme Programming improves a software project in five essential ways; communication, simplicity,
feedback, respect, and courage. Extreme Programmers constantly communicate with their customers and
fellow programmers. They keep their design simple and clean. They get feedback by testing their
software starting on day one. They deliver the system to the customers as early as possible and
implement changes as suggested.

4.2 Assumptions made by the system developer

With regards to the intended users of the system, the following assumption are made
 The end user shall have a basic knowledge of working with computers
 The end user shall have a basic knowledge of some rudimentary terms.
 That the end user shall have a basic knowledge of the English language which is used in the GUI and in
documentation

29
 CHAPTER FIVE

PROJECT TIMELINE AND BUDGET

5.0 GANT CHART

A Gantt chart is a type of bar chart, adapted by Karol Adamiecii in 1896 and independently by Henry
Gantt in the 1910s, that illustrates a project schedule. Gantt charts illustrate the start and finish dates of
the terminal elements and summary elements of a project. Terminal elements and summary elements
comprise the work breakdown structure of the project.
Advantages of Gantt charts

 It creates a picture of complexity – complex ideas can be easily understood when presented
diagrammatically.
 It organizes your thoughts- A big task can be divided into subtasks
 It helps you to set realistic time frames –the bars on the chart indicate in which period a particular
task will be completed. This can help you get things in perspective properly.
 It is highly visible – a larger version of it can be placed where everyone can see.
Disadvantages of Gant chart

 The size of bars does not indicate the amount of work

 Gantt Charts can be complex in big projects.
 They need to be constantly updated.

30
5.1 Gant Chart for the Development of ANITTAH Fruit Management System

MONTH NOVEMBER DECEMBER JANUARY FEBRUARY MARCH

WEEK 1 2 3 4 1 2 3 4 1 2 3 4 1 2 3 4 1 2 3 4

Project
proposal

Project
planning
5.2
Project
initialization

Project
Research

System Design

System
Development

System
validation

Report Writing

Project
Presentation

BUDGET

Budget Item Details Amount in

KSH

1.EQUIPMENTS Computer 58,000/=

system(Laptop

31
 )

External Hard 4000/=

Disk for
Backup

8 GB Flash 1000/=
Disk

Printing 650/=
services

Sub-Total 48650/=

2. COMMUNICATIONS Airtime for 5 5000/=

months

Internet 5000/=
Services for 5
months

Sub-Total 10000/=

3.TRAVELLS Transportation 1000/=

services

Sub-Total 1000/=

GRAND 75,650/=
TOTAL

CHAPTER SIX

SYSTEM IMPLEMENTATION

6.0 INTRODUCTION

32
System implementation is a stage in system life cycle whereby a new system is developed, installed and
made ready for use. System implementation therefore, is a very essential stage in which its success
determines to a great extent the success of the new system. At this instance the system is duly ready to be
implemented (ANITTAH Fruit Management System).

6.1 CHOICE OF PROGRAMMING LANGUAGE

Choosing a programming language depends on how much knowledge you have on a certain programming
language and the scope of the application you are building.
The proposed application is not a web based application that needs internet facilities to function but a
desktop based application.
The programming language used for this software is JAVA. The structure of the Basic programming
language is very simple, particularly as to the executable code.
JAVA has many new and improved features such as inheritance, interfaces, and overloading that make it a
powerful object-oriented programming language. It’s easy to develop graphical user interfaces and to
connect them to handler functions provided by the application.
JAVA fully integrates the common language runtime, which together provide language interoperability,
garbage collection, enhanced security, and improved versioning support.

6.2 SYSTEM TESTING AND DEBUGING

Testing a program consists of providing the program with a set of test inputs (or test cases) and
observing if the program behaves as expected. If the program fails to behave as expected, then the
conditions under which failure occurs are noted for later debugging and correction
The aim of the testing process is to identify all defects existing in a software product. However, for most
practical systems, even after satisfactorily carrying out the testing phase, it is not possible to guarantee
that the software is error free.

Unit Test
Unit testing is undertaken after a module has been coded and successfully reviewed. Unit testing (or
module testing) is the testing of different units (or modules) of a system in isolation.
In order to test a single module, a complete environment is needed to provide all that is necessary for
execution of the module.

Integration Test
The primary objective of integration testing is to test the module interfaces, i.e. there are no errors in the
parameter passing, when one module invokes another module. During integration testing, different
modules of a system are integrated in a planned manner using an integration plan.
The integration plan specifies the steps and the order in which modules are combined to realize the full
system. After each integration step, the partially integrated system is tested.

System Test
33
System tests are designed to validate a fully developed system to assure that it meets its requirements.
There are essentially three main kinds of system testing:
 Alpha Testing. Alpha testing refers to the system testing carried out by the test team within
the developing organization.
 Beta testing. Beta testing is the system testing performed by a select group of friendly
customers.
 Acceptance Testing. Acceptance testing is the system testing performed by the customer to
determine whether he should accept the delivery of the system.

6.3 SYSYEM DOCUMENTATION

System documentation is a crucial aspect of implementation process. It describes the working of

components and serves as a method of communication between application developers and users. It also
helps future analysis of application either by the same or different system analysts and developers.
To setup the system, there must be Net beans 8.1 software and its JDK installed on the computer before it
can work.

6.4 HARDWARE REQUIREMENTS

 A minimum hard disk space of 20 Gigabytes (GB)

 RAM size of 1GB
 Pentium 4 dual processor CPU
 A VGA color monitor
 Mouse
 Keyboard

6.5 SOFTWARE REQUIREMENTS

 Windows operating system and Linux Operating System

 Net Beans software and its JDK or Eclipse software.

6.6 DATABASE SPECIFICATIONS

A database is a single file which consists of structured data and records which are stored in minimum or
no duplication of data. It is therefore a constructed, consistent and controlled pool of data. A good
database must be common to all users and independent of the programs which use it to generate output.
SQLite was used as the database application tool for designing the database.

6.7 SYSTEM ARCHITECTURE

ANITTAH Fruit Management system has a backend engine that consists of a SQLite database, Java as the
programming language and SQLite Manager and the user interface modules. The system architecture is
illustrated in Figure below.

34
 Java
Database

SQLite
Manager

AFMS Interface

AFMS SYSTEM

View Savings User Change

Stock Sales Records Reports
Sales Accounts Management password
Management

User Interface

USERS Administrator Staff

Figure 6.1 System architecture

6.8 MODULE DESCRIPTION

Admin Login Menu

35
Figure 6.1 Admin Login Form
Figure 6.1 above, shows the admin login area. This form only allows only the System Adminstrator to login to
the system

Staff Login Menu

Figure 6.2 staff Login Form

Figure 6.2 above shows the staff login section.

36
The login area for only the staffs. Main

Menu

Figure 6.3 Main Interface

Figure 6.3 above shows the main menu of this software. This interface is only for the System Administrator
who have the priviledge of managing users,access to saving accounts and also to view the daily sales.Also
enables to manage stocks,make sales ,produce reports,view custome and supplier records and change password

37
Staff Main Menu

Figure 6.4 Main Interface

The figure above shows the staff main interface. They have access to stock management, make sales, access to customer
and supplier records and produce reports.

38
Stock Management

39
Figure 6.4 Stock Management
Stock management comprises of the following Forms:

 Product Category
 Product Entry
 Stocks

Product Category

This is where the new product category is added to the system, also allow to delete the existing product category.

Product Entry Form

After adding product category, this form allows the user to add the product category type into the system
also allow to delete the existing product type.

Stocks

This form allows to add the quantity of new products and also the existing products in the system. This
is done after product Entry.

40
Sales

Figure 6.5 Sales

This module allows the user to make sales and produce receipts. Easier to use because the system is configured
to have calculation on its own after the value inputs from the user

View Sales

41
Figure 6.6 View Sales
System Administrator can view daily sales or any sales from a certain date and also print.

Customer records

42
Figure 6.7 Customer Records
The figure above shows the customer record form which help to record the customer details in case of a debt or credit.

Supplier Records

43
Figure 6.8 Supplier Records
The figure above it’s a supplier record form which allows the Administrator or User to record supplier details for
easier communication in case of need of new suppliers.

44
Reports

Figure 6.9 Reports

Customer and supplier reports are generated from here and also allow to use dates to filter the results.

Change Password

45
Figure 6.10 Change Password
This form is only accessible to the system administrator which help in password recovery.

Saving Accounts

46
Only accessible to the administrator. Allows to keep track or record of your daily savings or profits.

6.9 SYSTEM MAINTAINANCE

Maintenance is a continuous process of making modifications and upgrading the application. There are
two different ways by which this application can be maintained. They include:
 Additive or Enhancement maintenance: Business processes are dynamic. As business processes
change, applications that support these processes must evolve to reflect these changes. Thus, for
this application to perform optimally and to meet changing user requirements, it must be modified
continuously.
 Corrective maintenance: This is required in the event that an error occurred when the application
is in use. Corrections must be made to changes discovered that can cause malfunctioning of the
system.

47
 CHAPTER SEVEN

CONCLUSION AND RECOMENTATION

7.0 SUMMARY

ANITTAH Fruit management system for small business is designed to improve the accuracy, enhance
safety and streamline process in small business and ease the use because of simple and friendly user
interface.
ANITTAH Fruit management system will help ensure the security of information and reliability of
business records when accessing and improved efficiency in providing services to the customers. The
information gathered during the data collection was properly analyzed and the results provided the basis
for this system. The system underwent various types of testing and found to be functional and the
outputs produced by this system were encouraging. The Software will help reduce the loss of information
and streamline business process i.e. selling process unlike the existing system.

7.1 RECOMMEDATION

The software should be used with the necessary specifications of the system requirements and
uninterrupted power supply should be made available throughout in case of power loss.
The user of the software should have basic knowledge on computers.
The system need improvement especially in areas of accounting to deliver better services to the user.

Recommendations for future enhancements to the system include;

Widening the scope

Given the limited amount of time given to the developer, the project’s scope was rather limited to small
business and desktop application the scope can further be widened to include large scale business and in
form of android application to make a more integrated comprehensive system that covers the entire
business field.

Including additional components and functionalities

In future a new module can be included in the system payroll module. This module will help keeping
record of workers or staff and payment details.

Increased accessibility

The system can also be further enhanced so that the customers themselves can be able to access services
online in a secure manner or in mobile phones

48
7.2 CONCLUSION

ANITTAH Fruit management system for small business is designed in such a way that It can run several
types of small business, it is not restricted in running only one type of business which make it exception
and unique from existing system. Its cost effective in case you’re running several businesses, there is no
need to have each business with its own system, you only need to have one system which can manage
and provide better service, also its user friendly interface hence efficient to use.

REFERENCES

 Lectures Notes
 http://www.businessdictionary.com/definition/business.html
 Emmanuel, B. and Choji, D. (2012). A Software Application for Colleges of Education Student’s
Results Processing. Journal of Information Engineering and Applications.
 Anigbogu, S.O. (2000). Computer Application and Operation. Awka:Optimum Press.
 Barrett, S. (1999). Information’s Systems: An Exploration of Factors Influencing Effective Use. Journal
of Research on Computing in Education.

49