In the context of Polarion Requirements, we are using it for requirement management, for test activities, and to produce traceability metrics between requirements and tests in the context of medical devices within highly regulated environments.

We use Polarion Requirements mostly to capture all our requirements for our project deliverables, for engineering, and we were also thinking of standardizing our technical standards internally. So, we are able to efficiently generate and cross-check all of the requirements across all our technical disciplines, and to be able to streamline those requirements together. We do find cases where it's difficult for us to actually capture and trace all this historical track records that have been changed.

My company mainly utilizes the product for documenting internal standards, guidelines, and requirements. Currently, we're focusing on using it for internal purposes, but the vision is to expand its usage to include contract requirements and tracking functionalities. While we're not there yet, it has proven effective for managing our internal documentation needs.

We begin by drafting their requirements. However, we have only attempted to employ them for document management, even though they are meant for a requirements management system. Now, we have been attempting to use Polarion in its current manner to oversee the entire process, from requirements to calls. I began using Polarion, primarily for creating demos during the pre-sales phase. However, in my current company, I'm working on enhancing our project delivery methodology.

Polarion is used for Application Lifecycle Management. It supports various functions such as requirements management, testing, etc.

I'm a test engineer and expert, and I generate test cases and protocols from customer requirements for the company. Based on the requirements, I facilitate test runs and execution. The tool proves valuable for creating comprehensive test reports.

I primarily use Polarion Requirements for industrial servicing.

Our primary use case is to track the requirements, user stories, software solution designs, and deliveries for our team-centered projects.

Polarion Requirements is used in different industries like automotive, medical devices, and aerospace. It's primarily for managing requirements within an entire project. You can store requirements and have end-to-end traceability. 

This means you can track everything from initial customer requirements all the way down to system or subsystem requirements (even hardware or software components in the case of medical devices).

Polarion also provides LiveDocs and live reports, which can be configured once and then used to give top management an easy view of the product status or how the requirements process is going. 

It's a flexible tool where you can write requirements, track their statuses, and plan your entire software release.

My clients also use Polarion Requirements for traceability in their projects.

We worked with the web interface.

We use it for requirements management.

We are users of the product and I'm a systems engineer. We use the product to review and assign requirements we receive from customers. For now we have around 10 people using the solution. This may be increased in the coming months. 

We use this solution for systems engineering and department management.

We have a private-cloud deployment.

The primary use case involves developing custom products. We manage the requirements there.