Kyle:

5/1/2009

What we have done

• Created an easy reference summary of work
• Developed algebraic definition of application
• Explored applications as an algebraic field
• Built Java classes that correspond to application/application component definitions
• Built tools for mapping to and from Java application components and XML files
• Built tools for implementing algebraic operations on applications (add, multiple, subtract, divide)
• Explored Fowler's Analysis Patterns: Inventory and Accounting (chapt. 6)

Things we want to talk about

• Fowler's Analysis Patterns: Inventory and Accounting (chapt. 6)
• Differences between J2EE front-to-back layered architecture vs. OO class-based hierarchical architecture and their implications for patterns
• Do we need to extend our notion of components that comprise applications (i.e., UserTypes, DataObjects, Interactions, Relations)?
  • DataObject properties that include other DataObjects as type?
  • DomainObjects that don't correspond to a basic data type, have methods that apply to multiple DataObjects, include transactions?
  • Rules?
  • Triggers?
  • Registration and Notification?
• Balance between simplicity (what we now have, requiring some custom coding) and complexity (more complete, less custom coding, but more detailed specification)?
   
• Use a multiset/bag vs. set as the data type for components in Java algebraic operations implementations (to support field inverse operations)?