ACE
Working Plan

A very very rough draft framework...

Staff & Organisation

Working Team

Implementers:

• MartinHill (Edin),
• KonaAndrews (Cambridge),

Reporting to:

• TonyLinde

Astronomy and Technical Consultants:

• AnitaRichards
• GuyRixon
• RichardMcMahon
• NicholasWalton

Collaborations

Interfacing with other working groups:

1. Project Management - Peter Quinn, with Markus helping on technical side
2. Science Work Area - Piero B / Nick Walton - short of people.
3. Interoperability - Francoise / CDS - federating archives
4. Infrastructure - Andy Lawrence - AstroGrid overlap

Interfaces / Resources

• Image formats (CDS? ESO?)
• SExtractor
• Result sets suitable for Aladdin - VOTable?
• CDS - interfacing - static tables of catalogues
• ESO - Providing calibrating data, images (pixel data) & catalogues

Louise de Costa - he's been doing some image proccessing already on the South Deep Field, so can provide/help with making parameter templates for SExtractor

Testing

Lots - this is to be used for Real Science. As such it must be reliable or people will be put off right at the beginning.

Plan

Work breakdown

Requirememts & Interfaces agreed

• Image formats
• Output (VOTable XML/FITS)
• Confirm SOAP documents do what we expect.

Design:

• Demo AstroGrid Protocol defined & agreed (done)
• Component interfaces agreed

Document

• Test cases agreed.
• Code documentation up to package level should be JavaDoc .
• TogetherJ used for diagramming.

Implementation:

• Components (as given in AVODemoDesign)
• Configure Apache/Axis

Test, test, test:

• Against hand-run SExtractor
• Assemble test data & confirmed correct results (--> version control).

NB - important that this initial service is reliable, otherwise users loose faith

Milestones

end Sep - System-level setup completed:

• Apache/Axis servers installed & configured at development sites
• Version control available

(Initial) Design & Research completed

Oct/Nov - develop & unit test components.

Dec - Integration & System testing.

Risks

Risk	Effect	Likelihood	Action
Dodgy Requirements			Get in there and make 'em
Interfaces with AVO		Not many of them	Make sure they're clear
Other tasks	Divertion	Likely	Prioritise. Agree & Assign proportion of time.
Geographically separated workforce	Lost time working on out-of-date specs, Lost time on travelling to meetings, lost time on no casual questions	Certain	Loosely couple tasks. Max use of forums/emails/phones. Web version control.

-- MartinHill - 28 Aug 2002