Algorithms and OOD (CSC 207 2014F) : EBoards
Primary: [Front Door] [Schedule] - [Academic Honesty] [Disabilities] [Email] - [Learning Outcomes] [FAQ] [Teaching & Learning] [Grading] [Rubric] - [Calendar]
Current: [Assignment] [EBoard] [Lab] [Outline] [Reading]
Sections: [Assignments] [EBoards] [Examples] [Handouts] [Labs] [Outlines] [Readings]
Reference: [Student-Curated Resources] [Java 8 API] [Java 8 Tutorials] [Code Conventions]
Related Courses: [CSC 152 2006S (Rebelsky)] [CSC 207 2014S (Rebelsky)] [CSC 207 2014F (Walker)] [CSC 207 2011S (Weinman)]
Misc: [Submit Questions] - [SamR] [Glimmer Labs] [CS@Grinnell] [Grinnell] - [Issue Tracker (Course)] [Issue Tracker (Textbook)]
Overview
How many teams?
- (The 11th team that appears in the distance table is switching conferences.)
What belongs in the I/O subsystem?
Read distances. Read dates of competition. Read restrictions on competition. Read anything else you think will be useful. Write schedule.
How do we know what file to read from?
Either you will prompt the user or the user will specify it on the command line.
Do we need to build a GUI?
No. A textual UI will suffice.
How should we submit our non-code materials?
In your GitHub repo. You can have a Markdown document or a Wiki post or ....