Software prototyping: Difference between revisions

Revision as of 01:35, 9 February 2022

Revision as of 01:42, 9 February 2022

Line 103:

'''Improved and increased user involvement''': Prototyping requires user involvement and allows them to see and interact with a prototype allowing them to provide better and more complete feedback and specifications.<ref name=Crinnion1991p18/> The presence of the prototype being examined by the user prevents many misunderstandings and miscommunications that occur when each side believe the other understands what they said. Since users know the [[___domain (software engineering)|problem ___domain]] better than anyone on the development team does, increased interaction can result in a final product that has greater tangible and intangible quality. The final product is more likely to satisfy the user's desire for look, feel and performance.

'''Achieve buy-in from investors and executives:''' Software prototyping demonstrates to investors and other stakeholders that the app is viable, and often precipitates funding. Software prototypes turn vague concepts that are difficult to describe into something stakeholders can interact with, which makes them more likely to approve and invest in the software.<ref>{{Cite web|date=2018-11-27|title=7 Benefits of Prototyping Mobile Apps to Save Time and Money {{!}} Discover the Importance of Prototyping Apps - Big Fish|url=https://discoverbigfish.com/blog/mobile-app-prototypes-save-time-money.html|access-date=2022-02-09|website=Custom Software Development & App Design Agency - Big Fish|language=en-US}}</ref>

==Disadvantages==