Fundamental to the success of an application development and systems integration project is the existence of a stable set of detailed system requirements. For this reason, full-scope, fixed-price projects are risky. The 'pecking order' of requirements documents must be defined to provide both Buyer and Vendor with clarity on what functionality will be delivered. Non functional requirements are an essential prerequisite of infrastructure design. RAD projects require tight management to avoid 'galloping elegance'. Also key to the success of an application development and systems integration project is the correct choice of technical platform or architecture. The next key requirement is that the design should be documented, 'frozen' as a baseline for the development, and subject to change management.
Requirements and Design Baselines, Page 1 of 2
< Previous page Next page > /docserver/preview/fulltext/books/pc/pbpc003e/PBPC003E_ch15-1.gif /docserver/preview/fulltext/books/pc/pbpc003e/PBPC003E_ch15-2.gif