Project Cs (Deepak)
Project Cs (Deepak)
Project Cs (Deepak)
PROJECT REPORT ON
CREATING MEDICAL STORE MANAGEMENT SYSTEM
ROLL NO : 23162793
NAME : DEEPAK YADAV
CLASS : XII
SUBJECT : COMPUTER SCIENCE
SUB CODE : 083
CERTIFICATE
This is to certify that Mr DEEPAK YADAV Roll No: 23621793
Pddu. Nagar.
01 ACKNOWLEDGEMENT 04
02 INTRODUCTION 05
04 PROPOSED SYSTEM 06
07 TESTING 26
09 BIBLIOGRAPHY 29
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.
Deepak Yadav
XII A
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.
The objective of this project is to let the students apply the programming
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
One has to use the data management software. Software has been an
are now in markets, which have helped in making the organizations work
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
This prevents a lot of time and money. The work becomes fully
BILL:-
STAFF:-
MENU
CODE:-
OUTPUT:-
CODE :-
OUTPUT:-
CODE:-
OUTPUT:-
CODE:-
OUTPUT:-
CODE:-
OUTPUT:-
CODE:-
OUTPUT:-
CODE:-
OUTPUT:-
CODE:-
OUTPUT:-
CODE:-
OUTPUT:-
CODE:-
OUTPUT:-
CODE:-
OUTPUT:-
CODE:-
OUTPUT:-
CODE:-
OUTPUT:-
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 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
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.
SOFTWARE REQUIREMENTS:
1.Windows OS
2. Python 3.4 and above
3. MySql
.
BIBLIOGRAPHY
3. https://www.youtube.com
***