Project Management Quality Management

Introduction Project planning Gantt chart and WBS Project planning Network analysis I Project planning Network analysis II Plan Project planning Resource analysis Budgets and cost control Risk management Quality Project teams

Main Sources Pressman “Software Engineering” Gillies “Software Quality” Somerville “Software Engineering” Hughes and Cotterell “Software Project Management” Cadle and Yeates “Project Management for Information Systems”

Quality Management Three main concerns of Project Management

Quality Management Three main concerns of Project Management

Quality Management Three main concerns of Project Management

Quality Management Three main concerns of Project Management

Quality Guru’s J. M. Juran Fitness for purpose W. E. Deming Conformity and Dependability P. B. Crosby Zero Defects

What is Quality Quote from Crosby Taken from Pressman “Software Engineering” 4 th Edition

Garvin’s views on quality There is more than one ‘Stakeholder view’ of Quality: Transcendental View Manufacturing View Product-based View Value-based View User-based View

Views of Quality What view of quality might the following IS development ‘stakeholders’ have? IS Project Manager End User Customer/Project Sponsor Software Developer

Quality Management Quality Assurance Quality Control Total Quality Management

QA - Elements A QM Approach Effective SW Engineering Technologies Formal Technical Reviews Multi-tiered test strategy Change control in documentation Procedure to ensure compliance with SW development standards Measurement and reporting mechanisms

Quality in IS Reliability Maintainability Integrity Efficiency Usability Adaptability Interoperability Portability

Quality Control Control of Variation in Products Variance between design and implementation Consistent look and feel Quality Reviews Automatic Quality Control

Quality Control “The quality control process has its own set of procedures and reports that must be used during software development. These procedures should be straightforward and easily understood by the engineers developing the software.”

Feedback Control Loop

Measuring Quality What do we use to measure software quality? No direct measures – so we use Metrics Metrics are indicative of the characteristic we want to measure

A Good Metric Objective – not subjective Reliable – precise and repeatable Valid – should fit the characteristic Standard – unambiguous Comparable – with similar measures Economical – benefits match costs Useful – why is it being measured?

Measurable features Cyclomatic complexity Number of errors found MTTF Lines of code Fog rating Cohesion Function points

Quality in IS Reliability Correctness Maintainability Usability Complexity MTTF No of Errors Complexity Modularity Readability

Problems with Metrics Examples No of errors found = 0 Therefore software is correct and error free! TRUE or FALSE

Recording Statistics - Example

Quality Management Process TQM CMM ISO 9000

Total Quality Management Kaizen Continuous improvement Process is visible, repeatable, measurable Atarimae hinshitsu Optimise the effect of intangibles on process Kansei - “the five senses” Improve product by examining how it is used Miryokuteki hinshitsu Look for opportunities as an outgrowth

Capability Maturity Model Initial Repeatable Defined Managed Optimizing Undefined process and controls Standardised methods allowing repeatable processes Monitors and improves processes Advanced controls, metrics and feedback Uses metrics for optimization

ISO 9001 ISO 9001 Quality Systems – Model for Quality Assurance in Design, Development, Production, Installation and Servicing Describes the quality system used to support the development of a product

ISO ISO Guidelines for the application of ISO 9001 to the Development, Supply and Maintenance of Software.

ISO ISO Quality Management and Quality System Elements – Part 2. Provides guidelines for the servicing of software facilities – e.g. user support.

Costs of Quality Prevention Quality Planning, formal technical reviews Appraisal Inspection and testing Failure Rework, repair External Complaint handling, help line support, warranty work

Quality Manual - Example

Costs of Quality

IS Development Trends Introduction of Waterfall model To remove costly errors in process User centred development approaches To avoid errors in requirements Integrated development tools Reduce the errors from one stage to the next User friendly development tools Now anyone can program

Summary Many Different views required to get an overall picture of quality – Garvin Quality cannot be measured directly. IS Development requires certain metrics to aid measurement Processes and procedures must be in place in order to monitor and control quality – ISO 9000

Introduction Project planning Gantt chart and WBS Project planning Network analysis I Project planning Network analysis II Plan Project planning Resource analysis Risk management Quality Budgets and cost control Project teams