1. LCG Applications Area Milestones
Torre Wenaus, BNL/CERN
LCG Applications Area Manager
LHCC Meeting
November 25, 2002

2. Initiation of AA Work via SC2-RTAGS
Applications Area prerequisite and priority for initiating work:
RTAGs successfully addressing common projects
And SC2 turning over project mandates to the PEB-AA
Initial round of project mandates emerged from RTAGs in April
Software process
Persistency framework
Math libraries
Second round emerging now
Architecture blueprint (guidance for all projects; work for several)
Event generators
Detector description
Simulation
Translation into AA projects…

3. Apps Area Project Status
Apr: Software process and infrastructure (SPI) – Alberto Aimar
Apr: Persistency framework (POOL) – Dirk Duellmann
Jun: Math libraries – Fred James
Oct: Core libraries and services (CLS) – Pere Mato
Nov: Physicist Interface (PI) – Vincenzo Innocente
Event generators (Project activity pending)
Detector description (RTAG complete; SC2 deliberating)
Simulation (RTAG complete; SC2 deliberating)
Status relative to preliminary plans at March Launch Week…

4. Top Priorities from March – A Current Look
Initiate: First half 2002
Establish process and infrastructure project (Active)
Address core areas essential to building a coherent architecture, and develop the architecture
Object dictionary (Active)
Persistency (Active)
Interactive frameworks (Launched), analysis tools (Partially launched)
Address priority common project opportunities
Driven opportunistically by a combination of experiment need, appropriateness to common project, and ‘the right moment’ (existing but not entrenched solutions in some experiments)
Detector description and geometry model (RTAG complete; SC2 deliberating)
Driven by need and available manpower
Simulation tools (RTAG complete; SC2 deliberating)

5. Near term priorities from March
Initiate: Second half 2002
Build outward from the core top tier components
Conditions database (Pending, but common tool exists)
Framework services, class libraries (Launched)
Address common project areas of less immediate priority
Math libraries (Active)
Physics packages (Mandate received by PEB-AA)
Extend and elaborate the support infrastructure
Software testing and distribution (Active)
Deliver: fall/late 2002: basic working persistency framework (On schedule)

6. Medium term priorities from March
Initiate: First half 2003
The core components have been addressed, architecture and component breakdown laid out, work begun. Grid products have had another year to develop and mature. Now explicitly address physics applications integration into the grid applications layer.
Distributed production systems. End-to-end grid application/framework for production.
Distributed analysis interfaces. Grid-aware analysis environment and grid-enabled tools.
Blueprint RTAG recommends prompt attention (RTAG)
Under SC2 consideration
Some common software components are now available. Build on them.
Lightweight persistency, based on persistency framework
Release LCG benchmarking suite

7. Candidate RTAG timeline from March
Blue: RTAG/activity launched or (light blue) imminent

8. Apps area planning materials on web
Planning page linked from applications area page: in development
Applications area plan spreadsheet: overall project plan
High level schedule, personnel requirements
Applications area plan document: overall project plan
Incomplete draft
Personnel spreadsheet
Currently available/foreseen apps area personnel, activities
Planning materials – PBS, milestones, personnel resources

9. Apps Area Milestones
Level 2 milestones developed for existing and anticipated projects
Except for small projects, not done yet (math libs, generators)
At least until mid 2003
Milestones in the existing projects have been either defined by or OK’d by the project managers
Project data maintained in XProject (in-house tool for software project planning)
And exported to MS Project for integration with other areas, Gantt display, etc.

10. Apps Area Milestones
State of the AA milestones reflects the state of the AA projects
L1 milestones are only in project areas which were defined or foreseeable early
Persistency and grid interfaces
Nonetheless, we probably have the right set of L1 milestones, unless our mandate in simulation warrants L1 milestone(s)
L2 milestones are detailed only in the one software development project that has been active for >1 month and has developed a work plan: persistency
Other development projects were initiated in Oct, Nov or are still pending
Will be filling out the L2 milestones and delivering work plans to the PEB+SC2 over the next several months
Detailed milestone descriptions are shown on the web, but not on these slides

11. L1 Milestones (1)

12. L1 Milestones (2)

13. MS Project – Gantt Schedule for POOL

14. Pool Release Schedule End September – V0.1 (Released on schedule)
Core components for navigation
“End October” (Nov 15) – V0.2 (Released on schedule)
First collection implementation
“End November” (Dec 15) – V0.3 (First public release)
EDG/Globus FileCatalog integrated
Persistency for general non-ROOT C++ classes
Event meta data annotation and query
End Feb – Interface-complete release
For experiment software integration
Mid Apr – Pre-production release
Feature-complete with respect to June; bug fix release
June 2003 – Public Production Release (L1 milestone)

15. POOL L1, L2 Milestones

16. Software Process and Infrastructure Milestones

17. Core Libraries and Services Milestones

18. Physicist Interface Milestones

19. Concluding Remarks
Applications area schedule in rapid evolution as new projects come into scope
Level 1 milestones, set last spring, still seem appropriate and attainable
Their definitions were tightened up as much as possible given present knowledge
And tightening them further as new (e.g. RTAG) info comes in has been built into the schedule
Level 2 milestones establish the detailed program of work and provide project tracking
Granularity ~1/month for the major projects, for ~1yr out; less frequent beyond 1yr
Will be fleshed out for the new projects over next ~2 months