Notes for 5/5/09

• Summary of Issues

• Release 2
• Did get the build this morning
• Started a bunch of notes. They are building locally and running locally.
• Was it refreshed from last build?
• Yes
• Joe -  Usually it means something happened with the xml files
• Erika’s comments
• Open Catalog when editing an entity when adding a feature: Why is there two separate buttons for add product and add business rules?  This is not the same as creating a refrence, but from a user perspective. Keep it as “Add” for the user it is the same. Perhaps say “add” instead of create and link or attach instead of add.
• Is the conditional field necessary?
• It doesn’t matter if it is a conditional, the user doesn’t know, its no special entity.
• There is one exception that is being thrown and caught, showing up in the gwt log, that occurs when saving. On save entity. 
• Erika copied this exception and will send it to us.
• When having anything with Multiple attributes there are several that are MRC NRC, unless this done  in the description there is no way to know which one is which.  This is so when looking at summary they can see more and not have to navigate inside and not see the others.
• Features attributes those extra variables, should at least show whether it is MRC, NRC, recurring price or cost. 
• For features showing whether is required or not.
• For Attributes should be pricing,  maybe value type.
• Way may need to send more information  (parameter info)
• Table version of values is something to be done later, but seeing
• Need to look at error during discussion with Erika and neil.
• Looking at known defects
• Did not know about the conditions. We need to go through these sections. There must have been sections that were unchanged.
• Can we fix deploy it somewhere?
• Yes we do it
• Or do a war files as we get updates with location for properties files.
• We can uploaded it the web server and Neil and Erika can download it.
• We have a lot to demo and features, so time is an issue.
• Unit tests Erika hasn’t seen it or run it.
• Add info about it  in release notes.
• Technical report should stand by itself, read as Valino would read it.

• Decisions

• View a feature instead of saying pricing have all the parameters too. The pricing title doesn’t match the what was there. It needs to be more descriptive. It doesn’t have to do with pricing, but it is whether the actual feature is optional, required.
• It should be reworded as “Is Feature required?”.
• The important part is the label.
• Future work section if we don’t get around to it
• MMF should be MMF %
• The rest should be apply to blank, or Is waivable?
• Pricing should be pricing type.
• PPT
• Steal text from poster
• Combine first two slides
• But these the same and add functionality to them next to them.
• Add xml to Architecture slides
• Change the Diagram to be like poster
• Edit File System to be File system
• Rename what when poorly something more positive… things to improve on.
• Add blueprint to requirements in what went well.
• Maybe be more specifice about what documents we need to update
• Instead of intergrate current system say business process. It is not a software system to intergrate with.
• User’s aren’t going to know what result type is,
• Use value type instead of result

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

• Technical Report Due Thursday /Friday
  • Who Rob/Whole team
  • Due Thursday by midnight
• Fix Poster
  • Who: Mark and Rob
  • Due: Tuesday
• Fix lingering bugs and continue testing
  • Who: Tom and Joe
• When: By Next Thursday