Your SlideShare is downloading. ×
kats.ppt
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

kats.ppt

690

Published on

may be use fuel to all

may be use fuel to all

Published in: Education, Technology
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
690
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
10
Comments
0
Likes
1
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. •Introduction system analysis •System requirements •System design •Technologies used •Testing and implementation •Screen shots •Conclusion •Future enhancement •bibliography
  • 2. 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.
  • 3. Disadvantages:
  • 4. PROPOSED SYSTEM
  • 5. Merits of This System:
  • 6.  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
  • 7. HARDWARE REQ’S  Processor : Pentium IV or i3 Intel processor.  Hard Disk : 40 GB  RAM : 256 MB or 512
  • 8. MODULES The project contains “three” modules Super User. Administrator . Student. MODULES
  • 9. 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.
  • 10. 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
  • 11. 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
  • 12. UML DIAGRAMES Student Registration View Question/Answers Post a Question Administrator View Answer for a Posted Question Student
  • 13. Use Case for Administrator: Addministrator Send Answers to Students Add/Delete/Modify qestions/answers Student Check Posted questions Addministrator
  • 14. Use case for student • Student Registration View Question/Answers Post a Question Administrator View Answer for a Posted Question Student
  • 15. 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 Add Topic Sucess Delete Topic Delete Admin Delete Dept
  • 16. 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 SucessCheck for more Add que/ans Sucess Modify que/ans Sucess Delete que/ans Sucess
  • 17. Sequence Diagram for Student: Post Question : Student Register Login Check Available Questions Check Answer for Posted Question Enter Details Id Enter Id Details Verify Verify Sucess Check Available Questions view Post a Question Sucess Verify Answer Check Answer
  • 18. Collaboration Diagram for Super User
  • 19. 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:
  • 20. 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 Student 6: Sucess 7: Check for more 8: Add que/ans 9: Sucess 10: Modify que/ans 11: Sucess 12: Delete que/ans 13: Sucess
  • 21. Class Diagram:
  • 22. Entity-Relationship Diagrams:
  • 23. DATABASE DESIGN • The design starts with the end users view of t he organization called conceptual requiremen ts and user in a decision-making, which uses information obtained by accessing the databa se. The end users also provide data to be sto red in the database. In considering the end us er requirements tradeoff have to be taken into account.
  • 24. TABLE NAME: super user: It contains all details about super 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
  • 25. TABLE NAME: QANDA: It contains all details about Questions and answers with categories. The following table explains all t he fields Field Name Data Type Size DEPARTMENT VARCHAR2 10 TOPICS VARCHAR2 10 QUESTION VARCHAR2 50 ANSWER VARCHAR2 50 CATEGORY VARCHAR2 15 COUNT NUMBER 15 POSTDATE VARCHAR2 15 Field Name Data Type Size DEPARTMENT VARCHAR2 10 TOPICS VARCHAR2 10 QUESTION VARCHAR2 50 ANSWER VARCHAR2 50 CATEGORY VARCHAR2 15 COUNT NUMBER 15 POSTDATE VARCHAR2 15
  • 26. TABLE NAME: DEPTOPICS:It contains all details about department s and topics. The following table explains all the fiel ds Field Name Data Type Size DEPARTMENT VARCHAR2 10 TOPICS VARCHAR2 10 Field Name Data Type Size DEPARTMENT VARCHAR2 10 TOPICS VARCHAR2 10
  • 27. Home Page:
  • 28. Super user login page:
  • 29. Login failure page:
  • 30. Login success page:
  • 31. Admin registration page:
  • 32. Registering success:
  • 33. Add department’s page:
  • 34. Add topics page:
  • 35. Add questions page:
  • 36. Successfully posted page:
  • 37. Admin checking for posted questions page:
  • 38. Admin answering for posted question page:
  • 39. TESTING Test levels • Unit testing tests the minimal software compo nent and sub-component or modules by the p rogrammers. • Integration testing exposes defects in the inte rfaces and interaction between integrated co mponents (modules). • Functional testing tests the product accordin g to programmable work. • System testing tests an integrated system to verify/validate that it meets its requirements.
  • 40. ALPHA TESTING: • Alpha testing is simulated or actual operation al testing by potential users/customers or an i ndependent test team at the developers' site. Alpha testing is often employed for off-the-sh elf software as a form of internal acceptance t esting, before the software goes to beta testin g
  • 41. BETA TESTING • Beta testing comes after alpha testing. Ver sions of the software, known as beta versio ns, are released to a limited audience outsi de of the company. The software is release d to groups of people so that further testin g can ensure the product has few faults or bugs. Sometimes, beta versions are made available to the open public to increase the feedback field to a maximal number of futu re users.
  • 42. 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.
  • 43. 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.
  • 44. BIBLIOGRAPHY Core Java™ 2 Volume I – Fundamentals 7th Edition - Cay S. Hortsman Pearson Education – Sun Microsystems Gary Cornell Core Java™ 2 Volume II – Advanced - Cay S. Hortsman Pearson Education – Sun Microsystems Gary Cornell Head First Servlets & JSP - Eric Freeman O’Reilly – SPD Elisabeth Freeman The Book of JavaScript 2nd Edition - Thau SPD Effective Java – Programming Language Guide - Joshua Bloch Pearson Education – Sun Microsystems Java Database Best Practices - George Reese O’Reilly – SPD JBoss – A Developers Notebook - Norman Richards O’Reilly – SPD Sam Griffith
  • 45. ANY QUIRES

×