INDEX

ABSTRACT
Introduction
Introduction to Project
Introduction to Organization
System Analyses
Introduction
Existing System
Proposed System
Feasibility Study
System Requirement
Introduction
Functional Requirements
System Requirements
Software Requirements
Hardware Requirements
System Design
Introduction
High Level Design
System Design
Subsystem Design
Block Design
Low Level Design
UML Diagrams
Data Flow Diagrams
Use case Diagrams
Sequence Diagrams
Class Diagrams
1

Object Diagrams
Activity Diagrams
State chart Diagrams
Activity Diagrams
Collaboration Diagrams
Component Diagrams
Deployment Diagrams
Coding
Testing
Screen Shots
Conclusion
Bibliography

ABSTRACT
This Project Drug Order Management System is a solution to Aurobindo Pharma to take the
orders from its distributors who are geographically distributed. This new system not only takes
the orders from distributors for Aurobindo Pharma but it also facilities.The administration, as
well as the report generation for the firm.
Each user of this system is given a unique id and password along with some Information for our
report generation, and administration. Later the user id will be used for his identification. The
system maintains vendors, category of products they are supplying, products under each
category, discount, and payment modes such as DD, Cheque, and online payment mode Credit
Card. This system also maintains the order details, to provide the valuable reports regarding
sales to the organization whenever they want. Here we are providing the administration part too
for the organization.This system provides information entered but also analyzes data. Each
users details are kept private and no other body can tinker with them.
Existing System
1. In this we could store the data manually.
2. In the existing system data storing was not so easy.
3. Retrieving data is very difficult.

Proposed System
The proposed system can be accessed from any part of the world, as opposed to stand alone or
manual system, and provides information at any time, anywhere.
Even though it is a web-based application it will keep the details of its clients private and no
body is allowed to tinker with the details.
No need to own any computer for this specific ordering of products, it just requires user to
register with the system.It provides easy to use and user friendly interface for the user.
The organization people can do administration over the products, vendor, customer (only deletion
in case of dealer ship cancellation) etc.

Modules
1. Administration Module
2. Reports Module
3. EndUser Module
4. WebUserInterface Module
.

Administration Module
In this module admin can add product details, vendors details,category details,discount
details,stock detals and view customer details.And also he could update,delete the product,
vendors,category details,discount details,stock details.

Reports Module
In this module we could view all the information regarding like how many number of customers,
vendors.We can view differerent catogaries of products.we could view different discount details
and also we view stock details.

EndUser Module
In this module customers send orders for products to admin.

WebUserInterface
Web user Interface will provide the interface to the user to communicate with the system.

System Specifications
Software Requirements
Operating System

Windows XP

User Interface

HTML, CSS

Client-side Scripting

JavaScript

Programming Language

Java

Web Applications

JDBC, Servlets, JSP

Database

Mysql

Server Deployment

Apache Tomcat

Hardware Requirements
Processor

Pentium IV

Hard Disk

160GB

RAM

1GB

Process flow Diagram or architecture Diagram

Introduction
This Project Drug Order Management System is a solution to Aurobindo Pharma to take the
orders from its distributors who are geographically distributed. This new system not only takes
the orders from distributors for Aurobindo Pharma but it also facilities.The administration, as
well as the report generation for the firm.
Each user of this system is given a unique id and password along with some Information for our
report generation, and administration. Later the user id will be used for his identification. The
system maintains vendors, category of products they are supplying, products under each
category, discount, and payment modes such as DD, Cheque, and online payment mode Credit
Card. This system also maintains the order details, to provide the valuable reports regarding
sales to the organization whenever they want. Here we are providing the administration part too
for the organization.This system provides information entered but also analyzes data. Each
users details are kept private and no other body can tinker with them.

INTRODUCTION TO ORGANIZATION
NeoApp Profile
NeoApp develops custom software solutions for companies in a variety of industries. Since its
beginning in August 2008, NeoApp has offered efficient, reliable and cost-effective solutions
with good quality by implementing CMMI practices from its development facility located at
Hyderabad.
NeoApp has expertise in latest technologies and caters to your exacting requirements. NeoApp
helps you from concept to completion of a project with full range of service offerings.
Most importantly, NeoApp combines the right strategy with the right products and the right
people, ensuring technical superiority, high quality deliverables and timely implementations.
NeoApp supports different delivery and billing models to fit your requirements. By having
NeoApp involved with your software development projects, you benefit with reduced costs and
faster development cycles. To reduce the development costs NeoApp strictly adhere on reusable
component model with plug and play architecture.
Offshore outsourcing model became easily adoptable and has increased benefits beyond cost
reductions. The offshore outsourcing with NeoApp includes full spectrum services and multi fold
benefits.
NeoApp, with its experience in executing offshore projects ranging from large enterprise
solutions to small plug-in applications, helps customers achieve the offshore outsourcing goals.
NeoApp establishes suitable project execution methodologies for each project and accomplishes
offshore execution on time and on budget. NeoApp pays high importance to quality of
deliverables and has mandatory quality doors in place for each project ensuring success of the
overall project.
NeoApp works with you from conceptualization to completion and has the required expertise to
pick up the project at any stage in its life cycle.
1. Business concept and system study
2. Requirement Study
3. Design Architecture and develop specifications
4. Design the framework of the solution
5. Develop the solution
6. QA the solution against requirements
7. Continuous support for the solution
8. Develop prototypes for proof of concept
9. Engineer the solution
10. Release as per plan

The team and project approach of NeoApp has resulted in above expected deliveries of projects.
NeoApp works with you in refining the project at every stage and with its vast and experienced
talent pool, NeoApp brings value with innovation to the project.
NeoApp offers complete solutions to application maintenance requirements helping
organizations to cut costs and optimize resource utilization. NeoApp performs the following
tasks on a variety of technology platforms beginning with Legacy to Client Server to Browser
based internet application.

1. Application Development
2. Application Maintenance
3. Application Support
NeoApp with its experience in wide range technologies and ability to learn quickly help you
ensuring availability of your systems to your customers. NeoApp performs systems monitoring
and undertakes evolutionary development of these applications as required and deemed fit.

SYSTEM ANALASYS
Analysis is the process of understanding the existing system by gathering and interpreting the
facts, diagnosing the problems. It is not just to determining the how best to solve the manual
system problems, it should also work for the system observes the feasibility of system then
design, coding phases will be executed. Analysis phase delivers requirements specification .The
system specification serves as an interface between the designer and developer as well as
between developers and users. This describes the external behavior of the software without
bothering about the internal implementation. Specification must be carefully checked for
suitability, omission, inconsistencies and ambiguities.
Problem analysis is performed to getting a clear understanding of the needs of the clients and the
users and what exactly desired form the software. Analysis leads to the actual specification.
During the process of analysis, a massive amount of information is collected in the form of
interviews, questionnaires, and information from documentation, and so forth. The major
problem during analysis is resolving how to organize the information from documentation, and
so forth. So the information can be effectively evaluated for completeness and consistency.

Existing System
4. In this we could store the data manually.
5. In the existing system data storing was not so easy.
6. Retrieving data is very difficult.

Proposed System
The proposed system can be accessed from any part of the world, as opposed to stand alone or
manual system, and provides information at any time, anywhere.
Even though it is a web-based application it will keep the details of its clients private and no
body is allowed to tinker with the details.
No need to own any computer for this specific ordering of products, it just requires user to
register with the system.It provides easy to use and user friendly interface for the user.
The organization people can do administration over the products, vendor, customer (only deletion
in case of dealer ship cancellation) etc.

10

FEASIBILITY STUDY
All projects are feasible given unlimited resources and infinite time! Unfortunately, the
development of computer-based system or product is more likely plagued by a scarcity of
resources and difficult delivery dates. It is both necessary and prudent to evaluate the feasibility
of a project at the earliest possible time. Months or years of effort, thousands or millions of
dollars, and untold professional embarrassment can be averted if an ill-conceived system is
recognized early in the definition phase.
Feasibility and risk analysis are related in many ways. If project risk is great the
feasibility of producing quality software is reduced. During product engineering, however, we
concentrate our attention on four primary areas of interest

Technical Feasibility
This application in going to be used in an Internet environment called www (World wide web).
So, it is necessary to use a technology that is capable of providing the networking facility to the
application. This application as also able to work on distributed environment. Application on
developed with J2EE (Java 2 Enterprise Edition platform) Technology. One major advantage in
application is platform neutral. We can deploy and used it in any operating system.
GUI is developed using HTML.to capture the information from the customer. HTML is used to
display the content on the browser. It uses TCP/IP protocol. It is an interpreted language. It is
very easy to develop a page/document using HTML some RAD(Rapid Application
Development) tools are provided to quickly design/develop our application. So many objects
such as button, text fields, and text area etc are provide to capture the information from the
customer.
We can use this application in any OS. They can have their own security and transactional
advantages. But are the responsible for selecting suitable and secured OS, which is suitable to
our application.
The back-end Oracle 8i and front-end application are platform independent. So we can port this
enterprise application in any environment. Both are having their individual configuration to get
better performance and backup issues.

11

Economical Feasibility
In present system customer need to go to billers place to pay the bill. So he/she needs to spend
some time to complete this protocol. It is time consuming process some times customer not able
to spend that much of time. In such case needs to pay some additional payment to the biller for
late payment.
If it is developed in electronic payment system, He can pay the bill from any where in the world.
No need to travel to pay the bills. For doing this process electronically have to spend some time.

Operational Feasibility
In our application front end is developed using GUI. So it is very easy to the customer to enter
the necessary information. But customer has some knowledge on using web applications before
going to use our application.

12

SYSTEM REQUIREMENTS
INTODUCTION
Software Requirements Specification plays an important role in creating quality software
solutions. Specification is basically a representation process. Requirements are represented in a
manner that ultimately leads to successful software implementation.
Requirements may be specified in a variety of ways. However there are some guidelines worth
following: Representation format and content should be relevant to the problem
Information contained within the specification should be nested
Diagrams and other notational forms should be restricted in number and consistent in use.
Representations should be revisable.
The software requirements specification is produced at the culmination of the analysis task. The
function and performance allocated to the software as a part of system engineering are refined by
establishing a complete information description, a detailed functional and behavioral description,
and indication of performance requirements and design constraints, appropriate validation
criteria and other data pertinent to requirements.

Functional Requirements
This section contains specification of all the functional requirements needed to develop this
module or sub-module.

13

Requirement ID

Requirement Specification

DOMS_01

System should provide a provision for admin to login.

DOMS_02

System should provide a provision for admin to add product details.

DOMS_03

System should provide a provision for admin to update product details.

DOMS_04

System should provide a provision for admin to delete product details.

DOMS_05

System should provide a provision for admin to view customers

details.
System should provide a provision for admin to delete customers
details.
System should provide a provision for admin to add vendors details.

DOMS_06
DOMS_07
DOMS_08
DOMS_09

System should provide a provision for admin to update vendors

details.
System should provide a provision for admin to delete vendors details.

DOMS_10

System should provide a provision for admin to add catogery details.

DOMS_11
DOMS_12

System should provide a provision for admin to update catogery

details.
System should provide a provision for admin to delete catogery details.

DOMS_13

System should provide a provision for admin to add discount details.

DOMS_14
DOMS_15

System should provide a provision for admin to update discount

details.
System should provide a provision for admin to delete discount details.

DOMS_16

System should provide a provision for admin to add stock details.

DOMS_17

System should provide a provision for admin to update stock details.

DOMS_18

System should provide a provision for admin to add stock details.

DOMS_19

System should provide a provision for admin to view product details.

DOMS_20

System should provide a provision for admin to view order details

14

Priority
(A/B/C)

DOMS_21

System should provide a provision for admin to view catogery details.

DOMS_22

System should provide a provision for admin to view discount details.

DOMS_23

System should provide a provision for admin to view vendors details.

DOMS_24

System should provide a provision for admin to view registration details.

DOMS_25

System should provide a provision for enduser to registration.

DOMS_26

System should provide a provision for enduser to login.

DOMS_27
DOMS_28

System should provide a provision for enduser to send order details to the
admin.
System should provide a provision for end user to logout.

DOMS_29

System should provide a provision for admin to logout.

15

Non-Functional Requirements
Usability: Usability is the ease of use and learns ability of a human-made object. The object of
use can be a software application, website, book, tool, machine, process, or anything a human
interacts with. A usability study may be conducted as a primary job function by a usability
analyst or as a secondary job function by designers, technical writers, marketing personnel, and
others.
Reliability: The probability that a component part, equipment, or system will satisfactorily
perform its intended function under given circumstances, such as environmental conditions,
limitations as to operating time, and frequently and thoroughness of maintenance for a specified
period of time.
Performance: Accomplishment of a given task measured against preset standards of accuracy,
completeness, cost, and speed.
Supportability: To which the design characteristics of a stand by or support system meet the
operational requirements of an organization.
Implementation: Implementation is the realization of an application, or execution of a plan,
idea, model, design, specification, standard, algorithm, or policy.
Interface: An interface refers to a point of interaction between components, and is applicable at
the level of both hardware and software. This allows a component whether a piece of hardware
such as a graphics card or a piece of software such as an internet browser to function
independently while using interfaces to communicate with other components via an input/output
system and an associated protocol.
Legal: It is established by or founded upon law or official or accepted rules of or relating to
jurisprudence; legal loophole.
Having legal efficacy or force, a sound title to the property
Relating to or characteristic of the profession of law, the legal profession.
Allowed by official rules; a legal pass receiver.

16

Software Requirements
Operating System

Windows XP

User Interface

HTML, CSS

Client-side Scripting

JavaScript

Programming Language

Java

Web Applications

JDBC, Servlets, JSP

Database

Mysql

Server Deployment

Apache Tomcat

Hardware Requirements
Processor

Pentium IV

Hard Disk

160GB

RAM

1GB

17

DESIGN
DESIGN SPECIFICATION
Design of software involves conceiving planning out and specifying the externally
observable characteristics of the software product. We have data design, architectural design and
user interface design in the design process. These are explained in the following section. The
goals of design process it to provide a blue print for implementation, testing, and maintenance
activities.

DATA DESIGN
The primary activity during data design is to select logical representations of data objects
identified during requirement analysis and software analysis. A data dictionary explicitly on the
elements of the data structure. A data dictionary should be established and used to define both
data and program design.

DESIGN METHODOLOGY
The two basic modern design strategies employed in software design are
Top Down Design
Bottom Up Design
Top Down Design is basically a decomposition process, which focuses on the flow of control. At
later stages it concern itself with the code production. The first step is to study the overall
aspects of the tasks at hand and to break it into a number of independent modules. The second
step is to break each one of these modules further into independent sub-modules. The process is
Repeated one to obtain modules, which are small enough to group mentally and to code in a
straightforward manner. One important feature is that at each level the details of the design at the
lower level are hidden. Only the necessary data and control that must be called back and forth
over the interface are defined.
In a bottom-up design one first identifies and investigates parts of design that are most
difficult and necessary designed decision are made the reminder of the design is tailored to fit
around the design already chose for crucial part. It vaguely represents a synthesis process
explained in previous section.
One storage point of the top-down method is that it postpones details of the decision
until the last stage of the decision. It allows making small design changes when the design is
half way through. There is danger that the specifications will be incompatible and this will not
be discovered until late in the design process. By contrast the bottom-up strategy first focuses on
the crucial part so that feasibility of the design is tested at early stage.
In mixing top-down and bottom-up design it often appears that we start in the middle of
the problem and work our way both up and down there. In a complex problem, it is often

18

difficult to decide how to modularize the various procedures in such cases one might consider a
list of system inputs and decide what functions are necessary to process these inputs. This is
called back to front design.

Similarly one can start with the required outputs and work

backwards evolving so called front-back design. We have applied both the top down and bottom
up approach in our design approach.

DATABASE DESIGN
Databases are normally implemented by using a package called a Data Base
Management System (DBMS). Each particular DBMS has somewhat unique characteristics, and
so such, general techniques for the design of database are limited. One of the most useful
methods of analyzing the data required by the system for the data dictionary has developed from
research into relational database, particularly the work of E.F.Codd. this method of analyzing
data is called Normalization. Unnormalized data are converted into normalized data by three
stages. Each stage has a procedure to follow.

NORMALIZATION
The first stage is normalization is to reduce the data to its first normal form, by removing
repeating items showing them as separate records but including in them the key fields of the
original record.
The next stage of reduction to the second normal form is to check that the record, which
one is first normal form, all the items in each record are entirely dependent on the key of the
record. If a data item is not dependent on the key of the record, but on the other data item, then it
is removed with its key to form another record. This is done until each record contains data
items, which are entirely dependent on the key of their record.
The final stage of the analysis, the reduction of third normal form involves examining
each record, which one is in second normal form to see whether any items are mutually
dependent. If there are any item there are removed to a separate record leaving one of the items
behind in the original record and using that as the key in the newly created record.

19

BUSINESS MODELING:
The information flow among business function is modeled in a way that answers the following
questions: what information drives the business process? What information is generated? What
generate it? Where does the information go? Who process it?

DATA MODELING:
The information flow defined as a process of the business modeling is refined into a set of data
objects that are needed to support the business. The characteristics 9called attributes0 of each
object are identified and relationships between these objects are defined.

PROCESS MODELING:
The data objects defined in the data-modeling phase are transformed to achieve the information
flow necessary to implement a business function. Processing description is created for addition,
modifying, deleting, or retrieving a data object.

OBJECT DESIGN
During the object design, we fill the gap between the application objects and the off-the-self
components, which provide a high level abstraction. It is done by identifying additional solution
objects and refining the existing objects.

Reusing Pattern Solutions:

Application objects also called domain objects, represent concepts of the domain that are
relevant to the system. Solution objects represent components that dont have a counterpart in the
application part domain, such as persistent data stores, user interface objects, or middleware.

Specification inheritance and implementation:

The focus of inheritance during Object Design is on Redundancy reduction and enhancement of
extensibility. The implementation of inheritance for the sole purpose of reusing the code is
known as Implementation inheritance, by which we reuse code quickly by sub classing an
existing class and refining its behavior.

INPUT DESIGN
The input design is the link between the information system and the user. It comprises the
developing specification and procedures for data preparation and those steps are necessary to put
transaction data in to a usable form for processing can be achieved by inspecting the computer to
read data from a written or printed document or it can occur by having people keying the data
directly into the system. The design of input focuses on controlling the amount of input required,
controlling the errors, avoiding delay, avoiding extra steps and keeping the process simple. The

20

input is designed in such a way so that it provides security and ease of use with retaining the
privacy. Input Design considered the following things:
What data should be given as input?
How the data should be arranged or coded?
The dialog to guide the operating personnel in providing input.
Methods for preparing input validations and steps to follow when error occur.

OBJECTIVES
1.Input Design is the process of converting a user-oriented description of the input into a
computer-based system. This design is important to avoid errors in the data input process and
show the correct direction to the management for getting correct information from the
computerized system.

2. It is achieved by creating user-friendly screens for the data entry to handle large volume of
data. The goal of designing input is to make data entry easier and to be free from errors. The data
entry screen is designed in such a way that all the data manipulates can be performed. It also
provides record viewing facilities.

3.When the data is entered it will check for its validity. Data can be entered with the help of
screens. Appropriate messages are provided as when needed so that the user will not be in maize
of instant. Thus the objective of input design is to create an input layout that is easy to follow.

OUTPUT DESIGN
A quality output is one, which meets the requirements of the end user and presents the
information clearly. In any system results of processing are communicated to the users and to
other system through outputs. In output design it is determined how the information is to be
displaced for immediate need and also the hard copy output. It is the most important and direct
source information to the user. Efficient and intelligent output design improves the systems
relationship to help user decision-making.
1. Designing computer output should proceed in an organized, well thought out manner; the right
output must be developed while ensuring that each output element is designed so that people will

21

find the system can use easily and effectively. When analysis design computer output, they
should Identify the specific output that is needed to meet the requirements.
2. Select methods for presenting information.
3. Create document, report, or other formats that contain information produced by the system.
The output form of an information system should accomplish one or more of the following
objectives.
Convey information about past activities, current status or projections of the
Future.
Signal important events, opportunities, problems, or warnings.
Trigger an action.
Confirm an action.

22

High Level Design

System Design
Understanding bigger application with its external interfaces is called
System Design.

Drug Order
Management
System

Data
base

Sub System Design:

Understanding bigger system into smaller independent working
systems is called subsystem design.

WUI

DOMSystem
Businesslogic
subsystem

23

Datab
ase
Subsy
stem

Block Design

WUI

Administration

Reports

DB Storage

Enduser

In this application each and every user must having their own User ID and Password, using these
User ID and Password only they can directly enter into their corresponding Login forms.
After enter into their Login forms each user will interact with the following functionalities.
But according to their responsibilities only they will use the above functionalities.

WUI (Web User Interface)

Web user Interface will provide the interface to the user to communicate with the system.
DB Storage
This block helps us to store the data or retrieve the data from database.
Administration Block
In this module admin can add product details,vendors details,category details,discount
details,stock detals.And also he could update,delete the product,vendors,category details,discount
details,stock details.
Reports Block
In this module we could view all the information regarding like how many number of customers,
vendors.We can view differerent catogaries of products.we could view different discount details
and also we view stock details.

24

EndUser Block
In this module customers send orders for products to admin.

Uml Diagrams
Data Flow Diagrams
The data flow diagram is used for classifying system requirements to major transformation that
will become programs in system design. This is starting point of the design phase that
functionally decomposes the required specifications down to the lower level of details. It consists
of a series of bubbles joined together by lines.
Bubbles: Represent the data transformations.
Lines: Represents the logic flow of data.
Data can trigger events and can be processed to useful information. System analysis recognizes
the central goal of data in organizations. This dataflow analysis tells a great deal about
organization objectives are accomplished.
Dataflow analysis studies the use of data in each activity. It documents this finding in
DFDs. Dataflow analysis give the activities of a system from the viewpoint of data where it
originates how they are used or hanged or where they go, including the stops along the way
from their destination. The components of dataflow strategy span both requirements
determination and systems design. The first part is called dataflow analysis.
As the name suggests, we didnt use the dataflow analysis tools exclusively for the analysis stage
but also in the designing phase with documentation.
NOTATIONS USED IN DATA FLOW DIAGRAMS
The logic dataflow diagrams can be drawn using only four simple notations i.e., special
symbols or icons and the annotation that associates them with a specific system. Since the
choice of notation we follow, does not affect impede or catalyze the system process; we used
three symbols from YOURDON notation and one from Gain and Sarson notation as
specified below.
Element References

symbols

Data Flow Process

Process
Data Store

25

Source or Sink

Description:
Process: describes how input data is converted to output

data

Data Store: Describes the repositories of data in a system

Data Flow: Describes the data flowing between process, Data

stores and

external entities.
Sources: An external entity causing the origin of data.
Sink: An external entity, which consumes the data.
Context Diagram
The top-level diagram is often called a context diagram. It contains a single process, but it
plays a very important role in studying the current system. The context diagram defines the
system that will be studied in the sense that it determines the boundaries. Anything that is not
inside the process identified in the context diagram will not be part of the system study. It
represents the entire software element as a single bubble with input and output data indicated by
incoming and outgoing arrows respectively.
Types of data flow diagrams
DFDs are two types
1. Physical DFDS
Structured analysis states that the current system should be first
understand correctly. The physical DFD is the model of the current system and is
used to ensure that the current system has been clearly understood. Physical DFDs
shows actual devices, departments, people etc., involved in the current system
2. Logical DFD
Logical DFDs are the model of the proposed system. They clearly should show the requirements on which the
new system should be built. Later during design activity this is taken as the basis for drawing the systems
structure charts.

26

.
.
DATA FLOW DIAGRAMS

Request
CONTEXT LEVEL
Request
CUSTOMER

Response

Drug Order
Management
System

Request
ADMINISTRATION

Response

27

Drug Order
Management
System

LEVEL 1 DATA FLOW DIAGRAM

Signup

Vendor
Informatio
n

Products
Informatio
n

User Id
Password

Drug Order
Management
System

User Id
Password
User Id
Password
Order
Details

28

User Id
Password
Direct
Orderin
g

LEVEL 2 DATA FLOW DIAGRAM

Validation
Process

Signup

YES

Error
Customer
ID
User
Information

Message

Display
Total
Informatio
n

Customer Table
User
Information

Registratio
n

Message

Process

29

USER

LEVEL 2 DFD FOR PRODUCTS INFORMATION

Discount table

Discount

User Id
Password

Product tables

Discount table

Product
Information

Product
Information

Ordering
Products

Order
Information

Qty, tax,
discount

Category
Name

Order
Processing

Amount
Payment Mode
Amount table
Payment
Process

USER

30

Er diagram

31

6.iii. FLOW CHARTS

FLOW CHART FOR LOGIN DAILS

START

ACCEPT USER_ID
AND PASSWORD

DATABASE

Is the input
information
valid?

YES
Display next choice based
on users choice

START

32

NO

FLOW CHART FOR ADDING NEW PRODUCT

START

Generate The
Product Code

DATABASE

Accept The Prod_Code,

Cat_Code, And Vendor_Code

NO

Valid
information?

YES
Submit The
Information

Accept Product Description

And Discount Sstructure

STOP

33

34

FLOW CHART FOR PRODUCT SELECTION

START

Accept Product Code, Name Etc

VALID
INFORMATION
?

Accept Product Code, Name Etc

Caalculate The Net Cost

Database

Place The Order

STOP

35

LowLevel Design
UseCase Diagrams

36

37

Sequence Diagrams

38

Communication Diagram

39

Class Diagram

40

Object Diagram

41

State Diagram

42

Activity Diagrams

Componet Diagram

Deployeement Diagram

43

Introduction
The Java web server is JavaSoft's own web Server. The Java web
server is just a part of a larger framework, intended to provide you
not just with a web server, but also with tools. To build customized
network servers for any Internet or Intranet client/server system.
Servlets are to a web server, how applets are to the browser.
About Servlets
Servlets provide a Java-based solution used to address the problems
currently associated with doing server-side programming, including
inextensible

scripting

solutions,

platform-specific

APIs,

and

incomplete interfaces.
Servlets are objects that conform to a specific interface that can be
plugged into a Java-based server. Servlets are to the server-side
what applets are to the client-side - object byte codes that can be
44

dynamically loaded off the net. They differ from applets in that they
are faceless objects (without graphics or a GUI component). They
serve as platform independent, dynamically loadable, plugable helper
byte code objects on the server side that can be used to dynamically
extend server-side functionality.
For example, an HTTP Servlets can be used to generate dynamic HTML
content. When you use Servlets to do dynamic content you get the following
advantages:

Theyre faster and cleaner than CGI scripts

They use a standard API (the Servlets API)

They provide all the advantages of Java (run on a variety

of servers without needing to be rewritten).

45

Attractiveness of Servlets
There are many features of Servlets that make them easy and attractive to use. These
include:

Easily configured using the GUI-based Administrator tool

Can be loaded and invoked from a local disk or remotely

across the network.

Can be linked together, or chained, so that one Servlets

can call another Servlets, or several Servlets in
sequence.

Can be called dynamically from within HTML pages,

using server-side include tags.

Are secure - even when downloading across the network,

the Servlets security model and Servlets sandbox protect
your system from unfriendly behavior.
Advantages of the Servlet API

One of the great advantages of the Servlet API is protocol

independence. It assumes nothing about:

The protocol being used to transmit on the net

How it is loaded

The server environment it will be running in

These qualities are important, because it allows the Servlet API to be

embedded in many different kinds of servers. There are other
advantages to the Servlet API as well. These include:

Its extensible - you can inherit all your functionality from

the base classes made available to you.

it's simple, small, and easy to use.

46

Features of Servlets

Servlets are persistent. Servlet are loaded only by the web server and
can maintain services between requests.

Servlets are fast. Since Servlets only need to be loaded

once, they offer much better performance over their CGI
counterparts.

Servlets are platform independent.

Servlets are extensible. Java is a robust, object-oriented

programming language, which easily can be extended to
suit your needs

Servlets are secure.

Servlets can be used with a variety of clients.

Loading Servlets
Servlets can be loaded from three places

From a directory that is on the CLASSPATH. The CLASSPATH of

the JavaWebServer includes service root/classes/ which is where the
system classes reside.
From the <SERVICE_ROOT /Servlets/ directory. This is *not* in the
servers class path. A class loader is used to create Servlets from this
directory. New Servlets can be added - existing Servlets can be
recompiled and the server will notice these changes.
From a remote location. For this a code base like http: // nine.eng /
classes / foo / is required in addition to the Servlets class name.
Refer to the administrator GUI docs on Servlet section to see how to
set this up.

47

Loading Remote Servlets

Remote Servlets can be loaded by:

1. Configuring the Administrator Tool to setup automatic loading of

remote Servlets
2. Setting up server side include tags in. shtml files
3. Defining a filter chain configuration
Invoking Servlets
A Servlet invoker is a Servlet that invokes the "service" method on a
named Servlet. If the Servlet is not loaded in the server, then the
invoker first loads the Servlet (either from local disk or from the
network) and the then invokes the "service" method. Also like
applets, local Servlets in the server can be identified by just the class
name. In other words, if a Servlet name is not absolute, it is treated
as local.
A client can invoke Servlets in the following ways:

The client can ask for a document that is served by the

Servlet.

The client (browser) can invoke the Servlet directly using

a URL, once it has been mapped using the Servlet
Aliases section of the administrator GUI.

The Servlet can be invoked through server side include

tags.

The Servlet can be invoked by placing it in the Servlets/

directory.

The Servlet can be invoked by using it in a filter chain.

48

JavaScript
JavaScript is a script-based programming language that was developed by Netscape
Communication Corporation. JavaScript was originally called Live Script and renamed
as JavaScript to indicate its relationship with Java. JavaScript supports the development
of both client and server components of Web-based applications. On the client side, it
can be used to write programs that are executed by a Web browser within the context of a
Web page. On the server side, it can be used to write Web server programs that can
process information submitted by a Web browser and then updates the browsers display
accordingly.

Even though JavaScript supports both client and server Web programming, we prefer
JavaScript at Client side programming since most of the browsers supports it. JavaScript
is almost as easy to learn as HTML, and JavaScript statements can be included in HTML
documents by enclosing the statements between a pair of scripting tags

<SCRIPTS>..</SCRIPT>.
<SCRIPT LANGUAGE = JavaScript>
JavaScript statements
</SCRIPT>

Here are a few things we can do with JavaScript:

Validate the contents of a form and make calculations.

Add scrolling or changing messages to the Browsers

status line.

Animate images or rotate images that change when we

move the mouse over them.

Detect the browser in use and display different content for

different browsers.

49

Detect installed plug-ins and notify the user if a plug-in is

required.

We can do much more with JavaScript, including creating entire

application.
JavaScript Vs Java
JavaScript and Java are entirely different languages. A few of the
most glaring differences are:

Java applets are generally displayed in a box within the

web document; JavaScript can affect any part of the Web
document itself.

While JavaScript is best suited to simple applications and

adding interactive features to Web pages; Java can be
used for incredibly complex applications.

There are many other differences but the important thing to

remember is that

JavaScript and Java are separate languages.

They are both useful for different things; in fact they can be used
together to combine their advantages.
Advantages

JavaScript can be used for Sever-side and Client-side

scripting.

It is more flexible than VBScript.

JavaScript is the default scripting languages at Clientside since all the browsers supports it.

50

Hyper Text Markup Language

Hypertext Markup Language (HTML), the languages of the World
Wide Web (WWW), allows users to produces Web pages that include
text, graphics and pointer to other Web pages (Hyperlinks).
HTML is not a programming language but it is an application of ISO
Standard 8879, SGML (Standard Generalized Markup Language),
but specialized to hypertext and adapted to the Web. The idea
behind Hypertext is that instead of reading text in rigid linear
structure, we can easily jump from one point to another point. We
can navigate through the information based on our interest and
preference. A markup language is simply a series of elements, each
delimited with special characters that define how text or other items
enclosed within the elements should be displayed. Hyperlinks are
underlined or emphasized works that load to other documents or
some portions of the same document.
HTML can be used to display any type of document on the host
computer, which can be geographically at a different location. It is a
versatile language and can be used on any platform or desktop.
HTML provides tags (special codes) to make the document look
attractive. HTML tags are not case-sensitive. Using graphics, fonts,
different sizes, color, etc., can enhance the presentation of the
document. Anything that is not a tag is part of the document itself.
Basic HTML Tags:
<!--

-->

Specifies comments

<A>.</A>

Creates hypertext links

<B>.</B>

Formats text as bold

<BIG>.</BIG>

Formats text in large font.

51

<BODY></BODY>

Contains all tags and text in the HTML

document

<CENTER>...</CENTER>

Creates text

<DD></DD>

Definition of a term

<DL>...</DL>

Creates definition list

<FONT></FONT>

Formats text with a particular font

<FORM>...</FORM>

Encloses a fill-out form

<FRAME>...</FRAME>

Defines a particular frame in a set of

frames

<H#></H#>

Creates headings of different levels

<HEAD>...</HEAD>

Contains tags that specify information

about a document

<HR>...</HR>

Creates a horizontal rule

<HTML></HTML>

Contains all other HTML tags

<META>...</META>

Provides

meta-information

about

document
<SCRIPT></SCRIPT>

Contains client-side or server-side script

<TABLE></TABLE>

Creates a table

<TD></TD>

Indicates table data in a table

<TR></TR>

Designates a table row

<TH></TH>

Creates a heading in a table

Advantages

A HTML document is small and hence easy to send over

the net. It is small because it does not include formatted
information.

HTML is platform independent.

HTML tags are not case-sensitive.

52

Java Database Connectivity

What Is JDBC?
JDBC is a Java API for executing SQL statements. (As a point of
interest, JDBC is a trademarked name and is not an acronym;
nevertheless, JDBC is often thought of as standing for Java
Database Connectivity. It consists of a set of classes and interfaces
written in the Java programming language. JDBC provides a
standard API for tool/database developers and makes it possible to
write database applications using a pure Java API.
Using JDBC, it is easy to send SQL statements to virtually any
relational database. One can write a single program using the JDBC
API, and the program will be able to send SQL statements to the
appropriate database. The combinations of Java and JDBC lets a
programmer write it once and run it anywhere.
What Does JDBC Do?
Simply put, JDBC makes it possible to do three things:

Establish a connection with a database

Send SQL statements

Process the results.

JDBC versus ODBC and other APIs

At this point, Microsoft's ODBC (Open Database Connectivity) API is
that probably the most widely used programming interface for
accessing relational databases. It offers the ability to connect to
almost all databases on almost all platforms.
So why not just use ODBC from Java? The answer is that you can use ODBC from Java,
but this is best done with the help of JDBC in the form of the JDBC-ODBC Bridge,
which we will cover shortly. The question now becomes "Why do you need JDBC?"
There are several answers to this question:

53

1. ODBC is not appropriate for direct use from Java because it

uses a C interface. Calls from Java to native C code have a
number

of

drawbacks

in

the

security,

implementation,

robustness, and automatic portability of applications.

2. A literal translation of the ODBC C API into a Java API would
not be desirable. For example, Java has no pointers, and
ODBC makes copious use of them, including the notoriously
error-prone generic pointer "void *". You can think of JDBC as
ODBC translated into an object-oriented interface that is
natural for Java programmers.
3. ODBC is hard to learn. It mixes simple and advanced features
together, and it has complex options even for simple queries.
JDBC, on the other hand, was designed to keep simple things
simple while allowing more advanced capabilities where
required.
4. A Java API like JDBC is needed in order to enable a "pure
Java" solution. When ODBC is used, the ODBC driver manager
and drivers must be manually installed on every client machine.
When the JDBC driver is written completely in Java, however,
JDBC code is automatically installable, portable, and secure on
all Java platforms from network computers to mainframes.
Two-tier and Three-tier Models
The JDBC API supports both two-tier and three-tier
models for database access.

54

In the two-tier model, a Java applet or application talks directly to the

database. This requires a JDBC driver that can communicate with
the particular database management system being accessed. A
user's SQL statements are delivered to the database, and the results
of those statements are sent back to the user. The database may be
located on another machine to which the user is connected via a
network. This is referred to as a client/server configuration, with the
user's machine as the client, and the machine housing the database
as the server. The network can be an Intranet, which, for example,
JAVA
Application
JDBC

Client machine
DBMS-proprietary protocol

DBMS

Database server

connects employees within a corporation, or it can be the Internet.

55

In the three-tier model, commands are sent to a "middle tier" of

services, which then send SQL statements to the database. The
database processes the SQL statements and sends the results back
Java applet or
Html browser

Application
Server (Java)
JDBC

Client machine (GUI)

HTTP, RMI, or CORBA
calls
DBMS-proprietary
Server
machine (business
protocol
Logic)
Database server

DBMS

to the middle tier, which then sends them to the user. MIS directors
find the three-tier model very attractive because the middle tier
makes it possible to maintain control over access and the kinds of
updates that can be made to corporate data. Another advantage is
that when there is a middle tier, the user can employ an easy-to-use
higher-level API which is translated by the middle tier into the
appropriate low-level calls. Finally, in many cases the three-tier
architecture can provide performance advantages.
Until now the middle tier has typically been written in
languages such as C or C++, which offer fast performance.
However, with the introduction of optimizing compilers that
translate Java byte code into efficient machine-specific code, it is
becoming practical to implement the middle tier in Java. This is a
big plus, making it possible to take advantage of Java's
robustness, multithreading, and security features. JDBC is
important to allow database access from a Java middle tier.

56

JDBC Driver Types

The JDBC drivers that we are aware of at this time fit into
one of four categories:

JDBC-ODBC bridge plus ODBC driver

Native-API partly-Java driver

JDBC-Net pure Java driver

Native-protocol pure Java driver

JDBC-ODBC Bridge
If possible, use a Pure Java JDBC driver instead of the
Bridge and an ODBC driver. This completely eliminates the client
configuration required by ODBC. It also eliminates the potential
that the Java VM could be corrupted by an error in the native
code brought in by the Bridge (that is, the Bridge native library,
the ODBC driver manager library, the ODBC driver library, and
the database client library).
What Is the JDBC- ODBC Bridge?
The JDBC-ODBC Bridge is a JDBC driver, which
implements JDBC operations by translating them into ODBC
operations. To ODBC it appears as a normal application
program. The Bridge implements JDBC for any database for
which an ODBC driver is available. The Bridge is implemented as
the
Sun.jdbc.odbc Java package and contains a native library
used to access ODBC. The Bridge is a joint development of
Intersolv and JavaSoft.
57

Java Server Pages (JSP)

Java server Pages is a simple, yet powerful technology for
creating and maintaining dynamic-content web pages. Based on
the Java programming language, Java Server Pages offers proven
portability, open standards, and a mature re-usable component
model .The Java Server Pages architecture enables the separation
of content generation from content presentation. This separation
not eases maintenance headaches; it also allows web team
members to focus on their areas of expertise. Now, web page
designer can concentrate on layout, and web application
designers on programming, with minimal concern about
impacting each others work.

Features of JSP
Portability
Java Server Pages files can be run on any web server or
web-enabled application server that provides support for them.
Dubbed the JSP engine, this support involves recognition,
translation, and management of the Java Server Page lifecycle
and its interaction components.
Components
It was mentioned earlier that the Java Server Pages architecture can
include reusable Java components. The architecture also allows for
58

the embedding of a scripting language directly into the Java Server

Pages file. The components current supported include Java Beans,
and Servlets.
Processing

A Java Server Pages file is essentially an HTML document with JSP

scripting or tags. The Java Server Pages file has a JSP extension to
the server as a Java Server Pages file. Before the page is served,
the Java Server Pages syntax is parsed and processed into a Servlet
on the server side. The Servlet that is generated outputs real content
in straight HTML for responding to the client.
Access Models:
A Java Server Pages file may be accessed in at least two different
ways. A clients request comes directly into a Java Server Page. In
this scenario, suppose the page accesses reusable Java Bean
components that perform particular well-defined computations like
accessing a database. The result of the Beans computations, called
result sets is stored within the Bean as properties. The page uses
such Beans to generate dynamic content and present it back to the
client.
In both of the above cases, the page could also contain any valid
Java code. Java Server Pages architecture encourages separation of
content from presentation.
Steps in the execution of a JSP Application:

59

1. The client sends a request to the web server for a JSP file by
giving the name of the JSP file within the form tag of a HTML
page.
2. This request is transferred to the JavaWebServer. At the server
side JavaWebServer receives the request and if it is a request
for a JSP file server gives this request to the JSP engine.
3. JSP engine is program which can understands the tags of the
jsp and then it converts those tags into a Servlet program and it
is stored at the server side. This Servlet is loaded in the
memory and then it is executed and the result is given back to
the JavaWebServer and then it is transferred back to the result
is given back to the JavaWebServer and then it is transferred
back to the client.
JDBC connectivity
The JDBC provides database-independent connectivity between the J2EE platform and a
wide range of tabular data sources. JDBC technology allows an Application Component
Provider to:
Perform connection and authentication to a database server

Manager transactions

Move SQL statements to a database engine for preprocessing and execution

Execute stored procedures

Inspect and modify the results from Select statements

60

Purpose
The generated application is the first version upon the system. The overall
system is planned to be in the formal of distributed architecture with homogeneous
database platform. The major objective of the overall system is to keep the
following components intact.
System consistency
System integrity
Overall security of data
Data reliability and Accuracy
User friendly name both at administratoristration and user levels
Considering the fact of generality and clarity
To cross check that the system overcomes the hurdles of the version specific
standards.

61

CODING

62

Program Design Language

The program design language is also called as structured

English or pseudopodia. PDL is a generic reference for a
design language PDL looks like a modern language. The
difference between PDL and real programming language lies in
the narrative text embedded directly within PDL statements.
The characteristics required by a design language are:
1) A fixed system of keywords that provide for all structured
constructs date declaration and modularity characteristics.
2) A free syntax of natural language that describes processing
features.
3) Date declaration facilities that should include both simple and
complex data structures.
4) Subprogram definition and calling techniques that support various
nodes of interface description.
PDL syntax should include constructs for subprogram definition,
interface description date declaration techniques for structuring,
conditions constructs, repetition constructs and I/O constructs.
PDL can be extended to include keywords for multitasking
and/or concurrent processing interrupt handling, interposes
synchronization the application design for which PDL is to be
used should dictate the final form for the design language.

63

<body bgcolor=ivory scroll=no>

<LINK HREF="switch.xsl" rel="stylesheet">
<script>
document.oncontextmenu=new Function("return false");
document.onselectstart=new Function("return false");
var persistmenu="yes"
var persisttype="sitewide"
if (document.getElementById){
document.write('<style type="text/css">\n')
document.write('.submenu{display: none;}\n')
document.write('</style>\n')
}
function getLoad() {
var anc=document.getElementsByTagName("A");
for(an=0;an<anc.length;an++) {
anc[an].onmouseover=function() {status=this.innerHTML;return true;}
anc[an].onmouseout=function() {status="Done";return true;}
anc[an].onfocus=function() {status=this.innerHTML;this.blur();return true;}
anc[an].oncontextmenu=function() {
var cfm=confirm("Would u like to open this link in New
Window");
if(cfm) open(this.href);
else return;
}
}
}
function SwitchMenu(obj){
if(document.getElementById){
var el = document.getElementById(obj);
var ar =
document.getElementById("masterdiv").getElementsByTagName("span");
if(el.style.display != "block"){
for (var i=0; i<ar.length; i++){
if (ar[i].className=="submenu")
ar[i].style.display = "none";
}
el.style.display = "block";
}else{
el.style.display = "none";
}
}
}
function getReports(url) {
var mw=screen.availWidth-50;
var mh=screen.availHeight-50;
open(url,"reportss","scrollbars,width="+mw+",height="+mh+",left=20,top=20,maxi
mize=yes");
}
</script>
<br><br><br>
<div id="masterdiv">

64

<div class="menutitle"
onclick="SwitchMenu('sub1')">Administration</div>
<span class="submenu" id="sub1">
&nbsp;&nbsp;&nbsp;&nbsp;<font face=webdings
color=lightslategray>4</font> <a href="cust_admin.html" target="right">Go To
Customers Admin</a><br>
&nbsp;&nbsp;&nbsp;&nbsp;<font face=webdings
color=lightslategray>4</font> <a href="vendor_adm_screen.html"
target="right">Go To Vendors Admin </a><br>
&nbsp;&nbsp;&nbsp;&nbsp;<font face=webdings
color=lightslategray>4</font> <a href="cat_admin.html" target="right"> Go To
Category Admin </a><BR>
&nbsp;&nbsp;&nbsp;&nbsp;<font face=webdings
color=lightslategray>4</font> <a href="product_administration.html""
target="right"> Go To Products Admin </a><br>
&nbsp;&nbsp;&nbsp;&nbsp;<font face=webdings
color=lightslategray>4</font> <a href="discount_admin.html" target="right"> Go
To Discount Admin </a><br>
&nbsp;&nbsp;&nbsp;&nbsp;<font face=webdings
color=lightslategray>4</font> <a href="stock1.html" target="right">Go To Stock
Admin</a>
</span>
<br>
<div class="menutitle" onclick="SwitchMenu('sub3')">Reports
Terminal</div>
<span class="submenu" id="sub3">
&nbsp;&nbsp;&nbsp;&nbsp;<font face=webdings
color=lightslategray>4</font> <a href="javascript:getReports('report?
table=PHARMA_PRODUCT')">Pharna Prod Details</a><br>
&nbsp;&nbsp;&nbsp;&nbsp;<font face=webdings
color=lightslategray>4</font> <a href="javascript:getReports('report?
table=PHARMA_ORDER')">Pharna Order Details</a><br>
&nbsp;&nbsp;&nbsp;&nbsp;<font face=webdings
color=lightslategray>4</font> <a href="javascript:getReports('report?
table=PHARMA_CATEGORY')">Pharna Cate Details</a><br>
&nbsp;&nbsp;&nbsp;&nbsp;<font face=webdings
color=lightslategray>4</font> <a href="javascript:getReports('report?
table=PHARMA_DISCOUNT')">Pharna Dis Details</a><BR>
&nbsp;&nbsp;&nbsp;&nbsp;<font face=webdings
color=lightslategray>4</font> <a href="javascript:getReports('report?
table=PHARMA_VENDOR')">Pharna Ven Details</a><br>
&nbsp;&nbsp;&nbsp;&nbsp;<font face=webdings
color=lightslategray>4</font> <a href="javascript:getReports('report?
table=PHARMA_REGISTRATION')">Pharna Regi Details</a>
</span>
<br>
&nbsp;&nbsp;&nbsp;&nbsp;<font face=webdings
color=lightslategray>4</font> <a href="home_page.html"
target="_top">Logout</a>
</div><script>getLoad()</script>

65

TESTING

66

Testing
Testing is the process of detecting errors. Testing performs a very
critical role for quality assurance and for ensuring the reliability of
software. The results of testing are used later on during maintenance
also.
Psychology of Testing
The aim of testing is often to demonstrate that a program works by
showing that it has no errors. The basic purpose of testing phase is
to detect the errors that may be present in the program. Hence one
should not start testing with the intent of showing that a program
works, but the intent should be to show that a program doesnt work.
Testing is the process of executing a program with the intent of
finding errors.
Testing Objectives
The main objective of testing is to uncover a host of errors,
systematically and with minimum effort and time. Stating
formally, we can say,
Testing is a process of executing a program with the intent
of finding an error.
A successful test is one that uncovers an as yet
undiscovered error.
A good test case is one that has a high probability of finding
error, if it exists.
The tests are inadequate to detect possibly present errors.
The software more or less confirms to the quality and
reliable standards.
Levels of Testing
67

In order to uncover the errors present in different phases

we have the concept of levels of testing. The basic levels of testing
are as shown below
Acceptance
Testing

Client Needs

System Testing
Requirements
Design
Code

Integration Testing

Unit Testing

System Testing
The philosophy behind testing is to find errors. Test cases are devised with this in mind.
A strategy employed for system testing is code testing.

Code Testing:
This strategy examines the logic of the program. To follow this method we developed
some test data that resulted in executing every instruction in the program and module i.e.
every path is tested. Systems are not designed as entire nor are they tested as single
systems. To ensure that the coding is perfect two types of testing is performed or for that
matter is performed or that matter is performed or for that matter is performed on all
systems.

68

Types Of Testing
Unit Testing
Link Testing
Unit Testing
Unit testing focuses verification effort on the smallest unit of software i.e. the
module. Using the detailed design and the process specifications testing is done to
uncover errors within the boundary of the module. All modules must be successful
in the unit test before the start of the integration testing begins.
In this project each service can be thought of a module. There are so many
modules like Login, HWAdministrator, MasterAdministrator, Normal User, and
PManager. Giving different sets of inputs has tested each module. When developing
the module as well as finishing the development so that each module works without
any error. The inputs are validated when accepting from the user.

In this application developer tests the programs up as system. Software

units in a system are the modules and routines that are assembled and
integrated to form a specific function. Unit testing is first done on
modules, independent of one another to locate errors. This enables to
detect errors. Through this errors resulting from interaction between
modules initially avoided.
Link Testing
Link testing does not test software but rather the integration of each
module in system. The primary concern is the compatibility of each
module. The Programmer tests where modules are designed with
different parameters, length, type etc.
Integration Testing
After the unit testing we have to perform integration testing. The goal
here is to see if modules can be integrated proprerly, the emphasis being
on testing interfaces between modules. This testing activity can be
considered as testing the design and hence the emphasis on testing
module interactions.
In this project integrating all the modules forms the main system. When
integrating all the modules I have checked whether the integration

69

effects working of any of the services by giving different combinations

of inputs with which the two services run perfectly before Integration.
System Testing
Here the entire software system is tested. The reference document for this
process is the requirements document, and the goal os to see if software meets its
requirements.
Here entire ATM has been tested against requirements of project and it is
checked whether all requirements of project have been satisfied or not.

Acceptance Testing
Acceptance Test is performed with realistic data of the client to demonstrate
that

the software is working satisfactorily. Testing here is focused on external

behavior of the system; the internal logic of program is not emphasized.

In this project Network Management Of Database System I have collected
some data and tested whether project is working correctly or not.
Test cases should be selected so that the largest number of attributes of an
equivalence class is exercised at once. The testing phase is an important part of
software development. It is the process of finding errors and missing operations and
also a complete verification to determine whether the objectives are met and the
user requirements are satisfied.

White Box Testing

This is a unit testing method where a unit will be taken at a time and
tested thoroughly at a statement level to find the maximum possible
errors. I tested step wise every piece of code, taking care that every
statement in the code is executed at least once. The white box
testing is also called Glass Box Testing.
I have generated a list of test cases, sample data. which is used to
check

all

possible combinations of execution paths through the

code at every module level.

70

Black Box Testing

This testing method considers a module as a single unit and checks
the unit at interface and communication with other modules rather
getting into details at statement level.
Here the module will be treated as a block box that will take some
input and generate output. Output for a given set of input
combinations are forwarded to other modules.
Criteria Satisfied by Test Cases
Test cases that reduced by a count that is greater than one, the
number of additional test cases that much be designed to achieve
reasonable testing.
Test cases that tell us something about the presence or absence of
classes of errors, rather than an error associated only with the
specific test at hand.
SCREEN SHORTS

71

72

73

74

75

76

77

78

79

80

81

82

83

84

85

86

87

88

89

90

91

92

93

94

95

CONCLISION
This Project Drug Order Management System is a solution to Aurobindo
Pharma to take the orders from its distributors who are geographically
distributed. This new system not only takes the orders from distributors for
Aurobindo Pharma but it also facilities.The administration, as well as the
report generation for the firm.

96

It can be accessed from any part of the world, as opposed to stand alone or
manual system, and provides information at any time, anywhere.
Even though it is a web-based application it will keep the details of its
clients private and no body is allowed to tinker with the details.
No need to own any computer for this specific ordering of products, it just
requires user to register with the system.It provides easy to use and user
friendly interface for the user.
The organization people can do administration over the products, vendor,
customer (only deletion in case of dealer ship cancellation) etc.
FUTURE SCOPE OF APPLICATION
The current system is susceptible to handle the situation that, even the
organization grows and establishes various branches at various places in the
world.
The Database maintained here grows, as time passes by thus it has to be
cleaned up in frequent intervals so as to save memory. There are no special
provisions designed in the system. If the user wants an option of backing of
data in frequent intervals, it could be added to the present system.
The information of the Employee's working in the organization, like
payroll (remuneration's), details of their work, are not incorporated in the
system as it does not fall under the scope of this project. If Payroll
management is to be included it can be easily coupled with the present
modules.
The use of the system should be trained otherwise he would struggle to
operate it and would not be able to know all the features in it.
Frequently enough the system should be reviewed for updating as we know
that maintenance is rather difficult than developing a system so there should
be proper feedback about the usefulness of the system, otherwise the basic
purpose of automation would not achieved.

97

BIBLIOGRAPHY
The Knowledge required for developing this project is extracted from
the following books.
MASTERING VISUAL BASIC 6
Peter Norton
ORACLE 8 MASTERING CLIENT-SERVER CONCEPTS
Steven M. Bobrowski
SYSTEM ANALYSIS AND DESIGN
James A. Senn
VISUAL BASIC 5 DATABASE
Dennis Kennedy
Joe Garrick
Bill Harper
Jason T. Roff
SOFTWARE ENGINEERING
Roger S. Pressman
-

98