1. An organization is rewriting its Accounts Payable system to move it from an old batch-type mainframe system to a Web-enabled system. No new functionality will be added. The statement of work calls for conversion "as is". Only the input and output systems will be altered for the new environment. Because it is a financial application, testing and verification will be emphasized within the development activities. The schedule allows five months for the project, with two people working on it. What do you think is the most appropriate life cycle approach? What is the advantage of this approach for this project