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 "Category:OWASP Project Release Quality Projects Requirements"
From OWASP
| Line 10: | Line 10: | ||
* Include user documentation | * Include user documentation | ||
* Include documentation on how to build it from code | * Include documentation on how to build it from code | ||
| + | * Include UAT pass on functionality requirements of the tool | ||
| + | * Ask the developers to document any limitations | ||
| + | * Question Human Computer Interaction (HCI) and the user interface | ||
| + | * Add a common About Box (or help menu), regardless of language | ||
| + | * Overview of scanning the codebase findings (say findbugs) | ||
Revision as of 11:21, 11 January 2008
Project Release Quality Projects Requirements
For a tool to be release quality it would need to:
(Work in progress - add your contribution)
- Be reasonably useful
- Be reasonably easy to use
- Have an easy to use installer
- Have its code in Googlecode, or Sourceforge
- Include user documentation
- Include documentation on how to build it from code
- Include UAT pass on functionality requirements of the tool
- Ask the developers to document any limitations
- Question Human Computer Interaction (HCI) and the user interface
- Add a common About Box (or help menu), regardless of language
- Overview of scanning the codebase findings (say findbugs)
This category currently contains no pages or media.
