Before we go into the various techniques and tools that are specific to each of the steps in the systems development life cycle, let us first look at the overall approach. The issues that you must address when you choose one approach over another have already been outlined above: development projects take too long to pay back; by the time they are implemented, the needs have changed, and the time elapsed before errors and shortcomings are experienced in operation make corrections costly. On the other hand, the system may require a critical mass of functionality before it can be truly useful, and a rapid implementation of a part of the system may do no good. Finally, If the system you are building is truly innovative, especially in its use of technology, the risks of failure are high and special precautions must be taken.
- 1354 reads
