Prototyping

Prototyping has been proposed as a method to use for systems that are not overly complex and do not involve too many users or analysts. Just as automobile engineers design prototypes before attempting to build the final car, MIS programmers can build early versions of systems. These systems are then continually modified until the user is satisfied.

The first step in designing a system via prototyping is to talk with the user. The analyst then uses a fourth-generation language and a DBMS to create approximately what the user wants. This first step generally requires only a couple of weeks. The business user then works with the prototype and suggests changes.

The analyst makes the changes and this cycle repeats until the user is satisfied or decides that the system is not worth pursuing. The emphasis is on getting a working version of the system to the user as fast as possible, even if it does not have all the details. The figure at right illustrates the cycle involved in prototyping.

The major advantage of prototyping is that users receive a working system much sooner than they would with the SDLC method. Furthermore, the users have more input so they are more likely to get what they wanted. Finally, remember that a large portion of MIS time is spent making changes. A system designed with the prototyping method is much easier to change because it was designed to be modified from the start.