Notes for 3/24/09

• Summary of Issues
• Technical report - Look at PAETEC requirements
• Presentation
• Is two weeks enough for presentation and paper
• Push back of release 1 makes Erika nervous, but is ok with schedule change.
• Sequence Diagram
• It is a merge of two diagrams.
• Lack of complicated SVN diagram
• Would like to see one more diagram of getting list of products from catalog.
• Entity
• Sends a list of strings over to UI, and not the entity.
• Concerned with Wave-ability and Specific Feature/Attribute.
• Feature would know how to populate the list of Strings
• This should be clearer in design document.
• Doesn’t think there is a problem with bridging layers more, but make sure to explain how all information gets passed around clearly.
• Ints being passed around
• May want enumerations, Worried about case statements appearing everywhere
• Presentation
• Plan to talk for 15 min discussion
• Still Presentation (Not a Power Point)
• Important to cover what Project is
• Cover who we are
• What we have been doing (explain not just coding, explain we have been soliciting requirements)
• Be at PATEC @ noon.
• We have whiteboard if we need to use it.

• Decisions
• Add Non Negotiable Dates (or distinction) in schedule
• Look into enumerations instead of Ints
• Update Erika and Neil with information on Sever Communication

• Action Items (w/ person responsible and dues dates)
  • Add The detailed elements to Attribute and Feature in the Schema but not Design Diagram
    • Who Tom
    • When ASAP  (By Thursday)
  • Add List of next available space in Schema
    • Who Tom
    • When By This Weekend
• Add new Sequence Diagram
  • Who: Mark
  • When: ASAP ( By Thursday)