The document describes a proposed website called Inquest that aims to facilitate interaction between professors and students. It would allow students to post questions and experiences and allow professors and other students to provide answers. The site would use PHP, Bootstrap, CSS, HTML and be hosted on XAMPP. It would have separate modules for administrators, professors and students, each with different capabilities. Administrators could manage all site content and user accounts. Professors could add specializations and answer student questions. Students could post questions and answers. UML diagrams depict use cases for each user type interacting with the site. The goal is to create a more interactive knowledge sharing platform than existing sites.
Original Description:
A blogging website for students within the campus level
The document describes a proposed website called Inquest that aims to facilitate interaction between professors and students. It would allow students to post questions and experiences and allow professors and other students to provide answers. The site would use PHP, Bootstrap, CSS, HTML and be hosted on XAMPP. It would have separate modules for administrators, professors and students, each with different capabilities. Administrators could manage all site content and user accounts. Professors could add specializations and answer student questions. Students could post questions and answers. UML diagrams depict use cases for each user type interacting with the site. The goal is to create a more interactive knowledge sharing platform than existing sites.
The document describes a proposed website called Inquest that aims to facilitate interaction between professors and students. It would allow students to post questions and experiences and allow professors and other students to provide answers. The site would use PHP, Bootstrap, CSS, HTML and be hosted on XAMPP. It would have separate modules for administrators, professors and students, each with different capabilities. Administrators could manage all site content and user accounts. Professors could add specializations and answer student questions. Students could post questions and answers. UML diagrams depict use cases for each user type interacting with the site. The goal is to create a more interactive knowledge sharing platform than existing sites.
Contents : • Abstract • Introduction • Requirements/languages • Modules • UML diagrams • Conclusion Abstract: We all aware of the well known questioning Quora and of course we to know about one of the best blogging website Reddit and here comes the idea of making an interactive website INQUEST. Inquest is a blogger and a question arising site which can be used as a mode of interaction between the professor and students and to share knowledge. Introduction: Probably by now you all have got an overview about Inquest. The single line use of this site can be termed as a wholesome mode of asking queries and posting things. Can be related to a social website owned by a particular institution. Of course we have came across the sites which provide a way of communication between students and professors and may others but they only give information about the professors and the old students but our theme is to provide a blogger may be phrased as a social website which is used to communicate with everyone who have already registered by means of website itself but not just like giving information of old students. The query you have posted is visible to every valid user who have registered on the website and every one can answer your query . You can even post your experiences and the intern batch can share their experiences too. Requirements: Software Requirements : PHP scripting Boot strap CSS HTML Webserver : XAMPP Hardware Requirements : Minimum required CPU Pentium processor Modules: Admin module Professor module Student module Admin module: The admin is the responsible for the everything that happens inside the blogger. He can manage the accounts modify content of blogger and can go through the profile of every students. Admin maintains all the internal and external level schema and the do things according . He is the one who have full rights on the Inquest. The pre coded validator will validates the user upon new registration. Professor module:
Those profiles who are under the category of
professor has some special categorization. They can add their specializations and they play a key role in solving doubts and queries raised by students. They can also post some valuable information and their experience’s and call for workshops and activities. Student module:
The person who raises queries . He can post any
query regarding any thing and still he can answer to anyone. Only verified users will be added to the database server. Thereby only verified users can raise and answer to the queries. Admin use case diagram: Professor use case diagram: Student use case diagram: Conclusion : This is the prototype of the Inquest . Unlike other websites which just provides details of students and contact details of professors inquest also establishes a platform to contact and interact. Not just simply giving you information. Assume a situation a where you don’t know any professors related to your query but still you got solution.