-
Notifications
You must be signed in to change notification settings - Fork 5
ExceedVoting
Jim Brucker edited this page Apr 15, 2015
·
35 revisions
We are going to vote on the class projects using ExceedVote!
- There are 2 rounds of voting: Preliminary and Finals.
- In the Preliminary Round, teams are divided into 2 divisions. In the Final Round, the top 2 teams from each division (based on preliminary voting) will compete.
- Before voting there will be a "Preview Period" so everyone can try out the apps. Everyone should login and try each of the 4 apps you will be voting/rating.
- During Voting, login to each of the 4 apps (URLs are posted here) and submit your votes/ratings. Make exactly the same votes/ratings on all 4 sites, so that the results reported by each app should be identical.
- Help each other by reporting bugs and problems. Report bugs as issues on the team's Github repo, and report problems, experience, impressions on https://groups.google.com/forum/#!forum/ssd2015 (Google Group).
| Division | Contestants | Voters |
|---|---|---|
| Division 1 | Saint4 | Everyone in GG, TheFrank, Malee, JDED, |
| Manat | and Saran, Thai, Keeratipong, Jim. | |
| 2Big2Slim | ||
| FatCat | ||
| Division 2 | GG | Everyone in Saint4, Manat, 2Big2Slim, FatCat, |
| TheFrank | and Saran, Thai, Keeratipong, Jim. | |
| Malee | ||
| JDED |
Please see the Google Group and your email for login credentials to use in voting. Email Jim for a file containing logins and passwords.
| Dates | Activity | Description |
|---|---|---|
| before 18 Apr | Prepare app for try-out. | Configure your application. Add contestants, voters, and voting criteria (see below). OK to deploy now. |
| 18-19 April | Preview | All apps are up and running with mock voting. Voters login to each app and try them. Report problems. |
| 19-20 April | Prepare for Prelim Voting | Reset vote counts, deploy bug fixes. |
| 20 April 9:00 | Start of Preliminary Round of Voting | Voting by Division. Everyone votes for 4 contestants, and you have to vote (identically) 4 times! Report bugs and problems. |
| 20 April 18:00 | End of Prelim Voting | Voting is closed. Results are available on each of the apps. Compare results for all 4 apps in same division (should be same). Send voting logs to instructor and TAs. |
| 21 April | Finalists Announced | Finalists from each division announced. |
| 21 April | Prepare for Final Voting | Finalists configure your applications. Add contestants, voters, and criteria for final round. |
| 22 April | Final Preview | Apps are up and running with mock voting. Voters login to each finalist and try them. |
| 23 April (Lab) | Demo | Demo admin interface in lab. Optional demo mobile version of your app. |
| 23 April (Lab) | Final Voting | Vote for finalists during lab. |
| 23 April 10:00 | Final Voting Closed | Voting closed. Results compared across the 4 finalist apps. |
| 23 April | Retrospective | Discuss and record experience in using ExceedVote, to help improve actual ExceedCamp voting. |
Each team, prepare your application for the preliminary voting.
- Add contestants (4 ExceedVote teams), voters, and voting criteria.
- Use the table above for what contestants (Teams) and voters you need to add.
- Test that you can deploy your application. Test that people can login.
- Please keep a log of all logins and votes. You can do this by configuring the Logback tool included with by Play.
- Post your application URL and how to contact a "sysadmin" (for login problems) on class wiki. Be careful about posting email addresses.
- Best app for use at ExceedCamp.
- Ease of use - how easy is to understand how to vote and actually vote? How easy is navigation? Is there clear feedback on what you have done so far?
- Reliability/Stability - can you smoothly login and complete voting without information loss? Does app prevent submission of invalid data?
- Completeness - does it have the features required by customer?
- Security - does application prevent unauthorized access? Can you logout of application? Hint: Look at the project's routes file on Github. Try to directly access URLs without logging in.
- Quality of UI - does it have consistent look? Can use on different size screens? Is important info clearly displayed? Is navigation provided and clear (not using browser "back" button).
The Preview Period is like viewing the projects at ExceedCamp.
Contestants:
- Deploy your applications and enable login & voting.
Everyone:
- Login to each app you will be voting for. Navigate around and try voting/rating. (Votes won't be counted now.)
- If you find a bug, open an issue on the team's Github project.
- If you can't login/vote, report it on the Google SSD2015 Group and also contact the team's "sysadmin". Email jim and TAs if the team doesn't fix the problem.
- Try to break the app. Access URLs without logging in, enter invalid data, vote after the preview period is over. (Hint: look at the project's
conf/routesfile to find what URLs is uses.)
Contestants:
- Reset all vote counts. (remove votes from preview period)
- If necessary, deploy bug fixes from the preview period.
- Keep a log (log file or database entries) of who logged in and who voted.
- Don't deploy any bug fixes after voting starts, unless people really can't login/vote.
Everyone:
- Please login to each of the 4 apps in division where you are a voter, and make the same votes/rating on each app. This is so we can compare results.
- Example: login to ExceedVote A and vote for A, B, C, and D. Then login to ExceedVote B and vote for A, B, C, and D, casting the same votes/ratings as you did on the previous site (ExceedVote A). Repeat this process for ExceedVote C and D.
- Please record your votes and ratings on paper, in case we need to check the accuracy later.
- Report bugs as issues on the team's Github project. Report problems and feedback to Google Group.
Each team
- Post the voting results. You should have a URL for this.
- Send a summary of the login data (log file or data from database) showing who logged in/voted to TAs.
- Archive the Results. Create an archive (backup) of the voting results (database) and record of logins. This is one of the customer's requirements.
- The top 2 contestants from each division will be posted for final round.
- In case of a tie, the instructor and TA votes will be used to break the tie.
Finalist Contestants:
- Add the final 4 contestants to your app.
- Add the entire class and TA/instructor as voters, reset the voting criteria.
- Update your application URL and "sysadmin" contact information on wiki.
Contestants:
- Start you apps. Allow logins and mock voting.
Everyone:
- Login to the final 4 apps and try them out.
- Even if you have used the app before, the finalists may have fixed bugs, so you should try each app again.
- Report bugs as issues on team's Github project. Give feedback on Google Group.
This will be done in lab on 23 April.
- Teams can demo the administrative interface to class. This is an important feature we couldn't test before.
- If you have a mobile interface, you can demo that, too.
- Everyone login to all 4 finalist apps and vote.
- Please cast the same vote using each of the 4 finalists' ExceedVote apps.
- Review the results in class.
- Discuss experience and how to make actual voting at ExceedCamp smooth and efficient.
- Incorporate ideas into your next (and last) round of software development.