Quality Management

University of Paderborn Software Engineering Group
I.3 Quality Management
[Sommerville2004]
Quality Management System [ISO 9000]: The organizational structure, responsibilities, procedures, processes and resources for implementing quality management

Concerned with ensuring that the required level of quality is achieved in a software product. Involves defining appropriate quality standards and procedures and ensuring that these are followed. Should aim to develop a quality culture where quality is seen as everyones responsibility.
WS04/05 Software Quality Assurance I Introduction I-60
Dr. Holger Giese
Environment Characteristics

[Galin2004]
Being contracted Subjection to customersupplier relationship Requirement for teamwork Need for cooperation and coordination with other development teams Need for interfaces with other software systems Need to continue carrying out a project while the team changes Need to continue maintaining the software system for years
Dr. Holger Giese
WS04/05 Software Quality Assurance I Introduction
I-61
The Cost of Quality
Cost of Quality includes all costs incurred in the pursuit of quality or in performing quality related activities such as appraisal costs, failure costs and external failure costs. [Pressman2004]
The Quality Compromise:

We cannot wait for specifications to improve before paying attention to quality management. We must put quality management procedures into place to improve quality in spite of imperfect specification. [Sommerville2004]
Dr. Holger Giese
Scope of Quality Management
Quality management is particularly important for large, complex systems. The quality documentation is a record of progress and supports continuity of development as the development team changes. For smaller systems, quality management needs less documentation and should focus on establishing a quality culture.
[Sommerville2004]
Dr. Holger Giese
Quality Management and Software Development

Software development process D1 D2 D3 D4
[Sommerville2004]
D5
Quality management process
Standards and procedures
Quality plan
Quality review reports
Dr. Holger Giese
I-64
Quality Management Activities

(1) Quality assurance
Establish organisational procedures and standards for quality. Select applicable procedures and standards for a particular project and modify these as required. Ensure that procedures and standards are followed by the software development team.
(2) Quality planning
(3) Quality control
Quality management should be separate from project management to ensure independence.

[Sommerville2004]
Dr. Holger Giese
(1) Quality Assurance

Quality Assurance [ISO 9000]: All those planned and systematic actions necessary to provide adequate confidence that a product or service will satisfy requirements for quality Software quality assurance [IEEE]: 1. A planned and systematic pattern of all actions necessary to provide adequate confidence that an item or product conforms to established technical requirements. 2. A set of activities designed to evaluate the process by which the products are developed or manufactured. Contrast with: quality control.
Dr. Holger Giese
I-66
Quality Assurance
Software quality assurance is [Galin2004] : A systematic, planned set of actions necessary to provide adequate confidence that the software development process or the maintenance process of a software system product conforms to established functional technical requirements as well as with the managerial requirements of keeping the schedule and operating within the budgetary confines.
Quality assurance consists of the auditing and reporting functions of management [Pressman2004]
Dr. Holger Giese
I-67
(2) Quality Planning
Quality planning is the process of assessing the requirements of the procedure and of the product and the context in which these must be observed. Quality assurance plan is the central aid for planning and checking the quality assurance. [Pressman2004]
Dr. Holger Giese
Quality Assurance Plan
[Sommerville2004]
A quality assurance plan sets out the desired product qualities and how these are assessed and defines the most significant quality attributes. The quality assurance plan should define the quality assessment process. It should set out which organisational standards should be applied and, where necessary, define new standards to be used.
Dr. Holger Giese
I-69
Quality Assurance Plans
[Sommerville2004]
Quality assurance plan structure:

Product introduction Product plans Process descriptions Quality goals Risks and risk management
Quality assurance plans should be

short, succinct (If they are too long, no-one will read them)
Dr. Holger Giese
I-70
Example: SQA Plan

Purpose of Plan References Management
organization structure, SQA tasks, their placement in the process roles and responsibilities related to product quality
Documentation
project documents, models, technical documents, user documents.
Standards, Practices and Conventions Reviews and Audits Test
test plan and procedure
Problem Reporting and Corrective action
Tools, Techniques and Methodologies Code Control Media Control Supplier control Records Collection, Maintenance and Retention Training Risk Management
[IEEE_Std_730-1998, Pressman2004]
I-71
Dr. Holger Giese
22
(3) Quality Control

Quality Control [ISO 9000]: The operational techniques and activities that are used to fulfil requirements for quality
Quality Control is the series of inspections, reviews and tests used throughout the development cycle to ensure that each work product meets the requirements placed upon it.
[Pressman2004]
Dr. Holger Giese WS04/05 Software Quality Assurance I Introduction I-72
Quality Control
[Sommerville2004]
This involves checking the software development process to ensure that procedures and standards are being followed. There are two approaches to quality control

Quality reviews; Automated software assessment and software measurement.
Dr. Holger Giese
I-73
Quality Control
Objective: minimize the produced defects increase the product quality Implementation approaches: Fully automated Entirely manual Combination of automated tools and human interactions
Quality Control
Quality control includes a feedback loop to the process: provide management with the necessary data about product quality. gain the insight and confidence of product quality Two types of quality control: Quality design: the characteristics that designers specify for an item (includes: requirements, specifications, and the design of the system). Quality of conformance: the degree to which the design specification are followed. It focuses on implementation based on the design. [Pressman2004]
Quality Assurance System
Quality assurance system is the organizational structure, responsibilities, procedures, processes and resources for implementing quality management.
[Pressman2004]
Dr. Holger Giese
I-76
Process and Product Quality

The quality of a developed product is influenced by the quality of the production process. This is important in software development as some product quality attributes are hard to assess. However, there is a very complex and poorly understood relationship between software processes and product quality.
[Sommerville2004]
Process-based Quality

[Sommerville2004]
There is a straightforward link between process and product in manufactured goods. More complex for software because:

The application of individual skills and experience is particularly important in software development; External factors such as the novelty of an application or the need for an accelerated development schedule may impair product quality.
Care must be taken not to impose inappropriate process standards - these could reduce rather than improve the product quality.
Dr. Holger Giese
Process-based quality
[Sommerville2004]
Dr. Holger Giese
I-79
Practical Process Quality
[Sommerville2004]
Define process standards such as how reviews should be conducted, configuration management, etc. Monitor the development process to ensure that standards are being followed. Report on the process to project management and software procurer. Dont use inappropriate practices simply because standards have been established.
Dr. Holger Giese
I.4 Components of a SQA System

(1) Pre-project components (2) Software project life cycle components (3) Infrastructure components for error prevention and improvements (4) Management SQA components (5) SQA standards, system certification and assessment components (6) Organizing for SQA the human components and considerations guiding construction of organizations SQA system
(1) Pre-project Components

Pre-project Contract reviews Development and quality plans (see Chapter II and III)
Dr. Holger Giese
I-82
(2) Project Life Cycle Components

Development Reviews Expert opinions Software testing Assurance of the quality of external participants work Maintenance Software maintenance components (see Chapter II and III)
(3) Infrastructure Components

Procedures and work instruction Templates and checklists Staff training, retraining and certification Preventive and corrective actions Configuration management Documentation control
(see Chapter IV)
Dr. Holger Giese
I-84
(4) Management SQA Components

Project progress control Software quality metrics Software quality costs
(see Chapter V)
Dr. Holger Giese
I-85
(5) Standards, Certification, Assessment

Project process standards Quality management standards
Objectives: Utilization of international professional knowledge Improvement of coordination with other organizations quality systems Objective professional evaluation and measurement of the organizations SQA achievement (see Chapter VI)
(6) Organizing for SQA

Managements role in SQA The SQA unit SQA trusties SQA committees SQA forums
(see Chapter I.5)
Dr. Holger Giese
I-87
The Software Quality Shrine

(1) ct SQ e j o r Pre-p ts onen p m A co
Project Development plan and Quality Plan Contract review
[Galin2004]
(2) Project Life Cycle SQA components

SQA of External Participants
Formal Design Reviews
(3) Quality Infrastructure components

Procedures Supporting Devices Training Instruction Preventive Actions
Configuration Management
(4) Quality Management

Project Progress Control Software Quality Metrics Software Quality Costs
Software Maintenance
Software Testing
Experts Opinion
Peer Reviews
(5) Standards
Management
Documentation Control
Quality
Standards
Project Process Standards
(6) Organizational Base Human components

Management SQA Unit SQA Trustees SQA Committees SQA Forums
Dr. Holger Giese
I-88
I.5 Organizing for SQA

(1) ts onen p m o QA c S t c ro j e Pre-p
Contract review Project Development plan and Quality Plan
[Galin2004]
(2) Project Life Cycle SQA components

Formal Design Reviews
(3) Quality Infrastructure components

Procedures Supporting Devices Training Instruction Preventive Actions
Configuration Management
(4) Quality Management

Project Progress Control Software Quality Metrics Software Quality Costs
(5) Standards
Management
SQA of External Participants
a) a) b) b) c) c) d) d) e) e)
Software Maintenance
Management Management SQAUnit Unit SQA SQATrustees Trustees SQA SQACommittees Committees SQA SQAForums Forums SQA
Software Testing
Experts Opinion
Peer Reviews
Documentation Control
Quality
Standards
Project Process Standards
(6) Organizational Base Human components

Management SQA Unit SQA Trustees SQA Committees SQA Forums
Dr. Holger Giese
I-89
Management
Exec. Exec . Exec. Executive responsible for software quality
The SQA framework

SQA unit
Other Departments
Software Testing Department
Software Development and Maintenance Department
SQA Committees
Legend Line of authority line for SQA issues Flow of Forum s recommendations line
SQA Forums
[Galin2004]
Software Testing Teams
Software Development Teams
SQA Trustees
Dr. Holger Giese
I-90
The SQA Framework: Participants

Managers
Testers
Top management executives, especially the executive in charge of SQA Software development and maintenance department managers Software testing department managers Project managers and team leaders of development and maintenance projects Leaders of software testing teams
Members of software testing teams
SQA professionals and interested practitioners

SQA trustees SQA committee members SQA forum members SQA unit team members
Dr. Holger Giese
I-91
a) Management
Overview: Top managements quality assurance activities Software quality policy The executive in charge of software quality Management review Department management responsibilities for quality assurance processes Project management responsibilities for quality assurance
TOP Management Responsibilities

[Galin2004]
Assure the quality of the Companys software products and software maintenance services. Communicate the importance of product and service quality in addition to customer satisfaction to employees. Assure full compliance with customer requirements. Ensure that SQA objectives are established and accomplished. Initiate planning and oversee implementation of changes to adapt the SQA system to changes related to the organization's clientele, competition and technology. Intervene directly to resolve of crisis situations and minimize damages. Ensure availability of resources required by SQA systems.
Dr. Holger Giese
SQ Policy Requirements
[Galin2004]
Quality policy refers to the basic aims and objectives of an organization regarding quality as stipulated by the management. [Pressman2004]
Conformity to the organization purpose and goals Commitment to: General software quality assurance concepts The quality standards adopted by the organization Allocate adequate resources for software quality assurance Continuous improvement of the organizations quality and productivity
Responsibilities (Executive in Charge)

Responsibility for preparation of an annual

SQA activities program and budget
Responsibility for preparation of SQA system

development plans
Overall control of implementation of the

annual SQA regular activities program and planned SQA development projects
Presentation and advocacy of SQA issues to

executive management
[Galin2004]
Dr. Holger Giese
I-95
Management Reviews
Def.: Management review is the name given to the periodic meeting convened to allow executives to obtain an overview of their organizations software quality issues. Typical items: Periodic performance reports, including quality metrics Customer satisfaction feedback Follow up reports for SQA annual regular activity program and SQA development projects Summary of special quality events related to customers, suppliers, subcontractors, etc. Review of significant findings of internal and external quality audits as well as special surveys Identification of new software quality risks and unsolved pre-existing risks Recommendations for software quality management improvements.
[Galin2004]
Management Reviews: Objectives
Assess achievement of quality objectives set

for the organizations software quality management system Initiate updates and improvements of the software quality management system and its objectives Outline directions for remedying major SQA deficiencies and software quality management problems. Allocate additional resources to the software quality management system. [Galin2004]
Dr. Holger Giese
Department Responsibilities (1/2)

The quality system-related responsibilities: Preparation of the departments annual SQA activities program and budget, based on recommended SQA unit program. Preparation of the departments SQA systems development plans, based on recommended SQA unit plan. Control of performance of the departments annual SQA activities program and development projects Presentation of the department's SQA issues to the executive in charge of software quality. [Galin2004]
Department Responsibilities (2/2)

Project-related responsibilities Control of compliance to quality assurance procedures in the department's units Detailed follow up of contract review results and proposal approvals Review of unit performance of planned review activities; approval of project documents and project phase completion Follow up of software tests; approval of projects software products. Follow up of progress of software development project schedules and budget deviations. Advise and support project mangers in resolving difficulties. Follow up of quality of maintenance services Detailed follow up of project risks and their solutions Follow up of project's compliance with customer requirements and customers satisfaction. Approval of large software change orders and significant deviations from project specifications.
[Galin2004]
Project Management Responsibilities

Professional hands-on tasks: Preparation of project and quality plans and their updates. Participation in joint customer-supplier committee Close follow up of project team staffing, including recruitment, training and instruction. Management tasks The follow up issues: Performance of review activities and the consequent corrections, including participating in some reviews. Software development and maintenance units performance with respect to development, integration and system test activities, corrections and regression tests and acceptance tests Software installation in customer sites and the running-in of the software system by the customer SQA training and instruction of project team members Schedules and resources allocated to project activities. Customer requests and satisfaction Evolving project development risks, application of solutions and control of results.
[Galin2004]
b) The SQA Unit

Overview: Activities Responsibilities Tasks performed by the head of the SQA unit SQA sub-unit tasks related to the project life cycle SQA sub-unit infrastructure operations tasks SQA sub-unit audit and certification tasks SQA sub-unit support tasks SQA sub-unit standards and procedures: Development and maintenance tasks SQA sub-unit information system tasks
Dr. Holger Giese
I-101
SQA Unit Tasks

[Pressman2004]
Quality assurance planning oversight, record keeping, analysis and reporting Participates in the development of the projects software process Reviews software engineering activities to verify compliance with the defined software process. Audits designated software work products to verify compliance with those defined as part of the software process. Ensures that deviations in software work and work products are documented and handled according to a document procedure. Records any noncompliance and reports to senior management.
Dr. Holger Giese
12
Unit: Organizational Structure

Head SQA Unit
[Galin2004]
SQA Operations
SQA Development and Maintenance
Project Life Cycle SQA SQA Infrastructure Operations
Internal and Certification SQA Audits SQA Support
SQA Standards and Procedures SQA Engineering
SQA Information Systems
Dr. Holger Giese
I-103
SQA Unit Head Tasks (1/2)

Planning tasks

Preparation of proposals for the Units annual activity program and budget Planning and updating the organizations software quality management system and recommended annual SQA activities programs for the software development and maintenance departments. Preparation of recommended SQA systems development plans for the software development and maintenance departments. Management of SQA team's activities Monitoring implementation of the SQA activity program Nomination of team members, SQA committee members and SQA trustees Preparation of special and periodic status and performance reports.
[Galin2004]
Management tasks

Dr. Holger Giese
I-104
SQA Unit Head Tasks (2/2)

Contacts with customers and other external bodies and the executive in charge of software quality

Serving as the customers address for software quality issues of software products and services supplied Representation of the organization before external bodies regarding software quality issues Drafting the management review reports Raising SQA organizational issues and preparing requested material for top management's consideration Participation in project joint committees Participation in formal design reviews Review and approval of deviations from specifications Consultation to project managers and team leaders Participation in SQA committees and forums
[Galin2004]
SQA professional activities

Dr. Holger Giese
I-105
Life Cycle Tasks (Sub-Units)

Project life cycle control tasks
Follow up of development and maintenance teams compliance with SQA procedures and work instructions Approval or recommendation of software products (design reports and code). Monitoring delivery of software maintenance services to internal and external customers Monitoring customer satisfaction (surveys, etc.) and maintaining contact with customers SQA representatives Participation tasks participation in: Contract reviews Preparation and updating of project development and project quality plans Formal design reviews Subcontractors formal design reviews Software testing, including customer acceptance tests Software acceptance tests of subcontractors software products Installation of new software products
[Galin2004]
Infrastructure Tasks (Sub-Units)

Publication of updated versions of procedures, work instructions, templates, checklists, etc., with their circulation. Training and instruction to new and current staff and SQA trustees regarding SQA procedures, work instructions, new and revised procedures, development tools and methods, etc. Monitoring and supporting implementation of new and revised SQA procedures Follow up of staff certification activities Proposal of subjects requiring preventive and corrective actions Follow up of configuration management activities Follow up of compliance with documentation procedures and work instructions
[Galin2004]
Types of Audits (in or by SW Org)

Internal audits Audits of subcontractors and suppliers to evaluate their SQA systems External audits performed by certification bodies External audits performed by customers who wish to evaluate the SQA system prior to accepting the organization as a supplier
[Galin2004]
Dr. Holger Giese
Audits and Certifications (Sub-Units)

Preparation of annual programs for SQA audits Performance of SQA audits Follow up of corrections Preparation of periodic summary reports Collection of data on the performance of the audited organization from internal and external sources Periodic evaluation of the audited organization Coordination of the external audit's contents and schedule Preparation of documents as specified by external auditors Instruction of the audited teams and performance of preparations for external audits Participation in the audit
[Galin2004]
Dr. Holger Giese
I-109
Support Tasks (Sub-Units)

Preparation of project development plans and project quality plans Staffing review teams Choice of development methodologies and tools that reflect the accumulated failure experience Choice of measures to solve identified software development risks Choice of measures to solve schedule delays and budget overruns Choice of SQA metrics and software costs components Use of SQA information systems
[Galin2004]
Dr. Holger Giese
Standard and Procedures (Sub-Units)

Prepare an annual program for development of new procedures and procedure updates Responsibility for development of new procedures and procedure updates, including participation in appropriate committees and forums Follow up of developments and changes in SQA and software engineering standards; introduction of additional relevant procedures and changes Initiation of updates and adaptations of procedures in response to changes in professional standards, including adoption or deletion of standards applied by the organization.
[Galin2004]
Dr. Holger Giese
I-111
Engineering (Sub-Units)

Testing quality and productivity aspects with respect to new development tools and new versions of currently used development tools Evaluation of quality and productivity of new and improved development and maintenance methods Development of solutions to difficulties confronted in application of currently used software development tools and methods Development of methods for measuring software quality and team productivity Provision of technological support to CAB committees during analysis of failures and formulation of solutions
[Galin2004]
Information Systems (Sub-Units)
Development of SQA information systems for software development and maintenance units for: Collection of activity data. Processing of information delivered by the units: periodic reports, lists, exception reports, queries and estimates of software quality metrics and software quality costs. Updating of SQA information systems Development and maintenance of the organization's SQA Intranet/Internet site
[Galin2004]
I-113
Dr. Holger Giese
SQA Unit Plan

[Pressman2004]
Evaluations to be performed Audits and reviews to be performed Standards that are applicable to the project Procedures for error reporting and tracking Documents to be produced by the SQA group Amount of feedback provided to software project team
Dr. Holger Giese
I-114
c) SQA Trustees
Unit-related tasks:

Support their colleagues' attempts to solve difficulties in the implementation of SQA procedures and work instructions Help their unit manager in performing his or her SQA tasks Promote compliance and monitor implementation of SQA procedures and work instructions by colleagues Report substantial and systematic non-compliance events to the SQA unit Report severe software quality failures to the SQA unit Initiate changes and updates of organization-wide SQA procedures and work instructions Initiate organization-wide improvements of development and maintenance processes and applications for solutions to recurrent failures observed in their units Identify organization-wide SQA training needs and propose an appropriate training or instruction program
[Galin2004]
Organization-related tasks
Dr. Holger Giese
I-115
d) SQA Committees
Permanent committees commonly deal with: SCC (software change control), CA (corrective actions), Procedures, Development of method, tools and quality metrics. Ad-hoc committees commonly deal with specific cases: Updates of a specific procedure, Analysis and solution of a software failure, Elaboration of software metrics for a targeted process or product, Updating software quality costs, Data collection methods for a specific issue.
[Galin2004]
e) SQA Forums
SQA forums typically focus on: SQA procedures improvements and implementation Quality metrics Corrective actions analysis of failure and success cases Quality system issues development and implementation of new tools Quality line management problems daily operational software quality problems Members of an open forum may include: SQA unit members SQA trustees Software development and maintenance staff SQA and software engineering consultants/experts Customer representatives
[Galin2004]
Other Relevant Structures
[Pressman2004]
Requirements Control Board

All
requirement changes must be formally reviewed and approved design changes must be formally reviewed and approved
Software Control Board

All
Interface Control Board
Dr. Holger Giese
I-118
I.6 Discussion & Summary
General quality definitions of quality are not sufficient in practice. Thus, software quality is described by specific quality models which determine the causal relationship from intangible quality views to tangible software measures [ISO/IEC 9126] We cannot wait for specifications to improve before paying attention to quality management. We must put quality management procedures into place to improve quality in spite of imperfect specification. Quality management activities consist of quality assurance, quality planning, and quality control.
Dr. Holger Giese
I-119
Discussion & Summary
The quality of a developed product is influenced by the quality of the production process. This is important in software development as some product quality attributes are hard to assess. However, there is a very complex and poorly understood relationship between software processes and product quality. The main instrument for quality is the software quality assurance system. Components of a software quality assurance system for the pre-project phase, each life cycle phase, management, infrastructure, standardization, and organization exist. Organizing for SQA involves mainly the management, SQA Unit, SQA Trustees, SQA Committees, and SQA Forums
Dr. Holger Giese
I.7 Bibliography (1/4)

[Basili&Rombach1988] V.R. Basili, H. D. Rombach, "The TAME Project: Towards Improvement-Oriented Software Environments," IEEE Transactions on Software Engineering, vol.SE-14, no.6, June 1988, pp.758-773 [Glass1992] R.~L. Glass, Building Quality Software. Englewood Cliffs, NJ, USA: Prentice Hall, 1992. [Galin2004] D. Galin, Software Quality Assurance: From theory to implementation. Harlow, England: Pearson Addison Wesley, 2004. [Horch1996] J.~W. Horch, Practical guide to software quality management. Boston, USA: Artech House, first ed., 1996. [Horch2003] J.~W. Horch, Practical guide to software quality management. Boston, USA: Artech House, second ed., 2003.
Dr. Holger Giese
I-121
I.7 Bibliography (2/4)

[ISO9000] [ISO9001] [ISO 9004] [ISO 9000addon] ISO 9000:2000, Quality management systems Fundamentals and vocabulary ISO 9001:2000, Quality management systems Requirements ISO 9004:2000, Quality management systems Guidelines for performance improvements "ISO 9000 Introduction and Support Package" guidance documents from ISO/TC 176 SC2: N524 - Guidance on ISO 9001:2000 Sub-clause 1.2 'Application' N525 - Guidance on the Documentation Requirements of ISO 9001:2000 N526 - Guide to the Terminology used in ISO 9001:2000 and ISO 9004:2000 N544 - Guidance on the Concept and Use of the Process Approach for management systems N630 - Guidance on Outsourced Processes
Dr. Holger Giese
I-122
Bibliography (3/4)
[ISO9000-2002] ISO Handbook:2002, ISO 9001:2000 for small businesses What to do, Advice from ISO/TC 176 [ISO/IEC 9126] Information technology - Software Product Evaluation - Quality characteristics and guidelines for their use - 1991. http://www.cse.dcu.ie/essiscope/sm2/9126ref.html ISO/IEC 9126-1:2001: Software engineering -- Product quality -- Part 1: Quality model ISO/IEC TR 9126-2:2003: Software engineering -- Product quality -Part 2: External metrics ISO/IEC TR 9126-3:2003: Software engineering -- Product quality -Part 3: Internal metrics ISO/IEC TR 9126-4:2004: Software engineering -- Product quality -Part 4: Quality in use metrics [IEEE_Std_610.12-1990] Standards Coordinating Committee of the IEEE Computer Society, The Institute of Electrical and Electronics Engineers, Inc. 345 East 47th Street, New York, NY 10017-2394, USA. IEEE Std 610.121990, IEEE Standard Glossary of Software Engineering Terminology. (Revision and redesignation of IEEE Std 729-1983). [IEEE_Std_730-1998] Standards Coordinating Committee of the IEEE Computer Society, The Institute of Electrical and Electronics Engineers, Inc. 345 East 47th Street, New York, NY 10017-2394, USA. IEEE Std 730-1998, IEEE Standard fro Software Quality Assurance Plans.
Dr. Holger Giese
Bibliography (4/4)
Michael R. Lyu, editor. Handbook of software reliability engineering. IEEE Computer Society Press, Los Alamitos, Calif., 1996. [McCall +1977] J.A. McCall, P.K. Richards, and G.F. Walters, Factors in Software Quality, Vol. 1, AD/A-049-014/015/055, Nat'l Tech. Information Service, Springfield, Va., 1977. [McConnell 1996] Steve McConnell. Software Quality at Top Speed. Software Development. August 1996 [Pressman2004] Roger Pressman. Software Engineering: A Practitioner's Approach. McGraw-Hill, 6 ed., 2004. [Sommerville2004] Ian Sommerville. Software Engineering. Addison Wesley. 7 ed., 2004. [Schulmeyer1992] G. G. Schulmeyer, ed., Handbook of software quality assurance. Van Nostrand Reinhold, 1992. [Lyu1996]
Dr. Holger Giese
I-124

Quality Management

Diunggah oleh

Informasi Dokumen

Deskripsi Asli:

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

Quality Management

Diunggah oleh

Hak Cipta:

Format Tersedia

University of Paderborn Software Engineering Group

I.3 Quality Management

Dr. Holger Giese

University of Paderborn Software Engineering Group

Dr. Holger Giese

WS04/05 Software Quality Assurance I Introduction

University of Paderborn Software Engineering Group

The Cost of Quality

The Quality Compromise:

Dr. Holger Giese

University of Paderborn Software Engineering Group

Scope of Quality Management

Dr. Holger Giese

University of Paderborn Software Engineering Group