Title of the Project

Supply Chain Management System

Introduction of the Project:

The ”SUPPLY CHAIN MANAGEMENT SYSTEM” is the web-based system, designed for
a production sector, which gives information related to the clients and dealers of
the company with respect to its product launches. This product develops a system
that can be used by the company management to keep track of the sales, dealers
and its clients. In the existing method of tracking of all the details is tedious and
time consuming. Any product survey and launching of the area carried out manually
by representatives, which is a time taking task. It fulfills different requirements of
clients of the company. The specific purpose of the system is to automate the
communication between clients, Admin and the dealers of the organization.

Pictorial View of the Project:

Objective of the Project:

The main objective of the project is to find out the supply chain management
system. Supply chain is a lengthy process. Basically their supply chain is totally
warehouse-based. In supply chain, at first they store the entire product from
different manufacturer in their warehouse. The transportation cost is totally born by
the manufacturing company. Then the stored products are distributed through the
own vehicles to its several outlets. There is no intermediary between warehouse
and manufacturing company. No product directly comes to the outlet without the
hands of warehouse. Other objectives of this report are:

✓ To know the supply chain of supermarket.

✓ To understand the difference between the traditional markets supply chain
and supermarkets supply chain.
✓ To explore the relation of shopping to the supermarket of residential area &
non-residential area based on gender, income & age.
✓ To gather practical knowledge of supply chain management.
✓ To explore the variation between male and female customer in residential &
non- residential area.
✓ Improve operational & Streamlining operations
✓ Maintain all the project, employee, project database
✓ Maintain global standards of the project development
✓ Reduce Manpower and manual paper works for maintaining the records
offline
✓ Main the accuracy, integrity and consistency of the data
✓ Providing such a mechanism to make the man power fast to maintain all the
information about the project
Abstract of the project:

“SUPPLY CHAIN MANAGEMENT SYSTEM” is the management of a

network of interconnected businesses involved in the ultimate provision of product
and service packages required by end customers. It spans all movement and
storage of raw materials, work-in-process inventory, and finished goods from point-
of-origin to point-of-consumption. It is mainly designed for the production sector,
which gives information related to client and dealers of the company with respect to
product launches.

This application is designed to run on any computer. There is need

to install java software on client side machine. Based on the designation of the user
who registers into the application he has the permission to submit his registration
form and then specify the requirements. This Document plays a vital role in
companies are the targets of the Supply chain management Tool. Thus it is
expected that the company will deal directly with each clients of the company
regarding product information. . It fulfills different requirements of client’s. The
specific purpose of the system is to automate the communication between the
management (Admin), clients and the dealers of the organization.
Purpose of the Project:

The specific purpose of the system is to automate the communication

between the management, clients and the dealers of the organization. This project
maintains the information related to the client and dealers of the company with
respect to its product launch. This will also keep track of sales and dealers. The
scope of this project is to enable the user of an organization to view the issues
through the LAN/Internet. Based on the category of the user i.e. employee or
administrator, the various parts of the system are made available to the users.

Input and Output of the Project:

“Supply chain management” is basically, the movement of raw materials

into finished goods. In this project the Client provides its requirements about the
product. The admin, then contacts its various dealers for gathering the
requirements. The dealers display the list of items from which the admin selects the
items as specified by the client. After gathering the required items, admin gives the
gathered items to the inventory department where the processing is done. The final
product is manufactured and then finally delivered to the client which is the output
of the project. In the mean while the manufacturing cost is tabulated by the
accounting department and given to the client. Finally the client gives its feedback
which is transferred to the Admin and the dealers.
Existing Project Structure:

Supply chain management (SCM) is the management of a network of

interconnected businesses involved in the ultimate provision of product and service
packages required by end customers Supply Chain Management spans all
movement and storage of raw materials, work-in-process inventory, and finished
goods from point-of-origin to point-of-consumption. Organizations increasingly find
that they must rely on effective supply chains, or networks, to successfully compete
in the global market and networked economy. During the past decades,
globalization, outsourcing and information technology have enabled many
organizations to successfully operate solid collaborative supply networks in which
each specialized business partner focuses on only a few key strategic activities. Any
product survey and launching of the area carried out manually by representatives,
which is a time taking task. And even gathering all the requirements from different
dealers was also very tedious.

Proposed System Structure:

The product designed is the web-based system, mainly for production sector,
which gives information related to the clients and dealers of the company with
respect to its product launches. This product develops a system that can be used by
the company management to keep track of the sales, dealers and its clients. It
spans all movement and storage of raw materials, work-in-process inventory, and
finished goods from point-of-origin to point-of-consumption. This application is
designed to run on any computer. There is need to install java software on client
side machine. Based on the designation of the user who registers into the
application he has the permission to submit his registration form and then specify
the requirements. This Document plays a vital role in companies are the targets of
the Supply chain management Tool. Thus it is expected that the company will deal
directly with each clients of the company regarding product information. . It fulfills
different requirements of client’s. The specific purpose of the system is to automate
the communication between the management (Admin), clients and the dealers of
the organization.
Tools/Platform, Hardware and Software Requirement specifications:

Software Requirements:

Name of component Specification

Operating System Windows 98, Windows XP, Windows7,
Linux
Language PHP Server Side Scripting
Database MySQL Server
Browser Any of Mozilla, Opera, Chrome etc
Web Server Apache 2
Software Development Kit WAMP or XAMP
Scripting Language Enable JavaScript, HTML
Database JDBC Driver MySQL

Hardware Requirements:

Name of component Specification

ProcessorPentium III 630MHz
RAM 128 MB
Hard disk 20 GB
Monitor 15” color monitor
Keyboard122 keys
Modules and their description

Orders Module: When a customer goes through checkout, the information on their
order is automatically transferred to the Orders section for you to keep track of. In
the administration, you can view all of the orders made on their site, manually add
orders, or edit the details of existing orders. The Orders section is located under
Sales > Orders. On this page, every order ever made from the store is listed in
detail.

Customer Module: Shop owners should know who their customers are and how
to manage their information. In the administration, customer information will need
to be stored efficiently to remember any transactions made with their account. To
access customer information, you can log into the administration panel of the
store. The Customer management sections are located under Sales > Customers.
There are three sections used to manage customer information: Customers,
Customer Groups, and IP Blacklist.

Affiliate Module: Ecommerce gives you the opportunity to set up an affiliate

program to promote additional traffic to your shop. Affiliates will receive a
commission for each time they direct traffic or sales to your site. The commission
% can be adjusted in the administration under Sales > Affiliate.

Coupons Module: You may create and designate coupons to specific products or
product categories under Sales > Coupons. The Coupons page will display a list of
all the coupons created in the administration.

Gift vouchers: Gift vouchers can be individually sent to customers through their
email by other customers in the store front. The customer receiving the gift
certificate can use the code provided in the email at the shopping cart to deduct the
gift voucher amount from the order total. To manage the Gift Vouchers of the store,
go to Sales > Gift Vouchers > Gift Vouchers.
Mail Module: The Mail system send emails to specific customer groups. You can
use this feature to send newsletters, information on specials, or to communicate
any type of store information to select groups of customers. Customer groups are
especially useful in emailing specific groups of people instead of every customer
stored in the administration. For more information on how to create a customer
group, see Customer Groups. The Mail page can be accessed from Sales > Mail.

Profiles Module: Profiles are a new, optional feature. They allow you to set up
recurring payments for your customers. Profiles are useful if you plan to sell
products by subscription, if you are promoting a discount or member's club, or if
you are simply breaking up payments into smaller portions. This feature gives the
store owner more control over how customers are charged for products or services.

Manufacturers Module: The Manufacturer section is used to categorize products

by manufacturer. This section can be accessed under Catalog > Manufacturers. The
Manufacturer names below came with the install. They can be deleted, and new
manufacturer information can be added in its place. The manufacturer information
should be created before products are added, so the manufacturer category can be
selected when adding the product. Saving a product without including the
manufacturer isn't advised, because customers can search for products in the store
front through their manufacturer page. With the manufacturer missing from the
product information, the product will not be available on those pages.

Categories Module: In the default theme of the store front, parent categories are
listed in the top menu of the home page, and on the left side of product pages. This
navigational feature is used to guide customers to similar products within the same
category. Exposing customers to different products within a category lets the
customer compare the similarities and differences between products to make the
most informed purchase. When adding products to the store, you will be asked for
a product category to sort them in. It is a good idea to establish these categories
before adding products, to save yourself the trouble of adding the category name to
the products later.
 List of reports that are likely to be generated.

Affiliate commission report: The Affiliate Commission Report can be accessed

from Reports>Affiliates>Commission in the administration. This report lets you
keep track of the affiliates who are making a commission for referring customers to
the store.

 The Affiliate Commission Report displays the following information:

 Affiliate Name: The name of the individual/company acting as an affiliate for
the store.
 E-mail: The e-mail for contacting the affiliate.
 Status: Shows if the affiliate is enabled or disabled.
 Commission: The commission amount made from a customer purchase.
 No. Orders: The number of orders obtained through this affiliate.
 Total: The total amount that this affiliate has earned through the
affiliate program.

Customer reports: The Customer Reports section can be accessed under

Reports>Customers. These reports display specific information to track orders
made, reward points, and store credit for each customer using the store.

Order reports : The Order Report section can be accessed under

Reports>Customers>Orders.

The following information will be displayed about customer orders:

 Customer Name
 E-Mail
 Customer Group: The customer group the customer is categorized in.
 Status: Shows if the customer is currently allowed to login to their store
account.
 No. Orders: The total number of orders made by this customer.
 No. Products: The total number of products purchased by this customer.
 Total: The total amount purchased from this customer. Customers
are arranged on the list from the highest amount to the lowest.

Reward points report : The Order Report section can be accessed under
Reports>Customers>Reward Points.
The following information will be displayed about customer reward point usage:
 Customer Name
 E-Mail
 Customer Group: The customer group the customer is categorized in.
 Status: Shows if the customer is currently allowed to login to their store
account.
 Reward Points: The amount of reward points obtained by this customer.
Reward points can be acquired by a customer by purchasing a product
with reward points designated to it under its Data tab under
Catalog>Products.
See Reward Points for more information.
 No. Orders: The total number of orders made by this customer.
 Total: The total amount purchased from this customer.

Customer credit report : The Order Report section can be accessed under
Reports>Customers>Credit.

The following information will be displayed about customer store credit:

 Customer Name
 E-Mail
 Customer Group: The customer group the customer is categorized in.
 Status: Shows if the customer is currently allowed to login to their store
account.
 Total: The total amount purchased from this customer.

Products viewed report : The Products Viewed Report gives you an idea of what
products are being viewed the most, or the least, in the store front. You can access
this section under Reports > Products > Viewed in the administration side. The
report will position the top viewed product first. Along with the product name and
model, the report will display the number of customers who viewed that product in
the store front, and the percentage of views for this specific product out of all the
views for products on the site. Clicking "Reset" will clear the information below and
reset the report to only collect information from that moment on.
Sales reports : The reports under Sales Reports can be accessed from Reports
Sales. Orders, taxes, shipping, returns, and coupon sales information can be
tracked in list form.

Tax Report : The Tax Report can be accessed through Reports > Sales > Tax. The
Tax report displays which type of tax is being paid the most by customers in the
store front. Tax information is displayed in either daily, weekly, monthly, or yearly
increments depending on which option you select in the "Group By" drop box.
The Tax Report displays the following information:
 Date Start: The date of the first day of the week tracked (if set to week
in Group By).
 Date End: The date of the last day of the week tracked (if set to week in
Group By).
 Tax Title: The title of the tax type used.
 No. of Orders: The number of orders made through the store between the
date start and end.
 Total: The total amount of money paid for taxes by customers between
the date start and end.

Shipping report : The Shipping Report can be accessed through Reports > Sales >
Shipping. The Shipping report displays which shipping method is being used the
most by customers in the store front. Shipping information is displayed in either
daily, weekly, monthly, or yearly increments depending on which option you select
in the "Group By" drop box.
The Shipping Report displays the following information:
 Date Start: The date of the first day of the week tracked (if set to week
in Group By).
 Date End: The date of the last day of the week tracked (if set to week in
Group By).
 Shipping Title: The shipping method used. The shipping title with the highest
total will be displayed at the top. The lowest total will be at the bottom.
 No. of Orders: The number of orders made through the store between
the date start and end.
  Total: The total amount of money paid for shipping between the date
start and end.

Returns report : The Returns Report can be accessed through

Reports>Sales>Returns. The returns report shows how many returns were
requested within a given time frame. The returns information is displayed in either
daily, weekly, monthly, or yearly increments depending on which option you select
in the "Group By" drop box.
 The Returns Report displays the following information:
 Date Start: The date of the first day of the week tracked (if set to week in
Group By)
 Date End: The date of the last day of the week tracked (if set to week in
Group By)
 No. Returns: The number of return requests submitted or created
between the date start and date end.
SYSTEM ANALYSIS

INTRODUCTION TO SYSTEM ANALYSIS

System analysis is a process of gathering and interpreting facts, diagnosing
problems and the information to recommend improvements on the system. It is a
problem solving activity that requires intensive communication between the system
users and system developers. System analysis or study is an important phase of
any system development process. The system is studied to the minutest detail and
analyzed. The system analyst plays the role of the interrogator and dwells deep into
the working of the present system. The system is viewed as a whole and the input
to the system are identified. The outputs from the organizations are traced to the
various processes. System analysis is concerned with becoming aware of the
problem, identifying the relevant and decisional variables, analyzing and
synthesizing the various factors and determining an optimal or at least a
satisfactory solution or program of action. A detailed study of the process must be
made by various techniques like interviews, questionnaires etc. The data collected
by these sources must be scrutinized to arrive to a conclusion. The conclusion is an
understanding of how the system functions. This system is called the existing
system. Now the existing system is subjected to close study and problem areas are
identified. The designer now functions as a problem solver and tries to sort out the
difficulties that the enterprise faces. The solutions are given as proposals. The
proposal is then weighed with the existing system analytically and the best one is
selected. The proposal is presented to the user for an endorsement by the user.
The proposal is reviewed on user request and suitable changes are made. This is
loop that ends as soon as the user is satisfied with proposal. Preliminary study is
the process of gathering and interpreting facts, using the information for further
studies on the system. Preliminary study is problem solving activity that requires
intensive communication between the system users and system developers. It does
various feasibility studies. In these studies a rough figure of the system activities
can be obtained, from which the decision about the strategies to be followed for
effective system study and analysis can be taken.
Existing System
In the existing system the exams are done only manually but in proposed system
we have to computerize the exams using this application.

 Lack of security of data.

 More man power.

 Time consuming.

 Consumes large volume of pare work.

 Needs manual calculations.

 No direct role for the higher officials

Proposed System
The aim of proposed system is to develop a system of improved facilities. The
proposed system can overcome all the limitations of the existing system. The
system provides proper security and reduces the manual work.

 Security of data.

 Ensure data accuracy’s.

 Proper control of the higher officials.

 Minimize manual data entry.

 Minimum time needed for the various processing.

 Greater efficiency.

 Better service.

 User friendliness and interactive.

 Minimum time required.

FEASIBILITY STUDY
Feasibility study is made to see if the project on completion will serve the purpose
of the organization for the amount of work, effort and the time that spend on it.
Feasibility study lets the developer foresee the future of the project and the
usefulness. A feasibility study of a system proposal is according to its workability,
which is the impact on the organization, ability to meet their user needs and
effective use of resources. Thus when a new application is proposed it normally
goes through a feasibility study .The document provide the feasibility of the project
that is being designed and lists various areas that were considered very carefully
during the feasibility study of this project such as Technical, Economic and
Operational feasibilities. The following are its features:

TECHNICAL FEASIBILITY
The system must be evaluated from the technical point of view first. The
assessment of this feasibility must be based on an outline design of the system
requirement in the terms of input, output, programs and procedures. Having
identified an outline system, the investigation must go on to suggest the type of
equipment, required method developing the system, of running the system once it
has been designed.
Technical issues raised during the investigation are:

 Does the existing technology sufficient for the suggested one?

 Can the system expand if developed?

The project should be developed such that the necessary functions and
performance are achieved within the constraints. The project is developed within
latest technology. Through the technology may become obsolete after some period
of time, due to the fact that never version of same software supports older
versions, the system may still be used. So there are minimal constraints involved
with this project. The system has been developed using Java the project is
technically feasible for development.
ECONOMIC FEASIBILITY
The developing system must be justified by cost and benefit. Criteria to ensure that
effort is concentrated on project, which will give best, return at the earliest. One of
the factors, which affect the development of a new system, is the cost it would
require.
The following are some of the important financial questions asked during
preliminary investigation:

 The costs conduct a full system investigation.

 The cost of the hardware and software.

 The benefits in the form of reduced costs or fewer costly errors.

Since the system is developed as part of project work, there is no manual cost to
spend for the proposed system. Also all the resources are already available, it give
an indication of the system is economically possible for development.
2.1 PRODUCT PERSPECTIVE

Web traffic can be analyzed by viewing the traffic statistics found in the web server
log file, an automatically-generated list of all the pages served. A hit is generated
when any file is served. The page itself is considered a file, but images are also
files, thus a page with 5 images could generate 6 hits (the 5 images and the page
itself). A page view is generated when a visitor requests any page within the web
site – a visitor will always generate at least one page view (the main page) but
could generate many more.. Web Traffic Analyzer is aimed towards the vendors
who want to reach out to the maximum cross-section of customer and common
people who can be potential customer. This project envisages bridging the gap
between the seller, the retailer and the customer. Web Traffic Analyzer should be
user-friendly, ‘quick to learn’ and reliable software for the above purpose. OSM is
intended to be a stand-alone product and should not depend on the availability of
other software. It should run on both UNIX and Windows based platform.

2.2 PRODUCT FUNCTIONS

Web traffic is the amount of data sent and received by visitors to a web site. It is a
large portion of Internet traffic. This is determined by the number of visitors and
the number of pages they visit. Sites monitor the incoming and outgoing traffic to
see which parts or pages of their site are popular and if there are any apparent
trends, such as one specific page being viewed mostly by people in a particular
country. There are many ways to monitor this traffic and the gathered data is used
to help structure sites, highlight security problems or indicate a potential lack of
bandwidth — not all web traffic is welcome. Some companies offer advertising
schemes that, in return for increased web traffic (visitors), pay for screen space on
the site. Sites also often aim to increase their web traffic through inclusion on
search engines and through Search engine optimization.

2.3 USER CHARACTERISTICS

We have 2 levels of users

 User module: This is a normal level of user who will be very few number of
functionality for website
 Administration module: This user is an admin type who has full rights on the
system.

2.4 GENERAL CONSTRAINTS

The amount of traffic seen by a web site is a measure of its popularity. By analysing
the statistics of visitors it is possible to see shortcomings of the site and look to
improve those areas. It is also possible to increase (or, in some cases decrease) the
popularity of a site and the number of people that visit it.

2.5 ASSUMPTIONS AND DEPENDENCIES

All the data entered will be correct and up to date. This software package is
developed using JSP as front end which is supported by Aapache Server system.
MySQL as the back end which is supported by Window 7.
3.1.1 User Interface

 HTML has been used for developing the User Layout for the system

 JavaScript has been used for creating all the validations and client side
scripting functionality
 CSS has been used for designing the web pages of the system

3.1.2 HARDWARE INTERFACE:

 Processor : Intel Pentium IV or more

 Ram : 512 MB or more

 Cache : 1 MB

 Hard Disk : 10 GB recommended

3.1.3 Software Interface:

 Client on Internet: Web Browser, Operating System (any)

 Web Server: Operating System (any), Apache 2

 Database: MySQL

 Scripting Language: JSP, JavaScript, JQuery

3.1.4 Communication Protocol

Following protocols are required to be permitted on the server side

 HTTP incoming request

3.2 Functional Requirements

 The system runs of apache server so it is needed that server must have
apache server version 2.0 available
  We have used JSP for server side scripting so the current version of JSP must
be available on the server
 MySQL database has been used for storing the data of the website

 HTML has been used for creating the layout of the web application

 CSS has been used for creating the designing of the webpages

 JavaScript scripting language has been implemented on the system for

performing all of the Client Side Server Validation.

3.4. Classes and Objects of the Project

 Login Class: Used for performing all the operations of the login functionality.

 Page Class: Class for managing all the operations of the page.

 Traffic Class: Class for managing the traffic of the website

 IP Class: It has been used for storing all the IPs which hits the website

 Users Class: Class for managing all the user operations

 Permission Class: This class has been used for managing all the permissions
level opeations.

3.5. Non-Functional Requirements

 Performance: System should be able handle multiple users at a time using

any of the web browsers.
 Reliability: Database updating should follow transaction processing to avoid

data inconsistency.
 Availability: The project will be deployed on a public shared server so it will

be available all the time and will be accessible anywhere of the world using
internet.
 Security: We have implemented a lot of security mechanism to avoid to hack
the system by outer world.
 Maintainability: It is very easy to maintain the system. The system has been

developed on JSP so anyone who has the knowledge of JSP, can easily
maintain the system
 Portability: Yes this system is portable and we can switch the servers very
easily.
 Browser Compatibility: The project being web based required compatibility

with at least the popular web browsers. Microsoft Windows XP and above,
Linux and Macintosh being the current popular operating system and
Microsoft Internet Explorer, Mozilla Firefox, Opera, Safari and Google Chrome
being the currently popular web browser.
Security Testing of the Project

Testing is vital for the success of any software. no system design is ever perfect.
Testing is also carried in two phases. first phase is during the software engineering
that is during the module creation. second phase is after the completion of
software. this is system testing which verifies that the whole set of programs
hanged together.

White Box Testing:

In this technique, the close examination of the logical parts through the software
are tested by cases that exercise species sets of conditions or loops. all logical parts
of the software checked once. errors that can be corrected using this technique are
typographical errors, logical expressions which should be executed once may be
getting executed more than once and error resulting by using wrong controls and
loops. When the box testing tests all the independent part within a module a logical
decisions on their true and the false side are exercised , all loops and bounds within
their operational bounds were exercised and internal data structure to ensure their
validity were exercised once.

Black Box Testing:

This method enables the software engineer to device sets of input techniques that
fully exercise all functional requirements for a program. black box testing tests the
input, the output and the external data. it checks whether the input data is correct
and whether we are getting the desired output.

Alpha Testing:

Acceptance testing is also sometimes called alpha testing. Be spoke systems are
developed for a single customer. The alpha testing proceeds until the system
developer and the customer agree that the provided system is an acceptable
implementation of the system requirements.
Beta Testing:

On the other hand, when a system isto be marked as a software product, another
process called beta testing is often conducted. During beta testing, a system is
delivered among a number of potential users who agree to use it. The customers
then report problems to the developers. This provides the product for real use and
detects errors which may not have been anticipated by the system developers.

Unit Testing:

Each module is considered independently. it focuses on each unit of software as

implemented in the source code. it is white box testing.

Integration Testing:

Integration testing aims at constructing the program structure while at the same
constructing tests to uncover errors associated with interfacing the modules.
modules are integrated by using the top down approach.

Validation Testing:

Validation testing was performed to ensure that all the functional and performance
requirements are met.

System Testing:

It is executing programs to check logical changes made in it with intention of

finding errors. a system is tested for online response, volume of transaction,
recovery from failure etc. System testing is done to ensure that the system satisfies
all the user requirements.
Implementation and Software Specification Testings

Detailed Design of Implementation

This phase of the systems development life cycle refines hardware and software
specifications, establishes programming plans, trains users and implements
extensive testing procedures, to evaluate design and operating specifications
and/or provide the basis for further modification.

Technical Design

This activity builds upon specifications produced during new system design, adding
detailed technical specifications and documentation.

Test Specifications and Planning

This activity prepares detailed test specifications for individual modules and
programs, job streams, subsystems, and for the system as a whole.

Programming and Testing

This activity encompasses actual development, writing, and testing of program

units or modules.

User Training

This activity encompasses writing user procedure manuals, preparation of user

training materials, conducting training programs, and testing procedures.

Acceptance Test

A final procedural review to demonstrate a system and secure user approval before
a system becomes operational.
Installation Phase

In this phase the new Computerized system is installed, the conversion to new
procedures is fully implemented, and the potential of the new system is explored.

System Installation

The process of starting the actual use of a system and training user personnel in its
operation.

Review Phase

This phase evaluates the successes and failures during a systems development
project, and to measure the results of a new Computerized Transystem in terms of
benefits and savings projected at the start of the project.

Development Recap

A review of a project immediately after completion to find successes and potential

problems in future work.

Post-Implementation Review

A review, conducted after a new system has been in operation for some time, to
evaluate actual system performance against original expectations and projections
for cost-benefit improvements. Also identifies maintenance projects to enhance or
improve the system.

THE STEPS IN THE SOFTWARE TESTING

The steps involved during Unit testing are as follows:

a. Preparation of the test cases.

b. Preparation of the possible test data with all the validation checks.
c. Complete code review of the module.

d. Actual testing done manually.

e. Modifications done for the errors found during testing.

f. Prepared the test result scripts.

The unit testing done included the testing of the following items:

1. Functionality of the entire module/forms.

2. Validations for user input.

3. Checking of the Coding standards to be maintained during coding.

4. Testing the module with all the possible test data.

5. Testing of the functionality involving all type of calculations etc.

6. Commenting standard in the source files.

After completing the Unit testing of all the modules, the whole system is integrated
with all its dependencies in that module. While System Integration, We integrated
the modules one by one and tested the system at each step. This helped in
reduction of errors at the time of the system testing.

The steps involved during System testing are as follows:

 Integration of all the modules/forms in the system.

 Preparation of the test cases.

 Preparation of the possible test data with all the validation checks.

 Actual testing done manually.

 Recording of all the reproduced errors.

 Modifications done for the errors found during testing.

 Prepared the test result scripts after rectification of the errors.

The System Testing done included the testing of the following items:

1. Functionality of the entire system as a whole.

2. User Interface of the system.

3. Testing the dependent modules together with all the possible test data
scripts.

4. Verification and Validation testing.

5. Testing the reports with all its functionality.

After the completion of system testing, the next following phase was the
Acceptance Testing. Clients at their end did this and accepted the system with
appreciation. Thus, we reached the final phase of the project delivery.

There are other six tests, which fall under special category. They are
described below:

 Peak Load Test: It determines whether the system will handle the volume of
activities that occur when the system is at the peak of its processing demand.
For example, test the system by activating all terminals at the same time.

 Storage Testing: It determines the capacity of the system to store

transaction data on a disk or in other files.

 Performance Time Testing: it determines the length of time system used by

the system to process transaction data. This test is conducted prior to
 implementation to determine how long it takes to get a response to an inquiry,
make a backup copy of a file, or send a transmission and get a response.

 Recovery Testing: This testing determines the ability of user to recover data
or re-start system after failure. For example, load backup copy of data and
resume processing without data or integrity loss.

 Procedure Testing: It determines the clarity of documentation on operation

and uses of system by having users do exactly what manuals request. For
example, powering down system at the end of week or responding to paper-out
light on printer.

 Human Factors Testing: It determines how users will use the system when
processing data or preparing reports.
Project Category

Relational Database Management System (RDBMS) : This is an RDBMS based

project which is currently using MySQL for all the transaction statements. MySQL is
an opensource RDBMS System.

Brief Introduction about RDBSM :

A relational database management system (RDBMS) is a database management

system (DBMS) that is based on the relational model as invented by E. F. Codd, of
IBM's San Jose Research Laboratory. Many popular databases currently in use are
based on the relational database model.

RDBMSs have become a predominant choice for the storage of information in new
databases used for financial records, manufacturing and logistical information,
personnel data, and much more since the 1980s. Relational databases have often
replaced legacy hierarchical databases and network databases because they are
easier to understand and use. However, relational databases have been challenged
by object databases, which were introduced in an attempt to address the object-
relational impedance mismatch in relational database, and XML databases.
 Implementation

Methodology:
Model View
Controller or MVC as it
is popularly called, is a

software design
pattern for developing web
applications. A Model View
Controller pattern is
made up of the
following three parts:
 Model - The lowest level
of the pattern which is
responsible for maintaining data.
 View - This is responsible for displaying all or a portion of the data to the
user.
 Controller - Software Code that controls the interactions between the Model
and View.
MVC is popular as it isolates the application logic from the user interface layer and
supports separation of concerns. Here the Controller receives all requests for the
application and then works with the Model to prepare any data needed by the View.
The View then uses the data prepared by the Controller to generate a final
presentable response. The MVC abstraction can be graphically represented as
follows.
MVC (Model View Controller Flow) Diagram

PROJECT SCHEDULING

An elementary Gantt chart or Timeline chart for the development plan is given
below. The plan explains the tasks versus the time (in weeks) they will take to
complete.
 January February March

Requirement
Gathering

Analysis

Design

Coding

Testing

Implement

W1 W2 W3 W4 W1 W2 W3 W4 W1 W2 W3 W4

Wi‘s are weeks of the months, for i =1, 2, 3, 4

Database Structure and Table Details

Coupon Table
Category
Customer Table

Manufacturer Table

Customer Table
Order History Table
Product Discount Table

Product Image Table

 Order Table

Store Table

Product Table
 int{1L) No None AUTO INCREMENT
No
3 sku
varchar(64) utf8 General ci No None
4 upc
No
5 ean
varchar(14) utf8 General ci No None
6 jan
No
7 isbn
varchar(17) utf8 General ci No None
No
9 location
varchar(128) utf8 General ci No None
No O
LI stocK status id
int{1L) No None
Yes
L3 manufacturer id int{1L)
No None
decimal[L5. 4) No 1
15 price
int(8) No
int{1L) No O
L7 tax class id
No None
No

21 length decimal(L5 8) No
No 0.00000000
23 height decimal(L5 8) No
No O
25 subtract 11 I1/II1 £(I) No 1
No 1
27 sort order int{1L) No O
No O
29 viewea No O
No
31 date modified datetime No None
Voucher Table

User Table
 Return Table

Tax Rate Table

Dataflow Diagram Level 1:
Dataflow Diagram Level 2:
ER Diagram:
High Level Table Relationship:
Identification of Need

The old manual system was suffering from a series of drawbacks. Since whole of
the system was to be maintained with hands the process of keeping, maintaining
and retrieving the information was very tedious and lengthy. The records were
never used to be in a systematic order. there used to be lots of difficulties in
associating any particular transaction with a particular context. If any information
was to be found it was required to go through the different registers, documents
there would never exist anything like report generation. There would always be
unnecessary consumption of time while entering records and retrieving records.
One more problem was that it was very difficult to find errors while entering the
records. Once the records were entered it was very difficult to update these
records. In present, work done in the electricity board is performed manually which
is a great headache for the department .The reason behind it is that there is lot of
information to be maintained and have to be kept in mind while running the
business .For this reason we have provided features Present system is partially
automated (computerized), actually existing system is quite laborious as one has to
enter same information at three different places.

Following points should be well considered:

 Documents and reports that must be provided by the new system: there can
also be few reports, which can help management in decision-making and cost
controlling, but since these reports do not get required attention, such kind of
reports and information were also identified and given required attention.

 Details of the information needed for each document and report.

 The required frequency and distribution for each document.

 Probable sources of information for each document and report.

 With the implementation of computerized system, the task of keeping

records in an organized manner will be solved. The greatest of all is the retrieval
of information, which will be at the click of the mouse. So the proposed system
helps in saving the time in different operations and making information flow easy
giving valuable reports.

Data Dictionary:

This is normally represented as the data about data. It is also termed as

metadata some times which gives the data about the data stored in the
database. It defines each data term encountered during the analysis and
design of a new system. Data elements can describe files or the processes.

Following are some major symbols used in the data dictionary

 = equivalent to
 + and
 [] either/ or
 () Optional entry

Following are some rules, which defines the construction of data

dictionary entries:

1. Words should be defined to understand for what they need and not the
variable need by which they may be described in the program .
2. Each word must be unique. We cannot have two definition of the
same client.
3. Aliases or synonyms are allowed when two or more enters shows
the same meaning. For example a vendor number may also be called as
customer number.
4. A self-defining word should not be decomposed. It means that the
reduction of any information in to subpart should be done only if it is
really required that is it is not easy to understand directly.
Data dictionary includes information such as the number of records in file, the
frequency a process will run, security factor like pass word which user must
enter to get excess to the information.
Limitation of this report:

 Employees of supply chain are usually busy with their daily work and
activities, so it is quite impossible sometime to get time from them for getting
information about our report.

 Sometimes the authority does not provide their internal information which is
very difficult to collect from any other sources.

 Our group members were so busy because they had to make 2 or 3 reports.
That‘s why it was quite difficult to regroup and group study for making report.

 We did not have any proper financial support and limitation of time is also a
barrier for making this report.

 In the website, information about supply chain is not sufficient. 100%

accurate supply chain of Agora we could not collect.

Future scope of the Project:

 Delivery date and time have not been specified in our project which can be
included as a further enhancement to the project.

 Dealers can also have the authentications in the futher expansion.

 The entire functions are controlled by the Admin.only one report is generated
at a time.generation of more reports,keeping the day-wise schedule can also be
dine as part of future enhancement to this project.
Conclusion of the Project:

 This project has more scope in future and it can be integrated further

 This project is successfully implemented with all the features mentioned

earlier.

 This project is designed keeping in view the needs of the commen user and
satisfying the user upto the maximum extent possible.

 Deployement of our application will help the user to reduce the unneceaasry
wastage of time in going and ordering the product manuallly.

 Therefore we are successfully able to reach the goals and target of the
project.

Bibliography

 Google for problem solving

 http://www.javaworld.com/javaworld/jw-01-1998/jw-01-
Credentialreview.html
 Database Programming with JDBC and Java by O'Reilly
 Head First Java 2nd Edition
 http://www.jdbc-tutorial.com/
 Java and Software Design Concepts by Apress