Using inteGREAT would eliminate inconsistencies in requirements documentation, increase team moral, enhance maintainability, and increase team productivity. This is accomplished through requirements reuse and repurposing of requirement definitions  into diagrams and documentation.

Additional benefits are:

·    Communication is improved – information is defined within inteGREAT. Stakeholders from various teams within the organization can process and understand the information regardless of location, language, and cultural barriers.

·    Code and Test data can be reused – Requirements are defined within inteGREAT, and code is produced based on those specifications. The code is then tested using those same requirements in order to ensure traceability.

These programming modules can now be reused in other parts of the organization. The business analyst can simply reuse these requirements in his process definition, and the development team can then ‘reuse’ the corresponding section of code. Stakeholders can be assured that the information is identical, and that sufficient quality assurance measures have been executed.

·    Traceability – Once a module is linked to its corresponding goals and functional requirements, the traceability is permanently in place. If the module is reused, then the traceability is there for the new section of code as well.