College Course Evaluation

1. Team 9 Evan Pittfield epittfie@uncc.edu Joshua Shinn jshinn5@uncc.edu Farooq Yousuf fyousuf@uncc.edu Jerry Hung chung7@uncc.edu College Course Evaluation

2. At the end of each college semester, each student is required to fill out a course evaluation. The course evaluations are used to collect anonymous data that helps determine learning and effectiveness of teaching throughout the student population. Currently many colleges choose to deploy this evaluation on paper. Not only is the paper based method environmentally unfriendly, but many problems occur. For instance, typically one student is responsible for delivering all of the evaluations at the end of class. This may cause a problem because the paper evaluations might be lost or never delivered. Additionally, the evaluation process takes away class time. Team 9 is designing a digital software implementation of the already existing paper college course evaluation. This software can be used anonymously, and will save both paper and valuable class time. It is expected that this will make more efficient use of the college course evaluation system. This software will run mainly on a Windows based platform including XP and Vista. Introduction

3. Grand Vision • The system will allow students to anonymously submit evaluation scores and comments using a web-based interface which would be integrated into the universities Banner system. • The system will allow professors/administrators to view aggregated course evaluation data and perform analysis of evaluations through comparison of other course evaluations across the department, college, and university. • The analysis would be in the form of tabulated data or generated graphs. • The system will allow professors/administrators to compare both current and historical data for specific courses with specific properties such as the number of enrolled students. • The system will be operated from a single central control program interface. • The system will contain a database driven login. • The system will create a fast and concrete software solution with minimal hardware requirements necessary to field a viable product. • The system will include a date window allowing the Administrator and/or instructor to select a time frame to compare courses within. • The system will be database driven. • The system will allow the Administrator to compare courses based on attributes, such as Professors who are considered tenure, or lecturers. • This system will allow the Administrator and/or the instructor to compare courses based on attributes such as gender, college class(Fre, Sop, Jun, Sen) and age of students within course • The system will be open to students beginning the first day of class, and will be changeable throughout the semester until the last day of finals.

4. Scope • The system will allow students to anonymously submit evaluation scores and comments using a web-based interface which would be integrated into the universities Banner system. • The system will allow professors/administrators to view aggregated course evaluation data and perform analysis of evaluations through comparison of other course evaluations across the department, college, and university. • The analysis would be in the form of tabulated data or generated graphs. • The system will allow professors/administrators to compare both current and historical data for specific courses with specific properties such as the number of enrolled students. • The system will be operated from a single central control program interface. • The system will contain a database driven login. • The system will create a fast and concrete software solution with minimal hardware requirements necessary to field a viable product. • The system will include a date window allowing the Administrator and/or instructor to select a time frame to compare courses within. • The system will be database driven. • The system will allow the Administrator to compare courses based on attributes, such as Professors who are considered tenure, or lecturers. • This system will allow the Administrator and/or the instructor to compare courses based on attributes such as gender, college class(Fre, Sop, Jun, Sen) and age of students within course • The system will be open to students beginning the first day of class, and will be changeable throughout the semester until the last day of finals.

5. Scope • The system will allow students to anonymously submit evaluation scores and comments using a web-based interface which would be integrated into the universities Banner system. • The system will allow professors/administrators to view aggregated course evaluation data and perform analysis of evaluations through comparison of other course evaluations across the department, college, and university. • The analysis would be in the form of tabulated data or generated graphs. • The system will allow professors/administrators to compare both current and historical data for specific courses with specific properties such as the number of enrolled students. • The system will be operated from a single central control program interface. • The system will contain a database driven login. • The system will create a fast and concrete software solution with minimal hardware requirements necessary to field a viable product. • The system will include a date window allowing the Administrator and/or instructor to select a time frame to compare courses within. • The system will be database driven. • The system will allow the Administrator to compare courses based on attributes, such as Professors who are considered tenure, or lecturers. • This system will allow the Administrator and/or the instructor to compare courses based on attributes such as gender, college class(Fre, Sop, Jun, Sen) and age of students within course • The system will be open to students beginning the first day of class, and will be changeable throughout the semester until the last day of finals.

6. Scope • The system will allow students to anonymously submit evaluation scores and comments using a web-based interface which would be integrated into the universities Banner system. • The system will allow professors/administrators to view aggregated course evaluation data and perform analysis of evaluations through comparison of other course evaluations across the department, college, and university. • The analysis would be in the form of tabulated data or generated graphs. • The system will allow professors/administrators to compare both current and historical data for specific courses with specific properties such as the number of enrolled students. • The system will be operated from a single central control program interface. • The system will contain a database driven login. • The system will create a fast and concrete software solution with minimal hardware requirements necessary to field a viable product. • The system will include a date window allowing the Administrator and/or instructor to select a time frame to compare courses within. • The system will be database driven. • The system will allow the Administrator to compare courses based on attributes, such as Professors who are considered tenure, or lecturers. • This system will allow the Administrator and/or the instructor to compare courses based on attributes such as gender, college class(Fre, Sop, Jun, Sen) and age of students within course • The system will be open to students beginning the first day of class, and will be changeable throughout the semester until the last day of finals.

7. Scope • The system will allow students to anonymously submit evaluation scores and comments using a web-based interface which would be integrated into the universities Banner system. • The system will allow professors/administrators to view aggregated course evaluation data and perform analysis of evaluations through comparison of other course evaluations across the department, college, and university. • The analysis would be in the form of tabulated data or generated graphs. • The system will allow professors/administrators to compare both current and historical data for specific courses with specific properties such as the number of enrolled students. • The system will be operated from a single central control program interface. • The system will contain a database driven login. • The system will create a fast and concrete software solution with minimal hardware requirements necessary to field a viable product. • The system will include a date window allowing the Administrator and/or instructor to select a time frame to compare courses within. • The system will be database driven. • The system will allow the Administrator to compare courses based on attributes, such as Professors who are considered tenure, or lecturers. • This system will allow the Administrator and/or the instructor to compare courses based on attributes such as gender, college class(Fre, Sop, Jun, Sen) and age of students within course • The system will be open to students beginning the first day of class, and will be changeable throughout the semester until the last day of finals.

8. Scope • The system will allow students to anonymously submit evaluation scores and comments using a web-based interface which would be integrated into the universities Banner system. • The system will allow professors/administrators to view aggregated course evaluation data and perform analysis of evaluations through comparison of other course evaluations across the department, college, and university. • The analysis would be in the form of tabulated data or generated graphs. • The system will allow professors/administrators to compare both current and historical data for specific courses with specific properties such as the number of enrolled students. • The system will be operated from a single central control program interface. • The system will contain a database driven login. • The system will create a fast and concrete software solution with minimal hardware requirements necessary to field a viable product. • The system will include a date window allowing the Administrator and/or instructor to select a time frame to compare courses within. • The system will be database driven. • The system will allow the Administrator to compare courses based on attributes, such as Professors who are considered tenure, or lecturers. • This system will allow the Administrator and/or the instructor to compare courses based on attributes such as gender, college class(Fre, Sop, Jun, Sen) and age of students within course • The system will be open to students beginning the first day of class, and will be changeable throughout the semester until the last day of finals.

9. Summary of overall scope • Preserve all the required functionalities. • No graphs, tables or pretty pictures. Instead we will use labeled text boxes for data. • We will not be able to integrate into Banner due to limited access to the university systems. • Secured login will be done by simulation (hard- coded data).

10. What Team 9 will complete for an “A” grade. • The system must allow students to anonymously submit evaluation scores and comments using a web-based interface. • The system must allow professors/administrators to view aggregated course evaluation data and perform analysis of evaluations through comparison of other course evaluations across the department and college • The system must allow teachers/administrators to compare both current and historical data for specific courses with specific properties such as the number of enrolled students. • The system must include a date window allowing the administrator and/or instructor to select a time frame to compare courses within. • The system must be operated from a single central control program interface. • The system must mock a web-based simulation system involving the pre-integration of each student’s courses. • The system must allow the administrator and/or instructor to compare courses based on attributes such as gender, college class (Fre, Sop, Jun, Sen) and age of students within course. • The system must be open to students beginning the first day of class, and must be changeable throughout the semester until the last day of finals.  • The system must contain the option for student to resume/edit a partially completed evaluation. • The system must simulate a secure login.

11. What Team 9 will complete for a “B” grade. • The program must offer all the core functionality that is required in this project. • It must be a less polished version and must not include all the “luxury” features of the Grade A version. Some of these features include: course over time comparison, departmental comparison, must not include all attributes, or the time available for the evaluation to be open. • The program must not support saving of partially completed evaluations.

12. What Team 9 will complete for a “C” grade. • This version of the program must be fully functional but only for one of the user types; the student, instructor or the administrator. • The system will not include any carefully designed interfaces. • At this minimum the system should at least simulate a secure login.

13. Sample interfaces and features

14. Student Evaluation question interface

16. Administrator(Dean) Interface

18. Use case for Administrator (Dean) Compare different sections Compare scores <<extends>> <<extends>> Compare different instructors Login <<extends>> Administrator Compare to previous course scores Filter results <<extends>> Filter by demographic <<extends>> <<extends>> Filter by faculty Filter by class

19. Instructor Interface

21. Use case for Instructor Compare different sections Compare scores <<extends>> <<extends>> Compare to previous course scores Login Instructor Filter results Filter by demographic <<extends>> <<extends>> Filter by class

22. Student Interface

24. Use case for Student Retrieve saved forms <<extends>> Fill out evaluation form Login Select Course <<extends>> <<extends>> Student Submit form anonymously Save evaluation form

25. Plans for Final Prototype • The system will have functional interfaces. • The system will implement/simulate a data driven login. • The system will simulate a save/return and edit functionality. • The system will lock if the date/time is not properly met • The system will generate statistical data into labeled text boxes. • The final prototype will have a user manual for the customer

26. methods for making progress on the project • Team 9 follows the waterfall model + increments. • This model fits perfectly with the teams skill set and availability • “Grow, don’t build, software.” --Fred Brooks, Mythical Man Month

27. Examples of how team 9 has used the waterfall model to make progress. • team 9 re-vamped D1 in order to better understand requirements and constraints. • team 9 has met to discuss what tools and skill sets each team member contains. • team 9 has done “unofficial” homework by playing/experimenting with unexplored software such as Microsoft Visual Studio 2008

28. Progress Schedule/Model