Team 2 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 1 report
  • All source code from increment 1
• Select the goals for increment 2
  • 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 2
• Update the design document as needed
  • Again, take recommendations into account from team 1

Increment 2 Timeline

• March 3, March 5:
  • Updates to documents
  • Setting goals
  • Organizing team resposibilities
  • Prototyping
• March 7-15: Spring break
• March 17: Team meetings, in class
• March 19, 24, 26: Code inspections, in class
• March 31: Code freeze; demonstrations in class
• April 2: Report from second 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 2
    • 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?

• 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 1, including:
    • the information from Tuesday's presentation about the source code
    • the infromation from Thursday's presentation about the design
• Each team should give an oral presentation concerning the following:
  • 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
  • Any issues unanswered on Tuesday