Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
The aim of the project is to computerize the pharmacy stores. The modules
of the project are;
1. PURCHASE
2. SALES
PURCHASE :
In this module, we have Manufacturer, Purchase Transaction and Purchase
Returns. We have the details of Manufacturer of the Medicine under Manufacturer sub
module.
We have the Details of Transactions i.e. the Purchase Details under Transaction
sub module. In Purchase Returns, We have the Details of Purchase Returns of Purchase,
if there any.
SALES :
In this module, we have Customer, Sales Transaction and Sales Returns. In
Customer sub module, we have the Details of the Customer. In Transaction sub module,
we have the Transactions i.e., Sales. In Sales Returns, we have the Details of the Returns
of Sales, if any, In Customer module, we have details of the customers. In Sales
Transactions we have cash & credit sales of the Pharmacy.
SYSTEM ENVIRONMENT
1.HARDWARE ENVIRONMENT
RAM : 512 MB
Hard Disk : 80 GB
SOFTWARE DESCRIPTION
Visual Basic was developed forms the BASIC programming language. In 1970’s
Microsoft got its start by developing ROM based interpreted Basic for the early
microprocessor based computer. In 1982, Microsoft QuickBasic revolutionized Basic
and legitimized as a serious development language for MS-DOS environment. Later on,
Microsoft Corporation created the enhanced version of BASIC called Visual Basic for
Windows.
Visual Basic 6.0 allows creating Object Oriented Application. When Visual
Basic originally developed, it allowed to the programmer to create programs using
pre-defined objects, forms and controls. It uses some of the Windows 95 Controls.
Visual Basic 6.0 can be used to develop both standalone systems and Client Server
Based systems.
• Standard Edition
• Professional Edition
• Enterprise Edition
A Visual Basic project is compiled to native code for faster execution. Profiles
native code using new native code compiler option, and debug native code using the
Visual C++ environment.
Wizards:-
The application Wizard is new and the Setup Wizard has been enhanced to enable
creating a dependency file for a standard project. In the professional Edition, the Active
X control Interface Wizard, Active X Document Migration Wizard, Data Form Wizard,
and property page Wizard are new. The Setup Wizard has been enhanced to support
distribution via the Internet. The installation of remote server components using
Distributed COM(DCOM)and Remote Automation is an added feature. The ability to
create dependency files for projects and components created with Visual Basic.
Extensibility Model:-
Objects provided by the components can raise events that can be handled in other
applications, or by our objects, using with Events variables, Events provide a simple
alternative to asynchronous callbacks.
ActiveX document s can be created that boosts the Visual Basic application to the
Internet Browser Windows. The data control, DAO or Microsoft Access, you can create
that is virtually database independent, because jet automatically performs all syntax and
data manipulation translations.
ACCESS - 2003
When we create a Microsoft Access database, we create one file that contains the
data and table structures as well as the queries, forms, reports and other objects that make
up the database.
SYSTEM DEFINITION
EXISTING SYSTEM
The Existing system was required to include functionalities that will take care of all the
future development which are not available in the system .The purchasing can be done at
any time it works around the clock. In future we can add the database that can provide
various types and best in all of that are available.
DATAFLOW DIAGRAMS:
OVER VIEW:
MANUFACTURER
USER
DEALER
CUSTOMER
PURCHASE:
ADDITION
USER
MANUFACTURER DELETION
MODIFIES
PURCHASE PURCHASE
RETURNS
STOCK
SALES:
STOCK SALES
SALES CUSTOMER
RETURNS
DATA BASE DESIGN
NORMALIZATION
CUSTCODE DOUBLE 8
CUSTNAME TEXT 50
ADDRESS TEXT 50
PHONE DOUBLE 8
TABLE NAME:-MANU
MEDCODE DOUBLE 8
MEDNAME TEXT 50
ADDRESS TEXT 50
PHONE DOUBLE 8
MANUCODE DOUBLE 8
MANUNAME TEXT 50
MEDRATE DOUBLE 8
MANDATE DATE/TIME 8
EXPDATE DATE/TIME 8
TABLE NAME:-PTRAN
DATEOFTRAN DATE/TIME 8
TYPE TEXT 4
MANCODE LONG 4
MEDCODE LONG 4
QTY LONG 4
BALANCE DOUBLE 8
TABLE NAME:-PURRET
MANCODE DOUBLE 8
MEDCODE DOUBLE 8
QTYDEF DOUBLE 8
DATEOFTRANS DATE/TIME 8
TABLE NAME:-SALSRET
CUSTCODE DOUBLE 8
MEDCODE DOUBLE 8
QTYDET DOUBLE 8
DATEOFTRANS DATE/TIME 8
TABLE NAME:-SALTRANS
DATEOFTRANS DATE/TIME 8
TYPE TEXT 4
CUSTCODE DOUBLE 8
MEDCODE DOUBLE 8
QTY DOUBLE 8
BALANCE DOUBLE 8
TABLE NAME:-STOCK
MEDCODE DOUBLE 8
STKLEV DOUBLE 8
RELEV DOUBLE 8
SCREENS:-
The proposed system uses very simple data structures in order to simplify and
maintain the entire system. The only data structure used in our system is TABLES.
The necessity for using files is as follows:
CODING:
CODING:
/*PASSWORD FORM*/
/*MAIN MENU*/
In a software development project, errors can be injected at any stage during the
development. Testing performs a very critical role for quality and for ensuring the
reliability of software. During testing ,the program to be tested is executed with set of
test cases ,and the output of the program for the test cases is evaluated to determine if the
program is performing as it is expected to. Due to its approach, dynamic testing can only
ascertain the presence of error in the program; the exact nature of the error is not usually
decided by testing . Testing forms the first step in determining the errors in the program.
Clearly the success of testing in revealing errors in programs depends critically on the test
cases.
Testing is usually relied upon to detect the faults that occur during any phase of
the software development cycle ,in addition to the faults that introduced during the
coding phase itself. For this ,different levels of testing are used which perform different
tasks and aim to test different aspects of the system. the basic levels of testing are unit
testing ,integration testing ,system and acceptance testing. the different levels of testing
attempt to detect different types of faults.
Client Needs Acceptance Testing
Test Plan:
A Test plan is a general document for the entire project, which defines the scope
approach to be taken, and the schedule of testing ,as well as identifying the test items for
the entire testing process and the personnel responsible for the different activities of
testing commences and can be done in parallel with the coding and design phases, the
inputs for the test plan are the
Project plan
Requirements Document
The project plan is needed to make sure that the test is consistent with overall plan for
the project and the testing schedule matches that of the project plan the requirements
document and the design document are the basic document Used for selecting the test
unit and deciding the approaches to be employed during testing .A test plan sholud
contain the Following:
Test unit specification
Features to be Tested
Test Deliverables
Schedule
Test unit
It is a set of one or more modules together with associated data which are the
forms a single computer program and which are the object of testing. It can occur at any
level and can contain from a single module to the entire system. This is carried out at
every stage of the project i.e., after completion of every module
Features to be tested
Specifies the overall approach to be followed in the current project. This is some
times called testing criteria, or the criteris evaluating the set of test cases used in testing.
Testing deliverables should be specified in the test plan, before the actual testing
begins. Deliverables could be a list of test cases that were used detailed results of testing,
test summary report, test log and data about the code coverage.
Schedule
specifies the amount of time and effort to be spent on different activities of
testing, and testing of different units have been identified.
UNIT TESTING:
Unit testing is a dynamic method for verification, where the programs is actually
compiled and executed .It is one of the most widely used method, and the coding phase is
sometimes called “coding and unit testing phase”, as in other forms of testing, unit testing
involves executing the code with some test cases and then evaluating the results.
The goal of unit testing is to test modules or ”units” and not the entire software
system. The programmer himself most often does unit testing, the programmer, after
finishing the coding of a module, test it with some data. The tested module is then
delivered for system integration and further testing there are 4 categories of tests that a
programmer will typically perform on a program unit
Functional tests:
Performance tests:
Stress tests:
Stress tests are designed to overload a system in various ways. Structural tests are
concerned with examining internal process logic of software system.
Integration tests:
After the unit testing the modules is gradually integrated into subsystem, which
are then integrated them to eventually form the entire system. During integration of
modules Integration testing is performed .The goal of this testing is to detect design
errors, while focusing on testing the interconnection between modules.
System testing
After the system is put together, system testing is performed. here the system is
tested against the system requirements to see if all the requirements are met and the
system performs as specified by requirements. The entire software is tested and the goal
is to see if the software meets the requirements
Alpha-beta testing:
A customer does the alpha test at the developer site .the software is used in a
natural setting with the developer and usage problems.
The beta testing is conducted at one or more customer areas of the end of
software. The problems are recorded and updated.
Conditional testing is a test case design method that exercises the logical
condition in a program module. The possible types of components in
a condition include a Boolean operator, Boolean variable, pair of Boolean parenthesis
relational operator or an arithmetic operator.
Data flow testing method selects test path of program according to the location
of definition and uses of variables in the program .they are useful for selecting test. They
are useful for selecting test paths of a program containing nested if and loop statements.
Loop Testing:
Loops are the cornerstone for the vast majority of all algorithm implemented in
software loop testing is a white box technique that focuses exclusively on validity of
loop construct.
Black box testing method focuses on the functional requirements of the software.
black box testing method attempts to find in the following categories.
This Application is designed to be generic .as we develop our site we should take
advantage of several areas in which you can improve and customize business.
The main approach in having this application is that this type of the systems can
play a major role in the part of the life. Since the health is the major context in our life for
that we can make use of such systems for suggesting the good medicines like one of the
application is Medical Transcription we can do many improvements by making available
to every body by proving this type of applications through net or online.
I would like to extend my warm wishes and thanks to everyone who contributed their
valuable suggestion and time for the development of this application.
BIBLIOGRAPHY