Windchill Systems/Software Engineering Ideas (Integrity)

skitschke-2 · ‎09-04-2019

For instance OpenJDK.

Neeraj_Jain · ‎11-14-2017

Till the present release of Integrity 11.2, in an Admin staging set up, i. Creation & update of IM Project (Workflow & Documents Project), ii. Update of existing Dynamic Group is not possible directly at the Production Server. Users need to request administrator to create the IM Project and set its dynamic group membership at the staging server and then push / promote those changes to Production Server using Admin Migration Wizard. This is required to be done everytime for each and every small changes in Project / Dynamic Group. I believe creation / update of Project & editing of existing dynamic group membership is a end user activity rather than an administrative tasks. It does not change the Integrity Object model but rather it only defines the user access to the new Projects. So, my idea / request is to EXCLUDE the IM Project and Dynamic group functions out of Admin Staging promotion list. Even in context of Windchill, it is just like creating a Project / Product container and then setting up a team of that Project / Product container and that is clearly separated from administrative tasks. Having worked with multiple customers, I sensed this as a pain point with almost everyone them who uses Admin Staging set up.

spoussard · ‎06-22-2016

Integrity Modeler allows creation of default display options and to modify options diagram by diagram. When we want to show the same diagram with more information for a stakeholder than for another, we need to recreate a new diagram from scratch and apply view options to this diagram. When, as it is our case, we have hundreds of diagrams, it is no more managable to double or triple the number of diagrams. We suggest to allow creation of display options which can be applied on collections of diagrams. Depending on the user, diagrams may have more or less informations (callout notes, names, stereotypes,...) These options may also be used by Publisher to provide documents with the right point of view.

ahaas-2 · ‎08-10-2016

The Integrity Modeler Populate function helps to populate diagrams with elements. For example it is possible to populate all ports of a part. If a part has many ports often not all ports are nedded in one diagram. The two options which are available now is - to poulate all elements and delete the not needed or - to drag and drop the neede elements from the bib. Both solutions has lagrge disadvantages if the numer of needed elements is quite high but still only a few of the total amount of elements. The 1. proposal is that after activating the populate function a option menu shall shows up, in which the elements to populate can be chosen by selecting check boxes. In a case in which a populate function adresses really many elements for example when populating linked requirements of a part the check box menue would get to large to handle The 2. proposal is that the check box menue shall include a filter option. This could be realised by (multiselect) menues in which different element attributes and their values can be chosen to filter the selectable elements. but + -->

uminet · ‎11-22-2016

Variation items (variation points and variants) are presented to the user under their model names. As these names are typically of technical nature, often following unwieldy naming conventions, users often have problems understanding what the item really means in the context of the application domain. It would be helpful to have alias names and explanatory text associated with the variation items and display them to the user in the front-end tools.

shrinivasguruna · ‎03-27-2019

The exported document from Integrity shows inconsistent borders .Can we not have consistent borders and font text after Export.Can we specfy border layouts in our mapping file. Attaching a wishlist of what we need from Integrity Table creation; Autofit-Window function (no matter if A3, A4 or what so ever) Table-Border Separate document view on two screens (new window) the way we have like a laptop and monitor Preview of items in document view --> no difference if in edit mode, selected or not selected (only difference is white background for edit mode) -Easier influence on Exporter for {Text}-Attribute --> If Attribute X has value Y then Textstyle... If Content Category = Table then .... default table style. Trace creation triggers --> to be updated: First time trace creation while copy&paste+ traces status Create own Shortcuts or/and bring easy edit of fonts and so on to toolbars. How to use "Document --> View Differences..." or have more options on it.

spoussard · ‎02-01-2017

In the scope of Integrity Modeler (IM) improvement, I propose some suggestions which could increase PTC footprint in System's Engineering. - Improvements in handling huge models (big data) IM is today not tailored to handle a complete system containing tens of thousands data and retrieving the useful information fluently and quickly. Historically, the tool is tailored for Software Engineering which handles less data than a complete system or system of systems. Latencies in the tool (modeler, publisher,...) limit the deployements. - Improvements in authentication and privacy For confidentiality reasons some parts of a model may be accessible to specific teams and others may be public. Today's SysML and IM concepts require the creation of 2 separated models even if 80% are common leading to time consuming and error prone export/imports. - Improvements in possibilities to create ontologies Profiling allows creation of business names above UML concepts but do not handle rules between these concept. For instance, if we profile a computer as a SysML block and a CPU board also as a SysML block, SysML will allow us to say that a CPU board is made of a computer which is a non sense. Once an ontology is defined, advance researches and analysis may designed easily All these topics are quiet linked with one another and I hope this will help PTC building a roadmap answering to System Engineering concerns.

Windchill Systems/Software Engineering Ideas (Integrity)

Support other Java implementations than Oracle JRE

Exclusion of IM Project & Dynamic groups from Admin Staging Set up.

Integrity Modeler - Filter diagrams symbols

Integrity Modeler selection and filter menue for Populate function

Variant Selector - Support of Alias Name and Explanatory Text

Layout Improvements for Integrity documents

Integrity Modeler (IM) improvements