SHRI RAM INSTITUTE OF TECHNOLOGY, JABALPUR

A PROJECT REPORT ON ONLINE HELP-DESK SYSTEM

For Fulfillment of the Degree Of

MASTER OF COMPUTER APPLICATION

Under the valuable guidance of

Submitted To: DR. J. K. SOLANKI PRINCIPAL Submitted By SHILPA DUBEY (0205CA081049) SHRI RAM INSTITUTE OF TECHNOLOGY 2010-11 MRS. ANAMIKA SONI (PROJECT GUIDE)

ACKNOWLEDGEMENT

Success is the manifestation of diligence, perseverance, inspiration, motivation and innovation. The

completion of any interdisciplinary project depends on coordination, co-operation and combined effort of several sources of knowledge, energy and time. Hence these lines trying our best to give full credit wherever it is due. We would like to express our sincere gratitude to Dr. J. K. Solanki, Principal of SHRI RAM INSTITUTE OF TECHNOLOGY, for his encouragement and facilities provided to carry out this work at Jabalpur Engineering College, Jabalpur. We express my sincere gratitude to Miss Nidhi Mishra, Mrs. Anamika Soni for their encouragement and inspiration for providing me the required assistance from the department. Finally we thank all those who are involved directly and indirectly in completion of this project.

Shilpa Dubey

SHRI RAM INSTITUTE OF TECHNOLOGY JABALPUR (M.P.)

CERTIFICATE

This is to certify that Shilpa Dubey ,student of SHRI RAM INSTITUTE OF TECHNOLOGY, JABLPUR (M.P.) have completed the project on the system for ONLINE HELPDESK.

They are submitting the project in partial fulfillment of the degree of MASTER OF COMPUTER APPLICATION from SHRI RAM INSTITUTE OF TECHNOLOGY, JABLPUR (M.P.) academic year 20010-11.

This report is up to the standard both in respect of its contents and its literary presentation for being referred to the examinees. I wish them all the success.

Dr. J. K. Solanki (Principal) (M.C.A. Department) (SRIT, Jabalpur)

SHRI RAM INSTITUTE OF TECHNOLOGY JABALPUR (M.P.)

CERTIFICATE

This is to certify that Shilpa Dubey, student of SHRI RAM INSTITUTE OF TECHNOLOGY, JABLPUR (M.P.) have completed the project on the system for ONLINE Help Desk.

They are submitting the project in partial fulfillment of the degree of MASTER OF COMPUTER APPLICATION from SHRI RAM INSTITUTE OF TECHNOLOGY, JABLPUR (M.P.) academic year 20010-11.

This report is up to the standard both in respect of its contents and its literary presentation for being referred to the examinees. I wish them all the success.

Department) Jabalpur)

Ms. Nidhi Mishra (M.C.A. (SRIT,

SHRI RAM INSTITUTE OF TECHNOLOGY JABALPUR (M.P.)

CERTIFICATE

This is to certify that Shilpa Dubey, student of SHRI RAM INSTITUTE OF TECHNOLOGY, JABLPUR (M.P.) have completed the project on the system for ONLINE Help Desk.

They are submitting the project in partial fulfillment of the degree of MASTER OF COMPUTER APPLICATION from SHRI RAM INSTITUTE OF TECHNOLOGY, JABLPUR (M.P.) academic year 20010-11.

This report is up to the standard both in respect of its contents and its literary presentation for being referred to the examinees. I wish them all the success.

Department) Jabalpur)

Mrs. Anamka Soni (M.C.A. (SRIT,

SHRI RAM INSTITUTE OF TECHNOLOGY JABALPUR (M.P.)

CERTIFICATE

This is to certify that Shilpa Dubey, student of SHRI RAM INSTITUTE OF TECHNOLOGY, JABLPUR (M.P.) have completed the project on the system for ONLINE HELP DESK.

They are submitting the project in partial fulfillment of the degree of MASTER OF COMPUTER APPLICATION from SHRI RAM INSTITUTE OF TECHNOLOGY, JABLPUR (M.P.) academic year 20010-11.

This report is up to the standard both in respect of its contents and its literary presentation for being referred to the examinees. I wish them all the success.

. External Examiner Examiner

... Internal

DECLARATION

I , the students of SHRI RAM INSTITUTE OF TECHNOLOGY, JABLPUR (M.P.) hereby declare that project entitled ONLINE HELP-DESK SYSTEM is being developed by me for the partial fulfillment of the degree of Master of Computer Application. The project embodies our work.

Project submitted by: Shilpa Dubey

TABLE OF CONTENT

Introduction Objective Design Principle & Explanation Theoretical Background System Analysis and Design Methodology adopted, system implementation and details of Hardware and Software Project dictionary Data flow diagram Input and Output design E-R diagram Methodology used for testing Conclusion Bibliography

Title of project: ONLINE-RECRUITMENT SYSTEM Objective and scope of the project 1.INTRODUCTION This project is basically developed for the Personal institutes or Hospitals or Colleges etc .This project/software fulfills the requirement of the particular Institutes. With the help of this project or software any institute can generate its full information on the internet and the users can get that information from anywhere. All the above mentioned work, Institution were doing personally means if anyone wants to know about their institute they have to go to that particular institute and for this they have a time boundation and if they are going to ask any thing they have to do good dressing, but with the help of this project they dont have to think about anything they can just visit the site and can ask questions from anywhere at any time. And both ends get satisfied.

software proved as an easy tool to overcome the problem that the users and institutes were facing. This software is developed using the JAVA as the frontend and the MY MQL as the database or the backend.

HELP DESK At Help Desk you can ask questions in any topic and have them answered for free by our experts. To ask questions or participate in answering them you must register for a free account. By registering you will be able to:

Get free answers from experts in any of our topics. Enhance knowledge by answers that we will provide you. Communicate privately with other members (PM). See fewer ads. A satisfied customer will stay with your web site and bring you new customers therefore a help desk system is a must for membership sites.

Objectives of Online Help Desk System :

Provide an innovative, cost efficient and effective querying system. Increase the quality and quantity of information asking for answer. Reduce time consumption of user and administrator .

2.Objective User friendliness: This project will have user-friendly screens. The screens designed will have very simple functionality for retrieving/ adding/ updating the information.

Consistency: The consistency in the proposed system will provide high efficiency due to smaller learning curves and increased data integrity.

Compatibility: This project offers great compatibility, as it will be designed with proper methodology, new tools and technology Security:

This project is a secured system, which will provide corporate level security. Only the authorized people will be able to access critical information. Also that will enable a user to view /edit/ add the information, based on roles and privilege assigned to that user. Reliability & Robustness: This project is built with proper architecture and design and it will provide a reliable and robust application to the users. Performance: The performance of this application will be high because of its optimize design and sound architecture. Extensibility: This project has a modular design and would provide the flexibility of adding, future modules to the application Database Creation: A database of the registered users will be created and this will help the users to fetch the details of EXAMINATION. There is a separate database for administrator for updating. Informative The project has all the necessary details about the concerned SRIT information, updates, news and also job info hence, provides all the relevant information therefore. Flexibility: This project has the flexibility of adding new modules when needed.

3. DESIGN PRINCIPLES & EXPLANATION 3.1. MODULES

Overall Description of Online Help Desk System

Users Modules
Registration. Login. FAQ. Settings. Online Contact

Admins Modules
Registration. Login. Add Moderators. Answers for the Question. Manage Knowledge Base. Manage FAQ. 3.2. MODULE DESCRIPTION

Users Module :-

1. Registration In this module Users will register . For this registration the users need to mention some information about

themselves like name, DOB, address & contact number. As soon as they get register they will their ID & Password. 2. Login In this module user have to enter their ID & password and they get linked with that particular institute . And after linking they can have many facilities like Ask Queries, Old Queries, View KB, View FAQ, Edit profile, Setting, and Online contact. 3. FAQ In this module user can ask any type of question related to the institute and they will get their answers at once. If they are not getting their answer at the same time, then it means that they will get their answer within some time duration and that time duration will be fixed. 4. Settings - In this module user can reset any information filled by them and can set the properties like allowing questions publicly or privately. as users go for public then that question or information will send to the KB and if it is private then answer for that private question will send only to that particular user. 5. Online Contact In this module user can directly interact with the responder and the conversation will automatically be saved and user can discard that conversation too.

Admins module-

1. Registration - In this module staff will register. For this registration they need to enter some of their information like name, DOB , address ,contact number. As soon as they get register they will get their ID and password. 2. Login - In this module staff will enter their ID and password. And after login they will handle each and every functions.

3. Add moderator - In this module new staff will add himself/herself to the database and admin will give approval. 4. Answers for the questions - In this module staff will answer to the questions asked by the user and store these questions to the knowledge base. 5. Manage KB and FAQ - in this module admin will manage so many functions like updating FAQ and KB time to time.

4.THEORETICAL BACKGROUND JAVA Introduction:Adobe Flash now performs many of the functions that were originally envisioned for Java applets, including the playing on Java is a programming language originally developed by Sun Microsystems and released in 1995 as a core component of Sun Microsystems' Java platform. The language derives much of its syntax from C and C++ but has a simpler object model and fewer low-level facilities. Java applications are typically compiled to byte code that can run on any Java virtual machine (JVM) regardless of computer architecture.

The original and reference implementation Java compilers, virtual machines, and class libraries were developed by Sun from 1995. As of May 2007, in compliance with the specifications of the Java Community Process, Sun made available most of their Java technologies as free software under the GNU General Public License. Others have also developed alternative implementations of these Sun technologies, such as the GNU Compiler for Java and path. so required a download by the user before applets would appear f video content, animation, and some rich GUI features. Java itself has become more

widely used as a platform and language for server-side and other programming.

PRIMARY GOALS:There were five primary goals in the creation of the Java.
1. 2. 3. 4. 5.

It should use the object-oriented programming methodology. It should allow the same program to be executed on multiple operating systems. It should contain built-in support for using computer networks. It should be designed to execute code from remote sources securely. It should be easy to use by selecting what were considered the good parts of other object-oriented languages.

CLASS LIBRARIES:Java libraries are the compiled byte codes of source code developed by the JRE implementer to support application development in Java. Examples of these libraries are:

The core libraries, which include:

1.Collection libraries that implement data structures such as lists, dictionaries, trees and sets. 2. XML Processing (Parsing, Transforming, Validating) libraries Security. 3. Internationalization and localization libraries. 4. The integration libraries, which allow the application writer to Communicate with external system. These libraries include:

The Java Database Connectivity (JDBC) API for database access Java Naming and Directory Interface (JNDI) for lookup and discovery RMI and CORBA for distributed application development .

User Interface libraries, which include: The (lightweight, or native) Abstract Windowing Toolkit (AWT), which provides GUI components, the means for laying out those components and the means for handling events from those components. The (heavyweight) Swing libraries, which are built on AWT but provide (non-native) implementations of the AWT widgetry. APIs for audio capture, processing, and playback A platform dependent implementation of Java virtual machine (JVM) that is the means by which the byte codes of the Java libraries and third party applications are executed.

Java version:

JDK 1.0 (January 23, 1996) (Unsupported) JDK 1.1 (February 19, 1997) (Unsupported)

Major additions an extensive retooling of the AWT event model inner classes added to the language.

JavaBeans JDBC RMI J2SE 1.2(December 8, 1998) (Unsupported)

Codename Playground. This and subsequent releases through J2SE 5.0 were reframed retrospectively Java 2 and the version name "J2SE" (Java 2 Platform, Standard Edition) replaced JDK to distinguish the

base platform from J2EE (Java 2 Platform, Enterprise Edition) and J2ME (Java 2 Platform, Micro Edition ). The Swing graphical API was integrated into the core classes. Sun's JVM was equipped with a JIT compiler for the first time.

Java Plug-in Java IDL, an IDL implementation for CORBA interoperability Collections framework _Collections framework2 _Collections framework3.0

J2SE 1.3 (May 8, 2000) (Unsupported) Codename Kestrel. Hotspot JVM included (the Hotspot JVM was first released in April, 1999 for the J2SE 1.2 JVM) RMI was modified to support optional compatibility with CORBA Java Sound. Java Naming and Directory Interface (JNDI) included in core libraries (previously available as an extension) Java Platform Debugger Architecture (JPDA) J2SE 1.4 (February 6, 2002) (EOL) Codename Merlin. This was the first release of the Java platform developed under the Java Community Process as JSR 59. Assert keyword. Regular expressions modeled after Perl regular expressions exception chaining allows an exception to encapsulate original lower-level exception, Internet Protocol version 6 (IPv6) support

Non-blocking NIO (New Input/output) Logging API Image I/O API for reading and writing images in formats like JPEG and PNG integrated XML parser and XSLT processor (JAXP). Integrated security and cryptography extensions (JCE, JSSE, and JAAS). Metadata: Also called annotations, allows language constructs such as classes and methods to be tagged with additional data, which can then be processed by metadata-aware utilities. Auto boxing/unboxing: Automatic conversions between primitive types (such as int) and primitive wrapper classes (such as Integer). Enumerations: The enum keyword creates a type safe, ordered list of values (such as Day. MONDAY, Day. TUESDAY, etc.). Previously this could only be achieved by non-type safe constant integers or manually constructed classes (type safe enum pattern). Swing: New sinkable look and feel, called synth. Vardars: The last parameter of a method can now be declared using a type name followed by three dots (e.g. void draw text (String... lines)). In the calling code any number of parameters of that type can be used and they are then placed in an array to be passed to the method, or alternatively the calling code can pass an array of that type. Enhanced 'for loop': The for loop syntax is extended with special syntax for iterating over each member of either an array or any iterable, such as the standard Collection classes, using a construct of the form:

Java SE 6 (December 11, 2006) (Supported) Codename Mustang. As of this version, Sun replaced the name "J2SE" with Java SE and dropped the ".0" from the version number.[11] Internal numbering for developers remains 1.6.0.[12] This version was developed under JSR 270.

During the development phase, new builds including enhancements and bug fixes were released approximately weekly. Beta versions were released in February and June 2006, leading up to a final release that occurred on December 11, 2006. The current revision is Update 7 which was released in mid-2008.

Scripting Language Support (JSR 223): Generic API for tight integration with scripting languages, and built-in Mozilla JavaScript Rhino integration. Dramatic performance improvements for the core platform [15] [16], and Swing. Java Compiler API (JSR 199): an API allowing a Java program to select and invoke a Java Compiler programmatically. Upgrade of JAXB to version 2.0: Including integration of a STAX parser. Support for pluggable annotations (JSR 269).

Many GUI improvements, such as integration of Swing Worker in the API, table sorting and filtering, and true Swing double-buffering (eliminating the gray-area effect).

Java SE 6 Update 10

Java SE 6 Update 10 (previously known as Java SE 6 Update N), while it does not change any public API, is meant as a major enhancement in terms of end-user usability. Java Deployment Toolkit, a set of JavaScript functions to ease the deployment of applets and Java Web Start application Java Kernel, a small installer including only the most commonly used JRE classes. Other packages are downloaded when needed.

The Features of JAVA are:-

 Compiled and Interpreted. Platform-Independent and portable. Object-Oriented. Robust and Secure. Distributed. Simple, Small and Familiar. Multithreaded and Interactive. High Performance Dynamic. Jsp and Servlet A Servlets Job Read explicit data sent by client (form data) Read implicit data sent by client (request headers) Generate the results Send the explicit data back to client (HTML) Send the implicit data to client (status codes and response headers) The Advantages of Servlets Over Traditional CGI Efficient Threads instead of OS processes, one servlet copy Convenient Lots of high-level utilities Powerful Sharing data, pooling, persistence Portable Run on virtually all operating systems and servers

 Inexpensive There are plenty of free and low-cost servers Secure No shell escapes, no buffer overflows The Need for JSP With servlets, it is easy to Read form data Read HTTP request headers Set HTTP status codes and response headers Use cookies and session tracking Share data among servlets Remember data between requests Get fun, high-paying jobs But, it sure is a pain to Use those println statements to generate HTML Maintain that HTML Benefits of JSP Although JSP technically can't do anything servlets can't do, JSP makes it easier to: Write HTML Read and maintain the HTML JSP makes it possible to: Use standard HTML tools such as Macromedia DreamWeaver or Adobe Go Live. Have different members of your team do the HTML layout than do the Java programming JSP encourages you to Separate the (Java) code that creates the content from the (HTML) code that presents it. Advantages of JSP over Competing Technologies Versus ASP or ColdFusion Better language for dynamic part Portable to multiple servers and operating systems

 Versus PHP Better language for dynamic part Better tool support Versus pure servlets More convenient to create HTML Can use standard tools (e.g., Dreamweaver) Divide and conquer JSP programmers still need to know servlet programming Versus Velocity or WebMacro Standard Versus client-side JavaScript (in browser) Capabilities mostly do not overlap with JSP, but You control server, not client Richer language Versus server-side JavaScript (e.g., LiveWire, BroadVision) Richer language Versus static HTML Dynamic features Adding dynamic features no longer "all or nothing" decision Implementing MVC with Request Dispatcher 1. Define beans to represent the data 2. Use a servlet to handle requests Servlet reads request parameters, checks for missing and malformed data, calls business logic, etc. 3. Populate the beans The servlet invokes business logic (application-specific code) or data-access code to obtain the results. Results are placed in the beans that were defined in step 1. 4. Store the bean in the request, session, or servlet context The servlet calls setAttribute on the request, session, or servlet context objects to store a reference to the beans that represent the results of the request. 5. Forward the request to a JSP page.

 The servlet determines which JSP page is appropriate to the situation and uses the forward method of RequestDispatcher to transfer control to that page. 6. Extract the data from the beans. JSP 1.2: the JSP page accesses beans with jsp:useBean and a scope matching the location of step 4. The page then uses jsp:getProperty to output the bean properties. JSP 2.0: the JSP page uses ${nameFromServlet.property} to output bean properties The JSP page does not create or modify the bean; it merely extracts and displays data that the servlet created.

5.SYSTEM ANALYSIS AND DESIGN

ANALYSIS: Requirement analysis is down in order to understand the problem the software system is to solve. The problem could be automating an existing manual process, developing a new automated system, or a combination of the two. For large systems that have many features, and that need to perform many different tasks, understating the requirements of the system is the major task. The emphasis in the requirements analysis is on identifying what is needed from the system, not how the system will achieve its goals. The developer has to develop the system to satisfy the clients needs. Once the problem is analyzed and the essentials understood, the requirement must be satisfied in the requirement specification document. For requirement specification in the form of a document, some specification language has to be selected. All the factors that may affect the design and the proper functioning of the system should be specified in the requirement document. Preliminary user manual

That describes the entire major user interfaces frequently forms a part of the requirements documents.

DESIGN: The purpose of the design phase is to plan a solution of the problem specified by the requirement document. This phase is the first step in moving fro the problem domain to the solution domain. Stating with what is needed; design takes us towards how to satisfy the needs. The designs affect the quality of software; it has major impact on the later phases, particularly testing and maintenances. The output of this phase is the design document. This document is similar to a blue print or as plan fort the solution and is used later during implementation, testing and maintenance. The design activity is often divided into two separate phases system design And detailed design, which is some time also called top level design, aims to identify the modules should be in the system, the specifications of these modules, and how the they interact with each other to produce the desired results. At the end of the system design all the major data structures, file formats, output formats and the major modules in the system and their specifications are decided.

METHADOLOGY USED FOR TESTING

Testing is the process of detecting errors. Testing performs a very critical role for quality assurance and for ensuring the reliability of software. The results of testing are used later on during maintenance also.

LEVEL OF TESTING In order to uncover the errors present in different phases we have the concept of levels of testing. The basic levels of testing are follows:System Testing The philosophy behind testing is to find errors. Test cases are devised with this in mind. A strategy employed for system testing is code testing. Code Testing This strategy examines the logic of the program. To follow this method we developed some test data that resulted in executing every instruction in the program and module i.e. every path is tested. System is not designed as entire nor are they tested as single systems. To ensure that the coding is perfect two types of testing is performed or for that matter is performed on all system.

Types Of Testing Unit Testing Link Testing

Unit Testing Unit testing focuses verification effort on the smallest unit of software i.e. the module. Using the detailed design and the process specification testing is done to uncover errors within the boundary of the modules must be successful in the unit test before the start of the integration testing begins. In this project each service can be thought of a module. There are so many modules like Login, a HWAdmin, MasterAdmin Normal User and

PManager. Giving different set of inputs has tested each module. When developing the module as well as finishing the development so that each module works without any error. The inputs are validated when accepting from the user.

System Testing Here the entire software system is tested. The reference document for this process is the requirement document, and the goal OS to see if software meets its requirements. Here entire ATM has been tested against requirements of project and it is checked whether all requirements of project have been satisfied or not. Acceptance Testing Acceptance Test is performed with realistic data of the client to demonstrate that the software is working satisfactorily. Testing here is focused on external behavior of the system: the internal logic of program is not emphasized. In this project Network Management of Database System I have collected some data and tested whether project is working correctly or not. Test cases should be selected so that largest number of attribute of an equivalence class is exercised at once; the testing phase is an important part of software development. It is the process of finding errors and missing operations and also a complete verification to determine whether the objectives are met and the user requirements are satisfied.

White Box Testing

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

Black Box Testing This testing method considers a module as a single unit and checks the unit at interface and communication with other module rather getting into details at statement level. Here the module will be treated as a block box that will take some input and generate output. Output for a given set of input combination is forwarded to other modules. 6.METHADOLOGY ADOPTED, SYSTEM IMPLEMENTATION & DETAILS OF HARDWARE & SOFTWARE

System implementation:The implementation phase is less creative then system design. It is primarily concerned with user train, site preparation and file conversion. When the candidate system is linked to terminals or remote sites, the telecommunication network and tests of the network along with the system are also included under implementation. During the final testing, user acceptance is tested followed by user training. Depending on the nature of the system, extensive user training may be required. Details of hardware & software

Hardware:

Processor Dual Core Ram 1 GB Hard Disk 10GB

Software:Front-end Tools: Windows 7 Jdk 1.6 Netbeans Back-end Tools:

MY SQL

7.PROJECT DICTIONARY DATAFLOW DIAGRAMS Data flow diagrams represent the flow of data through a system. A DFD is composed of: 1. Data movement shown by tagged arrows. 2. Transformation or process of data shown by named bubbles. 3. Sources and destination of data represented by named rectangles. 4. Static storage or data at rest denoted by an open rectangle that is named.

The DFD is intended to represent information flow but it is not a flowchart and is not intended to indicate decision-making, flow of control, loops and other procedural aspects of the system. DFD is a useful graphical tool and is applied at the earlier stages of requirements analysis. It may be further refined at preliminary design stage and is used as mechanism for creating a top level structural design for software. The DFD drawn first at a preliminary level is further expanded into greater details: The context diagram is decomposed and represented with multiple bubbles Each of these bubbles may be decomposed further and documented as more detailed DFD s.

User

( Mnage Admins & FAQ & KB, & all functions as admin.) ( Registration,longin,view KB & FAQ,Online contact,Ask que.)

0.0

Help_desk
System

Administrator

( Registration,login,manage FAQ & KB, , online contact with user, Ans to the que.)

Moderators

One Level DFD

User

Register

Registration

Login

Edit

View View
conversation

Profile

FAQ

KB Que

Chat

FAQ

table
KB que.

do

table
Answer

Staff
Setting

for selected Que.

KB ans. table

User
Profile

User

Moderators

Registration Login

Manae FAQ

KB que. table Chat Manage KB

FAQ

table
KB Ans. table

View tickets

Ticket table

Moderators
for Que.

User

Moderators

Answer table

User

Registratio n

Administrator

Login Chat Manage Moderator

User
Admin table FAQ table Manag e KB KB Ans. table KB que. table Ans. Of Que. Manage FAQ Open a ticket
Ticket table

Administrator

Answer table

Administrator

User

Address

ER-Diagram
Give s

Name

Date of joining Contact no. Staff Will add User ID Date of Que.

Staff ID

Is admin Is active

Ans. ID Staff ID Answer

Que. ID Is ans KB Que.

KB Ans.

Date of Ans. Ans. ID Que.ID KB Que. ID Date of Ans. Answe r Ticket ID Time of ans.

Ranking

Time of Que.

Answer User ID
Staff

Adds Address Name

ID

Contact no. Date of joining

User

Is active

answere d

User ID

Ticke t ID

Que. ID

Question

as k Que.

User ID Time of Que. Date of Que.

DATA BASE DESIGN Tables Database Tables

Data dictionary

Field name Staff ID Name Address Ph. No. Mob No. e-mail Is Admin Date of joining

Data type Number Varchar Varchar Number Number Varchar Varchar Date

Width 06 15 25 10 10 15 05

Constraints Primary Key Not null Not null Not null Not null Not null Not null Not null

Field name Users Table

Data type

Width

Constraints

User ID Name Address Ph. No. mob. No. e-mail Date of joining

Number Varchar Varchar Number Number Varchar Date

06 15 25 10 10 15

Primary Key Not null Not null Not null Not null Not null Not null

Field name Query Table Query ID User ID Question Date of Que. Time of Que.

Data type Number Number Varchar Date Time

Width 06 06 50

Constraints Primary Key Foreign Key Not null Not null Not null

Field name Answer Table Ans. ID User ID Question ID Staff ID Answer Date of Ans.

Data type Number Number Number Number Varchar Date

Width 06 06 06 06 60

Constraints Primary Key Foreign Key Foreign Key Foreign Key Not null Not null

Field name KB Que. Table Que. ID User ID Date of Que. Time of Que.

Data type Number Number Date Time

Width 06 06

Constraints Primary key Foreign key Not null Not null

Field name KB Ans. Table Ans. ID KB Que. ID Staff ID. Answer Date of Ans. Ranking

Data type Number Number Number Varchar Date Number

Width 06 06 06 60 08

Constraints Primary key Foreign key Foreign key Not null Not null Not null

FAQField name table Que. ID Ans. ID Date of Que.

Data type Number Number Date

Width 06 06

Constraints Primary key Foreign key Not null

LIMITATION

This projects only lacks the interaction of the user and company employees face to face which is more impactful, but future enhancements can dissolve the problem easily.

Possible Improvement: Feedback can be taken

CONCLUSION

This project is useful for any company to respond to the customers queries, where both customers and company employees have got the facility of adding questions and answers at ANY TIME, from ANY WHERE and on ANY DAY. Since, this project is based on JAVA and JAVA is platform independent language, so this project can run easily on any operating system.

References

Ian Somerville, Software Engineering, Sixth Edition, Pearson Education Ltd, 2002. www.programmersheaven.com www.project4students.com Elamsri and Navathe, Fundamentals of Database Systems, Pearson Asia Edition 2000

Naughton & Schildt The Complete Reference Java 2, Tata McGraw Hill

Deitel Java-how to Program Pearson Education, Asia.

CMS professional Complete references for java

Henry F.Korth and S.Sudarshan for DBMS Horstmann & Cornell Core Java 2 (Vol I & II), Sun Microsystems HTML and XHTML The Complete Reference by Thomas A. Powell.