User Oriented Design

 

Problems with the Conventional View : In the conventional approach to systems analysis and design, the analyst is skilled leader.  The analyst interviews users, collects data, and returns to the information services department to create a new system. Instead of viewing the analyst as the designer of the system, we recommend strongly that users design their own systems. Stressing user input in design has become more popular lately.  It is often called joint applications development (JAD)  and includes both users and analysts.  (IBM coined the term JAD and it offers a much more structured series of meetings and steps than described here.)

 

A more user-oriented approach to design may require deviations from the standard systems life cycle.  Although the conceptual steps represented in the cycle may be followed, innovations will be included.  For example, design is often facilitated by prototyping.  A prototype  is a smaller-scale version of a planned feature for a new system.   A good example is sales forecasting. We can code the new forecasting routine on a personal computer and analyze past data for a limited number of products.  Users will be intimately involved in this test so they can provide feedback on the prototype and evaluate its output.  When they are satisfied, the prototype can be programmed in final form with more errors routines, data manipulation features, and so forth, which had been excluded to keep the prototype simple.

 

Design Team: To coordinate users and the IS department staff, we recommend the formation of a design team with a user as head of the team.  Having a user in charge makes the users' role apparent, ensures time will be available from other users and demonstrates a strong commitment to users on the part of the information services department.  Normal job activities should be reduced for the user in charge of the design team.