TABLE OF CONTENTS [ T O C]

SER DESCRIPTION PAGE NO

01 ACKNOWLEDGEMENT 04

02 INTRODUCTION 05

03 OBJECTIVES OF THE PROJECT 05

04 PROPOSED SYSTEM 06

05 PHASES OF SYSTEM DEVELOPMENT LIFE CYCLE 07

06 INPUT OUTPUT SCREEN 08

07 TESTING 26

08 HARDWARE AND SOFTWARE REQUIREMENTS 28

09 BIBLIOGRAPHY 29

3
 ACKNOWLEDGEMENT
Apart from the efforts of me, the success of any project
depends largely on the encouragement and guidelines of
many others. I take this opportunity to express my gratitude
to the people who have been instrumental in the successful
completion of this project.

My sincere thanks to Mr. Mithun Chakraborty

Master In-charge, A guide, Mentor all the above a friend, who
critically reviewed my project and helped in solving each and
every problem, occurred during implementation of the project

The guidance and support received from all the members

who contributed and who are contributing to this project, was
vital for the success of the project. I am grateful for their
constant support and help.

Gayr ik Biswas
XII

4
 PROJECT ON MEDICAL STORE MANAGEMENT SYSTEM

INTRODUCTION
This programme helps the user to manage all type of records in a medical
store like: - staff data, medicine availability and can easily be updated
according to users’ requirements.
This project can easily create bill and displays it.
It consists of 12 major tasks to fully computerise management of store.

OBJECTIVES OF THE PROJECT

The objective of this project is to let the students apply the programming

knowledge into a real- world situation/problem and exposed the students

how programming skills helps in developing a good software.

1. Write programs utilizing modern software tools.

2. Apply object-oriented programming principles effectively when

Small and medium sized projects.

3. Write effective procedural code to solve small to medium sized problems.

4. Students will demonstrate a breadth of knowledge in computer science, as

exemplified in the areas of systems, theory and software development.

5. Students will demonstrate ability to conduct a research or applied

Computer Science project, requiring writing and presentation skills which

exemplify scholarly style in computer science.

5
 PROPOSED SYSTEM
Today one cannot afford to rely on the fallible human beings of be really

wants to stand against today’s merciless competition where not to wise

saying “to err is human” no longer valid, it’s out-dated to rationalize your

mistake. So, to keep pace with time, to bring about the best result without

malfunctioning and greater efficiency so to replace the unending heaps of flies

with a muchsophisticated hard disk of the computer.

One has to use the data management software. Software has been an

ascent in atomizationvarious organisations. Many software products working

are now in markets, which have helped in making the organizations work

easier and efficiently. Data management initially had to maintain a lot of

ledgers and a lot of paperwork has to be done but now software production

this organization has made their work faster and easier. Now only this

software has to be loaded on the computer and work can be done.

This prevents a lot of time and money. The work becomes fully

automated and any information regarding the organization can be obtained

by clicking the button. Moreover, now it’s an age of computers of and

automating such an organization gives the better look.

6
SYSTEM DEVELOPMENT LIFE CYCLE (SDLC)

The systems development life cycle is a project management

technique that divides complex projects into smaller, more easily
managed segments or phases. Segmenting projects allows managers
to verify the successful completion of project phases before
allocating resources to subsequent phases.
Software development projects typically include initiation,
planning, design, development, testing, implementation, and
maintenance phases. However, the phases may be divided differently
depending on the organization involved.
For example, initial project activities might be designated as
request, requirements-definition, and planning phases, or initiation,
concept-development, and planning phases. End users of the system
under development should be involved in reviewing the output of
each phase to ensure the system is being built to deliver the needed
functionality.

7
 TABLES:-
STOCK:-

BILL:-

STAFF:-

8
 MENU
CODE:-

OUTPUT:-

9
CODE :-

OUTPUT:-

10
CODE:-

11
OUTPUT:-

12
CODE:-

13
OUTPUT:-

14
CODE:-

15
OUTPUT:-

16
CODE:-

OUTPUT:-

17
CODE:-

OUTPUT:-

18
CODE:-

OUTPUT:-

19
CODE:-

OUTPUT:-

20
CODE:-

21
OUTPUT:-

22
CODE:-

OUTPUT:-

23
CODE:-

OUTPUT:-

24
CODE:-

OUTPUT:-

25
 TESTING
Software Testing is an empirical investigation conducted to provide stakeholders with
information about the quality of the product or service under test [1] , with respect to
the context in which it is intended to operate. Software Testing also provides an
objective, independent view of the software to allow the business to appreciate and
understand the risks at implementation of the software. Test techniques include, but are
not limited to, the process of executing a program or application with the intent of finding
software bugs.
It can also be stated as the process of validating and verifying that a software
program/application/product meets the business and technical requirements that
guided its design and development, so that it works as expected and can be implemented
with the same characteristics. Software Testing, depending on the testing method
employed, can be implemented at any time in the development process, however the
most test effort is employed after the requirements have been defined and coding
process has been completed.

TESTING METHODS

Software testing methods are traditionally divided into black box testing and
white box testing. These two approaches are used to describe the point of view that a
test engineer takes when designing test cases.

BLACK BOX TESTING

Black box testing treats the software as a "black box," without any knowledge of
internal implementation. Black box testing methods include: equivalence partitioning,
boundary value analysis, all-pairs testing, fuzz testing, model-based testing, traceability
matrix, exploratory testing and specification-based testing.

SPECIFICATION-BASED TESTING
Specification-based testing aims to test the functionality of software according to
the applicable requirements.[16] Thus, the tester inputs data into, and only sees the
output from, the test object. This level of testing usually requires thorough test cases to
be provided to the tester, who then can simply verify that for a given input, the output
value (or behaviour), either "is" or "is not" the same as the expected value specified in
the test case. Specification-based testing is necessary, but it is insufficient to guard
against certain risks
26
ADVANTAGES AND DISADVANTAGES
The black box tester has no "bonds" with the code, and a tester's perception is very
simple: a code must have bugs. Using the principle, "Ask and you shall receive," black box
testers find bugs where programmers don't. But, on the other hand, black box testing has
been said to be "like a walk in a dark labyrinth without a flashlight," because the tester
doesn't know how the software being tested was actually constructed.
That's why there are situations when (1) a black box tester writes many test cases
to check something that can be tested by only one test case, and/or (2) some parts of the
back end are not tested at all. Therefore, black box testing has the advantage of "an
unaffiliated opinion," on the one hand, and the disadvantage of "blind exploring," on the
other.

WHITE BOX TESTING

White box testing, by contrast to black box testing, is when the tester has access to
the internal data structures and algorithms (and the code that implement these)

Types of white box testing:-

The following types of white box testing exist:
 ap testing - Testing of the application using Public and Private APIs.
 Code coverage - creating tests to satisfy some criteria of code coverage.
For example, the test designer can create tests to cause all statements in the
program to be executed at least once.
 fault injection methods.
 mutation testing methods.
 static testing - White box testing includes all static testing.

CODE COMPLETENESS EVALUATION

White box testing methods can also be used to evaluate the

completeness of a test suite that was created with black box testing methods.
This allows the software team to examine parts of a system that are rarely
tested and ensures that the most important function points have been tested.

Two common forms of code coverage are:

 FunctionCoverage: Which reports on functions executed and
 Statement Coverage: Which reports on the number of lines
executed to complete the test.
They both return coverage metric, measured as a percentage
27
HARDWARE REQUIREMENTS
I. MOTHERBOARD : 1.845 OR 915,995 FOR PENTIUM 0R MSI

K9MM-V VIAK8M800+8237R PLUS

CHIPSET FOR AMD ATHALON

II. RAM : 512MB+

III. Hard disk : SATA 40 GB OR ABOVE

IV. MONITOR : 14.1 or 15 -17 inch

V. Key board and mouse

VI. Printer : (if print is required – [Hard copy])

SOFTWARE REQUIREMENTS:

1.Windows OS
2. Python 3.4 and above
3. MySql

28
 BIBLIOGRAPHY

1.Computer science With Python - Class XII

By: SumitaArora

2.A Project Report on Pharmacy Management

System (PMS)
By: Ajay Singh
Website: https://www.google.com

3. https://www.youtube.com

***

29