Azure DevOps (formerly VSTS, Microsoft Visual Studio Team System) is an agile development product that is an extension of the Microsoft Visual Studio architecture. Azure DevOps includes software development, collaboration, and reporting capabilities.
$2
per GB (first 2GB free)
PTC Windchill RV&S
Score 7.7 out of 10
N/A
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
Pricing
Azure DevOps Services
PTC Windchill RV&S
Editions & Modules
Azure Artifacts
$2
per GB (first 2GB free)
Basic Plan
$6
per user per month (first 5 users free)
Azure Pipelines - Self-Hosted
$15
per extra parallel job (1 free parallel job with unlimited minutes)
Azure Pipelines - Microsoft Hosted
$40
per parallel job (1,800 minutes free with 1 free parallel job)
ADO is well suited for the visibility of day-to-day tasks and responsibilities as well as things such as Features, user stories, etc. Off the top of my head, I can't think of any scenario where it might not be well suited, as you can customize ADO to your liking to a degree.
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.
Flexible Requirements Hierarchy Management: AZDO makes it easy to track items such as features or epics as a flat list, or as a hierarchy in which you can track the parent-child relationship.
Fast Data Entry: AZDO was designed to facilitate quick data entry to capture work items quickly, while still enabling detailed capture of acceptance criteria and item properties.
Excel Integration: AZDO stands out for its integration with MS Excel, which enables quick updates for bulk items.
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.
Need to make the changes so that it doesn't occupy most of the CPU utilization and memory
Execution of Bulky SQl Queries leads to either the SQl being out of exception or the VS being unresponsive
Integration with Microsoft products is easy, but with non-Microsoft products it is more difficult, and you have to make a lot of configuration changes to integrate
With every upgrade of the Visual Studio, like from VS 2010 to VS 2013 , we need to upgrade our hardware/machine, as the VS hardware requirement also increases
If code is getting compiled in one visual studio, like in VS 2010, that the same code could possibly give an error when compiled in VS 2013, due to certain changes in keyword, data format, etc., with the VS upgrade
I don't think our organization will stray from using VSTS/TFS as we are now looking to upgrade to the 2012 version. Since our business is software development and we want to meet the requirements of CMMI to deliver consistent and high quality software, this SDLC management tool is here to stay. In addition, our company uses a lot of Microsoft products, such as Office 365, Asp.net, etc, and since VSTS/TFS has proved itself invaluable to our own processes and is within the Microsoft family of products, we will continue to use VSTS/TFS for a long, long time.
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
Azure DevOps is a powerful, complex cloud application. As such there are a number of things it does great and something where there is room for improvement. One of those areas would be in usability. In my opinion it relies too much on search. There is no easy way to view all projects or to group them in a logical way. You need to search for everything.
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.
When we've had issues, both Microsoft support and the user community have been very responsive. DevOps has an active developer community and frankly, you can find most of your questions already asked and answered there. Microsoft also does a better job than most software vendors I've worked with creating detailed and frequently updated documentation.
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
Jira is fantastic for project management and customer facing portal. It is not good for pure development (no integration with Git, pipeline management, automated testing features). If DevOps were to integrate and adopt the project features of Jira as well as the customer facing interfaces, I feel it would be a complete project management system.
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.
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.
