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

OWASP Live CD 2008 Project - Assessment Frame Experience

From OWASP
Revision as of 14:26, 8 June 2009 by Paulo Coimbra (talk | contribs)

Jump to: navigation, search

Click here to return to project's main page

RELEASE ASSESSMENT

Release Leader

Release Leader's Self Evaluation Matt Tesauro

ALPHA RELEASE TOOL CRITERIA/PRE-ASSESSMENT CHECKLIST
1. Is your tool licensed under an open source license?
2. Is the source code and any documentation available in an online project repository? (e.g. Google Code or Sourceforge site)
3. Is there working code?
4. Is there a roadmap for this project release which will take it from Alpha to Stable release?
Field to be kept blank
BETA RELEASE TOOL CRITERIA/PRE-ASSESSMENT CHECKLIST
1. Are the Alpha pre-assessment items complete?
2. Is there an installer or stand-alone executable?
3. Is there user documentation on the OWASP project wiki page?
4. Is there an "About box" or similar help item which lists:

4.1. Project Name?
4.2. Short Description?
4.3. Project Lead and contact information?(e.g. email address)
4.4. Project Contributors (if any)?
4.5. License?
4.6. Project Sponsors (if any)?
4.7. Release status and date assessed as Month-Year e.g. March 2009?
4.8. Link to OWASP Project Page?

5. Is there documentation on how to build the tool from source including obtaining the source from the code repository?
6. Is the tool documentation stored in the same repository as the source code?
Field to be kept blank
BETA RELEASE TOOL CRITERIA/REVIEWER ACTION ITEMS
1. Is an installer for the tool available and easy to use? How close does it reach the goal of a fully automated installer?
2. Is the end user documentation complete, relevant and presented on the OWASP wiki page?
3. Does the tool have an “About box” or similar help item which allows the end user to get an overview of the state of this tool? Is this information readily available and easy to find?
4. Does the documentation on building the source provide the necessary information and detail to allow someone to build the tool? Is there sufficient detail and information for the target user? Is there any domain specific knowledge that is assumed and not provided?
5. Is the tool's documentation available with the source code and would it readily discoverable by a new user of the tool?
Field to be kept blank
STABLE RELEASE TOOL CRITERIA/PRE-ASSESSMENT CHECKLIST
1. Are the Alpha and Beta pre-assessment items complete?
2. Does the tool include documentation built into the tool?
3. Does the tool include build scripts to automate builds?
4. Is there a publicly accessible bug tracking system?
5. Have any existing limitations of the tool been documented?
Field to be kept blank
STABLE RELEASE TOOL CRITERIA/REVIEWER ACTION ITEMS
1.
2.
3.
4.
5.
6.
7.
8.
9.
| style="width:21%; background:#b3b3b3" align="center"|First Reviewer
Dustin Dykes
(applicable for Alpha Quality&further) | style="width:21%; background:#b3b3b3" align="center"|Second Reviewer
Kent Poots
(applicable for Beta Quality&further) | style="width:21%; background:#b3b3b3" align="center"|OWASP Board Member
Sesbastien Deleersnyder
(applicable just for Release Quality) |- | style="width:15%; background:#7B8ABD" align="center"|Alpha Release Tool Criteria
(Pre-Assessment Checklist)
| style="width:21%; background:#C2C2C2" align="center"|To fill in
To View | style="width:21%; background:#C2C2C2" align="center"| | style="width:21%; background:#C2C2C2" align="center"| | style="width:22%; background:#C2C2C2" align="center"| |- | style="width:15%; background:#7B8ABD" align="center"|Final Review | style="width:21%; background:#C2C2C2" align="center"|Objectives & Deliveries reached?
Yes
---------
Which status has been reached?
Release Quality
---------
Self-Evaluation (B) | style="width:21%; background:#C2C2C2" align="center"|Objectives & Deliveries reached?
Yes
---------
Which status has been reached?
Release Quality
---------
First Reviewer (D) | style="width:21%; background:#C2C2C2" align="center"|Objectives & Deliveries reached?
Yes
---------
Which status has been reached?
Release Quality
---------
Second Reviewer (F) | style="width:22%; background:#C2C2C2" align="center"|Objectives & Deliveries reached?
Yes
---------
Which status has been reached?
Release Quality
---------
Board Member's Review (G) |}