Apache Subversion is a version control option that is free to download and open source under the Apache 2.0 license.
N/A
PTC Windchill RV&S
Score 2.0 out of 10
N/A
PTC Windchill RV&S (formerly Integrity Lifecycle Manager of the Integrity suite) is an MBSE (model-based systems engineering) suite. The former Integrity suite contains an Asset Library which supports systems-of-systems approach to design (i.e. linking models into higher-level models that subsume them), a Process Director which is designed to articulate, manage and improve the design process, and a Modeler for visualizing and controlling the product design process. The Integrity suite is…
After Microsoft Visual SourceSafe was discontinued, we chose Subversion and it was a great choice. We were able to migrate to Apache Subversion very quickly and easily and benefited immediately from its non-locking workflow (SourceSafe required users to "lock" the file when …
Git has become the new standard of version control, with its support for distributed design. As a tool to manage and control versions, Subversion does it well, but Git is the future.
We used Visual SourceSafe before SVN many years ago and we chose SVN at that time mainly because it allowed us to do collaborative work on the same source code. It also had improved conflict resolution when doing code merges, blaming changes etc, which improved the speed of …
Git is probably the biggest open source rival to Subversion. It's designed for distributed development, an environment I'm not very familiar with. I've only got some experience with it, and only as a user, and even that is limited. I had some trouble wrapping my mind around the …
Git is a newer version control system compared to that of svn. I think that svn is more stable, easy to learn/use, and not-so-complex as git. Also, svn has very good client applications which provide extremely user-friendly user interfaces. Apache Subversion is also open source …
Git is better than Subversion in every aspect except that is not free . But since our company has bought Git licenses and I would not go back to using Subversion .
Projektspezialist bei Steffen Jäschke EinzUnt Physik, Berechnungen
Chose PTC Windchill RV&S
As PTC places PTC Windchill RV&S is confirmed in the market. PTC is able to lead the market well. It is due to the American university mechanism for software research and science that innovation does not come the first time up in industrial software applications. Software …
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 …
We liked that PTC Integrity requirements management, testing and source control are accessible through a single interface. This is not what we found with DOORS. DOORS only offers requirements management and testing and they are in separate interfaces. We are also beginning to …
I think the reason that PTC Integrity was initially chosen is that it was the best product available in the mix at the time. This coupled with the PTC deal on multiple products was a no brainer based on the size and scope of potential users.
We evaluated IBM's offering and CMstat. IBM's offering is "klugy", we needed Rhapsody, ClearQuest and ClearCase to get all the components to answer our requirements. And it's very costly. CMstat offered a good change managment solution, but was lacking in version control …
I was previously employed by a electronic laboratory notebook (ELNN company in Columbus Ohio. I felt that MKS and the ELN that I worked at in the past were more or less similar in terms of functionality, however both the products address different needs.
MKS integrity does well in some areas such as merging changes into the main trunk and managing change sets. We actually selected Git after using MKS integrity for over 7 years.
MKS Integrity is a toolbox of components that you can use to create any Software Change Configuration Management system to fit your own organization. This was the main reason why we went with Integrity over the other solutions that were evaluated.
Subversion solves our software versioning problem by providing tools for conflict resolution when doing collaborative work on the same files and projects. We use it with TortoiseSVN and it works great for some of our projects with smaller teams. However, we have a need to make code reviews more and it is a little more difficult to do that in SVN, compared to Bitbucket and Git.
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.
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.
Refactoring the layout of a respoitory--or a part of a repository--can be a bit painful, especially for users with workspaces associated with the affected part of the repository. Not sure what could be done to make that better, but it would be nice if something was possible.
Folks coming from Git can have problems using Subversion. Again, not sure anything can (or should) be done to address that, but it is occasionally an issue.
While there are interesting alternatives, such a GIT, Subversion has been a breath of fresh air compared to its predecessors like CVS or Microsoft Source Safe (now called Team Foundation Server). Its ease of use and high adoption rate is going to keep me using this product for years to come.
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
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.
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
After Microsoft Visual SourceSafe was discontinued, we chose Subversion and it was a great choice. We were able to migrate to Apache Subversion very quickly and easily and benefited immediately from its non-locking workflow (SourceSafe required users to "lock" the file when editing to prevent editing conflicts from other users, whereas Subversion allows multiple users to edit the same file simultaneously and then merge conflicts later.)
While we still use Apache Subversion for our legacy projects, we've migrated to Git and GitHub for our new projects as that is the new "cool kid" and it provides some benefits such as distributed and offline development. But Git is more complex than Apache Subversion and not as easy to learn.
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.
It allowed us to deliver the right files to our customer without "clobbering" previous releases, making for a far more satisfied customer.
It allowed our developers to work on two releases in parallel (plus an occasional third, for emergency fixes).
With some simple hooks, it allowed us to set up a system where code was was automatically deployed to test servers as soon as developers committed it, making testing easier. This was made easier by virtue of being a ColdFusion project, which requires no compilation. However, that is possible for compiled code with a continuous integration system like Jenkins.
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.