Ambulance service provider.doc

7/26/2019 Ambulance service provider.doc

1/97

Project Report

On

XXXXXXXXX

Project work submitted in partial fulfillmentOf the requirement for the award of the degree

B.Tech

By

XXXXXXXXX

( Regd.No: )

!nder the "uidance of

Mr. XXXXXXXX(Project Coordinator, XXXXXXXXXXX)

XXXXXXX UNIVERSITY


2/97

CERTIFICATE

This is to certify that this project entitled #$is a bonafide work carried

out by bearing %all &icket No: '()'*'+,in and submitted to

!ni-ersity in partial fulfillment of the requirements for the award of Bachelor of

&echnology.

Project "uide /ternal /aminer Principal


3/97


4/97

ACKNOWE!"MENT

Task successful! makes everyone happy" But the happiness will be

gold without glitter if we didn#t state the persons who have supported us to make

it a success"

$uccess will be crowned to people who made it a reality but the

people whose constant guidance and encouragement made it possible will be

crowned first on the eve of success"

This acknowledgement transcends the reality of formality when we

would like to e%press deep gratitude and respect to all those people behind the

screen who guided, inspired and helped me for the completion of our project

work"

& consider myself lucky enough to get such a good project" This

project would add as an asset to my academic profile"

& would like to e%press my thankfulness to my project guide, 0r

for his constant motivation and valuable help through the project work,

and & e%press my gratitude to 0r. , 'irector of XXXXXXXXX

(yderabad, for his constant supervision, guidance and co)operation through out

the project"

I also extend my thanks to my Team Members for their co-

operation during my course.

inally I !ould like to thanks my friends for their co-

operation to complete this pro"ect.

#######


5/97


6/97

$aste %rgani&ation pro'le here


7/97


8/97

CONTENTS

#. INTRO!UCTION

IT%*+,TI% T% $%,T$+$%/ % T0 $%,T#I/TI1 /2/TM 3 IT/ *I/4*54T41/$%$%/* /2/TM 3 IT/ 4*54T41/

$. SYSTEM ANAYSIS

6.7. /T+*2 % T0 /2/TM6.6. I$+T 3 %+T$+T $/T4TI%6.8. $%,// M%*9/ +/* :IT0 +/TII,4TI%6.;. /2/TM 4,0IT,T+

%. FEASIBIITY STU!Y

8.7. T,0I,49 4/II9IT28.6. %$4TI%49 4/II9IT28.8. ,%%MI, 4/II9IT2

&. RE'UIREMENT SPECIFICATIONS

;.7. +,I%49 =+IMT/

;.6. $%M4, =+IMT/;.8. /%T:4 =+IMT/;.;. 04*:4 =+IMT/

;.;.7. IT%*+,TI% T% 454;.;.6. /erlets?/$;.;.8. *,;.;.;. %racle;.;.@. 0TM9;.;.A. aa /cript

. SYSTEM !ESI"N

@.7 . IT%*+,TI%@.6 *4T4 9%: *I414M/@.8 +M9 *I414M/@.; - *I414M@.@ %M49IB4TI%@.A *4T4 *I,TI%42


9/97

. OUTPUT SCREENS

*. SYSTEM TESTIN"

C.7 IT%*+,TI% T% T/TI1C.6 T/TI1 /T4T1I/

+. SYSTEM SECURITY

D.7 IT%*+,TI%D.6 /,+IT2 I /%T:4

,. BIBIO"RAP-Y


10/97


11/97

#.#. INTRO!UCTION OB/ECTIVE

The objective of this application is to develop a system that automates and organizes the ambulance

service sector. The purpose is to maintain a well-defined interface to the offered services and

maintain a centralized database of entire information.

#.$. PURPOSE OF T-E PRO/ECT

The purpose of the project is to make the ambulance services available to everybody by maintaining

the data in the database.

#.%. EXISTIN" SYSTEM !ISA!VANTA"ESThe present system is not efficient and effective as the entire data is maintained across various files and

systems. It is difficult to access the data and perform the necessary operations. The system cannot

respond properly to emergency situations.

#.&. PROPOSE! SYSTEM ITS !ISA!VANTA"ES

The proposed system organizes the data effectively. It provides mechanisms to communicate

information efficiently and accurately. It provides information regarding ambulance services offered by

different hospitals. It is easy to generate reports. Users can access the information quickly.


12/97

$.# STU!Y OF T-E SYSTEM

To provide fleibility to the users! the interfaces have been developed that are accessible through a

browser. The "UI#$ at the top level have been categorized as

%. &dministrative user interface

'. The operational or generic user interface

The (administrative user interface# concentrates on the consistent information that is practically! part of

the organizational activities and which needs proper authentication for the data collection. These

interfaces help the administrators with all the transactional states like )ata insertion! )ata deletion and

)ate updation along with the etensive data search capabilities.


13/97

The (operational or generic user interface# helps the end users of the system in transactions through the

eisting data and required services. The operational user interface also helps the ordinary users in

managing their own information in a customized manner as per the included fleibilities

$.$ INPUT OUTPOUT REPRESENTETION

Input design is a part of overall system design. The main objective during the input design is as given

below*

To produce a cost-effective method of input.

To achieve the highest possible level of accuracy.

To ensure that the input is acceptable and understood by the user.

INPUT STAGES:

The main input stages can be listed as below*

)ata recording

)ata transcription

)ata conversion

)ata verification

)ata control

)ata transmission

)ata validation

)ata correction

INPUT TYPES:

It is necessary to determine the various types of inputs. Inputs can be categorized as follows*

+ternal inputs! which are prime inputs for the system.

Internal inputs! which are user communications with the system.

,perational! which are computer department#s communications to the system

Interactive! which are inputs entered during a dialogue.

INPUT MEDIA:


14/97

&t this stage choice has to be made about the input media. To conclude about the input media

consideration has to be given to

Type of input

/leibility of format

$peed

&ccuracy

0erification methods

1ejection rates

+ase of correction

$torage and handling requirements

$ecurity

+asy to use

2ortability

3eeping in view the above description of the input types and input media! it can be said that most of the

inputs are of the form of internal and interactive. &s

Input data is to be the directly keyed in by the user! the keyboard can be considered to be the most

suitable input device.

OUTPUT DESIGN:

In general are*

+ternal ,utputs whose destination is outside the organization.

Internal ,utputs whose destination is with in organization and they are the User#s main interface

with the computer. ,utputs from computer systems are required primarily to communicate the

results of processing to users. They are also used to provide a permanent copy of the results for

later consultation. The various types of outputs

,perational outputs whose use is purely with in the computer department.

Interface outputs! which involve the user in communicating directly with the system.

OUTPUT DEFINITION


15/97

The outputs should be defined in terms of the following points*

Type of the output

4ontent of the output

/ormat of the output

5ocation of the output

/requency of the output

0olume of the output

$equence of the output

It is not always desirable to print or display data as it is held on a computer. It should be decided as

which form of the output is the most suitable.

/or +ample

6ill decimal points need to be inserted

$hould leading zeros be suppressed"

OUTPUT MEDIA:

In the net stage it is to be decided that which medium is the most appropriate for the output. The main

considerations when deciding about the output media are*

The suitability for the device to the particular application.

The need for a hard copy.

The response time required.

The location of the users

The software and hardware available.

3eeping in view the above description the project is to have outputs mainly coming under the

category of internal outputs. The main outputs desired according to the requirement specification are*

The outputs were needed to be generated as a hard copy and as well as queries to be viewed on the

screen. 3eeping in view these outputs! the format for the output is taken from the outputs! which are

currently being obtained after manual processing. The standard printer is to be used as output media for

hard copies.


16/97

$.% PROCESS MO!E USE! WIT- /USTIFICATION

SDLC (Umbrella Model):

$)54 is nothing but $oftware )evelopment 5ife 4ycle. It is a standard which is used by software

industry to develop good software.

Stages in SDLC:

1equirement "athering

&nalysis

)esigning

4oding

Testing

7aintenance

Requirements "athering stage:

UmbrellaActivity

UmbrellaActivity

UmbrellaActivity

Feasibility StudyTEAM FORMATIONProject Specification

PREPARATION

Business Requireent!ocuentation

ANA"#SIS $!ESI%N

&O!E 'NIT TEST

!O&'MENT &ONTRO"

ASSESSME

TRAININ%

INTE%RATION$ S#STEMTESTIN%

!E"I(ER#)INSTA""ATION

A&&EPTAN&ETEST

Requireents%at*erin+


17/97

The requirements gathering process takes as its input the goals identified in the high-leve

requirements section of the project plan. +ach goal will be refined into a set of one or more

requirements. These requirements define the major functions of the intended application! define

operational data areas and reference data areas! and define the initial data entities. 7ajor functions

include critical processes to be managed! as well as mission critical inputs! outputs and reports. & user

class hierarchy is developed and associated with these major functions! data areas! and data entities.

+ach of these definitions is termed a 1equirement. 1equirements are identified by unique requirement

identifiers and! at minimum! contain a requirement title and

tetual description"

These requirements are fully described in the primary deliverables for this stage* the 1equirements

)ocument and the 1equirements Traceability 7atri 81T79. The requirements document contains

complete descriptions of each requirement! including diagrams and references to eternal documents as

necessary. :ote that detailed listings of database tables and fields are not included in the requirements

document.

The title of each requirement is also placed into the first version of the 1T7! along with the title of

each goal from the project plan. The purpose of the 1T7 is to show that the product components

developed during each stage of the software development lifecycle are formally connected to the

components developed in prior stages.


18/97

In the requirements stage! the 1T7 consists of a list of high-level requirements! or goals! by title!

with a listing of associated requirements for each goal! listed by requirement title. In this hierarchical

listing! the 1T7 shows that each requirement developed during this stage is formally linked to a specific

product goal. In this format! each requirement can be traced to a specific product goal! hence the term

requirements traceability.

The outputs of the requirements definition stage include the requirements document! the 1T7! and

an updated project plan.

/easibility study is all about identification of problems in a project.

:o. of staff required to handle a project is represented as Team /ormation! in this case only modules

are individual tasks will be assigned to employees who are working for that project.

2roject $pecifications are all about representing of various possible inputs submitting to the server

and corresponding outputs along with reports maintained by administrator

Analysis Stage:

The planning stage establishes a bird;s eye view of the intended software product! and uses this to

establish the basic project structure! evaluate feasibility and risks associated with the project! and

describe appropriate management and technical approaches"

The most critical section of the project plan is a listing of high-level product requirements! also referred

to as goals. &ll of the software product requirements to be developed during the requirements definition


19/97

stage flow from one or more of these goals. The minimum information for each goal consists of a title

and tetual description! although additional information and references to eternal documents may be

included. The outputs of the project planning stage are the configuration management plan! the quality

assurance plan! and the project plan and schedule! with a detailed listing of scheduled activities for the

upcoming 1equirements stage! and high level estimates of effort for the out stages.

1esigning 2tage:

The design stage takes as its initial input the requirements identified in the approved requirements

document. /or each requirement! a set of one or more design elements will be produced as a result of

interviews! workshops! and


20/97

The development stage takes as its primary input the design elements described in the approved

design document. /or each design element! a set of one or more software artifacts will be produced

$oftware artifacts include but are not limited to menus! dialogs! data management forms! data reporting

formats! and specialized procedures and functions. &ppropriate test cases will be developed for each set

of functionally related software artifacts! and an online help system will be developed to guide users in

their interactions with the software.

The 1T7 will be updated to show that each developed artifact is linked to a specific design

element! and that each developed artifact has one or more corresponding test case items. &t this point

the 1T7 is in its final configuration. The outputs of the development stage include a fully functional set

of software that satisfies the requirements and design elements previously documented! an online help

system that describes the operation of the software! an implementation map that identifies the primary

code entry points for all major system functions! a test plan that describes the test cases to be used to

validate the correctness and completeness of the software! an updated 1T7! and an updated project plan

6ntegration 7 &est 2tage:

)uring the integration and test stage! the software artifacts! online help! and test data are migrated

from the development environment to a separate test environment. &t this point! all test cases are run to

verify the correctness and completeness of the software. $uccessful eecution of the test suite confirms a


21/97

robust and complete migration capability. )uring this stage! reference data is finalized for production

use and production users are identified and linked to their appropriate roles. The final reference data 8or

links to reference data source files9 and production user list are compiled into the 2roduction Initiation

2lan.

The outputs of the integration and test stage include an integrated set of software! an online help

system! an implementation map! a production initiation plan that describes reference data and production

users! an acceptance plan which contains the final suite of test cases! and an updated project plan.

Installation & Acceptance Test:

)uring the installation and acceptance stage! the software artifacts! online help! and initial

production data are loaded onto the production server. &t this point! all test cases are run to verify the

correctness and completeness of the software. $uccessful eecution of the test suite is a prerequisite to

acceptance of the software by the customer.


22/97

&fter customer personnel have verified that the initial production data load is correct and the test

suite has been eecuted with satisfactory results! the customer formally accepts the delivery of the

software.

The primary outputs of the installation and acceptance stage include a production application! a

completed acceptance test suite! and a memorandum of customer acceptance of the software. /inally! the

2)1 enters the last of the actual labor data into the project schedule and locks the project as a permanent

project record. &t this point the 2)1 =locks= the project by archiving all software items! the

implementation map! the source code! and the documentation for future reference.

0aintenance:

,uter rectangle represents maintenance of a project! 7aintenance team will start with requirement

study! understanding of documentation later employees will be assigned work and they will under go

training on that particular assigned category.

/or this life cycle there is no end! it will be continued so on like an umbrella 8no ending point to

umbrella sticks9.

$.& SYSTEM ARC-ITECTURE


23/97

Arcitect!re "lo#:

>elow architecture diagram represents mainly flow of requests from users to database through servers.

In this scenario overall system is designed in three tires separately using three layers called presentation

layer! business logic layer and data link layer. This project was developed using ?-tire architecture.

SERVER

User

Data

Base

Request Response


24/97

U$L Pattern:

U15 pattern represents how the requests are flowing through one layer to another layer and howthe responses are getting by other layers to presentation layer through server in architecture diagram.

Presentatio

n Layer

SERVLETSAT THE

SERVERSIDE

URLRequestsentthrough thebroser

Responsesent !ro"the ser#let

DATABASE

Veri!ying orup$ating the

$atabasethrough astate"ent

Reply !ro"the $atabasea%%or$ing to

thestate"ent


25/97


26/97

Fe0123242t5 St6758

2reliminary investigation eamines project feasibility! the likelihood the system will be useful to the

organization. The main objective of the feasibility study is to test the Technical! ,perational and

+conomical feasibility for adding new modules and debugging old running system. &ll systems are

feasible if they are given unlimited resources and infinite time. There are aspects in the feasibility study

portion of the preliminary investigation*

Technical /easibility

,peration /easibility

+conomical /easibility

%.# TEC-NICA FEASIBIITY

The technical issue usually raised during the feasibility stage of the investigation includes the following*

)oes the necessary technology eist to do what is suggested

)o the proposed equipments have the technical capacity to hold the data required to use the new

system

6ill the proposed system provide adequate response to inquiries! regardless of the number or

location of users

4an the system be upgraded if developed

&re there technical guarantees of accuracy! reliability! ease of access and data security

%.$ OPERATIONAFEASIBIITY

OPE$ATIONAL FEASI%ILITY

User-friendly

4ustomer will use the forms for their various transactions i.e. for adding new routes! viewing the

routes details. &lso the 4ustomer wants the reports to view the various transactions based on the

constraints. Theses forms and reports are generated as user-friendly to the 4lient.


27/97

Reliability

The package wills pick-up current transactions on line. 1egarding the old transactions! User will

enter them in to the system.

Security

The web server and database server should be protected from hacking! virus etc

Portability

The application will be developed using standard open source software 8+cept ,racle9 like @ava!

tomcat web server! Internet +plorer >rowser etc these software will work both on 6indows and

5inu o


28/97

,pen source software like T,74&T! @&0&! 7ysql and 5inu is used to minimize the cost for the

4ustomer.

&.# FUNCTIONA RE'UIREMENTS SPECIFICATION

This application mainly consist three modules

' A()inistrator Mo(!le

*' E)plo+ee Mo(!le

,' $eport Mo(!le

- A()inistration Mo(!le:

&dministrator manages the entire application. &dministrator can add! delete! edit and view the employee

details. &dministrator also manages the doctors details along with other attendants. &dministrator keeps

track of ambulances available and their current status.

2.E)plo+ee Mo(!le:

This module allows one to generate reports based on different criteria such as ambulance details!

employee details! patient details! services offered and so on.

,- $eport Mo(!le:

This module allows employees to register and manage patient details. 6hen a request is made! an

employee immediately dispatches an ambulance with available doctor and other attendants. +mployee

keeps track of patient status and in case of emergency consults a hospital for admitting the patient.


29/97

&.$ PERFORMANCERE'UIREMENTS

2erformance is measured in terms of the output provided by the application. 1equirement specification

plays an important part in the analysis of a system. ,nly when the requirement specifications are

properly given! it is possible to design a system! which will fit into required environment. It rests largely

with the users of the eisting system to give the requirement specifications because they are the people

who finally use the system. This is because the requirements have to be known during the initial stages

so that the system can be designed according to those requirements. It is very difficult to change the

system once it has been designed and on the other hand designing a system! which does not cater to the

requirements of the user! is of no use.

The requirement specification for any system can be broadly stated as given below*

The system should be able to interface with the eisting system

The system should be accurate

The system should be better than the eisting system

The eisting system is completely dependent on the user to perform all the duties.

&.% SOFTWARE RE'UIREMENTSE

Technology * @ava and @'++

6eb Technologies * AT75! 4$$! @ava$cript

)atabase * ,racle%Bg

@)3 0ersion * @)3%.C

$erver * TomcatC.C

&.&-AR!WARE RE'UIREMENTSE

2rocessor** 2entium-III 8or9 Aigher

1am** DE7> 8or9 Aigher 4ache** C%'7>

Aard disk** %B">

A((itional Tools:

AT75 )esigning * )ream weaver Tool


30/97

)evelopment Tool kit * 7y +clipse

&.&.#. INTRO!UCTION TO /AVA

About Java*

Initially the language was called as FoakG but it was renamed as FjavaG in %HHC.The primary

motivation of this language was the need for a platform-independent8i.e. architecture

neutral9language that could be used to create software to be embedded in various consumer

electronic devices.

@ava is a programmer#s language

@ava is cohesive and consistent

+cept for those constraint imposed by the Internet environment. @ava gives the

programmer! full control

/inally @ava is to Internet 2rogramming where c was to $ystem 2rogramming.

Importance of Java to the Internet

@ava has had a profound effect on the Internet. This is because java epands the Universe of objects

that can move about freely in 4yberspace. In a network! two categories of objects are transmitted

between the server and the personal computer. They are passive information and )ynamic active

programs. in the areas of $ecurity and probability. >ut @ava addresses these concerns and by doing

so! has opened the door to an eciting new form of program called the &pplet.

Applications and applets.

&n application is a program that runs on our 4omputer under the operating system of that computer.

It is more or less like one creating using 4 or 4 .@ava#s ability to create &pplets makes it

important. &n &pplet I san application! designed to be transmitted over the Internet and eecuted by


31/97

a @ava-compatible web browser. &n applet I actually a tiny @ava program! dynamically downloaded

across the network! just like an image. >ut the difference is! it is an intelligent program! not just a

media file. It can be react to the user input and dynamically change.


32/97

$olaris or &pple 7acintosh running system and all could receive code from any computer through

internet and run the &pplets.

2imple*

@ava was designed to be easy for the 2rofessional programmer to learn and to use effectively. If youare an eperienced 4 2rogrammer. 5earning @ava will oriented features of 4 . 7ost of the

confusing concepts from 4 are either left out of @ava or implemented in a cleaner! more

approachable manner. In @ava there are a small number of clearly defined ways to accomplish a

given task.

Object oriented

+ava was not designed to be source)code compatible with any other language" This

allowed the +ava team the freedom to design with a blank state" ne outcome of this was a

clean usable, pragmatic approach to objects" The object model in +ava is simple and easy

to e%tend, while simple types, such as integers, are kept as high)performance non)objects"

Robust

The multi)platform environment of the web places e%traordinary demands on a program,

because the program must e%ecute reliably in a variety of systems" The ability to create

robust programs" -as given a high priority in the design of +ava" +ava is strictly typed

language. it checks your code at compile time and runtime"

+ava virtually eliminates the problems of memory management and deal location, whichis completely automatic" &n a well)written +ava program, all run)time errors can and shouldbe managed by your program"

Ser94et1:/SP

&/T0'1CT&/

2 $ervlet &s a generic server e%tension" a +ava class that can be loaded

'ynamically to e%pand the functionality of a server"$ervlets are commonly used with web

servers" -here they can take the place C3& scripts"


33/97

2 servlet is similar to proprietary server e%tension, e%cept that it runs inside a +ava 4irtua

5achine 6+457 on the server, so it is safe and portable

$ervlets operate solely within the domain of the server"

1nlike C3& and 8ast C3&, which use multiple processes to handle separate program or

separate requests, separate threads within web server process handle all servlets" This

means that servlets are all efficient and scalable"

$ervlets are portable. both across operating systems and also across web servers" +ava

$ervlets offer the best possible platform for web application development"

$ervlets are used as replacement for C3& scripts on a web server, they can e%tend any

sort of server such as a mail server that allows servelts t e%tend its functionality perhaps by

performing a virus scan on all attached documents or handling mail filtering tasks"

$ervlets provide a +ava)based solution used to address the problems currently associated

with doing server)side programming including ine%tensible scripting solutions platform)

specific 2Ps and incomplete interface"

$ervlets are objects that conform to a specific interface that can be plugged into a +ava)

based server"$ervlets are to the server)side what applets are to the server)side what

applets are to the client)side)object byte codes that can be dynamically loaded off the net"

They differ form applets in than they are faceless objects6with out graphics or a 31

component7"They serve as platform independent, dynamically loadable,plugable helper

byte code objects on the server side that can be used to dynamically e%tend server)side

functionality"

8or e%ample an (TTP servlet can be used to generate dynamic (T59 content when

you use servlets to do dynamic content you get the following advantages*


34/97

They#re faster and cleaner then C3& scripts

They use a standard 2P&6 the servlet 2P&7

They provide all the advantages of +ava 6run on a variety of servers without needing

to be rewritten7

A t t r 0 c t 2 9 e ; e 1 1 o < S e r 9 4 e t 1:

They are many features of servlets that make them easy and attractive to tuse these

include*

:asily configure using the 31&)based 2dmin tool;

Can be 9oaded and &nvoked from a local disk or remotely across the network"

Can be linked together or chained, so that on servlet can call another servlet, orseveral servlets in sequence"

Can be called dynamically from with in (T59, pages using server)side include)

tags"

2re secure)even when downloading across the network, the servlet security

model and servlet and bo% protect your system from unfriendly behavior",

9d-antages of the ser-let 9P6

ne of the great advantages of the servlet 2P& is protocol independent" &t assumesnothing about*

The protocol being used to transmit on the net

(ow it is loaded

The server environment it will be running in

These quantities are important, because it allows the $ervlet 2P& to be

embedded in many different kinds of servers"There are other advantages to the

servelt 2P& as well These include*

&t#s e%tensible)you can inherit all your functionality from the base classes made

available to you

&t#s simple small, and easy to use"

8eatures of 2er-lets:


35/97

$ervlets are persistent"$ervlet are loaded only by the web server and can

maintain services between requests"

$ervlets are fast" $ince servlets only need to be l


36/97

&nContrast"an(ttp servlet usually does not override the service67 method"&nstead it

overrides do3et67 to handle 3:T requests and doPost67 to handle Post requests" 2n (ttp

servlet can override either or both of these modules the service67 method of (ttp$ervlet

handles the setup and dispatching to all the doXXX67 methods"which iswhy it usually should

not be overridden

The remainders in the java%"servlet and java%"servlet"http"package are largely suppor

classes "The $ervlet0equest and $ervlet0esponse classes in java%"servlet provide access

to generic server requests and responses while (ttp$ervlet0equest and

(ttp$ervlet0esponse classes in java%"servlet provide access to generic server requests

and responses while (ttp$ervlet0equest and (ttp$ervlet0esponse in java%"servlet"http

provide access a (TTP requests and responses " The java%"servlet"http provide contains

an (ttp$ession class that provides built)in session tracking functionality and Cookie class

that allows quickly setup and processing (ttpCookies"

oading 2er-lets:

$ervlets can be loaded from their places" 8rom a directory that is on the C92$$P2T(" The

C92$$P2T( of the +ava-eb$erver includes service root=classes=, which is where the

system classes reside

8rom the >$:04&C:?0T=servlets=directory"This is not in the server#s classpath" 2 class

loader is used to create servlets form this directory"/ew servlets can be added)e%isting

servlets can be recompiled and the server will notice these changes" 8rom a remote

location"8or this a code base like http*==nine"eng=classes=foo= is required in addtion to the

servlet#s class name"0efer to the admin 3ui docs on servlet section to see how to set this

up"

9oading 0emote $ervlets

0emote servlets can be loaded by*

Configuring the admin Tool to setup automatic loading of remote servlets"

$electiong up server side include tags in "html files

'efining a filter chain Configuration
http://nine.eng/classes/foo/http://nine.eng/classes/foo/


37/97

6n-oking 2er-lets

2 servlet invoker is a servlet that invokes the server! method on a named servlet"&f the

servlet is not loaded in the server,then the invoker first loades the servlet6either form local

disk or from the network7 and the then invokes the service! method"2lso like applets,loca

servlets in the server can be identified by just the class name"&n other words, if a servlet

name is not absolute"it is treated as local"

2 Client can &nvoke $ervlets in the 8ollowing -ays*

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

The client6browser7 can invoke the servlet directly using a 109, once it has been

mapped using the $:049:T 29&2$:$ $ection of the admin 31&

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

&he 2er-let ife 4ycle:=

The $ervlet life cycle is one of the most e%citing features of $ervlets"This life cycle is a

powerful hybrid of the life cycles used in C3& programming and lower)level /$2P& and

&$2P& programming"

The servlet life cycle allows servlet engines to address both the performance and resource

problems of C3& and the security concents of low level server 2P& programming"

$ervlet life cycle is highly fle%ible $ervers hava significant leeway in how they choose to

support servlets"The only hard and fast rule is that a servlet engine must confor to the

following life cycle contact*

Create and initiali@e the servlets

(andle @ero or more service from clients

'estroy the servlet and then garbage Collects it"

&t#s perfectly legal for a servlet t be loaded, created an initial@ed in its own +45,only to be

destroyed an dgarbage collected without hancdling any clientrequest or after handling just

one request


38/97

The most common and most sensible life cycle implemntations for (TTP servelts are*

$ingle java virtual machine and astatine persistence"

6nit and 1estroy*)

+ust like 2pplets servlets can define init67 and destroy67 methods, 2 servlets

init6$erviceConfig7 method is called by the server immediately after the server constructs

the servlet#s instance"'epanding on the server and its configuration, this can be at any of

these times

-hen the server states

-hen the servlet is first requested, just before the service67 method is invoked

2t the request of the server administrator

&n any case, nit67 is guaranteed to be called before the servlet handles its first request

The init67 method is typically used to perform servlet initiali@ation creating or loading objects

that are used by the servlet in handling of its request" &n order to providing a new servlet

any information about itself and its environment, a server has to call a servelts init67 method

and pass an object that implement the $ervletConfig interface"

This $ervletConfig object supplies a servlet with information about its initiali@ation

parameters"These parameters are given to the servlets and are not associated with any

single request"They can specify initial values, such as where a counter should begin

counting, or default values, perhaps a template to use when not specified by the request,

The server calls a servlet#s destroy67 method when the servlet is about to be unloaded" &n

the destroy67 method, a servlet should free any resources it has acquired that will not be

garbage collected" The destroy67 method also gives a servlet a chance to write out its

unsaved" cached information or any persistent information that should be read during thene%t call to init67"

2ession &racking:

(TTP is a stateless protocol, it provides no way for a server to recogni@e that a sequence

of requests is all from the same client" This causes a problem for application such as


39/97

shopping cart applications" :ven in chat application server can#t know e%actly who#s making

a request of several clients"

The solution for this is for client to introduce itself as it makes each request, :ach clients

needs to provide a unique identifier that lets the server identify it, or it needs to give some

information that the server can use to properly handle the request, There are several ways

to send this introductory information with each request $uch as*

!2R 9!&%OR6>9&6ON:

One way to perform session tracking is to le-erage the information that comes with

1ser authori@ation" -hen a web server restricts access to some of its resources to only

those clients that log in using a recogni@ed username and password" 2fter the client logs in,

the username is available to a servlet through get0emote1ser 67

-ean use the username to track the session" nce a user has logged in, the browser

remembers her username and resends the name and password as the user views new

pages on the site" 2 servlet can identify the user through her username and they#re by

Track her session"

The biggest advantage of using user authori@ation to perform session tracking is that it#s

easy to implement" $imply tell the protect a set of pages, and use get0emote1ser67 to

identify each client"2nother advantage is that the technique works even when the user

accesses your site form or e%ists her browser before coming back"

The biggest disadvantage of user authri@ation is that it requires each user to register for an

account and then log in in each time the starts visiting your site" 5ost users will tolerate

registering and lagging in as a necessary evil when they are accessing sensitive

information, but its all overkill for simple session tracking"ther problem with user

authori@ation is that a user cannot simultaneously maintain more than one session at the

same site"

%idden 8orm 8ields:


40/97

ne way to support anonymous session tracking is to use hidden from fields" 2s the name

implies, these are fields added to an (T59, form that are not displayed in the client#s

browser, They are sent back to the server when the form that contains them is submitted"

&n a sense, hidden form fields define constant variables for a form" To a servlet receiving asubmitted form, there is no difference between a hidden fields and a visible filed"

2s more and more information is associated with a clients session " &t can become

burdensome to pass it all using hidden form fields" &n these situations it#s possible to pass

on just a unique session &' that identifies as particular clients session"

That session &' can be associated with complete information about its session that is

stored on the server"

The advantage of hidden form fields is their ubiquity and support for anonymity" (idden

fields are supported in all the popular browsers, they demand on special server

requirements, and they can be used with clients that haven#t registered or logged in"

The major disadvantage with this technique, however is that works only for a sequence of

dynamically generated forms, The technique breaks down immediately with static

documents, emailed documents book marked documents and browser shutdowns"

!R Rewriting:

109 rewriting is another way to support anonymous session tracking, -ith 109

rewriting every local 109 the user might click on is dynamically modified" or rewritten, to

include e%tra, information" The e%tra information can be in the deform of e%tra path

information, added parameters, or some custom, server)specific"109 change" 'ue to the

limited space available in rewriting a 109, the e%tra information is usually limited to a

unique session"

:ach rewriting technique has its own advantage and disadvantage

1sing e%tra path information works on all servers, and it works as a target for forms that

use both the 3et and Post methods" &t does not work well if the servlet has to use the e%tra

path information as true path information


41/97

The advantages and disadvantages of 109"rewriting closely match those of hidden form

fileds,The major difference is that 109 rewriting works for all dynamically created

documents, such as the (elp servlet, not just forms" -ith the right server support, custom

109 rewriting can even work for static documents"

Persistent 4ookies:

2 fourth technique to perform session tracking involves persistent cookies" 2 cookie is a bit

of information" sent by a web server to a browser that can later be read back form that

browser" -hen a browser receives a cookie, it saves the cookie and there after sends the

cookie back to the server each time it accesses a page on that server, subject to certain

rules" Because a cookie#s value can uniquely identify a client, cookies are often used for

session tracking"

Persistent cookies offer an elegant, efficient easy way to implement session tracking"

Cookies provide as automatic an introduction for each request as we could hope for" 8or

each request, a cookie can automatically provide a client#s session &' or perhaps a list of

clients performance" The ability to customi@e cookies gives them e%tra power and

versatility"

The biggest problem with cookies is that browsers don#t always accept cookies sometimes

this is because the browser doesn#t support cookies" 5ore often its because

The browser doesn#t support cookies" 5ore often its because the user has specifically

configured the browser to refuse cookies"

The power of serves*

The power of servlets is nothing but the advantages of servlets over other approaches,

which include portability, power, efficiency, endurance, safety

elegance,integration,e%tensibility and fle%ibility"

Portability:

2s servlets are written in java and conform to a well defined and widely accepted

2P&"they are highly portable across operating systems and across server implementation


42/97

-e can develop a servlet on a windows /T machine running the java web server and later

deploy it effortlessly on a high)end 1ni% server running apache" -ith servlets we can really

write once, serve every where!

$ervlet portability is not the stumbling block it so often is with applets, for two reasons

8irst,$ervlet portability is not mandatory i"e" servlets has to work only on server machines

that we are using for development and deployment

$econd, servlets avoid the most error)prone and inconstancy implemented portion of the

java languages"

Power:

$ervlets can harness the full power of the core java" 2Ps* such as /etworking and 1r

access, multithreading, image manipulation, data compression, data base connectivity

internationali@ation, remote method invocation605&7 C0B2 connectivity, and object

seriali@ation, among others,

fficiency 9nd ndurance:

$ervlet invocation is highly efficient, nce a servlet is loaded it generally remains in the

server#s memory as a single object instance, There after the server invokes the servelt to

handle a request using a simple, light weighted method invocation "1nlike the C3&, there#sno process to spawn or interpreter to invoke, so the servlet can begin handling the request

almost immediately, 5ultiple, concurrent requests are handled the request almost

immediately" 5ultiple, concurrent requests are handled by separate threads, so servlets are

highly scalable"

$ervlets in general are enduring objects" Because a servlets stays in the server#s memory

as a single object instance" it automatically maintains its state and can hold onto e%ternalresources, such as database connections"

2afety:

$ervlets support safe programming practices on a number of levels"


43/97

2s they are written in java,servlets inherit the strong type safety of the java language" &n

addition the servlet 2P& is implemented to be type safe" +ava#s automatic garbage collection

and lack of pointers mean that servlets are generally safe from memory management

problems like dangling pointers invalid pointer references and memory leaks"

$ervlets can handle errors safely, due to java#s e%ception A handling mechanism" &f a

servlet divides by @ero or performs some illegal operations, it throws an e%ception that can

be safely caught and handled by the server"

2 server can further protect itself from servlets through the use of java security

manager"2 server can e%ecute its servlets under the watch of a strict security manager"

legance:

The elegance of the servlet code is striking "$ervlet code is clean, object oriented

modular and ama@ingly simple one reason for this simplicity is the served 2P& itself" -hich

includes methods and classes to handle many of the routine chores of servlet development

:ven advanced to operations like cookie handling and session tracking tracking are

abstracted int convenient classes"

6ntegration:

$ervlets are tightly integrated with the server" This integration allows a servlet to

cooperate with the server in two ways " for e"g"* a servlet can use the server to translate file

paths, perform logging, check authori@ation, perform 5&5: type mapping and in some

cases even add users to the server#s user database"

/tensibility and 8le/ibility:

The servlet 2P& is designed to be easily e%tensible" 2s it stands today the 2P& includes

classes that are optimi@ed for (TTP servlets"But later it can be e%tended and optimi@ed for

another type of servlets"&t is also possible that its support for (TTP servlets could be further

enhanced"


44/97

$ervlets are also quite fle%ible, $un also introduced java server pages" which offer a way to

write snippets of servlet code directly with in a static (T59 page using synta% similar to

5icrosoft#s 2ctive server pages62$P7

?.?.( /!BC

1at is .D%C2

any relational database" ne can write a single program using the +'BC 2P&,and the +'BC

is a +ava 2pi for e%ecuting $9,$tatements62s a point of interest +'BC is trademarked

name and is not an acronym. nevertheless,+dbc is often thought of as standing for +ava

'atabase Connectivity" &t consists of a set of classes and interfaces written in the +ava

Programming language"+'BC provides a standard 2P& for tool=database developers and

makes it possible to write database applications using a pure +ava 2P&

1sing +'BC, it is easy to send $9 statements to virtually program will be able to send

$9 "statements to the appropriate database" The Combination of +ava and +'BC lets a

programmer writes it once and run it anywhere"

1at Does .D%C Do2

Si)pl+ p!t3.D%C )a4es it possi5le to (o tree tings

o :stablish a connection with a database

o $end $9 statements

o Process the results

o +'BC 'river Types

o The +'BC drivers that we are aware of this time fit into one of four categories

o +'BC)'BC Bridge plus 'BC driver

o /ative)2P& party)java driver

o +'BC)/et pure java driver

o /ative)protocol pure +ava driver

2n individual database system is accessed via a specific +'BC driver that implements the

java"sql"'river interface" 'rivers e%ist for nearly all)popular 0'B5$ systems, through few

are available for free" $un bundles a free +'BC)'BC bridge driver with the +' to allow


45/97

access to a standard 'BC,data sources, such as a 5icrosoft 2ccess database, $un

advises against using the bridge driver for anything other than development and very

limited development"

+'BC drivers are available for most database platforms, from a number of vendors andin a number of different flavours" There are four driver categories

T+pe 67.D%C7OD%C %ri(ge Dri/er

Type DE drivers use a bridge technology to connect a java client to an 'BC database

service" $un#s +'BC)'BC bridge is the most common type DE driver" These drivers

implemented using native code"

T+pe 6*7Nati/e7API part+78a/a Dri/er

Type DF drivers wrap a thin layer of java around database)specific native code libraries

for racle databases, the native code libraries might be based on the C&6racle call

&nterface7 libraries, which were originally designed for c@cAAprogrammers, Because type)

DF drivers are implemented using native code" in some cases they have better performance

than their all)java counter parts" They add an element of risk, however, because a defect in

a driver#s native code section can crash the entire server

T+pe 6,7Net7Protocol All7.a/a Dri/er

Type DG drivers communicate via a generic network protocol to a piece of custom

middleware" The middleware component might use any type of driver to provide the actua

database access" These drivers are all java, which makes them useful for applet

deployment and safe for servlet deployment

T+pe7697nati/e7protocol All78a/a Dri/er

Type oH drivers are the most direct of the lot" -ritten entirely in java, Type DH drivers

understand database)specific networking" protocols and can access the database directly

without any additional software


46/97

.D%C7OD%C %ri(ge

&f possible use a Pure +ava +'BC driver instead of the Bridge and an 'BC driver" This

completely eliminates the client configuration required by 'BC"&t also eliminates the

potential that the +ava 45 could be corrupted by an error in the native code brought in by

the Bridge6that is, the Bridge native library, the 'BC driver manager library, library, the

'BC driver library, and the database client library7

1AT IS Te .D%C7OD%E %ri(ge 2

The +'BC)'BC Bridge is a +dbc driver, which implements +'BC operations by translating

them into 'BC operations" To 'BC it appears as a normal application program" The Bridge

is implemented as the sun"jdbc"odbc +ava package and contains a native library used toaccess 'BC"The Bridge is joint development of &ntersolv and +ava $oft

?.?.* Or0c4e

racle is a relational database management system, which organi@es data in the form of

tables" racle is one of many database servers based on 0'B5$ model, which manages a

seer of data that attends three specific things)data structures, data integrity and data

manipulation"

-ith oracle cooperative server technology we can reali@e the benefits of open, relationa

systems for all the applications" racle makes efficient use of all systems resources, on all

hardware architecture. to deliver unmatched performance, price performance and scalability

2ny 'B5$ to be called as 0'B5$ has to satisfy 'r":"8"Codd#s rules"

"eatures of #racle$

Portable

The racle 0'B5$ is available on wide range of platforms ranging from PCs to super

computers and as a multi user loadable module for /ovel /et-are, if you develop application

on system you can run the same application on other systems without any modifications"


47/97

Compatible

racle commands can be used for communicating with &B5 'BF mainframe 0'B5$

that is different from racle, which is racle compatible with 'BF" racle 0'B5$ is a high

performance fault tolerant 'B5$, which is specially designed for online transaction processing

and for handling large database applications"

Multithreaded Server Architecture

racle adaptable multithreaded server architecture delivers scalable high performance

for very large number of users on all hardware architecture including symmetric

multiprocessors 6sumps7 and loosely coupled multiprocessors" Performance is achieved by

eliminating CP1, &=, memory and operating system bottlenecks and by optimi@ing the racle

'B5$ server code to eliminate all internal bottlenecks"

racle has become the most popular 0'B5$ in the market because of its ease of use

Client=server architecture"

'ata independence"

:nsuring data integrity and data security"

5anaging data concurrency"

Parallel processing support for speed up data entry and online transaction processing

used for applications"

'B procedures, functions and packages"

%r!&!"!Codd's Rules

These rules are used for valuating a product to be called as relational database

management systems" ut of EF rules, a 0'B5$ product should satisfy at least I rules J rule

called rule D that must be satisfied"

RU(& )$ "oundation Rule

8or any system to be advertised as, or claimed to be relational 'B5$ should manage

database with in it self, with out using an e%ternal language"


48/97

RU(& *$ Information Rule

2ll information in relational database is represented at logical level in only one way as

values in tables"

RU(& +$ ,uaranteed Access

:ach and every data in a relational database is guaranteed to be logically accessibility

by using to a combination of table name, primary key value and column name"

RU(& $ Systematic .reatment of /ull 0alues

/ull values are supported for representing missing information and inapplicable

information" They must be handled in systematic way, independent of data types"

RU(& 1$ %ynamic #nline Catalog based Relation Model

The database description is represented at the logical level in the same way as ordinary

data so that authori@ed users can apply the same relational language to its interrogation as

they do to the regular data"

RU(& 2$ Comprehensive %ata Sub (anguage

2 relational system may support several languages and various models of terminal use(owever there must be one language whose statement can e%press all of the following*

'ata 'efinitions, 4iew 'efinitions, 'ata 5anipulations, &ntegrity, Constraints

2uthori@ation and transaction boundaries"

RU(& 3$ 0ie4 Updating

2ny view that is theoretical can be updatable if changes can be made to the tables that

effect the desired changes in the view"

RU(& 5$ 6igh level Update7 Insert and %elete

The capability of handling a base relational or derived relational as a single operand

applies not only retrieval of data also to its insertion, updating, and deletion"


49/97

RU(& 8$ Physical %ata Independence

2pplication program and terminal activities remain logically unimpaired whenever any

changes are made in either storage representation or access method"

RU(& 9$ (ogical %ata Independence

2pplication programs and terminal activities remain logically unimpaired whenever any

changes are made in either storage representation or access methods"

RU(& *)$ Integrity Independence

&ntegrity constraints specific to particular database must be definable in the relationa

data stored in the catalog, not in application program"

RU(& **$ %istributed Independence

-hether or not a system supports database distribution, it must have a data sub)

language that can support distributed databases without changing the application program"

RU(& *+$ /on Sub-0ersion

&f a relational system has low level language, that low language cannot use to

subversion or by pass the integrity rules and constraints e%pressed in the higher leve

relational language.

#racle supports the follo4ing Codd's Rules

0ule E* &nformation 0ule 60epresentation of information7)K:$"

0ule F* 3uaranteed 2ccess)K:$"

0ule G* $ystematic treatment of /ull values)K:$"

0ule H* 'ynamic on)line catalog)based 0elational 5odel)K:$"

0ule L* Comprehensive data sub language)K:$"

0ule M* 4iew 1pdating)P20T&29"

0ule N* (igh)level 1pdate, &nsert and 'elete)K:$"

0ule I* Physical data &ndependence)P20T&29"

0ule O* 9ogical data &ndependence)P20T&29"

0ule ED* &ntegrity &ndependence)P20T&29"

0ule EE* 'istributed &ndependence)K:$"


50/97

0ule EF* /on)subversion)K:$"

?.?.? -TM

(yperte%t 5arkup 9anguage6(T597, the languages of the world wide web6---7allows users to produces web pages that included te%t, graphics and pointer to other web

pages 6(yperlinks7"

(T59 is not a programming language but it is an application of &$ $tandard

IINO,$3596$tandard 3enerali@ed 5arkup 9anguage7,but

$peciali@ed to hyperte%t and adapted to the -eb" The idea behind (yperte%t one point to

another point" -e can navigate through the information based on out interest and

preference" 2 markup language is simply a series of items enclosed within the elements

should be displayed"

(yperlinks are underlined or emphasi@ed works that load to other documents or some

portions of the same document"

(tml can be used to display any type of document on the host computer, which can be

geographically at a different location" &t is a versatile language and can be used on any

platform or desktop

(T59 provides tags6special codes7 to make the document look attractive"

(T59 provides are not case)sensitive" 1sing graphics,fonts,different si@es, color, etc"" can

enhance the presentation of the document" 2nything

That is not a tag is part of the document it self"

Basic %tml &ags*

>)) ))Q $pecific Comments"

>2QRRR>=2Q Creates (yperte%t links">BQRRR>=BQ Creates hyperte%t links"

>BigQRR"">=BigQ 8ormats te%t in large)font

>BodyQRR">=BodyQ contains all tags and te%t in the (tml)document

>CenterQRR>=CenterQ Creates Te%t

>''QRRR"">=''Q 'efinition of a term"


51/97

>T2B9:QRR>=T2B9:Q creates table

>TdQRRR"">=TdQ indicates table data in a table"

>TrQRRR"">=TrQ designates a table row

>ThQRRR">=ThQ creates a heading in a table"

9 1 9 N & 9 " 2:=

2 (T59 document is small and hence easy to send over the net"&t is smal

because it does not include formatted information"

(T59 is platform independent

(T59 tags are not case)sensitive"

&.&. /AVA SCRIPT

The +ava $cript 9anguage

+ava$cript is a compact , object)based scripting language for developing client and server

internet applications" /etscape /avigator F"D interprets +ava$cript statements embedded

directly in an (T59 page" and 9ivewire enables you to create server)based applications

similar to common gateway interface6cgi7 programs"

&n a client application for /avigator, +ava$cript statements embedded in an (T59 Page

can recogni@e and respond to user events such as mouse clicks form

&nput, and page navigation"

8or e%ample, you can write a +ava$cript function to verify that users enter valid information

into a form requesting a telephone number or @ip code " -ithout any network transmission,

an (tml page with embedded +ava $cript can interpret the entered te%t and alert the user

with a message dialog if the input is invalid or you can use +ava$cript to perform an action

6such as play an audio file, e%ecute an applet, or communicate with a plug)in7 in response

to the user opening or e%iting a page"


52/97

.# INTRO!UCTION

S51te=1 7e12>;

6ntroduction: 2ystems designis the process or art of defining the architecture,

components, modules, interfaces, and data for a system to satisfy specified requirements" ne

could see it as the application of systems theory to product development" There is some

overlap and synergy with the disciplines of systems analysis, systems architecture and

systems engineering"

Conte:t level %"%$


53/97

(evel-) %"%for &dmin

$erver on

Internet5+ =&7>U5&:4+=

8 =&7>U5&:4+:U7= 0&14A&1'8EB9 :,T :U55 +:&>5+!

=1+$U5T= 0&14A&1'8EB9

9

41+&T+ T&>5+ =&TT+:)&:T=

8 =&TT+:)&:T:&7+= 0&14A&1'8EB9 :,T :U55 +:&>5+!=&TT+:)&:TI)= 0&14A&1'8EB9 :,T :U55 +:&>5+

9

41+&T+ T&>5+ =),4T,1=

8 =),4:&7+= 0&14A&1'8EB9 :,T :U55 +:&>5+!

=),4I)= 0&14A&1'8EB9 :,T :U55 +:&>5+ 9

41+&T+ T&>5+ =+725,L++=

8 =+72:&7+= 0&14A&1'8EB9 :,T :U55 +:&>5+!=+72I)= 0&14A&1'8EB9 :,T :U55 +:&>5+

9

41+&T+ T&>5+ =+725,L++I:/,=8 =5,"I::&7+= 0&14A&1'8EB9 :,T :U55 +:&>5+!

=),>= 0&14A&1'8EB9 :,T :U55 +:&>5+!

=4,:T&4T:,= 0&14A&1'8EB9 :,T :U55 +:&>5+!=+7&I5= 0&14A&1'8EB9 :,T :U55 +:&>5+!

=4U11+:T5,4&TI,:= 0&14A&1'8EB9 :,T :U55 +:&>5+!

=2,$T&5&))1+$$= 0&14A&1'8EB9 :,T :U55 +:&>5+!=4U11+:T,1"&:I$&TI,:= 0&14A&1'8EB9 :,T :U55 +:&>5+!

=+M2+1I+:4+= 0&14A&1'8EB9 :,T :U55 +:&>5+!

=4U11+:T)+$I":&TI,:= 0&14A&1'8EB9 :,T :U55 +:&>5+

941+&T+ T&>5+ =5,"I:=

8 =5,"I::&7+= 0&14A&1'8EB9 :,T :U55 +:&>5+!

=2&$$6,1)= 0&14A&1'8EB9 :,T :U55 +:&>5+!=1,5+= 0&14A&1'8EB9 :,T :U55 +:&>5+

9

41+&T+ T&>5+ =2&TI+:T=

8 =2&TI+:T:&7+= 0&14A&1'8EB9 :,T :U55 +:&>5+!=2&TI+:TI)= 0&14A&1'8EB9 :,T :U55 +:&>5+

9


67/97


68/97

Aome page*

(ogin Page$


69/97

Admin's login$


70/97


71/97

Admin's login page$


72/97

Manage &mployee screen$


73/97

Adding employee$


74/97

%elete &mployee$


75/97

0ie4 &mployee$


76/97

Managing the doctors =adding a doctor>$


77/97

0ie4 %octors$


78/97

%elete %octor$


79/97

Managing the attendants =adding the attendant>$


80/97

0ie4 Attendants$


81/97

%elete Attendant$


82/97

Status of ambulance$


83/97

Status of ambulance$


84/97

0ie4 ambulance services$


85/97

&mployee's login$


86/97

Managing the patient =adding a patient>$


87/97

0ie4 patients$


88/97

%elete Patient$


89/97

0ie4ing patient Status$


90/97

*.# INTRO!UCTION TO TESTIN"

6ntroduction to &esting:

Testing is a process, which reveals errors in the program" &t is the major quality measure

employed during software development" 'uring software development" 'uring testing, the

program is e%ecuted with a set of test cases and the output of the program for the test cases is

evaluated to determine if the program is performing as it is e%pected to perform"

*.$ TESTIN" IN STRATE"IES

&n order to make sure that the system does not have errors, the different levels oftesting strategies that are applied at differing phases of software development are*

Unit Testing:

1nit Testing is done on individual modules as they are completed and become

e%ecutable" &t is confined only to the designerSs requirements"

Eac )o(!le can 5e teste( !sing te "ollo#ing t#o Strategies:

%lac4 %o; Testing:&n this strategy some test cases are generated as input conditions that fully e%ecute

all functional requirements for the program" This testing has been uses to find errors in the

following categories*

&ncorrect or missing functions


91/97

&nterface errors

:rrors in data structure or e%ternal database access

Performance errors

&nitiali@ation and termination errors"

&n this testing only the output is checked for correctness"

The logical flow of the data is not checked"

1ite %o; testing :

&n this the test cases are generated on the logic of each module by drawing flow

graphs of that module and logical decisions are tested on all the cases" &t has been uses to

generate the test cases in the following cases*

3uarantee that all independent paths have been :%ecuted"

:%ecute all logical decisions on their true and false $ides"

:%ecute all loops at their boundaries and within their operational bounds

:%ecute internal data structures to ensure their validity"

Integrating Testing :

&ntegration testing ensures that software and subsystems work together a whole" &t

tests the interface of all the modules to make sure that the modules behave properly

when integrated together"

S+ste) Testing:

&nvolves in)house testing of the entire system before delivery to the user" &tSs aim is to

satisfy the user the system meets all requirements of the clientSs specifications"

Acceptance Testing :

&t is a pre)delivery testing in which entire system is tested at clientSs site on real world datato find errors"

Test Approac :Testing can 5e (one in t#o #a+s:

Bottom up approach

Top down approach


92/97

%otto) !p Approac:

Testing can be performed starting from smallest and lowest level modules and

proceeding one at a time" 8or each module in bottom up testing a short program e%ecutes

the module and provides the needed data so that the module is asked to perform the way it

will when embedded with in the larger system" -hen bottom level modules are tested

attention turns to those on the ne%t level that use the lower level ones they are tested

individually and then linked with the previously e%amined lower level modules"

Top (o#n approac:

This type of testing starts from upper level modules" $ince the detailed activities

usually performed in the lower level routines are not provided stubs are written" 2 stub is a

module shell called by upper level module and that when reached properly will return a

message to the calling module indicating that proper interaction occurred" /o attempt is

made to verify the correctness of the lower level module.


93/97


94/97

+.# INTRO!UCTION

2ystem 2ecurity:

2etting !p 9uthentication for Ceb 9pplications

6ntroduction:To configure authentication for a -eb 2pplication, use the >login)configQ element of the

web"%ml deployment descriptor" &n this element you define the security realm containing theuser credentials, the method of authentication, and the location of resources for authentication"

+.$ SECURITY IN SOFTWARE

To set up authentication for -eb 2pplications*

E" pen the web"%ml deployment descriptor in a te%t editor or use the 2dministration

Console" $pecify the authentication method using the >auth)methodQ element" The

available options are*

B9264Basic authentication uses the -eb Browser to display a username=password dialog

bo%" This username and password is authenticated against the realm"

8OR0

8orm)based authentication requires that you return an (T59 form containing the

username and password" The fields returned from the form elements must be*

j?username and j?password, and the action attribute must be j?security?check" (ere is

an e%ample of the (T59 coding for using 805 authentication*

>form methodUP$TU actionUj?security?checkUQ


95/97

>input typeUte%tU nameUj?usernameUQ

>input typeUpasswordU nameUj?passwordUQ

>=formQ

The resource used to generate the (T59 form may be an (T59 page, a +$P, or a

servlet" Kou define this resource with the >form)login)pageQ element"

The (TTP session object is created when the login page is served" Therefore, the

session"is/ew 67 method returns 829$: when called from pages served after

successful authentication"


96/97


97/97

,. BIBIO"RAP-Y

0eferences fo r the Pro jec t 'eve lopment -ere Taken 8 rom the fo l low ing

Books and -eb $i tes"

JAVA Technologies

+242 Complete 0eference

+ava $cript Programming by Kehuda $hiran

5astering +242 $ecurity

+242F /etworking by Pistoria

+242 $ecurity by $cotl oaks

(ead 8irst :+B $ierra Bates

+F:: Professional by $hadab siddiqui

+242 server pages by 9arne Pekowsley

+242 $erver pages by /ick Todd

HTML

Documents

Ambulance service provider.doc