JRA2: Quality Assurance Overview EGEE is proposed as a project funded by the European Union under contract IST.2003-508833 [email protected] JRA

JRA2: Quality AssuranceOverview

EGEE is proposed as a project funded by theEuropean Union under contract IST.2003-508833

[email protected]

JRA workshop -28/10/03

JRA2 Quality Assurance - 2

Summary

• QA objectives

• QA organisation

• JRA2 major milestones and deliverables

• JRA2 structure

• JRA2 execution plan (draft)


Quality objectives

• Quality assurance in EGEE is the planned and systematic set of activities that ensure that processes, products and operation services conform to EGEE requirements and to the required level of services.

• Quality assurance will be present right from the start in all activities within the EGEE project and integrated in each project activity.

• Quality Assurance will be a very practical activity and an iterative process with the continuous improvement of the standards or procedures in order to improve the global quality system.


QA organisation

Quality Assurance Management Team

(QAM) -JRA2(3 FTE)

Project Executive Board

SA1 QARs• SA1 Manager•CIC Rep.•ROC Rep.

NA QARs•NA2/NA3 Rep. •NA4 Rep.

JRA1 QARs•JRA1 Manager•Rep. from each cluster•Rep. fromintegration/tests•Rep. from Tools

SA2/JRA4 Rep. JRA3 Rep.

Quality Group (QAG) – Monthly Meeting

QA head

Coordination

Dedicated Testing / Validation teamsJRA1, SA1, NA4

Methodology and Tools support team

JRA1

Related Activities• Define in collaboration with the relevant activities the overall standards, procedures and metrics• Make sure they are applied• Evaluate metrics• Report and propose progress factors

The main role of QA representatives is to ensure that quality measures as agreed are applied inside their activity group.

The execution of the verification and testing activities is the responsibility of the individual activities.


JRA2 Major milestones & deliverables

Month Deliverable Item

4 DJRA2.1 Quality Plan for EGEE

5 MJRA1.1 Internal QA website deployed

12 DJRA2.2 1st Report on EGEE Quality Status, including software and Grid operations and plans for the second year.

24 DJRA2.3 2nd report on EGEE Quality Status, including software and Grid operations


JRA2 structure

• CSSI is a service provider company in the development integration and operation of secured IT infrastructures. CSSI is responsible for GEANT network operation, with expertise in deployment, quality, operation and security issues. CSSI is also responsible for the Quality Assurance activity of the EU DataGrid project.

• CNRS played a major role in DataGrid in particular concerning integration, deployment and operation activities.

Partners Activity FTE (F+UF)

CSSI (France) Quality management and coordination. QA head in the Project Executive Board

1

CNRS (France) Quality standards, procedures and verifications

1+1

JRA2 Quality Assurance Management team


JRA2 Execution Plan

Tasks Period PM Artifacts

T.1 - Initialisation task M1 to 7 tbd

T.1.1 - Provide Quality Plan M1 to 4 Quality Plan, QA website

T.1.2 - Define with other activities standards, tools, procedures, guides (see next slides for details)

M1 to 4 Guidelines, procedures

T.1.3 - Define metrics and associated requirements for automatic monitoring tools)

M1 to 4 Convention of services

T.1.4 - Prepare and provide the initial training (QA principles, standards, procedures, etc.)

M5 to 7 Training

Recurrent tasks M1 to 24 tbd

T.2 - EU deliverables monitoring

T.3 - EU reporting process monitoring tasks repartition with the office financial officer?

T.4 - Quality metrics centralization and analyses See T.9

T.5 - Verification See T.9

T.6 - QAG coordination QAG minutes

T.7 - QA dissemination Training, presentations

T.8 - Audit Audit report

T.9 - JRA2 Management Quarterly report on QA activities and measurement


T.1.2.1: Document Management

• Procedures (target: 11/03)• Documentation management procedure

Document identification– e.g. EG-JA2-TYP-identifier-v2.1 – where identifier=EDMS number and/or internal number and/or

file_name) Documents templates (Word, Latex)

• Publication procedure

• Tools• Word, Latex• Document Management

EDMS: Deliverables (Egee EDMS structure - target:11/03) EDMS and/or CVS for others documents

• Metrics (tbd)


T.1.2.2: Project Management

• Procedures (target:12/03)• EU deliverables procedure

• EU reporting process and templates

• Project members check-in, check-out procedure

• Risk management procedure

• Tools• A tool for collecting “effort” will be appreciated (tbd)

• Excel reporting templates (target: 01/04)

• Agenda Maker (target: 12/03)

• Metrics (tbd)


T.1.2.3: Software engineeringTasks force should be constituted with JRAs in order to define:• Procedures and guides (part of the Software Development Plan)

• Release policy• Tests and validation procedures• External package validation• Anomalies procedure• Verification procedure (VV: Verification and Validation activities and check list)• Developers’ guide: Software packaging, Code Management, Build system, interfaces and

API, Documentation, tests guidelines, style and naming conventions, ….• Templates: checklist, test plan, manual style guides, …

• Tools• Build tool - Bugs tracking tool (priority)• Standardisation of the main languages for new developments and associated compilers• Memory leaks tool• Code analyser - Coding rules checking tool• Testing Framework tool. Tests coverage tool• Auto-documentation tool

• Metrics (tbd)• Actions: Target dates, Tasks force, Editors and 1st meeting date should be

defined


T.1.2.4: Production

Tasks force should be constituted with SAs in order to define:

• Procedures• Validation and acceptance procedure• Deployment procedure• New infrastructure certification• ….

• Tools• tbd

• Metrics (tbd)• Performance indicators (see https://edms.cern.ch/document/386039)• MTBF• MTTR• ….


T.1.2.5: Applications

Tasks force should be constituted with NA4 in order to define:

• Procedures (tbd)• Validation and acceptance procedure

• Tools (tbd)• Requirements coverage matrix

• ….

• Metrics (tbd)• ….


T.1.2.6: Dissemination and outreach

Tasks force should be constituted with NA2/3 in order to define:

• Procedures (tbd)• ….

• Tools (tbd)• ….

• Metrics (tbd)• ….