| CS 327 - FALL 2002 PROJECT WEBSITE |
|---|
1) This is the last week we have to do anything on this project this semester. We want to show that we've done things iteratively, so I want new revisions of almost all documents for the end of Elaboration2. I've sent out reviews of a lot of the documents. I'd like these to be used in writing up the revisions. I also want the reviews themselves to be put on the web site so the prof can see we did do some sort of review stuff. Anyone who has a document I reviewed, write a revision for it. This must be done by FRIDAY MIDNIGHT in order to give the web people time to put it on the web site.
2) Discuss reviews that people've done on our project. Strengths and weaknesses should be discussed briefly and recorded in an informal report so the group next semester can do better. I'm only looking for some description of the major issues (1-2pg writeup). Need a volunteer for this--someone who KNOWS they'll have enough time. This must be done by FRIDAY MIDNIGHT in order to give the web people time to put it on the web site.
3) We don't have a Test Plan. We should have a Test Plan. Someone should write up a test plan. Anything is better than nothing, and nothing is what we have. Don't worry much about how it looks, since we won't use it this semester, and people next semester don't have to use it if they don't like it. Need a volunteer for this--someone who KNOWS they'll have enough time. This must be done by FRIDAY MIDNIGHT in order to give the web people time to put it on the web site.
4) David and Ross - Document Reviews. Please get these written up in a presentable form for posting on web site. Doesn't need to be fancy. Just unambiguous as to what it is and what it says. And one or both of you review the Software Dev Plan please? This must be done by FRIDAY MIDNIGHT in order to give the web people time to put it on the web site.
5) Web site still needs work! This is literally what we're "turning in" to the TA. The documents page looks good, but there are still the issues with the other pages. Sandra (and Brian if he has time) - Continue working on web site. - Copy people-role table from software dev plan onto front page - Get rid of the announcements section. Cleanup FAQ. - Include review text on the documents page: Sid's, David's and Ross's. - The Software Architecture document is an Elaboration Phase doc, not inception. - Get new revisions of documents onto site.
6) Further coding - We ran outta time, and it's unclear whether we're ahead or behind schedule, because I never defined how much the "prototype" would do (in the Software Dev Plan). Technically, a prototype is throw-away software that's written just to illustrate that it can be done and how it could look. A "skeleton" is what we have, which is what I said we'd do in Construction1. Looks like I need to edit the Software Dev Plan again. =) As far as further development goes, I think we shouldn't try to put in more functionality this semester. I want documentation more than code, at this point.
7) Tasking Summary: Abhay - Vision and Use case revisions Brian - Use Case Model revision, Use Case revisions, web site if he has time Sandra - Web site David - write reviews Jianmei, Sonia - Software Arch Doc revision (probably only 1 of Jianmei/Sonia needs to do it?) Ross - write reviews, help Jianmei and/or Sonia with Software Arch Doc revision Sid - Software Dev Plan revision, Iteration plans, Iteration Reports
8) Other Q&A?
9) Conclusion: We WILL have a short meeting next Monday (standard time) just to discuss status. Also, we might have things to talk about how/when to actual present the project to the TA and/or Prof.