kats.ppt

INFO WARE SERVICESPresented by:Karthik nch

Contents:

•Introduction system analysis

•System requirements•System design•Technologies used•Testing and implementation•Screen shots•Conclusion•Future enhancement•bibliography

ABSTRACT In “Info ware Services” maintaining all the

details of 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. The primary goal of a Info ware Services is to provide an environment that is both “convenient” and “efficient” to use in retrieving and storing database information.

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

Existing System:

• Difficulty in contacting the concerned person.• Difficult to handle more students for administrator.

• Difficulty of maintaining frequently asked questions in a data base

Disadvantages:

PROPOSED SYSTEM

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

.

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.

functi

onal

req’s

SOFTWARE

HARDWARE

SYST

EM

Req

uire

men

t’

s

SOFTWARE REQ’S Operating system : windows XP or

Linux User Interface : HTML,CSS Clint-Side Scripting : Java Script Programming Language : Java Web Applications : JDBC,JSP IDE/Workbench : Eclipse Database : Oracle Server Deployment : Apache Tomcat

6.0

HARDWARE REQ’S

Processor : Pentium IV or i3 Intel processor.

Hard Disk : 40 GBRAM : 256 MB or 512

MODULES

The project contains “three” modules

Super User.

Administrator .

Student.

MODULES

1.Super user:

The responsibility of the super user is to centrally control the data, appoint administrators to all the departments and shifting the administrators one department to other and replacing with

others when there is a vacancy in any departments.

The super user can also have a right to change the questions like adding deleting the records from the database. The

super user provides the login names and password for entire administrators department wise.

2.Administrator

Each department will have one or more administrator; some departments may have more than one administrator. The major responsibility of

administrator is to answer all the questions posted by students on a regular basis.

The administrator can add, modify or remove questions from all the

Categories (about the question categories described below).

All the questions posted by the students will be added to the list of existing questions only when the administrator answers that

question, simultaneously a copy of answer is sent to student who initiated that question.

Administrator also reserves a right to post a question into a particular category even if it is not a question frequently asked. The

administrators have the capability of changing his password as when he requires.

adminstrator

Students

These are the users at the lower level of our abstraction. Before posting a question, the student has to select the department to which it belongs. A

copy of the answer will be sent to the student after the administrator answered his question.

students

UML DIAGRAMES

Student

Registration

View Question/Answers

Post a Question

Administrator

View Answer for a Posted Question

Student

use case diagram for super user

Use Case for Administrator:

Addministrator

Send Answers to Students

Add/Delete/Modify qestions/answers

Student

Check Posted questions

Addministrator

Use case for student

•

Student

Registration

View Question/Answers

Post a Question

Administrator

View Answer for a Posted Question

Student

Sequence Diagram for Super User:

: SuperUserLogin Create

DepartmentReg Admin & Assign

DepartmentAdd Topic Delete Topic Delete Dept Delete Admin

Enter Id ,password,TypeVerify

Invalid

Create DepartmentAssign Admin

Add Topic

Sucess

Delete Topic

Delete Admin

Delete Dept

Sequence Diagram for Administrator:

: AdministratorLogin View Posted

QuestionAnswer to Posted

QuestionsAdd

Question/AnswerModify

Question/AnswerDelete

Question/Answer

Enter Id,password,TypeCheck

Check Posted queAnswer to Student

SucessCheck for more

Add que/ans

Sucess

Modify que/ans

Sucess

Delete que/ans

Sucess

Sequence Diagram for Student:

Post Question : Student

Register Login Check Available Questions

Check Answer for Posted Question

Enter Details

Id

Enter Id Details

Verify

VerifySucess

Check Available Questionsview

Post a QuestionSucess

Verify Answer

Check Answer

Collaboration Diagram for Super User

Collaboration Diagram for Administrator:

: SuperUser

Login

Create Department

Reg Admin & Assign Department

Add Topic

Delete Topic

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

13:

14: Delete Dept

15:

Collaboration Diagram for Student:

Answer to Posted Questions

: Administrator

Login Add Question/Answer

Modify Question/Answer

View Posted Question

Delete Question/Answer

1: Enter Id,password,Type

2: Check

3:

4: Check Posted que

5: Answer to Student6: Sucess

7: Check for more

8: Add que/ans

9: Sucess

10: Modify que/ans

11: Sucess

12: Delete que/ans

13: Sucess

Class Diagram:Register User

name : StringDob : Dateage : DoubleAddress : Stringemail : StringPassword : String

Login

Id : Stringname : Stringtype : string

CheckAvailable

Deptid : StringTopic : Stringquestion : StringAnswer : String

CheckAnswer

Question : StringAnswer : String

Check

type : String

PostQuestion

Deptid : StringTopic : Stringquestion : StringStudId : Int

CreateDept

DeptId : Stringname : String

Check

type : String

RegAdmin

name : StringDob : dateAge : DoubleAdd : Stringemail : Stringpass : stringDeptId : String

CheckPostedQuestion

Studid : inttopic : StringQuestion : String

SendAnswer

studId : intquestion : Stringans : String

Check

type : String

AddQus

deptId : Stringtopic : Stringqus : Stringans : String

Student

SuperUser

Administrator

Entity-Relationship Diagrams:

DATABASE DESIGN

• The design starts with the end users view of the organization called con-ceptual requirements and user in a decision-making, which uses informa-tion obtained by accessing the data-base. The end users also provide data to be stored in the database. In con-sidering the end user requirements tradeoff have to be taken into ac-count.

TABLE NAME:super user: It contains all details about su-per user. The following table explains all the fields

Field Name Data Type Size

USER I.D VARCHAR2 5

FIRST NAME VARCHAR2 25

LASTNAME VARCHAR2 20

PASSWORD VARCHAR2 10

AGE NUMBER 3

DATEOFBIRTH VARCHAR2 12

QUALIFICATION VARCHAR2 15

GENDER VARCHAR2 7

MARTIAL STATUS VARCHAR2 15

EMAIL VARCHAR2 20

ADDRESS VARCHAR2 15

CITY VARCHAR2 15

STATE VARCHAR2 16

COUNTRY VARCHAR2 14

ZIPCODE NUMBER 10

DESIGNATION VARCHAR2 19

TABLE NAME: QANDA: It contains all details about Questions and answers with categories. The follow-

ing table explains all the fields


DEPARTMENT VARCHAR2 10

TOPICS VARCHAR2 10

QUESTION VARCHAR2 50

ANSWER VARCHAR2 50

CATEGORY VARCHAR2 15

COUNT NUMBER 15

POSTDATE VARCHAR2 15



TOPICS VARCHAR2 10

QUESTION VARCHAR2 50

ANSWER VARCHAR2 50

CATEGORY VARCHAR2 15

COUNT NUMBER 15

POSTDATE VARCHAR2 15

TABLE NAME: DEPTOPICS:It contains all details about de-partments and topics. The following table

explains all the fields



TOPICS VARCHAR2 10



TOPICS VARCHAR2 10

无忧PPT整理发布 S

CREEN SHOTS

http://www.51ppt.com.cn/



无忧PPT整理发布

Home Page:





Super user login page:





Login failure page:





Login success page:





Admin registration page:





Registering success:





Add department’s page:





Add topics page:





Add questions page:





Successfully posted page:





Admin checking for posted questions page:





Admin answering for posted question page:




TESTING

Test levels• Unit testing tests the minimal software com-

ponent and sub-component or modules by the programmers.

• Integration testing exposes defects in the in-terfaces and interaction between integrated components (modules).

• Functional testing tests the product accord-ing to programmable work.

• System testing tests an integrated system to verify/validate that it meets its requirements.

ALPHA TESTING:

• Alpha testing is simulated or actual op-erational testing by potential users/cus-tomers or an independent test team at the developers' site. Alpha testing is of-ten employed for off-the-shelf software as a form of internal acceptance testing, before the software goes to beta testing

BETA TESTING

• Beta testing comes after alpha testing. Versions of the software, known as beta versions, are released to a limited audi-ence outside of the company. The soft-ware is released to groups of people so that further testing can ensure the product has few faults or bugs. Some-times, beta versions are made available to the open public to increase the feed-back field to a maximal number of future users.

CONCULSION

It has been a great pleasure for us to work on this exciting and challenging project. This project proved good for me as it provided practical knowledge of java and servlets.This will provide better opportunities and guidance in future developing projects independently and tomcat server, but also about handling procedure related with ”Info ware Services”. It also provides knowledge about the latest technology used in web enabled application and client server technology that will be great demand in future. This will provide better opportunities and guidance in future in developing projects independently.

FUTURE ENHANCEMENT

Future enhancement of this project can be achieved by adding web seminars between the lecturers and students so that they can interact each other at the

moment. Hence they can clarify their doubts instantaneously.

BIBLIOGRAPHYCore Java™ 2 Volume I – Fundamentals 7th Edition - Cay S. HortsmanPearson Education – Sun Microsystems Gary Cornell

Core Java™ 2 Volume II – Advanced - Cay S. HortsmanPearson Education – Sun Microsystems Gary Cornell

Head First Servlets & JSP - Eric FreemanO’Reilly – SPD Elisabeth Freeman

The Book of JavaScript 2nd Edition - ThauSPD

Effective Java – Programming Language Guide - Joshua BlochPearson Education – Sun Microsystems

Java Database Best Practices - George ReeseO’Reilly – SPD

JBoss – A Developers Notebook - Norman RichardsO’Reilly – SPD Sam Griffith

ANY QUIRES

THANK U ALL