Abstract
This paper will describe and discuss the contents of a human factors field test plan in support of software development. Defining control of a test is, as pointed out by Shneiderman, of necessity in field testing to avoid getting volumes of “interesting” data which is neither replicable nor generalizable. In addition, the degree to which the test plan supported the actual test and predicted potential problem areas will be discussed.
Sign-in/Register to access full text options 
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a callMore From: Proceedings of the Human Factors Society Annual Meeting
Disclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.
