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 Application Security Tool Benchmarking Environment and Site Generator Refresh Project 50 Review Second Review E"

From OWASP
Jump to: navigation, search
 
Line 19: Line 19:
  
 
2. At what extent have the project deliveries & objectives been accomplished?  Having in consideration [[OWASP Summer of Code 2008 Applications - Need Futher Clarifications#P003/P013 - OWASP Application Security Tool Benchmarking Environment and Site Generator refresh.=|'''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 - Need Futher Clarifications#P003/P013 - OWASP Application Security Tool Benchmarking Environment and Site Generator refresh.=|'''the assumed ones''']], please quantify in terms of percentage.
−
  | colspan="2" style="width:75%; background:#cccccc" align="left"|  I would say the project is about 35-40% of the way done.  The UI isn't fully complete and the UI should be the smaller of the project as the generation of the site and the server-side code should take a decent chunk of the project.   
+
  | colspan="2" style="width:75%; background:#cccccc" align="left"|  I would say the project is about 50% of the way done.  The UI is pretty much complete.   
 
  |-  
 
  |-  
 
  |-
 
  |-
Line 32: Line 32:
 
* If a large number of directories and or files are specified the application locks up (or at least appears to).  I put 26000+ for each field and the application went bye-bye.  We should set a maximum range (I noticed there was a minimum range which was good).
 
* If a large number of directories and or files are specified the application locks up (or at least appears to).  I put 26000+ for each field and the application went bye-bye.  We should set a maximum range (I noticed there was a minimum range which was good).
 
* There is no clear way to modify the access control
 
* There is no clear way to modify the access control
 +
*
 +
* As of 3/15/2009 these issues have all been fixed.
 
|}
 
|}

Latest revision as of 04:22, 16 March 2009

Click here to return to the previous page.

50% REVIEW PROCESS

Project Deliveries & Objectives

OWASP Application Security Tool Benchmarking Environment and Site Generator refresh 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 UI has been created and is usable minus a few bugs that were found and sent along to Dmitry. The UI is a lot easier to work with then the previous version and should work well once the back-end code is written.

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

I would say the project is about 50% of the way done. The UI is pretty much complete.

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

Here are the suggestions I passed on to Dmitry:
  • During the install there is no option to add a shortcut to the desktop
  • From the install the name of the program is Sitegen yet when you run the program the title is SiteGenerator 2.0 we should keep these values similar
  • When you expand the window the inner frames do not expand with it (good job on handling the case of making the window smaller though, that can't be done leading to no mashed up UI).
  • You can add invalid directory path and the program does not correct you which leads to invalid directory paths when you hit generate
  • You can add in a blank role in the "Access Control" tab when you are creating a new site.
  • If a large number of directories and or files are specified the application locks up (or at least appears to). I put 26000+ for each field and the application went bye-bye. We should set a maximum range (I noticed there was a minimum range which was good).
  • There is no clear way to modify the access control
  • As of 3/15/2009 these issues have all been fixed.

Retrieved from "https://wiki.owasp.org/index.php?title=Project_Information:template_Application_Security_Tool_Benchmarking_Environment_and_Site_Generator_Refresh_Project_50_Review_Second_Review_E&oldid=56758"