Application Requirements Management Features

Read what people say are the most valuable features of the solutions they use.
Senior IT Manager at a manufacturing company with 10,001+ employees
The most valuable feature for us is the automatic creation of the test cases, based on the models. And the impact analyzer that shows you where your change is impacting your test cases, and the ability to export that to our TFS Instance. View full review »
Carrie Strickland says in a CA Agile Requirements Designer review
QA Group Manager at a financial services firm with 1,001-5,000 employees
* Now, we get automated test cases, where before we did not. It cuts out the construction time of testing, about 75%, is what we found. * It is a store that we keep all of our requirements in where, before projects would come in and we would not have a place where we keep the past requirements so there was always a fight between development, testing, and the business writers because they can't remember how functionality works. Now, there is a black and white copy of how the processes are flowing through the system, so there is not a fight anymore about what is happening and what is not happening. View full review »
TeamLeade840 says in an Inflectra SpiraTest review
Team Leader: Test Automation at a financial services firm with 10,001+ employees
Strong integration capabilities with other vendor tools, especially test automation tools. Good user documentation. View full review »
Lana Rousakovski says in a CA Agile Requirements Designer review
Senior Leader in Software Testing and Process Improvement at a tech company with 10,001+ employees
The ability to create models/diagrams at multiple levels (nest/embed them) helps in taking models from high-level business requirements and building them into detailed requirements models and test models. Plus, it helps reuse lower level models. It also allows maintaining models at appropriate levels, even for very complex systems/solutions. The above features also help to avoid redundancy and use appropriate level models for different levels/phases of testing and/or communicating to different audiences. Integration with TDM, test data management tool, provides the ability to generate data or use identified (preset or parametrized) test data. It allows significant expansion of test coverage and flexibility, without creating new tests and needing to maintain them. Integration with automation is one of the reasons we started to consider moving to this tool from our original tool for implementing test modeling. ARD appears to have better integration with Selenium. It also has the ability to record scripts/flows using Selenium Builder and import them into ARD, which will then create and optimize a model based on that. Measuring test coverage helps in one of the most challenging tasks. It has logic that can help to select the right set of scenarios and know what coverage it will provide. Handling loops in models was one of the challenges that we came across in our previous tool. ARD seems to have better control and logic over handling loops in models. View full review »
Alexander Dobry says in a JIRA review
Fachbereichsleiter with 10,001+ employees
The most valuable features are * the easy handling * drag and drop * what you see is what you get. It's, smooth, accessible. It fully supports the Scrum approach, and the Agile way of working, and it has Agile thinking behind it, so this is very much helpful. View full review »
reviewer812835 says in a JIRA review
Sr. QA Manager with 501-1,000 employees
The traceability mapping feature is something that became very useful, especially during releases and bug fixes. The creation of epics and stories/defects is also very useful and simple. View full review »
Jan Van Dravik says in a CA Agile Requirements Designer review
Chief Of Architecture & Industrialisation (Agile/Devops Prg Leader) at BNP Paribas
Modeling how the application works, and then getting every use case we can test. Designing the right tests, what are the most critical tests we must do. View full review »
Director Of QA with 1,001-5,000 employees
* The co-monitorial modeling. It lets us reduce the amount of scripts that we need to execute to get complete coverage. That is really important to us. * Traceability from requirements through test cases. View full review »
Jonathan Machado says in a JIRA review
Senior Test Engineer at a venture capital & private equity firm with 10,001+ employees
The most important is the Agile management, because we use Agile in our everyday tasks. Also, the task manager is important. View full review »
it_user461610 says in a JIRA review
Technical QA Lead in HPE NGA Synchronizer at a tech vendor with 10,001+ employees
For QA, the most interesting for me are boards, backlog, and filters. View full review »
Satyajit Roy says in a JIRA review
UX Architect at a software R&D company with 51-200 employees
Active sprints. It is like a Kanban Board drag and drop backlog to assign, to do, and finish the task. View full review »
Veronica Aruquipa says in an Inflectra SpiraTest review
Software QA Engineer at a tech company with 51-200 employees
* Indent/outdent functionality, because it makes it easier to relocate the test cases under any folder (all-in-one) at the same time. * Copy/paste of multiples test cases at the same time wherever you want. It helps me to save time. * Copy/clone a test case based on an existent one. It helps me to save time. * Export test cases from a project to another one. It helps me to save time. * Sign-in only from only one browser, which is good security stuff. View full review »
Ahmet Izgi says in an Inflectra SpiraTest review
Test Software Development Manager at a tech vendor with 501-1,000 employees
* Price * Ease of use * Integration with automation. SpiraTest is cheaper than its rivals. It has very simple UI designs. We don’t need to train testers for SpiraTest. Everyone can handle it. We are using custom automation tools. SpiraTest’s client engine mechanism is very dynamic for integrating custom automation tools. View full review »
SeniorSdd843 says in an Inflectra SpiraTest review
Senior SDET
Currently, I work as an SDET only and I don’t write or run tests. However, I use SpiraTeam existing tests so I can decide how to automate them. I use Spira RemoteLaunch to schedule a test server, which in turn schedules various test clients which run Ranorex. In the future, we intend to use SpiraTest to store a script which will be passed on to the test server. This will run the tests and return the pass/fail result. We will generate the test script using a web page server. In my previous job, I used SpiraTest to design and document tests. I would have a technician run manual tests using SpiraTest. I used Spira RemoteLaunch to run Ranorex automated tests and store test results. I would use SpiraTest to produce reports to generate a Test Plan, and also to produce a test result based on both manual and automated tests. View full review »
Sherman Duffie says in an Inflectra SpiraTest review
Sr. QA Engineer at a tech vendor with 201-500 employees
The most important area in SpiraTest is the customizable reports; being able to create test reports that make sense to shareholders, testers, and developers. The ability to lay out detailed test reports made life simpler, as a test manager. View full review »
it_user535656 says in a JIRA review
Test Manager
One of the valuable features is traceability from requirements to test cases. View full review »
Aimee White says in a JIRA review
Website and EComm at a local government with 10,001+ employees
Perfect for keeping track of large amounts of bugs, tasks queries and releases for fixes. The SaaS does the job it is supposed to: helps you keep track of your projects. What I like most is the ease of adding users and the obvious nature of what they need to do - drag and drop is always a win. It is cross methodology so Scrum, Kanban... it doesn't matter, you can use JIRA. I like how it shows the sprints remaining. Being able to instantly see where you are in a project and what is coming up is invaluable. Also, the ability to link a programme of projects is very helpful. I can see where all of the teams are with their individual projects but also how they fit into the overarching business plan for the year. View full review »
Anaya Struncova says in a JIRA review
Software Developer at a tech vendor with 201-500 employees
The most valuable features or functions that I have found in this software are several but mainly that it is a platform that gives the user the option to customize its interface to the point that it can be fully adapted to the team that implements it. This generates a great advantage since it is much easier for users to adapt to it and be able to work in a much more comfortable and highly effective way, in addition to providing tools that can be followed up on tasks or projects and give priority to them. It is really useful because in this way the team can focus on those who need a much closer delivery date. View full review »
Daryn Louw says in a JIRA review
Head of Product with 51-200 employees
Workflow management as very specific workflows can be configured to serve any number of business processes. View full review »
Rolf Schweingruber says in a JIRA review
Head of Embedded Development with 11-50 employees
* Sprint planning * Overviews over tasks and which assignees are doing what * Specific workflows for projects. View full review »
John Sell says in a JIRA review
Regional Vice President with 51-200 employees
One form for each feature/item. View full review »
Neetu Singh says in a JIRA review
Engineer -QA at a financial services firm with 10,001+ employees
This software helps us to follow the process the team agreed to and see the progress on issue and sprint level. With the help of this tool, we will be able to track the progress of the issue and sprint. View full review »
Baskaran Senthivel says in a JIRA review
RTE (Release Train Engineer with 10,001+ employees
* Dashboard possibility * JQL query * Workflow management. View full review »
Test Engineer Senior Analyst at a tech services company with 10,001+ employees
CA ARD has some beautiful features which I haven't found anywhere else. For example, when designing or creating our test cases and doing scenarios, we are able to restrict our flows. If we take a data link between two processes, we can actually restrict it, so that in production, if our functionality breaks down, we can restrict that, and all the flows related to it will be removed from the test data set. That is something we can actually do from CA ARD. View full review »
Kijal Parekh says in a JIRA review
Digital Test Lead at a comms service provider with 1-10 employees
It has an easy UI that can easily plug-in to every level. View full review »

Sign Up with Email