Walkthroughs may be held at various points in the system development life cycle. In addition to system design, they may be held to review system test plan, program design, and production acceptance. In each c the people who will be running the system should be consulted.
The probability of success improves with the user's interest and involvement in the design of the system. The user can save a system that might otherwise he of marginal benefit, and likewise he/she can kill a superbly designed system if it is perceived as making only a small contribution to performance. Thus, promoting a user’s contribution in the walkthrough and throughout the design phase can be crucial for successful implementation.
User involvement gives the designer important feedback as the design is being completed. It also provides the user with a basic understanding of what the candidate system will and will not do. User involvement invariably paves the way for acceptance of the system by the user staff. It also bridges the gap between the designer, who as a staff person has an "expert" perspective, and the user, who is more typically "line" with a generalist or managerial view.
No comments:
Post a Comment