A PROJECT REPORT

ON
Medical Store Management System
Presented and Submitted By

Tafseer Alam Shah

PRN No. 04419002303
Tauqeer Ramzan khan
PRN No. 04419001452
Bachelor of Computer Application

Vikas College Study Center,

Vikhroli (East),

Tilak Maharashtra Vidayapeeth, Pune

Faculty of Distance Education
2021-2022
 A PROJECT REPORT
ON
Medical Store Management System
Presented and Submitted By

Tafseer Alam Shah

PRN No. 04419002303
Tauqeer Ramzan khan
PRN No. 04419001452
Towards The Partial Fulfilment of the
Bachelor of Computer Application

Vikas College Study Center,

Vikhroli (East),

Tilak Maharashtra Vidayapeeth, Pune

Faculty of Distance Education
2021-2022

TILAK MAHARSHTRA VIDYAPEETH,

 (‘Deemed University’ under section 3 of UGC Act 1956 vide notificationNO.F 9-
19/85-U3 dated 24th April 1987 by the Government of India) Vidyapeeth Bhavan,
Gultekdi, Pune- 411 037

CERTIFICATE

This is to certify that project

“Medical Store Management System”
Has been satisfactory completed
by
Tafseer Alam Shah
PRN NO : 04419002303

Tauqeer Ramzan Khan

PRN NO : 04419001452

Towards the partial fulfilment of the “Bachelor Of Computer Application”,

For the Academic Year [2021-2022] at [Vikas College Study Centre],

city [Vikhroli],Tilak Maharashtra Vidyapeeth, Pune (Faculty of Distance

Education),

And is approved.
……………………………………………………………………………………….

Project Guide Examiner Head Of Departmen

Vikas College – Vikhroli
 Vidya Vikas Education Society’s

VIKAS COLLEGE STUDY CENTRE

Vikas High School Marg, Kannamwar Nagar No.2, Vikhroli (East), Mumbai – 400 083.

Prof. Vikas P.Raut Shri.P.M.RAUT

Study Centre Co-ordinator Chairman, V.V.E. Society

CERTIFICATE
THIS IS TO CERTIFY THAT THE PROJECT

“MEDICAL STORE MANAGEMENT”

HAS BEEN SATISFACTORILY COMPLETED BY

TAFSEER ALAM SHAH (PRN NO : 04419002303) SEAT NO : 1684

TAUQEER RAMZAN KHAN (PRN NO : 04419001452) SEAT NO : 1696

TOWARD THE PARTIAL FULFILMENT OF THE

“ BACHELOR OF COMPUTER APPLICATION ”,

FOR THE ACADEMIC YEAR [2021-2022] AT VIKAS COLLEGE,VIKHROLI

TILAK MAHARASHTRA VIDYAPEETH, PUNE

(FACULTY OF DISTANCE EDU CATION), AND IT IS APPROVED.

PROJECT GUIDE EXAMINER HEAD OF DEPARTMENT

DEPARTMENT MR. VIKAS RAUT
Asma Qazi

Page | 4
 PROJECT SYNOPSIS

INTRODUCTION
The main goal of the application is to maintain the records of purchase ,
Sales and stock details with cash transaction Maintenance . Medical store
management is very needy for . Medical Store . this software help them
maintain day to day transaction in computer Medical Store Management
system is an application project develope for medical shops. This system is
field concerned with purchasing and selling medicines, The purpose of this
project is to reduce time consuption and human efforts. this application
provides user friendly interface as well.
FUNCTIONAL SPECIFICATION :
Login module : Used for managing for managing the login details.

Admin : admin can login in desktop application

Sales Reports : admin can check the daily reports of the user.

Sells modules : Used for managing the details of Sells

Purchase module : Supplier give the information about purchase item s information

Sales Process : Admin enter the sales information also check the details in retrieve from the
sales

User module : Used for managing for managing the user of system
Name of component Specification

Operating System : Windows 10

Language Used : java with swing

Database Mysql

Development Platform : Netbeans

Processore : Intel(R) Celeron(R) CPU N3060 @ 1.60GHz 1.60 GHz

Printer Options

Page | 5
 Acknowledgement

With Immense Pleasure We Are Presenting “Medical Store Management System”

Project Report As Part Of The Curriculum Of “Bachelor Of Computer

Application”. We Wish To Thank All The People Who Gave Us Unending

Support.

We Express Profound Thanks To Our Head Of Department Mr. “ Vikas Raut ”,

Project Guide And Project In charge Ms. “Asma Qazi ” And All Those

Who have Indirectly Guided And Helped Us In Preparation Of This Project.

Tafseer Alam Shah Tauqeer Ramzan Khan

PRN NO : 04419002303 PRN NO : 04419001452

Page | 6
 ABSTRACT

The "Medical Store Management System" has been developed to override the
problems prevailing in the participating manual system. This software is supported to
eliminate and in some cases reduce the hardships faced by the existing system.
Moreover this system is designed for the particular need of the store to carry out
operations in a smooth and effective manner. The application is reduced as much as
possible to avoid errors while entering the data. No formal knowledge is needed for
the user to use this system.

The main objective of the Medical Store Management System is to manage the
details of Medicine, See the Medical Sales Record. It manages all the Product
information . The project is totally built at administrative end and thus only the
administrator is guaranteed the access.

Page | 7
 INDEX

Chapter 1: Introduction.....................................................................................9
Chapter 2: Need New For System...................................................................12
Chapter 3: Feasibility Study............................................................................16
Chapter 4: Technology Review........................................................................19
Chapter 5: SDLC Life Cycle............................................................................20
Chapter 6: Software Development Model......................................................28
7.1: Structure of Waterfall Model....................................................................34
7.2: Waterfall Model – Design........................................................................34
7.3: Advantages of the Waterfall Model.........................................................37
7.4: Disadvantages of the Waterfall Model....................................................38
Chapter 7: Stakeholder....................................................................................40
Chapter 8: Gantt Chart....................................................................................47
Chapter 9: UML Diagrams.............................................................................57
9.1.1: ER Diagram...........................................................................................58
9.1.2: Use-Case Diagram.................................................................................60
9.1.3: Data Flow Diagram...............................................................................64
9.1.4: Activity Diagram...................................................................................69
9.1.5: Sequence Diagram.................................................................................71
9.1.6: Component Diagram.............................................................................74
Chapter 10: Data Structures Screenshorts.....................................................76
Chapter 11: Code..............................................................................................97
Chapter 12: Project Screen Shorts..................................................................84
Chapter 13: Testing and Validations..............................................................95
Chapter 14: Limitations and Future Enhancements.....................................99
Chapter 15: Conclusion....................................................................................97
Chapter 16: Bibilography................................................................................97

Page | 8
 Chapter 1
Introduction

The main goal of the application is to maintain the records of purchase

, Sales and stock details with cash transaction Maintenance . Medical store

Page | 9
management is very need for . Medical store . this software help them
maintain day to day transaction in computer
Medical Store Management system is an application project develope
for medical shops. This system is field concerned with purchasing and
selling medicines,
The purpose of this project is to reduce time consuption and human
efforts. this application provides user friendly interface as well.
The software requirment Specification is a document that describe
the external requirement for any system . the requirement analysthas to
identify the Requirement by taking to the client and understading
In the present time, the medical stores are looking for the services
that are accurate and reliable for providing services to the customers and
workers. Every store is making efforts to computerize their activities for
providing better services to the customers. The medical store management
system is the system used for medicine stock inventory in the medical
stores. This system enables the manager of the store to record and manage
all activities of the medical store.

Page | 10
 Chapter 2
Need For
New System

It helps in current all works relative to Medical Store Management System. The first
subsystem is a Supplier which has all the details of all the suppliers of a particular
Medical Shop. The second subsystem is Medicines. The third subsystem is Reports
which generates reports for all suppliers and the pharmacists. This Medical Store

Page | 11
Java project aims at Business process automation, i.e. I have tried to computerize the
various process of the Medical Store Management System.

IMPLEMENTATION
This Medical Store project implementation is done in java language which consists of
several classes as mentioned below to perform several operations.

Login

Allows the administrator to login into the Medical Store Management System
software with a valid user and user I’d , password

Add New Medicines

Allows the administrator to add the new medicines

Search Medicine

Allows the administrator to search the medicines with the Medicine batch number or
Medicine name

Delete Supplier

Allows the administrator to delete the record of the existing supplier

Delete Medicine

Allows the administrator to delete the record of the existing medicines

Update Supplier

Allows the administrator to update the record of the existing suppliers

Update Medicines

Allows the administrator to update the record of the existing medicines

Medicine List

Page | 12
Allows the administrator to view the records of the medicines

Daily Purchase Report

Allows the administrator to view the records of the medicines by entering the
Medicine Purchase Date

New sales

Allowo the Purchase Medicine And add Cart

Page | 13
 Chapter 3
Feasibility
Study

3.1 Technical Feasibility

The minimum hardware requirement to implement the system is AMD A6 processor
with 4 GB RAM. The whole system is being developed on Apache NetBeans for
GUI (Front End) and uses MySQL workbench and MySQL for Database. These are
the software which are very popular and easily available in market

Page | 14
3.2 Economical Feasibility
It is cost effective system . No extra efforts are needed to train for using the system .
This system is quite beneficial with respect to its cost. The user shall be conversant
with computer technology . The system is user friendly and thus easy to use and
operate

3.3 Operational Feasibility

This system will reduce the workload and loss of vital information. It is time saving
and will aid the Customer to be system generated rather than person dependent . Data
retrieval and data presenting will be done by the system so the report generation will
be automated .

Page | 15
 Chapter 4
Technology
Review

4.1 Programming Language :

Java is a popular programming language, created in 1995.

It is owned by Oracle, and more than 3 billion devices run Java.
It is used for:
 Mobile applications (specially Android apps)

Page | 16
  Desktop applications
 Web applications
 Web servers and application servers
 Games
 Database connection
 And much, much more
Java works on different platforms (Windows, Mac, Linux, etc.)
 It is one of the most popular programming language in the world
 It is easy to learn and simple to use
 It is open-source and free
 It is secure, fast and powerful
 It has a huge community support (tens of millions of developers)
 Java is an object oriented language which gives a clear structure to programs
and allows code to be reused, lowering development costs

4.2 Database :

MySQL Workbench is used to design database for the proposed Medical Store
Management System. MySQL language and Relational Data Base Management
System(RDBMS) are used to set the foundation of system’s back end . RDBMS is
the basis for MySQL, and for all modern database systems such as MySQL, Oracle,
and Microsoft Access .
The data in RDBMS is stored in database objects called tables . A table is a
collection of related data entries and it consists of columns and rows .

Page | 17
 Structured Query Language (MySQL) is a standard Database language which is
used to create, maintain and retrieve the relational database . It is particularly used to
work with structured data where there are relations associated within the data itself .
MySQL being distributed database language, Distributed Database
Management Systems use MySQL to distribute data across multiple connected
computer systems . In the proposed system, MySQL serves as the link between
“front-end” computer systems optimized for user interaction and “back - end”
systems specialized for database management .

MySQL :
 MySQL lets you access and manipulate databases .
 MySQL was founded by Allan Larsson, Michael Widenius and David Axmark in
the year 1995.

Page | 18
 Chapter 5
SDLC Life
Cycle

SDLC is a process followed for a software project, within a software organization. It

consists of a detailed plan describing how to develop, maintain, replace and alter or
enhance specific software. The Software Development Life Cycle defines a
methodology for improving the quality of software and the overall development
process.

Page | 19
 The following figure is a graphical representation of various stages of a typical
SDLC.

Chapter 6
Page | 20
 Software
Development
Model

To solve actual problems in an industry, it is imperative to adopt a

development strategy that encompasses the process, methods and tool layers. The
strategy is incorporated by software engineer and his team and is called Software
Development Life Cycle (SDLC). It aims to produce high-quality software that meets
or exceeds customer expectations, reaches completion within times and cost
estimates .
Software Development Process Models are defined
and designed and are meant to be followed during the software development process .
Following are the most important and popular SDLC models followed in the
industry

Page | 21
➢ Waterfall Model : The Waterfall Model was the first Process Model to be
introduced. It is also referred to as a linear-sequential life cycle model. It is very
simple to understand and use. In a waterfall model, each phase must be completed
before the next phase can begin and there is no overlapping in the phases

➢ Iterative Model : In the Iterative model, iterative process starts with a

simple implementation of a small set of the software requirements and iteratively
enhances the evolving versions until the complete system is implemented and ready
to be deployed.
An iterative life cycle model does not attempt to start with a full
specification of requirements. Instead, development begins by specifying and
implementing just part of the software, which is then reviewed to identify further
requirements. This process is then repeated, producing a new version of the software
at the end of each iteration of the model.

➢ Spiral Model : In the Iterative model, iterative process starts with a simple
implementation of a small set of the software requirements and iteratively enhances
the evolving versions until the complete system is implemented and ready to be
deployed.

An iterative life cycle model does not attempt to start with a full specification of
requirements. Instead, development begins by specifying and implementing just part
of the software, which is then reviewed to identify further requirements. This process
is then repeated, producing a new version of the software at the end of each iteration
of the model .

➢ RAD Model : The RAD (Rapid Application Development) model is

based on prototyping and iterative development with no specific planning involved.
The process of writing the software itself involves the planning required for
developing the product.
Rapid Application Development focuses on gathering customer requirements
through workshops or focus groups, early testing of the prototypes by the customer
using iterative concept, reuse of the existing prototypes (components), continuous
integration and rapid delivery.

Page | 22
➢ V – Model : The V-model is an SDLC model where execution of
processes happens in a sequential manner in a V-shape. It is also known as
Verification and Validation model.
The V- Model is an extension of the waterfall model and is
based on the association of a testing phase for each corresponding development
stage. This means that for every single phase in the development cycle, there is a
directly associated testing phase. This is a highly-disciplined model and the next
phase starts only after completion of the previous phase

6.1 Structure of Waterfall Model :

The Waterfall Model was the first Process Model to be introduced . It is also referred
to as a linear - sequential life cycle model . It is very simple to understand and use.
In a waterfall model, each phase must be completed before the next phase
can begin and there is no overlapping in the phases.
The Waterfall model is the earliest SDLC approach that was used for
software development. The waterfall Model illustrates the software development
process in a linear sequential flow. This means that any phase in the development
process begins only if the previous phase is complete. In this waterfall model, the
phases do not overlap.

6.2 Waterfall Model – Design :

Waterfall approach was first SDLC Model to be used widely in

Software Engineering to ensure success of the project. In "The Waterfall" approach,
the whole process of software development is divided into separate phases. In this
Waterfall model, typically, the outcome of one phase acts as the input for the next
phase sequentially.

Page | 23
6.2.1 Requirement Gathering and Analysis :

All possible requirements of the system to be developed are captured in this

phase and documented in a requirement specification document.

6.2.2 System Design :

The requirement specifications from first phase are studied in this phase and the
system design is prepared. This system design helps in specifying hardware and
system requirements and helps in defining the overall system architecture.

6.2.3 Implementation :

With inputs from the system design, the system is first developed in small programs
called units, which are integrated in the next phase. Each unit is developed and tested
for its functionality, which is referred to as Unit Testing.

Page | 24
6.2.4 Integration and Testing :

All the units developed in the implementation phase are integrated into a system after
testing of each unit. Post integration the entire system is tested for any faults and
failures. 6.2.5 Deployment of system Once the functional and non-functional testing
is done; the product is deployed in the customer environment or released into the
market.

6.2.5 Deployment of system :

Once the functional and non-functional testing is done; the product is
deployed in the customer environment or released into the market
6.2.6 Maintenance :
There are some issues which come up in the client environment. To fix
those issues, patches are released. Also to enhance the product some better versions
are released. Maintenance is done to deliver these changes in the customer
environment.
All these phases are cascaded to each other in which progress is seen as
flowing steadily downwards (like a waterfall) through the phases. The next phase is
started only after the defined set of goals are achieved for previous phase and it is
signed off, so the name " Waterfall Model ". In this model, phases do not overlap.

6.3 Advantages of the Waterfall Model :

The advantages of waterfall development are that it allows for departmentalization

and control. A schedule can be set with deadlines for each stage of development and
a product can proceed through the development process model phases one by one.
Development moves from concept, through design, implementation, testing,
installation, troubleshooting, and ends up at operation and maintenance. Each phase
of development proceeds in strict order.
Some of the major advantages of the Waterfall Model are as follows –
• Simple and easy to understand and use

Page | 25
• Easy to manage due to the rigidity of the model. Each phase has specific
deliverables and a review process.
• Phases are processed and completed one at a time.
• Works well for smaller projects where requirements are very well understood.
• Clearly defined stages.
• Well understood milestones.
• Easy to arrange tasks.
• Process and results are well documented

6.4 Disadvantages of the Waterfall Model :

The disadvantage of waterfall development is that it does not allow much reflection
or revision. Once an application is in the testing stage, it is very difficult to go back
and change something that was not well-documented or thought upon in the concept
stage.

The major disadvantages of the Waterfall Model are as follows –

• No working software is produced until late during the life cycle.
• High amounts of risk and uncertainty.
• Not a good model for complex and object-oriented projects.
• Poor model for long and ongoing projects.
• Not suitable for the projects where requirements are at a moderate to high risk of
changing. So, risk and uncertainty is high with this process model.
• It is difficult to measure progress within stages.
• Cannot accommodate changing requirements.
• Adjusting scope during the life cycle can end a project.

Page | 26
 • Integration is done as a " big-bang ”. at the very end, which doesn't allow
identifying any technological or business bottleneck or challenges early.

Page | 27
 Chapter 7
stakeholders

It is a software that retains its original simplicity yet offers comprehensive business
functionalities such as search produt, create user account , transaction , managing
sales record, are the functionalities uses there

Following are the important stakeholders in our project:

1) Admin :
Admin is owner and the manager of software. Admin is allowed to update
and modify.

Page | 28
2) User:
They are the ones who uses software as per their requirement .
3) Developer :
Builds the whole application.
4) Tester:
This is the one who tests the software. In our project, we developed as well
as tested our own application

Page | 29
 Chapter 8
Gantt Chart

Gantt chart provides a graphical illustration of a schedule that helps to

plan, coordinate, and track specific tasks in a project .

A Gantt chart is constructed with a horizontal axis representing the

total time span of the project, broken down into increments (months) and a
vertical axis representing the tasks that make up the project
MEDICAL STORE MANAGEMENT

It depicts our Project Development Road Map based on task

scheduling right from Preliminary Research up to Project Submission .

Page | 30
Timelines are indicated that show the time required for the completion of each
and every module . It gives a clear idea as to how our project development is
phased out on modules to summaries the entire Project Assessment .

Page | 31
 Chapter 9
UML
DIAGRAMS

The Unified Modeling Language is a standard visual modeling

language intended to be used for modeling business and similar processes,
analysis, design, and implementation of software-based systems .

UML is a common language for business analysts, software architects

and developers used to describe, specify, design, and document existing or new
business processes, structure and behavior of arti-facts of software systems .

Page | 32
 UML defines various kinds of diagrams to cover most of the aspects of
a system. There are two broad categories of diagrams and they are again
divided into subcategories −

Structural Diagrams :

The structural diagrams represent the static aspect of the system. These
static aspects represent those parts of a diagram, which forms the main
structure and are therefore stable .

1. Class diagram

2. Object diagram

3. Component diagram

4. Deployment diagram

Behavioural Diagrams :
Behavioural diagrams basically capture the dynamic aspect
of a system . Dynamic aspect can be further described as the
changing/moving parts of a system .

Page | 33
UML has the following five types of behavioral diagrams :

1. Use - Case Diagram

2. Sequence Diagram

3. Collaboration Diagram

4. State - Chart Diagram

5. Activity Diagram

9.1 E-R Diagram

The ER or (Entity Relational Model) is a high-level

conceptual data model diagram . Entity- Relation model is based on
the notion of real-world entities and the relationship between them .

ER modeling helps to analyze data requirements

systematically to produce a well-designed database . So, it is ideal
to complete ER modelling before implementing your database .

Page | 34
 Entity relationship diagram displays the relationships of

entity set stored in a database. This model is based on three basic

concepts :

1. Entities : A real-world thing either living or nonliving

that is easily recognizable and unrecognizable .

2. Attributes : It is a single-valued property of either an

entity-type or a relationship- type. However there exist
multi-valued attributes too .

3. Relationships : Relationship is nothing but an association among

two or moreentities .

9.1.1. Cardinalities :

Cardinality defines the number of entities in one entity set, which

can be associated with the number of entities of other set via

relationship set .

One – to - One − One entity from entity set A can be associated

with at most one entity of entity set B and vice-versa .

Page | 35
One – to - Many − One entity from entity set A can be
associated with more than one entities of entity set B however an
entity from entity set B, can be associated with at most one entity .

Many – to - One − More than one entities from entity set A can
be associated with at most one entity of entity set B, however an
entity from entity set B can be associated with more than one entity
from entity set A .

Many – to - Many − One entity from A can be associated with

more than one entity from B and vice versa .

E-R Diagram

Page | 36
 An entity relationship diagram ( ERD ) shows the
relationships of entity sets stored in a database . An entity in this context
is an object, a component of data . An entity set is a collection of similar
entities . These entities can have attributes that define its properties .

By defining the entities, their attributes, and showing the relationships between
them, an ER diagram illustrates the logical structure of databases

9.2 Use - Case Diagram

Page | 37
 A use case is a methodology used in system analysis to identify, clarify
and organize system requirements. The use case is made up of a set of possible
sequences of interactions between systems and users in a particular environment
and related to a particular goal. The method creates a document that describes all
the steps taken by a user to complete an activity .

Use cases are typically written by business analysts and can be employed during
several stages of software development, such as planning system requirements, validating
design, testing software and creating an outline for online help and user manuals. A use case
document can help the development team identify and understand where errors may occur
during a transaction so they can resolve them.

Every use case contains three essential elements:

The actor. The system user this can be a single person or a group of people interacting with the
process .

The goal. The final successful outcome that completes the process .
The system. The process and steps taken to reach the end goal, necessary functional
requirements and their anticipated behaviors .

A use case should display the following characteristics :

Organizes functional requirements .
Models the goals of system/actor interactions .
Records paths -- called scenarios -- from trigger events to

Describes one main flow of events and various alternate flows .

Multi-level, so that one use case can use the functionality of another

Page | 38
Page | 39
9.3 Class Diagram

Class diagram is a type of static structure diagram that describes the structure

of a system by showing the system's classes, their attributes, operations (or

methods), and the relationships among objects .

A UML class diagram is made up of :

1. Set of classes
2. Set of relationships between classes

A class notation consists of three parts :

1.Class Name :
The name of the class appears in the first partition.

2.Class Attributes :

Attributes are shown in the second partition .

The attribute type is shown after the colon .
Attributes map onto member variables (data members) in code .

3.Class Operations (Methods) :

Operations are shown in the third partition. These are the services a class
provides .The return type of a method is shown after the colon at the end of the method
signature .The return type of method parameters are shown after the colon following the
parameter name .

Page | 40
Page | 41
9.6 Sequence Diagram :

A sequence diagram simply depicts interaction between objects in a

sequential order i.e. the order in which these interactions take place. Sequence
diagrams describe how and in what order the objects in a system function .

These diagrams are widely used by businessmen and software developers to document and

understand requirements for new and existing systems .

9.6.1 Sequence Diagram Notations :

Actors – An actor in a UML diagram represents a type of role where it

interacts with the system and its objects .

Lifelines – A lifeline is a named element which depicts an individual

participant in a sequence diagram .

Messages – Communication between objects is depicted using messages.

The messages appear in a sequential order on the lifeline

9.6.2 Use of Sequence Diagrams :

1. Used to model and visualize the logic behind a sophisticated

function, operation or procedure .
2. They are also used to show details of UML use case diagrams .

3. Used to understand the detailed functionality of current or future systems .

Page | 42
Page | 43
9.7 Activity Diagram
Activity diagram is basically a flowchart to represent the flow from
one activity to another activity. The activity can be described as an operation
of the system.The control flow is drawn from one operation to another. This
flow can be sequential, branched, or concurrent. Activity diagrams deal with
all typ+e of flow control by using different elements such as fork, join, etc

Activity is a particular operation of the system. They are used tconstruct

the executable system by using forward and reverse engineering techniques .

9.7.1 The purpose of an activity diagram is

1. To Draw the activity flow of as system .

2. Describe the sequence from one activity to another .

3. Describe the parallel, branched and concurrent flow of the system .

9.7.2 Activity Diagram consists of following elements

4. Activities

5. Association

6. Conditions

7. Constraints

Activity diagram is suitable for modeling the activity flow of the

system. Activity diagram also captures these systems and describes the flow
from one system to another. This specific usage is not available in other
diagrams. These systems can be database, external queues, or any other
system.

Activity diagram can be used for −

Page | 44
1. Modeling workflow by using activities .

2. Modeling business requirements .

3. High level understanding of the system's functionalities .

4. Investigating business requirements at a later stage .

Page | 45
Activity Diadram

Page | 46
Chapter 10 :
MySQL Data
Structures Screen-
Shots

Page | 47
1] Login :

2] Company Detail Table :

Page | 48
3] product Detail Table :

4] product_category :

Page | 49
5] sales_record :

6] user Detail Table :

Page | 50
Chapter 12
Project Screen
Shorts

Page | 51
Logiun page

Medicines add Delete and Update

Page | 52
Companies Add Delete and Update

View Sale Records

Page | 53
New Sales

Change Password

Page | 54
Create User

Page | 55
 Chapter 11
Code

Login Page

import java.awt.Toolkit;

Page | 56
import java.awt.event.WindowEvent;
import java.sql.*;
import javax.swing.ImageIcon;
import javax.swing.JFrame;
import javax.swing.JOptionPane;
import javax.swing.UIManager;
public class Login extends javax.swing.JFrame {
Connection conn = null;
PreparedStatement pst = null;
ResultSet rs = null;
static String username;
public Login() {
initComponents();
conn = ConnectionToDatabase.connectToDb();
this.setExtendedState(this.getExtendedState() | JFrame.MAXIMIZED_BOTH);
}
public void close(){
WindowEvent we = new WindowEvent(this,WindowEvent.WINDOW_CLOSING);
Toolkit.getDefaultToolkit().getSystemEventQueue().postEvent(we);
}
private void initComponents() {
LoginPanel = new javax.swing.JPanel();
userTxt = new javax.swing.JTextField();
jLabel2 = new javax.swing.JLabel();
passTxt = new javax.swing.JPasswordField();
jLabel3 = new javax.swing.JLabel();
loginBtn = new javax.swing.JButton();
setDefaultCloseOperation(javax.swing.WindowConstants.DISPOSE_ON_CLOSE);
setTitle("Medical Store Management System");

Page | 57
 setResizable(false);
LoginPanel.setBackground(new java.awt.Color(255, 255, 255));
LoginPanel.setBorder(javax.swing.BorderFactory.createTitledBorder(null, "Sign In
here", javax.swing.border.TitledBorder.DEFAULT_JUSTIFICATION,
javax.swing.border.TitledBorder.DEFAULT_POSITION, new java.awt.Font("Calibri", 0,
14), new java.awt.Color(102, 0, 0))); // NOI18N
LoginPanel.setFont(new java.awt.Font("Calibri", 0, 14)); // NOI18N
userTxt.setFont(new java.awt.Font("Calibri", 0, 14)); // NOI18N
jLabel2.setFont(new java.awt.Font("Calibri", 0, 14)); // NOI18N
jLabel2.setText("Username");
passTxt.setFont(new java.awt.Font("Calibri", 0, 14)); // NOI18N
jLabel3.setFont(new java.awt.Font("Calibri", 1, 14)); // NOI18N
jLabel3.setText("Password");
loginBtn.setFont(new java.awt.Font("Calibri", 0, 14)); // NOI18N
loginBtn.setText("Login");
loginBtn.addActionListener(new java.awt.event.ActionListener() {
public void actionPerformed(java.awt.event.ActionEvent evt) {
loginBtnActionPerformed(evt);
}
});
javax.swing.GroupLayout LoginPanelLayout = new
javax.swing.GroupLayout(LoginPanel);
LoginPanel.setLayout(LoginPanelLayout);
LoginPanelLayout.setHorizontalGroup(

LoginPanelLayout.createParallelGroup(javax.swing.GroupLayout.Alignment.LEADING)
.addGroup(javax.swing.GroupLayout.Alignment.TRAILING,
LoginPanelLayout.createSequentialGroup()
.addContainerGap(34,
Short.MAX_VALUE) .addGroup(LoginPanelLayout.createParallelGroup(javax.sw
ing.GroupLayout.Alignment.TRAILING)
.addComponent(jLabel3)

Page | 58
 .addComponent(jLabel2))
.addGap(26, 26,
26) .addGroup(LoginPanelLayout.createParallelGroup(javax.swing.GroupLayout.Ali
gnment.LEADING)
.addComponent(loginBtn, javax.swing.GroupLayout.PREFERRED_SIZE, 148,
javax.swing.GroupLayout.PREFERRED_SIZE)
.addComponent(passTxt, javax.swing.GroupLayout.PREFERRED_SIZE, 213,
javax.swing.GroupLayout.PREFERRED_SIZE)
.addComponent(userTxt, javax.swing.GroupLayout.PREFERRED_SIZE, 213,
javax.swing.GroupLayout.PREFERRED_SIZE))
.addGap(60, 60, 60))
);

LoginPanelLayout.setVerticalGroup( LoginPanelLayout.createParallelGroup(javax.swing
.GroupLayout.Alignment.LEADING)
.addGroup(javax.swing.GroupLayout.Alignment.TRAILING,
LoginPanelLayout.createSequentialGroup() .addGroup(LoginPanelLayout.createPar
allelGroup(javax.swing.GroupLayout.Alignment.LEADING)
.addGroup(LoginPanelLayout.createSequentialGroup()
.addGap(80, 80, 80)
.addComponent(userTxt, javax.swing.GroupLayout.PREFERRED_SIZE,
javax.swing.GroupLayout.DEFAULT_SIZE,
javax.swing.GroupLayout.PREFERRED_SIZE))
.addGroup(LoginPanelLayout.createSequentialGroup()
.addGap(94, 94, 94)
.addComponent(jLabel2)))
.addGap(30, 30,
30) .addGroup(LoginPanelLayout.createParallelGroup(javax.swing.GroupLayout.Align
ment.BASELINE)
.addComponent(jLabel3)
.addComponent(passTxt, javax.swing.GroupLayout.PREFERRED_SIZE,
javax.swing.GroupLayout.DEFAULT_SIZE,
javax.swing.GroupLayout.PREFERRED_SIZE)) .addPreferredGap(javax.swing.Lay
outStyle.ComponentPlacement.RELATED, 142, Short.MAX_VALUE)

Page | 59
 .addComponent(loginBtn, javax.swing.GroupLayout.PREFERRED_SIZE, 33,
javax.swing.GroupLayout.PREFERRED_SIZE)
.addGap(21, 21, 21))
);
javax.swing.GroupLayout layout = new javax.swing.GroupLayout(getContentPane());
getContentPane().setLayout(layout);
layout.setHorizontalGroup(
layout.createParallelGroup(javax.swing.GroupLayout.Alignment.LEADING)
.addGroup(javax.swing.GroupLayout.Alignment.TRAILING,
layout.createSequentialGroup()
.addGap(0, 368, Short.MAX_VALUE)
.addComponent(LoginPanel, javax.swing.GroupLayout.PREFERRED_SIZE,
javax.swing.GroupLayout.DEFAULT_SIZE,
javax.swing.GroupLayout.PREFERRED_SIZE))
);
layout.setVerticalGroup(
layout.createParallelGroup(javax.swing.GroupLayout.Alignment.LEADING)
.addComponent(LoginPanel, javax.swing.GroupLayout.DEFAULT_SIZE,
javax.swing.GroupLayout.DEFAULT_SIZE, Short.MAX_VALUE)
);
pack();
setLocationRelativeTo(null);
}// </editor-fold>

private void loginBtnActionPerformed(java.awt.event.ActionEvent evt) {

try {
conn = ConnectionToDatabase.connectToDb();
String sql = "SELECT username,password FROM users WHERE username=? AND
password=?";
pst = conn.prepareStatement(sql);
pst.setString(1, userTxt.getText());

Page | 60
 pst.setString(2, passTxt.getText());
rs = pst.executeQuery();
username=userTxt.getText();
if (rs.next()) {
conn.close();
JOptionPane.showMessageDialog(null, "Welcome " + userTxt.getText());
MainPanel mp = new MainPanel();
mp.loggedInAsLbl.setText(userTxt.getText());
close();
mp.setVisible(true);
} else {
conn.close();
JOptionPane.showMessageDialog(null, "Please check your username and
password and try again!");
}
} catch (Exception e) {
JOptionPane.showMessageDialog(null, e);
}
}
try {
for (javax.swing.UIManager.LookAndFeelInfo info :
javax.swing.UIManager.getInstalledLookAndFeels()) {
UIManager.setLookAndFeel("com.jtattoo.plaf.aluminium.AluminiumLookAndFeel");
}
} catch (ClassNotFoundException ex)
{ java.util.logging.Logger.getLogger(Login.class.getName()).log(java.util.logging.Leve
l.SEVERE, null, ex);
} catch (InstantiationException ex)
{ java.util.logging.Logger.getLogger(Login.class.getName()).log(java.util.logging.Leve
l.SEVERE, null, ex);

Page | 61
 } catch (IllegalAccessException ex)
{ java.util.logging.Logger.getLogger(Login.class.getName()).log(java.util.logging.Le
vel.SEVERE, null, ex);
} catch (javax.swing.UnsupportedLookAndFeelException ex)
{ java.util.logging.Logger.getLogger(Login.class.getName()).log(java.util.logging.Le
vel.SEVERE, null, ex);
}
java.awt.EventQueue.invokeLater(new Runnable() {
public void run() {
new Login().setVisible(true);
}
});
}

// Variables declaration - do not modify

private javax.swing.JPanel LoginPanel;
private javax.swing.JLabel jLabel2;
private javax.swing.JLabel jLabel3;
private javax.swing.JButton loginBtn;
private javax.swing.JPasswordField passTxt;
private javax.swing.JTextField userTxt;
// End of variables declaration
}

Page | 62
 Chapter 13
Testing and
Validations

Why Is Testing Important

Page | 63
 This is the most important part of the software life cycle. It provides better
quality of software to end users; therefore, those end users won't come
across software issues. Testing of any software is very important for
validating functionality of the software. Testing will provide the following
information: It finds issues during early phases, which can be fixed before
finalization. It assures stability and reliability of software in different
conditions. It helps to provide issue- free software for delivery. Any
application must be tested with different methodologies. If the application
is not tested properly, then some faulty application will be delivered to
customers. Delivering such quality of application will reduce credibility,
and the customers will be not delighted with application. Testing is usually
conducted by development and quality assurance teams. This testing
validates the functionality of the application

Page | 64
 Chapter 14
Limitation and
Validations

14.1 Limitations :

Page | 65
 The Medical Store Management System makes use of Reports which are not
portable. For the clients, the plug-in needs to be installed on their machine with
NetBeans and Mysql compatible versions. System design is hard to be customized
for Customer Needs.

14.2 Future Enhancements :

Project Assigning and Task Completion Modules to be implemented in
Current System to help Customer / User to supervise and monitor Supplier Company
Performance. It will increase efficiency organization . - Email like Communication
system to be implemented to ensure swift and smooth internal vertical and lateral
official conversations to help user and Admins to interact with in Departments Data
Warehousing and Data Visualization to be implemented to help user / View Sales
Reporte

Page | 66
 Chapter 15
Conclusion

This Project “ Medical Store Management System” is prepared to meet the

requirements of store to manage their Sales Base, their User Requisites and effective
control, there by make it convenient for Admin Administration and eventually the

Page | 67
Store. This software will help Medical Store improve its Work Force Management
Efficiencies. This System in particular also offers solution to increase Sales and thus
will positively impact Retention . Thus, this System will by far be a complete
Administration effectively

Page | 68
Chapter 16
Bibliography

Page | 69
For MySQL Queries:
https://www.w3schools.com/MySQL
For Coding Reference: java:
The Complete Reference Book. Author:
https://www.javatpoint.com
https://www.GeeksforGeeks.com
https://stackoverflow.com
For UML Diagrams: Staruml
https://draw.io

Page | 70