[263] in ad-lib
Testing Group
daemon@ATHENA.MIT.EDU (Marilyn McSweeney )
Fri Mar 31 18:08:09 1995
To: gyoung@MIT.EDU
Cc: bog-lib@MIT.EDU, acq2@MIT.EDU
Date: Fri, 31 Mar 95 18:04:06
From: mgm@MIT.EDU (Marilyn McSweeney )
Hi, Grant: When I reported on the BOG/Matt discussion in our ACQ2 meeting
on 3/30, I discovered that we had some different recollections about what
the purpose of the Testing Group was going to be. Here's what some of us
remembered from the BOG meeting of 3/23:
Group to be composed of Grant and testing coordinators from the different
functions would be convened very soon to
1. discuss and share testing strategy for the different functional areas,
recognizing that testing might not be "one size fits all".
2. design an appropriate test reporting form(s)
3. decide how to test across functions
4. discuss how to fit in the RFP with the Users Guide as an outline of
what to test
5. insure that whatever "test plan" we develop meets Institute audit
requirements, as well as system acceptance.
This may be phrased badly, but you probably get the idea of what we were
thinking. Some folks had this broad view, while others were thinking that
the testing group was primarily going to stick to no. 3 on the list above.
Can you provide some clarification for us? I know the Ad-Cat group has
already done some good work on this, and we've got some ideas, but were
uncertain how far to go before the group was convened... Thanks, MGM
