Git vs. PTC Windchill RV&S

Git is by far the best Source Control Management Tool I've used. I would recommend it to anyone, whether it's an individual working on their own project, a small start-up company, or a huge organization with thousands of developers. Maintaining code via source control is absolutely mandatory for all developers everywhere.

Incentivized

We enjoy doing requirement mappings. The enhancement in transferring them between models is great. It is for innovation all the time a challenge to conduct them. We have two major scenarios for that task set. One is to integrate already well-validated models into greater sets. The other is defining totally new ones. We developed new strategies and refined the existing ones. We rate the synching requirement configurations as comfortable. The processes of synching the items back to the models. The major advantage is to optionally synchronize all-important and intended traceability relationships from Modeler so that both can be given the correct right the right group of uses while others only see the structures. We too prefer the handling of deletion and creation. It is a real advantage how the mapping and relation are implemented. The implemented integration to third-party tools for requirements definition and management is a plus. We like the profiling features and the high compliance to industrial standards as well as the module variability modeling.Windchill RV&S makes us perform better and let us take over control. It enhances our return-of-investment efficiencies to the top. The only drawbacks are the high skill levels needed and the necessary relation in businesses to make the profits. Another topic is the resources that are needed.

• Git is designed to work in a distributed manner, allowing each developer to run a local node that has full control of the project. Through this, the developer is able to merge his work with others on a main 'branch' & work in sync without having to worry about stepping on your other developers toes.
• Because Git has solved the software problem of dependency, users who commit code that needs to be deleted can just roll back to a restore point, saving precious development time & tons of headaches for Information Technology. This is also very helpful when cloning projects or creating new features on the current project.
• Git has a beautiful command line interface that is intuitive, easy to learn & extensible. You can also observe all the changes you have made in your project throughout the development with just a few simple commands. This diverse set of command-line tools is easy for the end user & very powerful.

Incentivized

• It allows the user the ability to link all aspects of the SDLC together so that there is only one source of documentation and information rather than having to search in multiple places.
• It is very customizable to suit a particular businesses needs.
• It is helpful for all areas of software development.

Incentivized

• Some of the commands are a little obtuse if you're not using a Git Client
• Since Git is so widely used in the development space, it's easy to believe that growth and innovation might become stale in the area of version control. Competition is sparse these days and I'm curious if this "Standard" is going to keep moving forward somehow.
• It's hard to fault a tool that is so ubiquitous and hardly gets in your way.

Incentivized

• Main trunk is not protected and has no pre-conditions before committing a fix or feature to it.
• Conducting reviews is not possible. there is no avenue for people to comment on a check in
• When working with multiple snadboxes, the client seems to freeze up and needs to be started.

Incentivized

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.

Incentivized

I do not make decisions on what tool my company uses. I am just the user of the tool and such decisions are not handled by me. If I were to make such decisions, I would definitely renew MKS, considering the amount of data we have stored in MKS and the current number of users who are familiar with the system

Incentivized

Git is easy to use most of the time. You mostly use a few commands like commiting, fetch/pull, and push which will get you by for most of time.

Incentivized

PTC Integrity comparatively could be considered a nice Source code management, Version controlling tool and could be compared with tools like StarTeam. If the integration to move/migrate code could be integrated into this tool, it would become an extremely powerful tool.

Incentivized

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.

Incentivized

PTC Integrity administration can be somewhat daunting. They have been able to help with every question that I have submitted. Their support website is very easy to understand and submit questions and their phone support is wonderful

Incentivized

It's easy to set up and get going.

Incentivized

I wasn't involved in implementation.

Incentivized

GIT being a widely used tool have better reliability than its peers and have stands out when we compare it on operational performance criteria. GIT with speedy and extensive branching capabilities have helped developers to use check in their code quickly and space efficient way. GIT have the facility to quickly fetch the complete repository on to your local system.

Incentivized

There are some tools which are available for free like GitHub. I've used StarTeam when it was a product of Borland, and while using PTC Integrity, I feel PTC Integrity has most of the features which were available in StarTeam. Although there are some other free tools like Tortoise SVN, it's always better to stick with tools which are licensed and supported in case of any issues/problems.

Incentivized

• 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.

Incentivized

• Better requirements through PTC Integrity - which will equate to better products and less warranty costs (very large savings).
• Better efficiency ....PTC Integrity can help keep track of a globally managed project structure. This will go far in helping keep repeat and duplicate efforts from happening multiple times.
• Better products for our customers through a more attentive corporate ear. PTC Integrity can help make customer wants and needs a reality.

Incentivized