| 1 | Begnoche | Noel |
dpp |
page |
| 2 | Terrell | Junuzovic |
sbs |
page |
| 3 | Olivier | Lee |
sbs |
page |
| 4 | Sidhu | Krishnan |
sbs |
page |
| 5 | Culp | Hansen |
sbs |
page |
| 6 | Pan | Zhang |
sbs |
page |
| 7 | Grace | O'Shea |
sbs |
page |
| 8 | Lu | Wu |
dpp |
page |
| 9 | Awasthi | Sommervoll |
dpp |
page |
| 10 | Cornell | Knott |
dpp |
page |
| 11 | Xu | Wang |
dpp |
page |
Deadlines
-
First release: Sunday night, April 2, 11:59 pm.
We will discuss it in class Tues. April 4.
-
Second release: Mon. night April 24, 11:59 pm.
-
Final demos: Beginning Tues April 25, continuing Thurs April 26
and Fri April 27.
-
Final information to hand in, all by Sunday April 30, midnight:
-
Please email me the time reports from your pair sessions.
Put them all in ONE file and send me one email for your group.
Title the email "Group NN, Mancala time report" where NN is your
group number.
-
Have your website updated with all final information.
Include code your developed (first and second releases
separately), original user stories, test cases, final presentation,
time reports, information of how to install your product.
Also include a final group report giving your impressions and
observations on developing this project with pair programming.
Stuff to be doing
-
For now, put your user stories on the website
(the originals you wrote, and a link to the common
ones we are now using)
-
Put some easy to find description of the technical infrastructure you
are working with (including dPP or sbs)
-
Continue to develop with regression testing, supported with good
comprehensive JUnit test cases.
-
Keep accurate time records... keep date, start time, end time for each
pair programming session you do. Keep notes on what general tasks you
worked on in each session.