Project Information:template OpenSign Server Project 50 Review Second Review E

De OWASP
Saltar a: navegación, buscar

Click here to return to the previous page.

50% REVIEW PROCESS

Project Deliveries & Objectives

OWASP OpenSign Server 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.

Beta Quality for Tools


All Alpha Quality Requirements plus:

  • Have an easy to use installer (Goal: Fully automated installer) (or stand alone executable version)

OK

  • Include user documentation in Project's OWASP Wiki page(s)

OK

  • 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 ACHIEVED

To be placed at OWASP Project page. OK

  • Solves a core application security need.

OK since selected for the OWASP SoC


What has been done by the authors

  • documents:

server concept and architecture : to be completed, Beta quality OK


  • implementation:

Welcome page of the OpenSign Server Web Interface.

code structure

Summary

  • The criteria for Beta quality of the OpenSign Projects have been met by 2008.10.10


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

Beta Quality: 50 %.

Overall project: 50 %

Software development: 30 %

3. Please do use the right hand side column to provide advice and make work suggestions.

Document sent to the authors, 1. week of July [1]