Specification 1

Last modified: Oct 22, 2:45 pm

Due date changed to 6:00 pm, Friday, Oct 27.

Each iteration of the project specification should contain the following information:

• Text description. This should identify the capabilities that will be explored in this prototype iteration, and provide sufficient detail regarding the implementation of those capabilities to permit coordination among team members. A sketch of the evaluation strategy that will be used for this prototype iteration should also be provided. The description should also include the task assignments for each team member for this prototype iteration. At a minimum, the following roles should be specified:
  • Architect
  • Programmer (there should typically be several programmers, and specific tasks should be assigned to each.)
  • Integrator
  • Evaluation
  More than one role can (and often should) be assigned to an individual. Each team member should seek to gain experience in multiple roles over the course of the project, and no member should serve as a programmer less than twice.
• Visual layout. Typically a sketch using powerpoint or any other drawing tool is an effective way of conveying the intended visual layout. Dynamic behavior such as resizing need not be depicted, but should be explained in the text description.
• Functional view. One or more powerpoint slides (or output from any other drawing tool) can be used to present the use case diagram. This may be accompanied by one or more use case narratives and/or by one or more use case scenarios if that is useful.
• Static View. One or more powerpoint slides (or output from any other drawing tool) can be used to present the class diagram. This may be accompanied by one or more object diagrams if that is useful.
• Dynamic View. One or more powerpoint slides (or output from any other drawing tool) can be used to present one or more sequence or collaboration diagrams (which you choose is up to you, and you may use both if that is helpful) .