CS504 GDB solution

by **kamran** Sun Jul 10, 2011 4:47 am

A part of Software Engineering community claims that a “Prototype” is part of requirements elicitation as it helps to refine the requirements further. On the other hand, in second stance, some people claim it to be part of the design process as it provides a base (e.g. interface design etc.) for developing an operational product.

What is your stance? please provide your opinion with logical reasons with in five (5) to seven (7).

by **kamran** Sun Jul 10, 2011 4:48 am

Solution:

I will go with the first choice because.....
• Prototypes may be easily changed or even discarded.
• Prototyping may improve communication between and among developers and customers
• Users may be more satisfied with systems developed using prototyping.
• A prototype may provide the proof of concept necessary to attract funding.
• Early visibility of the prototype may help management assess progress.
• Prototypes may demonstrate progress at an early stage of development.

CS504 GDB solution

CS504 GDB solution

Re: CS504 GDB solution