First of all let me congratulate you on the successful launch of version 2.0 of RTC and 1.0 JF. It is realy great work, thank you and all the Jazz Team.
The functionality of Rational Team Concert greatly overlaps with the ClearQuest and ClearCase. Why is it necessary to create a new product? Why not just release it as new versions of old? For customers, it could be easier to adapt.
What is the future of CQ|CC, how you see it?
Thank you.
As background, I work for IBM/Rational, participated in the design and construction of RTC from its inception, and among other activities, have been leading the teams building the "Connectors" between RTC and ClearCase/ClearQuest. Back in 1995, I joined Atria to work on ClearCase.
So why did we created a new product?.
Over the years we've observed that for large software projects, what mattered even more than point tool functionality was how well the different tools were integrated. More recently, as companies started focusing on agile development where single individuals perform multiple roles concurrently, the same became true for smaller software projects. So we put increasing amounts of efforts into integrating our tools. But we concluded that without a tool integration platform, there's only so far we could go (and in particular, the integrations were tool version sensitive, requiring upgrading the tools together, which is not something users wanted to do). And even with a tool integration platform which improved the level of integration of all the tools, we also concluded that the only way to get optimal integration is to also build the products specifically for that tool integration platform.
In addition, a requirement for ClearCase and ClearQuest has always been that they handle all SCM (software configuration management) and CM (change management) problems that our customers have encountered over the years, work on all hardware and OS platforms, and remain compatible with all previous versions we've released. But that breadth of coverage comes at a cost... both in performance and in ability to do all the new cool things that we and others have thought of.
So a few years ago, we started Team Concert, both to build the platform that we were going to use to improve the integration between all of our tools, as well as to build new instances of those tools that were designed to take optimal advantage of that new platform. And while we were building those new integrated tools, we were also free to focus those new tools on the most common problems and the most common platforms, since we had ClearCase and ClearQuest to back the new tools up with breadth of problem and platform coverage. The "Connectors" then plug ClearCase and ClearQuest into that platform, and into those new tools, so that a customer can use the new tools when appropriate, and use ClearCase and ClearQuest whenever they weren't. And the integration between all these tools were enhanced by the Jazz integration architecture (i.e. it was no longer an either/or... a customer uses whatever tools best solve their problems). And while all this is going on, we continue to invest heavily in enhancing ClearCase and ClearQuest (we have significantly more people working on ClearCase and ClearQuest than we do on Team Concert).
At any rate, that was the idea (:-). For some more perspectives on this question from some other folks, you can also listen to the webcast: http://www.rational-ug.org/webcastDetail?wid=74 [rational-ug.org].
As background, I work for IBM/Rational, participated in the design and construction of RTC from its inception, and among other activities, have been leading the teams building the "Connectors" between RTC and ClearCase/ClearQuest. Back in 1995, I joined Atria to work on ClearCase.
So why did we created a new product?.
Over the years we've observed that for large software projects, what mattered even more than point tool functionality was how well the different tools were integrated. More recently, as companies started focusing on agile development where single individuals perform multiple roles concurrently, the same became true for smaller software projects. So we put increasing amounts of efforts into integrating our tools.
But we concluded that without a tool integration platform, there's only so far we could go (and in particular, the integrations were tool version sensitive, requiring upgrading the tools together, which is not something users wanted to do). And even with a tool integration platform which improved the level of integration of all the tools, we also concluded that the only way to get optimal integration is to also build the products specifically for that tool integration platform.
In addition, a requirement for ClearCase and ClearQuest has always been that they handle all SCM (software configuration management) and CM (change management) problems that our customers have encountered over the years, work on all hardware and OS platforms, and remain compatible with all previous versions we've released. But that breadth of coverage comes at a cost... both in performance and in ability to do all the new cool things that we and others have thought of.
So a few years ago, we started Team Concert, both to build the platform that we were going to use to improve the integration between all of our tools, as well as to build new instances of those tools that were designed to take optimal advantage of that new platform.
And while we were building those new integrated tools, we were also free to focus those new tools on the most common problems and the most common platforms, since we had ClearCase and ClearQuest to back the new tools up with breadth of problem and platform coverage. The "Connectors" then plug ClearCase and ClearQuest into that platform, and into those new tools, so that a customer can use the new tools when appropriate, and use ClearCase and ClearQuest whenever they weren't.
And the integration between all these tools were enhanced by the Jazz integration architecture (i.e. it was no longer an either/or... a customer uses whatever tools best solve their problems). And while all this is going on, we continue to invest heavily in enhancing ClearCase and ClearQuest (we have significantly more people working on ClearCase and ClearQuest than we do on Team Concert).
At any rate, that was the idea (:-). For some more perspectives on this question from some other folks, you can also listen to the webcast: http://www.rational-ug.org/webcastDetail?wid=74 [rational-ug.org].
Much more readable that way.
"Spock, did you see the looks on their faces?"
"Yes, Captain, a sort of vacant contentment."
RTC vs CQ and CC (Score:1)
Re:RTC vs CQ and CC (Score:1)
Re: (Score:1)
As background, I work for IBM/Rational, participated in the design and construction of RTC from its inception, and among other activities, have been leading the teams building the "Connectors" between RTC and ClearCase/ClearQuest. Back in 1995, I joined Atria to work on ClearCase.
... both in performance and in ability to do all the new cool things that we and others have thought of.
... a customer uses whatever tools best solve their problems). And while all this is going on, we continue to invest heavily in enhancing ClearCase and ClearQuest (we have significantly more people working on ClearCase and ClearQuest than we do on Team Concert).
So why did we created a new product?.
Over the years we've observed that for large software projects, what mattered even more than point tool functionality was how well the different tools were integrated. More recently, as companies started focusing on agile development where single individuals perform multiple roles concurrently, the same became true for smaller software projects. So we put increasing amounts of efforts into integrating our tools.
But we concluded that without a tool integration platform, there's only so far we could go (and in particular, the integrations were tool version sensitive, requiring upgrading the tools together, which is not something users wanted to do). And even with a tool integration platform which improved the level of integration of all the tools, we also concluded that the only way to get optimal integration is to also build the products specifically for that tool integration platform.
In addition, a requirement for ClearCase and ClearQuest has always been that they handle all SCM (software configuration management) and CM (change management) problems that our customers have encountered over the years, work on all hardware and OS platforms, and remain compatible with all previous versions we've released. But that breadth of coverage comes at a cost
So a few years ago, we started Team Concert, both to build the platform that we were going to use to improve the integration between all of our tools, as well as to build new instances of those tools that were designed to take optimal advantage of that new platform.
And while we were building those new integrated tools, we were also free to focus those new tools on the most common problems and the most common platforms, since we had ClearCase and ClearQuest to back the new tools up with breadth of problem and platform coverage. The "Connectors" then plug ClearCase and ClearQuest into that platform, and into those new tools, so that a customer can use the new tools when appropriate, and use ClearCase and ClearQuest whenever they weren't.
And the integration between all these tools were enhanced by the Jazz integration architecture (i.e. it was no longer an either/or
At any rate, that was the idea (:-). For some more perspectives on this question from some other folks, you can also listen to the webcast:
http://www.rational-ug.org/webcastDetail?wid=74 [rational-ug.org].
Much more readable that way.