Prototyping

October 25, 2007

Prototyping!

Prototype is the model of a business that serves as a model for future development.

A prototype of a business system may be used to demonstrate its initial performance and the system may be modified to achieve its objective.

A prototype may be used to

  • select the best design from a number of designs

  • to test a chosen design under different environmental conditions

  • To verify that the users needs have been met.

  • Verify that the design meets the specifications

Generally prototyping is not advisable for batch systems or one that produces standard hard copy report using a large institutional database. Online interactive systems favour prototyping e.g. advisable in decision support system.

There are 3 approaches to prototyping according to logical structured design methodology.

  1. 1st Approach:

In this approach a series of menus and screens are built and the user processes transaction as he would do in a live system. If it’s acceptable the prototype is further developed. This system is best when the user requirements are well defined and it does not support logic or a database.

  1. 2nd Approach:

This is building of a throw away version for user trials. It incorporates system logic in addition to menus screen and databases. This is the best used in large complex projects where user’s requirements are not well defined. The prototype software is unlikely to have performances and facilities for implementation as a physical system

  1. 3rd Approach

This is the second approach but the prototyping software is intended to form the final system. This becomes the pilot for a project with phased implementation plan.

Advantages of prototyping:

  • Enable the user to visualize how the system will work.

  • An accurate user requirement is met by or in that if one does not want a certain system or if it has a weakness one can change.

  • Increases productivity

  • Saves time and money on system analysis.

  • Improves or reduces backlogs by improving turn-around time in finding system solutions.

  • New user requirements can evolve

  • Increase productivity

  • Saves time and costs by ensuring they are implementing the correct design.

  • Heavy user involvement less resentment

  • Early training

  • User feel confident supporting a system they have already tested.

Recommended Text


Page copy protected against web site content infringement by Copyscape

Written by Anthony Kinyua · Filed Under Information Technology 

Comments

Got something to say?

You must be logged in to post a comment.