Medical Agency

A
PROJECT REPORT
ON
Submitted towards partial fulfillment of the requirement

For the awards of the degree of
“BACHELOR OF COMPUTER APPLICATION”
Submitted by
Monika Sharma
Roll no. 062119505
Indira Gandhi National Open University
1
CONTENTS
1. Acknowledgement………..…………………………………………. 3
2. Study Center Certificate……….……………………………………. 4
3. Introduction…………………………………………………………. 5
4. Preface………………………………………………………..……… 6
5. Hardware, Software Specification…………………………………… 7
 Hardware requirement………………………………………… 10
 Software requirement…………………………………………. 11
 Database design……………………………………………….. 12
 Dataflow diagram…………………………………………….. 16
 ER-Diagram ………………………………………………….. 22
5. System analysis………………………………………………………. 23
6. Software Planning……………………………………………………. 27
7. System design………………………………………………………… 29
8. Testing & Debugging...………………………………………………. 36
9. Security of the system………………………………………………… 45
10. Coding……………………..………………………………………… 46
11. Output……………………………………………………………….. 61
11. Bibliography………………………………………….……………... 89
2
INTRODUCTION
The aim of this project i.e Medical Agency Management System is to

maintain the Medicine data, Purchase, Sales, and most important Stock data.
There is only one type of user in this system, known as registered user. The
user first insert the data of all the students whse attendance is to be maintained
and then can use attendance window. In this project, we can maintain the
Student and attendance data Month wise. This software provides you we can
search the attendance details of a particular student quickly which helps in
time saving.
3
HARDWARE AND SOFTWARE
REQUIREMENTS SPECIFICATION
If a document that completely describes what the proposed software should

do without describing how the software will do it, The basic goal of
requirements specific to produce the requirements, which describes the
complete external behavior of the proposed software. However, producing
the report is said to be done.
The basic limitation is that the user’s need keep on changing as the
environment in which system was to function changes with time. This
happens more in complex application where all the needs may not be
known to any set of people during the requirement phase. Types of error in
this specifications can clearly be avoided or at least considerably, by
properly performing the requirement phase.
As many times a developer or administrator does not know what a user and
the supplier on what the software product will do. This is the only
document which tells the time agreement and procedure of complete project
as well as what a user wants.
There are some steps which are considered in the SOFTWARE

REQUIREMENT SPECIFICATION such as
4
 Introduction Description
 Information Description
 Function Description
 Behavioral Description
 Validation checks and criteria
 Bibliography
 Appendix
Introduction
The introduction states the goals and objectives of the software describing it
in the context of the computer -based system. Actually the introduction may
be nothing more than the software people of the planning document.
Functional description
The project also provides the facility to contact the registered user easily
without any admin interaction. If you find an existing entry meeting your
requirement, then you can contact the concerned party directly.
If there is no entry, which meets your requirement, you can register your
details on the site, so that others can find you. The project improves the
efficiency and effectiveness of the whole system.
5
Behavioral description
IT Examine the operations of the software as a consequence of external

events and internally generated control characteristics. Here the Admin
checks the classified entered by the registered users. Admin is the only
person who can activate or deactivate the classified entered by the
registered users.
6
HARDWARE REQUIREMENT
Hardware is the term given to machinery itself and to various individual

pieces of equipment.
It refers to the physical devices of a computer system. Thus the input,

storage, processing control and output devices are hardware.
Minimum Hardware Requirement Of Client Side:
Processor : Any Pentium IV or Equivalent Machine

RAM : 256 MB
HDD : 40 GB
FDD : 1.44 MB
CD-ROM : 52X
15 inches Color Monitor
104 Keys Keyboards
7
SOFTWARE REQUIREMENT
To use this software, some software are required. Software means a

collection of program where the objective is to enhance the capabilities of
the hardware machine.
Minimum Software Requirement Of Client Side:
Operating System : Windows Operating System
Database : MS-ACCESS
8
DATABASE DESIGN
Introduction to data dictionary:
Data dictionaries are an integral component of structured analysis, since data

flow diagrams by themselves do not fully describe the subject of the
investigation. The data flow diagrams provide the additional details about
the project/system.
Data Dictionary (Definition):
A data dictionary is a catalog- a repository- of the elements in a system.

These elements center on the data and the way they are structured to meet
user requirements and organization needs. A data dictionary consists of a
list of all the elements composing the data flowing through a system. The
major elements are data flows, data stores, and processes. The data
dictionary stores details and descriptions of these elements.
Describing Data Elements:
Each entry in the data dictionary consists of a set of details describing the
data used or produced in the system. Each item is identified by a data name,
9
description, alias, and length and has specific values that are permissible for
it in the system being studied.
List of Tables:
Table Structure
1. User table
2. Student table
3. Attendance table
1. Login table
Field Name Data Type

Loginname Text
Password Text
2. Supplier Table

SNO Number
SName Text
ADDRESS Text
PHONE Text
10
3. Purchase Table

SNO Number
SName Text
ADDRESS Text
MNAME TEXT
MEDICINETYPE TEXT
COMPNAME TEXT
ORDERNO NUMBER
PURCHASEDATE DATE
MDATE DATE
EXPDATE DATE
QTY NUMBER
RATE NUMBER
BILL NUMBER
11
4. Sale Table

CNO Number
CName Text
ADDRESS Text
MNAME TEXT
MEDICINETYPE TEXT
COMPNAME TEXT
ORDERNO NUMBER
SALEDATE DATE
MDATE DATE
EXPDATE DATE
QTY NUMBER
RATE NUMBER
BILL NUMBER
5. Stock Table

MEDICINNAME TEXT
COMPANY Text
QTY NUMBER
RATE NUMBER
12
DATA FLOW DIAGRAM (DFD)
Definition of Analysis and Design:
Analysis and design refers to the process of examining a business situation

with the intent of improving it through better procedures and methods.
Overview of Analysis and Design:
System development can generally be thought of as having two major

components - analysis and design.
Introduction of User:
The term user is widely used in the system analysis and design. The term
end-user is widely used by the analysts to refer to people who are not
professional information systems specialists but who can use computers to
perform their Jobs. We can group end-user into four categories.
Hands-on Users actually interact with the system. They feed in data or
receive output , perhaps using a terminal.
Indirect Users benefit from the results or reports produced by these

systems but do not directly interact with the hardware or software.
These users may be managers of business functions using the system.
13
End-Users are not alike. Some are intermittent users. The end-user can also
be a competitor, not an employee of the firm.
User managers have management responsibilities for application systems.
Definition of System:
In the broad sense, a system is simply a set of components that interact to

accomplish some purpose. Systems are all around us. As computers are
used more and more by persons who are not computer professionals ,
the face of systems development is taking on an additional dimension.
Users themselves are undertaking development of some of the systems
they use , as the executive in the vignette emphasized.
These different situations are represented by three distinct approaches to
the development of computer information systems:
 Systems Development Life Cycle.

 Structured Analysis Development Method.
 Systems Prototype Method.
Systems Development Life Cycle:
Systems development, a process consisting of two major steps of

systems analysis and design, starts when management or sometimes
systems development personnel realize that a particular business system
needs improvement.
14
SDLC is classically thought of as the set of activities that analysts, designers
and users carry out to develop and implement an information system.
Different parts of the project can be in various phases at the same time,
with some components undergoing analysis while others advanced stages.
SDLC consists of following activities:
 Preliminary investigation.
 Determination of system requirements.

 Design of system.
 Development of software.
 System testing.
 Implementation and evaluation.
Two main steps of development are:
 Analysis
 Design
15
ANALYSIS:
Objectives:
System analysis is conducted with the following objectives in mind:
 Identify the user’s need.

 Evaluate the system concept for feasibility.
 Perform economic and technical analysis.
 Allocate functions to hardware, software, people, database, and other
system elements.
 Establish cost and schedule constraints.

Create a system definition that forms the foundation for all subsequent
engineering work. Both hardware and software expertise are required to
successfully attain the objectives listed above.
16
DFD FOR LOGIN
Searched
Username data
USER1
User Detail
Password
Invalid
CHECK message
THE
VALID
USER2 USER
17
DFD FOR MEDICAL AGENCY
STOCK
SUPPLIER
.
Medicine data
Supplier data
Medicin data
PURCHAS
SALE E AND
& SALES
REGISTER
PURCHASE
CUSTOMER
Customer data
18
E-R DIAGRAM
Year
Month
User
Total
absent
User
U_pass name
Login
Purchase Stock
& Sale
medicine
Suppno Phone
Supplier
&
Customer
Addres
Name
s
19
SYSTEM ANALYSIS
The analysis model must achieve three primary objectives:-
1. To describe the requirements of the customer.

2. To establish a basis for the creation of a software design.
3. To define a set of requirements that can be validated once software is
built.
An Overview to system analysis
The system analysis phase is considered to be one of the most important

phases in the system development life cycle. It is immensely important that
the software developer make through study of the existing system.
Thorough study of the system is made and need i.e. features that are critical
to system success and users wants (i.e. features that would be good but not
essential) are brought out. The study will enable the developer to know the
intricacies of the existing system.
Requirement analysis is done in order to understand the problem which the

S/W system is to solve e.g., the problem could be automating the existing
manual system or developing a completely new automated system or a
combination of the two. For large systems having a large number of
features and the need to perform many different tasks, understanding the
requirement of the system is a major task. The emphasis in requirement
20
analysis is on identifying what is needed from the system, and not how the
system achieves its goal.
The main objective behind any business organization is to maximize its

profit besides maintaining quality and strategic norms. This can be
achieved by improving the efficiency of the system by providing more
facilities using automation, by adopting faster data access, proper
communication.
Since Computer Craft is an educational institute, whereas its main
objective behind automation is not only to maximize profit but also to take
care of students’ interest by providing coaching of latest courses benefiting
students, in turn the country.
The most important objective behind automation is to minimize Paper

Work. Paper Work/Registers are replaced by a Centralized Data Bank,
which is well equipped to store / provide information as and when required.
Data Bank also helps speed up the communication between various depts. /
outside agencies, as there is no need of making request against different
departments for a specific data and to wait for it for a long period. This also
improves the efficiency as it saves time and human resources.
By making the manual system computerized, we can ensure complete

utilization of our existing resources. Automation helps in generating the
reports / information in a consistent way, which saves time and labour if
done manually.
21
NEED OF COMPUTERIZATION
In the area of information technology, it is need of hour to have a fast

information processing system capable of providing processed data at right
time and to right person which appropriately justified by the following
limitation of manual system:
 Delay in information search and retrieval

 Problem in updation of current information and maintaining proper
backup of information
 Possible damage of paper carrying the information thereby chance of
loosing valuable information.
 Much time required in giving correct information
 Less reliability and maintainability of data
 Secrecy of information may not be maintained due to visible facts
on paper.
IMPORTANCE OF COMPUTERIZATION
After computerization of the system, it will be helpful for

giving correct information in a short period of time. This will provide:
 Easy storage and retrieval of data

 Giving correct information with less effort and high accuracy
22
 Secrecy and less chance of change of loss of data
 Easy data updating facility
 Data integrity and inconsistency
Requirement Collection and Analysis
Most information regarding identification of user group and application

areas, the operating environment, the processing requirements have been
obtained during the system analysis phase through on-site observations and
interviews.
23
SOFTWARE PLANNING
I was assigned the duty for developing a computerized system known as

“Online Attendance Management System”. Working in team reinstates the
team for some common guidelines and standard to be followed by all the
team members across all team. For the optimum use of practical time it is
necessary that every session is planned. Planning of this project will include
the following things:
 Topic Understanding.
 Modular Break –Up Of The System.
 Processor Logic For Each Module.
 Database Requirements.
Topic Understanding:
It is vital that the field of application as introduced in the project may be

totally a new field. I carefully went through the project to identify the
requirements of the project.
Modular Break –Up Of The System:
 Identify The Various Modules In The System.

 List Them In The Right Hierarchy.
 Identify Their Priority Of Development.
24
Description Of The Modules:
Module 1: Password Module
In this module, registered user enters a password and the software checks its
validity. If the password is valid then he is allowed to enter, otherwise
“Invalid User/Password” message is displayed.
Module 2: Medicine
In this module we can maintain the medicine data.
Module 3: Supplier
In this module, all the suppliers information are maintained
Module 4: Purchase and Sale

This is an important module by which we can purchase and sale of the
medicine.
Database Requirements:
 Identify The Various Tables Required.

 Fields For These Tables.
 The Various Key Fields (for example Primary key and Foreign key).
 Identify The Various Constraints like Not Null, Unique etc.
The Database here used is Ms-ACCESS The database tables are shown in
DATABASE DESIGN.
25
SYSTEM DESIGN
Introduction:
System design is a solution, “How to approach ” to the creation of a new

system. This important phase is composed of several steps. It provides the
understanding and procedural feasibility study. Design gose through a
logical and physical stage of development. Logical design reviews the
present physical system, prepares input – output specification, makes edit,
security and control specification, detail implementation plans, prepares a
logical design walkthrough. The physical design maps out the details of the
physical system, plans the system implementation and specifies any new
hardware and software.
System design is a highly created process that can be greatly facilitated by

the following:
 Strong problem definition,

 Pictorial description of the existing system,
and
 Set of requirements of the new system.
Input Design
The most common cause of errors in data processing is inaccurate input data
errors entered by the data entry operator. It can be controlled by the input
design. Input design is the process of converting user oriented inputs to the
26
computer based formats. The goal of the input design is to make data entry
as easy, logical and free from as many errors as possible.
Output Design
Computers are the most important sources of information to the users are fed
into the computers to acquire the necessary outputs. The computers can
provide the well enough output in the form of information regarding various
items to the users. The major form of output is a hard copy from the printer.
Printouts are designed around the output requirements of the user(s).
Interface Design
Forms are designed to control the redundancy, increased operator accuracy

maximum readability, easy data entry and elimination of unnecessary data to
provide easier checking and correction of data.
Keeping in view the user’s requirements, the input/output forms have been
designed
and developed for easy data entry and query handling. Based on the various
types of inputs to be fed into the computer in using this system, several
inputs forms have been designed to make data entry easier and accurate.
Database Design
The collection of data is usually referred to as the database. The database

contains information about the particular enterprise. Database systems are
27
designed to manage larger bodies of information. The management of data
involves both the definition of the structures for the storage of the
information and the provision for the mechanism to manipulate the
information. In addition the database system must provide the safety of the
information stored in the database, despite system crashes or attempts at
unauthorized access.
System implemantation
Implementation, literally, means to put into effects or to carry out. The

system implementation phase of software engineering deals with all
activities that take place to convert from the old system to the new. Proper
implementation is essential to provide system to meet organization’s
requirements.
During the implementation phase debugging, documentation of the system

was created out, module in the project for
 Accuracy of Results,
 Minimization of response Time,
 Clarity and Simplicity of the code,
 Minimization of hard – Coding i.e. (a generic approach was followed)
 Minimization of amount of memory used.
Various types of errors were discovered while debugging the modules.

These ranged from errors to failure to account for various processing cases.
28
Proper documentation of each module was done by embedding comments in
the executable portion of the code. To enhance the readability, comments,
indentation, parenthesis, block spaces, blank lines and borders were around
the blocks of comments. Care was taken to use descriptive names for table,
field modules, forms etc. The proper use of indentation, parenthesis and
blank lines was also ensured during coding.
Testing of the report Generation module was carried out to find out the
response time of the system for the generating reports. To make the response
time negligible.
SYSTEM DOCUMENTATION
Documentation is the process of collecting, organizing, storing, and

maintaining on paper (or some relatively permanently medium ) a complete
record of why application were developed, for whom, what function they
perform, and how these function are carried out. Thus it provides an
explanation of how a system operates & what features characterize models
& algorithms. Producing documentation is an important – but often
neglected – activity of programmers.
Documentation of the system always reduces maintenance costs and make
maintenance much more easier. Documentation can be broadly classified as:
1. INTERNAL DOCUMENTATION
2. EXTERNAL DOCUMENTATION
29
Internal documentation
Internal documentation in the code can be extremely useful in enhancing the

understandability of programs. Internal documentation of programs is done
by the use of comments. All the language provide means of writing
comments in the programs. Comments are textual statements that are meant
for the reader and are not executed. Comment, if properly written, and if
kept consistent with the code, can be invaluable during maintenance.
The purpose of comments is not to explain the internal logic of the program
– the program itself is the best documentation for the details of logic.
The comments should explain what the code is done is doing, and not how it
is done it. Comments should be provided for the block of code, particularly
those parts of code which are hard to follows.
Providing comments for module is most useful as module form the unit
testing, compiling, verification and modification. Comments for a module
are often called prologue for the module. It is best to standardized the
structure of the prologue of the module. It is desirable that prologue contains
the following information ;
a) Module functionality or what the module is doing.
b) Parameters are their purpose
c) Assumptions about the input, if any
30
d) Global variable accessed and or modified in the module As explanation
of parameters (whether they are input only, output only or both input and
output, why they are needed by the module and how the parameters are
modified) can be quite useful during Maintenance.
In addition to that given above, often information can be included,

depending on the local coding standards. Example include:
 Name of the author,
 Date of compilation
 Last date of modification
Note that if the module is modified, then the prologue should also be
modified, if necessary. A prologue that is inconsistent with the internal logic
of the module is prologue worse than having no prologue at all.
While coding programs for the Station Coding System special attention has
been paid to the internal documentation of the system, in addition to the
external documentation. Each program/module has:
 Program/module name on top.

 Date of creation of the program.
 Last modification date.
 The S/W tool used to develop the program.
 Description of input to the program/module.
 Description of the output produced.
31
 How the module is related to other modules?
 Purpose of variable/constants used.
Apart from this comments lines have been inserted whenever it was felt that
they were necessary. Moreover meaningful variable names/constants have
been assigned to different variable/constants used in the program.
External documentation
The external documentation of the system contains all the relevant

information about the system which is not included within the programs.
The external documentation typically explains:
 What is the basic purpose of the system?

 Why the system was developed?
 The platform on which the system will run.
 The various trouble shooting mechanisms.
 The operation’s guide.
32
TESTING & DEBUGGING
TESTING
It should be clear in mind that the philosophy behind testing is to find errors.
Test cases are devised with this purpose in mind. A test case is a set of data
that the system will process as normal input. However, the data are created
with the express intent of determining whether the system will process them
correctly. For example, test cases for inventory handling should include
situations in which the quantifies to be withdrawn from inventory exceed,
equal and are less than the actual quantities on hand. Each test case is
designed with the intent of finding errors in the way the system will process
it. There are two general strategies for testing software: Code testing and
Specification testing. In code testing, the analyst develops that cases to
execute every instructions and path in a program. Under specification
testing, the analyst examines the program specifications and then writes test
data to determine how the program operates under specific conditions.
Regardless of which strategy the analyst follows, there are preferred
practices to ensure that the testing is useful. The levels of tests and types of
test data, combined with testing libraries, are important aspects of the actual
test process.
Levels of Testing
Systems are not designed as entire systems nor are they tested as single
systems. The analyst must perform both unit and system testing.
33
Unit Testing:
In unit testing the analyst tests the programs making up a system. For this
reason, unit testing is sometimes called program testing. Unit testing gives
stress on the modules independently of one another, to find errors. This
helps the tester in detecting errors in coding and logic that are contained
within that module alone. The errors resulting from the interaction between
modules are initially avoided. For example, a hotel information system
consists of modules to handle reservations; guest checking and checkout;
restaurant, room service and miscellaneous charges; convention activities;
and accounts receivable billing. For each, it provides the ability to enter,
modify or retrieve data and respond to different types of inquiries or print
reports. The test cases needed for unit testing should exercise each condition
and option.
Unit testing can be performed from the bottom up, starting with smallest and
lowest-level modules and proceeding one at a time. For each module in
bottom-up testing a short program is used to execute the module and
provides the needed data, so that the module is asked to perform the way it
will when embedded within the larger system.
System Testing:
The important and essential part of the system development phase, after
designing and developing the software is system testing. We cannot say that
every program or system design is perfect and because of lack of
34
communication between the user and the designer, some error is there in the
software development. The number and nature of errors in a newly designed
system depend on some usual factors like communication between the user
and the designer; the programmer's ability to generate a code that reflects
exactly the systems specifications and the time frame for the design.
Theoretically, a newly designed system should have all the parts or sub-
systems are in working order, but in reality, each sub-system works
independently. This is the time to gather all the subsystem into one pool and
test the whole system to determine whether it meets the user requirements.
This is the last change to detect and correct errors before the system is
installed for user acceptance testing. The purpose of system testing is to
consider all the likely variations to which it will be subjected and then push
the system to its limits.
Testing is an important function to the success of the system. System testing

makes a logical assumption that if all the parts of the system are correct, the
goal will be successfully activated. Another reason for system testing is its
utility as a user-oriented vehicle before implementation.
System testing consists of the following five steps:
1) Program testing
2) String testing
3) System testing
4) System documentation
5) User acceptance testing
35
Program Testing:
A program represents the logical elements of a system. For a program to run

satisfactorily, it must compile and test data correctly and tie in properly with
other programs. it is the responsibility of a programmer to have an error free
program. At the time of testing the system, there exists two types of errors
that should be checked. These errors are syntax and logic. A syntax error is a
program statement that violates one or more rules of the language in which it
is written. An improperly defined field dimension or omitted key words are
common syntax errors. These errors are shown through error messages
generated by the computer. A logic error, on the other hand, deals with
incorrect data fields out of range items, and invalid combinations. Since the
logical errors are not detected by compiler, the programmer must examine
the output carefully to detect them.
When a program is tested, the actual output is compared with the expected
output. When there is a discrepancy, the sequence of the instructions, must
be traced to determine the problem. The process is facilitated by breaking
the program down into self-contained portions, each of which can be
checked at certain key points.
String Testing:
Programs are invariably related to one another and interact in a total system.
Each program is tested to see whether it conforms to related programs in the
36
system. Each part of the system is tested against the entire module with both
test and live data before the whole system is ready to be tested.
System Testing:
System testing is designed to uncover weaknesses that were not found in

earlier tests. This includes forced system failure and validation of total
system as it will be implemented by its user in the operational environment.
Under this testing, generally we take low volumes of transactions based on
live data. This volume is increased until the maximum level for each
transaction type is reached. The total system is also tested for recovery and
fallback after various major failures to ensure that no data are lost during the
emergency. All this is done with the old system still in operation. When we
see that the proposed system is successful in the test, the old system is
discontinued.
System Documentation:
All design and test documentation should be well prepared and kept in the
library for future reference. The library is the central location for
maintenance of the new system.
User Acceptance Testing:
An acceptance test has the objective of selling the user on the validity and
reliability of the system. It verifies that the system's procedures operate to
37
system specifications and that the integrity of important data is maintained.
Performance of an acceptance test is actually the user's show. User
motivation is very important for the successful performance of the system.
After that a comprehensive test report is prepared. This report shows the
system's tolerance, performance range, error rate and accuracy.
Special Systems Tests:
There are other six tests which fall under special category. They are
described below:
Peak Load Test: It determines whether the system will handle the volume
of activities that occur when the system is at the peak of its processing
demand. For example, test the system by activating all terminals at the same
time.
Storage Testing: It determines the capacity of the system to store

transaction data on a disk or in other files. For example, verify
documentation statements that the system will store 10,000 records of 400
bytes length on a single flexible disk.
Performance Time Testing: it determines the length of time system used

by the system to process transaction data. This test is conducted prior to
implementation to determine how long it takes to get a response to an
inquiry, make a backup copy of a file, or send a transmission and get a
response.
38
Recovery Testing: This testing determines the ability of user to recover data
or re-start system after failure. For example, load backup copy of data and
resume processing without data or integrity loss.
Procedure Testing: It determines the clarity of documentation on operation

and use of system by having users do exactly what manuals request. For
example, powering down system at the end of week or responding to paper-
out light on printer.
Human Factors Testing: It determines how users will use the system when
processing data or preparing reports.
DEBUGGING
This stage is the discovery & correction of programming errors. Few

programs run correctly the first time, so debugging is important & time-
consuming stage of the software development. Programming theorists &
testing as verification & validation, respectively. Verification ensures that
the program does what the programmer intend to do. It is the checking or
testing of the items ,including software ,for conformance and consistency
with an associated specification. Validation ensures that the program
produces the correct results for a set of test data. It refers to the different set
of activities that ensures that the software that has been built is traceable to
custom requirements.
BOEHM states these terms as
39
VERIFICATION—“Are we building the product right?”
VALIDATION—“Are we building the right product?”
The debugging of microprocessor programs is generally quite difficult

because of the inability to observe register contents directly, the primitive
debugging aids, the close interaction between hardware & software, the
frequent dependence of programs on precise timing, and the difficulty of
obtaining adequate data for real-time applications, The tools that can be used
by programs with brief description are given below: -
Simulators: -
It is a compute program that simulates the execution of programs on another

computer.
Logical Analyzers:
It is a test instrument that is the digital bus-oriented version of the

oscilloscope. It detects the states of digital signals during each clock cycle &
stores them in the memory. It then displays the information on a CRT, much
as an oscilloscope does.
Breakpoints: -
It is place in a program at which execution can be halted, in order to

examine the current contents of registers, memory locations & I/O ports.
40
Trace Routines: -
A trace is a program that prints information concerning the status of the

processor at specified intervals. Most simulator program & some
microcomputer development system have trace facilities.
Memory Dumps: -
A memory dump is a listing of the current contents of a section of the

memory. Most simulator programs, microcomputer development systems &
monitors can produce memory dumps.
Software Interrupts: -
The software interrupts or trap instruction is frequently used for debugging

purposes. The instruction usually saves the current value of the program
counter & then branches to a specified memory location. That information
location can be the starting point of a debugging program that lists or
displays status information – breakpoint may be inserted with trap
instructions.
41
SECURITY OF THE SYSTEM
While setting up a system aspect should be kept in mind for various reasons
like privacy of data, investment costs and levels this can be achieved by
appointing system administrator, users control supervisor etc. this
organization that depends heavily on information. These controls are
classified into:
 Physical security: This security of system is performed by the protection

from fire, flood and other physical damages. For that many measures are
taken such as hardware locks, preventing access of unauthorized person
from entering the system area, keep the floppy and disk in face custody,
keeping any heat generating appliances away from the system. Obtaining
insurance cover against the risk and natural calamities.
 Database integrity: to maintain the data integrity many data validation

techniques are used so that the user cannot enter any unauthorized data.
The access of database is possible only to responsible user through
password.
 Operating system level security: The measures is taken by giving no

permission to the direct access to the data in primary memory or to online
files, which protect it’s both program and data.
 Application security: The application has also given a security

measures, so that no unauthorized person can enter the application, by
giving the password at the start of the program.
 Administration security: By monitoring user on regular basis.
42
OUTPUT
43
44
45
46
47
48
49
50
51
52
53
54
55
56
CODING
57
LOGINFORM
Private Sub cmdexit_Click()

End
End Sub
Private Sub CMDOK_Click()

Data1.Refresh
If txtlogin.Text = Data1.Recordset.Fields("login") And txtpassword.Text =
Data1.Recordset.Fields("password") Then
Unload Me
Splashform.Show
Else
ans = MsgBox("Incorrect, Try again ", vbYesNo + vbQuestion)
If ans = vbYes Then
txtlogin.SetFocus
Else
End
End If
End If
End Sub
Private Sub Form_Load()

Data1.DatabaseName = App.Path + "\madicaldatabase.mdb"
58
Data1.RecordSource = "logintable"
End Sub
SPLASHFORM
Private Sub Timer1_Timer()

Static i As Integer
If i = 100 Then
Unload Me
Mainform.Show
Else
ProgressBar1.Value = i
i=i+1
End If
End Sub
MAINFORM
Private Sub addopt_Click()

Add_supplier.Show
End Sub
Private Sub dispstk_Click()

Stockform.Show
59
End Sub
Private Sub ed_Click()

Deleteeditsale.Show
End Sub
Private Sub Listsupplier_Click()

Suppreport.Show
End Sub
Private Sub MDIForm_Load()

Me.WindowState = 2
End Sub
Private Sub Modifyopt_Click()

EDITDELETESUPP.Show
End Sub
Private Sub Purchaseopt_Click()

purchase.Show
End Sub
Private Sub Purchassopt_Click()

purchasereg.Show
End Sub
Private Sub Reportopt_Click()
60
STKSEARCH.Show
End Sub
Private Sub Saleopt_Click()

Saleform.Show
End Sub
Private Sub Saleopt2_Click()

Saleregister.Show
End Sub
Private Sub Searchingopt_Click()

Del_Edit_purchase.Show
End Sub
ADD_SUPPLIER
Private Sub cmdsave_Click()

On Error GoTo message
Data1.Refresh
Data1.Recordset.AddNew
Data1.Recordset.Fields("SNO") = txtsno.Text
Data1.Recordset.Fields("SName") = txtsname.Text
Data1.Recordset.Fields("ADDRESS") = txtaddress.Text
Data1.Recordset.Fields("PHONE") = TXTPHONE.Text
61
Data1.Recordset.Update
txtsno.Text = ""
txtsname.Text = ""
txtaddress.Text = ""
TXTPHONE.Text = ""
MsgBox "Successfully saved", vbExclamation

Exit Sub
message:
MsgBox "Invalid data", vbExclamation
End Sub
Private Sub cmdclear_Click()

txtsno.Text = ""
txtsname.Text = ""
TXTPHONE.Text = ""
txtsno.SetFocus
End Sub

Me.Hide
End Sub

Data1.RecordSource = "SUPPtab"
62
End Sub
EDIT_SUPPLIER
Private Sub CMDDELETE_Click()

a = MsgBox("are you sure", vbYesNo + vbQuestion)
If a = vbYes Then
Data1.Recordset.Delete
Data1.Refresh
txtsno.Text = ""
txtsname.Text = ""
TXTPHONE.Text = ""
MsgBox "Successfully deleted", vbExclamation
End If
Exit Sub
mssage:
End Sub

Me.Hide
63
End Sub
Private Sub CMDSEARCH_Click()

Data1.Refresh
Data1.Recordset.FindFirst "SNO=" & txtsno.Text
If Data1.Recordset.NoMatch Then
MsgBox "NOT FOUND", vbExclamation
Else
txtsname.Text = Data1.Recordset.Fields("SNAME")
txtaddress.Text = Data1.Recordset.Fields("ADDRESS")
TXTPHONE.Text = Data1.Recordset.Fields("PHONE")
End If
Exit Sub
message:
End Sub
Private Sub CMDUPDATE_Click()

Data1.Recordset.Edit
Data1.Recordset.Fields("sno") = txtsno.Text
Data1.Recordset.Fields("sname") = txtsname.Text
Data1.Recordset.Fields("address") = txtaddress.Text
Data1.Recordset.Fields("phone") = TXTPHONE.Text
64
End Sub
Private Sub Form_Activate()

txtsno.AddItem 1
txtsno.AddItem 2
txtsno.AddItem 4
txtsno.AddItem 32
End Sub

End Sub
PURCHASE

TXTORDERNO.Text = ""
txtpdate.Text = ""
txtsno.Text = ""
txtsname.Text = ""
txttype.Text = ""
65
txtmname.Text = ""
txtcompany.Text = ""
txtmdate.Text = ""
txtexpdate.Text = ""
txtrate.Text = ""
txtqty.Text = ""
txtbill.Text = ""
TXTORDERNO.SetFocus
End Sub

Data2.Refresh
Data2.Recordset.Fields("orderno") = TXTORDERNO.Text
Data2.Recordset.Fields("purchasedate") = txtpdate.Text
Data2.Recordset.Fields("medicinetype") = txttype.Text
Data2.Recordset.Fields("mname") = txtmname.Text
Data2.Recordset.Fields("compname") = txtcompany.Text
Data2.Recordset.Fields("mdate") = txtmdate.Text
Data2.Recordset.Fields("expdate") = txtexpdate.Text
Data2.Recordset.Fields("rate") = txtrate.Text
Data2.Recordset.Fields("qty") = txtqty.Text
Data2.Recordset.Fields("bill") = txtbill.Text
66
'Update stock
Data3.Refresh
Data3.Recordset.FindFirst "medicinename='" & txtmname.Text & " ' "
Data3.Recordset.Fields("medicinename") = txtmname.Text
Data3.Recordset.Fields("company") = txtcompany.Text
Else
Data3.Recordset.Fields("qty") = Data3.Recordset.Fields("qty") +
Val(txtqty.Text)
End If
txtpdate.Text = ""
txtsno.Text = ""
txtsname.Text = ""
67
txttype.Text = ""
txtmname.Text = ""
txtmdate.Text = ""
txtrate.Text = ""
txtqty.Text = ""
txtbill.Text = ""
Exit Sub
message:
End Sub

Me.Hide
End Sub

txtsno.Clear
Data1.Refresh
While Data1.Recordset.EOF = False
txtsno.AddItem Data1.Recordset.Fields("sno")
68
Data1.Recordset.MoveNext
Wend
txttype.Clear
txttype.AddItem "Tablet"
txttype.AddItem "Capsule"
txttype.AddItem "Syrup"
txttype.AddItem "Injection"
End Sub

Data1.RecordSource = "supptab"
Data2.RecordSource = "purchasetab"
Data3.RecordSource = "stocktable"
End Sub
Private Sub txtqty_Change()

txtbill.Text = Val(txtrate.Text) * Val(txtqty.Text)
End Sub
69
Private Sub txtrate_Change()
End Sub
Private Sub TXTSNO_Click()

Data1.Refresh
Data1.Recordset.FindFirst "sno=" & txtsno.Text
MsgBox "Not found", vbExclamation
Else
txtsname.Text = Data1.Recordset.Fields("sname")
txtaddress.Text = Data1.Recordset.Fields("address")
End If
End Sub
DEL_EDIT_PURCHASE
a = MsgBox("Are you sure ", vbYesNo + vbQuestion)

If a = vbYes Then
70
txtpdate.Text = ""
txtsno.Text = ""
txtsname.Text = ""
txttype.Text = ""
txtmname.Text = ""
txtmdate.Text = ""
txtqty.Text = ""
txtrate.Text = ""
txtbill.Text = ""
End If
End Sub

Me.Hide
End Sub

71
Data2.Recordset.Fields("orderno") = TXTORDERNO.Text
Data2.Recordset.Fields("purchasedate") = txtpdate.Text
Data2.Recordset.Fields("medicinetype") = txttype.Text
Data2.Recordset.Fields("compname") = txtcompany.Text
Data2.Recordset.Fields("bill") = txtbill.Text
txtpdate.Text = ""
txtsno.Text = ""
txtsname.Text = ""
txttype.Text = ""
txtmname.Text = ""
txtmdate.Text = ""
txtrate.Text = ""
txtqty.Text = ""
txtbill.Text = ""
72
Exit Sub
message:
End Sub

Data1.Refresh
TXTORDERNO.AddItem Data1.Recordset.Fields("ORDERNO")
Wend
End Sub

Data1.RecordSource = "purchasetab"
End Sub
Private Sub TXTORDERNO_Click()

Data1.Refresh
Data1.Recordset.FindFirst "orderno=" & TXTORDERNO.Text
Else
73
txtpdate.Text = Data1.Recordset.Fields("purchasedate")
txtsno.Text = Data1.Recordset.Fields("sno")
txtsname.Text = Data1.Recordset.Fields("sname")
txttype.Text = Data1.Recordset.Fields("medicinetype")
txtmname.Text = Data1.Recordset.Fields("mname")
txtcompany.Text = Data1.Recordset.Fields("compname")
txtmdate.Text = Data1.Recordset.Fields("mdate")
txtexpdate.Text = Data1.Recordset.Fields("expdate")
txtqty.Text = Data1.Recordset.Fields("qty")
txtrate.Text = Data1.Recordset.Fields("rate")
txtbill.Text = Data1.Recordset.Fields("bill")
End If
End Sub
SALEFORM

txtsale.Text = ""
txtcno.Text = ""
txtcname.Text = ""
txttype.Text = ""
74
txtmname.Text = ""
txtmdate.Text = ""
txtrate.Text = ""
txtqty.Text = ""
txtbill.Text = ""
End Sub

Me.Hide
End Sub

Data1.Refresh
Data1.Recordset.Fields("ono") = TXTORDERNO.Text
Data1.Recordset.Fields("dos") = txtsale.Text
Data1.Recordset.Fields("cno") = txtcno.Text
Data1.Recordset.Fields("cName") = txtcname.Text
Data1.Recordset.Fields("mtype") = txttype.Text
75
Data1.Recordset.Fields("bamount") = txtbill.Text
'update stock
Data3.Refresh
Data3.Recordset.FindFirst "medicinename='" & txtmname.Text & " ' "
Data3.Recordset.Fields("qty") = Data3.Recordset.Fields("qty") -
Val(txtqty.Text)
txtsale.Text = ""
txtcno.Text = ""
txtcname.Text = ""
txttype.Text = ""
txtmname.Text = ""
txtmdate.Text = ""
76
txtrate.Text = ""
txtqty.Text = ""
txtbill.Text = ""
Exit Sub
message:
End Sub
txttype.Clear
txttype.AddItem "Tablet"
txttype.AddItem "Capsule"
txttype.AddItem "Syrup"
txttype.AddItem "Injection"
End Sub

Data1.RecordSource = "saletable"
77
End Sub
Private Sub txtqty_Change()

End Sub
Private Sub txtrate_Change()

End Sub
EDITSALE
a = MsgBox("Are you sure ", vbYesNo + vbQuestion)

If a = vbYes Then
txtpdate.Text = ""
txtsno.Text = ""
txtsname.Text = ""
78
txttype.Text = ""
txtmname.Text = ""
txtmdate.Text = ""
txtqty.Text = ""
txtrate.Text = ""
txtbill.Text = ""
End If
End Sub

Me.Hide
End Sub

Data1.Recordset.Fields("ono") = TXTORDERNO.Text
Data1.Recordset.Fields("dos") = txtsale.Text
Data1.Recordset.Fields("cno") = txtcno.Text
Data1.Recordset.Fields("cName") = txtcname.Text
Data1.Recordset.Fields("mtype") = txttype.Text
79
Data1.Recordset.Fields("bamount") = txtbill.Text
txtsale.Text = ""
txtcno.Text = ""
txtcname.Text = ""
txttype.Text = ""
txtmname.Text = ""
txtmdate.Text = ""
txtrate.Text = ""
txtqty.Text = ""
txtbill.Text = ""
Exit Sub
message:
80
End Sub

Data1.Refresh
TXTORDERNO.AddItem Data1.Recordset.Fields("ONO")
Wend
End Sub

End Sub
Private Sub TXTORDERNO_Click()

Data1.Refresh
Data1.Recordset.FindFirst "ono=" & TXTORDERNO.Text
Else
txtsale.Text = Data1.Recordset.Fields("dos")
txtcno.Text = Data1.Recordset.Fields("cno")
txtcname.Text = Data1.Recordset.Fields("cname")
txttype.Text = Data1.Recordset.Fields("mtype")
81
txtmname.Text = Data1.Recordset.Fields("mname")
txtcompany.Text = Data1.Recordset.Fields("company")
txtmdate.Text = Data1.Recordset.Fields("mdate")
txtexpdate.Text = Data1.Recordset.Fields("expdate")
txtqty.Text = Data1.Recordset.Fields("qty")
txtrate.Text = Data1.Recordset.Fields("rate")
txtbill.Text = Data1.Recordset.Fields("bamount")
End If
End Sub
PURCHASEREG
Private Sub Command1_Click()

'Me.PrintForm
End Sub

Data1.RecordSource = "PURCHASETAB"
End Sub
SALEREG

82
End Sub
STOCKREG

Me.Hide
End Sub

End Sub
STOCKSEARCH

Me.Hide
End Sub
Private Sub Command1_Click()

Data1.Refresh
Data1.RecordSource = "select * from stocktable where medicinename='" &
Text1.Text & " ' "
83
Data1.Refresh
End Sub

End Sub
LISTSUPPLIER

Me.Hide
End Sub

End Sub
84
BIBLIOGRAPHY
The following are the books references that have been studied in the
duration of making of this project.
 Mastering in vb6.0
 Microsoft office
 Black book of vb6
WEB REFRENCES
www.microsoft.com
85

Medical Agency

Uploaded by

Copyright:

Available Formats

Medical Agency

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Medical Agency

Uploaded by

Copyright:

Available Formats

A

Submitted towards partial fulfillment of the requirement

“BACHELOR OF COMPUTER APPLICATION”

Indira Gandhi National Open University

The aim of this project i.e Medical Agency Management System is to

If a document that completely describes what the proposed software should

There are some steps which are considered in the SOFTWARE

IT Examine the operations of the software as a consequence of external

Hardware is the term given to machinery itself and to various individual

It refers to the physical devices of a computer system. Thus the input,

Minimum Hardware Requirement Of Client Side:

Processor : Any Pentium IV or Equivalent Machine

To use this software, some software are required. Software means a

Minimum Software Requirement Of Client Side:

Operating System : Windows Operating System

Introduction to data dictionary:

Data dictionaries are an integral component of structured analysis, since data

Data Dictionary (Definition):

A data dictionary is a catalog- a repository- of the elements in a system.

Describing Data Elements:

Field Name Data Type

Field Name Data Type

Field Name Data Type

Field Name Data Type

Field Name Data Type

Definition of Analysis and Design:

Analysis and design refers to the process of examining a business situation

Overview of Analysis and Design:

System development can generally be thought of as having two major

Indirect Users benefit from the results or reports produced by these

In the broad sense, a system is simply a set of components that interact to

 Systems Development Life Cycle.

Systems Development Life Cycle:

Systems development, a process consisting of two major steps of

SDLC consists of following activities:

 Determination of system requirements.

Two main steps of development are:

System analysis is conducted with the following objectives in mind:

 Identify the user’s need.

The analysis model must achieve three primary objectives:-

1. To describe the requirements of the customer.

An Overview to system analysis

The system analysis phase is considered to be one of the most important

Requirement analysis is done in order to understand the problem which the

The main objective behind any business organization is to maximize its

The most important objective behind automation is to minimize Paper

By making the manual system computerized, we can ensure complete

In the area of information technology, it is need of hour to have a fast

 Delay in information search and retrieval

After computerization of the system, it will be helpful for

 Easy storage and retrieval of data

Requirement Collection and Analysis

Most information regarding identification of user group and application

I was assigned the duty for developing a computerized system known as

It is vital that the field of application as introduced in the project may be

Modular Break –Up Of The System:

 Identify The Various Modules In The System.

Module 1: Password Module

Module 4: Purchase and Sale