RU beehive logo ITEC dept promo banner
ITEC 325
2019spring
ibarland

Project
requirements

For this course, teams of four students will design a web application. Some examples of the sorts of things that can be done are:

You encouraged to suggest your own projects, perhaps inspired by the suggestions above. However, your project must include the following features1:


Checkpoints include:

  1. (due Jan.31 (Thu) 23:59, one email per team.)
    Choose teams and projects.

    Choose one team member as liaison, who I’ll channel all communication through. The liaison should email me (as plain-text, not attachment):

    disclaimer: The liaison is not responsible for getting teammates to do their work, show up for meetings, etc.. The team lead (who is often also the liaison) should schedule meetings and coordinate with all members to help keep the project on track, but should not do others’ coding. One supporting role that can be useful is that of a sounding board: a team member might sit and code while another member is sitting next to them, and can bounce ideas, design decisions, and questions off of their teammate.

  2. (due Feb.1412 in class, hardcopy and D2L-group, one submission per team, .pdf or even .txt)
    Submit a proposal (10%): You aren’t locked in by this proposal; it is intended to make sure you have thought through what you need to do, and that the entire group understands exactly what functions will be implemented.
  3. (due Feb.2720 23:59)
    Have a working git account for your project, with a Readme file, and every team-member having pushed at least one change. Add ibarland@radford.edu as a team-member to the git project.

    The Readme (presumably on bitbucket.org or github.com): Have a README file for the project, which includes the team name and their members (as well as usual README info: a quick overview of the project, what sub-directories include what major components of your project).

    And of course, Everybody should be pushing their changes to this repo regularly. Members who have commited nearly-no code which is included in the final version may be subject to significant loss of points.

  4. (due Mar.2614 hardcopy in class, and on D2L (.txt or .pdf). One report per-team (not per individual).)
    Progress report I (2.5%):
    A short-but-specific written summary of progress and problems-encountered (less than one page), including which team-members have been contributing to which component(s).
  5. (due Apr.11Apr.02) Prototype (10%), with a class demonstration (10%):
  6. (due Apr.1625 hardcopy in class, and on D2L (.txt or .pdf). One report per-team (not per individual).)
    Progress report II (2.5%):
    A(nother) short-but-specific written summary of progress and problems-encountered (less than one page), including which team-members have been contributing to which component(s).
  7. (due Apr.30 (Tue)May.07 (Tue) 12:30 (our final-exam slot)) Final project (40%), with a class presentation (15%):
  8. (due May.0208 (Wed) 17:00, hardcopy under my door ) Peer evaluation (10%):
    Evaluate both other groups’ presentations, and your teammates. itec325 project feedback
Due dates are at the start of class, unless indicated otherwise.

Your grade will be mostly the same for all group members, with some variation based on the team feedback form. However: If the group concensus and/or git logs show that a member contributed very little (including not communicating clearly and professionally), that student’s grade might be given a lower score (even 0), if warranted. The converse is not true: if one student implements far more than their share of the project, they will not necessarily get significantly more points that others. (I do not want students to feel like they must be martyrs, to complete their group’s work.)


Archiving your project

The project-accounts will be cleared, a few weeks into the summer! If you want to keep a copy of your work…

If you archive your project, you might want to share your files with your teammates.


1 If you have an external client, their requirements trump my list. However, if you learn that there are features below that aren’t included at all, contact me before the proposal deadline, and we’ll work something out.      

logo for creative commons by-attribution license
This page licensed CC-BY 4.0 Ian Barland
Page last generated
Please mail any suggestions
(incl. typos, broken links)
to ibarlandradford.edu
Rendered by Racket.