Download Student Staff Feedback Management System: An Overview and more Study Guides, Projects, Research Web Programming and Technologies in PDF only on Docsity!
STUDENT STAFF FEEDBACK MANAGEMENT
SYSTEM
INTRODUCTION
Online student feedback system is the web based feedback collecting system from the students and provides the automatic generation of a feedback which is given by students. We have developed student feedback system to provide feedback in a quick and easy manner to the particular department. We have developed Student Staff Feedback System to provide feedback in an easy and quick manner to the college principal and Hod’s. So we call it as Student Staff Feedback System which delivers via the student staff interface as online system which acting as a Service Provider. So we called it a student’s feedback system which delivers via the student staff interface as online system which acting as a service provider. By using this technology we can make fast feedback about the staff by students on time to head of departments as they referred in online system. By using this technology we can give feedback in online system as fast as compare to the existing paper feedback system. This project has four kinds of users Student, Staff, Hod’s, and Principal. The student can give feedback in online system provided by college staff. The existing system carries more time to do a piece of work for this reason the online system feedback is implemented. First of staff can prepare questions & add, update these questions to the online system. After that it was viewed by the students and can give feedback about the lecturers.Students will fill online feedback using a standard form. In this project security is also maintain that is the result of feedback is only visible to authentic user. This feedback report was checked by the Hod’s. He can view grades and view the grades obtained to the lecturers and give this report to the principal and he give counseling to the college staff. EXISTING STUDENT STAFF FEEDBACK MANAGEMENT SYSTEM Coming to the existing system the feedback is done by manual process. In the existing system students can give feedback about the lecturers by using paper and pen. The purpose of this project is to make the process of taking feedback from the students in online regarding the lecturer’s teaching. As of now this task was done manually with the use of papers and pens. This has many drawbacks and evaluating this hand written forms is a difficult process. But the restriction here is once the student submits the report then he cannot modify it later. With this the student can successfully submit feedback on lecturer’s teaching in a very efficient manner without any loss of data. The administrator and the faculty members can access these feedbacks from the students and take appropriate actions. By this process. Student can give feedback in online system without waste his time in writing. After giving feedback by every student. With this, the institutes can access the feedback reports in a faster way and without any loss of data.This Page May Contain What is student staff feedback system on Java And Latest Information/News About student staff feedback system on Java,If Not Use Search.Papers are collected by the Hod’s and calculate the overall grade for each subject and each lecturer. Student needs to logging into the website of online feedback system and giving his/her feedback and can perform modifications too. Online Student Feedback System Project Topics, One student is allowed to give only one feedback in one
turn; however they are allowed to change it at any time After that those all grade report is viewed by the principal which is given by the Hod’s. for both staff and students in an institution. For Staff to provide student feedback collection form project in core me student feedback system Hence estimating the performance of lecturers and giving counseling to college staff. PROPOSED STUDENT STAFF FEEDBACK MANAGEMENT SYSTEM The Online Student Feedback System is a management information system for education establishments to manage student data. Student Feedback Systems provide capabilities for selecting particular subject for feedback and generate the report automatically, build student details, student-related data needs in a college. Using the latest Microsoft technology, the .Net framework and ASP.Net, our system is a complete feedback management and staff interaction system with built-in features proofing that easily supports Integration with the latest student staff feedback system providers. A Online Student Feedback System is an automatic feedback generation system that provides the proper feedback to the teachers as per the categories like always, poor, usually, very often, sometimes. Download Student Staff Feedback System Project Report .The provision may as well have a database of survey which can be given to the understudies following a secured. In the existing system students can give feedback about the lecturers by doing manually. By this process student can give feedback in online system without wasting his time in writing. This system is designed to be simple to use, simple to understand and easy to implement and configure to fit. After giving feedback by every student papers are collected by the faculty and calculated the overall grade for each subject and each lecturer. After that those all grade report is viewed by the HOD which is given by the faculty. It is provided as an Application Service Provision thus offering low setup costs.student staff feedback system.doc (Size: 2. MB / Downloads: 858). Hence estimating the performance of lecturers and giving feedback to college staff. So, the existing system carries more time to do a piece of work for this reason the online system feedback is implemented. INTRODUCTION We have developed Student Staff Feedback System to provide feedback in an easy way. This is the main disadvantage of the existing system for giving feedback about the lecturers and viewing report of lecturers manually. Student feedback on courses is an essential element in quality assurance. Here we aimed to design online web application for issuing the feedback about the lecturers by students, this is named as student staff feedback system. Questionnaires are of primary importance in the dialogue with students, since they are the best tool we currently have for collecting objective, detailed and reasonably systematic information on a wide range of questions, which Informs the teacher about student’s perceptions of the course's strengths and weaknesses. Student Staff feed Back System to provide feedback in a easy and quick manner to the college principal and Hod’s. Responses are collated on behalf of departments by the system, and will be used only for the purposes of quality enhancement. Classle-Online Social Learning Platform for the students to collaborate, Project Title. Project Embedded System : Create a Project: The aim of this is to save time for staff in academic departments and to allow a minimum level of statistical analysis of the data across the College. So we call it as Student Staff Feedback System which delivers via the student staff interface as online system
SYSTEM IMPLEMENTATION
In this project we implemented the system which works on the concept of online feedback from students which is the replacement of existing paper feedback system which is so complicated method for finding an average for particular subject feedback which is submitted by students. This project has four kinds of users Student, Staff, Hod’s, and Principal. In this system we have design main three forms student login form, admin login form, faculty login form. Student will login in their login form with proper id and password which is provided by admin at the time of registration. The student can give feedback in online system provided by college staff. First of staff can prepare questions and add, update these questions to the online system. After that if student want any changes in his profile then there is an option for edit such particular information of his own. Projects Skip to content Skip to content; Online Student Feedback System. Student Feedback. 3. Reports. After that the subject contains page is displayed, where the subject is located in it and as per the selection from student students continued to their feedback after this page the feedback page is displayed. This system can be developed using After that it was viewed by the students and can give feedback about the lecturers. This page contains a form which includes such questions about the teachers where it contains some simple question regarding particular subject faculty. After giving the feedback the page appeared which contains a message like you are feedback is submitted. Then after feedback is submitted there is a log out button after click on it student will successfully log out from their profile. In main page it contains some hyperlinks like contact us, frequently ask questions, and submit the queries. And contains three particular modules like student login, admin login, staff login etc. Admin will fill the information of students as well as view their feedback, add and delete student and generate the average report of that feedback. After that log out button occurs and admin simply logout from the system. Student will login by using user id and password and after the login page will be open contains subjects, suggestion box, submit suggestions, submit feedback and after their occurs a log out button for logout successfully from the system. MODULES OF STUDENT FEEDBACK MANAGEMENT SYSTEM The proposed system consists of four modules: Student : Student can give the feedback about the lecturers on the scale of five. Students can give feed back about the lecturer based on interaction of lecturer in the class room with students. Here we shared complete list of student projects that we shared in this page. Screenshot of Employee and Payroll System; Project SRS. IEEE Standard SRS. According to that, students can give feedback as per the given grades.
Staff: The feedback given by the students can be viewed by the staff and improve their performance in teaching and other aspects Head Of Departments : These feedback reports were checked by the Hod’s. He can view overall grades and view the grades obtained to the lecturers and give this report to the principal and he can give counseling to the college staff Principal : Finally, report was referred by the principal and give suggestions to lecturers to improve their teaching. These are the four modules present in the project so we have developed these things in very easy and clearly understandable way. So, by seen above description the proposed system having many advantages as compared to the existing system. Highlights: Saves your time Manage the entire process in easy and quick way Enhance the staff Improve the issuing standards
STAFF MODULE:
The staff will have the authorities on this as following:
- Add questions
- Update questions
- View questions
- View report Add questions: In this module the student or staff or Hod’s can add questions if he is interested to add another question to database to rate the lecturers. Update questions: In this module the student or staff or Hod’s can update questions. View questions: In this module students can view all questions in the database to give feedback about the lecturers View report: After giving feedback by the students; lecturers, Hod’s, principal can view report
SOFTWARE DESCRIPTION
INTRODUCTION TO DOT NET
Microsoft.NET Framework
The .NET Framework is a new computing platform that simplifies application development in the highly distributed environment of the Internet. The .NET Framework is designed to fulfill the following objectives: To provide a consistent object-oriented programming environment whether object code is stored and executed locally, executed locally but Internet-distributed, or executed remotely. To provide a code-execution environment that minimizes software deployment and versioning conflicts. To provide a code-execution environment that guarantees safe execution of code, including code created by an unknown or semi-trusted third party. To provide a code-execution environment that eliminates the performance problems of scripted or interpreted environments. To make the developer experience consistent across widely varying types of applications, such as Windows-based applications and Web-based applications. To build all communication on industry standards to ensure that code based on the .NET Framework can integrate with any other code. The .NET Framework has two main components: the common language runtime and the .NET Framework class library. The common language runtime is the foundation of the .NET Framework. You can think of the runtime as an agent that manages code at execution time, providing core services such as memory management, thread management, and remoting, while also enforcing strict type safety and other forms of code accuracy that ensure security and robustness. In fact, the concept of code management is a fundamental principle of the runtime. Code that targets the runtime is known as managed code, while code that does not target the runtime is known as unmanaged code. The class library, the other main component of the .NET Framework, is a comprehensive, object-oriented collection of reusable types that you can use to develop applications ranging from traditional command-
The runtime enforces code access security. For example, users can trust that an executable embedded in a Web page can play an animation on screen or sing a song, but cannot access their personal data, file system, or network. The security features of the runtime thus enable legitimate Internet-deployed software to be exceptionally feature rich. The runtime also enforces code robustness by implementing a strict type- and code- verification infrastructure called the common type system (CTS). The CTS ensures that all managed code is self-describing. The various Microsoft and third-party language compilers Generate managed code that conforms to the CTS. This means that managed code can consume other managed types and instances, while strictly enforcing type fidelity and type safety. In addition, the managed environment of the runtime eliminates many common software issues. For example, the runtime automatically handles object layout and manages references to objects, releasing them when they are no longer being used. This automatic memory management resolves the two most common application errors, memory leaks and invalid memory references. The runtime also accelerates developer productivity. For example, programmers can write applications in their development language of choice, yet take full advantage of the runtime, the class library, and components written in other languages by other developers. Any compiler vendor who chooses to target the runtime can do so. Language compilers that target the .NET Framework make the features of the .NET Framework available to existing code written in that language, greatly easing the migration process for existing applications. While the runtime is designed for the software of the future, it also supports software of today and yesterday. Interoperability between managed and unmanaged code enables developers to continue to use necessary COM components and DLLs. The runtime is designed to enhance performance. Although the common language runtime provides many standard runtime services, managed code is never interpreted. A feature called just-in-time (JIT) compiling enables all managed code to run in the native machine language of the system on which it is executing. Meanwhile, the memory manager removes the
possibilities of fragmented memory and increases memory locality-of-reference to further increase performance. Finally, the runtime can be hosted by high-performance, server-side applications, such as Microsoft® SQL Server™ and Internet Information Services (IIS). This infrastructure enables you to use managed code to write your business logic, while still enjoying the superior performance of the industry's best enterprise servers that support runtime hosting. .NET Framework Class Library The .NET Framework class library is a collection of reusable types that tightly integrate with the common language runtime. The class library is object oriented, providing types from which your own managed code can derive functionality. This not only makes the .NET Framework types easy to use, but also reduces the time associated with learning newfeatures of the .NET Framework. In addition, third-party components can integrate seamlessly with classes in the .NET Framework. For example, the .NET Framework collection classes implement a set of interfaces that you can use to develop your own collection classes. Your collection classes will blend seamlessly with the classes in the .NET Framework. As you would expect from an object-oriented class library, the .NET Framework types enable you to accomplish a range of common programming tasks, including tasks such as string management, data collection, database connectivity, and file access. In addition to these common tasks, the class library includes types that support a variety of specialized development scenarios. For example, you can use the .NET Framework to develop the following types of applications and services: Console applications. Scripted or hosted applications. Windows GUI applications (Windows Forms). ASP.NET applications. XML Web services. Windows services.
Unlike ActiveX controls, Windows Forms controls have semi-trusted access to a user's computer. This means that binary or natively executing code can access some of the resources on the user's system (such as GUI elements and limited file access) without being able to access or compromise other resources. Because of code access security, many applications that once needed to be installed on a user's system can now be safely deployed through the Web. Your applications can implement the features of a local application while being deployed like a Web page. C#.Net for Windows Application Overview of the .NET Framework The .NET Framework is a managed type-safe environment for application development and execution. The .NET Framework manages all aspects of your program’s execution. It allocates memory for the storage of data and instructions, grants or denies the appropriate permissions to your application, initiates and manages application execution, and manages the reallocation of memory from resources that are no longer needed. The .NET Framework consists of two main components: the common language runtime and the .NET Framework class library. The common language runtime can be thought of as the environment that manages code execution. It provides core services, such as code compilation, memory allocation, thread management, and garbage collection. Through the common type system (CTS), it enforces strict type-safety and ensures that code is executed in a safe environment by also enforcing code access security. The .NET Framework class library provides a collection of useful and reusable types that are designed to integrate with the common language runtime. The types provided by the .NET Framework are object-oriented and fully extensible, and they allow you to seamlessly integrate your applications with the .NET Framework. Languages and the .NET Framework The .NET Framework is designed for cross-language compatibility, which means, simply, that .NET components can interact with each other no matter what supported language they were written in originally. So, an application written in Microsoft Visual Basic .NET might
reference a dynamic-link library (DLL) file written in Microsoft Visual C#, which in turn might access a resource written in managed Microsoft Visual C++ or any other .NET language. This language interoperability extends to full object-oriented inheritance. A Visual Basic .NET class might be derived from a C# class, for example, or vice versa. This level of cross-language compatibility is possible because of the common language runtime. When a .NET application is compiled, it is converted from the language in which it was written (Visual Basic .NET, C#, or any other .NET-compliant language) to Microsoft Intermediate Language (MSIL or IL). MSIL is a low-level language that the common language runtime can read and understand. Because all .NET executables and DLLs exist as MSIL, they can freely interoperate. The Common Language Specification (CLS) defines the minimum standards to which .NET language compilers must conform. Thus, the CLS ensures that any source code successfully compiled by a .NET compiler can interoperate with the .NET Framework. The CTS ensures type compatibility between .NET components. Because .NET applications are converted to IL prior to deployment and execution, all primitive data types are represented as .NET types. Thus, a Visual Basic Integer and a C# int are both represented in IL code as a System.Int32. Because both languages use a common type system, it is possible to transfer data between components and avoid time-consuming conversions or hard-to-find errors. Visual Studio .NET ships with languages such as Visual Basic .NET, Visual C#, and Visual C++ with managed extensions, as well as the JScript scripting language. You can also write managed code for the .NET Framework in other languages. Third-party tools and compilers exist for Fortran, Cobol, Perl, and a host of other languages. All of these languages share the same cross-language compatibility and inheritability. Thus, you can write code for the .NET Framework in the language of your choice, and it will be able to interact with code written for the .NET Framework in any other language. .NET Framework Architecture
An assembly contains one or more modules. A module contains the code that makes up your application or library, and it contains metadata that describes that code. When you compile a project into an assembly, your code is converted from high-level code to IL. Because all managed code is first converted to IL code, applications written in different languages can easily interact. For example, one developer might write an application in Visual C# that accesses a DLL in Visual Basic .NET. Both resources will be converted to IL modules before being executed, thus avoiding any language-incompatibility issues. Each module also contains a number of types. Types are templates that describe a set of data encapsulation and functionality. There are two kinds of types: reference types (classes) and value types (structures). These types are discussed in greater detail in Lesson 2 of this chapter. Each type is described to the common language runtime in the assembly manifest. A type can contain fields, properties, and methods, each of which should be related to a common functionality. For example, you might have a class that represents a bank account. It contains fields, properties, and methods related to the functions needed to implement a bank account. A field represents storage of a particular type of data. One field might store the name of an account holder, for example. Properties are similar to fields, but properties usually provide some kind of validationwhen data is set or retrieved. You might have a property that represents an account balance. When an attempt is made to change the value, the property can check to see if the attempted change is greater than a predetermined limit. If the value is greater than the limit, the property does not allow the change. Methods represent behavior, such as actions taken on data stored within the class or changes to the user interface. Continuing with the bank account example, you might have a Transfer method that transfers a balance from a checking account to a savings account, or an Alert method that warns users when their balances fall below a predetermined level.
CLR Execution Model Compilation and Execution of a .NET Application When you compile a .NET application, it is not compiled to binary machine code; rather, it is converted to IL. This is the form that your deployed application takes—one or more assemblies consisting of executable files and DLL files in IL form. At least one of these assemblies will contain an executable file that has been designated as the entry point for the application. When execution of your program begins, the first assembly is loaded into memory. At this point, the common language runtime examines the assembly manifest and determines the requirements to run the program. It examines security permissions requested by the assembly and compares them with the system’s security policy. If the system’s security policy does not allow the requested permissions, the application will not run. If the application passes the system’s security policy, the common language runtime executes the code. It creates a process for the application to run in and begins application execution. When execution starts, the first bit of code that needs to be executed is loaded into memory and compiled into native binary code from IL by the common language runtime’s Just-In-Time (JIT) compiler. Once
Table 1-1.Representative .NET Namespaces Namespace Description System This namespace is the root for many of the low-level types required by the .NET Framework. It is the root for primitive data types as well, and it is the root for all the other namespaces in the .NET base class library. System.Collections This namespace contains classes that represent a variety of different container types, such as ArrayList, SortedList, Queue, and Stack. You also can find abstract classes, such as CollectionBase, which are useful for implementing your own collection functionality. System.ComponentModel This namespace contains classes involved in component creation and containment, such as attributes, type converters, and license providers. System.Data This namespace contains classes required for database access and manipulations, as well as additional namespaces used for data access. System.Data.Common This namespace contains a set of classes that are shared by the .NET managed data providers. System.Data.OleDb This namespace contains classes that make up the managed data provider for OLE DB data access. System.Data.SQLClient This namespace contains classes that are optimized for interacting with Microsoft SQL Server. System.Drawing This namespace exposes GDI+ functionality and provides classes that facilitate graphics rendering. System.IO In this namespace, you will find types for handling file system I/O. System.Math This namespace is home to common mathematics functions such as extracting roots and trigonometry.
Table 1-1.Representative .NET Namespaces Namespace Description System.Reflection This namespace provides support for obtaining information and dynamic creation of types at runtime. System.Security This namespace is home to types dealing with permissions, cryptography, and code access security. System.Threading This namespace contains classes that facilitate the implementation of multithreaded applications. System.Windows.Forms This namespace contains types involved in creating standard Windows applications. Classes that represent forms and controls reside here as well. The namespace names are self-descriptive by design. Straightforward names make the .NET Framework easy to use and allow you to rapidly familiarize yourself with its contents. Reference Types and Value Types Types in the .NET Framework come in two varieties: value types and reference types. The primary difference between value types and reference types has to do with the way variable data is accessed. To understand this difference, a little background on memory dynamics is required. Application data memory is divided into two primary components, the stack and the heap. The stack is an area of memory reserved by the application to run the program. The stack is analogous to a stack of dinner plates. Plates are placed on the stack one on top of another. When a plate is removed from the stack, it is always the last one to have been placed on top that is removed first. So it is with program variables. When a function is called, all the variables used by the function are pushed onto the stack. If that function calls additional functions, it pushes additional variables onto the stack. When the most recently called function terminates, all of its variables go out of scope (meaning that they are no longer available to the application) and are popped off the stack. Memory consumed by those variables is then freed up, and program execution continues.
