Much of the OSLC value comes from "swapping out" providers--if I consume the OSLC interface, I can use any CM tool that provides the interface. But what thinking has been done around simultaneously consuming multiple providers? Here's a few examples:
a) A large project has multiple component development groups. The requirements for the project are managed in a single place, but some component groups use RTC for defects, some use Rational ClearQuest, and some use Rational Change (or add any other OSLC CM provider)....Since a requirement can span components, how does the requirements tool link to all the defects against that requirement from these various providers? b) An organization has an independent product testing group. Each product development group has its own test group internally, but before a product can be released, it must be passed on by the independent group. A development group has a test plan in one QM OSLC provider, and the independent group has a test plan in a different provider's tool. How can the project manager know the status of the full testing effort across both tools? c) A complex project has multiple subcomponents that are different enough that they require different estimation models. So there are estimates from multiple OSLC providers for parts of the project. How can the project management tool "see" those estimates from different providers? d) A worker is working on multiple projects, and gets task information from multiple tools. How can all those tasks be organized in a single place? (this should sound familiar!) It will always be the case that an organization's tool infrastructure requires one tool to "know about" multiple providers of the same OSLC resource types. Do we have any thinking in general of how that should be handled? Andy Berner Lead Architect, ISV Technical Enablement and Strategy IBM Rational Business Development 972 561-6599 [email protected] Ready for IBM Rational software partner program - http://www.ibm.com/isv/rational/readyfor.html
