EC Review – 01/03/2002 – G. Zaquine – Quality Assurance – WP12 – CS-SI – n° 1 DataGrid Quality Assurance Gabriel Zaquine Quality Engineer - WP12 – CS-SI

EC Review – 01/03/2002 – G. Zaquine – Quality Assurance – WP12 – CS-SI – n° 2 Outline u Quality objectives u Quality deliverables & related deliverables u Main Process description n Project monitoring and reporting n Document management and deliverables review procedure n Software release procedure n Configuration management, code repository, autobuild and bug tracking management n Standards and tools u Plan for the next year u Summary u Questions

EC Review – 01/03/2002 – G. Zaquine – Quality Assurance – WP12 – CS-SI – n° 3 Quality objectives (1/2) u Merge Scientists from research environment with conventional industrial Quality Assurance activity. u Provide Quality assurance taking in to account the main DataGrid project characteristics: n Large software development (about 200 persons working on the project) n Long life cycle development (36 months) n Distributed development of software (21 partners) n Large scale integration (several Testbed sites) n Software portability (Linux, Solaris, …), ….

EC Review – 01/03/2002 – G. Zaquine – Quality Assurance – WP12 – CS-SI – n° 4 Quality objectives (2/2) Overall quality plan: u Year 1 - Focus on: n Quality of the deliverables n Project monitoring and reporting n Software infrastructure u Year 2 - Focus on: n Quality of the software production n User support n Software distribution and Testbed infrastructure u Year 3 - Focus on: n Global Quality of Services provided.

EC Review – 01/03/2002 – G. Zaquine – Quality Assurance – WP12 – CS-SI – n° 5 Quality deliverables & related deliverables u Quality Plan (D12.1) n Quality organisation - Project organisation - Risk management n Document management - Document templates n Software quality Assurance - Methods and tools used n Configuration Management - Code repository, autobuild and bug tracking management u Software Release Policy and Software release Plan (D12.3) n Policy for iterative software releases including milestones, time-scales and supporting techniques and tools to be employed. u Naming conventions (D12.2) n Naming conventions, project directories organisation and comments conventions, that should be applied to all DataGrid middleware packages. The use of these conventions is strongly encouraged for Java, C++ and C. u Configuration management and Build conventions (D6.2) n Conventions for CVS module structure, naming and tagging, as well as package organization.

EC Review – 01/03/2002 – G. Zaquine – Quality Assurance – WP12 – CS-SI – n° 6 Main Process Description

EC Review – 01/03/2002 – G. Zaquine – Quality Assurance – WP12 – CS-SI – n° 7 Project Monitoring and reporting (1/3) u Main project monitoring mechanisms: n WP Managers weekly meeting (Weekly phone conference calls) n Project Technical Board meeting ( every 2 months) n Project Management Board meeting (every quarter) n Quarterly and Annual Reports u Agenda n Achievements n Status of milestones n Deviations n Issues, Risks n Meetings/Conferences/Papers/Dissemination n Resources

EC Review – 01/03/2002 – G. Zaquine – Quality Assurance – WP12 – CS-SI – n° 8 Project Monitoring and reporting (2/3) Q1, Q2, … PTB, PMB Project Office WPs Partners WP1 to 12 Validation and Generates Quarterly Report Global Validation EUEU Quarter Consumed effort Validation Prepares the Project Quarterly Report Cost Claims (every year) Validation u Quarterly/Annual reports & Cost Claims process Generates WP annual Report Validation Prepares the Project Annual Report

EC Review – 01/03/2002 – G. Zaquine – Quality Assurance – WP12 – CS-SI – n° 9 Project Monitoring and reporting (3/3) u DataGrid website: Project management and technical part

EC Review – 01/03/2002 – G. Zaquine – Quality Assurance – WP12 – CS-SI – n° 10 Document Management u EDMS: Cern Document Management Tool u Document identification conventions u Document Templates u Deliverables review procedure u Standardised document production tools: Word, Latex, pdf u Standardised document management tool: EDMS

EC Review – 01/03/2002 – G. Zaquine – Quality Assurance – WP12 – CS-SI – n° 11 Deliverables Review Procedure In Work Under PMB Approval Under EU Approval Under PTB Approval Under Review Reviewed within the WP. For each deliverable the PTB chairman appoints a moderator. The moderator finds three appropriate reviewers.Others WP Managers can send their comments to the moderator. Last version deadline is one week before the PTB. Reviewed by PTB members and the internal independent reviewer. PMB members have one week to send their comments. Last version deadline is three weeks before the PTB. Endorsed by PMB. Endorsed by PTB. EU Approved 01/03/2002 Document Workflow followed within EDMS

EC Review – 01/03/2002 – G. Zaquine – Quality Assurance – WP12 – CS-SI – n° 12 Software Release Procedure u Coordination meeting n Gather feedback on previous release n Review plan for next release u WP meeting n WPs elaborate their specific work-plans for the next release. u Software Release work-plan coordination n Establishment of an overall plan for the next release. u Sw development n Performed by WPs in dispersed institutes and run unit tests u Software integration n Performed by WP6 on frozen sw n Integration tests run u Acceptance tests n Performed by the validation team. u Roll-out n Present sw to application groups n Deploy on testbed Coord. meeting Release Plan++ Release feedback Release Plan WP meetings WP1 WP3 WP7 Component 1 Component n Globus EDG release Distributed EDG release Roll-out. meeting testbed 1: Dec ~100 participants

EC Review – 01/03/2002 – G. Zaquine – Quality Assurance – WP12 – CS-SI – n° 13 Configuration Management, code repository, autobuild and bug tracking management u Central repository n DataGrid code is managed within a central repository. This repository consist of a CVS server for source code and a package repository to distribute the packaged code. The repository is hosted by WP6. u Autobuild system n Performs nightly rebuilds of the DataGrid code (based on build conventions D6.2) n Reports on results on a web page n API documentation is generated from source code and published on the website n An autocheck procedure will perform basic functionality tests u Bug reporting and tracking n Centralised via Bugzilla

EC Review – 01/03/2002 – G. Zaquine – Quality Assurance – WP12 – CS-SI – n° 14 Standards and tools u Documentation production: Ms Office, Latex, pdf u Documentation Management: EDMS u Code Management: CVS u Build tools: autoconf, automake, ant u Bug tracking: Bugzilla u Auto-documentation tools: Javadoc, Doxygen u Coding rules checking tool: Code Checker u Testing: junit, cppunit

EC Review – 01/03/2002 – G. Zaquine – Quality Assurance – WP12 – CS-SI – n° 15 Plan for the next year u Year 2: Focus on Quality of the software production, user support, software distribution and Testbed infrastructure n Improve and extend the infrastructure and toolset to facilitated software development, integration and distribution: Automatic build, autocheck, result notification, test plan. n Empower Iteam to control quality of contributed software and documentation. n Refine requirements priorities and coverage tests plan.

EC Review – 01/03/2002 – G. Zaquine – Quality Assurance – WP12 – CS-SI – n° 16 Summary From the quality point of view, u For the fist year, the quality focus was on: n Quality of the deliverables n Project monitoring and reporting n Software infrastructure u The second year will further incorporate the benefit of successive software releases as defined in the Software Release Policy document.