CENTRAL IT COLLEGE GUWAHATI

AUTHORIZED UNDER

CENTER CODE 01729

SIKKIM MANIPAL UNIVERSITY

Gangtok-737102

A PROJECT SYNOPSIS ON
FLOWER DISTRIBUTION MANAGEMENT SYSTEM BY

SHAHIN AKHTAR HUSSAIN

Submitted in partial fulfillment for the award of the degree of BACHELOR OF COMPUTER APPLICATION UNDER

Sikkim Manipal University

TITLE OF THE PROJECT

FLOWER DISTRIBUTION MANAGEMENT SYSTEM

INTRODUCTION

Zopar Exports Pvt. Ltd. is a Bangalore based floriculture ISO certified company having its branch offices all over all the satellite cities of India. The Guwahati branch is situated at Ulubari in Guwahati. Zopar Exports Pvt. Ltd. is engaged primarily in production and marketing of exotic floriculture products in India. ZOPAR is a Mizo word which means Flowers of the Hills. The system study focuses on the stage of the development of a system. The system analysis is given a system development project meaning and direction. A candidate system is approached after the analysis has a thorough understanding of user needs and problems. Then the analysts developed a solution to these problems and communicate the solution through the installation of a candidate system.

OBJECTIVES OF THE PROPOSED SYSTEM

The objectives of Flower Distribution Management System are :

To automate the complete operation. To fasten up the data processing speed. Simplification of the searching procedure. Efficient and easy management of the distributor. Maintain integrity of data. Store data with minimal redundancy. Maintain daily transactional reports.

SOFTWARE AND HARDWARE SPECIFICATION

SOFTWARE SPECIFICATION: OPERATING SYSTEM FRONT-END BACK-END Microsoft Office tools : :

Windows 7 Ultimate Visual Basic.Net : MySQL Server

HARDWARE SPECIFICATION: PROCESSOR RAM HARD DISK MONITOR KEYBOARD MOUSE PRINTER

:
: : : : : :

Core 2 Duo processor 2 GB RAM 250 GB hard disk Normal Normal Normal Inkjet

REQUIREMENT ANALYSIS

Introduction:

Requirement Analysis is the first step in the system development life cycle. This requirement emphasizes on the identification of need. This is a user request to change, improve or automated existing system. During the preparation of the initial information has to receive from users, managers and system developers. This helps in defining what the new system should do. The objective is to decide whether the request is valid and feasible.

Objective:

To fasten up the data processing speed.

Store the data with minimal redundancy. Simplification of the searching procedure.

Efficient and easy management of the distributor.

Maintain integrity of data.

Structure Chart:

A structure chart is a top-down modular design tool, constructed of squares representing the different modules in the system, and lines that connect them. The

lines represent the connection and or ownership between activities and sub activities as they are used in organization charts.

STRUCTURE CHART

FLOWER DISTRIBUTION MANAGEMENT SYSTEM

FLOWER

BOOKING

ORDER

PURCHASE

TYPES COLOUR

MODULE DESCRIPTION

 FLOWER: This is the main module of operation of the system and all the other

modules are its successors. This module contains variety of flowers with different colors.
BOOKING: Booking module covers the process of booking flowers by the

customer according to their requirements.

ORDER: As the name suggests this module is associated with placing order to

the supplier by the manager to meet the demand of the customer.

PURCHASE: This module is concerned with the process of receiving flowers

and making payment against the flower by the customer.

CONTEXT DIAGRAM
Context diagrams are related to Data Flow Diagram, and show the interactions between a system and other actors with which the system is designed to interface. Context diagrams can be helpful in understanding the context which the system will be part of.
FLOWER DISTRIBUTION MANAGEMENT SYSTEM

CUSTOMER

QUERY FOR TYPES AND COLOURS OF FLOWER

GET THE QUERY FOR TYPES AND COLOURS OF FLOWER GETS CUSTOMERS BOOKING DETAILS

MAKE BOOKING FOR FLOWER

PLACE ORDER FOR FLOWER MAKE PURCHASE FOR FLOWER GETS PAYMENT FOR FLOWER

MANAGES DIFFERENT TYPES AND COLOURS

OF FLOWER

MANAGER

GENERATE RECEIPT PROVIDE FLOWERS AGAINST THE PLACE ORDER PAYMENT RECEIPT

BOOKING DETAILS

COLLECTS FLOWER AGAINST THE PLACE ORDER

GETS THE TYPES AND COLOURS OF FLOWERS

GENERATE BOOKING FOR CUSTOMERS

DATA FLOW DIAGRAM (DEFINITION):

Data Flow Diagram was developed by Larry Constantine for expressing system requirements. A DFD or bubble chart is used to depict the data flow taking place in the system. This helps to understand what activities make up the system, what data enters and what leaves the system.

GETS PLACE ORDER

SUPPLIER

A DFD is a graphical tool which provides a mechanism for functional modeling as well as information flow modeling.

DFD symbols:

A PRODUCER OR CONSUMER OF INFORMATION

A TRANSFORMER OF INFORMATION (PROCESS)

DIRECTION OF DATA FLOW

STORAGE OF INFORMATION

1ST LEVEL DFD FOR FLOWER DISTRIBUTION MANAGEMENT SYSTEM

RETRIEVE ORDERED FLOWER DETAILS STORE FLOWER PROCESS 1.0 STORE FLOWER DETAILS

FLOWER DETAILS

MANAGE FLOWERS GETS THE QUERY FOR FLOWER

MANAGER

QUERY FOR FLOWERS

CUSTOMER
GETS FLOWER INFORMATION

QUERY FOR TYPES & COLOUR PROCESS 2.0

RETRIEVE FLOWER DETAILS

STORE CATEGORY DETAILS

CATEGORY DETAILS
RETRIEVE CATEGORY DETAILS GETS CUSTOMERS BOOKING DETAILS MAKE BOOKING FOR FLOWER BOOKING PROCESS 3.0 RETRIEVE FLOWER DETAILS STORE BOOKING DETAILS

GETS BOOKING DETAILS

BOOKING DETAILS
RETRIEVE BOOKING DETAILS

GETS THE PLACE ORDER FOR FLOWER

MAKES PLACE ORDER FOR FLOWER

SUPPLIER

PLACE ORDER PROCESS 4.0

STORE PLACE

PLACE ORDER DETAILS

ORDER DETAILS

PROVIDES FLOWER AGAINST PLACE ORDER

RETRIEVE BOOKING DETAILS

PROVIDES FLOWER MAKES PAYMENT PURCHASE PROCESS 5.0 GETS THE FLOWERS

PURCHASE DETAILS
STORE PURCHASE DETAILS

RETRIEVE PURCHASE DETAILS

GETS RECEIPT AGAINST PURCHASING THE FLOWERS

GENERATE RECEIPT RECEIPT PROCESS 6.0

2nd LEVEL DFD FOR QUERY FOR TYPES AND COLOURS

TYPES OF FLOWER 2.1

STORE FLOWER DETAILS FLOWER DETAILS

RETRIVE TYPES OF FLOWER CATEGORY DETAILS

RETRIEVE COLOURS OF FLOWER

COLOURS OF FLOWER 2.2

STORE FLOWER COLOURS DETAIL

GETS THE QUERY FOR FLOWER QUERY FOR FLOWER TYPES FLOWER INFORMATION 2.3

CUSTOMER
GET FLOWER DETAILS

MANAGER
PROVIDES FLOWER DETAILS RETRIEVE FLOWER DETAILS

ENTITY RELATIONSHIP DIAGRAM (DEFINITION):

Data objects are connected to each other in various ways. Object relationship is the cornerstone of any data model.This is represented graphically using ER Diagram. It was proposed by Peter Chen for design of relational database system. A set of primary components are identified for the ER diagram, Data objects, attributes, relationships and various type indicators. The primary purpose of ER diagram is to represent objects and their relationships.

The major components of an ER diagram are:

REPRESENT AN ENTITY

REPRESENT AN ATTRIBUTE

REPRESENT KEY ATTRIBUTE

..

REPRESENT DERIVED ATTRIBUTE

REPRESENT RELATIONSHIP

REPRESENT CARDINALITY

LINKS ATTRIBUTE WITH ENTITY AND ENTITY WITH RELATIONSHIP

ER DIAGRAM

F_TYPE F_NAME SL_NO B_NO

B_DATE

B_ADD

QNTY

M
AGAINST

FLOWER

BOOKING
M

ITEMS
F_COLOUR

SL_NO

HAS

D_O_PAY AMNT

R_NO

P_NO M M

P_DATE

1
RECEIPT
M

ON

PURCHASE

P_NO

AMNT

B_NO

GET

C_ID

C_NAME

1
R_NO

BYLN_NO

CUSTOMER

PHN_NO

STATE

DIST

BYLN_NAME Data Dictionary

A data dictionary is a collection of descriptions of the data objects or items in a data model for the benefit of programmers and others who need to refer to them. A data dictionary has many advantages. The most obvious is documentation; it serves as a store of organization information which can link analysis, design, implementation and evaluation. New information will be added to it. All information about the entity is kept on side. Data Dictionary of FLOWER DISTRIBUTOR MANAGEMENT SYSTEM:

SL_NO

FIELD NAME AMNT AMNT B_ADD B_DATE B_NO BYLN_NAME BYLN_NO C_ID C_NAME DIST D_O_PAY F_COLOUR F_NAME F_TYPE ITEM P_DATE PHN_NO P_NO QNTY R_NO

DATA TYPE INTEGER INTEGER VARCHAR DATE INTEGER VARCHAR INTEGER INTEGER VARCHAR VARCHAR DATE VARCHAR VARCHAR VARCHAR VARCHAR DATE INTEGER INTEGER INTEGER INTEGER

DESCRIPTION PURCHASE AMOUNT/COST RECEIPT AMOUNT CUSTOMERS BOOKING ADDRESS BOOKING DATE BOOKING NUMBER CUSTOMERS BYELANE NAME CUSTOMERS BYELANE NUMBER CUSTOMERS IDENTITY NUMBER CUSTOMERS NAME CUSTOMERS DISTRICT DATE OF PAYMENT COLOURS OF FLOWER FLOWERS NAME FLOWERS TYPE BOOKING ITEM DATE OF PURCHASE CUSTOMERS PHONE NUMBER

SOURCE PURCHASE RECEIPT BOOKING BOOKING BOOKING CUSTOMER CUSTOMER CUSTOMER CUSTOMER CUSTOMER RECEIPT FLOWER FLOWER FLOWER BOOKING PURCHASE CUSTOMER

CONSTRAINT

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20

PRIMARY KEY

PRIMARY KEY

PURCHASE NUMBER PURCHASE ITEM QUANTITY RECEIPT NUMBER BOOKING RECEIPT

PRIMARY KEY

PRIMARY KEY

21 22

SL_NO STATE

INTEGER VARCHAR

FLOWERS SERIAL NUMBER

FLOWER

PRIMARY KEY

CUSTOMERS STATE CUSTOMER

DATABASE STRUCTURE:

Database structure is the process of producing a detailed data model of a database. This logical data model contains all the needed logical and physical design choices and physical storage parameters needed to generate a design in a Data definition language which can then be used to create a database.

TABLE STRUCTURE

TABLE NAME: FLOWER SL.NO 1 2 3 4 FIELD NAME

SL_NO F_TYPE F_NAME F_COLOUR

DATA TYPE
INTEGER VARCHAR VARCHAR VARCHAR

KEY
PRIMARY KEY 20 25 25 20

SIZE

TABLE NAME: BOOKING

SL.NO FIELD NAME 1 2 3 4 5 6

B_NO B_DATE B_ADD QNTY ITEMS SL_NO

DATA TYPE
INTEGER DATE VARCHAR INTEGER VARCHAR INTEGER

KEY
PRIMARY KEY

SIZE
20 15 20 20 20

FOREIGN KEY

20

TABLE NAME: PURCHASE SL.NO FIELD NAME 1 2 3 4

P_NO P_DATE AMNT B_NO

DATA TYPE
INTEGER DATE INTEGER INTEGER

KEY
PRIMARY KEY

SIZE
20 15 20

FOREIGN KEY

20

TABLE NAME: RECEIPT SL.NO 1 2 FIELD NAME

R_NO D_O_PAY

DATA TYPE
INTEGER DATE

KEY
PRIMARY KEY

SIZE
20 15

3 4

AMNT P_NO

INTEGER INTEGER FOREIGN KEY

15 20

TABLE NAME: CUSTOMER SL.NO FIELD NAME C_ID C_NAME BYLN_NO BYLN_NAME DIST STATE PHN_NO R_NO DATA TYPE INTEGER VARCHAR INTEGER VARCHAR VARCHAR VARCHAR INTEGER INTEGER FOREIGN KEY KEY SIZE

1 2 3 4 5 6 7 8

PRIMARY KEY 20 25 20 20 20 20 15 15

TESTING PROCEDURE: The system should always be tested thoroughly before implementation of it as regard to the individual programs, the system as a whole, user acceptance etc. This is because implementing a new system is a major job that requires a lot of man-hour and other resources. So an error not detected before implementation may cost a lot. Effectively testing early in the process translates directly into long term cost saving from a reduced number of errors. The purpose of the system testing is to consider all the likely variations to which it will be subjected and then push the system to its limits. It is a tedious but necessary step in system development. The different types of testing techniques that are used during the development of the system under consideration are as follows: Module Testing: Module testing must be carried out during the programming stage itself. Here individual program testing must be carried out during the coding stage itself and the required System Testing changes are to be made on the module to ensure the smooth

and satisfactory execution of the module in the form of an individual program and the generation of the output in the required form. 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. Each portion of the system is tested against the entire module with both test and live data before the entire system is ready to be tested. Unit Testing: Unit testing is changes made in an existing or a new program. It is necessary for the verification of the code that would be produce during the code phase. It is mainly to test the internal logic of the module. Integration Testing: In integration testing, many unit tested modules are combined into sub systems, which would be then tested. The objective if this testing is to see if the modules can be integrated properly. That is, the prime emphasis is on testing the interfaces between the modules.
SYSTEM TESTING:

The purpose of system testing is to identify and correct errors in the system. As important as this phase is, it is one that is frequently compromised. Typically the project is behind schedule or the user is easier to go directly to conversion. In system testing performance and acceptance standards are developed. Substandard performance or service interruptions that result in system failure are checked during the test. Output Testing: No system could be useful if it does not produce required format. It includes asking the user about the required format of the output that would be displayed on screen or in a printed form. User Acceptance Testing: An acceptance test has the objective selling the user on the validity and reliability of the system. It verifies that the systems procedures operate to system specifications and that the integrity of the vital data is maintained, performance of an acceptance test is actually the users show. User motivation and knowledge are critical for the successful performance of the system. Then a comprehensive test report is prepared that indicates the systems tolerance, performance range, error rate and accuracy. FUTURE ENHANCEMENT

The FLOWER DISRIBUTION MANAGEMENT SYSTEM is designed and developed according to all the organizational needs as far as possible. The design of the project is done in such a manner so that the user can operate the system by using either keyboard or mouse in order to invoke command and push buttons. Menus are attached to form to serve this proposed. The menus are designed in a user-friendly manner. The data entry forms are provided with various command buttons for the ease of users. . Although the best efforts would be put in to cover every aspect of the Flower distribution management System, still due to the limited experience in software designing, some loop holes may creep into the software. But for time being, the proposed system is adequate to handle the Flower distribution management System in a proper way.