Application Prototype Development Strategy

You might also like

Download as ppt, pdf, or txt
Download as ppt, pdf, or txt
You are on page 1of 23

Application Prototype

Development Strategy
Prototype
• Prototype is a working system.
• It is developed to test the ideas and
assumptions about the new system.
• It consists of working software that accepts
input, performs calculations, procedures
printed or displayed information, or performs
other meaningful activities.
Prototype contd.
• Iteration Process
• The design and the information produced by
the system are evaluated by the users.
• Prototyping can be effectively done only if the
data are real and live situations.
• Prototypes are relatively inexpensive to build.
• Prototypes are created quickly.
Why Prototyping?
• No System with the characteristics of the one
proposed has yet been constructed by the
developer.
• The essential features of the system are only
partially known others are not identifiable even
through careful analysis of requirements
• Experience in using the system will significantly
add to the list of requirements.
• Alternate version of the system will evolve
through experience and additional development
and refinement of its features
Uses of application prototyping
• Clarifying the user requirements
• Verify the feasibility of a system design
Cont..
• The system users will participate in the
development process

• Another use of the prototype is to verify the


feasibility of a system design.

• Creating a prototype and evaluating its design


through use will prove design feasibility or
suggest the need to find other alternatives.
Foundation for application prototyping
• Development Productivity
• Planned Redevelopment
• User enthusiasm for prototypes
Development Productivity
• Development of an information is a very
lengthy process.
• To make the development process productive
following things should be considered:
– Time lost to incorrect development is minimized
– Design errors are minimized
– User receives the application they need
– Development work does not have to be redone.
Development Productivity contd.
• Some problems faced by the analyst:
– User have a great deal of difficulty in prespecifying
their information needs, especially for a new or
rapidly changing situations
– The complete Specification of requirements is
dependent on the particular way in which the
technology must be used.
– Static descriptions of systems, not exactly states or
communicates the details of the dynamic situations
– Miscommunication of ideas.
Planned Redevelopment
• Prototype applications are created to
recognize the needs of the user.
• Prototype is used as a base block for the
redevelopment of the system.
• Prototype gives a more detailed/complete
specifications which can be a great source for
the development
Reasons for Candidate Application
• Requirements not known.
• Requirements need evaluation.
• High cost.
• High Risk.
• New technology.
Steps of Prototype
Identify known Requirements
• The determination of application
requirements is very important under the
prototype development method .

• Therefore , before a prototype is created ,


both user and systems analyst work together
to identify the known requirements that must
be met.
Develop working System
• It is helpful to begin the prototype process by
developing a general plan so that individuals
know what to expect from each other and
from the development process.
Use Prototype
• It is the user’s responsibility to work with the
prototype and evaluate its feature and
operation. Experience in using the system
helps to determine what changes or
enhancements are necessary or which
inadequate features to eliminate.
Review Prototype
• During the evaluation, system analyst will
wants to capture information on users likes
and dislikes.
• Changes to the prototype are planned with
users before they are made. However, the
analyst is responsible for actually making the
modifications.
Repeat As Needed
• The process described may be repeated
several times to evolve the application. This
process ends when both users and analyst
agree that the system has evolved to include
the necessary features.
Use of Prototypes
• When the prototyping process is complete, a
decision is made about how to proceed. There
are four ways to proceed :-
– Discard the prototype
– Abandon the application project
– Implement the prototype
– Redevelop the application
– Begin another prototype
Abandon Application
• In some instances, the decision will be to
discard the prototype and to abandon
development of the application.
• This doesn’t mean that the prototype process
was a mistake . Rather, the information and
experience gained by developing and using
the prototype has led to a development
process.
Implement Prototype
A second alternative is to implement the
prototype. Sometimes the prototype becomes
the actual system needed. The decision to
implement the system is made under the
following circumstances:-
• The prototype evolved led to an application consisting
of the required features , capabilities and performance
characteristics.
• The application will be used infrequently and speed or
efficiency of operation is not essential.
Cont…
• The application does not affect or interact with
other applications or data in the organization
and meets the needs of its immediate users.
• The application environment is in a state of
flux , it is difficult to determine more long-term
or stable operating needs. Thus, other
development activities cannot be justified .
The prototype will do for the time being.
Redevelop Application
• A successful prototype can provide ample
information about application requirements
and lead to the development of a full
application.
• Completion of the prototype process is thus
not the end of the development process .
Rather, it signals the beginning of the next
activity-full applcation development.
Begin New Prototype
• The fourth alternative is to begin a new prototype
project.
• It may reveal that the features of the application
must be dramatically different if the existing
prototype is inappropriate to demonstrate and
evaluate those features.
• Rather than jumping into a full-scale development ,
management may support the creation of another
prototype that will add to the information.

You might also like