INDEX | ORGANISATION | TIME LINE | PEOPLE | STORY | RESEARCH METHOD | COMMENTARY | FINDINGS | HELP | BOTTOM
Testing is always a problem with prototyping because although the system automatically gets tested as part of the prototyping process, it is also necessary to do systematic tesing at both unit and system level after prototyping is complete. There are indications that phase I suffered from this problem but that the system was fairly thoroughly tested during prototyping (00428, 00429, 00271). This testing was largely done within the team (00067) not by users because of resource constraints (00517, 00599) and a lack of commitment (00679, 01030). As a consequence testing during phase I did not really ensure user acceptance. There was also the implication that use during phase I prototyping largely involved Keith and David (00082) rather than the eventual users.
 |
Commentary
|
 |
|
Social influence
|
|
 |
Technical influence
|
 |
INDEX | ORGANISATION | TIME LINE | PEOPLE | STORY | RESEARCH METHOD | COMMENTARY | FINDINGS | HELP | TOP
© Clare Tagg 2000