BuildForm

Functional specification

Take this interface and implement it in a new wicket page. The page should have the functionality for the user to input the project search options specified below and in return receive the hours (and costs) registered for that project, for the specified user, during the specified time frame in the specified format and order. The returned report can either be shown on screen, saved to a file (if in .cvs format) or the user can copy-paste the url from the (GET) query staright into a spreadsheet program that will open the report. Search options:

• Project name
• Company
• person
• time frame: from - till
• Declarable
• output format, choose one: full xml dump, csv, xhtml-total-per-project, xhtml-total, xhtml-total-per-week, xhtml-total-per-week-OOo, xhtml-total-per-employee, xhtml-total-per-week-summary.
• cost per hour
• taxes, if any
• sort by column, choose one: Start date, End date, Owner, Description, Projectname, Duration, Declarable
• order: ascending or descending
• locale

Technical specification

For the user to choose a project, the application first has to get a list of projects from the ldap storage. So the list of projects goes from ldap, through the dao and a manager to a wicket dromdownchoice. All the web-components will be wicket. The other fixed choices are: 'Declarable', 'Format', 'Sort by column', 'Order' and 'Locale'. Possibly 'Company', 'Person' (drop down) and 'Time Frame' (datePicker) should be fixed choice too. (Ajaxified, with the person-list depending on the selected project).
'Taxes' and 'Costs' should be Textfields.

Regardless of the decisions on Wicket components, the user constraints are then used to go to webdav and get the requested data by visiting one or more user .ics files. This is now implemented in the TimesheetHttpServlet.

-- IvanaCace - 07 May 2007

Story Layout

Keep it working, just change interface

Methods

Front End

Testing

Other

Hours

Estimates

task	estimated	hrs
kickoff: getting familiar with subject, writing stories, estimates	8
deciding on architecture (bean -> url?)	3
deciding on wicket components	1
getting the project list	2
implementing wicket components	4
backend: manager	3
backend: accessing all ics files in turn	8
checking funtionality	8
...
subTotal	37
slackfactor	1.3
Total	48.1	0

Discussion

Resources

• WDSL for used WebServices? : https://ops.func.nl/services/OpsProject?wsdl

-- RommertDeBruijn - 07 May 2007