Jama Connect® is a Requirements Management software and Requirements Traceability solution. Jama Software enables teams to manage product requirements and enable Live Traceability™ across the development process, in order to reduce cycle times and improve product quality.
N/A
PTC Windchill RV&S
Score 8.5 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…
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 …
Jama is an excellent tool for requirements management, development, and traceability throughout the development lifecycle. Jama aids in peer reviews of generated artifacts with time-boxed review cycles. Jama provides a robust ecosystem which is highly tailorable to the demands of the particular organization in which it is used
PTC Integrity is an excellent source code management and version control tool, and I would suggest anyone to use it for that purpose. We can even define our workflows using individual forms for implementing Change Management, Defect Management and Access management requests. If properly used, this tool is great for managing our code for very long periods, considering my 4-5 years of usage. Though the UI could be better, and integration with some application servers could be better implemented, this tool is a good tool.
Focus in the content without loosing the track of the evolution of the items by maintaining the exchange of information between the users inside the Tool.
The possibilities to integrate this tool within our IT-landcape and with our other engineering tools is for us a leverage to success.
The 'filtering' capabilities in Jama are not as good as they could be. In particular, the ability to "nest" filters is quite limited. I have certain seen much better capabilities in other tools. ('Cradle' is an example of a tool with excellent "nested filters" capabilities.)
From an administrative point of view, the 'License' admin view is pretty disappointing. The particular thing that I'd like to be able to find out from it is the peak number of 'Float Creator' licenses in concurrent use on each day. If there's a way to get to that information, I haven't found it yet.
It can be overwhelming with the number of tabs, functions and ways to achieve the same result. The average user may struggle with learning the tool.
The text editing in Integrity is weak and does not provide many options. Because of this, many user decide to use MS word instead, to document requirements.
Jama Connect is not adding many extra features with their major releases. It showed launched new features, but those are not very useful for developers or creators working with Jama. From the performance side, Jama has been reduced it's performance in Jama 8 as compared to Jama 2015.5 from the functional perspective. The test suite must be provided by Jama to test the performance and function of things in our instance, but Jama doesn't provide it. Also, Jama requires a lot of manual intervention for adding users.
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
Jama is mostly designed for requirement gathering, but that can be possible using JIRA if we add only approval type of plugin for special requirement types. Jama's performance and features do not improve on a periodic basis i.e. with each release. Even bug fixes take a lot of time and they don't care about customer impact.
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.
Jama is available most of the time if it is used within the application's boundary. Jama has very good availability if we use very high hardware servers. Sometimes we face issues if there are batch operations running.
With performance compared to JIRA, I do recommend Jama in this case. Jama provides very good performance, it loads immediately for any of the items and searches any item immediately. Performance is really good in all of the operations including creating stories, epics, item types or other support operations or report generation.
They typically answer within minutes of posting a ticket, and then you have a clear expectation of what the issue is, how to diagnose it, how long will it take to get resolved, and in which version a given problem is resolved, or if there is a patch for hosted services. They have a number of support people, and all of them are top-notch.
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
Jama 2015.5 implementation is very smooth and no need for much manual work. Jama 8 has many challenges and we can not install it as smoothly as Jama 2015.5. Initially, Jama didn't provide the Jama 8's installer files or zip files and they were just providing docker files to everyone (which was really strange). It is the worst that they don't provide all the files at a time. Why should they tell us where we should deploy, and why only a dockerfile? I am not very satisfied with Jama implementation.
The major sellingpoints of Jama were the review-system for internal and external reviewers and the inclusion of (Use Case) modelling tools, while keeping the core requirements-centric. Ability to synchronise with currently in use test-tooling and the low learning curve were additional selling points. Availablity of support in our local language was much appreciated as well.
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.
There is no horizontal scalability available in Jama, we have only one choice to scale it vertically. But vertical scalable applications always have limitations to grow. In this case, Jama doesn't support horizontal scalability functions like multi-node architectures with a shared drive for the home directory.
MKS Integrity has proved to be particularly useful in the software development process by increasing employee effieciency
MKS integrity has also made software development a very efficient process and makes feature releases and bug fixing a lot easier
In addition to the above, our organization has been able to support manufacturing easily by reverting to a previous software version in case of an emergency.
It has also led to faster time to market for new products.
