How do you deal with changing requirements?

Integrator has been designed to let you easily cope with change at all levels. Requirement change can have drastic impact on a project. It is thus important to first assess the impact on the project, then start modifiying the requirement chain to adapt to the new reality. Perhaps some tests need parameters to be modified? Maybe there are some product areas that will need more specification details? You can easily answer these questions while looking at the most up-to-date information directly into your project within Integrator.

A key element in change management is the necessity to keep everybody on the same page. In theory this is trivial but, in practice, this is often the area that is the most challenging. Questions like:

• What are the new specs?
• Who proposed the modification?
• Which unit has been re-tested, yet?

Can be answered in a few simple mouse clicks. If you have been through this dance before, you know how difficult it is to keep it together unless you have a tool in place to assist you with referential integrity.

Integrator is very easy to update and the incentives for keeping Integrator up-to-date are far greater than the perceived burden of performing the update. This is a major advantage in favor of Integrator when dealing with change.

In fact, you can just directly edit a requirement and follow the cascading changes down to test cases and spot all the units that need to be re tested. Using Integrator to assess the impact on the status of your project is trivial with the data drill down in the tree-view.

Integrator also features a specification upgrade mechanism that helps you deal with modifications within specification documents themselves. This feature is there to help you replace an old specification with a completely revised one and, yet, save time by re-using all unmodified requirement statements.