OHT 20.1 Galin, SQA from theory to implementation © Pearson Education Limited 2004 The components of project progress control Progress control of internal.

Slides:



Advertisements
Similar presentations
Chapter 7: Key Process Areas for Level 2: Repeatable - Arvind Kabir Yateesh.
Advertisements

More CMM Part Two : Details.
OHT 9.1 Galin, SQA from theory to implementation © Pearson Education Limited 2004 Definitions and objectives Software testing strategies Software test.
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 9.1 Galin, SQA from theory to implementation © Pearson Education Limited 2004 Definitions and objectives Software testing strategies Software test.
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 3.1 Galin, SQA from theory to implementation © Pearson Education Limited 2004 The need for comprehensive software quality requirements Classification.
OHT 1.1 Galin, SQA from theory to implementation © Pearson Education Limited 2004 The uniqueness of software quality assurance The environments for which.
OHT 7.1 Galin, SQA from theory to implementation © Pearson Education Limited 2004 Software development methodologies: - The software development life cycle.
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
OHT 13.1 Galin, SQA from theory to implementation © Pearson Education Limited 2004 What is a CASE tool? The contribution of CASE tools to software product.
ANSI/EIA -748 EVMS 32 Guidelines National Aeronautics and Space Administration.
Galin, SQA from theory to implementation © Pearson Education Limited Chapter 13 CASE Tools and their Effect on Software Quality.
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.
OHT 2.1 Galin, SQA from theory to implementation © Pearson Education Limited 2004 Software Quality - continued So let’s move on to ‘exactly’ what we mean.
Development and Quality Plans
Development plan and quality plan for your Project
OHT 22.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 21.1 Galin, SQA from theory to implementation © Pearson Education Limited 2004 Software Quality assurance (SQA) SWE 333 Dr Khalid Alnafjan
OHT 16.1 Galin, SQA from theory to implementation © Pearson Education Limited 2004 The objectives of training and certification The training and certification.
SQA Architecture Software Quality By: MSMZ.
Galin, SQA from theory to implementation © Pearson Education Limited Chapter 6 Development Plans Quality Plans.
National Cheng Kung University 軟體品質管理 期末報告 The SQA Unit and Other Actors in the SQA System Reporter: 羅國益 Teacher: 朱治平 Date: 2014/12/30.
OHT 18.1 Galin, SQA from theory to implementation © Pearson Education Limited 2004 Chapter 18 Configuration Management.
Galin, SQA from theory to implementation © Pearson Education Limited 2004 Review objectives Formal design reviews (FDRs) Participants Preparations The.
Project Sponsor Project Manager 04/24/ Major Projects Quarterly Review.
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.
SE513 Software Quality Control Lecture01: Introduction to Software Quality Assurance Galin, SQA from Theory to Education Limited.
Project Tracking. Questions... Why should we track a project that is underway? What aspects of a project need tracking?
OHT 7.1 Galin, SQA from theory to implementation © Pearson Education Limited 2004 Chapter 7.1.
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
Module 1: Introducing Windows Server 2003 Network Infrastructure Planning, Tools, and Documentation.
OHT 12.1 Galin, SQA from theory to implementation © Pearson Education Limited 2004 Introduction Types of external participants Risks and benefits of introducing.
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.
1 Project Management Software management is distinct and often more difficult from other engineering managements mainly because: – Software product is.
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.
OHT 18.1 Galin, SQA from theory to implementation © Pearson Education Limited 2004 Software configuration, software configuration items and software configuration.
M ANAGKEMENT COMPONENTS OF SOFTWARE QUALITY. M ANAGEMENT COMPONENTS OF SOFTWARE QUALITY The three basic SQA management tools offered here are: Project.
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.
Components of software quality assurance system overview
Components of software quality assurance system overview
Software Verification and Validation
Chapter # 6 Software Configuration Management
Chapter # 4 Development and Quality Plans
Chapter # 3 The Components of SQA
Presentation transcript:

OHT 20.1 Galin, SQA from theory to implementation © Pearson Education Limited 2004 The components of project progress control Progress control of internal projects and external participants Implementation of project progress control regimes Computerized tools for software progress control

OHT 20.2 Galin, SQA from theory to implementation © Pearson Education Limited 2004 · Control of risk management activities · Project schedule control · Project resource control · Project budget control

OHT 20.3 Galin, SQA from theory to implementation © Pearson Education Limited 2004 · Human resources · Development and testing facilities · Purchase of COTS software · Purchase of hardware · Payments to subcontractors.

OHT 20.4 Galin, SQA from theory to implementation © Pearson Education Limited 2004 *Lists of software risk items by category and their planned solution dates *Lists of exceptions of software risk items – overrun solution dates

OHT 20.5 Galin, SQA from theory to implementation © Pearson Education Limited 2004 *Classified lists of delayed activities. *Classified lists of delays of critical activities – delays that can affect the project’s completion date. *Updated activity schedules, according to progress reports and correction measures. *Classified lists of delayed milestones. *Updated milestones schedules, according to progress reports and applied correction measures.

OHT 20.6 Galin, SQA from theory to implementation © Pearson Education Limited 2004 *Project resources allocation plan - for activities and software modules - for teams and development units - for designated time periods, etc. *Project resources utilization – as specified above *Project resources utilization exceptions – as specified above *Updated resource allocation plans generated according to progress reports and reaction measures applied

OHT 20.7 Galin, SQA from theory to implementation © Pearson Education Limited 2004 *Project budget plans - for activity and software module - for teams and development units - for designated time periods, etc. *Project budget utilization reports — as specified above *Project budget utilization deviations – by period or accumulated – as specified above *Updated budget plans generated according to progress reports ports and correction measures