Notes from face to face meeting of the 2009 Roadmap Development working group in Chicago September 29, 2009
Discussion of the architecture diagram (under background)...
All agreed that this kind of diagram is very useful. The discussion led to the realization that we need several diagrams to serve the interests of our community:
Marketecture diagram - This is intended to be a high level conceptual diagram that represents some combination of current reality and desired future. The current diagram is our marketecture diagram. (Cath added - need to update this diagram to add a box for "Rice Future Rich UI Framework" in the Rich User Interface Services layer. This box got left out when KNS was pulled off to the left side of the diagram.)
Deployment diagram - This is a technically accurate diagram that represents how Rice components are actually deployed. It needs further description but will probably show both physical and logical deployment.
Service diagram - Needs further description
Library version schematic - This will show the actual versions of all the libraries in use (dependencies and original code).
There was a lot of discussion about component modularity. Though there wasn't one clear outcome from this discussion, it was clear that everyone involved favored increased modularity with regard to Rice components. With that in mind, we should be careful about prioritizing and implementing new capabilities and/or enhancements that increase tighter coupling or make it more difficult to decouple over time.
There was a fair bit of discussion about releasing Rice in modular ways. It would increase flexibility to be able to release just KIM, or just KEW without a complete release of Rice. The down side to release modularity is that it would take more effort in QA and would potentially increase complexity in other ways.