INTRODUCTION:

1.1 An overall view of an existing

system:

A tea-estate ,as a general ,mainly

functions basing on its production
system. Again there has always been a
general infrastructure into which all
tea-estate production system fits well.
1
 The overall plucking in tea-gardens in a
particular season ‘its weathering ,cutting,
grafting and curling , then oxidation ,separation
followed by standard gradation process and at
last packing and dispatching is almost the same
process irrespective of the different tea-
estates and their individual management
schemes.

2
AIM OF THE PROJECT:

AUTOMATED TEA ESTATE PRODUCTION

INFORMATION SYSTEM (ATEPIS) aims to
develop a software platform which automates
the maintenance of the daily information
about the yea production in a particular tea
industry .

3
The software developed aims to achieve the
following features:-

1.Ensure easy access to the data stored.

2.Inputting, processing and outputting data

should be handled efficiency.

3. Must work in an inter-related frame work for a

verity of operations like entry of collection,
amount of tea production and their respective
dispatched.
4
4.Must generate error detection signals and
also resist maximum error prone situations.

5.Provide an easy-to-understand inter face for

the user group.

6.Provide step- by-step ”update of table”

mechanism.

7.Avoid redundant data stores and clashes.

8.The security and durability of data entered.

5
 RECOGNITION OF NEED:

 Automated systems are a great success over

a vast field of industrial development these
days. This success has been achieved through
last two decades by highlighting only two features
of database software, namely :-

i) rapid storing and processing of data and on

demand producing the result and ii) security and
error correction schemes.
6
 As a contrast regular worker or
staff dependent manual systems are quite
regularly subjected to problematic situations
due to mechanical reasons , poor infrastructure
and humane errors accompanied by natural and
political circumstances.
In designing the present system
(ATEPIS), we have taken up the production unit
of the famous “Dewan Group of Tea Industries”
as a case study.

7
 SYSTEM ANALYSIS:
 COST ESTIMATION:

DIFFERENT TYPES OF COSTS:

a) HARDWARE COST.
b) PERSONNEL COST.
c) FACILITY COST.
d) OPERATING COST
e) SUPPLY COST.
8
 BROADER CLASSIFICATION OF COSTS:

TANGIBLE : Costs which can be easily measured .

INTANGIBLE: Those that have financial values not
easily measured .
DIRECT :Whose amount can be correctly predicted.
INDIRECT :These are not directly associated with a
given system.
FIXED AND VARIABLE: They are proportional to the
work volume .

9
 FEASIBILITY STUDY:

A feasibility study is conducted to select the best

system that meets performance requirements .This
entails an identification description, an evaluation of the
candidate systems, and the selection of the best system
for the job.
Three key considerations are involved in feasibility
analysis: Economic, technical and behavioral.

10
 ECONOMIC FEASIBILITY: Economic feasibility is
the most commonly used method for evaluating the
effectiveness of a candidate system.

 TECHNICAL FEASIBILITY: Technical feasibility

centers on the existing computer system and to what
extent it can support the proposed addition

 BEHAVIORAL FEASIBILITY: People are inherently

resistant to change and computers have been known to
facilitate change

11
DATA FLOW DIAGRAM

It is a practical graphical representation of a

system and clarifies the system requirements
and identifies the major transformations that
will become program in system design.

12
Data Flow Diagram

Edit Raw material

Green leaf collection register

Sorting
Separation Dryer mouth
register Edit total
Tea made
Bin card Grading
record process Packing
process

Daily account
(R.G.1)
Packed card
record
Dispatch
Dispatch
process tea packed
Dispatch
register tea 13
ER DIAGRAM

 An E-R diagram expresses the overall logical

structure of a database. They are simple and clear.

14
E-R diagram
Sl.no Net wt
date
Quantity used Sl no
1 1
Green Tea made
Green leaf
leaf Used in
Quantity
destroyed 1
Quantity Sl no
Quantity home use
received
despatched Export under entry made in
duty
From own Export under
Division quantity
division bond
name
1
Division 1
quantity
name Daily account 1

n
bin card despatch
grading
Lot no
grade 1
No of bags n
Used in

1 size of bags packed account

receipt remove
Packed card

date of
packages despatch
receipt
grade remove
15
 NORMALIZATION:

CONCEPTS OF:

 SUPERKEY: A set of attributes S in a relational

schema R ,R ={A1,A2,A3……}, such that no
two tuples t1 and t2 in a legal state r have the
property t1[S]=t2[S].

 CANDIDATE KEY: If a schema has more than

one key , each is called a candidate key.
16
 PRIMARY KEY: Any key is arbitrarily designated as
the primary key and others as the secondary key.

 FOREIGN KEY: A primary key of one relation

referred in another .

 PRIME ATTRIBUTE: Any member of a candidate key

and others are non prime.

17
 FUNCTIONAL DEPENDENCY: It specifies a
constraint on all possible tuples that can for the
relation r of R, the constraint is that for the
dependency X Y, if t1 and t2 are two tuples than
if t1[X]=t2[X] , then they must also have
t1[Y]=t2[Y].

 FULL FUNCTIONAL DEPENDENCY: A

functional dependency X Y is full if removal of
any attribute from X means that the dependency
does not hold any more.

18
 NORMALIZATION: The process of minimizing
redundancy and insertion, deletion and update anomalies
based upon the functional dependency and the primary
keys.

19
TYPES OF NORMAL FORMS:

 1NF: It says relations should not have non atomic

attributes or nested relations.

 2NF:It says every nonprime attribute should be

fully functionally dependent on the primary key.

20
 3NF:It says the relation should satisfy 2NF and no non
prime attribute should be transitively dependent on the
primary key.

 BCNF: A relational scheme is in BCNF if a non

trivial functional dependency X A holds in R and
X is a super key of R.

21
NORMALIZATION OF THE
RELATIONAL SCHEMAS:

 1).RAW MATERIAL :- {sl no, received (div name,

qty), dispatched (div name, qty send), qty used, qty
destroyed}

22
 Functional dependency:
{ sl no} {qty used, qty destroyed}

{sl no, div name} {qty}

{ sl no, div name} {qty}

Tables of first normal form:

a) Main Row Table={sl no, qty used, qty destroyed}
b) Received Row={sl no, div name, qty}
c) Dispatched Row={ sl no, div name, qty sent}

23
 2) Tea made:- { sl no, net wt}
Functional Dependency:-
{ sl no} {net wt}

 3) Daily Stock Account :- { sl no., hu, eud, eub}

Functional Dependency:-
{sl no} {hu,eud,eub}

24
 4) Grading Record :- { sl no., grade , recpt, rem}
Functional Dependency:-
{sl no, grade} { recpt, rem }

 5) Packing process :- { sl no, grade , recpt, rem}

Functional Dependency:-
{sl no., grade } { recpt, rem }

25
 6)Main Dispatch Record:-{lt no , slp, nob, sop,
grade, dod , dest, cons,
gwpb}
Functional Dependency:-
{ Lt no } {nob, sop, dod , dest, cons}
{slp } { grades, gwpb }

 Tables of second normal form:-

Main Dispatch Register 1:{ lt no,nob, sop,dod

dest,cons}
Main dispatch register 2:{ lt no, slp ,grade,gwpb}
26
 SYSTEM MODULES:

 Modularity, as the term itself indicates, means

viewing the overall system as a collection of
independent but interrelated blocks known as
modules. Modules not only make the overall
system viewing easier, but also it makes the
system design simpler and less error prone.

27
 we can divide the whole system as four basic
modules listed and described below:

 1.Green Leaf Record:

This module provide information about the
green leaf collected from different divisions,
green leaf dispatched to different divisions, the
amount of green leaf sent to the factory for
processing, the little amount destroyed due to any
reason and the balance amount left.

28
29
 2.Daily Stock Record:

This module contain how much quantity

of tea made is the present balance for a day.

30
31
32
 3. Grading Record:

This module access the available tea made

as data from the earlier Daily Stock Record module.
It mainly contains the quantity receipt, quantity
removal and the balance quantity for each grade.

33
34
35
 4. Packing of tea:

This module is almost similar to the

earlier one and also access data from Grading
Record module. This module mainly contains the
grade wise packing details containing the
quantity receipt, quantity removal, and balance
left.

36
37
38
 5.Dispatch Record:
The packet tea made are dispatched in
lots while a particular lot contain all the
necessary information about it along with
the details about the packages of the lot.
This module provide all this information.

39
40
Tables of second normal form:-

Main Dispatch Register 1:{ lt no,nob,

sop,dod
dest,cons}

Main dispatch register 2:{slp,grade,gwpb}

41
 SYSTEM TESTING

 No system is ever perfect. Communication

problem ,programmer’s negligence ,or time
constraints create error that must be
eliminated before the system is ready for user
acceptance testing.

42
 TYPES OF TESTING:

 Program testing:

A program represents a logical elements of a

system. Program testing Checks two types of errors:
logical and syntax error.

43
 String testing:

Programs are invariably related to one another and

interact in a total system. Each program is tested to see
whether it conforms to related programs in the system.

 System testing:

System testing is designed to uncover

weakness that were not found in earlier test.

44
 System documentation:

All design and test documentation

should be finalized and entered in the library for
future reference. The library is the central location
for maintenance of the system .

 User acceptance testing:

An acceptance test has the objective of

selling user on the validity and reliability of the
system

45
IMPLEMENTATION:

A process of converting a new or a revised

system design into an operational one .

46
There are three types of implementations:

1.Implementation of a new computer system to

replace an existing one.

2.Implementation of a modified application to

replace an existing one, using the same
computer.

3.Implementation of a computer system to

replace a manual system.

47
 POST IMPLEMENTATION REVIEW:

 A post-implementation review is an evaluation of

a system in terms of the extent to which the
system accomplishes stated objectives and actual
project costs exceed initial estimates.

 Unlike system testing ,which determines where

the system fails so that the necessary
adjustments can be made ,a post implementation
review determines how well the system continues
to meet performance specification. 48
 SOFTWARE MAINTENANCE:

 Maintenance is the enigma of system development.

It holds the software industry captive , tying up
programming resource. Maintenance accounts for
50-80 percents of total system development.
There are several problems :-

 1.Maintenance is not as rewarding as exciting as

developing system. It is perceived as requiring
neither skill nor experience.
49
 2.Users are not fully cognizant of the
maintenance problem or its high cost.

 3.Few tools and techniques are available for

maintenance.

 4.A good test plan is lacking.

 5.There are minimal standards for maintenance.

50
 CONCLUSION:

 ATEPIS is database software which has been

designed taking Dewan group of tea industries as
a case study to cater efficient data storage
smoother processing and user friendly data
retrieval processes. However the software is in
no way limited to functioning in that particular
tea estate only. In fact, it can be used by any
tea estate that operates under the same
production system.

51
 No software can ever demand to be completely
self complete and independent without requiring
any future modification. In ATEPIS also, there
are many provisions to incorporate further
modifications or future tie up with a variety of
other softwares to provide an excellent service
over the long run.

52
Some of the future works that might be done are
listed below:-

 A separate module to keep track of the

government’s taxes and other information relating
the duties can be added to the project.

 ATEPIS can be linked to the software which is

used to maintain the accounts section of a tea
estate so that the production section can directly
access the billing details.

53
 The software can be integrated through several
new tables and data stores to produce more
detailed reports.

 A World Wide Web form can be designed and

implemented so that various tea gardens can
access the information about each others status.

54