What is your primary use case for Polarion ALM?

We use Polarion ALM for software development, including requirements management, testing, change requests, and task tracking. We set up the environment by configuring items and reports based on user requests. Once the environment is prepared, users work with what we have set up. We collaborate with them to define their needs and then develop the technical solutions to meet them.

I use the solution in my company for STLC. We use the tool for testing processes, from test management to dashboard creation.

I’ve worked on a few exercises, mainly on importing requirements, customization, and integrating with other third-party software.

I work in an industry where I mainly look after the requirements, for which I use Polarion ALM.

We use the solution for managing the requirements for a development project for a new type of transportation system. The challenge was to create a common basis for a multi-functional DevOps team working on a big program with different connected projects and to improve the development processes with a single, unified platform for requirements management, development support, testing, and release management. A major need was to more effectively plan, orchestrate, and track the requirements for our complex system across those multiple projects, and their individual yet connected lifecycles.

The solution is to create the documentation necessary, especially if it is to be given in technical documentation, to get the right to put a medical device on the market. For a medical device, you have to give the regulatory authority a lot of information, and they go down to the lines of code and to the risk management of this line of code, for this database is needed since it is no more possible to do it with hands. In this case, they outsourced the validation of the software with another company, and they made the software with another company. Polarion was used to extract from the software the information for the regulatory authority.

We do requirement management and task management using this tool.

We use the solution for development.

I use the solution as a documentation control system. Polarion ALM is used for all facets of project management, release, testing, and validation. All the tools required are included in the solution.

The primary use case of the solution is writing test cases, mapping those test cases to the requirements, and creating and executing test runs.

We're an automotive company. Polarion ALM captures our customers' requirements and validates against those requirements. We have our environment within our mother company, so only our people can see our data. I think it's called a project environment, but we have multiple projects. We work on the customer requirements and translate them into products designed here in our headquarters. Those are produced in factories across the globe. Only the engineers and the test engineers in the headquarters will have access to Polarion. However, it is within the system of our mother company, so they have an automotive and medical project. We'll be in the automotive project, but we still coordinate with the guy managing the system. We want to make sure we're the only ones who can see our data. That is also a requirement of our audit.

We use Polarion ALM for development to track requirements, tasks, anomalies, project and design documentation, and other things.

Polarion can be used typically for application lifecycle management. Typically it's used for requirement management, test case management, and defect tracking.

Polarion is an all in one tool that we use from conception to validation testing. Our product team uses it for their requirements, our developers use it for their stories and tasks, and our quality team uses it for testing. It integrates with SVN and GitLab.

We mainly use Polarion ALM for requirements engineering as well as task planning and task execution, but we mainly use it as a documentation and traceability tool. I work in the medical device development field. Even though Polarion is quite expensive, it's quite a good solution for medical device development in general, especially for software development. Within our previous company, not that many people used Polarion as it was only used within our department relating to medical device development. I'd say around 20 to 30 people were using it. It's hard to say as we had around six licenses with some floating licenses.

I use the on-prem deployment model. Our primary use case is for application life cycle management, DevOps, and all the application requirements.

We primarily use this solution for requirement engineering. Our deployment is on a private cloud from Siemens.