Requirement Management

AyMINE supports requirement management for project of all types of projects. The requirement management is important regardless if projects manages the company movement, developing a new product, or anything else.

Requirement management is fully integrated with task management and testing, so requirements are linked with tasks and work reports. It provides clear overview which requirements are processed, how much time they cost, who works on them and what status they have.

Integrated and Custom Methodology

Solution supports the logic of current widely used standards including all processes that are required and necessary for effective management requirement. The major processes are described below:

Relation and Traceability Management

AyMINE allows you to manage relations between requirements, and in particular to maintain traceability, which requirements have been derived from which. At the same time, it ensures that it is used logically and correctly. It instructs the user to derive requirements correctly, so that there is no wrong cycle of derived requirements, for example.

Relations are used not only among requirements, but also to other objects, e.g. tests or other quality checks. The relations between requirements and controls definitions as well as relation to the control realisation give complete control by whom was the requirement verified.

Configuration management

Requirements are managed by the configuration bundles, which make control over their processing.

Requirements stored in configuration bundles remain fully linked to other requirements, but they are locked and protected against changes and modifications.

Change control and requirements versioning

Requirements could be modified until they are locked by a closed version. The lock is typically created by a configuration management, but they can also be locked individually.

For locked requirements a new version could be created. The old and new versions are interconnected, and the new version can inherit from the old all the links that the original requirement had

Manage special symbols

If special symbols are attached to a requirement, for example, a safety requirement mark, these symbols are consistently displayed everywhere and automatically inherited within traceability relationships to derived requirements.

Typical special symbols are a security requirement, a cybersecurity requirement, a legislative requirement, etc. Special symbols are part of the system setup that is done by companies according to their needs.

Support for custom methodologies

Requirements, like all other objects, are part of the workflow system, within which it is possible to define custom procedures, methodological guidelines or quality standards. The requirement management system is prepared in such a way that it fully supports important standards of component development: ISO 26262, IATF 16949, ISO 61508, ASPICE, CMMI and others.

Key Requirement management services

The system supports all necessary functions and services to work effectively with requirements:

Sharing, commenting and discussing

Each requirement can be internally discussed, commented and reviewed by project stakeholders. Discussion is stored with the requirement and always available to any team member or project auditor.

Task Management

For requirements, it is possible to create tasks and thus enter their processing – solution preparation, verification, or any other activity.

Tasks can be defined for a group, so more people are involved in the solution. The responsible person has task available at a mobile phone, MS Outlook or another calendar tool (tasks are accessible via the CalDav interface). For more information, see the Task Management chapter.

Enterprise Architect Support

Requirements can be directionally synchronized with the Enterprise Architect (a modelling tool from the Sparxsystems) including all relations. The requirements created in AyMINE are available in the Enterprise Architect model and vice versa. Thy can be processed by team in the AyMINE and included in the analytical model managed in the Enterprise Architect
For more information, see the eacon module.

Requirements in multiple languages

The documentation of the requirement allows it to be documented in multiple languages.
Teams that consists people from several countries or a project implemented for a foreign customer can manage requirement documentation in several languages and grantee that everybody understand them properly.

It is also possible translate requirements automatically within the system and then check and verify the translation.

Give us contact

Do you prefer to ask us directly?

Call us +420 605 203 938 (the Czech Republic)

or use this contacts

PDQM © PDQM, Ltd. 1997-2007-; Copyright and Legal Disclaimer;