Virtual Medical Home 4332c

CONTENTS

Page 0 of 97

Sudipta Dhara (1070100)

TITLE

PAGE NO.

1.

ACKNOWLEDGEMENT

2

2.

ABSTRACT

3

3.

INTRODUCTION

4

4.

SYSTEM ANALYSIS 4.1 EXITING SYSTEM

5

4.2 5.

6.

7.

PROPOSED SYSTEM

FEASIBILITY STUDY

5 5 6

5.1

TECHNICAL FEASIBILITY

6

5.2

OPERATIONAL FEASIBILITY

6

5.3

ECONOMICAL FEASIBILITY

7

5.4

PROJECT PLANING

8

SYSTEM REQUIREMENT SPECIFICATION

9

6.1

OVERVIEW

9

6.2

MODULE DESCRIPTION

10

6.3

REQUIREMENTS

11

6.4

DATA DICTIONARY

14

SYSTEM DESIGN 7.1 USECASE DIAGRAM

24 26

7.2

CLASS DIAGRAM

31

7.3

SEQUENCE DIAGRAM

32

8.

IMPLEMENTATION

43

9.

TESTING & DEBUGGING TECHNIQUES

74

10.

OUTPUT SCREENS

83

11.

FUTURE ENHANCEMENT

84

12.

CONCLUTION

95

13.

BIBLIOGRAPHY

96

Page 1 of 97


ACKNOWLEDGEMENTS

There are many people who have helped us directly or indirectly in the successful completion of our project. We would like to take this opportunity to thank one and all. First of all we would like to express our deep sense of gratitude towards our project Guide Sushil Raiguru, Asst Professor Dept. of KSCA for always being available whenever we require her guidance as well as for motivating us throughout the project work. We are also grateful to the Mr B.B.DAS, (Head of Dept.of KSCA) for her valuable guidance during our project. We would like to express our deep gratitude towards our teaching and non-teaching staff for giving their valuable suggestions and co operation for doing our project. We are also deeply indebted to Dr. MOHANTY, Associate Dean, Ksca for providing necessary facility during execution of project. We would like to thank all our friends for their help and constructive criticism during our project period. Finally, we are very much indebted to our parents for their moral and encouragement to achieve higher goals. we have no words to express our gratitude and still we are very thankful to our parents who have shown us this world and for every they gave us.

Signature Sudipta Dhara (1070100)

Page 2 of 97


ABSTRACT

The Project is aimed at providing essential medical services to s irrespective of their locations. This project is also helpful at generating a patient billing software system that is of importance to a hospital. This System maintains the vital information of s, their profiles, their functionalities etc. The System can be viewed as an online hospital service provider. Information about the patient and the charges to be paid is also stored. The development of this new system contains the following activities, which try to automate the entire process keeping in the view of database integration approach.The system provides the information related to the online appointments made by the patients.The appointments made by the patient can be viewed by the respective physicians.By using this system we can prepare all bills pending to be paid by a patient before the patient’s discharge.This system is providing the facility of viewing all information about patients details, their it time and the amount to be paid based on the treatment given.Keep track of latest developments happening in the medical technologies.Authentication is provided for this application only ed can access.

Page 3 of 97


INTRODUCTION

This project aims at developing a Virtual Medical Home system that is of importance to a hospital to facilitate the much needed and important Medical Services that are essential to human health. The VHM is a local software system. This system can be used to maintain the information of each patients, their profiles, Physician profile, latest developments in the medical technologies etc. Information about the patient and the charges to be paid is also stored. The patients can online.After ing the patients can use the large facilities of the system.The KIOS manager maintain the overall data flow of the system,like to search the doctor as specialist,manage the appointments,display the doctor and patients reply.The system can also maintain a good friendly environments.Patients can give to the doctor.Depending on the patients the can generate the rank of the doctor.The patients can search the doctor depending on his/her problems.The patients can also refer the system to select the appropriate doctor for the problems.The Kios manager take the patients requirements and take the appropriate task.

SYSTEM ANALYSIS Page 4 of 97


PURPOSE OF THE SYSTEM The Project is aimed at providing essential medical services to s irrespective of their locations. This project is also helpful at generating a patient billing software system that is of importance to a hospital. This System maintains the vital information of s, their profiles, their functionalities etc. The System can be viewed as an online hospital service provider. Information about the patient and the charges to be paid is also stored.

EXISTING SYSTEM The existing system is containing the full information about doctors,patients & gives a necessary information about the patients problem.It also contains the authentication for every s.

PROPOSED SYSTEM The development of this new system contains the following activities, which try to automate the entire process keeping in the view of database integration approach. •

The system provides the information related to the online appointments made by the patients.

•

The appointments made by the patient can be viewed by the respective physicians.

•

This system is providing the facility of viewing all information about patients details, their it time and the amount to be paid based on the treatment given.

•

Authentication is provided for this application only ed s can access.

•

Keep track of latest developments happening in the medical technologies

FEASIBILITY STUDY

Page 5 of 97


TECHNICAL FEASIBILITY: Evaluating the technical feasibility is the trickiest part of a feasibility study. This is because, at this point in time, not too many detailed design of the system, making it difficult to access issues like performance, costs on (on of the kind of technology to be deployed) etc. A number of issues have to be considered while doing a technical analysis. i)

Understand the different technologies involved in the proposed system: Before commencing the project, we have to be very clear about what are the technologies that are to be required for the development of the new system.

ii)

Find out whether the organization currently possesses the required technologies: Is the required technology available with the organization? If so is the capacity sufficient? For instance – Will the current printer be able to handle the new reports and forms required for the new system?‖

OPERATIONAL FEASIBILITY: Proposed projects are beneficial only if they can be turned into information systems that will meet the organizations operating requirements. Simply stated, this test of feasibility asks if the system will work when it is developed and installed. Are there major barriers to Implementation? Here are questions that will help test the operational feasibility of a project: 

Is there sufficient for the project from management from s? If the current system is well liked and used to the extent that persons will not be able to see reasons for change, there may be resistance.



Are the current business methods acceptable to the ? If they are not, s may welcome a change that will bring about a more operational and useful systems.



Have the been involved in the planning and development of the project?



Early involvement reduces the chances of resistance to the system and in



General and increases the likelihood of successful project. Page 6 of 97


Since the proposed system was to help reduce the hardships encountered. In the existing manual system, the new system was considered to be operational feasible.

ECONOMIC FEASIBILITY: Economic feasibility attempts to weigh the costs of developing and implementing a new system, against the benefits that would occur from having the new system in place. This feasibility study gives the top management the economic justification for the new system. A simple economic analysis which gives the actual comparison of costs and benefits are much more meaningful in this case. In addition, this proves to be a useful point of reference to compare actual costs as the project progresses. There could be various types of intangible benefits on of automation. These could include increased customer satisfaction, improvement in product quality better decision making timeliness of information, expediting activities, improved accuracy of operations, better documentation and record keeping, faster retrieval of information, better employee morale.

Project Planning: For successful completion of the project the project manager need to maintain the SPMP documents. Page 7 of 97


The SPMP documents is, 1.Introduction: i. ii.

iii.

Objective:-The main objective behind to develop this project is to create a best way to help the needy persons. Major Funtions:-The major functions of this project is to ,give them the facilities of the system with some authentications. Management & Technical constraints:-During live on the system it needed the internet facility.

2.Project Estimates: i. ii.

Efforts,Resource,Cost,Duration Estimates. Historical data used

3.Project Resource: i.

Hardware & Software Resource:

Operating System Interface

: :

Windows XP/2003/2008 or Linux HTML, CSS

Client-side Scripting

:

JavaScript

Programming Language

:

Java

Web Applications

:

JDBC, Servlets, JSP

IDE/Workbench

:

My Eclipse (Juno)

Database

:

Oracle

Server Deployment

:

Tomcat 7.x

Hardware Requirements: Processor Hard Disk

: :

Intel Core U 2.53 GHz or higher. 40GB

RAM

:

512MB or higher Page 8 of 97


Others Requirements:

Connectivity Power

: :

Internet Facilities Power Facilities

SYSTEM REQUIREMENT SPECIFICATION

STUDY OF THE SYSTEM NUMBER OF MODULES 1. module 2. Physician(Doctor) module 3. Patients module 4. KIOS manager module

MODULES DESCRIPTION : This module is having the facility of ing the s which are details pertaining to the hospital details. He maintains all the employee’s details. He can also view all the details of patients, ’s profiles etc and also provided with search options. He can track Page 9 of 97


down the available physicians present in the system. can also to take backup of all kind of data view formation etc.

Physician module This module deals with the details of all the patients, their online appointments and the amount to be paid based on the treatment given. He can also view the total patients as well as the appointments made by the patients to the respective physician. The physicians, based on the patient’s health condition also have an option of giving e-prescriptions, once the patient requests him for an appointment. Physician can track down the latest updations happening in the medical technology by utilizing the forum facilities available in the system. He can also post his own innovative techniques, as well as latest trends happening in the medical stream by posting in the forum options. Physician also has an option of viewing the patient’s history.

Patients module The patient’s module deals with the utilization of services related to the hospital. Patients to make online appointment, and make a request for the respective physician. The patient also has an option of viewing previous health record, their bills, medical prescriptions etc..The patient additionally has an option of lodging a complaint to in case of incorrect medicine prescriptions and fatal problems. Patient also can participate in forums and share his brilliance with different s and also can post his own new ideas or provide information to the s regarding the latest happenings in the field of medical.

Kiosk module The Kiosk functionality is specified to adjusting the appointments or viewing the respective appointments given by the patients. His work includes facilitating the patients by providing the physicians appointment or marking them by giving appropriate date. He can calculate his own commission and also perform different operations.

Page 10 of 97


Security and Authentication: 1. as , Physician, Patient or Kiosk. 2. Change 3. Session & cookies 4. Mail verification

Functional Requirements: R1. Registration of Patient. Input: name and . Output: Patients home page. Processing: and name match. R1.1.Search Doctor. Input: Doctor specialist. Output: Doctors list. Processing: Doctor search.

R1.2.Select Doctor. Input: Select appropiate doctor. Output: Submit form. Processing: Check doctor R1.3.Running Appointment Page 11 of 97


Input: Current symtomps. Output: Prescription form Processing: Check patient symptomps. R1.4.Pending Appointment Input: Symptoms. Output: Waiting for approved. Processing: Requesting to the Kiosk Manager R1.5.Close Appointment Input: Select close appointment. Output: form. Processing: Save to the database. R2.Registration of Kiosk Manager. Input: name and . Output: Kiosk Manager home page. Processing: and name match. R2.1.Approved Input: Patients requirements. Output: Redirect to the doctor. Processing: Notification to the doctor. R2.2.Unavailability Input: Selected doctor. Output: Unavailable doctor. Processing: Doctor search. R3.Registration of Doctor. Input: name & . Output: Doctor home page.. Processing: name matched.. Page 12 of 97


R3.1.Choose Appointment. Input: Search appointment. Output: Patients description with symtomps. Processing: Reply to the patient. R3.2.Prescription Input: Patients symptoms(appointment fixed) Output: Prescription form. Processing: Save to database.

R3.3.Close Case Input: Choose the case. Output: Remove appointment. Processing; Notification to the patient & save to database. R4.Registration of . Input: name and . Output: home page. Processing: and name match.

R4.1. handle. Input: Patient . Output: Rating/Notification to the doctor. Processing: processing,& save to database.

R4.2.News generate Input: System news. Output: Notification updated. Processing: Save to database. Page 13 of 97


Non Functional Requirements:  24 X 7 available  Services for ambulance and others facilities  Quick service

Goals Of Implementation: The goal in contrast to the functional and nonfunctional requirements is not checked by the customer for conformance at time of acceptance testing.This part of SRS documents offers some general suggestion regarding development.

Data Dictionary Tables & Its Attributes: Detail:-

Doctor Details:-

Page 14 of 97


Patients Details:-

Doctor Specialist Detail:Page 15 of 97


Symptoms Details:-

Appointments:Page 16 of 97


Kiosk Manager Details:-

Consult Details:Page 17 of 97


Page 18 of 97


Person Details:-

Prescription

Patients reply:-

Page 19 of 97


Details:-

Some SQL Statements: Page 20 of 97


 create table person(id number(10),fname varchar2(35),lname varchar2(35),sex varchar2(8),phno number(15),email varchar2(50) unique,street varchar2(50),city varchar2(30),country varchar(30),pin number(6),id varchar2(15) UNIQUE, varchar2(20),type

varchar(10),activation

number(1),dob

date,constraint

pk_id

PRIMARY KEY(id));  create

table

doctors(docid

varchar2(35),qualification

number(10),person_id varchar2(35),regno

number(10),specialist varchar2(15),work_in

varchar2(200),rank number(4),activation number(1),CONSTRAINT pk_DoctorID PRIMARY KEY (docid),FOREIGN KEY (person_id) REFERENCES person(id));

 create table patients(pid number(10),person_id number(10),height varchar2(10),weight number(3),blood_group varchar2(8),smoke varchar2(15),drink varchar2(15),work_in varchar2(200),case_id number(10),activation number(1),CONSTRAINT pk_PatientID PRIMARY KEY (pid),FOREIGN KEY (person_id) REFERENCES person(id));  create table kioskmanager(mid number(10),person_id number(10),qualification varchar2(35),working_exp

varchar2(500),activation

number(1),CONSTRAINT

pk_KioskID PRIMARY KEY (mid),FOREIGN KEY (person_id) REFERENCES person(id));

 create

table

symptoms(id

number(10)

PRIMARY

KEY,name

varchar2(35)

UNIQUE,sgroup varchar2(35),description varchar2(150),activation number(1));  create table doc_speciality(doc_type_id number(10) PRIMARY KEY,doc_type varchar2(35) UNIQUE,activation number(1));  create

table

appointment(id

number(5),docid

number(10),patient_id

number(10),booking_date date,suffering_from date,helth_status number(3),symptom varchar2(150),verified

number(1),activation

number(1),closed_by Page 21 of 97


number(10),CONSTRAINT pk_AppID PRIMARY KEY (id),FOREIGN KEY (docid) REFERENCES

doctors(docid),FOREIGN

KEY

(patient_id)

REFERENCES

patients(pid),FOREIGN KEY (closed_by) REFERENCES person(id));  create

table

consult(id

number(5),patient_id

varchar2(50),prob_description

number(10),prob_heading

varchar2(1500),reg_date

date,suffering_from

date,ref_by_kiosk number(10),ref_to_doc number(10),verified number(1),activation number(1),CONSTRAINT pk_ConsultID PRIMARY KEY (id),FOREIGN KEY (ref_to_doc)

REFERENCES

REFERENCES

doctors(docid),FOREIGN

patients(pid),FOREIGN

KEY

KEY

(ref_by_kiosk)

(patient_id)

REFERENCES

kioskmanager(mid));

 create

table

prescription(id

number(5),appointment_id

number(5),pdate

date,by_doc_id number(10),prescription nclob,activation number(1),CONSTRAINT pk_PrescriptionID REFERENCES

PRIMARY

KEY

(id),FOREIGN

appointment(id),FOREIGN

KEY

KEY

(by_doc_id)

(appointment_id) REFERENCES

doctors(docid));  create table patient_reply(reply_id number(10),prescription_id number(5),helth_status number(3),reply_date

date,updated_symptom

varchar2(150),reply_comments

nclob,activation number(1),CONSTRAINT pk_PatientReplyID PRIMARY KEY (reply_id),FOREIGN KEY (prescription_id) REFERENCES prescription(id));

 create table (id number(10),cure number(2),wait_time number(2),side_effect varchar2(150),rate_doctor varchar2(150),vmh_helpful

number(3),doc_manr number(2),visit_again

number(2),commentdoc number(2),

clob,appointment_id number(5),activation number(1),CONSTRAINT pk_FeedID PRIMARY

KEY

(id),FOREIGN

KEY

(appointment_id)

REFERENCES

appointment(id)): Page 22 of 97


 create table doctor_graph(param varchar2(35),jan number(3),feb number(3),mar number(3),apr

number(3),may

number(3),sep

number(3),oct

number(3),june number(3),nov

number(3),july number(3),dec

number(3),aug number(3),docid

number(10));

 select * from patient_reply where prescription_id=(select max(id) from prescription where appointment_id=(select max(id) from appointment where activation=1 and patient_id=2) and id<>(select max(id) from prescription where appointment_id=(select max(id) from appointment where activation=1 and patient_id=2)));

 create table news(id number(5), heading varchar2(50), description varchar2(100), ndate date, activation number(1));  create table (id number(5),name varchar2(100), email varchar2(100), message clob,activation number(1));

SYSTEM DESIGN UNIFIED MODELING LANGUAGE DIAGRAMS The unified modeling language allows the software engineer to express an analysis model using the modeling notation that is governed by a set of syntactic semantic and pragmatic rules. A Page 23 of 97


UML system is represented using five different views that describe the system from distinctly different perspective. Each view is defined by a set of diagram, which is as follows. MODEL VIEW This view represents the system from the s perspective. The analysis representation describes a usage scenario from the end-s perspective.

STRUCTURAL MODEL VIEW In this model the data and functionality are arrived from inside the system. This model view models the static structures.

BEHAVIORAL MODEL VIEW It represents the dynamic of behavioral as parts of the system, depicting the interactions of collection between various structural elements described in the model and structural model view.

IMPLEMENTATION MODEL VIEW In this the structural and behavioral as parts of the system are represented as they are to be built. ENVIRONMENTAL MODEL VIEW Page 24 of 97


In this the structural and behavioral aspects of the environment in which the system is to be implemented are represented. UML is specifically constructed through two different domains they are:

UML Analysis modeling, which focuses on the model and structural model views of the system.

UML design modeling, which focuses on the behavioral modeling, implementation modeling and environmental model views.

Use case Diagrams represent the functionality of the system from a ’s point of view. Use cases are used during requirements elicitation and analysis to represent the functionality of the system. Use cases focus on the behavior of the system from external point of view. Actors are external entities that interact with the system. Examples of actors include s like , bank customer …etc., or another system like central database.

USECASE DIAGRAM USE CASE:-

Page 25 of 97


System

Virtual Medical Home Physician

Patient

Kiosk

KIOSK MANAGER (USE CASE)

Page 26 of 97


System

Registration of Physician

Registration of Patient Kiosk

Registration of Kiosk

Viewing of s

Grievence and of Patients

DOCTOR (USE CASE) Page 27 of 97


System

Giving Appointments

Physician or Doctor

Giving e-prescriptions

Viewing of Patients

Patient (USE CASE)

Page 28 of 97


System

Make Online Appointment

Viewing of Health Record Patient

Viewing of Physicians Prescriptions

Viewing of Bills

(USE CASE)

Page 29 of 97


System

Viewing and Adjusting of Appointments

Viewing of Requirements

Checking the status

Calculation of Commission

Page 30 of 97


Class Diagram:

Page 31 of 97


Sequence Diagram: Person :

Page 32 of 97


Page 33 of 97


Assign doctor:

Page 34 of 97


Change Doctor:

Delete Appointment:

Page 35 of 97


Delete Consult:

Doctor:

Page 36 of 97


Patient :

appointment:

Page 37 of 97


Patient Close Case:

News:

Page 38 of 97


Update Database:

Page 39 of 97


Persons Registration:

Page 40 of 97


Doctor Prescription:

Page 41 of 97


Doctor registration:

Page 42 of 97


IMPLEMENTATION

HTML HTML, an initialism of Hypertext Markup Language, is the predominant markup language for web pages. It provides a means to describe the structure of text-based information in a document — by denoting certain text as headings, paragraphs, lists, and so on — and to supplement that text with interactive forms, embedded images, and other objects. HTML is written in the form of labels (known as tags), surrounded by angle brackets. HTML can also describe, to some degree, the appearance and semantics of a document, and can include embedded scripting language code which can affect the behavior of web browsers and other HTML processors. 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.

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 s 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 update the browser’s display accordingly Page 43 of 97


Even though JavaScript s both client and server Web programming, we prefer JavaScript at Client side programming since most of the browsers s 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 LANGUAGE = ―JavaScript‖> JavaScript statements 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 Browser’s 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.

 

Detect installed plug-ins and notify the if a plug-in is required. We can do much more with JavaScript, including creating entire application.

Page 44 of 97


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 Client-side since all the browsers s it.

Java Technology Initially the language was called as ―oak‖ but it was renamed as ―Java‖ in 1995. The primary motivation of this language was the need for a platform-independent (i.e., architecture neutral) language that could be used to create software to be embedded in various consumer electronic devices. •

Java is a programmer’s language.

•

Except for those constraints imposed by the Internet environment, Java gives the

Java is cohesive and consistent.

programmer, full control. Finally, Java is to Internet programming where C was to system programming.

Java Technology

Java has had a profound effect on the Internet. This is because; Java expands the Universe of objects that can move about freely in Cyberspace. In a network, two categories of objects are transmitted between the Server and the Personal computer. They are: ive information and Dynamic active programs. The Dynamic, Self-executing programs cause serious problems in the areas of Security and probability. But, Java addresses those

Page 45 of 97


concerns and by doing so, has opened the door to an exciting new form of program called the Applet. Java can be used to create two types of programs Applications and Applets: An application is a program that runs on our Computer under the operating system of that computer. It is more or less like one creating using C or C++. Java’s ability to create Applets makes it important. An Applet is an application designed to be transmitted over the Internet and executed by a Java –compatible web browser. An applet is actually a tiny Java program, dynamically ed across the network, just like an image. But the difference is, it is an intelligent program, not just a media file. It can react to the input and dynamically change.

Features of Java Security Every time you that you a ―normal‖ program, you are risking a viral infection. Prior to Java, most s did not executable programs frequently, and those who did scan them for viruses prior to execution. Most s still worried about the possibility of infecting their systems with a virus. In addition, another type of malicious program exists that must be guarded against. This type of program can gather private information, such as credit card numbers, bank balances, and s. Java answers both these concerns by providing a ―firewall‖ between a network application and your computer. When you use a Java-compatible Web browser, you can safely Java applets without fear of virus infection or malicious intent.

Page 46 of 97


Portability

For programs to be dynamically ed to all the various types of platforms connected to the Internet, some means of generating portable executable code is needed .As you will see, the same mechanism that helps ensure security also helps create portability. Indeed, Java’s solution to these two problems is both elegant and efficient.

The Byte code The key that allows the Java to solve the security and portability problems is that the output of Java compiler is Byte code. Byte code is a highly optimized set of instructions designed to be executed by the Java run-time system, which is called the Java Virtual Machine (JVM). That is, in its standard form, the JVM is an interpreter for byte code. Translating a Java program into byte code helps makes it much easier to run a program in a wide variety of environments. The reason is, once the run-time package exists for a given system, any Java program can run on it. Although Java was designed for interpretation, there is technically nothing about Java that prevents on-the-fly compilation of byte code into native code. Sun has just completed its Just In Time (JIT) compiler for byte code. When the JIT compiler is a part of JVM, it compiles byte code into executable code in real time, on a piece-by-piece, demand basis. It is not possible to compile an entire Java program into executable code all at once, because Java performs various run-time checks that can be done only at run time. The JIT compiles code, as it is needed, during execution.

Java Virtual Machine (JVM) Beyond the language, there is the Java virtual machine. The Java virtual machine is an important element of the Java technology. The virtual machine can be embedded within a web browser or an operating system. Once a piece of Java code is loaded onto a machine, it is verified. As part of the loading process, a class loader is invoked and does byte code verification makes sure that the code that’s has been generated by the compiler Page 47 of 97


will not corrupt the machine that it’s loaded on. Byte code verification takes place at the end of the compilation process to make sure that is all accurate and correct. So byte code verification is integral to the compiling and executing of Java code. Java programming uses to produce byte codes and executes them. The first box indicates that the Java source code is located in a. Java file that is processed with a Java compiler called javac. The Java compiler produces a file called a. class file, which contains the byte code. The .Class file is then loaded across the network or loaded locally on your machine into the execution environment is the Java virtual machine, which interprets and executes the byte code.

Java Architecture Java architecture provides a portable, robust, high performing environment for development. Java provides portability by compiling the byte codes for the Java Virtual Machine, which is then interpreted on each platform by the run-time environment. Java is a dynamic system, able to load code when needed from a machine in the same room or across the planet.

Java PC Compiler

Java

Source Code ………..

Interpreter (PC)

Macintosh

Byte code

Compiler

Java Interpreter

………..

(Macintosh ) SPARC

Java (Platform Interpreter (Spare )

During run-time the Java interpreter tricks the byte code file into thinking that it is running Page 48 of 97


Java was designed to be easy for the Professional programmer to learn and to use effectively. If you are an experienced C++ programmer, learning Java will be even easier. Because Java inherits the C/C++ syntax and many of the object oriented features of C++. Most of the confusing concepts from C++ are either left out of Java or implemented in a cleaner, more approachable manner. In Java there are a small number of clearly defined ways to accomplish a given task.

Object-Oriented Java was not designed to be source-code compatible with any other language. This allowed the Java team the freedom to design with a blank slate. One outcome of this was a clean usable, pragmatic approach to objects. The object model in Java is simple and easy to extend, while simple types, such as integers, are kept as high-performance nonobjects.

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 Page 49 of 97


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.

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: 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. Page 50 of 97


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 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 's SQL statements are delivered to the database, and the results of those statements are sent back to the . The database may be located on another machine to which the is connected via a network. This is referred to as a client/server configuration, with the 's machine as the client, and the machine

JAVA

JDBC

DBMS

Client machine

DBMS -proprietary protocol

Database server

Page 51 of 97


Java applet or

Client machine

HTTP, RMI, or CORBA Application Server (Java)

JDBC

Server machine DBMS - proprietary

Database server

DBMS

Page 52 of 97


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

Page 53 of 97


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 t development of Innersole and Java Soft.

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

Database: A database management system (DBMS) is computer software designed for the purpose of managing databases, a large set of structured data, and run operations on the data requested by numerous s. Typical examples of DBMSs include Oracle, DB2, Microsoft Access, Microsoft SQL Server, Firebird, PostgreSQL, MySQL, SQLite, FileMaker and Sybase Adaptive Server Enterprise. DBMSs are typically used by Database s in the creation of Database systems. Typical examples of DBMS use include ing, human resources and customer systems. A DBMS is a complex set of software programs that controls the organization, storage, management, and retrieval of data in a database. A DBMS includes:  A modeling language to define the schema of each database hosted in the DBMS, according to the DBMS data model. Page 54 of 97


•

The four most common types of organizations are the hierarchical, network, relational and object models. Inverted lists and other methods are also used. A given database management system may provide one or more of the four models. The optimal structure depends on the natural organization of the application's data, and on the application's requirements (which include transaction rate (speed), reliability, maintainability, scalability, and cost).

•

The dominant model in use today is the ad hoc one embedded in SQL, despite the objections of purists who believe this model is a corruption of the relational model, since it violates several of its fundamental principles for the sake of practicality and performance. Many DBMSs also the Open Database Connectivity API that s a standard way for programmers to access the DBMS.

 Data structures (fields, records, files and objects) optimized to deal with very large amounts of data stored on a permanent data storage device (which implies relatively slow access compared to volatile main memory). 

When a DBMS is used, information systems can be changed much more easily

as the organization's information requirements change. New categories of data can be added to the database without disruption to the existing system. 

Organizations may use one kind of DBMS for daily transaction processing and

then move the detail onto another computer that uses another DBMS better suited for random inquiries and analysis. Overall systems design decisions are performed by data s and systems analysts. Detailed database design is performed by database s. 

Database servers are specially designed computers that hold the actual databases

and run only the DBMS and related software. Database servers are usually multiprocessor computers, with RAID disk arrays used for stable storage. Connected to one or more servers via a high-speed channel, hardware database accelerators are also used in large volume transaction processing environments.

Page 55 of 97


SQL Structured Query Language (SQL) is the language used to manipulate relational databases. SQL is tied very closely with the relational model. In the relational model, data is stored in structures called relations or tables. Data definition: Defining tables and structures in the database (DDL used to create, alter and drop schema objects such as tables and indexes). Data manipulation: Used to manipulate the data within those schema objects (DML Inserting, Updating, Deleting the data, and Querying the Database). •

ALTER - Change an existing table, view or index definition (DDL)

•

AUDIT - Track the changes made to a table (DDL)

•

COMMENT - Add a comment to a table or column in a table (DDL)

•

COMMIT - Make all recent changes permanent (DML - transactional)

•

CREATE - Create new database objects such as tables or views (DDL)

•

DELETE - Delete rows from a database table (DML)

•

DROP - Drop a database object such as a table, view or index (DDL)

GRANT

- Allow another to access database objects such as tables or views (DDL) •

INSERT - Insert new data into a database table (DML)

•

No AUDIT - Turn off the auditing function (DDL)

•

REVOKE - Disallow a access to database objects such as tables and views (DDL)

•

ROLLBACK - Undo any recent changes to the database (DML -

Transactional) • SELECT - Retrieve data from a database table (DML) • TRUNCATE - Delete all rows from a database table (can not be rolled back) (DML) Page 56 of 97


SERVLETS 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. Servlets provide a Java-based solution used to address the problems currently associated with doing server-side programming, including inextensible scripting solutions, platformspecific APIs, and incomplete interfaces. Servlets are objects that conform to a specific interface that can be plugged into a Javabased server. Servlets 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 from applets in that they are faceless objects (without graphics or a GUI component). They serve as platform independent, dynamically loadable,

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:



They’re 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). Page 57 of 97


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 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.

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: •

It’s extensible - you can inherit all your functionality from the base classes made available to you.

•

It’s simple, small, and easy to use.

Page 58 of 97


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 server’s 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. Remote Servlets can be loaded by: 1. Configuring the Tool to setup automatic loading of remote Servlets 2. Setting up server side include tags in. shtml files 3. Defining a filter chain configuration

Page 59 of 97


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 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.

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.

Page 60 of 97


Portability: Java Server Pages files can be run on any web server or web-enabled application server that provides for them. Dubbed the JSP engine, this 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 the embedding of a scripting language directly into the Java Server Pages file. The components current ed include Java Beans, and Servlets.

Steps in the execution of a JSP Application: 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. JSP engine is program which can under stands 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.

Page 61 of 97


PROCESS FLOW

The Model 2 architecture for deg JSP pages is in reality, Model View Controller (MVC) applied to web applications. Hence the two can be used interchangeably in the web world. MVC originated in SmallTalk and has since made its way into Java community. Model 2 architecure and its derivatives are the cornerstones for all serious and industrial strength web applications designed in the real world. Hence it is essential for you understand this paradigm thoroughly.

The main difference between Model 1 and Model 2 is that in Model 2, a controller handles the request instead of another JSP. The controller is implemented as a Servlet. The following steps are executed when the submits the request 1. The Controller Servlet handles the ’s request. (This means the hyperlink in the JSP should point to the controller servlet). 2. The Controller Servlet then instantiates appropriate JavaBeans based on the request parameters (and optionally also based on session attributes).

3. The

Controller Servlet then by itself or through a controller helper communicates with the middle tier or directly to the database to fetch the required data. 4. The Controller sets the resultant JavaBeans (either same or a new one) in one of the following contexts – request, session or application. 5. The controller then dispatches the request to the next view based on the request URL. 6. The View uses the resultant JavaBeans from Step 4 to display data. Note that there is no presentation logic in the JSP. The sole function of the JSP in Model 2

Page 62 of 97


architecture is to display the data from the JavaBeans set in the request, session or application scopes.

What is a Web Application? Applications built using the Struts framework are at their core, web applications. A web application is a collection of individual components that once bound together, form a complete application that can be installed and executed by a web container. The components are tied together due to the fact that they reside in the same web context and in many cases, may refer to one another, directly or indirectly.

Page 63 of 97


Elements of a Web Application Obviously, not all web applications are created equal. They will not have the same functional and non-functional requirements across organizations, departments, or even the same vertical markets. Therefore, not all web applications will contain the same types of resources. In general however, web applications can consist of one or more of the following types of components:

 Servlets  JSP Pages  Standard JavaBeans and Utility Classes  HTML Documents  Multimedia Files (Images, Audio and Video Files, CAD Drawings, etc… )  Client side Applets, Stylesheets, and JavaScript Files  Text Documents Meta information that ties all of the above components together

Page 64 of 97


What is a Framework? I have been throwing the word framework around in this chapter without having really defined what exactly it is or how it adds value in software development. In its simplest form, a framework is a set of classes and interfaces that cooperate to solve a specific type of software problem. A framework has the following characteristics:  A framework is made up of multiple classes or components, each of which may Provide an abstraction of some particular concept.  The framework defines how these abstractions work together to solve a problem.  The framework components are reusable

A good framework should provide generic behavior that can be utilized across many different types of applications. There are many interpretations of what constitutes a framework. Some might consider the classes and interfaces provided by the Java language a framework, but it’s really a library. There’s a subtle, but very distinct difference between a software library and a framework. With a software library, your application is the main code that executes and it invokes routines on the library. With a framework, it contains the executing routines and invokes operations onto your extensions through inheritance and other means. The places where the framework can be extended are known as extension points. A framework is commonly referred to an ―upside-down‖ library because of the alternate manner in which it operates.

Creation of the Struts Framework By now you should have a foundation for JSP and Servlet technology and you should also understand the benefits that the Web MVC design and JSP Model 2 architecture adds to a web application. This section provides a little background and history on the Struts framework, which is an implementation of all of these ideas. Page 65 of 97


Page 66 of 97


Page 67 of 97


What are Action Forms? Almost every web application has a requirement to accept input from s. Some examples of input are credit card information, billing and shipping address information, or even something as small as a name and . The HTML language provides the necessary components to render the input fields in a browser, including text boxes, radio buttons, check boxes, buttons, and many more. When building these types of pages, the input components must be nested inside of an HTML form Elements. The Struts framework relies on the org.apache.struts.action.ActionForm class as the key component for handling these tasks. The ActionForm class is used to capture input data from an HTML form and transfer it to the Action class. Since the HTML input components don’t natively include an input buffer and s quite often enter invalid data, web applications need a way to store the input data temporarily, so that it can be redisplayed when an error occurs. In this sense, the ActionForm class acts as a buffer to hold the state of what the entered while it is being validated. The ActionForm also acts as a ―firewall‖ for your application in that it helps to keep suspect or invalid input out of your business tier until it can be scrutinized by the validation rules. Finally, the ActionForm is also used to transfer data from the Action class back to the HTML form. This allows more consistency for your HTML forms, because they are always pulling data from the ActionForm. When the input data does input validation, the ActionForm is ed into the execute() method of the Action class. From there, the data can be retrieved from the ActionForm and ed on to the business tier. Because the ActionForm imports packages from the Servlet API, you shouldn’t the ActionForm to the business tier. Doing so would couple the business methods to the Servlet API and make it more difficult to reuse the business tier components. Instead, the data within the ActionForm should be transferred to an object from the domain model instead of being ed as an argument to the business tier. A common approach is to create a data transfer object and populate it with the data from the ActionForm. You don’t have to declare an ActionForm for every HTML form in your application. The same ActionForm can be associated with one or more action mappings. This means that they can be shared across multiple HTML forms. For example, if you Page 68 of 97


had a wizard interface, where a set of data was entered and posted across multiple pages, a single ActionForm can be used to capture all of this data, a few fields at a time. The ActionForm class provided by the Struts framework is abstract. You need to create subclasses of it to capture your application specific form data. Within your subclass, you should define a property for each field that you wish to capture from the HTML form.The ActionForm is populated from request parameters, not request attributes. If you are forwarding from one action to anther, you can’tadd a request attribute and expect that the ActionForm will be populated from it.

Eclipse IDE: Eclipse is an open-source software framework written primarily in Java. In its default form it is an Integrated Development Environment (IDE) for Java developers, consisting of the Java Development Tools (JDT) and the Eclipse Compiler for Java (ECJ). s can extend its capabilities by installing plug-ins written for the Eclipse software framework, such as development toolkits for other programming languages, and can write and contribute their own plug-in modules. Language packs are available for over a dozen languages. The basis for Eclipse is the Rich Client Platform (R). The following components constitute the rich client platform:  OSGi - a standard bundling framework  Core platform - boot Eclipse, run plug-ins  the Standard Widget Toolkit (SWT) - a portable widget toolkit JFace - viewer classes to bring model view controller programming to SWT, file buffers, text handling, text editors

Page 69 of 97


 the Eclipse Workbench - views, editors, perspectives, wizards Eclipse's widgets are implemented by a widget toolkit for Java called SWT, unlike most Java applications, which use the Java standard Abstract Window Toolkit (AWT) or Swing. Eclipse's interface also leverages an intermediate GUI layer called JFace, which simplifies the construction of applications based on SWT. Eclipse employs plug-ins in order to provide all of its functionality on top of (and including) the rich client platform, in contrast to some other applications where functionality is typically hard coded. This plug-in mechanism is a lightweight software componentry framework. In addition to allowing Eclipse to be extended using other programming languages such as C and Python, the plug-in framework allows Eclipse to work with typesetting languages like LaTeX, networking applications such as telnet, and database management systems. The plug-in architecture s writing any desired extension to the environment, such as for configuration management. Java and CVS is provided in the Eclipse SDK. The key to the seamless integration of tools with Eclipse is the plug-in. With the exception of a small run-time kernel, everything in Eclipse is a plug-in. This means that a plug-in you develop integrates with Eclipse in exactly the same way as other plug-ins; in this respect, all features are created equal. The Eclipse SDK includes the Eclipse Java Development Tools, offering an IDE with a builtin incremental Java compiler and a full model of the Java source files. This allows for advanced refactoring techniques and code analysis. The IDE also makes use of a workspace, in this case a set of metadata over a flat file space allowing external file modifications as long as the corresponding workspace "resource" is refreshed afterwards. The Visual Editor project allows interfaces to be created interactively, hence allowing Eclipse to be used as a RAD tool.

Page 70 of 97


The following is a list of notable projects and plug-in for the Eclipse IDE. These projects are maintained by the Eclipse community and hosted by the Eclipse Foundation. Core projects: Rich Client Platform (Platform) is the core framework that all other Eclipse projects are built on. Java Development Tools (JDT) provides for core Java SE. This includes a standalone fast incremental compiler.

1. Tools projects: C/C++ Development Tools (CDT) adds for C/C++ syntax highlighting, code formatting, and debugger integration and project structures. Unlike the JDT project, the CDT project does not add a compiler and relies on an external tool chain. Graphical Editing Framework (GEF) allows developers to build standalone graphical tools. Example use includes circuit diagram design tools, activity diagram editors and WYSIWYG document editors. 2. Web projects: J2EE Standard Tools (JST) extends the core JDT to include for Java EE projects. Web Standard Tools (WST) adds standards compliant web development tools. These tools include editors for XML, HTML and CSS.

Page 71 of 97


3. Modeling projects: Eclipse Modeling Framework (EMF) a modeling framework and code generation facility for building tools and other applications based on a structured data model, from a model specification described in XMI. Graphical Modeling Framework (GMF) is a generative component and runtime infrastructure for developing graphical editors based on EMF and GEF.

4. Other projects: Test and Performance Tools Platform (TPTP) which provides a platform that allows software developers to build test and performance tools, such as debuggers, profilers and benchmarking applications. Business Intelligence and Reporting Tools Project (BIRT), an Eclipse-based open source reporting system for web applications, especially those based on Java EE.

Web Server/Application Server: An application server is a software engine that delivers applications to client computers or devices, typically through the Internet and using the Hypertext Transfer Protocol. Application servers are distinguished from web servers by the extensive use of serverside dynamic content and frequent integration with database engines. Page 72 of 97


Common features: Application server products typically bundle middleware to enable applications to intercommunicate with dependent applications, like web servers, database management systems, and chart programs. Some application servers also provide an API, making them operating system independent. Portals are a common application server mechanism by which a single point of entry is provided to multiple devices.

Java application servers:

Page 73 of 97


SYSTEM TESTING

Testing: •

The process of executing a system with the intent of finding an error.

•

Testing is defined as the process in which defects are identified, isolated, subjected for rectification and ensured that product is defect free in order to produce the quality product and hence customer satisfaction.

•

Quality is defined as justification of the requirements deviation from the requirements

Defect is nothing but

Defect is nothing but bug.

•

Testing --- The presence of bugs

•

Testing can demonstrate the presence of bugs, but not their absence

Debugging and

Testing are not the same thing! •

Testing is a systematic attempt to break a program or the AUT

Debugging is the art or method of uncovering why the script /program did not execute properly.

Page 74 of 97


Types: •

Black box Testing: is the testing process in which tester can perform testing on an application without having any internal structural knowledge of application.

Usually Test Engineers are involved in the black box testing. There are two types of black box testing approaches, 1.Equievalant classs partitions 2.Boundary value analysis •

White box Testing: is the testing process in which tester can perform testing on an application with having internal structural knowledge.

Usually The Developers are involved in white box testing. •

Gray Box Testing: is the process in which the combination of black box and white box tonics’ are used.

Page 75 of 97


Levels of Testing:

Module1

Module2

Unit

Unit

Unit

s

s

s

i/p

Integration o/p i/p

Module3

Integration o/p

System Testing: Presentation + business +Databases

STLC (SOFTWARE TESTING LIFE CYCLE)

Page 76 of 97


Test Planning: 1. Test Plan is defined as a strategic document which describes the procedure how to perform various testing on the total application in the most efficient way. 2. This document involves the scope of testing, 3. Objective of testing, 4. Areas that need to be tested, 5. Areas that should not be tested 6. Scheduling Resource Planning, 7. Areas to be automated, various testing tools Used. 1. Test case Development (check list) 2. Test Procedure preparation. (Description of the Test cases). 3. Implementation of test cases. Observing the result. Result Analysis: 1. Expected value: is nothing but expected behavior Of application. 2. Actual value: is nothing but actual behavior of application Bug Tracing: Collect all the failed cases, prepare documents. Reporting : Prepare document (status of the application)

Page 77 of 97




Smoke Testing: is the process of initial testing in which tester looks for the availability of all the functionality of the application in order to perform detailed testing on them. (Main check is for available forms)



Sanity Testing: is a type of testing that is conducted on an application initially to check for the proper behavior of an application that is to check all the functionality are available before the detailed testing is conducted by on them.

Regression Testing: is one of the best and important testing. Regression testing is the process in which the functionality, which is already tested before, is once again tested whenever some new change is added in order to check whether the existing functionality remains same. 

Re-Testing: is the process in which testing is performed on some functionality which is already tested before to make sure that the defects are reproducible and to rule out the environments issues if at all any defects are there.



Static Testing: is the testing, which is performed on an application when it is not been executed.ex: GUI, Document Testing



Dynamic Testing: is the testing which is performed on an application when it is being executed.ex: Functional testing.



Alpha Testing: it is a type of acceptance testing, which is conducted on an application when it is just before released to the customer.



Beta-Testing: it is a type of UAT that is conducted on an application when it is released to the customer, when deployed in to the real time environment and being accessed by the real time s.



Monkey Testing: is the process in which abnormal operations, beyond capacity operations are done on the application to check the stability of it in spite of the s abnormal behavior. Page 78 of 97




Compatibility testing: it is the testing process in which usually the products are tested on the environments with different combinations of databases (application servers, browsers…etc) In order to check how far the product is compatible with all these environments platform combination.



Installation Testing: it is the process of testing in which the tester try to install or try to deploy the module into the corresponding environment by following the guidelines produced in the deployment document and check whether the installation is successful or not.

Adhoc Testing: Adhoc Testing is the process of testing in which unlike the

formal

testing where in test case document is used, with out that test case document testing can be done of an application, to cover that testing of the future which are not covered in that test case document. Also it is intended to perform GUI testing which may involve the cosmotic issues. Test Case Document Contains •

Test Scope (or) Test objective

•

Test Scenario

•

Test Procedure

•

Test case

This is the sample test case document for the details of Blazon Agency project: Test scope: • Test coverage is provided for the screen ― check‖ form of a istration module of Blazon Agency application •

Areas of the application to be tested

Page 79 of 97


Test Scenario: •

When the office personals use this screen for the payment, tariff and company registration and web ments on basis of requirements and quit the form.

Test Procedure: The procedure for testing this screen is planned in such a way that the data entry, status calculation functionality, saving and quitting operations are tested in of GUI testing, Positive testing, Negative testing using the corresponding GUI test cases, Positive test cases, Negative test cases respectively

Test cases: T.C.No

Description

Exp

Act

Result

1

With

Home page

Home page

ok

name and

Page 80 of 97


Guidelines for Test Cases: 1. GUI Test Cases:

•

Total no of features that need to be check

•

Look & Feel

Look for Default values if at all any (date & Time, if at all any require)

Look for spell

check Example Of GUI Test Cases:

T.C.No

1

Description

Expected value

Actual value

Check for all the

The scree must contain all the features

n

features in the screen

Check for the alignment of 2

the objects as per the

The alignment should be proper way

validations

n

Page 81 of 97


Result

2. Positive Test Cases: • The positive flow of the functionality must be considered •

Valid inputs must be used for testing

Must have the positive perception to whether the requirements are justified. Example Of Positive Test Cases: T.C.No

Description

Expected value

Actual value

Result

1

as Patient but trying to access doctors pages

Never allow to access the page.

Redirect to patient home page

Redirect to patient home page

Nagative Test Cases: •

Must have negative perception.

•

Invalid inputs must be used for test.

Example for Negative Test cases: T.C.No

Description 1

Expected value

Try to modify The

Modification

information in

Should not be allow

date and time

Actual value

Result

Page 82 of 97


Output Screen: Home Page-

Page 83 of 97


Page 84 of 97


Us

Page 85 of 97


Our Mission:-

Page 86 of 97


:-

Page 87 of 97


Registration:-

Page 88 of 97


Doctor Prescription:

Page 89 of 97


Doctor Case :

Page 90 of 97


Book Appointment:

Page 91 of 97


Assign Doctor:

Page 92 of 97


Patient :

Page 93 of 97


FUTURE ENHANCEMENTS

It is possible to develop a system that makes all the requirements of the . requirements keep changing as the system is being used. Some of the future enhancements that can be done to this system for better use of the system: •

As the technology emerges, it is possible to upgrade the system and can be adaptable to desired environment.

•

Because it is based on object-oriented design, any further changes can be easily adaptable.

Based on the future security issues, security can be improved using emerging technologies. The payments gateway must be added to the system.

Page 94 of 97


CONCLUSION

This application software has been computed successfully and was also tested successfully by taking ―test cases‖. It is friendly, and has required options, which can be utilized by the to perform the desired operations. The software is developed using Java as front end and Oracle as back end in Windows environment. The goals that are achieved by the software are:  Optimum utilization of resources.  Efficient management of records.  Simplification of the operations.  Less processing time and getting required information.  friendly.  Portable and flexible for further enhancement.

Page 95 of 97


12. BIBLIOGRAPHY Core Java™ 2 Volume I – Fundamentals 7th Edition

Cay S. Hortsman

Pearson Education – Sun Microsystems

Gary Cornell

Core Java™ 2 Volume II – Advanced

Cay S. Hortsman

Pearson Education – Sun Microsystems

Gary Cornell

Head First Servlets & JSP

Eric Freeman

Effective Java – Programming Language Guide

Joshua Bloch

Java Database Best Practices

George Reese

O’Reilly – SPD

Sam Griffith

Page 96 of 97


Virtual Medical Home 4332c

Overview 6h3y3j

More details h6z72

Related Documents 543cg

Virtual Medical Home 4332c

Forms Non Medical Home Care Forms 464q5p

Virtual 655r1b

Home 2i5t12

Campus Virtual Usat Campus Virtual Usatcampus Virtual Usatcampus Virtual Usat 5io4t

Home 2i5t12

More Documents from "Sudipta Dhara" 2o411r

Lan.ppt u522z

Middleware Ppt 1o332n

Virtual Medical Home 4332c

Surface Area To Volume Ratio 4p4423

Requirements For Photosynthesis m4c68

6 Sop Pengawasan Dan Pembinaan Ttu.docx 3ft2p