Project Information:template JSP Testing Tool Project - Final Review - First Reviewer - D
From OWASP
Clik here to return to the previous page.
| FINAL REVIEW | ||
|---|---|---|
| PART I | ||
|
Project Deliveries & Objectives | ||
| QUESTIONS | ANSWERS | |
|
1. At what extent have the project deliveries & objectives been accomplished? Having in consideration the assumed ones, please exemplify writing down those of them that haven't been realised. | Design documentation, code, and user documentation have been completed. The code basically works, may only need performance tuning | |
|
2. At what extent have the project deliveries & objectives been accomplished? Having in consideration the assumed ones, please quantify in terms of percentage. | 90%-95% | |
|
3. Please do use the right hand side column to provide advice and make work suggestions. | What are the possible ways to improve performance? Would distributed/grid/cloud computing be a candidate? | |
| PART II | ||
|
Assessment Criteria | ||
| QUESTIONS | ANSWERS | |
|
1. Having into consideration the OWASP Project Assessment Methodology which criteria, if any, haven’t been fulfilled in terms of Alpha Quality status? | 'Alpha Quality' has definitely been achieved at the 50% stage. | |
|
2. Having into consideration the OWASP Project Assessment Methodology which criteria, if any, haven’t been fulfilled in terms of Beta Quality status? | Beta quality is practically there: documentation, very clean and well-organized code, and working jars, as well as canned reports for review constitute beta. | |
|
3. Having into consideration the OWASP Project Assessment Methodology which criteria, if any, haven’t been fulfilled in terms of Release Quality status? | Close to release quality, just needs a few people really using it to hammer out the details. | |
|
4. Please do use the right hand side column to provide advice and make work suggestions. | What are the future plans, how will it be made available to the coding public? | |
