PTC Windchill RV&S (formerly Integrity Lifecycle Manager of the Integrity suite) is an MBSE (model-based systems engineering) suite. The former Integrity suite contains an Asset Library which supports systems-of-systems approach to design (i.e. linking models into higher-level models that subsume them), a Process Director which is designed to articulate, manage and improve the design process, and a Modeler for visualizing and controlling the product design process. The Integrity suite is…
N/A
Rally Software
Score 6.8 out of 10
N/A
Rally Software headquartered in Boulder, Colorado developed the Rally agile software development / ALM platform which was acquired by CA Technologies and rebranded as CA Agile Central. After CA's acquisition by Broadcom the software was once again rebranded as Rally.
Projektspezialist bei Steffen Jäschke EinzUnt Physik, Berechnungen
Chose PTC Windchill RV&S
As PTC places PTC Windchill RV&S is confirmed in the market. PTC is able to lead the market well. It is due to the American university mechanism for software research and science that innovation does not come the first time up in industrial software applications. Software …
There are some tools which are available for free like GitHub. I've used StarTeam when it was a product of Borland, and while using PTC Integrity, I feel PTC Integrity has most of the features which were available in StarTeam. Although there are some other free tools like …
We liked that PTC Integrity requirements management, testing and source control are accessible through a single interface. This is not what we found with DOORS. DOORS only offers requirements management and testing and they are in separate interfaces. We are also beginning to …
I think the reason that PTC Integrity was initially chosen is that it was the best product available in the mix at the time. This coupled with the PTC deal on multiple products was a no brainer based on the size and scope of potential users.
We evaluated IBM's offering and CMstat. IBM's offering is "klugy", we needed Rhapsody, ClearQuest and ClearCase to get all the components to answer our requirements. And it's very costly. CMstat offered a good change managment solution, but was lacking in version control …
I was previously employed by a electronic laboratory notebook (ELNN company in Columbus Ohio. I felt that MKS and the ELN that I worked at in the past were more or less similar in terms of functionality, however both the products address different needs.
MKS integrity does well in some areas such as merging changes into the main trunk and managing change sets. We actually selected Git after using MKS integrity for over 7 years.
MKS Integrity is a toolbox of components that you can use to create any Software Change Configuration Management system to fit your own organization. This was the main reason why we went with Integrity over the other solutions that were evaluated.
Can you give some details as to why you selected Integrity over this tool?
Rally Software
Verified User
Anonymous
Chose Rally Software
Rally and Asana have comparable features and are both valuable project management tools, but Asana's user interface is well-organized and highly intuitive. It's easy to add tasks and collaborators, edit due dates, indicate progress on tasks, close out projects, etc. However, …
Overall, Rally Software is a better and more powerful tool than Jira for the same exact purposes. Jira cannot function as a requirements repository so it needs plugins or separate tools to do the same thing. There is no space or option to see all defects or user stories or …
We have used Jira in the past. Jira is easy to use and seems to be an industry standard. Rally is clunky and expensive. The dev side did not pick it, the business did due to its reporting capabilities.
I did not select Rally; it was chosen by the organization. If I were choosing what to use within my own team, I would use Trello. It's free, very simple to use, and has a much nicer user interface. My company previously used VersionOne however, and I prefer Rally over that …
It was a close race between JAMA, JIRA and Rally. We decided to go for JAMA as a requirements management tool and use Rally for Agile projects. The cost was another factor that made us select Rally.
Our evaluation was done many years ago, but at the time Rally provided the best mix of SCRUM-driven features, visibility and economy for our product engineering teams.
Selected because the others seemed worse two years ago when the decision was made. VersionOne seemed ugly and too restricted. Might look better now. Microsoft TFS, now VSO, looked limited but also might look better now. Microsoft is improving it at a remarkably rapid pace. Jira …
The process we used to select a tool was to create a scorecard of IT and Business stakeholder needs. We then reviewed seven tools and graded them against the scorecard requirements. We took the top two products and had a one day hands on demonstration with selected IT and …
We used CA Agile Central (formerly Rally) before but recently switched to Jira. I used jira before Rally too, and I think it was easier to manage defects in Jira. Also, I think Jira is better for teams and companies that want to implement agile/scrum life cycles. It's easier to …
We started exploring new tools, and found better adaptation of our team toward Jira. Jira provided engineers with simpler interfaces and more reliable service, even though less unnecessary features. Also the managers found in Jira better ability to eliminate noise and focus on …
I've also evaluated the following agile solutions: ActiveCollab, Agile Bench, Agilo for Scrum, Atlassian JIRA, Pivotal Tracker, SpringGround, Targetprocess. Telerik Teamprocess, VersionOne, ZebraPlan etc. If it’s time to transition to software that’s specific to your Agile …
Rally has much more features with regards to the the traditional Agile methodology and has more extensive tracking features for the project managers. Pivotal tracker was used for a smaller company and smaller teams but since my current company is larger in scale and has more to …
We enjoy doing requirement mappings. The enhancement in transferring them between models is great. It is for innovation all the time a challenge to conduct them. We have two major scenarios for that task set. One is to integrate already well-validated models into greater sets. The other is defining totally new ones. We developed new strategies and refined the existing ones. We rate the synching requirement configurations as comfortable. The processes of synching the items back to the models. The major advantage is to optionally synchronize all-important and intended traceability relationships from Modeler so that both can be given the correct right the right group of uses while others only see the structures. We too prefer the handling of deletion and creation. It is a real advantage how the mapping and relation are implemented. The implemented integration to third-party tools for requirements definition and management is a plus. We like the profiling features and the high compliance to industrial standards as well as the module variability modeling.Windchill RV&S makes us perform better and let us take over control. It enhances our return-of-investment efficiencies to the top. The only drawbacks are the high skill levels needed and the necessary relation in businesses to make the profits. Another topic is the resources that are needed.
If your organisation is planning to adopt Scaled Agile Framework Methodology (SAFe) without being worried about cost, CA Agile Central is one of the best tools. Here, you can look at various release trains and how that then flows up to the overall program budget. You can look holistically across all the release trains with minimal effort and have it flow up to the program office’s budget. It also helps by easily maintaining backlogs and integrating more seamlessly into software developers releases, iterations, and features. It has no conformance issue as it supports almost all the browsers like IE from version 8.0, Firefox from 3.6 and the newest versions of Chrome (from 6.0) and Safari (from 4.0).
It allows the user the ability to link all aspects of the SDLC together so that there is only one source of documentation and information rather than having to search in multiple places.
It is very customizable to suit a particular businesses needs.
It is helpful for all areas of software development.
structuring teams separately in a clean way. You can add as much teams as you want, and guarantee each team's work would stay separate in browsing, graphs and analytics.
detailed menus and drop-downs listing of features - technically it covers all there is of agile aspects and some more
ability to set your email notifications on/off
ability to split user stories into the next iteration if work isn't done in the previous one - no need to duplicate your user story manually
I do not make decisions on what tool my company uses. I am just the user of the tool and such decisions are not handled by me. If I were to make such decisions, I would definitely renew MKS, considering the amount of data we have stored in MKS and the current number of users who are familiar with the system
Assuming we were paying - right now my group gets it for free as the broader engineering organization pays for it. There would be switching costs. There would be pretty minimal data migration, but the biggest cost is getting people to learn a new tool and starting off on the right footing. Evaluation and identification of the right product is a big part of switching too
PTC Integrity comparatively could be considered a nice Source code management, Version controlling tool and could be compared with tools like StarTeam. If the integration to move/migrate code could be integrated into this tool, it would become an extremely powerful tool.
Great UI, recent refresh was terrific. Great graphs and metrics, inline editing for updates, and a multitude of views on sprint progress make for a great team collaboration experience. There is also an active community and forums so that if you do need help, it is readily available
The screens render relatively quickly but many actions that you would expect to require a single click require multiple clicks and pop-up windows. The extra windows and clicks make the product feel ponderous.
PTC Integrity administration can be somewhat daunting. They have been able to help with every question that I have submitted. Their support website is very easy to understand and submit questions and their phone support is wonderful
I've had to use support only one time and my issue was eventually resolved but not because of my ticket--because others complained about the functionality taken away so they brought it back. My ticket was never answered or addressed. So I can't really say much for the support factor for Rally.
It more or less confirmed that we are using it the way they had in mind. We were hoping for a epiphany in terms of how we could use it better.
They also want to be a go to source for agile processes and have an online resource center. It’s not that great but had a couple of nuggets. It hasn’t really helped us too much and we are not too far off from the classical interpretation of agile.
I would recommend training, in particular for organizations that multiple on-going projects. The product seems optimized for larger, more complex teams and getting proper training on how to configure, administer and use the system would be beneficial
Implementation of RALLY services and program satisfaction among various group,... 1) Dev Outcomes: How were our resiliencies, development, learning & practitioners “make them do the work,” but that they ask you to do it “in a way like before. 2) The Ops group: Just wish to make sure any change won't break current production envirements All the stake holders has to be on the same page
There are some tools which are available for free like GitHub. I've used StarTeam when it was a product of Borland, and while using PTC Integrity, I feel PTC Integrity has most of the features which were available in StarTeam. Although there are some other free tools like Tortoise SVN, it's always better to stick with tools which are licensed and supported in case of any issues/problems.
Rally and Asana have comparable features and are both valuable project management tools, but Asana's user interface is well-organized and highly intuitive. It's easy to add tasks and collaborators, edit due dates, indicate progress on tasks, close out projects, etc. However, Rally's interface is somewhat cluttered and difficult to navigate. My team ended up choosing Asana over Rally due to these concerns.
Better requirements through PTC Integrity - which will equate to better products and less warranty costs (very large savings).
Better efficiency ....PTC Integrity can help keep track of a globally managed project structure. This will go far in helping keep repeat and duplicate efforts from happening multiple times.
Better products for our customers through a more attentive corporate ear. PTC Integrity can help make customer wants and needs a reality.