E-care Help Desk System Java Project 2z55k

TABLE OF CONTENTS S.NO.

CONTENTS

1. Abstract 2. Introduction Organization Profile 3. System Analysis Existing system Problem Definition Proposed System Requirement Analysis Requirement Specifications Feasibility study 4. System Design 4.1

Project Modules

4.2

Data Dictionary

4.3

Data Flow Diagrams

4.4

E-R Diagrams

4.5

Hardware And Software Requirements

5. System Testing 6. Software Tools Used 7

Technical Notes 7.1

Introduction To Real-time programming

7.2

Introduction to OOPS and Windows

7.3

Introduction to Java

8.

Conclusion

9.

Bibliography

PAGE NO.

1. Abstract E-care is customer care management system. E-care is called as E-desk or Help Desk System. It is so called as Help Desk System because it tries to solve all the HD (helpdesk) problems, which are coming from the s of E-care. E-care will take care of every request coming from their s and try to solve and produce the solution of the particular request. E-care also will store the responses for the future use. E-care contains six main who play very important role in this Help Desk System. They include super , level1 , level2 , level3 , corporate client and corporate (or end-). Super is the chief head of the organization that assigns first level, second level, and third level s. The super is responsible for all the three level s including the corporate clients. The Super is the sole person who is responsible for creating categories, modules and the team. Super creates new categories only if HD problems don’t belong to those categories present in E-care and similarly with the creation of modules. When the super creates new categories and modules he will label these categories and modules as levels and appoint one for each of them. When the super gets the HD problem as request he can modify the request or can answer it by sending solution to the level3 or the team who is responsible for messaging the response or the solution to the end (corporate ).

Corporate client is the one who buys E-care product for his business purpose. He can create corporate s for his product. Corporate is the one who has to himself to the corporate client before he submits the HD problems to the super and corporate is the actual end- of the product or service. Corporate will to the corporate client and corporate client sends all the registration details to the super , and after the registration the end- will submit the HD problems to the super . When the super gets the HD problems he will check the details of the end- and send the responses to the team who will message the responses to the corporate s. E-care is very useful for the corporate clients who want their business to extend world wide i.e., by keeping and good relation with the corporate s who buy their products. The corporate clients who buy E-care for their business can know what are the various problems of their product which are coming from their s so that they improve their products to the needs. Any who knows a little about of the computer can handle e-care.

Introduction Organization profile

3.SYSTEM ANALYSIS System Analysis is first stage according to System Development Life Cycle model. This System Analysis is a process that starts with the analyst. Analysis is a detailed study of the various operations performed by a system and their relationships within and outside the system. One aspect of analysis is defining the boundaries of the system and determining whether or not a candidate should consider other related systems. During analysis, data is collected from the available files, decision points, and transactions handled by the present system. Logical system models and tools are used in analysis. Training, experience, and common sense are required for collection of the information needed to do the analysis.

3.1 Existing System This project mainly deals with automating the task of the Ecare system that helps many end-s to know the solutions for their request

within no time. E-care can be done manually but there may be problems that have to be faced so to overcome such problems we need to automate the Help Desk System. If the system is maintaining the list of all the details of corporate s and corporate clients manually it will take a lot of time to retrieve even single information such as retrieving or deleting single information becomes very difficult task. The updations for the list such as creating a new creating new end- details or creating new corporate client details and including the details of the categories and the modules that are created newly by the super becomes very difficult manually. Once all information is provided manually it become quit difficult for updating the records with new information manually, so we automate the system to overcome all such difficulties. E-care, which is developed manually, is the existing system. This system generates and delivers the services to the ends, which depends on the response provided by the team who actually message the responses to the corporate s for their requests. By manually the Help Desk System will face difficulties while updations and it is time consuming and leads more errors. E-care automates the tedious job of maintaining the corporate details or corporate client details and manages the updations and see that the responses are sent to the corporate as soon as possible. It includes main like:  Super  Corporate client  Corporate  Level1  Level2

 Level3 or team. Super will manage the entire organization that includes corporate clients, corporate s, and level s and also he can create the new categories and also modules.

3.2 Problem Statement This project mainly deals with automating the task of the E-care system that helps many end-s to know the solutions for their request within no time. E-care can be done manually but there may be problems that have to be faced so to overcome such problems We need to automate the Help Desk System. If the system is maintaining the list of all the details of corporate s and corporate clients manually it will take a lot of time to retrieve even single information such as retrieving or deleting single information becomes very difficult task. The updations for the list such as creating a new creating new end- details or creating new corporate client details and including the details of the categories and the modules that are created newly by the super becomes very difficult manually. Once all information is provided manually it become quit difficult for updating the records with new information manually, so we automate the system to overcome all such difficulties. E-care, which is developed manually, is the existing system. This system generates and delivers the services to the end-s, which depends on the response provided by the team who actually message the responses to the corporate s for their requests.

By manually the Help Desk System will face difficulties while updations and it is time consuming and leads more errors. E-care automates the tedious job of maintaining the corporate details or corporate client details and manages the updations and see that the responses are sent to the corporate as soon as possible. It includes main like:  Super  Corporate client  Corporate  Level1  Level2  Level3 or team. Super will manage the entire organization that includes corporate clients, corporate s, and level s and also he can create the new categories and also the modules. Proposed systems are those that are automated, so that it is easy to retrieve the responses from the system fastly and updating the details once the response or services are provided to the end-s upon their request without any difficulty and saves time.

3.3 Proposed System Proposed system are those that are automated, so that it is easy to retrieve the responses from the system fastly and updating the details once the response or services are provided to the end-s upon their request without any difficulty and saves time.

3.4 REQURIEMENTS ANALYSIS The requirement phase basically consists of three activities: 1.Requirement Analysis 2.Requirement Specification 3.Requirement Validation Requirement Analysis: Requirement Analysis is a software engineering task that bridges the gap between system level software allocation and software design. It provides the system engineer to specify software function and performance, indicate software’s interface with the other system elements and establish constraints that software must meet. The basic aim of this stage is to obtain a clear picture of the needs and requirements of the end- and also the organization. Analysis involves interaction between the clients and the analysis. Usually analysts research a problem from any questions asked and reading existing documents. The analysts have to uncover the real needs of the even if they don’t know them clearly. During analysis it is essential that a complete and

consistent set of specifications emerge for the system. Here it is essential to resolve the contradictions that could emerge from information got from various parties. This is essential to ensure that the final specifications are consistent. It may be divided into 5 areas of effort. 1. Problem recognition 2.Evaluation and synthesis 3.Modeling 4.Specification Review Each Requirement analysis method has a unique point of view. However all analysis methods are related by a set of operational principles. They are: 1.The information domain of the problem must be represented and understood. 2.The functions that the software is to perform must be defined. 2.The behavior of the software as a consequence of external events must be defined. 4.The models that depict information, function and behavior must be partitioned in a hierarchical or layered fashion. 5.The analysis process must move from essential information to implementation detail.

3.5 REQUIREMENT SPECIFICATION Specification Principles: Software Requirements Specification plays an important role in creating quality software solutions. Specification is basically a representation process. Requirements are represented in a manner that ultimately leads to successful software implementation. Requirements may be specified in a variety of ways. However there are some guidelines worth following: •

Representation format and content should be relevant to the problem

•

Information contained within the specification should be nested

•

Diagrams and other notational forms should be restricted in number and consistent in use.

•

Representations should be revisable.

Software Requirements Specifications: The software requirements specification is produced at the culmination of the analysis task. The function and performance allocated to the software as a part of system engineering are refined by establishing a complete information description, a detailed functional and behavioral description, and indication of performance requirements and design constraints, appropriate validation criteria and other data pertinent to requirements. An outline of the Software Requirements Specification: A simplified outline can be given for the framework of the specifications. This is according to the IEEE Standards.

3.6 FEASIBILITY STUDY

All projects are feasible, given unlimited resources and infinite time. But the development of software is plagued by the scarcity of resources and difficult delivery rates. It is both necessary and prudent to evaluate the feasibility of a project at the earliest possible time. Three key considerations are involved in the feasibility analysis. Economic Feasibility: This procedure is to determine the benefits and savings that are expected from a candidate system and compare them with costs. If benefits outweigh costs, then the decision is made to design and implement the system. Otherwise, further justification or alterations in proposed system will have to be made if it is to have a chance of being approved. This is an ongoing effort that improves in accuracy at each phase of the system life cycle. Technical Feasibility: Technical feasibility centers on the existing computer system (hardware, software, etc.,) and to what extent it can the proposed addition. If the budget is a serious constraint, then the project is judged not feasible. Operational Feasibility: People are inherently resistant to change, and computers have been known to facilitate change. It is understandable that the introduction of a candidate system requires special effort to educate, sell, and train the staff on new ways of conducting business.

FEASIBILITY STUDY IN THIS PROJECT Technical Feasibility E-Care is the product that is designed mainly on Java. The main reason behind choosing the Java environment is that, as the s. In order to post the queries to related Organization always require Input screen which usually provides services all around the time. Such environment that always gives instant reply to the s should input screen. These requirements are satisfied by Java, as it is multi platform environment s webBrowser where as other languages lack these features. In order to continuously communicate he/she needs a reliable protocol i.e., is T/IP protocol. This protocol frequently transfers messages between client and . Communication Standards such as HTTP is used .An HTTP is a client/server interaction consists of a single request/reply interchange, it -friendly environment. Economic Feasibility As E-care is help desk system which provides continuous communication to s at the front end ,provides solutions to different queries to various different problems as get from the use of different product. And the solutions for their queries are sent to them by messaging to their sites within the expiry time or the time mentioned i.e., within 12hrs or 24hrs. Operational Feasibility Operations done in the E-care are very fast and are able to succeed in sending the responses very fastly. Updations are done very quickly that the modified data is stored in the database in no time. E-care s up to five hundred simultaneously s against the central database at any given time. E-care must be able to complete 80% of all transactions within two minutes.

SYSTEM DESIGN The most creative and challenging phase of the life cycle is system design. The term design describes a final system and the process by which it is developed. It refers to the technical specifications that will be applied in implementations of the candidate system. The design may be defined as “the process of applying various techniques and principles for the purpose of defining a device, a process or a system with sufficient details to permit its physical realization”. The designer’s goal is how the output is to be produced and in what format. Samples of the output and input are also presented. Second input data and database files have to be designed to meet the requirements of the proposed output. The processing phases are handled through the program Construction and Testing. Finally, details related to justification of the system and an estimate of the impact of the candidate system on the and the organization are documented and evaluated by management as a step toward implementation. The importance of software design can be stated in a single word “Quality”. Design provides us with representations of software that can be assessed for quality. Design is the only way where we can accurately translate a customer’s requirements into a complete software product or system. Without design we risk building an unstable system, that might fail if small changes are made. It may as well be difficult to test, or could be one who’s quality can’t be tested. So it is an essential phase in the development of a software product.

4.1 PROJECT MODULES E-Care [help desk system] is a customer care management system. The following are the modules related to E-Care [help desk system] are as follows:  module  Super module  istration module Module In this module can themselves to the e-Care if they are new s, otherwise they can directly and can then post their queries to e-Care or e-desk. First has to with corporate client. In order to send request the end- has to and the details are stored in the database maintained by e-Care system. Database checks the details of the , if he is valid then allows the to access the help desk system.

Super module In this module Super is the chief head of the Organization who assigns 1st level and 3rd level s. The super is responsible for all the three levels s including the corporate clients. The super is the sole person who is responsible for creating categories, modules and team. Super will take all the registration details of the Corporate s so as to check with the queries which in turn consist of the query and also the id.

Super has the right to remove any level or add any level and also responsible for creating modules and categories . istration module Depending upon categories and modules created by super the three levels are allotted. They are three types of : Level 1 : the first level is the one who can add HD problems to a category created by the super . Level 2 s: The second level is the one who can add HD problems to the modules. Level 3 s: The third level is a member of the team who provides services to the Corporate clients and corporate s. Corporate Client : A corporate client is the one who buys e-desk products. He can create corporate s for his product. Corporate : Corporate is the one who s himself with the corporate client and who is the actual end- of the product/service. The product features are as follows:  Create & maintain levels  Create & maintain categories  Create & maintain s  Create sub category  Create team

 Assign 1st level to a category  Assign 2nd level to a sub category  Assign 3rd level to team  Create corporate client  Activate or inactivate all e-desk  Check for HD problems submissions  Check solutions in repository  Scheduling of tasks.

4.2 DICTIONARY The logical characteristics of current systems data stores, including name, description, aliases, contents, and organization, identifies processes where the data are used and where immediate access to information required, Serves as the basis for identifying database requirements during system design. Uses of Data Dictionary: 1. To manage the details in large systems. 2. To communicate a common meaning for all system elements. 3. To Document the features of the system. 4. To facilitate analysis of the details in order to evaluate characteristics and determine where system changes should be made. 5. To locate errors and omissions in the system. E-care consists of various tables like super , eloign, registration, hdlevels, categories,

modules,

team,

hdemp,

schedules,

hdproblemrequest,

superprofile, forward, problemhistory, messages etc. NOTE: Primary key is denoted by “* “ for all the database tables. SUPER

SNO 1* 2

FIELD NAME NAME

TYPE VARCHAR2(30) VARCHAR2(30)



SNO 1* 2

FIELD NAME NAME

TYPE VARCHAR2(30) VARCHAR2(30) HD Levels

SNO 1 2*

FIELD NAME LEVELNAME LEVELCODE

TYPE VARCHAR2(30) VARCHAR2(30)

HD CATEGORIES SNO 2* 3

FIELD NAME CATEGORYNAME CATEGORYCODE STATUS

TYPE VARCHAR2(30) VARCHAR2(30) VARCHAR2(30)

HD MODULES SNO 1* 2* 3 4

FIELD NAME MODULECODE CATEGORYCODE CATEGORYNAME STATUS

TYPE VARCHAR2(30) VARCHAR2(30) VARCHAR2(30) VARCHAR2(30)

TEAM

SNO 1*

FIELD NAME CODE

TYPE VARCHAR2(30)

2 3 4

MODULECODE CATEGORYCODE TEAM NAME

VARCHAR2(30) VARCHAR2(30) VARCHAR2(30)

SCHEDULES SNO 1* 2

FIELD NAME TICKET SCHEDULEDATE

TYPE NUMBER VARCHAR2(30)

REGISTRATION SNO 1 2 3 4 5 6 7 8 9 10 11 12* 13 14 15 16

FIELD NAME FIRSTNAME LASTNAME ADDRESS PHONENO CITY STATE COUNTRY GENDER ZIPCODE EMAILID CTYPE ID CONFORMATION HINTQUESTION HINTANSWER

TYPE VARCHAR2(30) VARCHAR2(30) VARCHAR2(30) NUMBER VARCHAR2(30) VARCHAR2(30) VARCHAR2(30) VARCHAR2(30) NUMBER VARCHAR2(30) VARCHAR2(30) VARCHAR2(30) VARCHAR2(30) VARCHAR2(30) VARCHAR2(30) VARCHAR2(30)

FORWARD SNO 1* 2 3 4

FIELD NAME TICKET FROM NAME TO NAME STATUS

TYPE NUMBER VARCHAR2(30) VARCHAR2(30) VARCHAR2(30)

SUPER PROFILE SNO 1 2 3 4 5 6 7 8 9 10 11* 12 13 14 15

FIELD NAME FIRSTNAME LASTNAME ADDRESS PHONENO CITY STATE COUNTRY GENDER ZIPCODE EMAILID ID CONFORMATION HINTQUESTION HINTANSWER

TYPE VARCHAR2(30) VARCHAR2(30) VARCHAR2(30) NUMBER VARCHAR2(30) VARCHAR2(30) VARCHAR2(30) VARCHAR2(30) NUMBER VARCHAR2(30) VARCHAR2(30) VARCHAR2(30) VARCHAR2(30) VARCHAR2(30) VARCHAR2(30)

HD EMPLOYEE SNO 1 2* 3 4 5 6 7 8 9 10

FIELD NAME LEVELNAME ID EMPLOYEENAME ADDRESS CITY STATE COUNTRY ZIPCODE PHONENUMBER EMAILID

TYPE VARCHAR2(30) VARCHAR2(30) VARCHAR2(30) VARCHAR2(30) VARCHAR2(30) VARCHAR2(30) VARCHAR2(30) NUMBER NUMBER VARCHAR2(30)

HD PROBLEMREQUEST SNO 1* 2* 3* 4 5 6* 7

FIELD NAME TICKET CATEGORYCODE MODULECODE PROBLEMDESCRIPTION LASTSOLUTION ID PROBLEM REPORT DATE

TYPE NUMBER VARCHAR2(30) VARCHAR2(30) VARCHAR2(30) VARCHAR2(30) VARCHAR2(30) VARCHAR2(30)

MESSAGES SNO 1 2 3 4 5

FIELDNAME FROM NAME TO NAME SUBJECT MESSAGE SENT DATE

TYPE VARCHAR2(30) VARCHAR2(30) VARCHAR2(30) VARCHAR2(30) VARCHAR2(30)

PROBLEM HISTORY SNO 1* 2 3 4 5 6 7

FIELDNAME TICKET PROBLEM DATE PROBLEM DESCRIPTION SOLUTION SOLUTIONBY SOLUTIONDATE STATUS

TYPE NUMBER VARCHAR2(30) VARCHAR2(30) VARCHAR2(30) VARCHAR2(30) VARCHAR2(30) VARCHAR2(30)

ENTITY-RELATIONSHIP Diagrams E-R (Entity-Relationship) Diagram is used to represents the relationship between entities in the table. The symbols used in E-R diagrams are: SYMBOL

PURPOSE Represents Entity sets. Represent attributes.

Represent Relationship Sets.

Structured analysis is a set of tools and techniques that the analyst. To develop a new kind of a system: The traditional approach focuses on the cost benefit and feasibility analysis, Project management, and hardware and software selection an personal considerations.

The tools for structured analysis are: 1. Data Flow Diagrams. 2. E-R Diagrams.

E-R DIAGRAMS OF e-Care

IdC idId

IdU

IdU idId



idId

nam e





Company name

nam e

s as customer

Corporate client

s

IdC idId

Ticketno

IdU

Super Categor y name

idId Module name

IdS idId

Flow for Posting Query IdU



IdU

nam e

idId

Ticket no

nam e

idId

Post quer y



IdS idId

Super

Module name

Query_des

Ticket no QUERYDETAILS

IdC idId Team name



Query date

Description of query

Categor y name

Flow for forwarding the query to the levels Id C Module name

Id U

Ticket no

Id S Categorisation And modularize And messaging the solution

Super

Category name levelid

Levelname

HD LevelS



So lu tio ns

DATAFLOW DIAGRAMS(DFD) The data flow diagram is used for classifying system requirements to major transformation that will become programs in system design. This is starting point of the design phase that functionally decomposes the required specifications down to the lower level of details. It consists of a series of bubbles ed together by lines. Bubbles: Represent the data transformations. Lines: Represents the logic flow of data. Data can trigger events and can be processed to useful information. System analysis recognizes the central goal of data in organizations. This dataflow analysis tells a great deal about organization objectives are accomplished. Dataflow analysis studies the use of data in each activity. It documents this finding in DFD’s. Dataflow analysis give the activities of a system from the viewpoint of data where it originates how they are used or hanged or where they go, including the stops along the way from their destination. The components of dataflow strategy span both requirements determination and system’s design. The first part is called dataflow analysis. As the name suggests, we didn’t use the dataflow analysis tools exclusively for the analysis stage but also in the deg phase with documentation.

NOTATIONS USED IN DATA FLOW DIAGRAMS

The logic dataflow diagrams can be drawn using only four simple notations i.e., special symbols or icons and the annotation that associates them with a specific system. Since the choice of notation we follow, does not affect impede or catalyze the system process; we used three symbols from YOURDON notation and one from Gain and Sarson notation as specified below. Element References

symbols

Data Flow Process Process Data Store

Source or Sink Description: Process: describes how input data is converted to output Data Data Store: Describes the repositories of data in a system Data Flow: Describes the data flowing between process, Data stores and external entities. Sources: An external entity causing the origin of data. Sink: An external entity, which consumes the data.

Context Diagram:

The top-level diagram is often called a “context diagram”.

It

contains a single process, but it plays a very important role in studying the current system. The context diagram defines the system that will be studied in the sense that it determines the boundaries. Anything that is not inside the process identified in the context diagram will not be part of the system study. It represents the entire software element as a single bubble with input and output data indicated by incoming and outgoing arrows respectively. Types of data flow diagrams DFDs are two types 1. Physical DFD Structured analysis states that the current system should be first understand correctly. The physical DFD is the model of the current system and is used to ensure that the current system has been clearly understood. Physical DFDs shows actual devices, departments, people etc., involved in the current system 1.

Logical DFD Logical DFDs are the model of the proposed system. They clearly should show the requirements on which the new system should be built. Later during design activity this is taken as the basis for drawing the system’s structure charts.

DataFlow Diagrams

ZeroLevel



Id,&query

E-care

Resposes of Queries



Context Level

Id, &query

first level

Responses E-care of Queries



2.0 Client process

database details Update Client_id Pwd

,id

solvedquery 1.0

Invalid

3.0

Super

process

process

id

4.0 Corporate process

Second Level 2



2.0 client process

Details Query No

Company Details 2.3 2.2

2.1

Company profile

Add, or Delete Query

add/del/ modify s Update

3.1

3.0

Update Query 3.4

Super 3.0 Update Profile

Update Process Status

create/del/m odify levels

Process details 3.2

3.5

Query status

modify company profile

istration Database

3.6 add/delete client details Second Level 3.0

Level data Level details Query

Query Details Details

3.2 query status

3.2.1

No

3.2.4

Client

Create 1st Level

3.2.5 create 2nd Level

Client details

1st Level 3.2.3 3rd level stration

Database 3.3 Messaging system

Third level 3.2 3.2.2 2nd level strator

database istration

new category

module

category

Unsolved Query, Category Name

resolved details module name

4.5 HARDWARE AND SOFTWARE REQUIREMENTS

Hard ware Specification:

Processor

:

Intel P-III based system

Processor Speed

:

250 MHz to 833MHz

RAM

:

64MB to 256MB

Hard Disk

:

2GB to 30GB

Key Board

:

104 keys

Language

:

JDK 1.2

Database

:

SQL

Operating System

:

WindowsNT/95/98/2000

Software Specification:

LIFE CYCLE MODELS The stage of planning and development process involves defining, developing, testing, delivering, operating, and maintaining a software product. Different lifecycle models emphasize different aspects and no single lifecycle model is suitable for all software products. A lifecycle model that is understood and accepted improves project communication and enhances project manageability, resource allocation, cost control, and product quality. The Phased Life Cycle Model The phased lifecycle model represents software lifecycle as a series of successive activities. This phase requires well-defined input information, processes and results in well-defined products. The phased lifecycle model consists of following phases. Analysis, Design, Implementation, System Testing and Maintenance This model is sometimes called the Waterfall Model, the products cascade from one level to another in smooth progression. Analysis

Design

Implementation

System

Maintenance

Testing Planning, needs

Design

Definition

Details Code,

debug

and Test Integration & Acceptance Enhance, Adapt The Analysis Stage consists of Planning and Requirements definition.

Fix

A feasibility study, developing a recommended solution strategy, determining the acceptance criteria and planning development process. The products of planning are a System definition and a project plan. The Software Design follows analysis. Design is concerned with its software components, specifying relationships among components specifying some structure, maintaining a record of design decisions and providing blueprint implementation phase. Design consists of detailed design and Architectural design. The implementation phase of software development involves translation of design specification into source code, and debugging, documenting and unit testing the source code. To enhance the quality of the software the methods are structured control constructs, built in and defined data types, secure type checking, flexible scope rules exception handling mechanism, concurrency constructs and separates compilation modules. System Testing involves two kinds of testing integration testing and acceptance testing. Developing a strategy for integrating the components of a software system into a functioning requires careful planning so that modules are available for integration when needed. Acceptance testing involves planning and execution of various tests in order to demonstrate that the implemented system satisfies the requirement document. The Maintenance phase comes after the acceptance of the product by the customer and release of the system for production work.

Maintenance activities include

enhancements of capabilities, adaptation of software to new processing environments, and correction of software bugs.This project follows the Phased Life Cycle Model or the Water Fall model to a large extent. The analysis stage consisted of listening to the needs and requirements of the examination department obtaining the required format of the system as desired by them, taking the required data to be stored for future use etc., In the design stage the structure of the system was designed and all the required

screens were formatted. This was then shown to the officer’s approval and the system was built. Implementation phase was done at PRITHVI INFORMATICS as they provided a computer with all the required software and with required configuration. The coding and debugging was done. Even after this stage certain changes were made as requested by the guide. The testing was done to check for any errors or bugs or unwanted behavior in the system. Individual modules as well as the whole system were tested separately.

SOFTWARE TESTING

Software Testing is a critical element of software quality assurance and represents the ultimate review of specification, design and coding, Testing presents an interesting anomaly for the software engineer. Testing Objectives include: 1. Testing is a process of executing a program with the intent of finding an error 2. A good test case is one that has a probability of finding an as yet undiscovered error 3. A successful test is one that uncovers an undiscovered error

Testing Principles: •

All tests should be traceable to end requirements

•

Tests should be planned long before testing begins

•

Testing should begin on a small scale and progress towards testing in large

•

Exhaustive testing is not possible

•

To be most effective testing should be conducted by a independent third party

TESTING STRATEGIES

A Strategy for software testing integrates software test cases into a series of well planned steps that result in the successful construction of software. Software testing is a broader topic for what is referred to as Verification and Validation. Verification refers to the set of activities that ensure that the software correctly implements a specific function. Validation refers he set of activities that ensure that the software that has been built is traceable to customer’s requirements Unit Testing: Unit testing focuses verification effort on the smallest unit of software design that is the module. Using procedural design description as a guide, important control paths are tested to uncover errors within the boundaries of the module. The unit test is normally white box testing oriented and the step can be conducted in parallel for multiple modules. Integration Testing: Integration testing is a systematic technique for constructing the program structure, while conducting test to uncover errors associated with the interface. The objective is to take unit tested methods and build a program structure that has been dictated by design. Top-down Integration: Top down integrations is an incremental approach for construction of program structure. Modules are integrated by moving downward through the control hierarchy, beginning with the main control program. Modules subordinate to the main program are incorporated in the structure either in the breath-first or depth-first manner.

Bottom-up Integration:

This method as the name suggests, begins construction and testing with atomic modules i.e., modules at the lowest level. Because the modules are integrated in the bottom up manner the processing required for the modules subordinate to a given level is always available and the need for stubs is eliminated. Validation Testing: At the end of integration testing software is completely assembled as a package. Validation testing is the next stage, which can be defined as successful when the software functions in the manner reasonably expected by the customer. Reasonable expectations are those defined in the software requirements specifications. Information contained in those sections form a basis for validation testing approach. System Testing: System testing is actually a series of different tests whose primary purpose is to fully exercise the computer-based system. Although each test has a different purpose, all work to that all system elements have been properly integrated to perform allocated functions. Security Testing: Attempts to the protection mechanisms built into the system. Performance Testing: This method is designed to test runtime performance of software within the context of an integrated system.

IMPLEMENTATION

ABOUT JAVA: The Internet helped catapult Java to the forefront of programming, and Java, in turn, has had a profound effect on the Internet. The reason for this is quite simple: Java expands the universe of objects that can move about freely in the cyberspace. In a network, two very broad categories of objects are transmitted between the server and our computer ive information and dynamic, active programs. As desirable as dynamic, networked programs are, they also present serious problems in the areas of security and portability. Java achieves this security or protection by confining a Java program to the Java execution environment and not allowing it to access to other parts of the computer. Many types of the computers and operating systems are in use throughout the world and many are connected to the Internet. For programs to be dynamically to all the various types of platforms connected to the Internet, some means of generating portable executable code is needed. Java was designed to be easy for the professional programmers to learn and use efficiently. The object model of Java is simple and easy to extend, while simple types, such as integers are kept as high-performance non-objects. E-care is implemented using the Java language so as to make the programmers (which includes super , and Levels) and different corporate clients and corporate s to handle e-Care easily without any difficulty. The multiplatformed environment of the web places extraordinarily

demands on a

program, because the program must execute reliably in a variety of systems. Thus, the ability to create robust programs was given a high priority in the design of Java. At the same time, Java frees us from having to worry about many of the most common cause of programming errors. Because Java is strictly typed language, it checks our code at the compile time and also at run-time.

Java was designed to meet the real world requirements of creating interactive, Networked programs. Java s multithreaded programming, which allows us to write programs that do many things simultaneously. A central issue for the Java designers was that of code longevity and portability. Their goal was “write once; run anywhere, any time , forever “. Java enables the creation of the cross-platform programs by compiling into intermediate representation called Javabytecode. This code can be interpreted on any system that provides a java virtual machine. Java is designed for the distributed environment of the Internet, because it handles T/IP protocols. In fact, accessing a resource using a URL is not much different from accessing a file. The original version of Java (OAK) included features for intra-address-space messaging. Java programs carry with them substantial amounts of the run-time type information that is used to and resolve accesses to objects at run-time. This makes it possible to dynamically link code in a safe and expedient manner.

ABOUT INTERNET AND INTRANET

Technologically, the Internet is network of computers. Not just a few special Computers, but over nine million of all kinds of computers. Similarly it is not just a network, but a network of networks hence the name and using T/IP (transmission control protocol and internet protocol). Internet is the name for a vast, worldwide system consisting of people, information and computers. Internet is global communication system of diverse, INTER connected computer NETWORK for the exchange of information of virtually every conceivable topic known to man. Internet is not just one thing. It is a lot of things to lot of people. In today’s world it is one of the most important commodity of life. The Internet is more important in what it enables than what it is, more of a phenomenon than fact. Intranet The classical definition of Intranet is the application of the Internet technologies to the internal business applications media most refer to the Intranet in of applying web technologies to information systems in the organization.

ABOUT JDBC (JAVA DATA BASE CONNECTION)

It is a java data base connectivity having data base as a back-end of java as front end. Database is a collectivity of related data. A data base management system (DBMS) controls the storage or retrieval of data in the database. The main use of this JDBC is the database connectivity. Using drivers we can get connection to the back-end: 1.which drive we are going to connect back-end. 2.create a data source name (dsn). 3.create a statement for connection. The package we use here is import java. Sql. * Interfaces of jdbc include driver, connection, and statement; prepare statement, callable statement, Result Set, Result Set Meta data. Classes of JDBC are driver manages, driver property information, date, time, and timestamp, type. The driver defined by the classJdbc odbc driver in package sun.jdbc.odbc. Class sun.jdbc.odbc.jdbc odbc driver represents the jdbc to odbc bridge driver.

ABOUT SERVLETS Servlet is server side applet. It contains several advantages. They are:

•

Performance is significantly better. Servlets execute within the address space of the web server. Creating a separate process to handle each client request isn’t necessary.

•

Servlets are platform-independent, because they are written in Java. Several web servers, from vendors such as sun, Netscape, and Microsoft, offer the servlet API Programs developed for this API can be moved to any of these environments without recompilation.

•

The java security manager on the server enforces a set of restrictions to protect the resources on a server machine.

•

The full functionality of the Java class libraries is available to a servlet. It can communicate with applets, databases, or other software via the sockets and RMI mechanisms.

The Lifecycle of a servlet: Three methods are central to the lifecycle of a servlet: init (), service( ), and destroy( ). First, assume that a enters a Uniform Resource Locator (URL) to the web browser. The web browser then generates an HTTP request for this URL and sends it to the appropriate server. Second the web server receives this HTTP request. The server maps this request to particular servlet. The servlet is dynamically retrieved and loaded into the address space of the server. Third, the server invokes the init( ) method of the servlet. This method is invoked only when the servlet is first loaded into the memory. Fourth, the server invokes the servlet service( ) method , which is called to process the HTTP request. The service( ) method is called for each HTTP request. Two packages are required to build the servlet they are javax.servlet and javax.srevlet.http. They constitute of servlet API. ServletRequest interface is used to read the data from a client0request and servletResponse is used to write data to the client

response.

The

javax.srevlet.http

package

include

interfaces

like

HttpServletRequest whish enables servlets to read data from HTTP request and HttpServletResponse which enables servlets to write data from HTTP response. Introduction to HTML

The hypertext markup language (HTML) is a simple markup language. Used to create a hypertext documents that are portable from one platform to another HTML documents are SGML (Standard generalized mark up language) documents with generic semantics that are appropriate for representing information from a wide range of applications. This specification defines HTML version 3.2. HTML 3.2 aims to capture recommended practice as of early ’96 and as such a replacement for HTML2.0 (RFC 1866). A set of instructions embedded in a document is called mark up language. These instructions describe what the document text means and how it should look like in a display. Hyper Text Mark Up language (HTML) is the language used to encode World Wide Web documents. WHY TO USE HTML? Website is a collection of pages, publications, and documents that reside on web server. While these pages publications and a document as a formatted in a single format, you should use HTML for home page and all primary pages in the site. This will enable the millions of web s can easily access and to take advantage of your website. HTML is considered first for formatting any new material you plan to publish on the web. HTML documents are platform independent, meaning that they don’t confirm to any standard. If they are created properly you can move home page to any server platform or you can access them with any complaint www browser. STRUCTURE OF HTML HTML elements perform a defined task. HTML uses two types of elements . Empty Tags . Container Tags These tags differ because of what they represent. Empty tags represent formatting constricts such as line breaks and horizontal rules. Container tags define a section of text, formats and dot all of the selected text. A container tag has both a beginning and an ending. HTML LAYOUT:

An HTML document consists of text, which comprises the content of the document and tags, which, defines the structure, and appearance of the document. The structure of an HTML document is simple, consists of outer. tag enclosing the document header and body <TITLE>the title of HTML document This is where the actual HTML documents Text lies, which is displayed in the browser