This site is the archived OWASP Foundation Wiki and is no longer accepting Account Requests.
To view the new OWASP Foundation website, please visit https://owasp.org
Project Information:template Classic ASP Security Project - Final Review - Second Reviewer - F
Clik here to return to the previous page.
FINAL REVIEW | ||
---|---|---|
PART I | ||
Project Deliveries & Objectives |
OWASP Classic ASP Security Project's 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. |
All the objectives are fully met up to Alpha Quality. | |
2. At what extent have the project deliveries & objectives been accomplished? Having in consideration the assumed ones, please quantify in terms of percentage. |
100% | |
3. What kind of help is required either from the Reviewers or from the OWASP Community? |
Software testing in order to receive feedback. | |
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? |
Use of google code or source forge as tool repository, however the tool was uploaded to the main page of the project and is fully available to everyone. | |
2. Having into consideration the OWASP Project Assessment Methodology which criteria, if any, haven’t been fulfilled in terms of Beta Quality status? |
Generation of tool documentation (user guide, installation, etc). | |
3. Having into consideration the OWASP Project Assessment Methodology which criteria, if any, haven’t been fulfilled in terms of Release Quality status? |
Not ready for Release Quality yet. | |
4. What kind of help is required either from the Reviewers or from the OWASP Community? |
As mentioned before, I think software testing from the OWASP Community could be very useful to get feedback. |