Frequently asked questions

You can start using agile-Requirements with a single license.

While a single license allows you to explore certain features, it does not allow you to use collaborative features.

Licenses are floating and therefore unnamed (not assigned to a given user account).

You can define as many users as you like.

The number of users who can work simultaneously with agile-Requirements is limited by the number of licenses you have purchased.

Agile-Requirements does not offer a free trial version.

However, you can try agile-Requirements for 6 months with a discovery version and for a modest fee. This cost covers account creation and use of the technical infrastructure (data storage and transfer).

The discovery version cannot be renewed once its term has expired.

Yes, the discovery version gives you access to all the tool’s functions.

The only limitations are the maximum number of licenses you can acquire, the number of languages you can use and the maximum number of requirements you can create.

Office tools have numerous drawbacks, which are well known and documented in the literature, as soon as a project exceeds a few dozen requirements. These include

• Difficulty finding information in its latest version;
• Impossible to maintain dependency relationships between requirements;
• Difficulties in finding out which version of a requirement is currently implemented in your IS;
• IS update times and costs soar with functional complexity and number of requirements.

A requirements management tool allows you to:

• Centralize requirements in a single repository;
• Give access to requirements only to those in your organization who need access to them;
• Maintain dependency relationships between requirements, thus facilitating the implementation of regulatory changes and new organizational needs;
• Improve the quality of your requirements repository while reducing the amount of information produced (duplicate identification mechanisms);
• Significantly reduce IS development costs and lead times.

In addition to being a publisher of agile-Requirements, CATISYS can support you in building your requirements repository, improving the quality of this repository and professionalizing your teams of functional analysts.

The creation of an environment for your organization is carried out by our team, usually the same day or the next working day following your request.

Your environment comes with:

• An administrator account;
• A project with a standard folder structure;
• 3 user groups offering the different roles available.

With this standard project and file structure, you can start working with agile-Requirements straight away. The ability to import requirements via Microsoft Excel further accelerates the learning curve.

New user accounts can be created in just a few clicks.

Your organization’s administrator can request a change in the number of licenses or a change of license at any time.

This quick and easy request is made directly from the administration interface.

Agile-Requirements lets you change your password directly from the login page.

A temporary password will be sent to you by email. This password will immediately replace the old one.

You will then need to enter a new password.

You can also change your password at any time from your user profile.

You can set up dual authentication for your users (MS or Google Authenticator).

In all cases, double authentication is required to access the administration interface.

Double authentication is not recommended for users. It is generally too cumbersome for a user who will be required to log in several times during the working day, and can act as a brake on adoption of the tool.

Your organization owns and retains all the data you can create in agile-Requirements: projects, requirements, discussions, requests, reviews, sprints, users.

You can export project data to an XML file at any time.

In the event of non-renewal of licenses by your organization, all your data, with the exception of billing data which must be retained by CATISYS for regulatory reasons, will be deleted within 2 weeks of the end date of your license.

No data from your repository is retained or used by CATISYS or any third party after this deletion. Backups of your data will be overwritten as they are replaced by more recent backups.

CATISYS will never communicate your data to a third party except in the case of a legal request.

All communication between the user, his administrator and CATISYS support is via requests in agile-Requirements.

The user writes up his request (for example, an upgrade request or a request to create a new project) and sends it to his administrator.

All users in your organization can contribute to this application.

The administrator closes the request (e.g. by giving the user access to the project) or forwards it to CATISYS support (e.g. for an upgrade request).

CATISYS examines the request and either closes or rejects it.

Agile-Requirements lets you remove a project from the list of projects to which you have access, from your profile and after logging in.

No need to involve your administrator.

This action is immediate and does not require you to reopen your session.

Agile-Requirements offers a number of diagrams (UML and BPMN). These diagrams enable the analyst to express/clarify the need in visual form, and thus perfectly complement requirements expressed in textual form.

However, Agile-Requirements is not a modeling tool, such as those used by your technical teams, and is not intended to replace these tools, whose use requires technical skills not generally possessed by your business analysts.

As no such need has been expressed, Agile-Requirements does not currently offer export in a standard exchange format to modeling tools.

Agile-Requirements offers collaborative reviews, so you don’t need to generate traditional functional documentation. However, if you wish, you can export a project as an XML file (including diagrams as images). From these extractions, you can generate conventional documents (Word, PDF) using tools such as Windward Studios ™.

Agile-Requirements only uses technical cookies that are strictly necessary for the operation of the application.

No information concerning your organization or your users, other than that strictly necessary for your use or for billing purposes, is stored by CATISYS or passed on to third parties.

There are no limits other than the maximum number of requirements defined by your license.

However, there are a number of best practices to follow to facilitate access to your project requirements:

Limit the number of subfolder levels

While it may be tempting to create many levels, this can lead to an excessive reduction in the number of requirements per folder and a significant amount of time spent just opening each folder.

Limit the number of requirements per file

In practice, it is not desirable to have to use your browser’s scroll bar to view the list of requirements for a file.

Limit the number of requirements per project

A maximum of 500 (standard project) to 1,000 (specific requirements) requirements of all types still allows users to navigate and find the requirements they need to work on fairly easily. Apart from the initial browser load, the number of requirements in a project has no impact on the display and processing times for requirements.

Do not mix requirement types in the same folder

Agile-Requirements allows you to define the type of direct requirements you can create in a folder (none, all, or a specific type). This feature helps you build a structured repository that is easy for all your users to use.