It's a relatively simple version control system so it works great for an individual or small team (less than 10 people). But if you have a medium to large team, especially one with members distributed over a large geographic area, or one where individuals need to be able to work "offline" without access to a central server, Apache Subversion will likely not be the best choice.
Also, if you're maintaining an open-source project where outside people will be interacting with your code repository, git is probably a better choice because it's becoming the de-facto standard these days and what most developers are familiar with.
Helix ALM is very well suited for maintaining traceability between user needs, requirements and tests for medical device design controls. It allows users to customize the reports to create a traceability matrix or any other reports that are needed. It is also a good program for tracking issues and bugs and for storing/linking verification and validation test protocols and reports.
Distributed development - I've never worked in an environment where distributed development (developers widely scattered geographically) was a factor, but that's why git exists.
Merging - Merging of code from one branch to another can be painful, especially if it's not done frequently. (On the other hand, doing merges is one of the reasons I get a nice salary, so I can't complain too much!)
Acceptance - Let's face it, git is what "all the cool kids are using." If you've got a bunch of developers fresh out of school, they'll probably know git and not Subversion.
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.
The support from Perforce has been extensive and allowed us to customize the setup of Helix ALM specific to our needs. They also hosted training sessions for our users and administrators and provided us with troubleshooting help during initial setup.
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.
The other tools that we evaluated did not have all of the capabilities and customization that Helix ALM had to offer and therefore we decided to select Helix ALM.
