Scribd
Upload
170 views13 pages

Software Prototyping: Vishnu Chaitanya Reddy Nara Vcnoo1@latech - Edu

Software prototyping involves implementing presumed software requirements to learn about actual requirements or alternative designs. It has several benefits: assessing market success of requirements; testing feasibility without building the whole system; and involving end-users in design. There are different types of prototyping including throwaway, evolutionary, and operational. Throwaway prototyping derives end system requirements and is discarded after, while evolutionary prototyping delivers a working system alongside requirements refinement. Prototyping clarifies missing requirements and user wants, reduces risks, and allows early working systems, but may lose focus on quality or plunder new ideas.

Uploaded by

gowthamj5400
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
170 views13 pages

Software Prototyping: Vishnu Chaitanya Reddy Nara Vcnoo1@latech - Edu

Software prototyping involves implementing presumed software requirements to learn about actual requirements or alternative designs. It has several benefits: assessing market success of requirements; testing feasibility without building the whole system; and involving end-users in design. There are different types of prototyping including throwaway, evolutionary, and operational. Throwaway prototyping derives end system requirements and is discarded after, while evolutionary prototyping delivers a working system alongside requirements refinement. Prototyping clarifies missing requirements and user wants, reduces risks, and allows early working systems, but may lose focus on quality or plunder new ideas.

Uploaded by

gowthamj5400
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
You are on page 1/ 13

SOFTWARE PROTOTYPING

Vishnu Chaitanya reddy Nara


vcnoo1@latech.edu


Introduction
what is software prototyping ?
It is the process of implementing the presumed software
requirements with an intention to learn more about the actual
requirements or alternative design that satisfies the actual set of
requirements .

Need for software prototyping
-To assess the set of requirements that makes a product
successful in the market
-To test the feasibility without building the whole system.
-To make end-user involved in the design phase

Phases of prototyping




Different Phases

Define the prototype objectives


Define the functionality


Develop Prototype


Evaluate Prototype.
Types of Prototyping
Types of Prototyping


Throw away prototyping


Evolutionary prototyping
.

Operational prototyping



Throw away prototyping



Objective - Derive end system requirements

Throw away prototyping is one type of approach where an initial prototype
is built mainly focusing on the poorly understood requirements

Once the requirements are understood requirements document is updated
and a conventional development process is followed to build system





Evolutionary Prototyping

Objective Deliver a working system + requirements

Evolutionary prototyping is the one in which a system is build using the well
understood requirements.
Evolutionary Prototyping
Advantages
Accelerated Delivery

Makes User Commit

Look like feel

Disadvantages

Availability of specialist skills

Maintenance over long term
Operational Prototyping

Used when requirements are either critical and understood or not
critical and poorly understood .

Throw away prototypes are selectively built on top of evolutionary
prototype

A trained prototyper keeps track of user .
Tools and Techniques


Low level tools

High Level languages

Fourth Generation Languages (4GL)

Visual programming .

Benefits of Software Prototyping
It makes the developers clear about the missing requirements.
Lets the developers know what actually the users want.

Reduces the loss by bringing the manufacturer to a conclusion
weather the system which we are about to build is feasible or not
rather than building the whole system and finding it .

One can have a working system in before hand.
It brings the user to get involved in the system design


Troubles of Software Prototyping


Developers may loose the focus on real purpose of prototype and
comprise with the quality of system .

New born ideas will be plundered at the initial stages

Prototyping will not reveal the non functional requirements like
robustness, safety etc .

You might also like