Difference between revisions of "Project Information:template Teachable Static Analysis Workbench - Final Review - First Reviewer - D"

From OWASP
Jump to: navigation, search
Line 28: Line 28:
 
3. Please do use the right hand side column to provide advice and make work suggestions.
 
3. Please do use the right hand side column to provide advice and make work suggestions.
 
  | colspan="2" style="width:75%; background:#cccccc" align="left"|
 
  | colspan="2" style="width:75%; background:#cccccc" align="left"|
# There could be a "How To" document 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.  
+
# 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.  
 
  |-  
 
  |-  
 
  | style="width:25%; background:white" align="center"|'''PART II'''  
 
  | style="width:25%; background:white" align="center"|'''PART II'''  
Line 59: Line 59:
 
4. Please do use the right hand side column to provide advice and make work suggestions.
 
4. Please do use the right hand side column to provide advice and make work suggestions.
 
  | colspan="2" style="width:75%; background:#cccccc" align="left"|
 
  | colspan="2" style="width:75%; background:#cccccc" align="left"|
I think the future versions should
+
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.
 
|}
 
|}

Revision as of 17:23, 3 November 2008

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.
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?

Add a common About Box.

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.