Skip to content

Authoring & Elicitation Tools

Common Questions and Tutorials

FAQ | Simulations | Use Case

Introduction to other Authoring and Elicitation tools

Authoring Requirements with Modern Requirements4DevOps

Why have so many authoring and elicitation modules?

In order to author and elicit the best requirements you need the right set of tools. In some scenarios the right tool for the job might not be a document or a diagram. 

Your team might need to use a question list (FAQ), mockup (Simulation), and/or use case model (Use Case). Each of these tools allow you to easily create a requirement asset and use it to directly build, or attach, project requirements. 

This offers you access to the right tool at the right times and any asset you create will already be stored within your project. No more need to manage, store, and maintain 3rd party assets!



Step 1) Creating a Mockup using the Simulation module

Authoring & Elicitation Tools​

Creating a Mockup allows you to easily visualize how an interface, feature, or component will be seen by the user. Mockups allow you to understand the user experience and to identify the appropriate requirements that need to be elicited/authored. 

In this video we cover how to build your first Mockup. 

Step 2) Adding requirements to a Mockup

Authoring & Elicitation Tools​

All of our Modern Requirements modules are driven by our belief in a single source of truth model. 

Our implementation of a Mockup tool follows this belief and allows you to easily connect requirements to the components of your Mockup tool.
Watch this video to find out more. 

Step 3) Building a Use Case Model

Authoring & Elicitation Tools​

Use Case Models are great opportunities for your team to easily create a textual narrative of a process. 

The Use Case module also turns your textual narrative directly into an Activity Flow Diagram. Building a Use Case Model helps your team, and Stakeholders, understand clearly what needs to be accomplished.


Step 4) Adding requirements to a Use Case Model

Authoring & Elicitation Tools​

One of the primary pain point of Use Case modelling is that there is no way to take a Use Case Model and associate requirements to the steps of a Use Case. 

In this video we cover how you can turn every step of your Use Case into a requirement of your choosing. 


Step 5) Building a question list using the FAQ module

Authoring & Elicitation Tools​

Do you gather requirements upfront?

If so, you know that the quality of your elicited requirements is a direct reflection of the quality of questions you ask. For this reason we allow you to use our pre-built question lists with over 3000 questions, or build your own questions to build up your own knowledge base. 

Go to previous playlist

Go to next playlist

Common Questions

About Authoring Tools

The FAQ Module is designed to help teams construct question lists.

It allows you to add questions, and supply answers that are automatically created as requirements within your project. You can create question lists from scratch or use our built-in question lists to get you started. 

This module is based on the idea that you need to ask the best questions in order to gather the best requirements.


With the addition of our ISO Compliance templates, the FAQ module now contains nearly 3000 questions spanning over 20 question templates. 


You can start from scratch and add in your own questions, or add/remove questions from one of our templates. Once you have your question lists exactly as you want you can then save it as your own template to reuse in a different project.

When you select a question in your list and then click “Add an Answer”, you will be given the option to answer this as a new requirement or to answer the question using an existing requirement in your project. 

By answering the question with a requirement, you will be adding requirements directly into your backlog. 

The FAQ module is used by all teams spanning all methodologies. 

If requirements must be elicited, they typically are done so by asking questions to Stakeholders. Whether your team is doing this upfront, such as waterfall or hybrid, or whether they are gathering requirements as they move iteratively, teams can benefit by having the knowledge they use for elicitation all in one place. 

Subscribe to our Monthly Newsletter!

Our newsletter gives new insights into long-standing best practices and how they are evolving in today’s BA world. We give insight into the hottest Requirements topics. Never miss an article or a webinar again by subscribing today!
Requirements Management Tools for Services and Technology industries

Subscribe to our Monthly Newsletter!

Wait! Before you go:

Want to see how ModernRequirements4DevOps works?

We’ll give you a quick Demo!