Topic: Software prototyping !!Advantages---Disadvantages!

Message

   Software prototyping

The
prototyping model is a software development process that begins with
requirements collection, followed by prototyping and user evaluation.
Often the end users may not be able to provide a complete set of
application objectives, detailed input, processing, or output
requirements in the initial stage. After the user evaluation, another
prototype will be built based on feedback from users, and again the
cycle returns to customer evaluation. The cycle starts by listening to
the user, followed by building or revising a mock-up, and letting the
user test the mock-up, then back.

In the mid-1980s, prototyping
became seen as the solution to the problem of requirements analysis
within software engineering. Prototypes are mock-ups of the screens of
an application which allow users to visualize the application that is
not yet constructed. Prototypes help users get an idea of what the
system will look like, and make it easier for users to make design
decisions without waiting for the system to be built. When they were
first introduced the initial results were considered amazing. Major
improvements in communication between users and developers were often
seen with the introduction of prototypes. Early views of the screens
led to fewer changes later and hence reduced overall costs considerably.

However, over the next decade, while proving a useful technique, it did not solve the requirements problem:

  * Managers, once they see the prototype, often have a hard time
understanding that the finished design will not be produced for some
time.
    * Designers often feel compelled to use the
patched-together prototype code in the real system, because they are
afraid to 'waste time' starting again.
    * Prototypes principally
help with design decisions and user interface design. However, they can
not tell what the requirements were originally.
    * Designers and
end users can focus too much on user interface design and too little on
producing a system that serves the business process.

Advantages of prototyping

    * May provide the proof of concept necessary to attract funding
    * Early visibility of the prototype gives users an idea of what the final system looks like
    * Encourages active participation among users and producer
    * Enables a higher output for user
    * Cost effective (Development costs reduced)
    * Increases system development speed
    * Assists to identify any problems with the efficacy of earlier design, requirements analysis and coding activities
    * Helps to refine the potential risks associated with the delivery of the system being developed

Disadvantages of prototyping

    * User’s expectation on prototype may be above its performance
    * Possibility of causing systems to be left unfinished
    * Possibility of implementing systems before they are ready.
    * Producer might produce a system inadequate for overall organization needs
    * Producer might get too attached to it (might cause legal involvement)
    * Often lack flexibility
    * Not suitable for large applications
    * Project management difficulties

Author	Message
tanushree Senior Member Joined: 04Apr2007 Online Status: Offline Posts: 2160	Topic: Software prototyping !!Advantages---Disadvantages! Posted: 15Oct2007 at 3:27am
	Software prototyping The prototyping model is a software development process that begins with requirements collection, followed by prototyping and user evaluation. Often the end users may not be able to provide a complete set of application objectives, detailed input, processing, or output requirements in the initial stage. After the user evaluation, another prototype will be built based on feedback from users, and again the cycle returns to customer evaluation. The cycle starts by listening to the user, followed by building or revising a mock-up, and letting the user test the mock-up, then back. In the mid-1980s, prototyping became seen as the solution to the problem of requirements analysis within software engineering. Prototypes are mock-ups of the screens of an application which allow users to visualize the application that is not yet constructed. Prototypes help users get an idea of what the system will look like, and make it easier for users to make design decisions without waiting for the system to be built. When they were first introduced the initial results were considered amazing. Major improvements in communication between users and developers were often seen with the introduction of prototypes. Early views of the screens led to fewer changes later and hence reduced overall costs considerably. However, over the next decade, while proving a useful technique, it did not solve the requirements problem: * Managers, once they see the prototype, often have a hard time understanding that the finished design will not be produced for some time. * Designers often feel compelled to use the patched-together prototype code in the real system, because they are afraid to 'waste time' starting again. * Prototypes principally help with design decisions and user interface design. However, they can not tell what the requirements were originally. * Designers and end users can focus too much on user interface design and too little on producing a system that serves the business process. Advantages of prototyping * May provide the proof of concept necessary to attract funding * Early visibility of the prototype gives users an idea of what the final system looks like * Encourages active participation among users and producer * Enables a higher output for user * Cost effective (Development costs reduced) * Increases system development speed * Assists to identify any problems with the efficacy of earlier design, requirements analysis and coding activities * Helps to refine the potential risks associated with the delivery of the system being developed Disadvantages of prototyping * User’s expectation on prototype may be above its performance * Possibility of causing systems to be left unfinished * Possibility of implementing systems before they are ready. * Producer might produce a system inadequate for overall organization needs * Producer might get too attached to it (might cause legal involvement) * Often lack flexibility * Not suitable for large applications * Project management difficulties Post Resume: Click here to Upload your Resume & Apply for Jobs

	IP Logged


One Stop Testing Forum : Software Testing @ OneStopTesting : Beginners @ OneStopTesting