[363] in Athena User Interface
Beta, system, and usability testing, p.s.
daemon@ATHENA.MIT.EDU (Janet Littell)
Mon Aug 14 11:44:12 2000
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Message-Id: <v04020a0bb5bdc3454bb1@[18.152.0.213]>
Date: Mon, 14 Aug 2000 11:44:09 -0400
To: tibbetts@mit.edu
From: Janet Littell <jlittell@MIT.EDU>
Cc: "Christopher D. Beland" <beland@mit.edu>, kcahill@mit.edu, sbjones@mit.edu,
aui@mit.edu
Usability testing provides optimally helpful results if it's done on
software where everything is already working, that is on software that has
mostly passed the "system testing" phase and major bugs have been fixed.
Janet
>> - In the proposed schedule with dates, where beta testing appears, could
>> usability testing also be included? Ideally beta/system testing occurs
>>befo
>> re
>> usability testing, but they can go on in parallel if necessary.
>
>This confuses me. What are the goals of usability testing that occurs
>after system testing? That is, after a product has been beta tested,
>it is no longer advisable to make fundamental changes which might be
>suggested by usability testing.
How about dividing beta testing into two parts explicitly, system testing
and usability testing?
Janet
