Deliverables from the first team meeting and work assigned there. All due as soon as you can get them done - some today, all by Thursday October 7 if possible. If not, the team schedule should show when they will be ready.

In the meanwhile, each of you should go to sourceforge, click on New User via SSL and set up a sourceforge account. Tell your team leader your sourceforge login name so s/he can add you as a member of the sourceforge project I will set up for your team. Team leaders should send me their sourceforge login names so I can add them!

• Zero^th draft of a project web page, on which to post everything. (Put this in one of the team's public_html directories for now. It will move when the unix sysadmin creates the appropriate groups and directories.)

  All work in progress should be publicly accessible on this page. That applies to each of the items discussed below.

  Inform the class when the page is up, and when significant changes (new links, redesign) happen there.

  You might want to look at the project pages from my classes last year and the year before. They're not perfect (nothing is) but they may suggest things you want to imitate in time. But don't spend time right now on web design. Just make a place to put the information that needs to be public.

  Note: although you are likely to have a project webmaster, all postings on this page are the collective responsibility of the team.

• Draft of letter (email) to the customer. Introduce yourselves. Say politely but not effusively how pleased you are to be working on this project. Start arranging the first meeting - ask for possible times, perhaps suggest some. Send the draft to me.

• Project name(s). You will need two - something memorable and pronounceable for the product you will build, another one short and easy to type and remember for your unix group and project directory and CVS tree. These two names may (but need not) be the same. You'll have to clear the first one with the customer (eventually) but he need not know anything about the second one. You should also probably Google the first one to see if it's already being used by someone (that can be OK - you just want to know). The second should probably be all lower case (unix convention).

  If you can't find the right name right away make a list of possibilities and try them out with your friends and your customer.

• A logo. Think about looking for one or designing one.

• Risk analysis. What are the major problems you foresee, and how might you go about preventing them?

• Preliminary thoughts on process: think about questions like: What kind of organization do you want? How will you divide responsibilities? How much XP do you want to do? How will you know that you are doing what you say you want to do?

• Preliminary assessment of software and hardware support you will need from the Department (not from your clients). Some projects may need a dedicated server. Others may need the .NET framework (available for installation on your own PCs if you need it). It's important to have this soon since there's sometimes lead time needed to get it from the lab staff.

• A short term schedule showing when each of these items will be completed, and who is primarily responsible for each. The schedule might even show when drafts should be completed and circulated, so that you don't arrive at the completion date with outstanding unresolved issues.

• Minutes from the first meeting.

• Other items that occur to you ...perhaps as a result of our class discussion.

Back to the CS681 home page.