Software Testing Prototype: The Pivotal Role of User Acceptance

This essay emphasizes the critical role of user approval in software development, particularly during the prototype phase. It highlights that software's ultimate quality and functionality are determined by users, not developers. The prototype model allows users to learn about software criticalities, ensuring the final product aligns with their specific requirements. User feedback bridges the gap between initial needs and system functionalities, enabling developers to refine the software iteratively. The process continues until the prototype meets user expectations, either leading to a refined final product or valuable insights for developing a new system. The conclusion underscores that user input is paramount for creating cost-effective and user-satisfying software.

Running Head: Software Testing
Prototype Software Testing

Software Testing 1
Introduction
Software is the set of computer and other related instructions that enables those devices to
function. Software is designed to meet the general or specific user requirements and needs. In
case of special purpose software, it is quite necessary to know the exact requirements of the
intended users of software that is to be developed to fulfil their specific requirements. The
purpose of the software can only be achieved when the required functionality or specification
is clearly defined by the users well before the software is created.
Following are the reasons that require user’s approval before the dev9elopment of full-
fledged software:
 Software developments involve considerable time, efforts and cost:
Since software development takes considerable time and efforts to reach at the final stage of
user approval, it is important to understand that a prototype model of the software must be
prepared before developing and delivering the final version of that software for the users.
Prototype is the pivot version of the software that must be created at the small scale within
the limited cost and time (Naik & Tripathy, 2011).
 Software quality is subject to user’s approval and not designer’s approval:
This is necessary because the ultimate quality and functionality of the software is to be
decided by the users and not by the developers of the software. For the purposes of general
quality control and assurance, user’s view regarding the real attributes of the software
influences its life and success to the great extent (Lewis, 2000). The prototypes model of the
software is prepared with the intention of seeking user’s acceptance for the intended full
version of software.

Software Testing 2
 To enable the users learn about software criticalities:
This model is aimed at enabling the final users to learn about the functionalities and
criticalities of the software by using it in the practical world so that they decide as to whether
the intended software will be able to meet their specific requirements (Ciortea, et al., 2010).
 To bridge the gap between user’s complete requirements and system functionalities:
After using the prototype model, the users can instruct the developers to modify, replicate,
expand or even replace it in accordance with the needs of those users. If the users are satisfied
with the pivot version of full software they can approve it by allowing the developers to
proceed with the creation of full software. If the users are not satisfied with the prototype
version they suggest the required changes in the software to improve it. The software
prototypes are prepared until the time users finally approve it completely. The final prototype
that meets all the requirements of the users is either refined or scrapped. If the cases when the
said model is scrapped, the knowledge obtained from its creation is used to design and
develop the real user system (Kaner, Falk & Nguyen, 2000).
Conclusion:
It is easy to conclude that users play the most important role on the software quality and their
feedbacks allows the system developers to create the software that can completely satisfy the
users in the cost and time effective manner.

Software Testing 3
References:
Ciortea, L., Zamfir, C., Bucur, S., Chipounov, V. and Candea, G., 2010. Cloud9: A software
testing service. ACM SIGOPS Operating Systems Review, 43(4), pp.5-10.
Kaner, C., Falk, J. and Nguyen, H.Q., 2000. Testing Computer Software. 2nd edn. India:
Dreamtech Press.
Lewis, W.E., 2000. Software testing and continuous quality improvement. 1st edn. Florida:
Auerbach publications
Naik, K. and Tripathy, P., 2011. Software testing and quality assurance: Theory and practice.
Retrieved from: < http://ebooks.bharathuniv.ac.in/gdlc1/gdlc1/Software%20Engineering/
SOFTWARE%20TESTING%20AND%20QUALITY%20ASSURANCE,Theory%20and
%20Practice%20-%20KSHIRASAGAR%20NAIK.pdf> Accessed on: 08.07.2018.

Software Testing 4

Software Testing 5

Software Testing 6

Software Testing 7