Notes for 4/21/09

• Summary of Issues
• Issue with Deployment (Erika and Joe have conversation)
• Setting up war file and deploying and making notes of where they downloaded links
• Joe is helping Erika setting up GWT
• Change Cypal to point to plug in GWT Library
• Took them a while to find GWT hosted mode connection
• Neil and Erika are using version 3.3
• Issue with finding root
• Instructions on how to build a full set of Java Docs.
• Somehow only one was created.
• Something might not have went right
• We will make sure we have the full set of JavaDocs for release 2
• Project> Generate JavaDoc
• On unix it might be a simple command like JavaDoc name of file.
• Might need to click next and tell it which files to generate for.
• Which built in svn are we using?
• Subclipse
• Less pre built things and the more they can generate the better
• When something does break it is good to refresh xml files
• A backup zip is a good idea for this.
• Locking isn’t working in release 1 so there may be some interesting effects.
• Release 2 there is a lot of new features being added.
• Features
• Attributes
• Conditionals
• There could be a good about text
• like if all conditionals are true than result value will be used. If more than one all are valid. No amount of training will make them remember it
• Could you use tabs?
• Nevermind they want to see both at same time.
• Names for conditionals would be nice
• If totally different conditions it might be nice.
• Add to future work section if we don’t get around to it
• Use word removes rather than delete for everywhere.
• Make sure to do a sanity check pop up are you sure to delete an entity and all of its children.
• Add on nice to have list redundancy for delete.
• Change wording to be Add (on button) … because action should include save and cancel.
•  
• Decisions
• Might be useful for a web cast or detailed document for people who are using it
• Something live might be better
• Document may only be skimmed.
• PAETEC does a lot of Computer based training
• Maybe basic video and doing voice and saying to add this go here, etc
• After Release 2 there will be some issues still. We will continue to work on them.
• IS there a final date?
• Perhaps the Friday of week 10 5/15
• Probably won’t be a lot of changes between release 2 and this final release.
• Will there be availability?
• Yes
• That seems reasonable.
• The code will also have any missing comments at this time.
•  Keep something online with most recent deployment so there isn’t a major change or surprise.
• Make sure directions date and time is updated on midterm page.
• Plan a date to get a draft of the PPT to Sponsors and Nate
• We do not have a date. Lets plan one now…
• Set to 5/3/09
• Ask Vallino about expectations of presentation
• Usually it is more demo based and covers more outcomes and results.
• Less about process
• The cell phone was a nice basic product that is plausible without details.
• Run with that and add details to it.
• Post mortem
• Look at finals dates and come up with list of options for Post Mortem
• Monday of finals week is no go.
• Tuesday/Wednesday would be better
• On features and attributes make them questions/phrases
• Like apply to profitability?
• Look at spreadsheets and ask questions
• Make delete last on table. This way you only look at it if you need it.
• Make comparisons textual based
• Don’t bother with less than less than equal
• Less than
• Greater than
• Equals
• Config file is needed for Deployment

• Action Items (w/ person responsible and dues dates)
• Try and figure out System Property for XML file directory so it can be taken from config file.
• Fix Attribute errors
• Look into video instruction
• Find requirements of Presentation