OHT 12.1 Galin, SQA from theory to implementation © Pearson Education Limited 2004 Introduction Types of external participants Risks and benefits of introducing.

Slides:



Advertisements
Similar presentations
Software Quality Assurance Plan
Advertisements

 Every stage from phase DESIGN in Software Development Process will have “design document” especially in analysis and design phases.  “Design document”
OHT 10.1 Galin, SQA from theory to implementation © Pearson Education Limited 2004 The testing process Determining the test methodology phase Planning.
OHT 5.1 Galin, SQA from theory to implementation © Pearson Education Limited 2004 Contract review process and stages Contract review objectives Implementation.
OHT 6.1 Galin, SQA from theory to implementation © Pearson Education Limited 2004 Development plan and quality plan objectives The elements of the development.
OHT 8.1 Galin, SQA from theory to implementation © Pearson Education Limited Review objectives Formal design reviews (FDRs) Participants Preparations.
OHT 2.1 Galin, SQA from theory to implementation © Pearson Education Limited 2004 What is software? Software errors, faults and failures Classification.
OHT 8.1 Galin, SQA from theory to implementation © Pearson Education Limited 2004 Review objectives Formal design reviews (FDRs) Participants Preparations.
OHT 4.1 Galin, SQA from theory to implementation © Pearson Education Limited 2004 Pre-project components Software project life cycle components Infrastructure.
OHT 7.1 Galin, SQA from theory to implementation © Pearson Education Limited 2004 Software development methodologies: - The software development life cycle.
OHT 22.1 Galin, SQA from theory to implementation © Pearson Education Limited Objectives of cost of software quality metrics 2.The classic model.
OHT 14.1 Galin, SQA from theory to implementation © Pearson Education Limited 2004 Software quality infrastructure components The need for procedures and.
Components of software quality assurance system overview
OHT 5.1 Galin, SQA from theory to implementation © Pearson Education Limited 2004 Contract review process and stages Contract review objectives Implementation.
OHT 1.1 Galin, SQA from theory to implementation © Pearson Education Limited 2004 The uniqueness of software quality assurance The environments for which.
OHT 6.1 Galin, SQA from theory to implementation © Pearson Education Limited 2004 Development plan and quality plan objectives The elements of the development.
Chapter 8 Assuring the quality of external participants’ contributions
Mitun PatelMXP07U. Organisational structure Top management; this includes the organisation’s general manager and its executives Department managers; this.
SQA Architecture Software Quality.
OHT 17.1 Galin, SQA from theory to implementation © Pearson Education Limited 2004 Corrective and preventive actions — definitions The corrective and preventive.
Development and Quality Plans
Development plan and quality plan for your Project
Configuration Management Avoiding Costly Confusion mostly stolen from Chapter 27 of Pressman.
OHT 22.1 Galin, SQA from theory to implementation © Pearson Education Limited 2004 Software Quality assurance (SQA) SWE 333 Dr Khalid Alnafjan
Prof. Mohamed Batouche Costs of software quality Introduction  More and more, commercial companies or public organizations are requiring.
OHT 2.1 Galin, SQA from theory to implementation © Pearson Education Limited 2004 Software Quality assurance (SQA) SWE 333 Dr Khalid Alnafjan
OHT 19.1 Galin, SQA from theory to implementation © Pearson Education Limited 2004 Controlled documents and quality records Definitions and objectives.
SE513 Software Quality Assurance Lecture04: Contract Review Galin, SQA from Theory to Education Limited 2004.
OHT 16.1 Galin, SQA from theory to implementation © Pearson Education Limited 2004 The objectives of training and certification The training and certification.
Software Quality assurance SQA – SWE 333
OHT 4.1 Galin, SQA from theory to implementation © Pearson Education Limited 2004 Software Quality assurance (SQA) SWE 333 Dr Khalid Alnafjan
SQA Architecture Software Quality By: MSMZ.
National Cheng Kung University 軟體品質管理 期末報告 The SQA Unit and Other Actors in the SQA System Reporter: 羅國益 Teacher: 朱治平 Date: 2014/12/30.
Chapter 4 Components of the Software Quality Assurance System
Galin, SQA from theory to implementation © Pearson Education Limited 2004 Review objectives Formal design reviews (FDRs) Participants Preparations The.
Software Quality Assurance Activities
OHT 25.1 Galin, SQA from theory to implementation © Pearson Education Limited 2004 The quality assurance organizational framework Top management’s quality.
Assuring the quality of external participants' contributions Michael Rooney mpr07u.
OHT 23.1 Galin, SQA from theory to implementation © Pearson Education Limited 2004 The benefits of use of standards The organizations involved in standards.
Chapter 5 Contract review Contract review process and stages
Overview of SQA Components
Project Tracking. Questions... Why should we track a project that is underway? What aspects of a project need tracking?
The Software Quality Assurance System By Jonathon Gibbs Jonathon Gibbs (jxg16u) 26 th November 2009.
S Q A.
OHT 5.1 Galin, SQA from theory to implementation © Pearson Education Limited 2004 Contract review process and stages Contract review objectives Implementation.
OHT 12.1 Galin, SQA from theory to implementation © Pearson Education Limited 2004 Introduction Types of external participants Risks and benefits of introducing.
OHT 18.1 Galin, SQA from theory to implementation © Pearson Education Limited 2004 Introduction The foundations of high quality Foundation 1: software.
OHT 1.1 Galin, SQA from theory to implementation © Pearson Education Limited 2004 The uniqueness of software quality assurance The environments for which.
SE513 Software Quality Assurance Lecture07: Maintenance Life Cycle Quality Assurance Tools Galin, SQA from Theory to Education.
Pre-Project Components
OHT 20.1 Galin, SQA from theory to implementation © Pearson Education Limited 2004 The components of project progress control Progress control of internal.
OHT 7.1 Galin, SQA from theory to implementation © Pearson Education Limited 2004 Software development methodologies: - The software development life cycle.
OHT 15.1 Galin, SQA from theory to implementation © Pearson Education Limited 2004 Templates The contribution of templates to software quality The organizational.
SE513 Software Quality Assurance Lecture10: Documentation and Quality Records Control Galin, SQA from Theory to Education Limited.
SEN 460 Software Quality Assurance. Bahria University Karachi Campus Waseem Akhtar Mufti B.E(C.S.E) UIT, M.S(S.E) AAU Denmark Assistant Professor Department.
Multitude of source of errors - various style of source of errors will affect the SQA components * The environment in which software development & maintenance.
Pertemuan 14 Matakuliah: A0214/Audit Sistem Informasi Tahun: 2007.
SQA COMPONENTS IN THE PROJECT LIFE CYCLE C HAPTER 8 Dr. Ahmad F. Shubita.
OHT 18.1 Galin, SQA from theory to implementation © Pearson Education Limited 2004 Software configuration, software configuration items and software configuration.
S TANDARDS, CERTIFICATION AND ASSESSMENT C HAPTER 23 Dr. Ahmad F. Shubita.
OHT 10.1 Galin, SQA from theory to implementation © Pearson Education Limited 2004 The testing process Determining the test methodology phase Planning.
OHT 15.1 Galin, SQA from theory to implementation © Pearson Education Limited 2004 Templates The contribution of templates to software quality The organizational.
Software Quality Assurance
Components of software quality assurance system overview
Components of software quality assurance system overview
Components of software quality assurance system overview
Components of software quality assurance system overview
Chapter # 8 Quality Management Standards
Chapter # 4 Development and Quality Plans
Chapter # 3 The Components of SQA
Presentation transcript:

OHT 12.1 Galin, SQA from theory to implementation © Pearson Education Limited 2004 Introduction Types of external participants Risks and benefits of introducing external participants Assuring the quality of external participants’ contribution: objectives SQA tools for assuring the quality of external participants’ contributions

OHT 12.2 Galin, SQA from theory to implementation © Pearson Education Limited 2004 Subcontractors (currently called “outsourcing” organizations) Suppliers of COTS software and reused software modules The customers themselves as participants in performing the project

OHT 12.3 Galin, SQA from theory to implementation © Pearson Education Limited 2004

OHT 12.4 Galin, SQA from theory to implementation © Pearson Education Limited 2004 Main risks to project quality (1) Delays in completion of the project (2) Low quality of project parts supplied by external participants (3) Future maintenance difficulties (4) Loss of control over project parts Main benefits for the contractor: (1) Budget reductions. (2) Remedy of professional staff shortages. (3) Shorter project schedule. (4) Acquisition of expertise in specialized areas Main benefits for the customer (as external participant): (1) Protecting the customer’s commercial secrets. (2) Provision of employment to internal software development department. (3) Acquisition of project know-how for self-supplied maintenance. (4) Project cost reductions.

OHT 12.5 Galin, SQA from theory to implementation © Pearson Education Limited 2004 Assuring the quality of external participants’ contribution: objectives To prevent delays and ensure early alert of anticipated delays. To assure acceptable quality levels and receive early warning of quality requirement. To assure adequate documentation To assure comprehensive control over external participants’ performance.

OHT 12.6 Galin, SQA from theory to implementation © Pearson Education Limited 2004 Requirements document reviews Evaluation of choice criteria regarding external participants Establishment of project coordination and joint control committee Participation in design reviews Participation in software testing Formulation of special procedures Certification of supplier’s team leaders and members Preparation of progress reports of development activities Review of deliverables (documents) and acceptance tests.

OHT 12.7 Galin, SQA from theory to implementation © Pearson Education Limited 2004 Requirements document reviews Issues to be dealt with include: Functionality – functional requirement, interface, performance, maintenance services Formal & Staff – qualification, joint control committee, delivered documents, criteria for completion, financial arrangement SQA – participation of design reviews & software testing

OHT 12.8 Galin, SQA from theory to implementation © Pearson Education Limited 2004 Evaluation of choice criteria regarding external participants Previous experience & performance Quality assurance system Survey of opinions - requires systematic reporting by a dept. Systematic evaluation by a evaluation committee or a responsible manager

OHT 12.9 Galin, SQA from theory to implementation © Pearson Education Limited 2004 Establishment of project coordination and joint control committee Activities: -Confirmation of timetable and milestones -Follow-up according to progress report -Meeting with team leader and others -Making decisions identified in design reviews, software tests, and follow-up -Solving disagreements

OHT Galin, SQA from theory to implementation © Pearson Education Limited 2004 Participation in design reviews extent

OHT Galin, SQA from theory to implementation © Pearson Education Limited 2004 Participation in software testing Include, when required, Planning Design of the tests Reviews of the test results Follow-up meeting for corrections and regression testing

OHT Galin, SQA from theory to implementation © Pearson Education Limited 2004 Formulation of special procedures Supported by templates, checklists and forms. Objectives - preparation of requirement documents - choice of subcontractor or supplier - audit of the subcontractor’s SQA system - appointment of the committee - progress reporting requirements

OHT Galin, SQA from theory to implementation © Pearson Education Limited 2004 Certification of supplier’s team leaders and members Qualification and certification Implementation Changes and replacement of team member are to be approved

OHT Galin, SQA from theory to implementation © Pearson Education Limited 2004 Preparation of progress reports of development activities Contents: -Follow-up of the risks -Follow-up of the schedule -Follow-up of the usage of resources -Follow-up of the budget

OHT Galin, SQA from theory to implementation © Pearson Education Limited 2004 Review of deliverables (documents) and acceptance tests Review of software development documents Testing of the software components of the external participant’s products