E-Care

A Mini Project Report By

B. Rohila Raj (08QH1A0541) D. Anusha (08QH1A0504)

P. Uday Kumar (08QH1A0557)

Under the Guidance of

T. Bharat Kumar (Asst. Professor)

Submitted in partial fulfillment for the award of the degree of

BACHELOR OF TECHNOLOGY In COMPUTER SCIENCE AND ENGINEERING

Submitted to

DEPARTMENT OF COMPUTER SCIENCE & ENGINEERING Holy Mary Institute of Technology (AFFILIATED TO JNTU-HYDERABAD, AP) Hyderabad-500090 2011-2012 1

Holy Mary Institute of Technology

(AFFILIATED TO JNTU-HYDERABAD, AP)

CERTIFICATE
This is to certify that B.Rohila Raj(08QH1A0541), D.Anusha(08QH1A0504) and P.Uday Kumar(08QH1A0557) has successfully completed their project work at CSE Department of HIT, Hyderabad entitled E-CARE in partial fulfillment of the requirements for the award of B.Tech degree during the academic year 2011-2012

This work is carried out under my supervision and has not been submitted to any other University/Institute for award of any degree/diploma.

Head of the Department: Mrs. S. Kavitha

Internal Guide:
Mr. T. Bharat Kumar

Declaration

We do, hereby, declare that the dissertation entitled E-CARE is an authentic work developed by me in HIT, Hyderabad, under the guidance of T.Bharat Kumar (Asst.

Professor) and submitted as a partial fulfillment of the degree of B .Tech (CSE.) in

JNTU.

We also declare that, any or all contents incorporated in this dissertation have not been submitted in any form for the award of any degree or diploma of any other institution or university.

B. Rohila Raj (08QH1A0541) D. Anusha (08QH1A0504)

P. Uday Kumar (08QH1A0557)

ACKNOWLEDGEMENT

We wish to take this opportunity to express my deep gratitude to all the people who have extended their cooperation in various ways during my project work. It is my pleasure to acknowledge the help of all those individuals.

We would like to thank my project guide TRYLOGIC for his guidance and help throughout the development of this Project work by providing us with required information. Without his guidance, cooperation and encouragement I couldnt learn many new things during my projects tenure.

We express my profound gratitude to my guide MR.T.BHARATH KUMAR Assistant Professor, Computers Department for his support and encouragement in completing my project.

We would like to thank Mrs.S.KAVITHA Head of Department of Computer Science for her encouragement and valuable guidance in bringing shape to this dissertation.

B.ROHILA RAJ D.ANUSHA P.UDAY KUMAR

ORGANIZATIONAL PROFILE

TRY LOGIC Soft Solutions AP Private Limited, having its Registered Office at: # 7-65, 3rd Floor, Habsiguda X Roads, Nacharam Road, adj: Bharat Petroleum, HYDERABAD 500 007. A.P. (India), home of a world-class professional software services company. We specialize in bespoke software development for business applications and outsourced commercial product development (R&D). Our domain of expertise ranges from B2B eCommerce, ERP, POS, Portal solutions, Human Resource & Payroll and Customer Relationship Management.

TRY LOGIC is a software development, web design & development Services Company that specializes in creating tailor made custom applications for enterprises. We use innovative engagement models, balancing a sophisticated understanding of business with a close attention to detail, to custom-design our process models and meet our client's automation development needs.

The company has expertise to develop new solutions and products right from the requirement definition stage to implementation and support. The company has specific skills Client/Server, databases, intranets, data warehousing, web technologies, WAN, LAN, networking, software design technologies.

The company is capable of creating software solutions covering the entire spectrum of typical Software Project Life-Cycle consisting of system studies, reengineering, system design, software development, testing, data migration, performance tuning and support, this is possible only because of our core technology expertise, project management skills, software engineering

methodologies, talented, motivated team of software engineers and business domain knowledge consultants.

With a view to identify and improve the latent talent in the students, primarily to cater their ACADEMIC requirements and mainly to groom them as INDUSTRY READY PROFESSIONAL, TRY LOGIC provides an opportunity for the much talented yet untapped students who were studying professional academic courses of various stream(s) on processes and methodologies under our unique program called TAC.

TAC (TRYLOGIC ACADEMIC CONCEPT) is a program from TSSPL, under which we shape future of many students as techies who were supposed to undergo industry relevant technical education program. The program consist of Technology updating as of the current industry Requirements along with soft skills improvement and attitude enrichment, more importantly hands on experience expertise during the project work of the participants under the observation of our senior programmers on different platforms into our client / real-time projects. 6

The concept of Knowledge for Knowledge is replaced by 'Knowledge for Application'. In such a situation, TAC try to accomplish everything possible to make learning application oriented. The advantage and idea is to overcome time, energy, and money in the recruitment process and to provide reciprocal benefit to the industries as well as the students who roll out of academic life. The company constantly focuses on learning, upgrading and disseminating state of art technologies among its engineers. Keeping abreast with the changes is an ongoing process with regular in house training programs. Besides technologies the engineers are trained on quality standards and personality development Our VISION is to be globally recognized as a provider of a trusted, reliable resource to quality Information Technology (IT) service / solutions. TRY LOGIC has applied for the membership of STPI Hyderabad unit for software import & export authorization and support as well for D & O trade license. TRY LOGIC is much interested to be part of HYSEA & NASSCOM in near future as our applications are in progress. We are a learning organization and we continually invest time and effort in the area of developing standards & process documentation in line with our objective of getting ISO Quality Management System certification and preparation for level 3 CMM-I certification. For more details please visit www.trylogic.in

Index
S.No 1. 2. 3. 3.1 3.2 3.3 3.4 Title Abstract Introduction System Analysis Existing system Problem Definition Proposed System Feasibility study Page No. 10 11 13 13 13 14 15

4. 4.1 4.2 4.3 4.4 4.5

System Design Project Modules Data Dictionary E-R Diagrams UML Diagrams Hardware and Software Requirements

17 17 20 24 25 33

5. 6. 6.1 6.2 7. 8. 9. 10.

Coding Testing System Testing Software Testing Screen shots Conclusion Bibliography Websites

34 48 48 50 52 55 55 56

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 (Help desk) problems, which are coming from the users of E-care. E-care will take care of every request coming from their users 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 is for better advice and assistance to the people through the use of computers and communication technology. With the individual's consent e-Care enables secure information-sharing between professionals such as doctors, nurses, social workers and teachers in public and voluntary agencies. This project mainly used to extend the business of the organizations worldwide. E-Care attempts to integrate all products and services of the organizations and provides the automated held desk to the end users.

10

2. Introduction:

E-care is very useful for the corporate clients who want their business to extend worldwide i.e. by keeping contact and good relation with the corporate users 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 users so that they improve their products to the user needs. Any user who knows a little about of the computer can handle e-care.

E-care contains six main members who play very important role in this Help Desk System. They include super user, level1 administrator, level2 administrator, level3 administrator, corporate client user and corporate user (or end-user).

Super user is the chief head of the organization that assigns first level, second level, and third level administrators. The super user is responsible for all the three level administrators including the corporate clients. The Super user is the sole person who is responsible for creating categories, modules and the support team.

Super user creates new categories only if HD problems dont belong to those categories present in E-care and similarly with the creation of modules. When the super user creates new categories and modules he will label these categories and modules as levels and appoint one administrator for each of them. When the super user gets the HD problem as request he can modify the request or can answer it by sending solution to the level3 or the support team who is responsible for messaging the response or the solution to the end-user (corporate user).

11

Corporate client is the one who buys E-care product for his business purpose. He can create corporate users for his product. Corporate user is the one who has to register himself to the corporate client before he submits the HD problems to the super user and corporate user is the actual end-user of the product or service.

Corporate user will register to the corporate client and corporate client sends all the registration details to the super user, and after the registration the end-user will submit the HD problems to the super user. When the super user gets the HD problems he will check the details of the end-user and send the responses to the support team who will message the responses to the corporate users.

12

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 E- care system that helps many end-users 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.

3.2 Problem Statement:

If the system is maintaining the list of all the details of corporate users 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-user details or creating new corporate client details and including the details of the categories and the modules that are created newly by the super user becomes very difficult manually.Once all information is provided manually it become quite difficult for updating the records with new information manually, so we automate the system to overcome all such difficulties.

13

E-care, which is developed manually, is the existing system. This system generates and delivers the services to the end-users, which depends on the response provided by the support team who actually message the responses to the corporate users 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 user details or corporate client details and manages the updations and see that the responses are sent to the corporate user as soon as possible. It includes main members like: 1. Super user 2. Corporate client 3. Corporate user 4. Level1 administrator 5. Level2 administrator 6. Level3 administrator or support team. Super user will manage the entire organization that includes corporate clients, corporate users, and level administrators and also he can create the new categories and also modules.

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-users upon their request without any difficulty and saves time.

14

3.4 Feasibility Study:

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 users. 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 users should support input screen. These requirements are satisfied by Java, as it is multi platform environment supports Web Browser where as other languages lack these features. In order user to continuously communicate he/she needs a reliable protocol i.e., is TCP/IP protocol. This protocol frequently transfers messages between client and user. Communication Standards such as HTTP is used .An HTTP is a client/server interaction consists of a single request/reply interchange, it user-friendly environment.

Economic Feasibility: As E-care is help desk system which provides continuous communication to users 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.

15

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 supports up to five hundred simultaneously users against the central database at any given time. E-care must be able to complete 80% of all transactions within two minutes.

16

4. 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 designers 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 user 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 customers 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 whos quality cant 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: -

17

 User module Super User module Administration module User Module : In this module user can register themselves to the e-Care if they are new users, otherwise they can login directly and can then post their queries to e-Care or e-desk. First user has to register with corporate client. In order to send request the end-user has to login and the login details are stored in the database maintained by e-Care system. Database checks the details of the user, if he is valid then allows the user to access the help desk system. Super User module : In this module Super user is the chief head of the Organization who assigns 1st level and 3rd level administrators. The super user is responsible for all the three levels administrators including the corporate clients. The super user is the sole person who is responsible for creating categories, modules and support team. Super User will take all the registration details of the Corporate Users so as to check with the queries which in turn consist of the query and also the userid. Super user has the right to remove any level or add any level and also responsible for creating modules and categories . Administration module: Depending upon categories and modules created by super user the three levels are allotted. They are three types of administrator: Level 1 Administrator: the first level administrator is the one who can add HD problems to a category created by the super user.

18

Level 2 Administrators: The second level administrator is the one who can add HD problems to the modules. Level 3 Administrators: The third level administrator is a member of the support team who provides services to the Corporate clients and corporate users. Corporate Client user: A corporate client user is the one who buys e-desk products. He can create corporate users for his product. Corporate User: Corporate user is the one who registers himself with the corporate client and who is the actual end-user of the product/service. The product features are as follows: Create & maintain levels Create & maintain categories Create & maintain administrators Create sub category Create support team Assign 1st level administrator to a category Assign 2nd level administrator to a sub category Assign 3rd level members to support team Create corporate client Activate or inactivate all e-desk members Check for HD problems submissions Check solutions in repository Scheduling of tasks
19

4.2 Data 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 login, e-login, hd levels, hd emp, categories, modules, support team, schedules, hd problem request, super userprofile, , registration ,forward, problem history, messages etc. NOTE: Primary key is denoted by * for all the database tables. LOGIN:
SNO 1* 2 FIELD NAME USERNAME PASSWORD TYPE VARCHAR2(30) VARCHAR2(30)

20

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 USERID PASSWORD CONFORMATIONPASSWORD HINTQUESTION HINT ANSWER 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)

21

FEEDBACK:
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)

22

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.

Line represents flow

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.

23

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

4.3 E-R Diagrams:

E-R Diagrams for E-Care

REGISTER

FEEDBACK

USER_ID COMMENTS

FIRSTNAME LASTNAME ADDRESS PHONENUMBER STATE CITY COUNTRY ZIPCODE GENDER EMAIL_ID USER_ID PASSWORD CONFIRMATION_PASSWORD HINT_QUESTION HINT_SOLUTION

PROBLEM

USER_ID PROBLEMTYPE DESCRIPTION ANSWER QUES_ID

24

4.4 UML Diagrams:

USE CASE DIAGRAMS: A use case describes a sequence of actions that provide something of measurable value to an actor and is drawn as a horizontal ellipse an actor is a person, organization, or external system that plays a role in one or more interactions with your system. ACTIVITY DIAGRAM: Activity diagrams are used to document workflows in a system, from the business level down to the operational level. When looking at an Activity diagram, you'll notice elements from state diagram, the Activity diagram is a variation of the state diagram where the "states" represent operations, and the transitions represent the activities that happen when the operation is complete. The general purpose of Activity diagrams is to focus on flows driven by internal processing vs. external events. SEQUENCE DIAGRAMS: UML sequence diagrams model the flow of logic within your system in a visual manner, enabling you both to document and validate your logic, and are commonly used for both analysis and design purposes. Sequence diagrams are the most popular UML artifacts for dynamic modeling, which focuses on identifying the behavior within your system. CLASS DIAGRAMS: A class diagram describes the static structure of the symbols in your new system. It is a graphic presentation of the static view that shows a collection of declarative (static) model elements, such as classes, types, and their contents and relationships. Classes are arranged in hierarchies sharing common structure and behavior, and are associated with other classes

25

USECASE DIAGRAM FOR ADMIN MODULE:

26

USECASE DIAGRAM FOR USER MODULE:

27

SEQUENCE DIAGRAM:

28

COLLABORATION DIAGRAM:

29

ACTIVITY DIAGRAM FOR ADMIN MODULE:

30

ACTIVITY DIAGRAM FOR USER MODULE:

31

CLASS DIAGRAM:

32

4.5 Hardware and Software Requirements:

Hard ware Specifications: Processor Processor Speed RAM Hard Disk Key Board : : : : : Intel P-III based system 250 MHz to 833MHz 64MB to 256MB 2GB to 30GB 104 keys

Software Specifications: Language Database Operating System : : : JDK 1.2 SQL Windows NT/95/98/2000

33

5.CODING:
SAMPLE CODE: Database Connection:
<%@page import="java.sql.*"%> <% DriverManager.registerDriver(new oracle.jdbc.driver.OracleDriver()); Connection con=DriverManager.getConnection("jdbc:oracle:thin:@localhost:1521:xe","ecare","ecare"); Statement st=con.createStatement(); %>

Login Form:
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"> <title>JSP Page</title> </head> <body bgcolor="../satya.jpg"> <center><h1>ECARE</h1></center>

<table> <tr> 34

<td><a href="index.jsp">Home</a></td> <td><a href="register.html">Register</a></td> <td><a href="login.html">Login</a></td> </tr></table> <br><br><br>

<center>Login form <form name="f" action="logincheck.jsp"> <table> <tr><td>User ID</td><td><input type="text" name="user"></td></tr> <tr><td>Password</td><td><input type="password" name="pass"></td></tr> <tr><td></td><td><input type="submit" value="Login"></td></tr> </table></form></center> </body> </html>

Registration form:
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"> <title>JSP Page</title> </head> <body bgcolor="lightgreen"> 35

<center><h1>ECARE</h1></center> <form name="f" action="regdata.jsp"> <table><tr><td><a href="index.jsp">Home</a></td> <td><a href="register.html">Register</a></td> <td><a href="login.html">Login</a></td> </tr></table> <br><br><br> <center>Registration Form</center> <form><TABLE> <TR> <TD> <P align=left><FONT size=3><STRONG>FIRST NAME</STRONG> </FONT></P></TD> <TD> <P align=left><INPUT id=fname name=fname ></P></TD></TR> <TR> <TD> <P align=left><STRONG>LAST NAME</STRONG>

&nbsp;</P> </TD> <TD> <P align=left><INPUT id=lname name=lname></P></TD></TR> <TR> 36

<TD> <P align=left><STRONG>ADDRESS</STRONG></P> </TD> <TD> <P align=left><INPUT id=address name=address></P></TD></TR> <TR> <TD> <P align=left><STRONG>PHONE NUMBER </STRONG> </P> </TD> <TD> <P align=left><INPUT id=phno name=phno onblur="number()"></P></TD></TR> <TR> <TD> <P align=left><STRONG>STATE</STRONG> </P> </TD> <TD> <P align=left><INPUT id=text1 name=city></P></TD></TR> <TR> <TD> <P align=left ><STRONG>CITY</STRONG> </P></TD> 37

<TD> <P align=left><INPUT id=text2 name=state></P></TD></TR> <TR> <TD> <P align=left ><STRONG>COUNTRY</STRONG></P> <TD> <P align=left><INPUT id=text3 name=country></P></TD></TR> <TR> <TD> <P align=left><STRONG>ZIPCODE</STRONG></P> </TD><TD> <P align=left><INPUT id=zipcode name=zipcode onblur=zipnum()></P> </TD></TR> <TR> <TD> <P align=left><STRONG>GENDER</STRONG></P></TD> <TD><INPUT id=gender name=gender style="HEIGHT: 20px; WIDTH: 30px" type=radio value=F>Female&nbsp; <INPUT CHECKED id=gender name=gender style="HEIGHT: 20px; WIDTH: 32px" type=radio value=M>Male</TD></TR> <TR> <TD> <P align=left><STRONG>EMAIL_ID</STRONG> </P> <TD> <P align=left><INPUT id=email_id name=email_id onBlur="email()"></P></TD></TR> <TD> 38

<P align=left><STRONG>USER_ID&nbsp;</STRONG> </P></TD> <TD> <P align=left><INPUT id=user_id name=user_id></P></TD></TR> <TR> <TD> <P align=left><STRONG>PASSWORD</STRONG></P></TD> <TD> <P align=left><INPUT id=password name=password

type=password></P></TD></TR> <TR> <TD> <P align=left><STRONG>CONFIRMATION PWD</STRONG> </P> <TD> <P align=left><INPUT id=confpwd name=confpwd type=password onblur="chkpass()"> </P></TD></TR> <TR> <TD> <P align=left><STRONG>HINT QUESTION</STRONG> </P></TD> <TD> <P align=left><SELECT id=hintquestion name=hintquestion style="HEIGHT: 22px; WIDTH: 156px"> <OPTION selected value="your name?">your name?</OPTION><OPTION value="your favourite color?">your favourite color?</OPTION><OPTION 39

value="your favourite sport">your favourite sport</OPTION><OPTION value="your favourite place">your favourite place</OPTION><OPTION value="your favourite actor">your favourite actor</OPTION><OPTION value="your favourite food">your favourite food</OPTION><OPTION value="your date of birth">your date of birth</OPTION><OPTION value="your place of birth">your place of birth</OPTION><OPTION value="your best friend">your best friend</OPTION><OPTION value=""></OPTION></SELECT></P></TD></TR> <TR> <TD> <P align=left><STRONG>HINT SOLUTION</STRONG> </P> </TD> <TD><INPUT id=hintsolution name=hintsolution ></TD></TR> <TR> <TD></TD> <TD></TD></TR> <TR> <TD></TD> <TD><INPUT id=submit1 value=Submit>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; name=submit1type=SUBMIT

<INPUT id=reset1 name=reset1 type=reset value=Reset></TD></TR></TABLE>

</form> </body> </html>

40

Post problems:
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"> <title>JSP Page</title> </head> <body bgcolor="lightgreen"> <center><h1>ECARE</h1></center> <table> <tr> <td><a href="UserHome1.html">userhome</a></td> <td><a href="postproblems.html">postproblem</a></td> <td><a href="solution.jsp">View Solutions</a></td> <td><a href="editprofile.jsp">editprofile</a></td> <td><a href="feedback.jsp">feedback</a></td> <td><a href="index.jsp">logout</a></td>

</tr></table> <br><br><br> <center><form name="f" action="problem.jsp"> <table> <tr><td>Select Problem Type</td> <td><select name="p"> <option value="-1">Select Problem type</option> <option value="medical">Medical Problem</option> 41

<option value="educational">Educational Problem</option> <option value="soft">Software Problem</option> <option value="hard">hardware Problem</option> </select></td></tr> <tr><td>Enter Problem Description</td></tr>

<tr><td><textarea cols="10" rows="10" name="des"></textarea></td></tr> <tr><td></td><td><input type="submit" value="Submit"> </td></tr></table>

</form> </body> </html>

Solution:
<%@include file="Db_Conn.jsp"%> <%@page contentType="text/html" pageEncoding="UTF-8"%> <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">

<html> <head> <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"> <title>JSP Page</title> 42

</head> <body bgcolor="lightgreen"> <center><h1>ECARE</h1></center> <table> <tr> <td><a href="UserHome1.html">userhome</a></td> <td><a href="postproblems.html">postproblem</a></td> <td><a href="solution.jsp">View Solutions</a></td> <td><a href="editprofile.jsp">editprofile</a></td> <td><a href="feedback.jsp">feedback</a></td> <td><a href="index.jsp">logout</a></td>

</tr></table> <br><br><br> <% String str="select * from problem"; ResultSet rs=st.executeQuery(str); %> <center> <table border="3">

<tr><td>Problem Type</td><td>Problem Description</td><td>Answer</td> <% while(rs.next()) {%> </tr><tr><td><%=rs.getString(2)%></td> 43

<td><%=rs.getString(3)%></td> <td><%=rs.getString(4)%></td> <%}%> </tr></table> </center> </body> </html>

Update answer:
<%@include file="Db_Conn.jsp" %> <%@page contentType="text/html" pageEncoding="UTF-8"%> <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">

<html> <head> <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"> <title>JSP Page</title> </head> <body bgcolor="lightgreen"> <center><h1>ECARE</h1></center> <table> <tr> <td><a href="Admin1.html">Home</a></td> <td><a href="deleteuser.jsp">Delete User</a></td> <td><a href="registeredusers.jsp">Registered Users</a></td> 44

<td><a href="update.jsp">Update Answers</a></td> <td><a href="feedbackview.jsp">View feedback</a></td> <td><a href="index.jsp">logout</a></td>

</tr></table> <br><br><br>

<% String qid=(String)session.getAttribute("qid"); String id=request.getParameter("q"); String a=request.getParameter("a"); String str="update problem set answer='"+a+"' where ques_id='"+qid+"'";

System.out.println(str); int i=st.executeUpdate(str); if(i>0) { out.println("answer Updated succesfully"); } else { out.println("answer Updation failed"); } %> </body> </html> 45

Feedback view:
<%@include file="Db_Conn.jsp" %> <%@page contentType="text/html" pageEncoding="UTF-8"%> <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">

<html> <head> <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"> <title>JSP Page</title> </head> <body bgcolor="lightgreen"> <center><h1>ECARE</h1></center> <table> <tr> <td><a href="Admin1.html">Home</a></td> <td><a href="deleteuser.jsp">Delete User</a></td> <td><a href="registeredusers.jsp">Registered Users</a></td> <td><a href="update.jsp">Update Answers</a></td> <td><a href="feedbackview.jsp">View feedback</a></td> <td><a href="index.jsp">logout</a></td>

</tr></table> <br><br><br> <center><h3>FeedBack View</h3>

46

<% String str="select * from feedback"; ResultSet rs=st.executeQuery(str); ResultSetMetaData rsmd=rs.getMetaData(); int count=rsmd.getColumnCount(); %> <table border="3"><tr> <% for(int i=1;i<=count;i++) { %><td><%=rsmd.getColumnName(i)%></td> <%} while(rs.next()) {%> </tr><tr> <% for(int j=1;j<=count;j++) {

%><td><%=rs.getString(j)%></td> <%}} %>

</tr></table> </center> </body>

</html>
47

6.TESTING:

6.1 SYSTEM TESTING:

LIFE CYCLE MODELS: The stage of planning and development process involves defining, developing, testing, delivering, operating, and maintaining a software product. Different life cycle models emphasize different aspects and no single life cycle model is suitable for all software products. A life cycle 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 life cycle model represents software life cycle as a series of successive activities. This phase requires well-defined input information, processes and results in well-defined products. The phased life cycle 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.

48

Analysis

Design

Implementation

System Testing

Maintenance

Planning, User needs Definition Design Details Code, and Test Integration & Acceptance debug

Enhance, Fix Adapt

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

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.

6.2 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: 1. All tests should be traceable to end user requirements. 2. Tests should be planned long before testing begins. 3. Testing should begin on a small scale and progress towards testing in large. 4. Exhaustive testing is not possible. 5. To be most effective testing should be conducted by a independent third party

50

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 customers requirements. 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 verify that all system elements have been properly integrated to perform allocated functions.

Security Testing: Attempts to verify 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.

51

7. Screen shots:

52

53

54

8. Conclusion:
The result of the E-care is that it supports many corporate clients and the individual users or the end-users with unique interface, through which the HD problems are solved within given time and it shows efficiency in the internal messaging system and results in accurate task scheduling system and this E-care can be run with the minimal administration.

9. Bibliography:
BOOKS AND MANUALS :-

1. JAVA-2 Author :

Complete-Reference Patric Norton & Herberlt Schild

2. System Analysis & Designing Author : James A. senn

3. Software Engineering Concept Author : Fairley

4. Software Engineering Principles Author : Pressman

5. Java Server Pages Author : James Good Will

55

10. Websites:

All about Microsoft controls http://www.msdn.microsoft.com/ Wikipedia for various diagrams & testing methods http://www.wikipedia.org/ Cool text for Images and Buttons http://cooltext.com/ Smart Draw for drawing all the Diagrams used in this report. http://www.smartdraw.com/ HTML coding http://www.w3schools.com

56