Title: Report on 1st QAG meeting Gabriel Zaquine JRA2 manager CSSI
1Report on 1st QAG meeting Gabriel ZaquineJRA2
managerCSSI
Cork Conference, 19-22 April 2004
www.eu-egee.org
EGEE is a project funded by the European Union
under contract IST-2003-508833
2Contents
- JRA2 Quality objectives
- Quality Management (QAM) people mandate
- Quality Group (QAG) people mandate
- Steps to be done between now and M3
- Main higth level metrics (to be reported in the
Quarterly report)
3JRA2 Quality objectives
- Ensure that processes, products and operation
services conform to EGEE requirements and to the
required level of services. - QA will be present right from the start in all
activities with commitments for all members. - QA is an iterative process with continuous
measurements and refinements in order to improve
the global quality system. - Measurements and metrics are needed to verify and
prove that we deliver the quality that we must
reach
4QA model and QA activities
Management
EU
Coordination Report (Project Collaborative
Tool) JRA2/QAM
Metrics / SLA
Production
Management
Verification QAG
Refinement all
Middleware
Application Training Dissemination
Definition (standards, procedures, metrics, tools
) Activities
5JRA2 QAM
- The Quality Assurance Management team has a
dedicated interface for each activity (3FTE) - Gabriel Zaquine - CSSI QA head NA1 SA1,2
interface - Alberto Aimar - CERN Deputy JRA1 interface
- Genevieve Romier CNRS (half-time) JRA3 JRA4
interface - Marcel Soberman CNRS (half-time) NA2, NA3, NA4
interface - Elodie Sanchez - CNRS Metric reports and
associated tools (will start in June) - Mandate Coordination of the overall Quality
Activities
6QAG
- The Quality Assurance Group has dedicated
representative(s) (QAR) from each activity - NA1/NA5 Bob Jones - CERN
- NA3 Dave Berry - NESC
- NA4 Vincent Breton - CNRS
- SA1 Alistair Mills - CERN
- SA2 Jean-Paul Gautier - CNRS
- JRA1 Alberto Di Meglio - CERN, Linda Cornwall -
RAL - JRA3 Martyin Steenbakkers - NIKHEF
- JRA4 Sophie Nicoud - CNRS
- Mandate
- Make sure QA materials (procedures, metrics,
tools, ) are provided by each activity - Make sure QA measures as defined are applied
inside their activity - Promote QA materials and production quality
attitude inside their activity - Monthly meeting (conf. Call) - First Friday of
each month, 1000 07/05/04, 04/06/04
7Risk analysis
- Procedures Metrics are defined too late
- Tools for metrics not ready in time to give quick
feedback - Difficult to achieve production quality
attitude - Failure to deliver quality software acceptable to
LCG or Applications () - Risk of having too much divergence on the way
people work, lots of disadvantages - Failure to comply to project quality guidelines
required for higher quality software () - This WILL have implications on people habits
- () taken from JRA1 risk analysis because they
are really crucial for all
8Steps to be done between now and M3
- M1 Identify and define timeline for (QARs)
- Main procedures
- Main tools
- Metrics
- Verification means and checklists
- M1 Timesheet reporting procedure - Gabriel /
NA1 - M1-M3 Follow PPT customisation for EGEE. See
EGEE PPT requirements - Gabriel - M1 Risk Management procedure (see LCG risk
procedure) - QAM - M3 Preparation of the deliverable DJRA2.1
(Quality Plan) - M1 Review of the existing QA materials - QARs
- M1 Documentation plan EDMS structure - QARs
- M1-M2 Implement on the UREC/CNRS CPU the
CrossGrid monitoring tools after LCG agreement -
Geneviève -
9Main indicators to be reported in the quarterly
report .
- EGEE should be evaluated though the angles of
- Services provided utilisation
- Products provided
- Project progress, effort, cost
- International recognition
- We suggest a list of high-level metrics that
should be reported in the quarterly report. Those
metrics should be refined and completed by each
activity.
10Main indicators to be reported in the quarterly
report .NA1
- NA1 Project management
- Track if project is on schedule and on budget
(progress, effort, cost). PPT (Cern Tool based on
Earned Value) will be used to re-estimate the
schedule and budget for the remainder of the
project. - On-time delivery of deliverables and quarterly
reports - Acceptance of deliverables by the EU Commission
11Main indicators to be reported in the quarterly
report SA1
- SA1 Operations
- Provider Engagement - Resources available/used
- Availability
- Job Success and Job throughput
- Grid Job overhead Time while job is running
against total time between submission and
completion. - Data Transfer
- User Support
12Main indicators to be reported in the quarterly
report NA4
- NA4 Application Identification and Support
- Utilisation Number of users, disciplines,
countries, VO, Applications, Jobs, ) - Requirements completeness
-
13Main indicators to be reported in the quarterly
report JRA
- Middleware JRA1, JRA3 (), JRA4
- Defect trends
- Change request - Requirement stability (Critical
defects, Normal defects, Improvement requests,
New features) - Size stability
- Tests progress trends
- () Particular indicators should be defined for
security
14Main indicators to be reported in the quarterly
report NA3
- NA3 User Training and Induction ()
- Application Developer Induction
- EGEE Operations Induction
- EGEE Expert Induction.
- EGEE software Infrastructure Induction
- Number of training versus target value for each
category - () Should be mainly evaluated on the number of
persons trained satisfied
15Main indicators to be reported in the quarterly
report NA2
- NA2 Dissemination and Outreach
- EGEE conferences Numbers of attendees by
categories (EGEE, Academic, Industry, ) versus
target attendees - Number of publications published versus target
publication to publish - Number of EGEE talks (invited) versus target
intended talks - Website audience
16Main indicators to be reported in the quarterly
report NA5
- NA5 International cooperation
- International Recognition The EGEE team will be
one of an international community of Grid
infrastructure developers and Grid service
providers. It is essential that EGEEs standards
are considered appropriate or exemplary by this
community. - Formal Endorsement EGEE should have formal
endorsement by members of the above community,
which includes software and service interchange
arrangements and mutual acceptance of each
others certification procedures.
17(No Transcript)