Iteration 4 Home Page

All Iteration 4 related Wiki pages should be referenced from here. Please add any that are missing!

Consolidation

Once again we find ourselves in need of consolidating the previous iteration before commencing the next. Please take note of the following (lifted almost verbatim from the Iteration 3 page):

• Do JUnit (and other) tests exist for all modules (classes and/or packages as appropriate) and do the modules pass the tests?
• Will your code build and report correctly under Maven? We must start daily build and integration if we are to avoid quality and usability problems late in each iteration.
• Have you avoided all hard-coded references and put properties where they should be; namely in property files? If not, refactor!
• Does all code meet the coding standards as defined in the Rogue Wave book? Do you have the Rogue Wave book ("The Elements of Java Style")? If not email ktn@starNOSPAM.le.ac.uk today. The cruital test here is: are you happy for other developers to undertake a critical review of your code?
• All components must be buildable with Maven and deployed using ANT (or by the deployment of JAR and/or WAR files if appropriate). All modules must have installation notes (INSTALL) and release notes (README).
• If you believe the development processes need updating or changing, please discuss on the forum and I'll amend as necessary.

Timetable

Notes

1. Due to the Christmas holidays, I have brought forward the code freeze and Alpha testing dates. Please make allowances for this in your plans
2. Designs and plans are scheduled for 20-Oct to allow for ADASS (13-17 Oct)

Processes

All work groups will follow all processes. If something doesn't work, we'll fix it, not bypass it. The WGL meeting agreed the following:

Continuous Integration

• All developers check in at least daily
• All checked in code must build
• 100% test coverage (goal)
• Milestones set to be achievable in roughly 1 week
• Completed milestones and major bug fixes to be tagged weekly (goal)
• WGL to update build tracking properties file with latest integrateable build tag
• Catherine to deploy latest integrated BL weekly
• Errors, bugs and omissions to be reported

Continuous Integration, definitions

• Daily integration = uploaded code builds against all dependent libraries (using Maven)
• We expect weekly deployments to have bugs, but we also expect the bug count to be zero, 2 weeks before code freeze

Bean based web service interface

• All WG to adopt SoapyBeans approach (except...)
• Interface definitions published through Catherine
• Interface need not be mirror of stub
• All WG to define an Interface and Mock Delegate for others groups to build against
• Interface and Mock Delegate produced by Itn+2
• WG to produce DelegateFactory by Itn+2 Changes to interfaces to be planned with Catherine who will communicate changes and planned dates to other WGs
• WG to produce Legacy and HTTP delegates by Itn+4

Infrastructure

• Logging: we will use commons logging in combination with log4j by default (use other logging mechanisms only where required)
• Properties: Martin is working on a generic solution to be presented by Wiki/Forum by Itn4+2

Planning

• WGL to arrange group planning meeting (see Timetable above)
• WGLs to meet monthly (rolling venue)
• Reporting
  • Weekly group report
  • Activities
  • Plans
  • Progress against plan
• Weekly deployment report from Catherine
• Designs will be maintained at domain and class level throughout iteration

Notes

1. Ensure plans are realistic
2. Review plans at the same time as code reviews
3. Negotiate changes to plans early
4. We will de-scope rather than miss the delivery date

Work Groups

GUI

• Common look and feel, liberal use of stylesheets et al
• GUI group members to work closely with one other group. This provides the continuity of interface by belonging to the GUI group, but provides the focus of only working one UI.

Applications Integration

• Review chosen application set and relate to Itn4 Use Cases
• Develop methods for building applications into Portal and Workflow
• Work with Data Federation research group to add data federation tool

Registry

• Implement new IVOA registry schema
• Harvesting capabilities.

Dataset Access

• Add new data sets (WFCAM, Vizier, 2MASS)
• Create FITS accessor
• Continue work on PAL

Definitions

CVS Tags

CVS tags will take the form:

where the date matches a completed milestone or a major bug fix release.

Milestone Status

The milestones defined on each Work Group page will be updated with the Status and Due Date for each milestone. The status column can contain:

Unresolved

-- KeithNoddle - 01 Oct 2003