Difference between revisions of "Rams"
From Finninday
(→Current questions) |
|||
| Line 1: | Line 1: | ||
===Current questions=== | ===Current questions=== | ||
* how to build a test database | * how to build a test database | ||
| − | |||
| − | |||
| − | |||
| − | |||
* loaded java code into eclipse and it all parses cleanly. | * loaded java code into eclipse and it all parses cleanly. | ||
* still need to get Run and Debug actions to do the right thing | * still need to get Run and Debug actions to do the right thing | ||
| Line 29: | Line 25: | ||
| | | | ||
|} | |} | ||
| − | + | * generate javadocs for rams-web: http://finninday.net/javadoc | |
| + | * analyze program flow based on struts configs | ||
| + | [[Image: struts-map.jpg|400px]] | ||
===Create a presentation=== | ===Create a presentation=== | ||
<table cellpadding="0" cellspacing="0" border="1" style="width: 200px"> | <table cellpadding="0" cellspacing="0" border="1" style="width: 200px"> | ||
Revision as of 17:48, 21 August 2009
Contents
Current questions
- how to build a test database
- loaded java code into eclipse and it all parses cleanly.
- still need to get Run and Debug actions to do the right thing
Review the code
Absorb 24K lines of rams-web java code.
| hours originally budgeted | 6 |
| revised budget | 2 |
| hours worked | 2 |
| hours billed |
- generate javadocs for rams-web: http://finninday.net/javadoc
- analyze program flow based on struts configs
Create a presentation
I assume a PDF would be most useful for this.
| hours originally budgeted | 2 |
| revised budget | |
| hours worked | 0 |
| hours billed |
Preload into eclipse
| hours originally budgeted | 1 |
| revised budget | 5 |
| hours worked | 1 |
| hours billed |
Deliver presentation
| hours originally budgeted | 1 |
| revised budget | |
| hours worked | 0 |
| hours billed |
Report on status
This web page.
Total
| hours originally budgeted | 10 |
| revised budget | |
| hours worked | 3 |
| hours billed |
