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

[[Project Information:template Teachable Static Analysis Workbench|Clik here to return to the previous page]].

{| style="width:100%" border="0" align="center"
 ! colspan="3" align="center" style="background:#4058A0; color:white"|<font color="white">'''FINAL REVIEW''' 
 |- 
 | style="width:25%; background:white" align="center"|'''PART I''' 
 | colspan="2" style="width:75%; background:white" align="left"|
 |- 
 | style="width:25%; background:#7B8ABD" align="center"| 
Project Deliveries & Objectives  
 | colspan="2" style="width:75%; background:#cccccc" align="left"|
[[OWASP Summer of Code 2008 Applications - Need Futher Clarifications#Teachable Static Analysis Workbench|OWASP Teachable Static Analysis Workbench Project's Deliveries & Objectives]]
 |-
 | style="width:25%; background:#4058A0" align="center"|<font color="white">'''QUESTIONS''' 
 | colspan="2" style="width:75%; background:#4058A0" align="left"|<font color="white">'''ANSWERS'''  
 |-
 | style="width:25%; background:#7B8ABD" align="center"| 
1. At what extent have the project deliveries & objectives been accomplished?  Having in consideration [[OWASP Summer of Code 2008 Applications - Need Futher Clarifications#Teachable Static Analysis Workbench|'''the assumed ones''']], please exemplify writing down those of them that haven't been realised.
 | colspan="2" style="width:75%; background:#cccccc" align="left"|
Input Validation functionality works as stated.
 |-
 | style="width:25%; background:#7B8ABD" align="center"| 
2. At what extent have the project deliveries & objectives been accomplished?  Having in consideration [[OWASP Summer of Code 2008 Applications - Need Futher Clarifications#Teachable Static Analysis Workbench|'''the assumed ones''']], please quantify in terms of percentage.
 | colspan="2" style="width:75%; background:#cccccc" align="left"|
The promised deliverables and functionality have been completed 100%.
 |- 
 | style="width:25%; background:#7B8ABD" align="center"|
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"|
# 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.
# 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. 
 |- 
 | style="width:25%; background:white" align="center"|'''PART II''' 
 | colspan="2" style="width:75%; background:white" align="left"|
 |- 
 | style="width:25%; background:#7B8ABD" align="center"| 
Assessment Criteria
 | colspan="2" style="width:75%; background:#cccccc" align="left"|
[[:Category:OWASP Project Assessment|OWASP Project Assessment Criteria]]
 |-
 | style="width:25%; background:#4058A0" align="center"|<font color="white">'''QUESTIONS''' 
 | colspan="2" style="width:75%; background:#4058A0" align="left"|<font color="white">'''ANSWERS'''  
 |-
 | style="width:25%; background:#7B8ABD" align="center"| 
1. Having into consideration the [[:Category:OWASP Project Assessment|OWASP Project Assessment Methodology]] which criteria, if any, haven’t been fulfilled in terms of '''Alpha Quality''' status?
 | colspan="2" style="width:75%; background:#cccccc" align="left"|
None.
 |-
 | style="width:25%; background:#7B8ABD" align="center"| 
2. Having into consideration the [[:Category:OWASP Project Assessment|OWASP Project Assessment Methodology]] which criteria, if any, haven’t been fulfilled in terms of '''Beta Quality''' status?
 | colspan="2" style="width:75%; background:#cccccc" align="left"|
Add a common About Box.
 |- 
 | style="width:25%; background:#7B8ABD" align="center"| 
3. Having into consideration the [[:Category:OWASP Project Assessment|OWASP Project Assessment Methodology]] which criteria, if any, haven’t been fulfilled in terms of '''Release Quality''' status?
 | colspan="2" style="width:75%; background:#cccccc" align="left"|
One-click build, Fortify Software's open source review and FindBugs.
 |-  
 | style="width:25%; background:#7B8ABD" align="center"|
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"|
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.
|}