List view
Submit the URL for a 5 minute, audio narrated, video demonstration of your final system. Your demo shall not be longer than five minutes. You can use screencast-o-matic.com, …., or if you are using a Mac, QuickTime, to capture your screen to video. You need to demonstrate the functionality described below. The video must be mp4 format or a YouTube video, and publicly accessible. If the TA and I can’t access it, we can’t grade it. • A one-page pdf document convincing us that your system is correct. That is, how did you test your system and what were the results? Not only correctness, but is your event planner useful? • A link to your documented source code in your repository. Show the TA how each team member made substantial contributions to the repository. • Each team member turns in the same pdf document, same link to the repository, and same link to the video demo.
No due date•1/2 issues closedThis check-ins depends on the approach your team adopted. You’ll need to convince the TA you are making progress. One way to do that is show how many of the user stories you have implemented, and/or how many of the RFC sections you’ve implemented (see below). There are some interesting things to be done with “location” and “geographic position” that involve maps, best ways to get from event to event, …
Overdue by 5 year(s)•Due by July 30, 2020•4/4 issues closed8: The third check-in is worth 5 points. You will demonstrate to the TA that: • you developing and performing test cases as you are developing code. If you aren’t doing TDD (test driven development), you must convince the TA that you have a process of demonstrating correctness • you have functioning code that does substantially more than it did for the first check-in. In particular, you must demonstrate a user interface for an event creation system that uses menus and checks input for validity (i.e., no 30 February events, no events that end before they start, …) • you have a plan for implementing recurring events (see below)
Overdue by 5 year(s)•Due by July 16, 2020•12/12 issues closedAt least minimally functioning code that does something: You must demonstrate code, even if it is just print statements, that generates a .ics file for a simple, single occurrence event: Study for exam, 10am-1pm HST, 13 August 2020, in Hamilton Library. You must then demonstrate that the calendar program of your choice (say, google calendar) successfully reads and processes your .ics file. • Assuming you are taking an agile approach, your user stories. • A sketch of the user interface. • Your current Kanban (or whatever your team decides) board.
Overdue by 5 year(s)•Due by July 2, 2020•5/5 issues closed