Polarion® is one of the world's fastest enterprise scale web-based Application Lifecycle Management (ALM) solution. Since its inception in 2004, the success of Polarion Software is best described by the hundreds of Global 1000 companies and its over 1 Million users who rely daily on Polarion Software solutions in their business processes.
Subject to changes and errors. The information given in this video only contains general descriptions and/or performance features which may not always specifically reflect those described, or which may undergo modification in the course of further development of the products. The requested performance features are binding only when they are expressly agreed upon in the concluded contract.
All product designations may be trademarks or other rights of Siemens AG, its affiliated companies or other companies whose use by third parties for their own purposes could violate the rights of the respective owner.
Who made this video, and why? What was going through their head as they did so? My heart aches for the video editor whose value on this planet has been distilled down to making buzzword videos that convey almost no actual information. We should take up a collection to help pay for their therapist. I might start a gofundme. And to Siemens, please cut the price of Teamcenter and NX by 75% and pay for it by firing whichever manager asked for this video. Nobody needed this and my head is spinning to think how lost you have to be to make it. What happened to your organization that nobody asked themselves what this video was for? How did I ever find myself watching this??????
You could have added the direct link of your extension on the Polarion extensions web site (instead of letting me search for it). But I cannot copy paste the full path because YT blocks my message: ..... /extensions/409-getpolarionproperties-library And the getPolarionProperties library is a commercial extension...
Nice content, but this perspective is of the older version of Polarion and MATLAB connecter right. I'm working on polarion Simulink connector 3.3.0. The workflow for newer version is same as what you've explained.
Hi, link was not working for me.. is template still available? I would like to demo & show to my department. If it is value added, work on business case for license
Hi David, the extension is manages by our partner Invenio: www.invenio.net/de/systems-engineering/polarion/ Currently it is not part of Polarion X Best Wishes Tim
Nice presentation of this Polarion Widget. I have the following questions: 1) How does this widget relate to Xcelerator? 2) Where do I find further videos of this series „Xcelerator Shorts“
Thanks for the feedback! The Polarion product forms a part of the Siemens Xcelerator platform, which, provides users with complete end to end traceability across all stages of a products lifecycle. Further videos of this series are in production with a plan to release them on a weekly basis.
@lionel , if I want to take user input from drop down (user selects projects) Based on selection I will pull data from Polarion. How to do my use case ?
I love your advent calender, it's great for gaining insight into what Polarion can do! As a complete newbie I unfortunatly can't get it to work. Is there anything I have to do before copy-pasting the script in the tutorial? Do I have to create a wish work item? Thank you!
Im Polarion gibt es task die man mehreren Assignees zuordnen kann. Hier lassen sich zwar Stunden eintragen aber nicht auf einzelne Ressourcen zurückführen oder?
Configuring import of test results from Jenkins is described here: almdemo.polarion.com/polarion/help/topic/com.polarion.xray.doc.user/guide/xid1853302.html
The documentation on connecting Jenkins is available here: almdemo.polarion.com/polarion/help/index.jsp?topic=%2Fcom.polarion.xray.doc.user%2Fguide%2Fxid1853297.html If you have specific questions please consider posting them on the Polarion community pages: community.sw.siemens.com/s/topic/0TO4O000000MihxWAC/polarion For assistance from our professional services please contact your Siemens sales representative.
Hi Jonathan, do you talk about the e.g. velocity code? I agree that this is hard to read using phone as an interface. Otherwise I don't have an idea how to change that. Any suggestions? Or special requests?
Polarion authentication guide covers advanced topics about user management: almdemo.polarion.com/polarion/help/index.jsp?topic=%2Fcom.polarion.xray.doc.user%2Fguide%2Fxid1974897.html If you have specific questions please consider posting your question on the Polarion community: community.sw.siemens.com/s/topic/0TO4O000000MihxWAC/polarion
Yes, the pictures will be imported as well. They will be part of the work item description. Here is additional information on that topic: almdemo.polarion.com/polarion/help/index.jsp?topic=%2Fcom.polarion.xray.doc.user%2Fguide%2Fxid1483735.html If you have further questions please consider posting them on the Polarion community: community.sw.siemens.com/s/topic/0TO4O000000MihxWAC/polarion
Further information about the new Simulink connector is available here: extensions.polarion.com/extensions/397-polarion-connector-for-simulink-public-beta-release-2
How do you work with headings and restrictions? If I e.g. set at restriction on a heading, all requirements under that heading is removed in the generated document (regardless of the individual work items restrictions), but the heading itself remains. How should you do if you want the headings to be treated as normal work items, i.e. if a heading is configured to be discarded in a generated document, how do you actually make that happen?
One question to Maxim: can one use several levels of Master Specification? I mean CRS (customer req spec) and PRS (product req spec)? What about relationships of reqs from Master PRS, are the copied automatically from Master Specification to Product Variant Specification? What about the connected Work Items? Are they also instantiated?
You can certainly define several levels of Master Specifications. Just add the restrictions from the Feature Model into the Restriction Field. Relationships are automatically copied over as the Variant that you build uses the branching mechanism of Polarion. That means it's not a real copy, but a pointer to the original spec until you overwrite it. Test Specificatins work similarly to Master Specifications. You can either enact propagations or restrict them based on the Feature Model as well.
