Blank Beta Release Tool Example

From OWASP
Revision as of 00:18, 21 June 2009 by Mtesauro (Talk | contribs)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

Click here to return to the tool assessment criteria

Stable Release Review of [Project Name] [Release Name and Version]

Project Leader for this Release

[Project Lead]'s Pre-Assessment Checklist:

Alpha level

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?

Beta Level

5. Are the Alpha pre-assessment items complete?

6. Is there an installer or stand-alone executable?

7. Is there user documentation on the OWASP project wiki page?

8. Is there an "About box" or similar help item which lists the following?

  • Project Name
  • Short Description
  • Project Lead and contact information (e.g. email address)
  • Project Contributors (if any)
  • License
  • Project Sponsors (if any)
  • Release status and date assessed as Month-Year (e.g. March 2009)
  • Link to OWASP Project Page

9. Is there documentation on how to build the tool from source including obtaining the source from the code repository?

10. Is the tool documentation stored in the same repository as the source code?



First Reviewer

[First Reviewer]'s Review:

Beta Release Level Questions

1. Is an installer for the tool available and easy to use? How close does it reach the goal of a fully automated installer?


Delete this text and place your answer here.


2. Is the end user documentation complete, relevant and presented on the OWASP wiki page?


Delete this text and place your answer here.


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?


Delete this text and place your answer here.


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?


Delete this text and place your answer here.


5. Is the tool's documentation available with the source code and would it readily discoverable by a new user of the tool?


Delete this text and place your answer here.