Systems Development Life CyclePrototype

What is Prototype?

Prototype

Prototype is an early sample or model of a product built to test a concept or process to act as thing to be replicated or learned from.

The word prototype is derives from the Greek prototypon meaning “primitive form”.

Prototype Development

is the activity of creating prototypes of software applications. It is the incomplete versions of the software program being developed.

The original purpose of a prototype is to allow users of the software to evaluate developers' proposals for the design of the eventual product by actually trying them out.

Prototyping can also be used by end users to describe and prove requirements that have not been considered

A prototype typically simulates only a few aspects, and may be completely different from the final product

Prototyping DiagramThe basic idea here is that instead of freezing the requirements before a design or coding can proceed, a throwaway prototype is built to understand the requirements. This prototype is developed based on the currently known requirements. By using this prototype, the user can get an “actual feel” of the system, since the interactions with prototype can enable the user to better understand the requirements of the desired system.

Requirements Gathering & Analysis

Build Prototype

Quick Design

Refining PrototypeProduct

User Evaluation

Prototype Disadvantages

● May increase the complexity of the system beyond original plans.

● User confusion of prototype and finished system

● Developer misunderstanding of user objectives

● Excessive development time of the prototype

Prototype Advantages

● Users are actively involved in the development

● Since in this methodology a working model of the system is provided, the users get a better understanding of the system being developed.

● Errors can be detected much earlier.

● Quicker user feedback is available leading to better solutions.

● Missing functionality can be identified easily

● Confusing or difficult functions can be identified

● Requirements validation, Quick implementation of, incomplete, but functional, application.

Final pointPrototype model should be

used when the desired system needs to have a lot of interaction with the end

users.

“If a picture is worth 1000 words, a prototype is worth 1000 meetings.”

Thanks!

Josi A.M. Zaid A.Elsa D.A.

13-BCIT-01STMIK Amikom Yogyakarta