Create Requirements and Other Artifacts Using GenAI with the

Generating Artifacts from the Requirements List Page

The first major update is the ability to perform the existing Inflectra.ai requirements actions directly from the main list page. This lets you generate test cases, tasks, BDD scenarios and risks for multiple requirements at the same time, without having to click on each one individually to use the AI actions sidebar:

This is a great time saver as it lets you take an existing set of requirements (for example the backlog for an upcoming release) and quickly create the downstream artifacts for the entire release at the same time.

Generating User Stories and Features from Epics

If you looked closely at the image above you would have noticed that we've also added a new option - "Generate child requirements" that was not in the original release of Inflectra.ai. This new feature lets you take an existing high-level requirement, and use Inflectra.ai to automatically generate multiple child requirements based on the name and description of the requirement.

In the Scaled Agile methodology, you often have an Epic > Feature > User Story hierarchy as illustrated below:

With this new functionality we can take a single Epic and generate multiple Features for the Epic. We can then take the generated Features and then generate additional User Stories.

Lets see this in action. If we have a new requirement called "Reporting Functionality" that has a detailed description as shown below:

Then we can use the new Inflectra.ai feature to automatically generate a set of detailed features that describe the main reporting features we're looking to add:

In this example, it generated four different child requirements:

Creating the reporting dashboard itself
Allowing the user to view the different types of graph/chart
Allowing the user to perform ad-hoc queries
Allowing the user to create reports in various formats

The updated Inflectra.ai provides feedback to the user on the created requirements:

Now, two of the requirements are still quite high-level. For example, it would be better to have the functionality available in the graphs/charts described explicitly, and similarly it would be good to know what formats of report are we building and testing against. Well, we can simply use the same AI action again, but this time selectively on just two of the requirements:

As you can see, it has now taken the two Features and generated more detailed user stories under them, so that each report format is now listed separately. For the graphs/charts, it has described the different features that could be supported. Of course a human will need to review and determine if they are all actually needed (for example, maybe we don't need zoom and hover functionality).

Finally, to round out this example, we would use the Create Tasks and Test Cases to finish off our Agile planning work:

Now we have acceptance tests and Scrum tasks ready for development.

We have seen the new functionality in action for an agile project, but what about Compliance requirements and standards, can it also help there? The answer is Yes!

Generating Compliance Requirements from Industry Standards

Lets try writing an industry-standard requirement for a sample medical device. For example we need to make sure that this new device complies with the standards defined by the United States Food and Drug Administration (FDA). These standards are often called 21 CFR Part 11, named after the section of the US Federal Government Code of Federal Regulations (CFR) that defines how medical devices should be regulated.

With that in mind we have written the following compliance requirement in Spira:

Once that has been created we use Inflectra.ai to generate the first level of compliance requirements:

That is very helpful, but again, some of them are a bit high-level. For example, it would be good to get more detail on the audit trails, electronic signatures and the electronic record management aspects.

No problem we just use Inflectra.ai again to add more detail to three of the four requirements:

As we saw before, we can now use the existing downstream artifact functionality to uncover the risks associated with one of these generated requirements: