Notes for 3/17/09

• Summary of Issues
• Design Document
• Description on The Diagram
• Export
• We don’t have requirements for it.
• Well we left it in there for your benefit.
• Any more diagrams or details?
• No,
• Erika only cares about time and how it works
• Subsystem level is a wall of text. I feel like we could change this.
• SVN 2.1.4 section could have more information here.
• It is a Crucial Part
• Note that diagram 3.1.3.2 how it relates (GWT, Big Picture, CatAsync)
• Entity manager will talk with svn system
• Entity is an abstract class.
• Entity diagram doesn’t show that enities can contain other diagrams.
• What about rules?
• Implementation of the enities themselves most likely.
• How do you go about creating a hierarchy?
• Add entity method would exist.
• All public methods should be handled at design level.
• What about getting other entities do to recursion?
• Thought about it, weighed pros and cons
• Could use some set, list, hash map and do a search.
• Maybe look into tree map for sorting.
• Tree could work really well.
• If we do a tree then a recursive tree down the tree.
• Which would be better getEntities() could return a  set.
• Saves different every time it could make versioning different, so when it is saved to xml it needs to be in some order so it doesn’t get completely messed up.
• How do we say get al product catalogs?
• We can say get type, get instance of.
• Sequence Diagrams will help to fill the gap of missing holes.  These should cover our base scenarios.
• Does The SVN need to know about the XMLHandler? No it probably just needs to know about the parser handler.
• If they were to put this into Oracle it would use “Hybernate?”
• It would use the Parser handler, but this is a file parser.
• If we want to leave it like this it is fine, but it is a bigger change for them. That is why an extra level is good. This wasn’t our requirement. 
• It might be ok just to have the Username as check in
• Not able to share password at all.
• Anonymous user is not a problem.
• If its data storage its one thing, but heap memory is another thing. Few hundred megs of file storage is fine.
• Our main concern is that there is no cap to number of file or size system. Cost a lot more to load into Java memory.
• How long will it take to check in and out?
• But if we don’t clear it… So we should clear it, leaves open the option later for them to not later.
• We were thinking of loading whole product Catalog. From User prospective. 
• One wait time is better than 20 when loading product catalog / products.
• Suggestion is stub out svn methods
• Acceptance testing issues
• We do same steps but go about it without the interface.
• We are going through the same steps as if we had a driver on top.
• Our Presentation @ PAETEC
• These are engineers.      
• This is our major
• This is our project  (Senior Project)
• They do not know
• They will be interested in technologies
• They will be interested in J Unit
• They will be interested in Blueprint.
• Concise! Short and Sweet.
• AWESOME IDEA!
• Film the system being used and talk about what is being doen as it is going in the background.
• Decisions
• Use term The Term ERD for our diagram.  Entity relationship Diagram
• Anything that we do that is related to design and not code should go into the Design Doc.
• This Relates to sequence diagrams.
• Add sequence diagram for 3.1.3.2
• For Diagram 3.1.4.2 add some distinction of lines, separate or add notes to explain.
• All public methods should be handled at design level.
• If set up as a tree being specific about parents and children helps. Entity could become confusing.
• Need to add a method that returns a list of entities (Product Catalogs)
• Look into loading of properties file.
• Properties.getProperties()
• Erika wants to see a sequence diagram for saving (with memory)
• Even if you pull whole thing into memory and the user doesn’t change anything you still need to resave it, and check it.
• Small set of users who use this
• Maybe 10
• Sequence Diagram about how we access SVN.
• JUNIT can do reports.
• Suggest just using Use Case. Why write 50 Use Tests.
• Moving Schedule to Excel
• Look into templates for this migration
• SPOLSKY
• So If we have as shortened meeting make them later so Neil and Erika can stay at work later.
• Week by Week basis. They will assume 4:30 unless agenda says something easier. 

Action Items (w/ person responsible and dues dates)

• Add sequence Diagrams to ( Entity)
  • Who: Mark
  • When: ASAP
• Research Collection Types for entity sorting
  • Who: Entire Team
  • When: 3/24/09
• Look into Properties file loading
  • Who: Joe
  • When: When he gets a chance (Sooner than later)
• Proof of concept of SVN
  • Who: Tom
  • When: ASAP
• Fix preformed
  • Who: Mark 
  • When: ASAP
• Move Schedule To Excel
  • Who: Robert Marinaro
  • When: Thursday Morning