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 Classic ASP Security Project - 50 Review - First Reviewer - C"

From OWASP
Jump to: navigation, search
(New page: Click here to return to the previous page. {| style="width:100%" border="0" align="center" ! colspan="3" align="center" styl...)
 
Line 15: Line 15:
 
1. At what extent have the project deliveries & objectives been accomplished?  Having in consideration [[OWASP Summer of Code 2008 Applications#OWASP Classic ASP Security Project|'''the assumed ones''']], please exemplify writing down those of them that haven't been realised.
 
1. At what extent have the project deliveries & objectives been accomplished?  Having in consideration [[OWASP Summer of Code 2008 Applications#OWASP Classic ASP Security Project|'''the assumed ones''']], please exemplify writing down those of them that haven't been realised.
 
  | colspan="2" style="width:75%; background:#cccccc" align="left"|
 
  | colspan="2" style="width:75%; background:#cccccc" align="left"|
 +
The project has five main tasks, being them:
 +
<br>- Creation of a Common Object Repository (time consuming task. The author segregated this work package in smaller pieces and offered a detailed overview of the achievements. %50+ of the work has been donde (not uploaded or linked at this time as would be convenient to upload once is finished. Upon requirement and author agreement documents could be disclosed)
 +
<br>- Create Documentation <snip>  providing additional technology-specific checks. (done)
 +
<br>- Addition of expression for Code Review Tool to support Classic ASP applications. (done)
 +
<br>- Implementation of Version 1 of Stinger for ASP either by using an installable COM library or ISAPI. (to be done)
 +
<br>- This same module will compliment the OWASP Validation Documentation Project. (to be done)
 
  |-  
 
  |-  
 
  | style="width:25%; background:#7B8ABD" align="center"|  
 
  | style="width:25%; background:#7B8ABD" align="center"|  
Line 20: Line 26:
 
2. At what extent have the project deliveries & objectives been accomplished?  Having in consideration [[OWASP Summer of Code 2008 Applications#OWASP Classic ASP Security Project|'''the assumed ones''']], please quantify in terms of percentage.
 
2. At what extent have the project deliveries & objectives been accomplished?  Having in consideration [[OWASP Summer of Code 2008 Applications#OWASP Classic ASP Security Project|'''the assumed ones''']], please quantify in terms of percentage.
 
  | colspan="2" style="width:75%; background:#cccccc" align="left"|
 
  | colspan="2" style="width:75%; background:#cccccc" align="left"|
 +
As stated before, we have five main work packages. Two of them already delivered in June, the first and main completed up to %53. We have missing two full work packages at this stage:
 +
<br>- Implementation of Version 1 of Stinger for ASP either by using an installable COM library or ISAPI. (to be done)
 +
<br>- This same module will compliment the OWASP Validation Documentation Project. (to be done)
 
  |-  
 
  |-  
 
  |-
 
  |-
Line 25: Line 34:
 
3. Please do use the right hand side column to provide advice and make work suggestions.
 
3. Please do use the right hand side column to provide advice and make work suggestions.
 
  | colspan="2" style="width:75%; background:#cccccc" align="left"|
 
  | colspan="2" style="width:75%; background:#cccccc" align="left"|
 +
Project indicators such communication, task assessment, timing and effort has been managed very well. The project author delivered full documentation at all time. We have confidence things will continue the same way. Smooth.
 
|}
 
|}

Revision as of 07:00, 30 June 2008

Click here to return to the previous page.

50% REVIEW PROCESS

Project Deliveries & Objectives

OWASP Classic ASP Security 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.

The project has five main tasks, being them:
- Creation of a Common Object Repository (time consuming task. The author segregated this work package in smaller pieces and offered a detailed overview of the achievements. %50+ of the work has been donde (not uploaded or linked at this time as would be convenient to upload once is finished. Upon requirement and author agreement documents could be disclosed)
- Create Documentation <snip> providing additional technology-specific checks. (done)
- Addition of expression for Code Review Tool to support Classic ASP applications. (done)
- Implementation of Version 1 of Stinger for ASP either by using an installable COM library or ISAPI. (to be done)
- This same module will compliment the OWASP Validation Documentation Project. (to be done)

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

As stated before, we have five main work packages. Two of them already delivered in June, the first and main completed up to %53. We have missing two full work packages at this stage:
- Implementation of Version 1 of Stinger for ASP either by using an installable COM library or ISAPI. (to be done)
- This same module will compliment the OWASP Validation Documentation Project. (to be done)

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

Project indicators such communication, task assessment, timing and effort has been managed very well. The project author delivered full documentation at all time. We have confidence things will continue the same way. Smooth.

Retrieved from "https://wiki.owasp.org/index.php?title=Project_Information:template_Classic_ASP_Security_Project_-_50_Review_-_First_Reviewer_-_C&oldid=32821"