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

Difference between revisions of "Project Information:template SKAVENGER Final Review Self Evaluation B"

From OWASP
Jump to: navigation, search
 
(15 intermediate revisions by the same user not shown)
Line 1: Line 1:
 +
[[Project Information:template SKAVENGER|Clik here to return to the previous page]].
 +
 
{| style="width:100%" border="0" align="center"
 
{| style="width:100%" border="0" align="center"
  ! colspan="4" align="center" style="background:#white; color:black"|
+
  ! 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#Skavenger|Skavenger 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:10%; background:#C2C2C2" align="center"| '''Class'''  
+
  | style="width:25%; background:#7B8ABD" align="center"|
  | style="width:60%; background:#C2C2C2" align="center"| '''Criteria'''   
+
1. At what extent have the project deliveries & objectives been accomplished?  Having in consideration [[OWASP Summer of Code 2008 Applications - Need Futher Clarifications#Skavenger|'''the assumed ones''']], please exemplify writing down those of them that haven't been realised.
  | style="width:20%; background:#C2C2C2" align="center"| '''Review Process'''   
+
  | colspan="2" style="width:75%; background:#cccccc" align="left"|
  | style="width:10%; background:#C2C2C2" align="center"| '''Example'''
+
|-
 +
| 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#Skavenger|'''the assumed ones''']], please quantify in terms of percentage.
 +
  | colspan="2" style="width:75%; background:#cccccc" align="left"|
 +
|-
 +
| style="width:25%; background:#7B8ABD" align="center"|
 +
3. What kind of help is required either from the Reviewers or from the OWASP Community?
 +
  | colspan="2" style="width:75%; background:#cccccc" align="left"|
 +
|-
 +
| 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:10%; background:#f2984c" align="center"|'''[[:Category:OWASP Project#Release_Quality_Projects|Release Quality OWASP Tools]]'''
+
  | style="width:25%; background:#4058A0" align="center"|<font color="white">'''QUESTIONS'''  
  | style="width:60%; background:#e6e6e6" align="left"|
+
  | colspan="2" style="width:75%; background:#4058A0" align="left"|<font color="white">'''ANSWERS'''   
All Beta Quality Requirements plus:
 
* Be reasonably easy to use
 
* Include online documention built into tool (based on required user documentation)
 
* Include build scripts that facilitate building the application from source (Goal: One-click build)
 
* Publicly accessible bug tracking system established, ideally at the same place as the source code repository (e.g., at Google code, or Sourceforge)
 
* Be run through [http://opensource.fortifysoftware.com/welcome.html Fortify Software's open source review] (if appropriate) and [http://findbugs.sourceforge.net/ FindBugs].
 
**WebGoat would not be appropriate for example since it would light up like a Christmas tree :-)
 
* C/C++ apps (if we have any) should consider being run through [http://scan.coverity.com/ Coverity's open source review]. Coverity also accepts submissions for open source Java applications.
 
* When approved to be Release Quality: Update the link to it on: the [[:Category:OWASP_Project | OWASP Project]] page and update its project quality tag on its project page to be Release Quality.
 
'''Recommendations:'''
 
* Conference style Powerpoint presentation that describes the use and status of the tool. (This could be used by others to discuss the tool at OWASP Chapter meetings, serve as easy to review offline documentation, etc.)
 
* UAT pass on functionality of the tool
 
* Developer documents any limitations
 
| style="width:20%; background:#e6e6e6" align="left"|
 
* '''Requirement''': 2 Reviewers + 1 OWASP Board Member.
 
** If possible, the project's lead should suggest two Project Reviewers. One of them should be an OWASP Project Leader.
 
** If the project's lead can't find the Project Reviewers, the OWASP Board will identify them. The same will happen whenever the reviewers suggested do not have the required approval.
 
| style="width:10%; background:#e6e6e6" align="center"|[[OWASP WebGoat Project|OWASP WebGoat Project]]
 
 
  |-
 
  |-
  | style="width:10%; background:#ffcc66" align="center"|'''[[:Category:OWASP Project#Beta_Status_Projects|Beta Quality OWASP Tools]]''' 
+
  | style="width:25%; background:#7B8ABD" align="center"|  
| style="width:60%; background:#e6e6e6" align="left"|
+
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?
All Alpha Quality Requirements plus:
+
  | colspan="2" style="width:75%; background:#cccccc" align="left"|
* Have an easy to use installer (Goal: Fully automated installer) (or stand alone executable version)
 
* Include user documentation in Project's OWASP Wiki page(s)
 
* Add a common About Box or help menu in the tool itself
 
**(which lists name of tool, author, e-mail address of author, current version number and/or release date)
 
* Include documentation on how to build it from code, starting with getting it directly from the code repository. (Ideally, this would include easy to use build scripts, which is required for Release Quality)
 
* This documentation must stored be in the same repository as the code.
 
* When approved to be Beta Quality: Update the link to it on: the [[:Category:OWASP_Project | OWASP Project]] page and update its project quality tag on its project page to be Beta.
 
| style="width:20%; background:#e6e6e6" align="center"|
 
* '''Requirement''': 2 Reviewers.
 
** If possible, the project's lead should suggest two Project Reviewers.  One of them should be an OWASP Project Leader.
 
** If the project's lead can't find the Project Reviewers, the OWASP Board will identify them. The same will happen whenever the reviewers suggested do not have the required approval.
 
  | style="width:10%; background:#e6e6e6" align="left"|[[:Category:OWASP AntiSamy Project|OWASP AntiSamy Project]]
 
 
  |-
 
  |-
  | style="width:10%; background:#ffff66" align="center"|'''[[:Category:OWASP Project#Alpha_Status_Projects|Alpha Quality OWASP Tools]]'''  
+
  | style="width:25%; background:#7B8ABD" align="center"|  
  | style="width:60%; background:#e6e6e6" align="left"|(D)
+
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?
| style="width:20%; background:#e6e6e6" align="left"|(E)
+
  | colspan="2" style="width:75%; background:#cccccc" align="left"|
| style="width:10%; background:#e6e6e6" align="center"|(F)
 
 
  |-  
 
  |-  
 +
| 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"|
 +
|- 
 +
| style="width:25%; background:#7B8ABD" align="center"|
 +
4. What kind of help is required either from the Reviewers or from the OWASP Community?
 +
| colspan="2" style="width:75%; background:#cccccc" align="left"|
 
|}
 
|}

Latest revision as of 21:00, 12 May 2008

Clik here to return to the previous page.

FINAL REVIEW
PART I

Project Deliveries & Objectives

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

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

3. What kind of help is required either from the Reviewers or from the OWASP Community?

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?

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

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

4. What kind of help is required either from the Reviewers or from the OWASP Community?