|
 Inspections / reviews
|
 |
|
|
|
Are we creating the right product? And are we doing it the right way? |
|
 |
|
stdSEM validation and verification |
In e-projects, the traditional methods used for the verification of results, such as reviews and tests, are not always sufficient. Sometimes it is necessary to modify long-established review methods. Combing reviews and tests (for example, when inspecting hypertext) requires new approaches. |
|
 |
|
PSE QM is preparing a review web (featuring tools, methods, tips, templates)
|
It goes without saying that "classic" testing is no less important in e-projects than it is in traditional projects. |
|
 |
|
Test |
Usability tests and inspections, however, take on a special importance in e-projects. Other major types of inspections include: |
|
|
|
Usability |
|
|
|
|
|
-
Reviews (documents, code, web reviews)
-
Coordination workshops (partial results or solution approaches are discussed with the customer or client)
-
Inspection of intermediary results
by customer/client
For more information, refer to the "Methods" page:
However, it is not enough to just hold coordination workshops and have intermediary results inspected by the customer/client; all major work results must be subjected to (internal) inspection. For an overview of the results to be inspected and recommendations on who should do this and how this should be done, refer to the "What - Who - How" page: |
|
|
|
|
|
|
|
Inspections must always be documented. These records should not only document what the results of the inspection were and who took part in it, but also against what benchmark the inspection was made. |
|
|
|
|
|