A customizable database workflow application development and production system that provides better visibility and control. IBM Rational ClearQuest is change management software that helps improve developer productivity while accommodating the methodologies, processes and tools that best fit the project and the people on the team. It provides tools and processes used to maintain control of changes while catering to the diverse needs of the developer.
GIT is good to be used for faster and high availability operations during code release cycle. Git provides a complete replica of the repository on the developer's local system which is why every developer will have complete repository available for quick access on his system and they can merge the specific branches that they have worked on back to the centralized repository. The limitations with GIT are seen when checking in large files.
If you are familiar with IBM Rational Suite products, RequisitePro will add up due to the synergy between other components. Beyond that, if your business is not structured to an adequate development methodology or lacks the degree of maturity or necessary resources, probably RequisitePro does not add much value. If you work with developers in the requirements analysis, they probably prefer to use an SVN repository.
Performance can be an issue. Make certain the server is sized properly
There is a large difference in capability of the Thick Client Version compared with the web based version. Make certain each job function has proper access to be able to do what is required of them.
Learning curve is not too steep, but would suggest having someone with experience setup the repository. Highly suggest getting a contractor to assist to get the repository up and running.
Git has met all standards for a source control tool and even exceeded those standards. Git is so integrated with our work that I can't imagine a day without it.
Most likely as it's one of the powerful tools in the organization. We needed this tool to track all the process related documentation and also to capture signatures.
Please keep in mind that this all has to do with you you customize the user interface. It becomes very easy to house all of your requirements, but it may and can make life difficult for you if you do not think ahead of how you want the app to work and house your data
I am not sure what the official Git support channels are like as I have never needed to use any official support. Because Git is so popular among all developers now, it is pretty easy to find the answer to almost any Git question with a quick Google search. I've never had trouble finding what I'm looking for.
IBM has good support and knowledge base. With the wealth of information on their site and the support desk, we were able to quickly resolve issues. It is smart to build up a COE and a group that manages the software otherwise it is quick to be able to lose the knowledge as team members are assigned different duties
I've used both Apache Subversion & Git over the years and have maintained my allegiance to Git. Git is not objectively better than Subversion. It's different. The key difference is that it is decentralized. With Subversion, you have a problem here: The SVN Repository may be in a location you can't reach (behind a VPN, intranet - etc), you cannot commit. If you want to make a copy of your code, you have to literally copy/paste it. With Git, you do not have this problem. Your local copy is a repository, and you can commit to it and get all benefits of source control. When you regain connectivity to the main repository, you can commit against it. Another thing for consideration is that Git tracks content rather than files. Branches are lightweight and merging is easy, and I mean really easy. It's distributed, basically every repository is a branch. It's much easier to develop concurrently and collaboratively than with Subversion, in my opinion. It also makes offline development possible. It doesn't impose any workflow, as seen on the above linked website, there are many workflows possible with Git. A Subversion-style workflow is easily mimicked.
IBM clearquest would the BEST option if you are looking for managing change requests, managing project workflows, generating reports on status of requests. The reason being: cost, cost and cost. It almost handles everything that you would need for your project including bug tracking unless you want something really fancy (like HP QC) with a higher cost that supports a wide variety of needs which you might need to evaluate based on your project needs. For example, if you would be really making use of all those additional features provided by HP Quality Center. To be honest it depends on your project size, the skills of team members and of course budget!
Git has saved our organization countless hours having to manually trace code to a breaking change or manage conflicting changes. It has no equal when it comes to scalability or manageability.
Git has allowed our engineering team to build code reviews into its workflow by preventing a developer from approving or merging in their own code; instead, all proposed changes are reviewed by another engineer to assess the impact of the code and whether or not it should be merged in first. This greatly reduces the likelihood of breaking changes getting into production.
Git has at times created some confusion among developers about what to do if they accidentally commit a change they decide later they want to roll back. There are multiple ways to address this problem and the best available option may not be obvious in all cases.
IBM Rational ClearQuest has provided a workflow that works without unique software methodology. As a result we deliver complete software products to our clients in a 6 to 8 week development time frame.
As a result of our highly customized implementation, we have 8 resources supporting IBM Rational ClearQuest. Three of the resources are full time configuration management staff that administer and support the tool set and the other 5 are from the testing group that handle ClearQuest user support issues in addition to their testing duties.
