Documente Academic
Documente Profesional
Documente Cultură
S OF T W AR E
DE V E L OPM E N T
Gulzeb Zahid
www.gulzeb7.web
s.com
00971558141631
Table of Contents
1
Introduction .................................................................................................................................. 2
Characteristics .............................................................................................................................. 4
3.1
Initial Requirement................................................................................................................ 4
3.2
3.3
3.4
3.5
3.6
4.2
4.3
4.4
Reference.......................................................................................................................................... 14
1 Introduction
It is a software development life cycle methodology in which user or
customer have not any clear idea about requirement and customer may
change its requirements during the programming process. Customer is well
involved in this methodology. Customer give feed back to the developer
that he need this design of software or not and either he need more
function in software or not. Changes can be made in this methodology and
remade in order to define a clear view of software to customer. When
customer see the design then he recommend to start software procedure.
All this effort is made getting no money for developer until customer is
satisfied with design then developer analyze and start the coding and
implementation.
2 Problem Statement
Question is why developer need prototype methodology? Answers are
simple. Developer have exactly the idea of customers problem throughout
the process of prototyping process as customer may not be some time tell
all of its requirement clearly . Then developer understand it easily and also
can give good suggestion to customer for current problem solving and also
suggest him some good benefits and future using option while knowing
the problem of customer.
3 Characteristics
3.1 Initial Requirement
Another reason to choose the prototype methodology for developer that
from the beginning of software development developer have an initial
view from the requirement of customer that what kind of software
customer want to make, after a little bit changes good developer can
design the software according to client requirement.
3.2 Pre-designed Template
One good reason to use prototype methodology that developer can show
multiple pre-designed software models or prototype to customer and
customer can select from these prototypes and it make it easy for developer
to change that prototype according to customer requirement until client is
satisfied then he can start building original software by coding as he
know all requirements from customers. As there is not much effort need on
pre-built prototypes so they can modify easily and taking not more cost
for customer and saving time for developer and also client have choice to
choose from a list of different type of prototype according to his
requirement or choice.
3.3 Reading client mind
Another reason of using prototype methodology for developer is that when
developer listen and understand the client requirement then design a
prototype software for customer, developer itself know that he can solve
the problem of customer exactly or not and either he can make an actual
software for client which can solve his problem before designing an actual
software, like this it will save time for customer and developer also. If
customer requirement and have a base for start structure of his software,
continue and flawlessly.
[1]
4 Prototype Types
A good Developer can create a functional prototype to show the customer
in just some weeks depending upon client requirement. if we are looking
at other methodologies, it will take months to design a good software, like
this it will save the time and money for client as well as save time and
effort of developer while designing a functional prototype and do some
changing in it. A very good reason to use the prototype that error
detection become very much easy during prototype as developer
understand the client requirement and not doing the same mistake while
working on actual software.
There are many types of prototypes which are given below;
a)
b)
c)
d)
Throw-away prototyping
Evolutionary prototyping
Low fidelity prototyping
High fidelity prototyping
Fig 1
Main base is ready for program in this type of prototype only what is need
to do , to design and built a structure in a or more better ways in order to
10
11
12
13
FIG 2
According to my recommendation prototype methodology should be used
for customer when his requirements are changing and he have not any
clear idea about his requirement because it will save time for developer
and save the money for client then the market rate of software
development.
14
5 Reference
[1]
http://www.umsl.edu/~sauterv/analysis/488_f01_papers/Hammer/term
_paper_body.htm visited 20 Apr, 2014
[2] http://it.toolbox.com/blogs/enterprise-solutions/prototyping-types-ofprototypes-14927 visited 21 Apr, 2014
[3] http://istqbexamcertification.com/what-is-prototype-modeladvantages-disadvantages-and-when-to-use-it/ visited 21 Apr, 2014
[4] http://arxiv.org/ftp/arxiv/papers/0803/0803.0162.pdf visited 22Apr,
2014
[5] http://www.tutorialspoint.com/sdlc/sdlc_software_prototyping.htm
visited 23 Apr, 2014
[6] http://en.wikipedia.org/wiki/Software_development_methodology
visited 24 Apr, 2014