PrototypingThe word prototype derives from the Greek prototypon, “primitive form”, neutral from prototypos, “original, primitive”, from protos, “first” and typos, “impression”. The first known use of the word prototype dates back to 1552 in France (Prototype, nd). A prototype is also called a case, exemplification, illustration, instance, example, sample, specimen, or representative of a system or part of a system. A prototype is a small-scale, incomplete but working sample of a desired system using rapid application development (RAD) tools. In the context of systems analysis and design, Whitten and Bentley (2007) describe prototype as “a small-scale, representative or functional model of the user requirements of a proposed design for an information system” (p. 98). Prototyping allows you to quickly create a functional but incomplete model of the future information system. The design of physical systems has traditionally been a paper-and-pencil process. Analysts drew pictures illustrating the layout or structure of inputs, outputs, databases, and the flow of processes in the system. The paper-and-pencil process is time-consuming and subject to considerable errors and omissions. Often, the resulting paper specifications are inadequate, incomplete, or inaccurate (Whitten & Bentley, 2007, p.448). Bowman (2004) states that some of the problems faced by analysts are: implementation is delayed, users are reluctant, the process takes too long, diagrams are poorly understood. Today, many analysts and designers prefer prototyping, which is a modern engineering-based design approach. An advantage of the prototype approach is an iterative process involving a close working relationship between the designer and users (p. 449). Prototyping has developed as a... middle of paper ...... type can solve its own problems and opportunities as easily as conventionally developed systems can. The systems analyst cannot completely replace a prototype with a paper specification. According to Whitten and Bentley (2007), many information systems professionals attempt to prototype without paper specifications. Prototyping should be used to complement, not replace, other methodologies. The level of detail required for paper design must be reduced, but it is not eliminated. Many design problems are not solved by prototyping. Prototyping often leads to premature commitment to a design. When prototyping, the scope and complexity of the system can quickly expand beyond the original plans. This can easily get out of hand. Finally, the very nature of any implementation can prevent analysts, designers, and end users from seeking better solutions..