Courier Management System

Project Submitted in partial fulfillment of the requirements of

Bachelor of Technology

Department of Computer Science

University of Delhi, Delhi
April 2017
Submitted By:

Satyam Soni: College Roll No 7808

Sudhanshu: Kumar College Roll No
Varsha: College Roll No No 7805
Renu: College Roll No 7806

1
 Project Report

POS System for Pharmacies

Work Carried at

Shaheed Sukhdev College of Business Studies

By

Satyam Soni , Sudhanshu Kumar , Varsha , Renu

Under the Joint Supervision of

Dr. Kavita Rastogi Dr. Sameer Annand

(Mentor) (Mentor)
Professor Professor
Dept. of Computer Science Dept. of Computer Science

Submitted in partial fulfillment of the requirements of

Bachelor of Technology
To
Shaheed Sukhdev College of Business Studies
University of Delhi
Delhi 110095

2
 CERTIFICATE

This is to certify that the project work entitled POS System for Pharmacies has been carried
out by Satyam Soni , Sudhanshu , Renu , Varsha in (7th Sem) Shaheed Sukhdev College of
Business Studies under the supervision of Dr.Kavita Rastogi and Dr .Sameer annand in
department of computer Science University of Delhi. This work has been carried out for the
partial fulfillment of the requirements of B.Tech (Bachelor of Technology ) degree in Department
of Computer Science, University of Delhi. This project has not been submitted anywhere for the
purpose of any other degree or diploma.

Signature: Signature:

Dr. Kavita Rastogi Dr. Sameer Anand

Associate Professor Associate Professor
Department of Computer Science Department of Computer
Science
University of Delhi University of Delhi

3
 ACKNOWLEDGEMENT

I take this opportunity to thanks colleagues and parents who were with me to help me out in
the entire major as well as the minor issues that were faced. They guided me on a lot of
aspects of work throughout the project duration. I wish to place on record my gratitude towards
Shaheed Sukhdev College of Business Studies, New Delhi for providing me
an opportunity to work on this project of such an importance. My stay in the organization has
been a great learning experience. This exposure has enriched me with a wide technical
knowledge and has also introduced me to the attributes of a successful professional life.
Im grateful Dr. Kavita Rastogi for his guidance and support for this Project work. I also
express my gratitude to the Dr. Sameer Anand , Head, Department of Computer Science,
University of Delhi for providing me with the opportunity to carry out this project work
in Shaheed Sukhdev College of Business Studies.

4
Table of Contents

1. Introduction.........................................................................................................................
1.1. Purpose of This Project...........................................................................................
1.2. Scope and Objects..................................................................................................
1.3. Overview.................................................................................................................
1.3.1 Login page.............................................................................................................
1.3.2 Dashboard Page....................................................................................................
1.3.3 Sales Page.............................................................................................................
1.3.4 Product Listing Page..............................................................................................
1.3.5 Suppliers page.......................................................................................................
1.3.6 Sales Report Page.................................................................................................
1.3.7 Sales Receipt.........................................................................................................
1.3.9 Product Inventory......................................................................................................
2. Feasibility Study for system Development.........................................................................
2.1 Technical Feasibility................................................................................................
2.2 Technical Feasibility................................................................................................
2.3 Operational Feasibility................................................................................................
3 . System Description..........................................................................................................
3.1 Objective & Need of the system..............................................................................
3.2 Advantages of the system.......................................................................................
3.3 System Requirements.............................................................................................
3.4 Database Design.....................................................................................................
4 Design of the System.........................................................................................................
4.1 Use Case Diagram..................................................................................................
4.2 Data flow Diagrams.................................................................................................
4.2.1 Level0 DFD............................................................................................................
4.2.2 Level1 DFD............................................................................................................
4.3 Architecture Diagram..............................................................................................
5 . Coding and Implementation.............................................................................................
5.1 Technology Used.....................................................................................................
5.2 Code Design............................................................................................................
6 . Testing..............................................................................................................................
7 . Conclusion and Future Scope..........................................................................................
7.2 Future Scope...........................................................................................................
8 . References.....................................................................................................................

5
 1. Introduction

Courier Management System is the simplest solution for Courier & Cargo Tracking Business.
This Courier Management System project will have different modules.
The login section will have login facility for the admin who will operate this system and online
tracking system of consignment and shipping detail for domestic shipping.
While taking orders from its customers, it will take all the details of its customers who is placing
the orders and all the details for the recipient such as its address,name,mobile number.

During billing process, system generates a consignment number for their products. Through
this consignment no. customers or its recipient will able to track their products from any
location using internet.

It will provide status of the product after placing orders.

This Courier Management System project will provide information recipient with following detail
where the current consignment is,till when it will reached its final destination, date of placing
consignment , final date to reach its destination etc

1.1. Purpose of This Project

This document outlines the software requirements for the Chemist management system
for the D-Watson Chemist. It describes the functional and non-functional requirements,
modeling requirements, diagrams and user profiles of the proposed system.

The Chemist Management System enables D-watson staff to maintain computerized

Record Of Customer who visits, their Employees & product. It also performs quick
search for their products, manages counter sales and Keep record of salesman. This
SRS provides detailed information on the internal and external view of the system as
well as interfaces required by Chemist Management System.

1.2. Scope and Objects

6
 As this is generic software it can be used by a wide variety of outlets (Retailers and
Wholesalers) to automate the process of manually maintaining the records related to the
subject of maintaining the stock and cash flows.

This project is basically updating the manual chemist inventory System to Automated
inventory system, So that organization can manage their record in efficient and
organized form.

This software helps you to track all the products of medical shop moreover its a medical
shop accounting software. Flexible and adaptive software suited to medical shops or
stores or pharmacies of any size.

Project Characteristics:

Customer management

Sales management

Reporting

1.3. Overview
Login Page
Dashboard
Product Listing Page (PLP)
Sales Page
Suppliers Page
Sales Report Page
Bill Print Style

1.3.1 Login page

7
 1.3.2 Dashboard Page

After logging in, user is allowed to visit to Dashboard page.

Home page consists of:

Product Listing Page (PLP)

Sales Page
Suppliers Page
Sales Report Page

8
1.3.3 Sales Page

9
 1.3.4 Product Listing Page

Once u select a category, you are directed to Product Listing Page (PLP). Product
listing page lists all the products of a particular category.

10
1.3.5 Suppliers page

11
1.3.6 Sales Report Page

1.3.7 Sales Receipt

12
1.3.9 Product Inventory

13
2. Feasibility Study for system
Development

A feasibility study refers to the implementation of the project. Can the project be
implemented? if yes, then what technology we should, are we capable of using that
technology, can that technology meet the system specification etc. Feasibility is the study of
impact, which happens in the organization by the development of a system. The impact can be
either positive or negative. When the positives nominate the negatives, then the system is
considered feasible.

Three key factors are to be considered during the feasibility study:

2.1 Technical Feasibility

Evaluating the technical feasibility is the trickiest part of a feasibility study. This is because, at
this point in time, not too many detailed design of the system, making it difficult to access
issues like performance, costs on (on account of the kind of technology to be deployed) etc. a
number of issues have to be considered while doing a technical analysis. The main
consideration is to be given to the study of available resources of the organization where the
software is to be implemented. Here the system analyst evaluates the technical merits of the
system giving emphasis on the performance, Reliability, maintainability and productivity.
We can strongly say that it is technically feasible, since there will not be much difficulty in
getting required resources for the development and maintaining the system as well. All the
resources needed for the development of the system as well as the maintenance of the same
is
available in the organization here we are utilizing the resources which are available already.

14
2.2 Technical Feasibility

Development of this application is highly economically feasible. The organization needed

not spend much m money for the development of the system already available. The only
thing is to be done is making an environment for the development with an effective
supervision. If we are doing so, we can attain the maximum usability of the
corresponding resources. Even after the development, the organization will not be in a
condition to invest more in the organization. Therefore, the system is economically
feasible.

2.3 Operational Feasibility

Proposed projects are beneficial only if they can be turned into information systems that
will meet the organizations operating requirements. Simply stated, this test of feasibility
asks if the system will work when it is developed and installed. Are there major barriers
to Implementation? Here are questions that will help test the operational feasibility of a
project:
Operational feasibility determines how much effort will be required in selling the
proposed system, and make it easily adoptable for the user. Since no such system
exists which is a freeware or performing so many tasks together and spying client
machine is essential these days in many areas and hence the system is behaviorally
feasible. Feasibility study of proposed system gave a satisfactory conclusion.
Our Feasibility analysis of this system involves 6 steps:-
Form a project team
Enumerate potential candidate system.

15
 Determine and evaluate performance and cost effectiveness of system.
Weight system performance and cost data.
Select the best system.

3 . System Description

3.1 Objective & Need of the system

The objective of the system is to create a Desktop or Laptop friendly platform Site.

3.2 Advantages of the system

The system once developed will provide a simple website to browse and take the
advantage of this System

3.3 System Requirements

Hardware Requirements
1. A high-end machine required with at least 2 GB RAM.
2. A high-end machine required with at least 2 GB RAM.
3. Processor CORE i3 (minimum) or AMD A8.

Software Requirements
1. Operating System Linux (Ubuntu 14.04) 64bit
2. Frontend Sublime Text (HTML, CSS, AngularJS)
3. Backend Eclipse (Java, Spring Framework)
4. Database MySQL
5. Web Server Apache Tomcat

16
3.4 Database Design

Entity Relationship Diagram for the System

An entityrelationship (ER) diagram is a systematic way of defining and describing a
business process. The business process is modeled as various entities, linked with
each other through relationships. The relationship between the entities expresses the
requirement and dependencies between them.

Table comments: collection

Column Type Nul Defau
l lt
transaction_ int(11) No
id
date varchar(10 No
0)
name varchar(10 No
0)
invoice varchar(10 No
0)
amount varchar(10 No
0)
remarks varchar(10 No
0)
balance int(11) No

Customer

17
Table comments: customer
Column Type Nul Defaul
l t
customer_id int(11) No
customer_name varchar(100 No
)
address varchar(100 No
)
contact varchar(100 No
)
membership_numbe varchar(100 No
r )
prod_name varchar(550 No
)
expected_date varchar(500 No
)
note varchar(500 No
)

Table comments: products

Column Type Null Default

product_id int(11) No
product_code varchar(200) No
gen_name varchar(200) No
product_nam varchar(200) No
e
cost varchar(100) No
o_price varchar(100) No
price varchar(100) No
profit varchar(100) No
supplier varchar(100) No
onhand_qty int(10) No
qty int(10) No
qty_sold int(10) No
expiry_date varchar(500) No
date_arrival varchar(500) No

18
Table comments: purchases
Column Type Nul Defau
l lt
transaction_id int(11) No
invoice_numb varchar(10 No
er 0)
date varchar(10 No
0)
suplier varchar(10 No
0)
remarks varchar(10 No
0)

Table comments: purchases item

Colum Type Nul Default

n l

id int(11) No
name varchar(100) No
qty int(11) No
cost varchar(100) No
invoice varchar(100) No
Table comments: sales

Column Type Nul Defaul

l t
transaction_id int(11) No
invoice_numbe varchar(100 No
r )
cashier varchar(100 No
)
date varchar(100 No
)
type varchar(100 No
)
amount varchar(100 No
)
profit varchar(100 No

19
 )
due_date varchar(100 No
)
name varchar(100 No
)
balance varchar(100 No
)

Table comments: sales_order

Column Type Null

transaction_i int(11) No
d
invoice varchar(100) No
product varchar(100) No
qty varchar(100) No
amount varchar(100) No

profit varchar(100) No
product_code varchar(150) No
gen_name varchar(200) No
name varchar(200) No
price varchar(100) No
discount varchar(100) No
date varchar(500) No

Table comments: supliers

Column Type Nul Defaul

l t
suplier_id int(11) No
suplier_name varchar(100 No
)
suplier_addres varchar(100 No
s )
20
suplier_contac varchar(100 No
t )
contact_perso varchar(100 No
n )
note varchar(500 No
)

Table comments: user

Colu Type N Def

mn ul ault
l
id int(11) No
usern varchar( No
ame 100)
passw varchar( No
ord 100)
name varchar( No
100)
positi varchar( No
on 100)

4 . Design of the System

21
4.1 Context level diagram

4.2 Context Analysis Diagram

22
4.3 LOGICAL DFD

4.3.1 Level0 DFD

23
4.3.2 Level1 DFD

4.3.3 Level2 DFD

24
4.4 Architecture Diagram

Presentation Layer: The presentation layer contains components required to interact with the
user of the application. In response to the request made, Spring MVC composes JSP/HTML to
send back HTTP response.

Business Layer: The business layer encapsulates the core business functionality of the
application. The business components/services are generally invoked via system interfaces or
web layer.

Data Access Layer: The data access layer provides EPP services to access and manipulate
data. Service layer and system interfaces interact with the data via Hibernate and MySQL to
generate the data access layer for applications. These data access objects use the Hibernate
API to convert database records into objects and viceversa. Applications store their data in one
or more data stores. Databases and file systems are two very common types of data stores.

25
System Architecture
This architecture diagram describes the overall functionality of the Employee Points Program
(EPP) component. The select.snapdeal.com interacts to different components in order to
process the requests made by the EPP. This service uses a load balancer to forward requests
and manages the workload across different application servers. Distributing the load will
increase the system reliability and performance.

EPP is served by two web servers, which can be increased to N number during to process large
number of requests.

The load balancer distributes the requests between these two web servers evenly. These web
servers interact directly with the MySQL database for the required information and appropriate
responses are then sent back to the respective users. Apart from this, EPP also interacts with
different components database, such as, OMS, CaMS, UMS, IPMS, CoCoFS, and ExCOMM in
order to process pertinent requests.

These databases act as central repository for the EPP. The data is extracted from central
repository and loaded to the application server and again transformed into the formats required
by the EPP service. The transformed data then loaded to the EPP.

Additional technical details concerning this architecture are given as follows:

26
27
 5 . Coding and Implementation

5.1 Technology Used

CSS
CSS is an excellent addition to plain HTML. With CSS you define the colors and sizes
in "styles". Then as you write your documents you refer to the styles. Therefore: if you
change a certain style it will change the look of your entire site. Another big advantage
is that CSS offers much more detailed attributes than plain HTML for defining the look
and feel of your site.

Ajax
Ajax is not a single technology, but a group of technologies. HTML and CSS can be
used in combination to markup and style information. The DOM is accessed with
JavaScript to dynamically display, and allow the user to interact with, the information
presented. JavaScript and the 13XMLHttpRequest object provide a method for
exchanging data asynchronously between browser and server to avoid full page reload

Jquery
jQuery is a fast and concise JavaScript library created by John Resig in
2006.jQuery simplifies HTML document traversing, event handling, animating,
and Ajax interactions for Rapid Web Development.jQuery is a JavaScript
toolkit designed to simplify various tasks by writing less code

Javascript
JavaScript (JS), also known as ECMAScript (the untrademarked name used for the
standard), is a dynamic programming language. It is most commonly used as part of
web browsers, whose implementations allow clientside scripts tointeract with the user,
control the browser, communicate asynchronously, and alter the document content that
is displayed. It is also used in serverside network programming with runtime
environments such as Node.js, game development and the creation of desktop and

28
mobile applications. JavaScript is classified as a prototypebased scripting language
with dynamic typing and firstclass functions. This mix of features makes it a multi-
paradigm language, supporting objectoriented, imperative, and functional programming
styles. Despite some naming, syntactic, and standard library similarities, JavaScript and
Java are otherwise unrelated and have very different semantics. The syntax of
JavaScript is actually derived from C, while the semantics and design are influenced by
the Scheme programming languages. JavaScript is also used in environments that
aren't webbased, such as PDF documents, sitespecific browsers, and desktop widgets.
Newer and faster JavaScript virtual machines (VMs) and platforms built upon them
have also increased the popularity of JavaScript for serverside web applications. On
the client side, JavaScript has been traditionally implemented as an interpreted
language, but more recent browsers perform justintime compilation.

Spring MVC web framework (angularJS)

The Spring Web MVC framework (Spring MVC) is a rich model view controller web
framework.
Spring MVC lets us create a special @Controller bean to handle all incoming HTTP
requests. The methods in our controller are mapped to HTTP using @RequestMapping
annotation.
The MVC pattern of Spring framework results in separating the different aspects of the
application (namely, input logic, business logic and UI logic), while providing a loose
coupling between these elements.
The Model encapsulates the application data and in general they will consist of
POJO.
The View is responsible for rendering the model data and in general it generates
HTML output that the client's browser can interpret.
The Controller is responsible for processing user requests and building
appropriate model and passes it to the view for rendering.

29
5.2 Code Design

Frontend

Backend

30
31
6 . Testing
It is the major quality control measure employed during software development. Testing is the
process of executing a program with the intention of finding an error. No piece of code is
completely ready unless it has been fully tested. This stage is very important as it is certified
whether the code developed meet the requirement specification or not. More over validations
are also checked in the testing stage

Need For Testing

Testing is vital to the success of the system. Testing may the logical assumption that all the part
of the system are correct and the goal is successfully achieved. Inadequate testing leads to
then error that may not appear until month later. A small system error can explode into a much
larger problem. Second reason for testing is its utility as an user-oriented vehicle before
implementation. Finally testing leads to software reliability. This increases user confidence in
the system.

The basic levels of testing are

Functional Testing

Structural Testing

Unit Testing

Integrity Testing

These different levels of testing attempt to detect different types of faults. The relation of faults
introduced in different phases and different levels of testing are shown here.

6.1 Functional Testing

This testing was done on a large scale. Each and every form of the project was tested to
check whether it performs the associated function in a proper manner for which it has been
prepared. In functional testing the structure of the program is not considered. Test cases are

32
 decided on the basis of the requirements or specification of the program code or module
and the internal of the module or the program are not considered for selection of test cases.
This is often called black box testing. Test case for functional testing are decided from the
module specification produced from the design.

6.2 Structural Testing

It is considered with testing the implementation of the program. The structural testing is not
to exercise all the different input/output conditions but to exercise the different programming
structure used in the program. This is also known as glass-box testing and white box testing
methods and is conducted to ensure that:

All independent paths within a module have been exercised at least once.

All logical decisions on their true and false sides are exercised.

Loops are executed at their boun daries and within their operational bounds.

When I test the program there were various errors, some of the those errors are reported in this
report like:

1. Accessing the private data members outside the class

2. Functions prototype mismatching.

6.3 Unit Testing

A unit is the smallest testable part of software. It usually has one or a few inputs and
usually a single output. In procedural programming a unit may be an individual program,
function, procedure, etc. In object-oriented programming, the smallest unit is a method,
which may belong to a base/ super class, abstract class or derived/ child class. (Some treat
a module of an application as a unit. This is to be discouraged as there will probably be
many individual units within that module.)

33
6.4 Integrity Testing

The goal was to detect and mitigate the effects of hardware failure. I
commented that further work could be done to address the issue of software
failure and this would need to wait until a future occasion.

7. Conclusion and Future Scope

7.1. Conclusion It has been a wonderful learning experience working with such
competent people. I feel fortunate for getting the opportunity to work on a live, realtime project
from its very inception. The opportunity brought to light, the real Software Development Life
Cycle as it exists in the industry, today. The thesis work exposed the benefits and the
limitations associated with various software tools and resources, available in the market today.
I have learnt that selecting the right approach and the right tools for developing software, is a
tedious job, and has a significant impact on the overall quality of the software product. What
may be a good solution for an application may not turn out to be the best for another. The most
important realization was the amount of cooperation, dedication, hard work, and team spirit,
diligence that goes into making of a successful project.

To conclude, I would just like to say that, I have never things as I have learnt in this very
short period of time. The thesis is gelled together with many computer science
concepts that we study, but rarely get the opportunity to implement in one application.

Developers always try to design their product as userfriendlier as they can, but unless
and until the user uses product, developers cannot preexamine every flaw that may
later be encountered. The difference may result in user dissatisfaction, as by the time
user receives final product, user needs may have changed. So the result of
communication gap and time difference in product developing & product receiving may
lead to errors.

And as in this field, technology changes every day, developer can never ensure
complete satisfaction to the user. But the product has been built in such a way that it
can be enhanced with ease, as the overall approach followed is object-oriented and
flexible enough to incorporate modifications

34
7.2 Future Scope

Integrate all online payment mode

Bar Code Scanner
Integrate promotional Code
Item Return
Integrate all features of listing, search, sort and product details
Customized site for individual corporate
Capability to offer different pricing for each corporate
Premium, customized packaging corporates
Brand store for different brands

8. References
DataSoft Institute Jhansi
SSCBS College Library Books
https://www.tutorialspoint.com
http://www.w3schools.com http://msdn.microsoft.com
http://www.stackoverflow.com
https://www.coursera.org

35