Polarion ALM is an application requirement management software platform now owned and supported by Siemens since the 2015 acquisition. It is available on the cloud (Polarion X) and on-premise. Polarion connect teams and projects to improve application development processes with
a single, unified solution for requirements, coding, testing and release.
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.
The question is actually not trivial to answer in 200 words. To summarize, I can say that we have had consistently positive experiences with all customers where we have used Polarion ALM. The sector in which the customer operates only played a subordinate role. We use Polarion ALM in almost all sectors: Medical technology, pharmaceuticals, aerospace, agriculture, automotive and many others. It is also interesting to note that in the beginning we were mostly active in the development of products, systems or software. Over time, this has changed more and more for some customers and risk management or projects for lessons learned have taken up more space. This enabled us to banish a seemingly endless number of Excel lists. Who doesn't know this problem: at first there is only one Excel list on the drive. Day by day there are more. Some with a date in the file name. Others with an employee abbreviation. In the end, nobody can tell which is the current and complete list. The really good thing about Polarion ALM is that it is extremely flexible to use and the configuration determines what the project is used for in Polarion ALM. It is customizable to my situation and not rigid.
Polarion ALM provides a centralized repository for capturing and managing requirements. Teams can define, organize, and link requirements to other artifacts like test cases and development tasks.
Test Management:
Polarion ALM facilitates end-to-end test management. Teams can create detailed test cases, manage test execution, and track test results.
Traceability and Impact Analysis:
Polarion ALM ensures traceability across all phases of the development lifecycle. Users can establish links between requirements, test cases, development tasks, and other artifacts. This traceability helps in impact analysis, allowing teams to understand how changes in one area may affect other parts of the project.
Customization and Adaptability:
Polarion ALM is highly customizable to fit the unique needs of different organizations and industries. Users can create custom workflows, define custom fields, and adapt the tool to their specific development processes.
More robust engine as far as the actual took is concerned. There are navigation components in trace to reporting which we feel can be improved especially when dealing with cross global accessing of the tool. It slows us down a bit so it's backend driven optimization as well as some front end "clunkiness" that can be improved.
Improve some filtering capabilities especially in creating custom reports and generally all around the ALM components of the tool.
As of the version we have, the ability to enhance replationship types in traceability is limited.
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.
There is too much at stake to go into a new system. But with everything else being promised as far as newer more innovative products, the justification to not renew is a huge risk so that is not a concern
Polarion ALM can be used individually and what I do with Polarion ALM is decided by my configuration. Lesson-learned, operational risk management, product, system or software development or customer management .... doesn't matter at all. I decide with my configuration what I will do with Polarion ALM. Of course, you can also use Polarion ALM out-of-the-box for your development because it comes with a large set of project templates.For this reason, I would also recommend not to just get started. A suitable consultant will show you the right templates and customize them according to your needs. Having Polarion ALM is like having a car. You know exactly how to operate the car. You've done it a thousand times before. The details are in the configuration: did I have a navigation system installed or not? Do I have a lane departure warning system or not? Do I have cruise control or not? Unlike when buying a vehicle, almost all functions are already available and can be used, usually at no extra cost. However, if something is missing, it can be obtained via the manufacturer's extension portal. Individual extensions are subject to a charge. Polarion ALM - easy to deploy and easy to use.
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.
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.
Polarion ALM has the best usability, extensibility and reactiv product management. The support is also very good compared to other companies. Or in other words it is closer to the customer. Codebeamer is for sure also a good ALM tool with a great feature set, but existing customers are often neglected. We will see, what PTC as the new owner of codebeamer will change at this point.
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.
