Team 3 Assignment 1: Requirements and Design

Your team will receive the updated documents and black box specifications. The team must do the following:

• Read each of the following items:
  • Requirements document
  • Black box (check against requirements)
  • Risks document
  • Design document
  • Post-increment 2 report
  • All source code from increment 2
• Select the goals for increment 3
  • Update the requirements document and black box as needed in this context
  • When updating the requirements, take any recommendations from the first team into account
• Determine a division of responsibilities for increment 3
• Update the design document as needed
  • Again, take recommendations into account from team 2

Increment 3 Timeline

• April 7-9:
  • Updates to documents
  • Setting goals
  • Organizing team resposibilities
  • Prototyping
• April 14, 16: Code inspections, in class
• April 21: Code freeze; demonstrations in class
• April 23: Report from third team due

Deadlines

• All documents and code should have been read
• Each team will give an oral presentation on the state of the project:
  • Goals currently met
  • Noteworthy bugs
  • Goals for increment 3
    • Be prepared to justify feasability
  • State of the source code
    • What are the best aspects of the code?
    • What are the worst aspects of the code?
    • Are the contracts usable?
      • Are they complete?
      • Are they unambiguous?
      • Do they need additional formality?
  • Primary unresolved risks (consensus opinion of the current team)
  • System design
    • For each element of the design that is not changing, state why it seems to be working well
    • For each element of the design that is changing, justify the change
  • Division of labor

• All documents (updated or not) should be re-submitted through Sauron
  • Requirements document
  • Black box
  • Risks document
  • Design document (including division of responsibilities)
  • A document containing a review of the current state of the source code from increment 2, including:
    • the information from Thursday's presentation about the source code and design
• Implementation should be under way; be prepared for code inspection