Project

General

Profile

Meeting Week 5

  • Class Meeting
    • Schedule: when is prototype? Answer: "you tell me"
    • Document reviews: specify what role Stuart should play, what are we looking for?
    • Reviews in general: why? What makes a good one? How can we get good reviews?
    • Active reviews. Have reviewer apply their specific expertise. Ask specific questions. Give a due date. Follow up with questions.
    • Next week: progress reports
      • Guidelines to be posted
      • 20 minutes should be enough
      • Describe project goals, key deliverables
      • SPMP, SRS, prototype
      • DELAYED UNTIL FEB 23
    • Action items
      • Proposal ASAP
      • Delivery plan for the next week, need by Sunday
  • Team Meeting
    • Agenda
      • Architecture specifics
      • Meet more often? (X)
      • Status (X)
      • Plan for presentation (X)
      • Document reviews: how, when (X)
      • Define an iteration (X)
  • Presentation
    • Do we need a demo? We have one, may as well show it off.
    • Content: more fleshed-out arch, demo, talk about SRS and SPMP content
  • Document reviews (all documents)
    • Leave comments, even if it's just "this looks good"
    • If changes are to be made, document owner sends email
    • Once all team members sign off, deliver to Stuart for review with Redmine issue
      • Need to define objectives, questions, role, etc.
    • SRS is for first system, vision doc is for family
  • Last Iteration (W5)
    • Arch. sketch
    • Started commonality analysis, fairly rough at this point (storage API level)
  • Next iteration (W6)
    • Existing documents need review (everyone, by Sunday)
    • Submit docs to Stuart (Authors, by Monday night; choose an appropriate role for him to play)
    • Back-end comm. analysis (Jesse)
    • Bounds of commonality. List back-end services that are covered. (Jesse)
    • Front-end comm. analysis (Ian)
    • Review/assist comm. analysis docs (Gabriel)
    • Controller arch. (Gabriel)
    • System generation/tools (Gabriel)
    • Finish vision document (stop generating new concrete examples), examples of what won't be included (Ben)
    • Update vision doc with excluded examples (Ben)
  • W7
    • Presentation
      • Current demos as fallback, if no production code ready
  • Next meeting agenda (after class, 2/16)
    • Iteration review
    • Iteration planning
  • Action items
    • Placeholder versions thru end of 556, rename to match week #s (Ben)
    • Deliverable dates attached to versions (Craig)