DECLARATION

This project proposal is my original work and has not been presented to any other examination body. No
part of this report should be produced without the permission of the author.
STANLEY OBWAYA MAKORI:

Sign______________________________________Date__________________________

DECLARATION BY THE SUPERVISOR

This project has been submitted with my approval as the Keroka Technical Training Institute supervisor.
Mrs ARIKA REBECCA:

Sign __________________________________Date____________________________

ii
DEDICATION
I dedicate this project to my friends as a motivation to them, to my family members and to my supervisor
for being my mentor.

iii
ACKNOWLEDGMENT

First I would like to acknowledge the almighty God for enabling me to come this far, I would also like to
acknowledge my supervisor for all the support and guidance she’s given to me, my parents for the moral
and financial support and the Institute at large.

iv
ABSTRACT
“DAILY MANAGEMENT SYSTEM” is software developed for managing various activities related to
dairy milk at Mavuno Milk Corporation. For the past few years, the numbers of dairy outlets are
increasing rapidly. Thereby the consumption of milk is also increasing hence there is a lot of strain on the
persons who are running the shops and software’s are not usually used in this context. This particular
project deals with the problems on managing dairy milk products and avoids the problems which occur
when carried out manually. Identification of the drawbacks of the existing system lead to the designing of
a computerized system that will be compatible with the existing work system. The system is user friendly
and more GUI oriented.
We can improve the efficiency of the system, thus overcome the drawbacks of the existing system.

Daily Management System deals with all kind of milk accounting details, dairy related reports,
employee details, supplier details and other resource related details. It tracks all the details of sales
from the day one to the end of the month which can be used for all reporting purpose, tracking of
employee’s attendance, progress in the sales.

Different reports and Queries can be generated based on the vast options related to sales and dairy
management.

v
 DECLARATION………………………………………………………………………………..ii

DEDICATION……………………………………………………………………………....…iii

ACKNOWLEDGMENT…………………………………………………………………….....iv

ABSTRACT…………………………………………………………………………………….v

TABLE OF CONTENTS………………………………………………………………………....vi

CHAPTER ONE

1.0 INTRODUCTION...................................................................................................................1

1.1 Definition of terms...................................................................................................................1

1.2 Background of the study..........................................................................................................2

1.3 Problem Statement...................................................................................................................2

1.4 Purpose of the study.................................................................................................................3

1.5 Objectives.................................................................................................................................3

1.7 Significance of the study..........................................................................................................3

1.8 Limitations of the current system............................................................................................4

CHAPTER TWO

LITERATURE REVIEW................................................................................................................5

2.1 Introduction..............................................................................................................................5

2.2 Management Information System............................................................................................5

2.3 Database Management Systems (DBMS)................................................................................6

2.4 Importance of DBMS...............................................................................................................7

2.5 Role of DBMS.........................................................................................................................7

2.6 DBMS ACTIVITIES...............................................................................................................7

vi
 CHAPTER THREE
RESEARCH METHODOLOGIES…………………………………………………………8

3.1 Introduction………………………………………………………………………………8

3.2 Data collection methods……………………………………………………………….…8

3.2.1 Questionnaire……………………………………………………………………….…..8

3.2.2 Observation……………………………………………………………………………..9

3.2.3Interviewing……………………………………………………………………………..9

3.3 Data analysis Method……………………………………………………………………..9

3.3.1 Sampling procedures…………………………………………………………………..10

3.4 Data analysis……………………………………………………………………………..10

CHAPTER FOUR
SYSTEM ANALYSIS AND REQUIREMENT MODELING……………………………....11

4.0 System analysis………………………………………………………………………….11

4.0.1 Feasibility study……………………………………………………………………….11

4.0.2 Operation Feasibility…………………………………………………………………..11

4.0.3 Technical Feasibility…………………………………………………………………..12

4.0.4 Economic Feasibility…………………………………………………………………..12

4.2 System specification……………………………………………………………………..12

4.3 System design……………………………………………………………………………13

4.3.0 Logical design…………………………………………………………………………13

4.3.1 Input design……………………………………………………………………………14

4.3.2 Output design………………………………………………………………………….14

4.3.3 Physical design………………………………………………………………………...15

vii
4.3.4 Modular design………………………………………………………………………...15

4.3.5 Database design………………………………………………………………………..16

4.4 system coding……………………………………………………………………………16

4.5 System testing……………………………………………………………………………17

4.6 System implementation………………………………………………………………….18

CHAPTER FIVE

DATA PRESENTATION AND ANALYSIS……………………………………………….24

CHAPTER SIX

CONCLUSION, RECOMMENDATION AND REFERENCES…………………...………29

6.0 Conclusion……………………………………………………………………………….29

6.1 Recommendations……………………………………………………………………….29

REFERENCES………………………………………………………………………………30

APPENDIX …………………………………………………………………………………31

viii
 CHAPTER ONE

1.0 INTRODUCTION

Daily Management System is an enterprise application for Mtafutaji Corporation. The system
will be used to track and maintain records of milk sold, customers available, suppliers, track
employees and produce reports.

This system is designed to ease the work load of everyday attendants and management.

The main feature includes, inventory and stock control, invoicing, accounting, client and vendor
management.

1.1 Definition of terms

Management Information System - is a computerized database of information organized and

programmed in such a way that it produces regular reports on operations for every level of
management in a company.
Database Management System - is a set of programs that enables you to store, modify, and
extract information from a database, it also provides users with tools to add, delete, access,
modify, and analyze data stored in one location.
Database - is a structured collection of data. The data are typically organized to model relevant
aspects of reality (for example, the availability of rooms in hotels), in a way that supports
processes requiring this information (for example, finding a hotel with vacancies).
System – this is a set of interrelated components which work together to achieve the specific
goal and produce reports which are useful to the managers.

1
1.2 Background of the study

For the past few years, the numbers of milk consumption is increasing thus promotes to the
increase in outlets rapidly. For this case, consumption of milk is also increasing hence there is a
lot of challenges and strains on the persons who are running the milk store and shops being that
software’s are not usually used.

Mtafutaji Corporation is one of the outlets located in Migori County, Migori is in the South
Nyanza Region.
Although Mtafutaji Corporation has been in existence for the past decade with current number
of employees totaling 28, a lot of facilities are missing.

When milk is brought by the supplier details are being recorded down on a piece of paper this
sometimes leads to duplication of data and information, when the supplier comes later his/her
records is checked through several files to confirm whether they are registered this manual
system leads to wastage of resources and time. Some of employees sneaked out of work since
the records of employees were not kept safely and also unauthorized employee can easily
manipulate the information and make it hard to calculate their salary. The dairy product sales
was also in a separate sheet where it had to be followed daily with lots of strain to keenly know
the stock balance and also quantity bought. Employees’ payment and suppliers’ payments were
also delayed as a result of slow calculation of their payments.

The system that was used was manual and for a long period, customers and suppliers have faced
the problem of slow data processing during registration and suppliers payments.

1.3 Problem Statement

In manual system, suppliers faced the problem of slow data processing during registering,
supplying and payments. There was also a lot of data duplication during registration as a result of
lack of proper records storage and poor security of data since unauthorized employee can easily
manipulate the data and information. Calculation of product sales was a time consuming and had
to be done daily to know the stock balance and also quantity bought.

2
 Daily Management System will track all the details of sales from day one to the end of the
month which can be used for all reporting purpose, tracking of employee’s attendance, and
progress in the sales.

1.4 Purpose of the study

The main goal of this project is to come up with a working Daily Management System that
deals with all kind of milk accounting details, dairy related reports, employee details, supplier
details and other resource related details. It tracks all the details of sales from the day one to the
end of the month which can be used for all reporting purpose, tracking of employee’s
attendance, progress in the sales

1.5 Objectives
The specific objectives this project will have to achieve so as to accomplish the goals set are:

i. Cost reduction.

ii. Change from a paper based way of record keeping to an electronic way hence
increasing efficiency
iii. Fast and develop information when needed i.e. reduce tedious repetitive process of
preparing payments for employees and suppliers.

iv. Enhance the security of data, and effectiveness of data by at least 60% compared to the
manual system during analyzing.

1.7 Significance of the study

The project mainly deals with Daily Management System. This system will provide several
advantages over the traditional system (manual).

The new system will speed up the entire process of producing reports and speed up payment of
employees and suppliers hence efficiency and providing effective services.

The system will also reduce errors and loss of records as well as fraudulent activities in the dairy.

3
1.8 Limitations of the current system

a) There’s poor storage of data hence it can be lost or tempered with due to poor storage
locations.
b) Increased transaction leads to increase of source document hence maintenance of
the paper based system was hard to manage
c) Since the system was manual, data retrieval and updating was tiresome
d) There was a lot of timewasting
e) There was a lot of errors encountered during retrieval and updating of data
and information.

4
 CHAPTER TWO

LITERATURE REVIEW

2.1 Introduction
This chapter examines the definition of Daily Management System by different authors,
transaction processing system, decision support systems and database management systems what
other researchers have published and said about a similar problem under study and review of
accounting records management

2.2 Management Information System

MIS refers to a system to convert data from internal and external sources into information and to
communicate that information in an appropriate format to managers at all levels to enable them
make timely and effective decisions in planning, directing and controlling their activities.

The MIS represents the electronic automation of several different kinds of counting, tallying,
record-keeping, and accounting techniques of which the by far oldest, of course, was the ledger
on which the business owner kept track of his or her business.

Automation emerged in the 1880s in the form of tabulating cards which could be sorted and
counted. These were the punch-cards still remembered by many: they captured elements of
information keyed in on punch-card machines; the cards were then processed by other machines
some of which could print out results of tallies. Each card was the equivalent of what today
would be called a database record, with different areas on the card treated as fields. World-
famous IBM had its start in 1911; it was then called Computing-Tabulating-Recording Company.

Before IBM there was C-T-R. Punch cards were used to keep time records and to record weights
at scales. The U.S. Census used such cards to record and to manipulate its data as well. When the
first computers emerged after World War II punch-card systems were used both as their front end
(feeding them data and programs) and as their output (computers cut cards and other machines
printed from these). Card systems did not entirely disappear until the 1970s. They were
ultimately replaced by magnetic storage media (tape and disks).

5
 Computers using such storage media speeded up tallying; the computer introduced calculating
functions. MIS developed as the most crucial accounting functions became computerized.

Jofre-Giraudo, Streeter, and Lazarus (1990) found that computerized management information
systems (MIS) improved the accuracy, speed, and timeliness of information for processing,
which improved the management decision-making process. They also found that records were
updated on a timelier basis and records were kept at a higher level of detail when using MIS.
This more accurate and timely data allowed more farmers to project their financial condition on
monthly basis, which could help farmers reevaluate their production and financial situations
quickly so that changes in management could be implemented, if necessary.

2.3 Database Management Systems (DBMS)

Database management systems are programs that are written to store, update and retrieve
information from a database

According to Loudon (1998), DBMS is an application program that permits an organization to

centralize data, manage it efficiently and provide access to the stored data by other application
programs. London further states that the database approach has promising potential advantages
they include;

 The database approach as compared to the traditional file based system attempt to
eliminate redundancy by integrating the files so that multiple copies of the same data are
not stored. However, the database approach does not eliminate redundancy entirely but
controls the amount of redundancy inherent in the database. Some time it is necessary to
duplicate some data items to improve performance.
 Data consistence; by controlling or eliminating redundancy we are reducing the risks of
inconsistencies occurring , if data item is stored only once in the database, any update to
its value has to be performed only once and a new value is available immediately to all
users.
 Sharing of data typically, the people or departments that use them own files; on the other
hand the database belongs to the entire organizational and can be shared by all authorized
users.
According to Haag, Blue plus an HMO of blue cross and blue shield of Minnesota also realizes
in the importance of information based preventive programs.

6
 It has developed a mammography programs called a decision for file, the key success of the
Kaiser and blue plus programs is formation technology tools such as database management system
that supports the concepts of data ware housing and mining.

2.4 Importance of DBMS

a. It ensure security for the data in the database by safe guarding it against unauthorized
access and corruption(damage)
b. Provides efficient data access.
c. Allows users to enter new information, update current records and delete outdated data
d. Keeps statistics of data items in database.
2.5 Role of DBMS
DBMS helps in providing effective and fast operation in the Mtafutaji Corporation. These
include:-
a. Easy retrieval of suppliers, customers and employees details.
b. Eases the employees work through faster customers or suppliers details.
c. It enforces integrity of data and information.
d. Backup and recovery of data.

2.6 DBMS ACTIVITIES

As a management system, it does the following;
a. Provides security of data on what data any employee can see or change.
b. Storing of data and information about suppliers, customers and employees
c. Multiuser access control without affecting the integrity of the database
d. Transaction management which ensures that all the updates in a given transaction are
made or not made at all.
The review helped modernize Mtafutaji Corporation which was more complicated in that there
was more paper work. This paper work was so insecure in that information can get lost leading
to backsliding of the everyday management.

This system will help employees and top management of Mtafutaji Corporation in
communication effectively leading to easy running of the Corporation.

7
 CHAPTER THREE

RESEARCH METHODOLOGIES

3.1 Introduction
This chapter describes the methodology and data collection techniques that the researcher used
to gather data and other factual information related to the designing and constructing of
Mtafutaji’s Daily Management System, the hardware and software requirements, time schedule
of the activities proposed to be done.

3.2 Data collection methods

The data collection instruments used to gather accurate information about the existing system
and the requirements for the new system were interviews with stakeholders, questionnaires,
observations and secondary data. Interviews and questionnaires were administered to employees
and management staff to collect user requirements. Observation of the current existing system
was done at the front desk and Administration Office in order to find out how the existing
system functions, the problems encountered and how they can be solved by the new
computerized system. In summary the data collection methods used to gather requirements are;

a) Interviews
b) Questionnaires
c) Observation

3.2.1 Questionnaire

Questionnaires were administered to the selected respondents. The questionnaires were made up
of both closed and open ended questions. The questionnaires administered helped the researcher
to get more information on the requirements to designing a computerized record and accounting
system.

8
 The questionnaires were given to the following individuals:

a) Chief Executive Officer.

b) Daily attendants. (employees)
c) Suppliers.

3.2.2 Observation

The researcher critically observed what takes place in the current work system, more especially
on how data is collected, entered, stored and retrieved, data security and management.

3.2.3Interviewing

The researcher interviewed face – to –face some employees on the current work system both
structured and unstructured questionnaires were used in capturing information and clarification
over some system requirements.

3.3 Data analysis Method

The researcher used both qualitative and quantitative data analysis to analyze the data and in
particularly the data collected was analyzed statistically, following the data collection
procedures to guarantee viability and reliability. The analyst used the fact finding techniques to
collect data from various sources of information about the system which comprised of:-

1 System users – they were the most important information source; from them it was
possible to find out the existing system activities and to determine the user objectives
and requirements.
2 Forms and documents – they were useful sources of information about the system
data flows and transactions.
3 Computer programs – they were used to determine the details of the data
structures or the processes.

9
4 Procedure manuals – they specified user activities in the business process. There after
data will be encoded analyzed and interpreted then a report of findings conclusion and
recommendation will be prepared as a final report and the data captured used in the various
stages of system development. These aspects will guarantee validity and reliability.

3.3.1 Sampling procedures

The researcher used two types of sampling:

 Ratified random sampling.

 Systematic random sampling.

In ratified random sampling the researcher divided the subjects (suppliers) according to their
growing regions and a subgroup as a sample from each region to represent the entire
population while the systematic random sampling was used in the management of as it is not
possible to get presentation of the all dairy’s management.

3.4 Data analysis

The data collected was analyzed using tools like DFD’s, Flow charts and both the functional
and non-functional requirements of the system.

10
 CHAPTER FOUR

SYSTEM ANALYSIS AND REQUIREMENT MODELING

4.0 SYSTEM ANALYSIS

The primary goal of the system analysis is to improve the efficiency of the existing system. For that the
study of specification of the requirements is very essential. For the development of the new system, a
preliminary survey of the existing system will be conducted. Investigation done whether the up gradation
of the system into an application program could solve the problems and eradicate the inefficiency of the
existing system.

4.0.1 FEASIBILITY STUDY

The initial investigation points to the question whether the project is feasible. A feasibility is conducted to
identify the best system that meets the all the requirements. This includes an identification description, an
evaluation of the proposed systems and selection of the best system for the job. The requirements of the
system are specified with a set of constraints such as system objectives and the description of the out puts.
It is then duty of the analyst to evaluate the feasibility of the proposed system to generate the above
results. Three key factors are to be considered during the feasibility study:

4.0.2 OPERATION FEASIBILITY

An estimate should be made to determine how much effort and care will go into the developing of the
system including the training to be given to the user. Usually, people are reluctant to changes that come in
their progression. The computer initialization will certainly affected the turn over, transfer and employee
job status. Hence an additional effort is to be made to train and educate the users on the new way of the
system.

11
4.0.3 TECHNICAL FEASIBILITY

The main consideration is to be given to the study of available resources of the organization
where the system is to be implemented. Here the system analyst evaluates the technical merits of
the system giving emphasis on the performance, Reliability, maintainability and productivity. By
taking the consideration before developing the proposed system, the resources availability of the
organization was studied. The organization was immense computer facilities equipped with
sophisticated machines and the software hence this technically feasible.

4.0.4 ECONOMIC FEASIBILITY

Economic feasibility is the most important and frequently used method for evaluating the
effectiveness of the proposed system. It is very essential because the main goal of the proposed
system is to have economically better result along with increased efficiency. Cost benefit analysis
is usually performed for this purpose. It is the comparative study of the cost verses the benefit
and savings that are expected from the proposed system. Since the organization is well equipped
with the required hard ware, the project was found to be economically.
4.0.5 SYSTEM SPECIFICATION
Hardware Requirements
Processor : Intel Pentium IV

Ram : 512 MB

Hard Disk : 80GB HDD

Software Requirements

Operating System : windows XP / Vista /Windows7/8/10

Data Base : MS Access

Application Software : Microsoft Office 2003/2007/2010/2013/2019

12
4.2 SYSTEM DESIGN

System design is the solution to the creation of a new system. This phase is composed of several
systems. This phase focuses on the detailed implementation of the feasible system. It emphasis
on translating design specifications to performance specification. System design has two phases
of development logical and physical design.

During logical design phase the analyst describes inputs (sources), out puts (destinations),
databases (data sores) and procedures (data flows) all in a format that meats the uses
requirements. The analyst also specifies the user needs and at a level that virtually determines the
information flow into and out of the system and the data resources. Here the logical design is
done through data flow diagrams and database design.

The physical design is followed by physical design or coding. Physical design produces the
working system by defining the design specifications, which tell the programmers exactly what
the candidate system must do.

The programmers write the necessary programs that accept input from the user, perform
necessary processing on accepted data through call and produce the required report on a hard
copy or display it on the screen.

4.2.0 LOGICAL DESIGN

Logical design of an information system shows the major features and also how they are related
to one another. The first step of the system design is to design logical design elements. This is the
most creative and challenging phase and important too. Design of proposed system produces the
details of the state how the system will meet the requirements identified during the system
analysis that is, in the design phase, we have to find how to solve the difficulties faced by the
existing system. The logical design of the proposed system should include the details that
contain how the solutions can be implemented. It also specifies how the database is to be built for
storing and retrieving data, what kind of reports are to be created, and what the inputs to be given
to the system are. The logical design includes input design, output design, and database design
and physical design.

13
4.2.1 INPUT DESIGN

The input design is the link between the information system and the user. It comprises the
developing specification and procedures for data preparation and those steps are necessary to put
transaction data into a usable form for processing data entry. The activity of putting data into the
computer for processing can be achieved by inspecting the computer to read data from a written
or printed document or it can occur by having people keying the data directly into the system.
The design of input focuses on controlling the amount of input required, controlling errors,
avoiding delay, avoiding extra steps and keeping the process simple.

The system needs the data regarding the asset items, depreciation rates, asset transfer, physical
verification for various validation, checking, calculation and report generation. The error raising
method is also included in the software, which helps to raise error message while wrong entry of
input is done. So in input design the following things are considered.

What data should be given as input?

 How the data should be arranged or coded?

 The dialogue to guide the operating personnel in providing input.

 Methods for preparing input validations and steps to follow when error occur

 The samples of screen layout are given in the appendix.

4.2.2 OUTPUT DESIGN

Computer output is the most important and direct information source to the user. Output design
is a process that involves designing necessary outputs in the form of reports that should be given
to the users according to the requirements. Efficient, intelligible output design should improve
the system's relationship with the user and help in decision making. Since the reports are
directing referred by the management for taking decisions and to draw conclusions they must be
designed with almost care and the details in the reports must be simple, descriptive and clear to
the user. So while designing output the following things are to be considered.

14
  Determine what information to present
 Arrange the presentation of information in an acceptable format
 Decide how to distribute the output to intended receipts

Depending on the nature and future use of output required, they can be displayed on the monitor
for immediate need and for obtaining the hardcopy. The options for the output reports are given
in the appendix.

4.2.3 PHYSICAL DESIGN

The process of developing the program software is referred to as physical design. We have to
design the process by identifying reports and the other outputs the system will produce. Coding
the program for each module with its logic is performed in this step. Proper software
specification is also done in this step.

4.2.4 MODULAR DESIGN

A software system is always divided into several sub systems that makes it easier for the
development. A software system that is structured into several subsystems makes it easy for the
development and testing. The different subsystems are known as the modules and the process of
dividing an entire system into subsystems is known as modularization or decomposition.

A system cannot be decomposed into several subsystems in any way. There must some logical
barrier, which facilitates the separation of each module. The separation must be simple but yet
must be effective so that the development is not affected.

The system under consideration has been divided into several modules taking in consideration
the above-mentioned criteria. The different modules are

1. Sales details

2. Login module

3. Employee Details

4. Stock Module

15
4.2.5 DATABASE DESIGN

The overall objective in the development of database technology has been to treat data as an
organizational resource and as an integrated whole. DBMS allow data to be protected and
organized separately from other resources. Database is an integrated collection of data. The most
significant form of data as seen by the programmers is data as stored on the direct access storage
devices. This is the difference between logical and physical data.

Database files are the key source of information into the system. It is the process of designing
database files, which are the key source of information to the system.

The files should be properly designed and planned for collection, accumulation, editing and
retrieving the required information.

The organization of data in database aims to achieve three major objectives: -

• Data integration

• Data integrity

• Data independence

The proposed system stores the information relevant for processing in the MS Access database.
This database contains tables, where each table corresponds to one particular type of
information. Each piece of information in table is called a field or column. A table also contains
records, which is a set of fields.

All records in a table have the same set of fields with different information.

There are primary key fields that uniquely identify a record in a table. There are also fields that
contain primary key from another table called foreign keys.

4.4 SYSTEM CODING

The goal of the coding phase is to translate the design. The aim in this phase is to implement the
design in the best possible manner. Well known code can reduce the testing and maintenance
effort. During coding, the focus should on developing programs that are easy to read and
understand and not simply on developing the programs that are easy to write. Simplicity and
clarity should be strived for during the code phase. An important concept that helps the
understandability of the programs is structured programming.

16
 The program that should be organized as a sequence of statements and during execution of the
statements is executed in the sequence given in the program. There are many different criteria for
judging of the program, execution time and required memory.

4.5 SYSTEM TESTING

System testing is a critical aspect of Software Quality Assurance and represents the ultimate
review of specification, design and coding. Testing is a process of executing a program with the
intent of finding an error. A good test is one that has a probability of finding an as yet
undiscovered error. The purpose of testing is to identify and correct bugs in the developed
system. Nothing is complete without testing. Testing is the vital to the success of the system.

In the code testing the logic of the developed system is tested. For this every module of the
program is executed to find an error. To perform specification test, the examination of the
specifications states what the program should do and how it should perform under various
conditions. Unit testing focuses first on the modules in the proposed system to locate errors. This
enables to detect errors in the coding and logic that are contained within that module alone.
Those resulting from the interaction between modules are initially avoided. In unit testing step
each module has to be checked separately.

System testing does not test the software as a whole, but rather than integration of each module
in the system. The primary concern is the compatibility of individual modules. One has to find
areas where modules have been designed with different specifications of data lengths, type and
data element name. Testing and validation are the most important steps after the implementation
of the developed system. The system testing is performed to ensure that there are no errors in the

Implemented system. The software must be executed several times in order to find out the errors
in the different modules of the system.

Validation refers to the process of using the new software for the developed system in a live
environment i.e., new software inside the organization, in order to find out the errors. The
validation phase reveals the failures and the bugs in the developed system. It will be come to
know about the practical difficulties the system faces when operated in the true environment. By
testing the code of the implemented software, the logic of the program can be examined. A
specification test is conducted to check whether the specifications stating the program are
performing under various conditions.

17
Apart from these tests, there are some special tests conducted which are given below:

Peak Load Tests: This determines whether the new system will handle the volume of activities when
the system is at the peak of its processing demand. The test has revealed that the new software for the
agency is capable of handling the demands at the peak time.

Storage Testing: This determines the capacity of the new system to store transaction data on a disk or
on other files. The proposed software has the required storage space available, because of the use of a
number of hard disks.

Performance Time Testing: This test determines the length of the time used by the system to process
transaction data.

In this phase the software developed Testing is exercising the software to uncover errors and ensure
the system meets defined requirements. Testing may be done at 4 levels

1 Unit Level

2 Module Level

3 Integration & System

4 Regression

1. UNIT TESTING

A Unit corresponds to a screen /form in the package. Unit testing focuses on verification of the
corresponding class or Screen. This testing includes testing of control paths, interfaces, local data
structures, logical decisions, boundary conditions, and error handling. Unit testing may use Test
Drivers, which are control programs to co-ordinate test case inputs and outputs, and Test stubs,
which replace low-level modules. A stub is a dummy subprogram.

2. MODULE LEVEL TESTING

Module Testing is done using the test cases prepared earlier. Module is defined during the time of
design.

3. INTEGRATION & SYSTEM TESTING

Integration testing is used to verify the combining of the software modules. Integration testing
addresses the issues associated with the dual problems of verification and program construction.

18
 System testing is used to verify, whether the developed system meets the requirements.

4. REGRESSION TESTING

Each modification in software impacts unmodified areas, which results serious injuries to that
software. So the process of re-testing for rectification of errors due to modification is known as
regression testing.

Installation and Delivery:

Installation and Delivery is the process of delivering the developed and tested software to the
customer.

Acceptance and Project Closure:

Acceptance is the part of the project by which the customer accepts the product. This will be
done as per the Project Closure, once the customer accepts the product; closure of the project is
started. This includes metrics collection, PCD, etc.

4.6 SYSTEM IMPLEMENTATION

Implementation includes all those activities that take place to convert from the old system to the
new. The old system consists of manual operations, which is operated in a very different manner
from the proposed new system. A proper implementation is essential to provide a reliable system
to meet the requirements of the organizations. An improper installation may affect the success of
the computerized system.

Implementation methods:

There are several methods for handling the implementation and the consequent conversion from
the old to the new computerized system.

The most secure method for conversion from the old system to the new system is to run the old
and new system in parallel. In this approach, a person may operate in the manual older
processing system as well as start operating the new computerized system. This method offers
high security, because even if there is a flaw in the computerized system, we can depend upon
the manual system. However, the cost for maintaining two systems in parallel is very high. This
outweighs its benefits.

19
Another commonly method is a direct cut over from the existing manual system to the
computerized system. The change may be within a week or a day. There are no parallel
activities. However, there is no remedy in case of a problem. This strategy requires careful
planning.

A working version of the system can also be implemented in one part of the organization
department and the personnel will be piloting the system and changes can be made as and when
required. But this method is less preferable due to the loss of entirety of the system.

IMPLEMENTATION PLAN:

The implementation plan includes a description of all the activities that must occur to implement
the new system and to put it into operation. It identifies the personnel responsible for the
activities and prepares a time chart for implementing the system.

The implementation plan consists of the following steps.

List all files required for implementation.

 Identify all data required to build new files during the implementation.
 List all new documents and procedures that go into the new system.
The implementation plan should anticipate possible problems and must be able to deal with
them. The usual problems may be missing documents; mixed data formats between current and
files, errors in data translation, missing data etc.

20
DATA FLOW DIAGRAM

The following dataflow diagrams show the control of flow in our system.

Figure 2.0: Control of Flow Information

System display list of suppliers

Customer Details

System Users

Milk Brought
Employee

Suppliers
Daily
Customer management
System

Sales

Salary payment

Customer Details

21
Figure 3.0: Below shows the Control Flow of Suppliers Information.

Supplier

K M N
L

DMS Storage

This is the description of the figure above

K- Daily management System displays the lists of suppliers

L- Suppliers provide his details to the Daily management system
M- Daily management System registers the record of customer and suppliers
N- Supplier has the Daily Management system to supply milk

22
 Figure 4.0: Control of Flow of Milk Information

Milk Information

A B C D

DMIS Storage

This is the description of the figure above.

A- The milk quantity is on the system display.

B- Milk is registered in the Daily Management System.

C- Milk suppliers provide their details to Daily Management System.

D- Daily Management System display records of Milk

23
 CHAPTER FIVE
DATA PRESENTATION AND ANAYSIS

Figure 5.0: Login Screen

24
Figure 6.0: Milk and Dairy Products Sales Screen

Figure7.0: Dairy Products Stocking Screen

25
Figure 8.0: Employee Registration

Figure 9.0: Supplier details

26
Figure 10.0: Suppliers payment

Figure 11.0: Employee Payment

27
Figure 12.0: Daily working attendance

Figure 13.0: Daily Sales Report

28
 CHAPTER SIX

CONCLUSION, RECOMMENDATION AND REFERENCES

6.0 CONCLUSION

The system has been developed with much care that it is free of errors and at the same time it is
efficient and less time consuming. The important thing is that the system is robust. Allows only
authenticated users .It was developed using the phases of software development cycle. So the
system is accurate, timely and eliminates the use of papers

6.1 RECOMMENDATIONS

The current system developed is in accordance with the request that has been provided by the
organization. On regarding the future enhancement, the application can further be expanded in
accordance with changing organizational needs. Since the change in testing and user needs arises
frequently in certain short intervals of time, the system can be further upgraded to meet the
requirements that may arise in the far or near future. With regarding to the needs that arises,
more and more features can be included by adding it as separate modules and integrated with the
existing system.

29
REFERENCES

Websites
 http://www.codeproject.com
 http://www.msdn.com.
 http://www.vb123.com
 http://www.vbcode.com
 http://www.sqltuner.com
Books

1. Whitten & Bentley, 2007, Systems analysis and design methods, 7th edition, McGraw-
Hill
, chap3
2. Whitten & Bentley, 2007, Systems analysis and design methods, 7th edition,
McGraw- Hill,chap.1
3. Saint JOSEPH Computer learning Center (System Analysis & Design e- Book) page

30
31