Quality Group activities Gabriel. Zaquine@cern. ch http: //edms. cern. ch/document/354542 QAG website: http: //www. eu-datagrid. org/QAG/ Mailing list: hep-project-grid-qag@cern. ch Gabriel Zaquine- Quality Group- 24/09/2002 - n° 1
Contents u Project policy statement to refocus on production quality u Retreat Release 1. 2 statement u QAG Objectives u QAG Organisation u Existing u QAG activities overview u Report u Main material from the 1 st QAG meeting (27/08/2002) actions & decisions Gabriel Zaquine- Quality Group- 24/09/2002 - n° 2
Project policy statement to refocus on production quality "The Data. Grid project's approach to software quality has been raised several times during the preparation of release 1. 2 of the software and most recently at the Project Technical Board. Improvements have been made to our procedures and style of work during the development of release 1. 2 based on our experience with the previous release. Data. Grid has a quickly growing community of users and dependent projects and hence with the expected large scale deployment of release 1. 2 it is now necessary to concentrate the project's efforts on its maintenance and support to allow the application groups to fully exploit the potential of this new software. To this end, the middleware work packages have been asked to identify resources for ensuring the continued support of deployed software and the implementation of software quality measures such as unit testing and adherence to project guidelines. WP 6 has been asked to create end-user support structures, a testing group and overall testbed control mechanisms. It is understood that resources are not infinite and that increased emphasis on quality and support aspects will mean that advanced functionality resulting from research work will take longer than originally foreseen in the project plans. The project management is convinced that making quality and support our highest priority is clearly within the project's goals and one of the most useful contributions the project can make to the grid community and Europe's aspirations in this domain. " Gabriel Zaquine- Quality Group- 24/09/2002 - n° 3
Retreat Release 1. 2 statement u Incremental n n improvements made to a stable release 1. 2 Each change tested and accepted/rejected before moving on to the next Advantage: we can move a working release to the certificate testbed after any improvement s u This Choice based on priorities for users and availability of resources (human and hardware) to perform further testing on the certification testbed relies on the 3 basic things being put in place: n A full-time testing group to assemble and maintain a comprehensive test suite n A certification testbed on which to perform tests n Automation of software installation, configuration & testing Gabriel Zaquine- Quality Group- 24/09/2002 - n° 4
QAG Objectives u The objectives of the quality group (QAG) is to define and introduce specific measures in the areas of the Software Development Process, Quality Assurance (QA) and related issues. The WP quality representative (QR) will make sure that it is happening inside his WP. u Here n n n are some priorities for 2002: Promote and facilitate QA (training) Concentrate quality effort on application of the test and validation process. Make sure the test plan is applied and input and output from each step are conforming to the required quality level. Progressively exchange between WPs best practices and common tools, by organizing some specific training (autotool, x. Unit, …). Gabriel Zaquine- Quality Group- 24/09/2002 - n° 5
QAG Organisation u Middleware WP representatives: n WP 1: Dave Colling, d. colling@ic. ac. uk n WP 2: Diana. Bosio, Diana. Bosio@cern. ch n WP 3: Steve Fisher, S. M. Fisher@rl. ac. uk n WP 4: Maite Barroso, Maria. Barroso. Lopez@cern. ch n WP 5: Regina Tam, R. Tam@rl. ac. uk u WP 6 & TSTG & Iteam ? group representative: Laurent Bobelin, laurent. bobelin@c-s. fr u WP 7 representative: ? u Applications representatives: n WP 8: Ingo Augustin, I. Augustin@cern. ch n WP 9: ? n WP 10: ? u Management representative: Bob Jones, Bob. Jones@cern. ch u Coordination: Gabriel Zaquine, gabriel. zaquine@cern. ch Gabriel Zaquine- Quality Group- 24/09/2002 - n° 6
Existing material (1/2) Software development and Quality documents: u Software release policy: http: //edms. cern. ch/document/331457 u Software release plan: http: //edms. cern. ch/document/333297 u Test and validation process (draft): http: //edms. cern. ch/document/349248 u Testbed software integration process, http: //edms. cern. ch/document/332372 operational policies and procedures: u Quality Plan: http: //edms. cern. ch/document/328806 u Naming and comments conventions: http: //edms. cern. ch/document/328838 u Developers Guideline (proposal) u u u Configuration management and build conventions: http: //datagrid. in 2 p 3. fr/HOWTO/CCIN 2 P 3 repository. Conventions. html Information about the automatic build procedure is here: http: //datagrid. in 2 p 3. fr/index. php? id=autobuild Quality indicators: http: //edms. cern. ch/document/341708 …. /…. . Gabriel Zaquine- Quality Group- 24/09/2002 - n° 7
Existing materials (2/2) u Test plan (drafts): n WP 1: http: //edms. cern. ch/document/348450 n WP 2: http: //edms. cern. ch/document/345533 n WP 3: http: //edms. cern. ch/document/348523 n WP 4: http: //edms. cern. ch/document/348628 n WP 5: http: //edms. cern. ch/document/348428 n Iteam : (not yet provided) n TSTG: http: //edms. cern. ch/document/341943 n WP 7: http: //edms. cern. ch/document/348745 n Applications: (not yet provided) u WP 6 Evaluation of testbed 1: http: //edms. cern. ch/document/336389 u WP 8 Evaluation of testbed 1: http: //edms. cern. ch/document/334920 u An up to date set of statistics (#modules, #lines of code, languages used etc. ) about the latest code release is available here: http: //datagrid. in 2 p 3. fr/autobuild/default/Code. Stats. html Gabriel Zaquine- Quality Group- 24/09/2002 - n° 8
QAG activities overview u Promote and facilitate QA (training) and make sure that QA is happening inside each WP for activities involved in design, development enhancement, distribution, support and maintenance of the products. Make the developers aware that the software they write should be easily installed, maintained, and reliable. Make sure QA information reaches all members of the project. u Procedures and standards monitoring (adherence to) u Verification and validation (V&V) monitoring and Testing monitoring u Deliveries monitoring: Input and output from each step are conforming to the required quality requirements – Delay, quality criteria, completeness, …. u Configuration management monitoring (CVS) u Nonconformance reporting and corrective action monitoring u Quality indicators set up and monitoring u Continuous improvement proposals of the QA process u Report on WPs QA activities Must be prioritised …. For more details, see QAG general presentation: http: //edms. cern. ch/document/353791 Gabriel Zaquine- Quality Group- 24/09/2002 - n° 9
Report from the 1 st QAG meeting u Open (27/08/02) discussion points: n Test plans status (Quid Iteam Test Plan and Application Test Plan) ? n Static metrics tools / code review n Bugzilla pending anomalies follow-up n n Quality indicators with a metric closer to the user (e. g. Number of important bugs, mean time to repair bugs, …. ). How to control, validate, and facilitate interaction and interfaces between WPs? n How making the release policy applied? n Design validation n How to improve quality culture inside the project Gabriel Zaquine- Quality Group- 24/09/2002 - n° 10
Current main Actions & Decisions u Main n n Actions list: QR should provide a document with proposals to improve quality inside each WP (3/10/02) QAG phone conference meeting (10/10/02, 14: 00) u QAG plan with prioritised measures (18/10/02) u Decision n (to be confirmed soon) Bugzilla pending anomalies follow-up: s Each QR will monitor his WP’s anomalies. s Weekly monitoring and Monthly Report. Gabriel Zaquine- Quality Group- 24/09/2002 - n° 11
Скачать презентацию Quality Group activities Gabriel Zaquine cern ch http edms
7fe87c716e86a3feadba602cbcfff410.ppt