1 / 13

EGEE Quality Assurance: Ensuring Compliance and Operational Excellence

This project overview covers the objectives, organization, milestones, and deliverables of EGEE's Quality Assurance system. Quality objectives include systematic activities ensuring compliance to standards, with a focus on continuous improvement. Dedicated testing and validation teams, methodology support, and QA organization structure are detailed, highlighting the role of Quality Assurance Management. The execution plan includes documentation management, project management procedures, software engineering tasks, and production procedures. Metrics and tools are integrated to maintain quality standards across activities and ensure operational excellence.

ndwight
Download Presentation

EGEE Quality Assurance: Ensuring Compliance and Operational Excellence

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. JRA2: Quality AssuranceOverview Gabriel.Zaquine@cern.ch EGEE is proposed as a project funded by the European Union under contract IST.2003-508833 JRA workshop -28/10/03

  2. Summary • QA objectives • QA organisation • JRA2 major milestones and deliverables • JRA2 structure • JRA2 execution plan (draft) JRA2 Quality Assurance - 2

  3. 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. JRA2 Quality Assurance - 3

  4. Dedicated Testing / Validation teams JRA1, SA1, NA4 Methodology and Tools support team JRA1 QA organisation Project Executive Board Related Activities QA head • 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 Quality Assurance Management Team (QAM) -JRA2 (3 FTE) Coordination Quality Group (QAG) – Monthly Meeting • JRA1 QARs • JRA1 Manager • Rep. from each cluster • Rep. fromintegration/tests • Rep. from Tools • SA1 QARs • SA1 Manager • CIC Rep. • ROC Rep. • NA QARs • NA2/NA3 Rep. • NA4 Rep. SA2/JRA4 Rep. JRA3 Rep. 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 Quality Assurance - 4

  5. JRA2 Major milestones & deliverables JRA2 Quality Assurance - 5

  6. JRA2 structure JRA2 Quality Assurance Management team • 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. JRA2 Quality Assurance - 6

  7. JRA2 Execution Plan JRA2 Quality Assurance - 7

  8. 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) JRA2 Quality Assurance - 8

  9. 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) JRA2 Quality Assurance - 9

  10. T.1.2.3: Software engineering Tasks 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 JRA2 Quality Assurance - 10

  11. 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 • …. JRA2 Quality Assurance - 11

  12. 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) • …. JRA2 Quality Assurance - 12

  13. 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) • …. JRA2 Quality Assurance - 13

More Related