Phase 3: Project Assignment-- Due no later
than May 6th, 12:15pm (Final exam day).
In
Phase 3
you will work in a new two person team -- the team assignments are
listed
below. There is no collaboration allowed between teams EXCEPT for the
following condition:
- Each
team member in the Phase 3 team may consult during
the April
20/22 lab session
times only with their Phase 2 team member for
clarifications on their Phase 2 code. The Phase 2 teams are now longer
your assigned teams -- so do not expect your Phase 2 partner to help
fix your code during Phase 3.
All code
from Phase 2 must be
made
available to both team members in the Phase 2 teams.
Make sure you
distribute the
workload evenly -- uneven workloads are being taken into account during
grading. Finally, we require that you migrate all your code to
the SEAS machines -- this is a requirement for Phase 3.
More details on
Phase 3 requirements are described in the project
details page posted earlier Phase 1; there are also details provided
for the submission
requirements.
You need to schedule
a demo by emailing the instructor -- some generic time slots will be
posted below (after team assignments). The schedule of your demo will
be on a first-come first served basis -- so those who wait until the
last minute will end up scheduling a demo earlier!
The "deliverables" for Phase 3 are: (a) Written report describing your
implementation -- the tables, the normal form, the application code
logic, the User Interface, (b) the code for the project, and (c) a demo
to be conducted with the instructors (sign up for the time slots or
schedule a time). To test your applications, you
must populate the database with enough sample data and must make sure
that you are able to demonstrate the entire workflow -- for example, in
application (A) a new applicant will apply, their application will be
processed, the reviews will be entered, and a final decision will be
made. Make sure you do NOT use the following ID numbers and names in
your testing since we will require specific information about these IDs
for our testing:
111-22-3333 John Coltrane
222-22-3333 Miles Davis
333-22-3333 Bud Powell
444-22-3333 Stan Getz
Submission
Instructions (also posted on blackboard): You must submit one
zip file containing your report and code. The zip file must be named
team<team-number>-phase3.zip. For example, if you are in Team 8
then your submission will be named team8-phase3.zip. The deadline
for submission is 11am on May 6th, with NO late acceptance (you will
receive a zero on the project phase 3 if you do not submit by this
time).
Additional
Instructions
for completing Phase 3 - Make sure you read through these carefully and
follow the instructions.
- The specifications listed on the project
details page should serve as a minimum -- you need to use your basic CS
and logical analysis skills to
figure out other design decisions. Making unreasonable, or unrealistic,
assumptions will cost you points.
- Go over the entire project (i.e., both applications)
and figure out how you will integrate the two modules. Remember that in
the end you are "delivering" one large system (CS-ARGS).
- In the report, you MUST describe
what was involved in the
integration process (of applications A and B), and the role of each
team member.
- Make sure you test your
application to check the entire
workflow. As a starting point, refer to the Phase 2 evaluation
that was discussed with you (and comments posted on your report). Go
through the steps listed in the
evaluations -- checking for the different types of errors.
Follow the entire workflow process -- i.e., go step by step to check if
the two applications are fully integrated and working correctly. For
this, you also need to refer to the project details page to see all the
specifications. Testing and evaluation during Phase 3 will be a lot
stricter than Phase 2 -- i.e., any deviation from the workflow (and
project specifications) will result in your project being penalized.
You must fix all the errors and problems that we pointed out during
Phase 2 -- the team member responsible for the particular application
will be held accountable. Since Phase 2 has officially ended, you have
to fix your own code -- you cannot ask your Phase 2 team partner to
help fix the code.
- During
testing, make sure you
use valid email addresses --
specifically, you must use only your email address to send messages
from the application.
- Make
sure you do not use banners
from other commercial sites (for
example, GW Banner system) -- this is a copyright infringement.
- On
the main page of your
application you must clearly state (at the
bottom of the page) that this is a class project
- Your
project must be implemented on the SEAS machines -- this is a
requirement.
- You
should populate your
database with a number of sample cases as described in the additional
instructions for submission.
- Make
sure that you write down the
password/ID numbers/Names etc. for this test data BEFORE you start your
demo.
IMPORTANT:
Please
follow these
additional instructions
before you submit your final project. We require this in order for us
to do a complete testing of your project -- you will get points taken
off if you do not follow these specifications.
Teamwork Requirements:
The requirements
also include meeting your project team partners in the lab
sections (or the lecture sessions that may be dedicated to project work
--which will be announced on the course announcements site) --
failure to turn up for lab and meet with your team partner
implies a zero on the
project Phase 3.
NO EXCEPTIONS. If you have trouble communicating with your project
partner, you have to inform the instructor asap -- waiting until the
due date will not excuse you from submitting the final work product.
PHASE 3 TEAMS:
- Team 1: Jacob Alperin-Sherif, Madina Ayapbergeva
- Team 2: Anugna Kasireddy, Alex Florescu, Arielle Ridolfino
- Team 3: Gulsum Tursumbayev, Riva Anand
- Team 4: Samy Bahra, Patrick Thompson
- Team 5: George Rivara, Ben Clarke
- Team 6: Jan Rubio, Rachel Cheuk
- Team 7: Mike Harkness, Denise Rockwell
- Team 8: Matt Harlan, Ben Meier
- Team 9: Ed Robinson, Nathaniel Ford
- Team 10: Mark Zulkiewicz, Sam Sternberg
- Team 11: Ryan Johnson, Chris Brese
Demo
Schedule Time Slots:
You must specify a list of preferred time slots (email the
instructor)-- first come, first served. I will update
this schedule periodically, so keep checking this to figure out your
final demo time slot. Demos will be held in Tompkins 411.
May 6th:
- 11:30--12noon:
- 12:45--1:15pm:
- Team 4: Samy, Patrick
- Team 8: Matt, Ben
- 1:15--1:45pm:
- Team 10: Mark, Sam
- Team 5: George, Ben
- 1:45--2:15pm:
- Team 11: Ryan, Chris
- Team 9: Ed, Nathaniel
- 2:15--2:45pm:
-
Team 2: Alex, Anugna, Arielle
-
Team 7: Mike, Denise