Software Quality SEII-Lecture 15

Slides:



Advertisements
Similar presentations
User Interfaces 4 BTECH: IT WIKI PAGE:
Advertisements

These slides are designed to accompany Software Engineering: A Practitioner’s Approach, 6/e (McGraw-Hill 2005). Slides copyright 2005 by Roger Pressman.1.
Risk Analysis for Testing Based on Chapter 9 of Text Based on the article “ A Test Manager’s Guide to Risks Analysis and Management” by Rex Black published.
軟工一 吳彥諄. * Scrum overview * What happened to the software * What is the quality attribute * ACRUM * Q&A.
Overview Lesson 10,11 - Software Quality Assurance
Design Modeling for Web Applications
R&D SDM 1 Metrics How to measure and assess software engineering? 2009 Theo Schouten.
1 These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 5/e and are provided with permission by.
1 SOFTWARE QUALITY ASSURANCE Basic Principles. 2 Requirements System Design Detailed Design Implementation Installation & Testing Maintenance SW Quality:
CS 325: Software Engineering March 26, 2015 Software Quality Assurance Software Metrics Defect Injection Software Quality Lifecycle Measuring Progress.
Chapter#7.  Part 1: Quality Management ◦ ƒ Understand the definition of quality and the different methodologies to provide quality ◦ ƒ Know quality management.
Planning and Tracking Software Quality Yordan Dimitrov Telerik Corporation
SOFTWARE QUALITY ASSURANCE SOFTWARE QUALITY ASSURANCE  DEFINITIONS OF SQA  SOFTWARE STANDARDS  Process Quality Assurance  Product Quality Assurance.
Non-functional requirements
CSEB233 Fundamentals of Software Engineering Module 7: Software Quality Management Badariah Solemon 2010.
Handouts Software Testing and Quality Assurance Theory and Practice Chapter 17 Software Quality
Chapter 1, SE (Pressman) and Chapter 1, IT Project Management (Schwalbe) Software/ software engineering IT project failure / investment Project / program.
Software Project Management Fifth Edition
Managing Software Quality
COURSE TITLE: 1 Software Quality Assurance. Course Aims Introduction to software quality assurance. Software testing terminology. Role and responsibility.
What is Software Engineering? the application of a systematic, disciplined, quantifiable approach to the development, operation, and maintenance of software”
 The software systems must do what they are supposed to do. “do the right things”  They must perform these specific tasks correctly or satisfactorily.
Planning and Tracking Software Quality.  What Is Software Quality?  Causes of Software Defects  What is Quality Assurance?  Improving the Software.
Sept - Dec w1d11 Beyond Accuracy: What Data Quality Means to Data Consumers CMPT 455/826 - Week 1, Day 1 (based on R.Y. Wang & D.M. Strong)
Based on D. Galin, and R. Patton.  According to D. Galin  Software quality assurance is:  A systematic, planned set of actions necessary to provide.
CS3100 Software Project Management Week 26 - Quality Dr Tracy Hall.
1 Software Quality CIS 375 Bruce R. Maxim UM-Dearborn.
Software Software is omnipresent in the lives of billions of human beings. Software is an important component of the emerging knowledge based service.
Software Quality Engineering Chapters 1-3 Overview, Software Quality and Quality Assurance.
Copyright © Jerzy R. Nawrocki ISO 9126 and Non-functional Requirements Requirements.
Patterns, effective design patterns Describing patterns Types of patterns – Architecture, data, component, interface design, and webapp patterns – Creational,
Click to edit Master subtitle style USABILITY and USER INTERFACE DESIGN Application.
Software Quality : The Elusive Target
University of Palestine software engineering department Testing of Software Systems Testing throughout the software life cycle instructor: Tasneem.
Software Methods Mö/ slide 1 Methods and Techniques of Software Quality Management ICEL Quality Management Systems: Methods and Techniques of Software.
OHT 1.1 Galin, SQA from theory to implementation © Pearson Education Limited 2004 The uniqueness of software quality assurance The environments for which.
About Quality Pre paired By: Muhammad Azhar. Scope What is Quality Quality Attributes Conclusion on software Quality Quality Concepts Quality Costs.
Chapter : 14 Quality Concepts
CS551 - Lecture 5 1 CS551 Lecture 5: Quality Attributes Yugi Lee FH #555 (816)
Software Testing for Intelligent Robots Justin Peckner Maria Velasquez November 13, 2012.
CSSE Software Engineering Process and Practice Lecture 5 Q UALITY A SSURANCE.
Chapter 2 Object-Oriented Paradigm Overview. Getting Acquainted with the Class Project Read the requirements specification carefully Make note of any.
1 These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 5/e and are provided with permission by.
Requirements Management with Use Cases Module 2: Introduction to RMUC Requirements Management with Use Cases Module 2: Introduction to RMUC.
Class-oriented metrics – Weighted methods per class, depth of the inheritance tree, number of children, coupling, response for class, lack of cohesion.
Project Management Quality Management. Introduction Project planning Gantt chart and WBS Project planning Network analysis I Project planning Network.
These slides are designed to accompany Software Engineering: A Practitioner’s Approach, 7/e (McGraw-Hill, 2009). Slides copyright 2009 by Roger Pressman.
Non Functional Testing. Contents Introduction – Security Testing Why Security Test ? Security Testing Basic Concepts Security requirements - Top 5 Non-Functional.
 System Requirement Specification and System Planning.
ISQB Software Testing Section Meeting 10 Dec 2012.
Chapter 2 Object-Oriented Paradigm Overview
TOTAL QUALITY MANAGEMENT
Software Verification and Validation
SEVERITY & PRIORITY RELATIONSHIP
Source & Courtesy: Doc. S. Dapkūnas
Software Quality Assurance Software Quality Factor
Software testing
Quality Exercise 2 Instructions
Lecture 15: Technical Metrics
Quality Exercise 2 Instructions
Quality Exercise 2 Instructions
Software Quality Engineering CS- 449
Introduction to Software Testing
Charakteristiky kvality
and Jose-Norberto Mazón University of Alicante
Software Quality Assurance Lecture 3
Software Quality Assurance 2015
ISO/IEC Systems and software Quality Requirements and Evaluation
Tomaž Špeh SURS TF SERV, Luxembourg,
Presentation transcript:

Software Quality SEII-Lecture 15 Dr. Muzafar Khan Assistant Professor Department of Computer Science CIIT, Islamabad.

Recap WebApp quality Content quality Design goals of WebApp Usability, functionality, reliability, efficiency, maintainability, security, availability, scalability, time-to-market Content quality Scope, depth, background, authority, currency, stability, Design goals of WebApp Simplicity, consistency, identity, robustness, navigability, visual appeal, compatibility WebApp design Interface, aesthetic, navigation, and architecture design

Quality Multi-aspects concept Transcendental view User view Difficult to explicitly define but easy to recognize User view End user’s specific goals Manufacturer’s view Product specification Product view Inherent characteristics Value-based view cost

Software Quality “An effective software process applied in a manner that creates a useful product that provides measurable value for those who produce it and those who use it.” Effective software process Infrastructure Check and balance Change control and technical reviews Useful product Explicit and implicit requirements Reliable, error-free Add value for producer and user of a software product Less maintenance effort Efficient business process

Garvin’s Quality Dimensions Performance quality Feature quality Reliability Conformance Durability Serviceability Aesthetics Perception “soft” look of quality

McCall’s Quality Factors Figure source: Software Engineering: A Practitioner’s Approach, R. S. Pressman, 7th ed., p. 403

ISO 9126 Quality Factors [1/2] Functionality Suitability Accuracy Interoperability Compliance security Reliability Maturity Fault tolerance recoverability Usability Understandability Learnability operability

ISO 9126 Quality Factors [2/2] Efficiency Time behavior Resource behavior Maintainability Analyzability Changeability Stability Testability Portability Adaptability Installability Conformance Replaceability

Targeted Quality Factors [1/4] Intuitiveness Is the interface layout conducive to easy understanding? Are interface operations easy to locate and initiate? Does the interface use a recognizable metaphor? Is input specified to economize keystrokes or mouse clicks? Does the interface follow the three golden rules? Do aesthetics aid in understanding and usage?

Targeted Quality Factors [2/4] Efficiency Information and operations can be located and initiated Does the interface layout and style allow a user to locate operations and information efficiently? Can a sequence of operations (or data input) be performed with an economy of motion? Are output data or content presented so that it is understood immediately? Have hierarchical operations been organized in a way that minimizes the depth to which a user must navigate to get something done?

Targeted Quality Factors [3/4] Robustness Will the software recognize the error if data at or just outside prescribed boundaries is input? More importantly, will the software continue to operate without failure or degradation? Will the interface recognize common cognitive or manipulative mistakes and explicitly guide the user back on the right track? Does the interface provide useful diagnosis and guidance when an error condition (associated with software functionality) is uncovered?

Targeted Quality Factors [4/4] Richness Can the interface be customized to the specific needs of a user? Does the interface provide a macro capability that enables a user to identify a sequence of common operations with a single action or command?

Software Quality Dilemma [1/3] “Good enough” software Known bugs Time to market Short cut Different domains Legal penalties Cost of quality Cost of conformance and nonconformance Prevention cost Plan and coordinate activities Technical activities Test planning costs Training activities

Software Quality Dilemma [2/3] Cost of quality Appraisal cost Technical reviews Data collection and metrics evaluation Testing and debugging Failure cost Internal failure cost External failure cost

Software Quality Dilemma [3/3] Risks Low quality software increases risks for user and developer Sometimes very serious risks Negligence and liability Customer/user VS developer Quality and security Secure data Impact of management actions Cost and schedule estimates

Relative Cost of Correcting Errors Boehm and Basili (2001) Figure source: Software Engineering: A Practitioner’s Approach, R. S. Pressman, 7th ed., p. 409

Cost of downtime Standish group study in 2008 Figure source: IT Project Management, K. Schwalbe, 6th ed., p. 258

Achieving Software Quality Software engineering methods Project management techniques Quality control Quality assurance

Summary Multi-aspects concept Software quality Software quality models Transcendental view, user view, manufacturer’s view, product view, value-based view Software quality Effective software process, useful product, add value for producer and user of a software product Software quality models Garvin’s quality dimensions, McCall’s quality factors, ISO 9126 quality model Software quality dilemma Achieving software quality