Software Process Training

Transcription

1 Dr. Ernest Wallmüller Wolfgang Höh Rule 9 and Product Quality Assurance Qualität & Informatik Copyright Qualität & Informatik 2005

2 - What does it mean? Nonconformance? Copyright Qualität & Informatik / 2

3 Context Measurements, analyses Information needs Configuration items; change requests All process areas Baselines; audit reports Quality and noncompliance issues es and work products; standards and procedures Copyright Qualität & Informatik / 3

4 SW Development Overview: Rule 9 (QM) Phase A Phase B Phase C Phase D Phase E Phase F P- Review 2 URS Handover of URS to PL-DP P- Review 3 Start Development KICK OFF SRS P- Review 4 (SRS- Review) DDS- Review Draft Architectural Design Complete Software Design Design- Review SDD- Review SW-Design Approval 09_ Impl. and Module Test Integration and Integration Test α n- Version Check Completeness of Deployments System Test Function Test Applic. Test P- Review 5 M Tryout Representative βa, β B, β C,.. GPM: Beta Version Release Review β1, β 2, β 3,.. Type Approval P- Review 6 Final Version Copyright Qualität & Informatik / 4

5 - Policy / Scope / Purpose! Policy According to the Quality-, Environmental- and Safety-Manual (chapter 5.3) the policy establishes the evaluation for: Performed processes (standard software development process and Qday process), work products and services against applicable process descriptions, standards and procedures Identifying, documenting, addressing and tracking of noncompliance issues Providing feedback to relevant stakeholder of the results of quality assurance activities! Scope The defined content is valid for all departments within the SBU Instrumentation and Test Systems for establishing and maintaining MI relevant work products. Copyright Qualität & Informatik / 5

6 - Policy / Scope / Purpose (cont.)! Purpose Providing staff and management with objective insight into processes and associated work products. Copyright Qualität & Informatik / 6

7 Exercise: Familiarization! Method: Plenum! Timing: 10! Form: Brainstorming and discussion! Documents: none! Deliverable: Documentation on flipchart (Trainer)! Questions: I. What are you experiences with SQA? II. What worked well in the past? III. What did not work so well? Copyright Qualität & Informatik / 7

8 Pillars of Quality Standards Quality Configuration Management Measurements guide control show Copyright Qualität & Informatik / 8

9 Cost of Quality... Quality Is Not Free But Quality Is Cheaper Than The Alternatives SEI Copyright Qualität & Informatik / 9

10 From Organization to the Product Copyright Qualität & Informatik / 10

11 Role of SQA Copyright Qualität & Informatik / 11

12 Exercise: Roles, Activities, Work Products! Method: Individual! Timing: 15! Form: Individual elaboration! Documents: Rule 9; form: next foil! Deliverable: Filled in form Question: I. Based on your experience, the prior discussion and the process definition list the involved roles, the performed activities, and the produced work products. Copyright Qualität & Informatik / 12

13 Roles, Activities, Work Products Roles Activities Work Products Copyright Qualität & Informatik / 13

14 Roles, Activities, Work Products Roles Central QM GPM HOD OPO QA SEPG Activities evaluation Evaluation of Work Products Resolution of Non-compliance Issues Work Products P design review reports MES System Audit Report Product Line Quality Trends Q-Day Analysis Reports Non-Compliance List Projects Non-Compliance List Audits Copyright Qualität & Informatik / 14

15 with Practices Work Products Objectively Evaluate es and Work Products Evaluation Evaluation of Work Products Reports and Records Provide Objective Insight Resolution of Non-compliance Issues Copyright Qualität & Informatik / 15

16 Tasks Practice Task Work Products Evaluation Evaluation of Work Products Resolution of Non-compliance Issues Organize, execute P Design Review meetings Plan, execute, and document internal audits Evaluate work packages according SQA plan Monitor and ensure closure of corrective actions of noncompliance lists (audits) Monitor and ensure closure of corrective actions of noncompliance lists (projects) P design review reports P Projects Action List MES Audit Report Updated SQA plan Non-Compliance List in MES Audit Report P Projects Action List Copyright Qualität & Informatik / 16

17 & Project Improvement Monitoring List Lessons learned and best practices Id Improvement Suggestion Project Priority Suggested by Date Responsible for improvement Solution available (date) Status L1 Einführung der Finanzberichte Project Verfahrensanweisung Astrid Dahmen Monitoring and Johann Neuhold MES-VA-- High Christoph Ennemoser Implemented Control - Christoph Ennemoser 001_R01_Financial_Report_englis Johann Neuhold "m1" ch.doc L2 Checkbox für unkoordinierte Schnittstellenänderungen Configuration Management - "m2" L3 Aufnahme von Abnahmekriterien in die URS Requirement Development RME - "mrm1" L4 L5 L6 L7 Anforderungsdatenbank Requirement Management RME - "mrm1" Einführung bzw. Erhöhung des Testautomatisierungsgrades Verification - "mvv2" High Middle High Middle Johann Neuhold Johann Neuhold Johann Neuhold Christoph Ennemoser Teilnahme Projektabschlussbesprechung (Hans Neuhold) Middle Johann Neuhold Definition der Arbeitsergebnissen die unter Versionskontrolle zu stellen sind Configuration Management - "m1" L8 P Meilenstein Trend Analyse Project Monitoring and Control - "m1" L9 L10 Final inspections of PU text data. An acceptance review of all PU text should be defined (Franz Steiner). SRS-Review should be performed in two parts: 1. Formal (Check, if all required chapters are available). 2. Technical review. If possible in cooperation with a member of X. Santorin V3.3 Santorin V3.3 Middle High Middle Middle Johann Neuhold Johann Neuhold Johann Neuhold Implemented in ClearQuest Implemented Michael Conrad Michael Conrad Christoph Ennemoser Johann Neuhold Johann Neuhold Johann Neuhold Astrid Lock Franz Steiner Astrid Lock SEPG Requirements-DB im ClearQuest implementiert KW 9 Vorstellung durch Hrn. Neuhold / alle GPM, PM File: \\nfs08\mesproj\development_standards\4002_mi\04_opal\ Best_Practice\Lessons_learned\Lessons_learned_and_best_practices.xls Submitted Submitted Implemented Einführung wurde durchgeführt keine direkte Teilnahme, sondern danach getrenntes Gespräch mit Implemented Projketleiter Version Control of Work Products.xls \\nspe001\abtpe\peq\p_metrics\ P_Milestones_Trend_Analysis_ PE.xls Implemented Implemented Submitted Submitted Copyright Qualität & Informatik / 17

18 AVL SW Organization Central Quality Department SPSC (SW Steering Committee) Members: Strategic Owner, HODs of LDCs & OPO Release of process changes Release of architecture rules Release of tools Implementation of process in LDCs CAMM (Central Analysis & Measurement Manager) Acquire metrics Analyse process performance LAMM (Local Analysis & Measurement Manager) Submit metrics Analyse process performance Identify and submit improvement actions to OPO OPO (Operational Owner) SEPG (SW Engineering Group) Members: Agents of LDCs Define/Maintain MI guidelines for PAs based on PAT proposals Define/maintain workflow Coaching in LDCs Administrate best practices in OPAL Propose PAOs Headed by OPO PAO ( Area Owner) PAT ( Action Team) Members: PAO & specialists (Senior Engineers) Define process guidelines Prepare improvement suggestions Submit best practices Headed by PAO (if PA affected) SEAG (SW Engineering Architecture Group) Members: Agents of LDCs Define/maintain architecture guidelines Manage interfaces between products Define certified MESdevelopment tools Headed by OPO AAT (Architecture Action Team) Members: Specialists (Senior Engineers) Define architectural guidelines Prepare architectual improvements Submit best practices Organizational SW Improvement Structure SEPG... OPO... PAT SEAG.. SPSC... SW Engineering Group Operational Owner Action Teams SW Engineering Architecture Group SW Steering Committee Copyright Qualität & Informatik / 18

19 Responsibilities in MES Define and monitor Implement SPO Strategic Owner Sponsor in upper management OPO Operational Owner Responsible in MES for SW process improvement Head of SEPG Reports status of SW process status to SPO and SPSC SPSC SW Steering Committee Release of SW processes proposed by SEPG Members: HODs of LDC HOD Head of Developments Implement defined SW processes in their development center Copyright Qualität & Informatik / 19

20 Responsibilities in MES Manage improvements Define rules SEPG SW Engineering Group 5 members of largest SW development centers Organize SW process improvement activities Coaching of SW engineers Distribute best practices via OPAL data base PAT Area Team Best 4 5 experts in MES for specific process areas Define/improve rules for process areas Proposed by HODs, appointed by SEPG Copyright Qualität & Informatik / 20

21 Exercise: Task Description! Method: Group work! Timing: 20 group work, 15 presentation & discussion (comparative discussion of group results)! Form: Group elaboration! Documents: Rule 9:! Deliverable: Task description on flipchart! Question: I. Describe the selected task _T01: Evaluation of Work Products using the presented description technique ("next foil). Copyright Qualität & Informatik / 21

22 Task Description Technique Input ID Task Name Description Roles Tools Method/Technique Output Copyright Qualität & Informatik / 22

23 Task Details Evaluation of Work Products Input Generic SQA-Plan Project-specific SQA-Plan ID _T01 Roles PL-DP Task Name Evaluation of Work Products Description Evaluation of the relevant work products according to the project-specific SQAplan (mandatory and optional work products) and the P Design Review checklist. Transfer of non-compliance issues to the P Projects Action List. Resp. for task _T01 Tools Template: Template FB-MES SQ Pdr1 to 6 P Design Review checklist Method/Technique Review techniques (Rule 24: ) Output P Design Review report Type Approval Report P Projects Action List Copyright Qualität & Informatik / 23

24 Rule 9: Work Products and Templates WP Id Type Description Task Id Resp. Link to Template _W01 M P design review reports _T01 QA Template FB-MES SQ- Pdr1 to 6 _W02 M MES System Audit Report _T03 Central QM Template FB-MES SQ_Bericht_internes_Audit.dot _W03 M Non-Compliance List - Projects _T05 HOD Template P_Projects_Action_List _W04 M Non-Compliance List - Audits _T04 Central QM Internal Audit Action List Copyright Qualität & Informatik / 24

25 Exercise: Adherence! Method: Small groups! Timing: 10 group work, 10 discussion in plenum! Form: Group elaboration! Documents: none! Deliverable: Group notes! Question: es are defined and trained according to its definition, standard, and procedures. I. How can we ensure that the processes are lived accordingly? II. Who is evaluating the adherence? Copyright Qualität & Informatik / 25

26 GP 2.9 for Objectively Evaluate Adherence GP2.9 OBJECTIVELY EVALUATE ADHERENCE Objectively evaluate adherence of the process against its process description, standards, and procedures, and address noncompliance. Purpose: Provide credible assurance that the process is implemented as planned and adheres to its process description, standards, and procedures. Practice:! People not directly responsible for managing or performing the activities of the process typically evaluate adherence.! Adherence is evaluated by people within the organization, but external to the process or project, or by people external to the organization. Copyright Qualität & Informatik / 26

27 Rule 90: Concluding Discussion What was important for you concerning this Rule? Copyright Qualität & Informatik / 27

28 Any Questions Copyright Qualität & Informatik / 28