ABSTRACT This project is be designed and developed to handle Frequently Asked Questions posted to various departments in a university. The University examination branch wants to maintain all the frequently asked questions in the database subject wise, to avail them to all the students whenever necessary. They will update the questions as and when required. The primary goal of the Query Handling Service is to provide an environment that is both convenient and efficient to use in retrieving and storing the information into database.. The database system must provide the safety to the information stored, despite system crashes or attempts of unauthorized access. If data are to be shared among several users, the system must avoid possible anomalous results. Existing System The existing system is a manual one. When the student wants to clear his query he personally contacts the concerned person in the university. The concerned person will clear his doubt. Disadvantages: • Difficulty in contacting the concerned person. • Difficult to handle more students for administrator. • Difficulty in maintaining frequently asked questions manually Proposed System The Query Handling Services is to replace the existing manual system with a software solution. The University examination branch wants to maintain all the frequently asked questions in the database subject wise, to avail them to all the students. And they will update the questions as and when required in online. The proposed system has one super user to control the data, appointing the administrators in each department. The administrator is responsible to answer all the questions posted by students. When the student post a question in certain department the respective administrator will answer the question and a copy of the answer will be sent to the student. Merits of This System • Faster processing when compared to existing one. • Maintaining frequently asked questions • Modifications of answers can be carried out immediately • Administrator can handle more number of students. • Easy maintenance of administrator details. Modules: • Super User • Administrator • Student Super User: super user to control the data, appointing the administrators in each department,appointing the administrator to a particular department for that he register the admin,adding a new departments like computer science, chemistry, physics, maths, etc.. At the same time he can delete the departments, adding a new topic to particular department. At the same time he delete the added topics also, adding the question with answers and storing the data in database. Administrator:  Admin can add the question with answers and it will be stored in database for students to retrieve it.  Admin will modify the answers.  The student post a question in certain department the respective administrator will answer the question and a co

1. QUERY HANDLING SYSTEM
3

2. Abstract:
• This project is designed for college students
to get clarify their doubts by posting their
queries.
• The queries posted by the students are
handled by the administrator.
• The administrator answers the queries
posted by students.

3. Objective Of The Project:
• The primary goal of the query handling
system is to provide an environment that
is both convenient and efficient for the
students and lecturers.
• It also provides the safety to the
information stored, despite system crashes
or attempts of unauthorized access.

4. Existing System:
• The existing system is manual one.
• When the students want to clear there
doubts they personally contact the concerned
person in the college.
Disadvantages:
• Difficulty in contacting the concerned person.
• Difficult to handle more students requests for
faculty.
• Difficulty in maintaining frequently asked
questions manually.

5. Proposed System:
• Proposed system has one super user to control
the data, appointing the administrators in
each department.
• The administrator is responsible to answer all
the questions posted by students.
Advantages:
• Faster processing when compared to existing
one.
• Easy in maintaining frequently asked questions.

6. Advantages Contd…
• Modifications of answers can be carried out
immediately.
• Faculty can handle more number of students
requests.
• Easy maintenance of faculty and student details.

7. Modules
The project contains three modules:
• Super User
• Administrator
• Student

8. Super User
Super User performs the following functions:
• Controls the data.
• Registers the administrators and appoints
them in each department.
• Add/delete departments like physics,
computer science, etc..
• Adding the question with answers and
storing the data in database.

9. Administrator
• The student post a question in certain
department and the respective administrator
will answer the question and copy of the
answer will be sent to the student.
• If there is any modification to be carried
out in the answers administrator will
modify the answers.

10. Student
• Student post a question in certain department.
• Student check the answer for which he posted.
• Student checks the answers for available
questions.

11. Feasiblility Study
• An important outcome of preliminary
investigation is the determination that system
required is feasible.
• Since data is voluminous and involves a lot of
overhead.
• Therefore it is best activity for
computerization.
• The proposed system is feasible in following
aspects.

12. Technical Feasibility
The proposed system is technically feasible
since the equipment,software technology and
available personal in the organization are
well suitable for the proposed system.

13. Operational Feasibility
• The operational feasibilty system is measured
by the usage of the system after
implementation and resistance from the users.
• Hence it is encouraging to undertake a
detailed system analysis.

14. Economical Feasibilty
• Since necessary hardware and software are
available in the organization,there is no need
to procure and install new hardware and
software.
• Thus there is no need of extra personal on the
proposed system.
• Hence the proposed system is economically
feasible.

15. Block Diagram:
Web user
interface
Query
handler
Database
system
Login management
handler
Post query
handler
Department
handler
Registration form
handler
Solution
Handler

16. Web User Interface:
• Web user interface will provide the interface
to the user to communicate with the system.
Query Handling System Handler:
• “Query handling services” maintains various
frequently asked questions posted by the
students and keeps them in a database so that
it can be retrieved easily by students when the
admin answer that question.

17. Login Management Handler:
• This block helps for authentication of user and
also changing the password.
Database System:
• This block helps us to store the data or retrieve
the data from database.
Solution handler:
• This block helps to store and retrieve the solution
for particular query. Also helps to modify the
solutions.

18. Post Query Handler:
• This block helps for handling various
frequently asked questions posted by students.
Department Handler:
• This block helps for handling different
departments like computer science ,maths etc…
Registration Form Handler:
• This block helps to register the faculty members
for answering the questions posted by students.
As well as it also helps to register the students.

19. UML Diagrams:
Static Diagrams:
Class Diagram:

20. Component Diagram

21. Object Diagram

22. Deployment Diagram

23. Dynamic Diagrams:
Use Case for Administrator:
Addministrator
Add/Delete/Modify
qestions/answers
Send Answers to Students
Student
Check Posted questions
Addministrator

24. Use Case For Student:
Student
Registration
View Question/Answers
Post a Question
Administrator
View Answer for a Posted
Question
Student

25. Sequence Diagram for Super User:
: SuperUser
Login Create
Department
Reg Admin & Assign
Department
Add Topic Delete Topic Delete Dept Delete Admin
Enter Id ,password,Type
Verify
Invalid
Create Department
Assign Admin
Sucess
Add Topic
Delete Topic
Delete Admin
Delete Dept

26. Sequence Diagram for Administrator:
: Administrator
Login View Posted
Question
Answer to Posted
Questions
Add
Question/Answer
Modify
Question/Answer
Delete
Question/Answer
Enter Id,password,Type
Check
Check Posted que
Answer to Student
Check for more Sucess
Add que/ans
Sucess
Modify que/ans
Sucess
Delete que/ans
Sucess

27. Sequence Diagram for Student:
Post Question
: Student
Register Login Check Available
Questions
Check Answer for
Posted Question
Enter Details
Id
Verify
Enter Id Details
Verify
Sucess
Check Available Questions
view
Post a Question
Sucess
Verify Answer
Check Answer

28. State Chart Diagram:

29. Activity Diagram:

30. Collaboration Diagram for
Administrator:
: SuperUser
Login
Create
Department
Reg Admin & Assign
Department
Add
Topic
Delete
Topic
13:
15:
Delete
Dept Delete
Admin
1: Enter Id ,password,Type
2: Verify
3: Invalid
4: Create Department
5: Assign Admin
6: Sucess
7:
8: Add Topic
9:
10: Delete Topic
11:
12: Delete Admin
14: Delete Dept

31. Collaboration Diagram for Student:
Answer to Posted
Questions
1: Enter Id,password,Type
11: Sucess
: Administrator
8: Add que/ans
Login Add
Question/Answer
Modify
Question/Answer
9: Sucess
View Posted
Question
13: Sucess
Delete
Question/Answer
2: Check
3:
4: Check Posted que
6: Sucess
5: Answer to Student
7: Check for more
10: Modify que/ans
12: Delete que/ans

32. System Specifications
Software Requirements:
• Operating system : Windows XP
• Programming Platform : j2sdk
• Backend Database : Mysql
• Server deployment : Apache Tomcat
Hardware Requirements:
• Processor : Pentium IV or higher
• Hard disk : 160 GB
• RAM : 1 GB

33. Testing
• Software testing is a critical element of
software quality assurance and represents the
ultimate review of specifications,design and
coding.
• Testing presents an interesting anomaly for
the software engineer.

34. Testing Type Methods
Unit Testing:
• Unit testing focuses verification effort on the
smallest unit of software design that is the
module.
• The unit test is normally white box testing
oriented and steps can be conducted in
parallel for multiple modules.

35. Integration Testing:
• The objective is to take unit tested methods
and build a program structure that has been
dictated by design. It is of two types
1.Top down Integration:
• It is an incremental approach for construction
of program structure.
• Modules are integrated by moving downward
through control hierarchy,beginning with the
main control program

36. 2.Bottom Up Integration:
• This method as the name sugggests,begins
construction and testing with atomic modules
i.e., modules at the lowest leveling of program
structure.
• The modules are integrated in bottom up
manner.

37. Validation Testing
• Validation testing is the next stage which can
be defined as successful when the software
functions in the manner reasonably expected
by the customer

38. System Testing:
• System testing is actually a series of different
tests whose primary purpose is to fully
exercise the computer-based system.
Recovery Testing:
• It is a system test that forces the system to fail
in a variety of ways and verifies that the
recovery is properly performed.

39. Security Testing:
• Attempts to verify the protection mechanisms
built into the system.
Perfomance Testing:
• This method is designed to test runtime
perfomance of software within the context of
an integrated system.

40. Test Cases

41. Test Case ID Test Case Description Expected Behavior Actual Behavior Test
Case
Result
1 Admin Login Admin should login to the infoware
application with his regisetered id and
password
Admin logged into the infoware
application.
PASS
2 Student Login Student should login to his account
with his regisetered id and password
Student logged into his account PASS
3 Shuffling admin Superuser should shuffle admin from
one department to another.
Superuser shuffled admin’s
department.
PASS
4 Add department Superuser should add a new department
into our application.
Superuser added a new department. PASS
5 Add topic Superuser should add a new topic in the
department.
Superuser added a new topic. PASS
6 Add question. Superuser should add a new question to
a topic.
Superuser added a new question. PASS
7 Delete department Superuser should delete a department
from the application.
Superuser deleted a department. PASS
8 Delete topic Superuser should delete a topic in the
department.
Superuser deleted a topic. PASS
9 Delete question. Superuser should delete a question
from a topic.
Superuser deleted a question. PASS

42. Conclusion
• The new system of QUERY HANDLING has been
implemented.
• The present system has been integrated with the
already existing.
• The database was put into the MYSQL server
.This was connected by JDBC.
• The database is accessible through internet on
any geographic location
• .This system has been found to meet the
requirements of the students/indenters and also
very satisfactory.

43. Screen Shots

52. Bibliography
References from the project development were
taken from the following books and websites:
Java Technologies
Java Complete Reference
Java Script Programming by Yehuda shiran
Mastering Java Security
Java2 networking By Pistoria

53. Bibliography Contd….
Java Security By Scotl Oaks
Head First EJB Sierra Bates
Java Server pages by Larne Pekowsley
Java Server pages by Nick Todd
HTML
HTML Black Book by Holzner

54. Bibliography Contd…
JDBC
Java Database Programming with JDBC by Patel
moss.
Software Engineering by Roger Pressman.