Team Projects

Version 11/15/17

Rulebook

On the change of day from 11/11 to 11/12 [midnight Sat 11/11 aka 12:00am Sun 11/12] a forum entitled Project Selection will open. To select your project topic, post to that forum one message with subject your topic. Here is the way this will work after that:

  1. The first poster for a topic will be designated team admin.
  2. If there are enough people choosing that topic for two teams, the first two posters will be the admins for the two teams, and team membership will be even/odd.
  3. By midnight on 11/12, the teams will be designated and each team will have a group with with discussion board in which the team should conduct all of its business related to the project, including communication and file exchange.
  4. Once the teams are specified, it will be the admin's job to organize the effort for the project.
  5. ALL intra-team communication and interaction is required to be in the open, accessible to all team members and the course instruction staff and within Blackboard. This is an honor-code-level rule, violation of which will affect the project grade for the entire team.

Assessment

Assessment will roughly 50% on the quality of the product, 25% on project documents, and 25% on effectiveness as a team member and/or team admin. (Details forthcoming.)

Common Deliverables

The following deliverables are common to all group projects:

makefile       # builds all project object code and executables
manual.txt     # operating instructions for software [team document]
report.txt     # overview of team and project [team document]
log.txt        # personal log for team member [individual document]

(Each project has additional deliverables specific to the project.)

Procedural Requirements

  1. The official development | testing | assessment environment is g++ -std=c++11 -Wall -Wextra on the linprog machines. Code should compile without error or warning.

  2. There is a project-specific deliverables configuration file for each project. Be sure to submit with that argument named explicitly.

  3. Each member of a team submits all project deliverables

  4. With the exception of log.txt, deliverables submitted should be identical across all team members. log.txt is the individual team member's personal log for the project.

  5. File report.txt should explain how the software was developed, what responsibilities each team member had, and how it was tested. File manual.txt should explain how to build and operate the software. Generally, it is the team admin's responsibility to create these two documents, with input from all team members if needed.

    6. Warning: Submit scripts do not work on the program and linprog servers. Use shell.cs.fsu.edu to submit projects. If you do not receive the second confirmation with the contents of your project, there has been a malfunction.

Links to project docs

  1. GREP
  2. Pattern Search
  3. Random Graphs
  4. String Sorts
  5. Weighted Graph Search