BMC AMI DevX vs. Modern Requirements4DevOps

I love these tools! However, my company has not yet transitioned from SCLM to a modern repository, and this is causing most of our developers to remain within TSO for all their development. It's been a slow adoption up to this point, but we are moving toward more modernization this year and next, so with any luck, we'll see usage pick up. Success depends on the speed at which your management is willing to move.

Incentivized

We tried the Modern Requirements4DevOps AddIn to see if it brings a added value to our development. I have to say that I would distinguish between types of projects in which it is beneficial and in which it is probably "over engineering". Certainly, bigger development projects with higher complexity are more suitable than small and not really complex projects. However, for the bigger projects Modern Requirements4DevOps definitely helps to deal with the complexity as it adds way more contextualisation to the various entities. It really helps to understand which requirements led to which action in a diagram or task during development. It helps to control the complexity and inform all team members along the project.

Incentivized

• The tool I use is fairly intuitive. It doesn't take long to be using it full time.
• Changing the layout/view is fairly easy. This allows it to fit individual preferences.
• It is helpful to be able to view specific windows in full screen. Usually, I have it set up to view multiple windows, but sometimes, I just want to view one window in full-screen mode.
• the debug utility is very useful. Place stopping points is easy and one can set parameters as to when you stop at a line of code. Changing the data on the fly is easy and usefull. The interface is easy to use and make sense.

Incentivized

• Smart Documents
• Building a connection between individual entities (requirements, documents, tasks, tests)
• Requirements Management and Reporting

Incentivized

• Download source code plug-in on Azure DevOps to allow downloading prod version even if it's not in the assignment.
• Publishing Test Results on Azure DevOps from Total Test plugin
• Integration with DevEnterprise in Workbench and GenAI capabilities for enhance code analysis (Accross multiple programs/applications)

Incentivized

• forms could be transferred into in line fields to allow in line maintenance of data
• make window management of diagram builder more flexibility to make more space to build diagrams
• I would wish that the performance is a bit better sometimes, loading times can be quite long in some cases

Incentivized

This is a very good range of tools that we use daily to maintain our programs

Incentivized

9 as it gives good smooth experience for all development tasks. Can be improved a little.

Incentivized

The tool is very reliable and we have had very few cases where we have had to contact support.

Incentivized

With one exception, we did not observe any slowdown in development activity when using the AMI DEVX Code DEBug tool.

Incentivized

Support has been amazing compared to Optim. Further, new features are very regular with File-AID - I can't remember the last time Optim had a significant update. File-AID support is very receptive to feature requests and reported bugs, including sending out hotfixes quickly.

Incentivized

The learning phase is relatively easy to implement.

Incentivized

The installation teams for these products have never complained about any difficulties during the integration of this range of tools into our IT system.

Incentivized

The names may have changed over the years, but anyone who has been around for a while will recognize them. For Software Configuration Management, I have used TSO/ISPF/SCLM, Panvalet, ChangeMan, Librarian, Endevor, and now Code Pipeline. All of them met the basic requirements. All of them had their advantages and disadvantages. Code Pipeline, however, stands head and shoulders above the rest in simplicity, completeness, effectiveness, efficiency, and elegance.

Incentivized

Modern Requirements4DevOps is an AddIn for Azure DevOps Server (Microsoft Azure DevOps) and extends the native features of Azure DevOps in the area of Requirements Engineering, Requirements Management and Reporting. Azure DevOps already contains tons of valuable features. However, for bigger and more complex projects Modern Requirements4DevOps extends Azure DevOps by further features. Thus we used both products alongside.

Incentivized

• Possitive impact. It is main product suite to enable devops in the mainframe applications team. All developers use these on day-to-day work.
• Negative impact: Recent usability issues caused disappointment in the application teams. It became hard motivate the development community to increase usage.

Incentivized

• Better communication --> thus less misunderstandings
• More Transparency about requirements --> adds context and helps to build a common understanding
• Traceability of Requirements --> we used the baseline also to look into the history of requirements to understand how certain requirements have changed

Incentivized