Project Information:template Teachable Static Analysis Workbench - Final Review - First Reviewer - D

De OWASP
Saltar a: navegación, buscar

Clik here to return to the previous page.

FINAL REVIEW
PART I

Project Deliveries & Objectives

OWASP Teachable Static Analysis Workbench 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.

Input Validation functionality works as stated.

2. At what extent have the project deliveries & objectives been accomplished? Having in consideration the assumed ones, please quantify in terms of percentage.

The promised deliverables and functionality have been completed 100%.

3. Please do use the right hand side column to provide advice and make work suggestions.

  1. The Technical Report should have a "How To" section that describes how to write additional analyzers for the project. If not, then a "Lessons Learned" for security analysts or developers who want to extend the project on their own, but could use your insight from building the first analyzer.
  2. I found a couple of minor spelling and grammar errors; it is probably best to just run all the documentation through a spelling/grammar checker and re-post.
PART II

Assessment Criteria

OWASP Project 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?

None.

2. Having into consideration the OWASP Project Assessment Methodology which criteria, if any, haven’t been fulfilled in terms of Beta Quality status?

None.

3. Having into consideration the OWASP Project Assessment Methodology which criteria, if any, haven’t been fulfilled in terms of Release Quality status?

One-click build, Fortify Software's open source review and FindBugs.

4. Please do use the right hand side column to provide advice and make work suggestions.

I think the documentation could be unified under the Technical Report as the main "Guide", and the current documents could be chapters, e.g., Install, Use, Lessons Learned, Appendix 1 - How To, Appendix 2 - Build Source, etc.