Com S 362 --- Object-Oriented Analysis and Design

	HOMEWORK 5: TEAM PROJECT INCEPTION PHASE AND USE CASES
		 (File $Date: 2003/02/26 21:57:23 $)

Due: problem 1 by February 17, 2003 at 11AM,
     problem 2 by March 5, 2003 at 11AM.

READINGS

Read chapters 4-7 of Craig Larman's book Applying UML and Patterns
(Second edition, Prentice-Hall PTR, Upper Saddle River, NJ,
2002). Also read chapters 2 and 3 of Martin Fowler with Kendall
Scott's book UML Distilled (Addison-Wesley Longman, Inc., Reading, MA,
2000).  Finally, as an example look at the web page for the StickSync
project:

  http://www.cs.iastate.edu/~cs362/sticksync/


1. (15 Points) [Team information]

Your team for the semester project can have either 3 or 4 members.
Have one team member send an e-mail to

   cs362s@cs.iastate.edu

with the subject:

   Our team for the Com S 362 semester project.

In the body of the email please include the following text, formatted
exactly as follows, which will go on a course web page to provide
access to team projects:

   <DT> short title of your project
   <DD> team member 1's name, team member 2's name, ...
        <A HREF="http://www.cs.iastate.edu/.../cs362/index.shtml">
	project web site</A>.

Please list the team members alphabetically by last name (e.g.,
"Zachery Antz, Yolanda Bull, ..."). You can have each team member's
name linked to their homepage if you wish, but that isn't
necessary. Fill in the correct short name of your project, and the
right web site URL.  Leave the HTML tags and the words "project web
site" alone.

2. [Project Inception Phase]

This problem is to do the inception phase of your semester-long team
project.  You and your team will produce the documents appropriate for
the inception phase.  The deadline is near, because inception is not
supposed to last too long.  We are specifying the documents required
in some detail, and perhaps requiring more than necessary, to provide
you with experience with such documents.  You may base your documents
on a solution to homework 2 if that is appropriate, but you will also
need, for example, to provide an initial set of use cases.  In
particular we require (see Larman pages 37-38):

  a. (30 points)
     a project vision (see Larman section 7.4-7.5)

  b. (10 points)
     a start of the glossary (see Larman 7.6-7.7)

  c. (30 points)
     a supplementary specification (see Larman 7.2-7.3)

  d. (15 points)
     a risk list (see the StickSync example)

  e. (70 points)
     an initial use-case model (see Larman chapter 6)

The use case model must include at least one fully dressed use case
(see Larman's section 6.6), two casual format use cases, two brief
format use cases, and a list of all of the other use cases.

You can also include other documents (such as a business case,
iteration plan, or a phase plan) at your option.  But these aren't
required and you should only do them if you and your team feel that
they add value.

Your documents must be available (in HTML) on your project's web site.
You can use the web formatting from the StickSync project (see
homework 2 for how to get the StickSync example files), and we
especially recommend that for the use cases.

For this problem, hand in:

  - a printout of the web pages for parts (a)-(e) above, and

  - a filled out and signed copy of the course's "Certification of
    Individual Contribution and Understanding Form".  Note that all
    team members must individually sign this form.

You can find the certification form in 3 formats from the course web
pages at the URL: 

  http://www.cs.iastate.edu/~cs362/docs/

or on the department machines in the directory

  /home/course/cs362/public/docs/

The certification form must be printed and signed, you cannot turn
that in by email.

(In the future we might neglect to mention the certification form, but
you must do it for each team homework anyway.  The certification form
is only needed for each homework, not for each problem on each homework.)