Medical Store Management System

Project Name : Medical Store Management System Academic Year :

2022-
2023
Subject Name: Software Testing Semester : Fifth

A Study On

Medical Store Management System

MICRO PROJECT REPORT

Submitted in Nov 2022 by the group of 3 students

Sr. No Roll No Full name of Student Enrollment No
(Sem-V)

1 3215 Lokesh Patil 2001340073

2 3255 Nitin Bare 2101340344
3 3259 Sachin Patil 2101340348

Under the Guidance of

[ Prof. Santosh Korder ]

at
[Y.B Patil Polytechnic,Akurdi]

Page 1
 Medical Store Management System

MAHARASHTRA STATE BOARD OF TECHNICAL EDUCATION, MUMBAI

Certificate

This is to certify that Mr. /Mrs. Lokesh patil , Sachin patil , Nitin bare of

Fifth Semester of Computer Science Diploma in Engineering & Technology at

Y.B Patil Polytechnic , has completed the Micro Project satisfactorily in Subject

Software Testing in the academic year 2022-2023 as per the MSBTE prescribed

curriculum of I Scheme.

Place: Akurdi,Pune Date:02/11/2022

Project Guide Head of the Department Principal

Prof. Santosh Korde Mrs. Pooja Ahuja Dr A.S Kondekar

H ead of
Institute

Page 2
 Medical Store Management System

INTRODUCTION
In this system, the management needs not to keep any type of registers, which they use to
keep in old one. They have work only with one computer. All the details are stored in
computer files. The dual entries are done very quickly as entry in one file only, affects the
other file where it has to record. In the way there is no need to record the computer operator.

The working through registers system is not only very laborious and time consuming, but
there are number of errors found. In comparison to old system the proposed system of
computer processes many advantages.

Page 3
 Medical Store Management System

REQUIREMENT ANALYSIS

• Hardware Requirement:

Desktop PC with broad specification Processor- Intel (R) Core (TM) i3-6100 CPU @
3.70GHz
RAM- 4.00 GB (Minimum 2 GB required)
System Type- 32- bit Operating System x64 based processor.

Page 4
 Medical Store Management System

TYPES OF TESTING
1. Unit Testing - Unit testing focuses verification efforts on the smallest unit of
software design, the machine module. This is also known as "MODULE TESTING".
The modules are tested separately is carried out during programming stage itself. In
this step, each module is found to be working satisfactory. So the expected output
from the module is arrived.

2. Integration Testing - Data can be lost across and interface, one module can have an
adverse effect on others, and sub-functions when combined may not produce the
desired major functions. Integration Testing is a Systematic Structure, while at the
same time conducting to uncover errors associated within the interfaces. The
objective is to take unit-tested modules and to combine them and test it as a whole.
Here correction is difficult because the vast expenses of the entire program
complicate the isolation of causes. This is the integration testing step. All the errors
encountered will be carried over to the next testing step.

3. Validation Testing - Validation testing is performed in order to find whether there is

any flow and deficiency in requirements of the system. Each and every module is
tested independently. The input and output process are validated effectively. The
input of the user for each field is validated to check if value entered is null (or) valid.
After field level validation, the module level is made such that they are integrated and
a validation is performed for the whole system

4. Output Testing - After performing the validation, the next is output testing of the
proposed system. Since no system could be useful. If it does not produce the required
output in the special format asking the user about the requirement, test the output
generated (or) displayed by the system. Hence the output format is considered in two
ways. On is on of the screen and other is printed format.

5. User-Acceptance Testing - User-Acceptance of a system is the key factors for the

success of any system. The system under consideration is tested for user acceptance
by constantly keeping in touch with the perspective system users at the time.

Page 5
 Medical Store Management System

TEST CASE TABLE

• Sign up form:-

TC_ID Objective Expected Result Actual Result Status

TC_1 Sign up id User id / phone no User id Pass

TC_2 Password Should not less than 8 Actual password Pass

character

TC_3 Enable Password/ face Password Pass

security

TC_4 Login id User id / phone no User id Pass

TC_5 Password Correct password Password accepted Pass

TC_6 OTP OTP password OTP verified Pass

TC_7 Login status Login successfully Login Pass

Page 6
 Medical Store Management System

• Login form:-

TC_ID Objective Expected Result Actual Result Status

TC_1 Open the Home page Enter in home page Pass

desktop
application
TC_2 Enter valid User id / phone no User id Pass
login id

TC_3 Enter valid Should not less than 8 Password accepted Pass
password character

TC_4 On the click Login successfully Login Pass

of login
button

• Customer/supplier/medicine entry form:-

TC_ID Objective Expected Result Actual Result Status

TC_1 On the click user have to fill all field Added record to the Pass
of ADD with proper data, if any database
button Error like entering text
data instead of number
or entering number
instead of text..is found
then it gives proper
message
TC_2 On the click Deletes the details in Deleted successfully Pass
of DELETE database
button

TC_3 On the click Modified records are Record has been updated Pass
of updated in database successfully
UPDATE
button

Page 7
 Medical Store Management System

TC_4 On the click Searching by entering Option are displayed Pass

of name
SEARCH
button
TC_5 On the click Should be exit Exit successfully Pass
of EXITE
button

• Stock:-

Page 8
 Medical Store Management System

• Customer bill:-

• Sale invoice form:-

Page 9
 Medical Store Management System

SYMBOLS USED IN DFD

An arrow indicates
dataflow

Double line with one end closed indicate data store

A rectangle represents external entity

Page 10
 Medical Store Management System

DATA FLOW DIAGRAM (DFD)

Page 11
Medical Store Management System

Page 12
 Medical Store Management System

WATERFALL MODEL

Page 13
 Medical Store Management System

REASON FOR CHOOSING WATERFALL MODEL

1. This is Small Project and Requirements Are Well understood.

2. This model is simple and easy to understand and use.

3. Waterfall model is simple to implement and also the amount of resources required for
it are minimum.

4. It is easy to manage due to the rigidity of the model - each phase has specific
deliverables and a review process.

5. In this model, output is generated after each stage (as seen before), Therefore it has
high visibility. The client and project manager gets a feel that there is considerable
progress. Here it is important to note that in any project psychological factors also play
an important role.

6. In this model phases are processed and completed one at a time. Phases do not
overlap. This Project Is Conversion From Manual To Automatic.

Page 14
 Medical Store Management System

ADVANTAGES

1. This system provides an easy way for the casher to determine whether the customer is
a valid member so that he can provide them with discount.

2. This system is also provides great help to the casher to add or update new or existing
members respectively

DISADVANTAGE

1. As every coin has a two side this system also suffers from disadvantage.

2. Multiple medicines can not be checked for a customer

Page 15
 Medical Store Management System

CONCLUSION
We effectively understood how to create a test case table on the coding program. Also
we understood how to draw the system diagram and to design the test cases as well as we
understood in the testing.

REFERENCES

• https://www.softwaretestinghelp.com/test-cases-for-atm/

Page 16