The stronger the shared understanding, the more complex and rigorous the RE process should be.

When schedules and budgets are constrained, a lightweight RE process is often adopted.

When there is a high degree of trust between the customer and the supplier, more formal specifications should be used.

The less experienced the Requirements Engineers are, the less sophisticated the RE process should be.

The more complex the system to be implemented is, the more formal and rigorous the RE process should be.

Focus on the acquisition costs.

Apply the tool to a non-critical project.

Deploy the tool in parallel with an ongoing project to ensure redundancy and minimize risks.

Train employees to ensure proper and effective use of the tool.

Version management of individual requirements

Generation of result documents

Requirements tracing

Creation of graphic models

Documentation of requirements and goals

the higher the benefit of the requirement.

the more familiar the developing team is with the context.

the higher the freedom to be given to developers.

the higher the availability of feedback from stakeholders.