CASE STUDY;The problem with the first approach is that there can be considerable pressure to implement an early prototype. Often, users observing a working model cannot understand why the early prototype has to be refined further. The fact that the prototype has to be expanded to handle transaction volumes, terminal networks, backup and recovery procedures, as well as provide for auditability and control is not often understood. Another disadvantage of prototyping is that it often leads to functions or extras being added to the system that are not included in the initial requirements document. All major enhancements beyond the initial requirements document should be reviewed to ensure that they meet the strategic needs of the organisation and are cost effective. Otherwise, the final system can end up being functionally rich but inefficient. A potential risk with prototyped systems is that the finished system will have poor controls. By focusing mainly on what the user wants and what the user uses, system developers may miss some of the controls that come out of the traditional system development approach, such as: backup/recovery, security and audit trails.
Try it now!
How it works?
Follow these simple steps to get your paper done
Place your order
Fill in the order form and provide all details of your assignment.
Proceed with the payment
Choose the payment system that suits you most.
Receive the final file
Once your paper is ready, we will email it to you.