Agenda

1. Jim will ask Scott (if participating) to update the workgroup on core activities.
2. Continue discussion of baselines. Jim has added several scenarios to discuss.

Minutes

Regrets:

Attendees: Alanna Zito, John Crouchley, Sandeep Kohli, Steve Speicher, Jim Conallen

1. Steve gave an update of Core activities this week.
2. John proposed a topic for today, and if we get through enough of our continuing discussions from last time, we'll discuss it. In lue of that we can start an email thread through the workgroup mailing list.
3. Jim walked the group through a list a scenarios that the baseline work would benefit.
4. John discussed some scenarios and functionality that SystemArchitect? already supports. The idea of locking resources was discussed. Jim asked if locking was soemthing we should consider here, as it would certainly support the review and approve scenario. However John pointed out overall baselines was the only way to be sure of complete closure.
5. John and jim discussed a scenario around data models, and the concept of what exactly is a resource was brought up. Steve wondered if the diagram or the table/column was a directly referencable resource. John indicated that in System Architect even a parameter in a method of a UML class is a directly addressable resource.
6. When locking resources, the resource is locked and all its children. However things like diagrams do not have tables or UML classes as children.
7. It was suggested that our service providers should be able to provide a list of all the baselines that a resource is part of, and that a service provider can provide a list of all the baselines that it is managing.
8. Jim started to explain the context manager diagram in the context of a scenario that needs to follow resource links in a context.