Page Number-1 Cold Chain Locator System, Group 15

Page Number-1 COLD CHAIN LOCATOR SYSTEM, GROUP 15
Certificate of Approval
This is to certify that this report of B.Tech. 7th semester, entitled “Cold Chain
Locator System” is a record of bona-fide work, carried out by Pinaki Chakraborty,
Sourish Atorthy, Utsav Dey, Spandan Ghosh under my supervision and guidance.
In my opinion, the report in its present form is in partial fulfillment of all the
requirements, as specified by the Future Institute of Engineering & Management
and as per regulations of the Maulana Abul kalam Azad University of Technology.
In fact, it has attained the standard necessary for submission. To the best of my
knowledge, the results embodied in this report, are original in nature and worthy
of incorporation in the present version of the report for B.Tech. program in
Computer Science and Engineering in the year 2017-2018.
It is understood that by this approval the undersigned does not necessarily

endorse or approve any statement made, opinion expressed or conclusion drawn
therein, but approve this for the purpose for which it is submitted.
Guide / Supervisor
Prof. Abhijit Saha

Department of Computer Science and Engineering
Future Institute of Engineering & Management
_______________________ _________________________
Examiner(s) Head of the Department
Computer Science and Engineering
Future Institute of Engineering & Management

Acknowledgement
We thank our mentor Prof. Abhijit Saha sir for his untiring guidance and his able
assistance. Without his support this project would not have seen the light of day.
We also thank our HOD Prof. Tapas Roy sir for his relentless moral support.
We also thank our seniors for rendering selfless help.
Finally and most importantly, we thank the entire faculty of CSE of FUTURE
INSTITUTE OF ENGINEERING AND MANAGEMENT for enriching us and for being
the only reason of our knowledge in a domain which was completely unknown to
us before college.
Mr. Pinaki Chakraborty _________________________________

MAKAUT Roll No. 14800114058
Mr. Sourish Atorthy _________________________________

Mr. Spandan Ghosh _________________________________

Mr. Utsav Dey _________________________________


Contents Page Number
1. Abstract ………………………………………………………………………………………..……6
2. Introduction …................................................................................................6
3. Objective………………………………………………………………………………………..…..6
4. Scope…………………………………………………………………………………………..……..7
5. Categories of perishable goods………………………………………………..………7
6. System Analysis
a. Requirement Analysis/ SRS of the Component
I. System Requirements............................................................9
II. Acceptance Criteria...............................................................10
b. Proposed System Functionality.......................................................11
7. Feasibility Analysis
a. Economic Feasibility ……………………………………………………………….12

b. Technical Feasibility ………………………………………………………………..12
c. Behavioral Feasibility ……………………………………………………………...13
d. Operational Feasibility..……………………………………………………..……14
8. Data Flow Diagrams
a. Context Diagram……………………………………………………………………15
b. Level 1 DFD ……………………………………………………………………………16
9. Entity-Relationship Diagrams…………………………………………………….……17
10. Database Tables.………………………………………………………………………….….18
11. Development…………………………………………………………………………………..19
12. Inter-module Interaction…………….………………………………………………..…19

13. Process Flow
a. Supplier side………………………………………………………………………..….19
b. Consumer side……………………………………………………………………..…20
14. Module wise description…………………………………………………………….20-29
a. Primary objectives of module Allocation(and flow chart)

b. Primary objectives of module Inventory(and flow chart)
c. Primary objectives of module Distribution(and flow chart)
15. Testing and Debugging
a. Goals and Objectives.........................................................................30

b. Statement of scope............................................................................30
c. Test Case...............................................................................................30
d. Debugging............................................................................................32
16. Implementation...........................................................................................33
17. Screenshots…………………………………………………………………………………34-49
18. Benefits…………………………………………………………………………………….……….50
19. Limitation…………………………………………………………………………….……………50
20. Glossary………………………………………………………………………………………….…51
21. Bibliography………………………………………………………………………………….....51

1. Abstract:
The project has been initiated to develop a part of the new web based inventory
management system replacing the old pen and paper based record system of
the large chain of cold storages present in the state of West Bengal, India. To
provide the basic services related to storage of various commodities viz. potato
etc., to maintain their loading and unloading details of particular cold store hirer
in the state. The product will take care of all the transactions of each cold storage.
Cold storage management information system help managers accurately
Scientific and rational allocation and use of cold storage device for more efficient
business processes, but also can help companies optimize resources, improve the
economic efficiency of enterprises.
2. Introduction:
We propose an integrated system of cold storages (referred to as a cold

chain).All the cold storages forming the cold chain would be interlinked via the
software we are making. The user would place an order through our portal and
we shall allocate the goods to the cold storage by minimizing the total cost of
storage and transportation. We shall also offer the facility of selling the stored
good via our portal. The Supplier of goods shall receive the selling price for the
goods kept by them after we deduct our commission and service charge.
3. Objective:
 Increase Efficiency- A lot of our government resources are wasted on

inefficient practises. This is because of lack in organised method of storing
goods in the cold storages. Here instead of humans the algorithms will
decide what is best for the overall service.

 Automate the management process- Due to minimal involvement of
humans there will less errors that occurs due to human.
 User friendly- Our aim is build a system that encompasses both the ease of
use of an Android phone but the sophistication of a Linux server. Overall
process of managing the whole thing will be an easy task.
 Decrease cost- The routing of every job will be done is a way that the fuel
and maintenance charge will be the minimum.
 Judicious use of space-Space in our cold storage is precious and every inch
will be used up to the best of its potential.
 Effective distribution of goods- A good cold chain service must be able to
supply goods when needed and wherever needed after meeting the
constraints.
4. Scope:
The individuals or entities affected by our establishment are as follows:
1) Farmers
2) Wholesalers
3) Retailers
4) Middlemen
5) Fishery
Our establishment if successfully implemented will usher a new system of food

distribution. Each and every common man will be affected by this system.
5. Categories of Goods:
In general, there are two groups of products: ~
i) Foods that are alive (e.g. In West Bengal mainly potatoes).

ii) Foods that are no longer alive and have been processed in some form (e.g.
In West Bengal mainly marine products).
6. System Analysis:
System Analysis refers into the process of examining a situation with the intent of
improving it through better procedures and methods. System Analysis is the
process of planning a new System to either replace or complement an existing
system. But before any planning is done the old system must be thoroughly
understood and the requirements determined. System Analysis is therefore, the
process of gathering and interpreting facts, diagnosing problems and using the
information to re-comment improvements in the System or in other words,
System Analysis means a detailed explanation or description. Before
computerized a system under consideration, it has to be analyzed. We need to
study how it functions currently, what are the problems, and what are the
requirements that the proposed system should meet.
System Analysis is conducted with the following objectives in mind:
1. Identify the customer’s need.
2. Evaluate the system concept for feasibility.
3. Perform economic and technical analysis.
4. Allocate functions to hardware, software people, database and other system

elements.
5. Establish cost and schedule constraints.
6. Create a system definition that forms the foundation for all the subsequent
engineering work.

a. REQUIREMENT ANALYSIS/ SRS OF THE COMPONENT
I. SYSTEM REQUIREMENTS
TECHNOLOGIES : JAVA 2 EE ( JSP, SERVLETS, JDBC)
WEB DEVELOPMENT
HTML, CSS, JAVASCRIPT, XML
TOOLS:
WEB SERVER : TOMCAT 9.0
RDBMS / BACK-END : MYSQL
IDE : ECLIPSE – OXYGEN
OPERATING SYSTEM : WINDOWS 7
OTHER APPLICATION
SOFTWARES USED : MS Word 2007 (For Documentation)
HARDWARE Intel(R) Core(TM)i3 CPU @2.80GHz ,

CONFIGURATION OF THE 4GB RAM,
MACHINE USED FOR 250GB HDD.
DEVELOPMENT :

SOFTWARE REQUIREMENT
 OS: Windows
 Database: Oracle
 IDE: Eclipse
 Server: Tomcat Server (Free-Open source)
 Language: Java-JEE environment (Free-Open source)
 Front end: Browser with support for JavaScript
HARDWARE REQUIREMENT
 Processor – i3
 Hard Disk – 50 GB
 Memory – 4GB RAM
 Mouse – Any Standard
 Keyboard – Any Standard
 Monitor – Any color monitor
 Local Area Network Preferable
II. ACCEPTANCE CRITERIA
The following acceptance criteria were established for the evaluation

of the new system:
 User friendliness: - The system should meet user needs and should
be easy to learn and use.
 Modularity: - The system should have relatively independent and
single function parts.

 Maintainability: - The system should be such that future maintenance
and enhancements times and efforts are reduced.
 Timeliness: - The system should operate well under normal, peak and
recovery conditions.
 The system developed should be accurate and hence reliable i.e. the
error rate should be minimized and the outputs should be consistent
and correct.
 Both the execution time and response time should be negligibly low.
 The system should be efficient i.e. the resources utilization should be
optimal.
 The system should have scope to foresee modifications and
enhancements i.e. it should be able to cope with the changes in
future technology.
b. PROPOSED SYSTEM FUNCTIONALITY
The proposed system will be designed to support the following features:-
 The proposed system has a user friendly interface for porting of data to
server.
 The proposed system provides the facility to pull the data from the server
of the specified Supply order number and get the respective report.
 The proposed system provides no replication of data.
 User can get the desired output according to their queries. This is an
added advantage.
7. Feasibility Analysis:
NEED FOR FEASIBILITY STUDY:
To do Feasibility Study we need to consider the economic, technical and

behavioural factors in the system development. First a project team is formed.
The team develops system flowcharts that identify the characteristic of the

system. Evaluate the performance of each system, weigh the system performance
and cost data and select the best proposed system for the job. The study
culminates in a final report to the management.
a. Economic Feasibility: Economic analysis is the most frequently used

method for evaluating the effectiveness of a proposed system. More commonly
known as cost / benefit analysis, the procedure is to determine the benefits and
savings expected from the system and compare them with costs. If the benefits
outweigh the cost, then the decision is made to design and implement the
system. Otherwise further justifications or alterations inthe proposed system will
have to be made so that it has a chance of being approved. This is an ongoing
effort that improves in accuracy at each face of the system life cycle. The
approximated economic cost of our project is such that we are able to ensure
that we will not be facing any losses.
b. Technical Feasibility: A study of function, performance and constraints

that may affect the ability to achieve an acceptable system is the next important
issue to be sorted out. The considerations that are normally associated with
technical feasibility include: development risk, resource availability and
technology. It mainly includes the technical facilities required for developing the
proposed system, hardware and software specification besides process and
modules. Technical risk can be brought down at satisfactory level by systematic
utilization of the software and hardware tools keeping in view the sound support.

MySql technology has been chosen for the development of the project.
MySql database provides the best option for development of the error free and
secure database development. As such a database in this system can grow to
considerable size so MySql is the best choice. It is used for building and
maintaining relational database as data transaction can be made faster and huge
amount of data can be manipulated efficiently and quickly.
Java sever pages (jsp) and Microsoft active server pages(asp) technologies
provide a simplified, fast way to create web pages that display dynamically
generated content. While asp and jsp technologies aresimilar in many ways,they
also differ significantly in some ways. The biggest difference between jsp and asp
technologies lies in the approach to thesoftware design. Asp is based on isapi
whereas jsp is implemented as a part of j2ee. Asp consists of a single dll (asp.dll)
which generates dynamic content when an asp page with server-side script
combined with html is parsed through it. Similarly, the jsp-enabled engine on the
web server will process the jsp page, which mayinclude technology-specific tags,
declarations, and possibly scriptlets in java, along with html or xml tags. Also jsp is
more portable that’s why we used jsp in our project.
c. Behavioural Feasibility: People in general are inherently resistant to

change. But by using a system which will be easily available to user the resistance
faced can be expected to be of a lower extent. An estimate should be made
about how strong a reaction the user staff is likely to have towards this

computerized system. It is also common knowledge that introduction of any new
system involves changes in company turnover. The employee system also faces
changes with retraining required along with transfers and changes in job status.
Therefore it is understandable that the introduction of any new system requires
special effort and expenses to convince, educate, sell and train the staff on these
new methods of business.
d. Operational Feasibility: Proposed projects are beneficial only if they can

be turned into information systems that will meet the operating system will work
when it is developed and installed. Are there major barriers to implementation?
Some of the important questions that are useful to test the operational feasibility
of a project are given below.

8. Data Flow Diagrams
a. CONTEXT DIAGRAM
CLIENT SIDE BUSINESS SIDE
SUPPLIER Allocation details Inventory status
Supply details
COLD CHAIN ADMINISTRATOR
Supply status LOCATOR
SYSTEM
Inventory details
0
Order status
CONSUMER Order details User details
User details

b. Level 1 DFD
Indexed Cold Storage data Inventory data
COLD STORAGE STORE

DATASTORE 0.1
Cold Storage details
Cold Storage details
Allocation Details
Supply Status CONTENTS

ALLOCATE
DATASTORE
0.2
Supply Details
User Details Distribution details
User Details Order Status
USER DARASTORE DISTRIBUTE

0.3
Order Details
User Details

9. ENTITY-RELATIONSHIP DIAGRAM (PROPOSED):
Capacity Address ItemName ItemPrice

State
Name District
Quantity
ItemID
Contact
CSID
GOODS
COLD STORE STORES
M N
M
Date
Name Status M
UserID Password OrderID
TYPE
1 N N
SUPPLIER GIVES BUY ORDER
CONTAINS
Name Date
UserID N
Password OrderID Status
CONSUMER 1 PLACES N SALE ORDER

10. Database Tables:
 CS
FIELD NAME FIELD TYPE FIELD SIZE REMARKS

Id int NOT NULL
Name Varchar 50 NOT NULL
Capacity int NOT NULL
Address Varchar 50 NOT NULL
State Varchar 50 NOT NULL
District Varchar 50 NOT NULL
Contact Varchar 50 NOT NULL
 Contents

csid int NOT NULL
Quantity Varchar 50 NOT NULL
 Pref

csid int NOT NULL
prefid int NOT NULL
rank Varchar 50 NOT NULL
 User

UId int NOT NULL
UName Varchar 50 NOT NULL
Password Varchar 50 NOT NULL

11. Development:
After designing the structures of all the modules and database, the project
is developed using, MVC (Model View Controller) Architecture. Implementation
of this architecture separates the three parts from each other- Data, View and
Business Logic and hence they can be developed separately. The View designed
using JSP and the logic is embedded in the controller which is nothing but a
servlet. In this project, we will be using pure JAVA Classes to hold the data. This
pure JAVA classes will be having only attributes, variables representing
corresponding data fields with no methods. The overall development is done
and executed with the help of web server like Tomcat.
12. Inter module interaction:
Inventory: The administrator facing module interacting with Allocation
Allocation: The user facing module interacting with modules Inventory and
Distribution. It interacts with the producer.
Distribution: The user facing module interacting with module Inventory. It

interacts with the consumer.
13. Process Flow:
a. Supplier side
i) Supplier registration
ii) Supplier placing an order(type, quantity, duration) to Allocation module
iii) Allocation module asking for statistics(Best 3 places to keep the goods,
present capacity) from Inventory module

iv) Allocation module allocates goods of Supplier to cold storage
v) Allocation module informs Supplier
vi) The allocation module bills the Supplier
b. Consumer side
i) Consumer registration
ii) Consumer placing an order to Distribution module
iii) Distribution module checks for statistics from Inventory
iv) Distribution module assigns route for fetching goods from cold storage
v) Distribution module delivers goods to the consumer
vi) Distribution module receives cash
14. Module wise Description
a. Primary objectives of module Allocation
Description
It is a user facing module. It takes input from Supplier of perishable goods

(primarily farmers)
Algorithm followed: ~
While(1) {
1. WaitForEvent();
2. If(Event(UserRequest))
a. If(AtomicEvent==true)
i. createProcess();
b. else
i. createThread();

createProcess() {
1. Take Information from inventory;

2. Calculate min cost;
3. Create transportation details();
4. Update allocation table();
5. Send request to transportation;
createThread() {
1. Create a thread;
2. Take Information from inventory;
3. Calculate min cost;
4. Create transportation details();
5. Update allocation table();
6. Send request to transportation;
}

Flow Chart :
START
TAKE INPUT
true false
IS ATOMIC
EVENT?
CREATE THREAD CREATE PROCESS
Take Information
from inventory
Calculate min cost
Create transportation details calculate min cost
Update allocation table
Send request to transportation
//STOPS ONLY WHEN THERE IS AN INTERRUPT

Functionality of User-Interface
i) Register every Supplier and provide them with a unique id. Following
information about Suppliers are to be stored:
a. Supplier name
b. Place from where the user will provide goods
ii) Takes input from Supplier/*consumer*/ in the following format:
a. Name of goods (The module will derive type from name)
b. Quantity of goods
iii) Provide details about allocation of cold storage to the Supplier
iv) Provide details about distribution of the goods stored to the
Supplier(Name of buyer and his contact co-ordinates)
v) Allocation module then calculates the number of days during which the
goods were there in the cold storage, transportation cost and charges
the Supplier accordingly
vi) Provide the producer with a bill stating expenses, service charge and tax
vii) Return the money obtained by selling the goods after deducting the bill
amount
Interaction with module Inventory
i) Input to Inventory:
a. Location
b. Type of goods
c. Quantity
ii) Output from Inventory:
a. Cold storages in that locality having free space
b. Free space in each of the cold storages.
Allocation module calculates the number of days the goods were
there in the cold storage

b. Primary objectives of module Inventory
DEFINITION:
A simple definition of a warehouse is: ‘A warehouse is a planned space for

the storage and handling of goods and material.’ In general, warehouses
are focal points for product and information flow between sources of
supply and beneficiaries.
IMPORTANCE OF WAREHOUSING:
The warehouse is a key component of the supply chain in emergencies. It

buffers uncertainties and breakdowns that may occur in the supply chain.
When properly managed and appropriately stocked a warehouse provides
a consistent supply of material when it is needed.
INPUT FOR INVENTORY MODULE:
 Name of the city where cold storage is located.

 Amount which needs to be stored in cold storage warehouse.
OUTPUT FOR INVENTORY MODULE:
 Current storage capacity of a cold storage.

 Best 3 cold storage places according to current storage capacity.
CALCULATING WAREHOUSE SPACE:The size of warehouse required for an

operation is determined by the maximum quantity, in tonnage and volume, of
supplies to be stored there at any one time. This quantity is determined by the
number of ‘pallets’. A pallet is a flat transport structure that supports goods in a
stable fashion while being lifted by a forklift, pallet jack, front loader, work saver
or other jacking device or a crane. A pallet is the structural foundation of a unit
load which allows handling and storage efficiencies.

Image of a Pallet
FORMULA:
Storage space in cold storage = Pallets stored at the ground level *

Pallet module size
Here,
Pallets stored at the ground level = Number of pallets needed to store a certain
good / ( Number of levels needed to stack a certain good * Division of pallets
structure )
Pallet module size = Pallet module width * Pallet module length

Image of Pallet storage system in a cold storage
ASSUMPTIONS TO CALCULATE SPACE:
 Module size of each and every pallet should be fixed i.e. a standard pallet size
which is 48 inch * 40 inch should be maintained.
 Size or area or capacity of each and every cold storage should also be fixed in
order to calculate the amount of free space after goods are stored in cold
storage.
ALGORITHM FOR FINDING BEST 3 PLACES FOR EFFICIENT GOODS ALLCATION:
Step 1: Start.
Step 2: Select the ALLOCATION module defined places and all of its information’s
from cold storage database of INVENTORY module. ( SQL Query )
Step 3: Sort the places i.e. cold storages of the specified places according to the
present capacity or space of cold storages in descending order.
Step 4: Enter the amount of goods, given by ALLOCATION module which needs to
be stored in cold storage warehouse.
Step 5: Search for the specified amount given in Step 4 from the sorted list of
present capacity of Step 3.

Step 6: If the given amount is found in the sorted list, then print that amount and
the next 2 amounts greater than it.
lf not found, print the 3 amounts greater than the given amount.
Step 7: Stop.
FLOW CHART:

c. Primary objectives of module Distribution
The distribution is an important module which is user facing. It takes input from
the distributer and is an important module for selling the products Distribution is
a business system concerned with the physical transportation of foods, including
the ‘handover’ of foods between different links in the cold chain, e.g. producer to
delivery truck, delivery truck to retailer.
FLOWCHART:
Check whether
Triangulate distance is less
Input cold storage in than shortest
area route
No Yes
Next
Input
No Check
availability
of product
Calculate shortest route Yes

Output
ALGORITHM:
Problem 1: How to locate resource and distribute accordingly
1) Input taken from consumer.

2) Location pin pointed.

3) Nearby cold storage is searched first in adaptable radius. Data taken from
Cold Storage Database. If no cold storage found, then redo step 3 with
next adaptable radius.
4) Check for availability of product in cold storage from Inventory database. If
product unavailable go to step 3.
5) Routes calculated expressways, national highway, and state highway. If
distance less than shortest route (which is initially INFINITY) then go to step
6 else go to step 3.
6) Check quantity of food to be sent. If it is large enough go to step 8 else
wait until large enough quantity (i.e., redo steps 1-5) is demanded on route
and go to step 7.
7) If drop points and pick up points are multiple calculate all routes possible
and hence calculate the shortest route possible using Dijkstra’s Algorithm.
8) Send the shortest route to transportation module with exact pickup and
drop points and go to step 1 for next input.
15. Testing and Debugging:
Software testing is a critical element of the ultimate review of specification design

and coding. Testing of software leads to the uncovering of errors in the software
functional and performance requirements are met .Testing also provides a good
indication of software reliability and software quality as a whole. The result of
different phases of testing are evaluated and then compared with the expected
results. If the errors are uncovered they are debugged and corrected. A strategy
approach to software testing has the generic characteristics:
 Testing begins at the module level and works “outwards” towards the
integration of the entire computer based system.
 Different testing techniques are appropriate at different points of time.
 Testing and debugging are different activities, but debugging must be
accommodated in the testing strategy

a. GOALS AND OBJECTIVES
“Testing is a process of executing a program with the intent of finding an error”. A
good test case is one that has a probability of finding an as yet undiscovered
error. A successful test is one that uncovers an as yet undiscovered error. Our
Objective is to design test processes that systematically uncover different classes
of errors and do so with minimum amount of time and effort.
b. STATEMENT OF SCOPE
A description of the scope of the software testing is developed. All the features to
be tested are noted as follows. The basic principles that guides software testing
are,
 All test cases should be traceable top customer requirements. The most
severe defects from the customer’s point of view are those that cause the
program to fail to meet its requirements.
 Test case should be planned long before testing begins. Testing plan can
begin as soon as the requirement model is complete. Detailed definition of
the test cases can begin as soon as the design is solidified. Therefore, the
entire test can be planned before any code has been generated.
 Testing should begin “in the small” and progress towards “in the large”. The
first test planned and executed generally focus on the individual modules.
As testing progresses testing shifts focus in an attempt to find errors in
integrating clusters of modules and ultimately in the entire system
c. TEST CASE
Before the project is released, it has to pass through a test cases suit, so that the
required functionality is met and previous functionality of the system is also not
broken to do this, there is existing test cases which checks for the previous
functionality. New test cases are prepared and added to this existing test suit to
check for the added functionality.
Test cases describe an input description and compare the observed output with
expected output to know the outcome of the test case. If it is different, then,
there is a failure and it must be identified.
Test Cases for different field used.

UName: should be a character value till length 50
TEST EXPECTED
INPUT
CASES OUTPUT
Invalid
1 123
Input
2 Spandan Valid Name
Invalid
qwertyuiopasdfghjklzxcvbnmmnbvcxzlkjhgfdsapoiuytre
3 Input ( out
wq
of range )
Invalid
4 -12
Input
UId: should be a numeric value
TEST CASES INPUT EXPECTED OUTPUT

1 123 Valid Number
2 Spandan Invalid Input

A pictorial representation of this can be shown as follows :
New Test case Output

Software Under
Testing
Existing Test
Case
Comparator
Result of
Testing
d. DEBUGGING
Debugging occurs as a consequence of successful testing i.e. when a test case

uncovers an error, debugging is the process that results in identifying the location
of error and the removal of error. The poorly understood mental process that
connects a symptom to cause is debugging. This process will always have one of
the two outcomes:
 The cause will be found, corrected and then removed or

 The cause will not be found. In the latter case the person performing
debugging may suspect a cause, design a test case to help validate his
suspicion, and then work towards the correction of errors in the interactive
fashion.
Following three approaches of debugging were used:

 Debugging by Induction
 Debugging by Deduction
 Backtracking

16. Implementation:
Once the system was tested, the implementation phase started. A crucial
phase in the system development life cycle is successful implementation of new
system design. Implementations simply mean converting new system design into
operation. This is the moment of truth the first question that strikes in every one’s
mind that whether the system will be able to give all the desires results as
expected from system. The implementation phase is concerned with user training
and file conversion.
The term implementation has different meanings, ranging from the

conversion of a basic application to a complete replacement of computer system
Implementation is used here to mean the process of converting a new or revised
system design into an operational one. Conversion is one aspect of
implementation. The other aspects are the post implementation review and
software maintenance. There are three types of implementation:
 Implementation of a computer system to replace a manual system.

 Implementation of a new computer system to replace an existing one.
 Implementation of a modified application to replace an existing one.

17. Screenshots:
17.1 Homepage:

17.2 Demonstration

17.3 Login Page

17.4 View all cold storage details

17.5 Search Results

17.6 Infrastructure page

17.7 Sign Up page

17.8 Confirmation

17.9 Receipt

17.10 Rate Chart

17.11 Log Out

17.12 Buy Item

18. Benefits:
1) Transparency: The entire process shall be automated and there is no

scope for the interference of any third party. The Supplier of goods shall
get all information about the goods he provided.
2) No middleman: The primary problem in the prevalent system comprising

a hierarchy of middlemen is the non-availability of proper selling price of
the goods produced by farmers. Using the software they can sell their
goods to customers directly and get their rightful price.
3) Steady supply (hence less fluctuation of price): The consumers get the
supply of perishable commodities with the lower fluctuation of prices. This
system will stabilize market prices and evenly distribute goods both on
demand basis and time basis. The farmers get the opportunity of
producing cash crops to get remunerative prices.
4) Efficient algorithms shall be devised and applied: Thus, the present
system of trial and error shall be removed. As algorithms will replace thumb
rules, the cost incurred shall also be minimized.
5) Employment: The implementation of the proposed system shall generate

employment as well as many entrepreneurial opportunities. Moreover, the
present middlemen get a chance to migrate from their unstructured way of
functioning and can bring themselves in the purview of law-abiding
businesses.
6) Transportation: Truck space utilization is maximum as an efficient

algorithm is followed. This in turn reduces fuel cost.
19. Limitation:
 Database used is SQL Server and every database has a stack limit.
 Manual Errors at the time of entering the data can’t be checked; only the
validation required with respect to proposed system is checked.

20. Glossary
Supplier: The individual or entity supplying perishable products to our

establishment
Consumer: The individual or entity purchasing perishable products to our

establishment
Administrator: There are two categories of administrators-
a. Inventory manager: An individual or entity (department) that updates

records regarding cold-storages.
b. Transportation manager: An individual, entity(department) or a third party
that provides the facility of transportation
21. Bibliography:
We are indebted to the following resources:
• “Fundamentals of Software Engineering” by Rajib Mall
• Introduction to Algorithms, by Thomas H. Cormen, Charles E. Leiserson,

Ronald L. Rivest, Clifford Stein
• “Database system concepts” by Abraham Silberschatz, Henry F. Korth and S.

Sudarshan
• www.wikipedia.com,www.google.com (and the internet in general)
• Research papers

Page Number-1 Cold Chain Locator System, Group 15

Загружено:

Сведения о документе

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Page Number-1 Cold Chain Locator System, Group 15

Загружено:

Авторское право:

Доступные форматы

Page Number-1 COLD CHAIN LOCATOR SYSTEM, GROUP 15

It is understood that by this approval the undersigned does not necessarily

Prof. Abhijit Saha

Page Number-2 COLD CHAIN LOCATOR SYSTEM, GROUP 15

We also thank our seniors for rendering selfless help.

Mr. Pinaki Chakraborty _________________________________

Mr. Sourish Atorthy _________________________________

Mr. Spandan Ghosh _________________________________

Mr. Utsav Dey _________________________________

Page Number-3 COLD CHAIN LOCATOR SYSTEM, GROUP 15

a. Requirement Analysis/ SRS of the Component

b. Proposed System Functionality.......................................................11

a. Economic Feasibility ……………………………………………………………….12

8. Data Flow Diagrams

Page Number-4 COLD CHAIN LOCATOR SYSTEM, GROUP 15

14. Module wise description…………………………………………………………….20-29

a. Primary objectives of module Allocation(and flow chart)

15. Testing and Debugging

a. Goals and Objectives.........................................................................30

Page Number-5 COLD CHAIN LOCATOR SYSTEM, GROUP 15

We propose an integrated system of cold storages (referred to as a cold

 Increase Efficiency- A lot of our government resources are wasted on

Page Number-6 COLD CHAIN LOCATOR SYSTEM, GROUP 15

The individuals or entities affected by our establishment are as follows:

Our establishment if successfully implemented will usher a new system of food

In general, there are two groups of products: ~

i) Foods that are alive (e.g. In West Bengal mainly potatoes).

Page Number-7 COLD CHAIN LOCATOR SYSTEM, GROUP 15

System Analysis is conducted with the following objectives in mind:

1. Identify the customer’s need.

2. Evaluate the system concept for feasibility.

3. Perform economic and technical analysis.

4. Allocate functions to hardware, software people, database and other system

5. Establish cost and schedule constraints.

Page Number-8 COLD CHAIN LOCATOR SYSTEM, GROUP 15

TECHNOLOGIES : JAVA 2 EE ( JSP, SERVLETS, JDBC)

WEB SERVER : TOMCAT 9.0

RDBMS / BACK-END : MYSQL

IDE : ECLIPSE – OXYGEN

OPERATING SYSTEM : WINDOWS 7

HARDWARE Intel(R) Core(TM)i3 CPU @2.80GHz ,

Page Number-9 COLD CHAIN LOCATOR SYSTEM, GROUP 15

II. ACCEPTANCE CRITERIA

The following acceptance criteria were established for the evaluation

Page Number-10 COLD CHAIN LOCATOR SYSTEM, GROUP 15

b. PROPOSED SYSTEM FUNCTIONALITY

The proposed system will be designed to support the following features:-

NEED FOR FEASIBILITY STUDY:

To do Feasibility Study we need to consider the economic, technical and

Page Number-11 COLD CHAIN LOCATOR SYSTEM, GROUP 15

culminates in a final report to the management.

a. Economic Feasibility: Economic analysis is the most frequently used

b. Technical Feasibility: A study of function, performance and constraints

Page Number-12 COLD CHAIN LOCATOR SYSTEM, GROUP 15

c. Behavioural Feasibility: People in general are inherently resistant to

Page Number-13 COLD CHAIN LOCATOR SYSTEM, GROUP 15

d. Operational Feasibility: Proposed projects are beneficial only if they can

Page Number-14 COLD CHAIN LOCATOR SYSTEM, GROUP 15

CLIENT SIDE BUSINESS SIDE

SUPPLIER Allocation details Inventory status

CONSUMER Order details User details

Page Number-15 COLD CHAIN LOCATOR SYSTEM, GROUP 15

Indexed Cold Storage data Inventory data