2021/4/16 CSE 3901 Project 6
web.cse.ohio-state.edu/~sivilotti.1/teaching/current/3901/labs/project6.html 1/2
Help BuckeyeLink Map Find People Webmail CSE Portal Search Ohio State
CSE 3901: Web Applications
Autumn 2020
Project 6: Ruby on Rails Project
Ruby on Rails Tutorial
Complete chapters 2, 3, 5, and 6 of the textbook. (If time permits, try the main bits of chapters 7 and 8 too.) See the syllabus for notes
on textbook access.
Everyone in the group should complete this part of the project. Collaboration is permitted and encouraged! You do not need to submit
anything for this part of the project, but completing it as soon as possible is highly recommended as it will help in completing the
second part (i.e. the final project, below).
Final Project: Audience Evaluation of Presentations
Background
In classes with presentations, such as CSE 3901, evaluations of these presentations by audience members (ie other students in the class)
can be a useful component of the grading rubric. The feedback from these evaluations is useful to the instructor for assigning a score to
an individual student, as well as to the students for receiving constructive criticism from their peers.
A web application would streamline the collection, collation, and analysis of these audience evaluations.
Required Features
1. The instructor/TA should be able to create presentation events for which evaluations can then be submitted.
2. An audience member should be able to submit scores and comments for a presentation. The application should support multiple
presentations over the semester (eg, different presenters or multiple presentations by the same presenter).
3. An administrative interface should give a useful view of the scores and comments submitted for a presentation. This view should
support the instructor's need to assign grades based on these evaluations.
4. A presenter should have access to the feedback provided by their audience.
Extensions
The following list is not exhaustive. The goal is to create as useful an application as possible, so the following are some challenges that
could be addressed to that end. You are encouraged to think of other improvements that would be useful.
1. Authentication/login. Evaluations should be connected to an authenticated user, preventing forging of evaluations.
2. Class roster. The instructor or TA should be control membership by, for example, populating the class with names and email
addresses from a roster.
3. Prevent self-evaluation. Presenters (for either individual or group presentations) should not be allowed to submit an evaluation of
their own work.
4. Admin dashboard to monitor submission of evaluations and simplify sending reminders or managing evaluations that are never
submitted.
5. Changing enrollment. Students might add or drop the course and this should be handled cleanly by the tool.
Submission
Update: Submit your final project via the usual mechanism: push a tag ("submission") to the github repo. The deadline is Saturday
December 5 at midnight. Also, don't forget to complete the peer evaluation survey!
There are 2 separate submissions for the final project, with different due dates.
2021/4/16 CSE 3901 Project 6
web.cse.ohio-state.edu/~sivilotti.1/teaching/current/3901/labs/project6.html 2/2
1. Beta version release. By the due date of the final project (as indicated on the class web site), you must push a tag called "v1.0" to your
github repo. Over the next several lectures, each group will have about 13 minutes to present their project to the class. In addition to
giving a client-view demo (_i.e._, from the end-user perspective), this presentation should also describe the technical details of the
design from an implementer's perspective (database schemas, architecture, etc). Your git repository should include documentation, the
slides to be used for the class presentation, as well as the application itself.
1. Updates. You may continue to push new versions (tagged appropriately, e.g., "v2.1") up until midnight, Sunday December 6th. Include
a file called RELEASE-NOTES.md that indicates the major changes between this version and the earlier beta version. Note: Your final
project github repos will become public _after_ the beta release. Thus, you will be able to borrow aspects of other groups' projects for
improving your own (and vice versa of course). If you make use of any work from other groups, you must include specific attribution in
your README file. Your final project grade will be 70% based on the beta release and 30% on this final version.
This page is maintained by: Department of Computer Science and Engineering
395 Dreese Lab, 2015 Neil Avenue, Columbus, OH 43210, Phone: (614) 292-5813 / Fax: (614) 292-2911
If you have trouble accessing this page and need to request an alternate format, contact [email protected].

欢迎咨询51作业君