Git vs PTC Windchill RV&S

• Ability to create branches off current releases to modify code that can be tested in a separate environment.
• Each developer had their own local copy of branches so it minimizes mistakes being made.
• Has a user-friendly UI called Git Gui that users can use if they do not like using the command line.
• Conflicts are displayed nicely so that developers can resolve with ease.

Read full review

• PTC Integrity helps engineers write better requirements. Better written requirements mean less issues for warranty.
• PTC Integrity provides a database that is virtually limitless. Product size or scope no longer has to be an issue.
• You don't have to save.....PTC Integrity does this for you.

Read full review

• There can be quite a number of commands once you get to the advanced features and functionality of Git. Takes time to master.
• Doesn't handle static assets (ie: videos, images, etc.) well. Although in the recent years, new functionality has been introduced to address this.
• Many different GUIs, many people (including myself) opt to just use the command-line.

Read full review

• It can be overwhelming with the number of tabs, functions and ways to achieve the same result. The average user may struggle with learning the tool.
• The text editing in Integrity is weak and does not provide many options. Because of this, many user decide to use MS word instead, to document requirements.

Read full review

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

Read full review

• MKS Integrity has proved to be particularly useful in the software development process by increasing employee effieciency
• MKS integrity has also made software development a very efficient process and makes feature releases and bug fixing a lot easier
• In addition to the above, our organization has been able to support manufacturing easily by reverting to a previous software version in case of an emergency.
• It has also led to faster time to market for new products.

Read full review