Tool and method reciprocity: a case study in requirements management

The paper examines the reciprocal influence of method, process and tool as evidenced in a case study in which a requirements management method and process were defined, evolved and applied on projects. Although a tool is primarily a means of implementing a defined method, it is inevitable that the evolution of the method and process will be influenced by the chosen tool. In the case study two tools were examined. This examination yielded important insights into requirements management issues. These insights contributed to the refinement of their defined method and process, as well as helping us identify desired tool improvements that would better support the process. Based on experience with actual projects it is argued that organizational maturity is a key factor in determining when and how to introduce a method-process-tool troika