Notes for 2/03/09

• Summary of Issues
• What happens when you have a lot
• Live Search as a limiting factor
• There is a way to tie user input to buttons, so it will go to the next screen.
• All mandatory feature would be in the spreadsheet
• We know waive ability
• Profitability
• Commissions
• Ignore SRS model
• Remove SRS
• What is a system Product Catalog Template
• Change language
• It was a popup
• System creates business rule definition file
• Too many Attributes just there
• Add As a tree structure
• Min and Max as well as default value for conditional constraints.
• Constraint Checking
• We can’t validate constraints
• But what if list of values for an attribute
• The situation where constraints both are met wouldn’t have to be handled.
• Do we want to edit table
• Yes
• Provide this as a way to edit also.
• Have both for redundancy.
• Have this be more drastic changes, and the other UI for minor tweaks, etc.
• What do stakeholders want to see from us?
• If draft of presentation
• Conditional attributes
• SRS
• Template for Design
• Expectations?
• This template covers 90% architecture. Keep it as high level design.
• UML design is more design.
• Database views not really relevant.
• Gear toward API interfaces is geared toward other projects.
• GWT would be covered. Project Plan may have some information needed already.
• Testing may not have to be handled here, only technical info; due to Project plan and testing doc.
• Pick and choose what makes sense.
• Project Presentation
• Rehash project plan into PPT as overview. (bullet number 7)
• Make up own product, do not talk about specific process. Anything related to zip don’t talk. Anything in the PDF proposal
• Do not go overboard on Conditional attributes
• Say it’s supported, little 10-second blurb.
• UI stuff ok, but don’t explain why
• Default answer is “flexibility!”
• PAETEC has a holiday on the 16th.
• Don’t be surprised if we get asked to do something related to blueprint for PAETEC
• Decisions
• Remove locking of system from use cases
• Use Case for each major view. Everything non-standard. Intuitive we can leave blank.
• Attributes on conditional screen in tree form.
• We Do Min/Max’s on Constraints.
• Ctrl as pick a set Shift as select all between.
• Results should be same as regular attribute.
• We are not actually constricting attributes?
• Yes
• We now ever say ok here is this attribute value now.
• Have view visualization button.
• Each column is an attribute.
• Similar to split cell view in excel. 
• What would we have next week
• Fleshed out version of Constraint UI
• Reflect changes in UI with attributes
• Create attribute and add constraint to it or not
• Add a constraint to an Attribute.
• 25 mins to present, 5mins for questions.
•  “I think they plan for transitions. “
• Cards for mins left.
• Practice presentation first.
• Send a copy to Neil, Erika, and Nate.
• But down Java versions and GWT all that in design document.
• Be at PAETEC @ 4.

• Action Items (w/ person responsible and dues dates)

•  Remove System locking from Use Cases and add a textual requirement saying such
• Look into moving prototype in Blueprint
• Legend for Use Case levels
• Remove SRS model
• Look for file manipulation that system takes care of and remove it.
• Post Mortem in the 11th week.
• Use same time and day if possible.
• We go through a whole bunch of questions
• It’s like a meeting, but more reflective and we lead it.
• Create a Date and Time and send it out.
• Design/Architecture Document.
• Could talk about nitty gritty top bottom/ bottom top design.
  • Due Tuesday
• Send something Thursday saying this is where we stand and this what you can expect.
• Take a look at estimation document next week.
• Tom take a look at Java SVN library connectivity.