Professional Documents
Culture Documents
Pharmacy
Pharmacy
1. PURCHASE
2. SALES
PURCHASE :
SALES :
1.HARDWARE ENVIRONMENT
RAM : 128 MB
SOFTWARE DESCRIPTION
• Standard Edition
• Professional Edition
• Enterprise Edition
Native Code:-
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:-
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
Normalization is a technique of separating redundant fields
and braking up a large table in to a smaller ones. All the tables
have been normalized up to the third normal form. In short the
rules for each of the three normal form are as below.
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
FIELD NAME DATA TYPE DATA SIZE
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*/
Private Sub Command1_Click()
If ((Text1.Text = " ") Or (Text1.Text = " ")) Then
MDIForm1.Enabled = True
MDIForm1.Show
Else
MsgBox "enter the password correctly"
Text1.Text = ""
Text1.SetFocus
End If
End Sub
/*MAIN MENU*/
Private Sub CU_Click()
DataReport5.Show
End Sub
Else
DISABLE
Command1.Enabled = True
Command4.Enabled = True
End If
If RS1.RecordCount <> 0 Then
RS1.MoveFirst
K = RS1(4)
Do While Not (RS1.EOF = True)
Combo1.AddItem RS1(4)
RS1.MoveNext
If RS1.EOF = True Then
GoTo ABC
End If
If RS1(4) = K Then
RS1.MoveNext
Else
K = RS1(4)
End If
ABC:
Loop
End If
End Sub
SYSTEM TESTING
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:
Features to be Tested
Test Deliverables
Schedule
Test unit
Features to be tested
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:
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:
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.
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.
BIBLIOGRAPHY