Software Engineering Software quality. Software quality characteristics:  External: user is aware of. User cares about.  Internal: programmer is aware.

Slides:

Advertisements

Similar presentations

Object Oriented Analysis And Design-IT0207 iiI Semester

Advertisements

Software Quality Seung Yang CS 525 Software Engineering II Dr. Sheldon X. Liang.

Software Engineering 1. Software development – the grand view 2. Requirements engineering.

Chapter 17 I.Omaima Al-Matrafi

Unit 251 Implementation and Integration Implementation Unit Testing Integration Integration Approaches.

© Prentice Hall CHAPTER 9 Application Development by Information Systems Professionals.

SE 555 Software Requirements & Specification Requirements Quality Attributes.

Software Engineering For Beginners. General Information Lecturer, Patricia O’Byrne, office K115A. –

1 Quality Assurance in Construction and Maintenance (Section 13.4 of Maintenance Text; Chapter 20 of Code Complete) Steve Chenoweth CSSE 375, Rose-Hulman.

1 SOFTWARE QUALITY ASSURANCE Basic Principles. 2 Requirements System Design Detailed Design Implementation Installation & Testing Maintenance SW Quality:

Software Engineering For Beginners. General Information Lecturer, Patricia O’Byrne. – Times: –See noticeboard outside.

Evaluating Architectures Quality control: rarely fun, but always necessary

 QUALITY ASSURANCE:  QA is defined as a procedure or set of procedures intended to ensure that a product or service under development (before work is.

Software Quality Assurance For Software Engineering && Architecture and Design.

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.

Introduction to Software Testing

Quality of Information systems. Quality Quality is the degree on which a product satifies the requirements Quality management requires that : that requirements.

Software Quality Chapter Software Quality  How can you tell if software has high quality?  How can we measure the quality of software?  How.

Systems Analysis and Design

Managing Software Quality

 The software systems must do what they are supposed to do. “do the right things”  They must perform these specific tasks correctly or satisfactorily.

Quality Assurance ITEC Rick Price. Expectations This course is not purely a lecture course – Classroom participation is a large portion – Everyone.

1 ICS 122: Software Specification and Quality Engineering Spring 2002Lecturers: H. Muccini and D. J. Richardson Lecture 13: Summary The three aspects:

Requirements specification Copyright, 2001 © Jerzy R. Nawrocki Quality Management.

Planning and Tracking Software Quality.  What Is Software Quality?  Causes of Software Defects  What is Quality Assurance?  Improving the Software.

Software Quality Applied throughout SW Engineering Process Encompasses ▫ Analysis, design, coding, testing, tools ▫ Formal tech reviews ▫ Multi-tiered.

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 Assurance SE Software Quality Assurance What is “quality”?

Planning and Tracking Software Quality Yordan Dimitrov Telerik Corporation Team Leader, Team Pulse, Team Leader, Team Pulse, Telerik Corporation,

Software Engineering Quality What is Quality? Quality software is software that satisfies a user’s requirements, whether that is explicit or implicit.

Basic of Software Testing Presented by The Smartpath Information System An ISO 9001:2008 Certified Organization

Question To know that quality has improved, it would be helpful to be able to measure quality. How can we measure quality?

Creator: ACSession No: 15 Slide No: 1Reviewer: SS CSE300Advanced Software EngineeringFebruary 2006 Software Quality Assurance & Software Quality Control.

Planning and Tracking Software Quality Yordan Dimitrov Telerik Corporation

12.1 Introduction Checklists are used as a technique to give status information in a formalized manner about all aspects of the test process. This chapter.

Jump to first page (C) 1998, Arun Lakhotia 1 Quality Assurance: Reviews and Walkthroughs Arun Lakhotia University of Southwestern Louisiana Po Box

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.

Code Complete Steve McConnell. 20. The Software-Quality Landscape.

Sylnovie Merchant, Ph.D. MIS 161 Spring 2005 MIS 161 Systems Development Life Cycle II Lecture 5: Testing User Documentation.

Quality Factors Chapter Three. Question To know that quality has improved, it would be helpful to be able to measure quality. How can we measure quality?

HND Computing Unit 8 Quality Management Prepared by S Hargrave

CS352 – Software Engineering II Lecture 17: SW Quality Assurance Landscape Slides by Mohammad El-Ramly, PhD.

Metrics "A science is as mature as its measurement tools."

Software Engineering Lecture 8: Quality Assurance.

Project Management Quality Management. Introduction Project planning Gantt chart and WBS Project planning Network analysis I Project planning Network.

by: Er. Manu Bansal Deptt of IT Software Quality Assurance.

 System Requirement Specification and System Planning.

TOTAL QUALITY MANAGEMENT

16CS202 & Software Engineering

Software Quality Control and Quality Assurance: Introduction

Rekayasa Perangkat Lunak Part-10

Rekayasa Perangkat Lunak

Software Quality Assurance

SEVERITY & PRIORITY RELATIONSHIP

Software Quality & Testing

McCall’s Quality Factors

Lecture 15: Technical Metrics

Software Quality Assurance

Software engineering.

مقدمه اي بر مهندسي نيازمنديها

Rekayasa Perangkat Lunak

Introduction to Software Testing

Thursday’s Lecture Chemistry Building Musspratt Lecture Theatre,

Software Quality Assurance

20. The Software-Quality Landscape

Software Testing COM /12/2019 Testing/Spring 98.

Software Quality Course 1 Introduction.

Presentation transcript:

Software Engineering Software quality

Software quality characteristics:  External: user is aware of. User cares about.  Internal: programmer is aware of. Programmer cares about. User does not care about.

Software quality External software quality: Correctness. Usability. Efficiency. Reliability. Integrity. Adaptability. Accuracy. Robustness.

Software quality Internal software quality: Maintainability. Flexibility. Portability. Reusability. Readability. Testability. Understandability.

Software quality External software quality – synergy: + = help each other - = mess with each other O = indifferent

Software quality Software quality programme: Explicit software quality goals. Explicit quality assurance activity. Testing strategy. Software engineering guidelines. Informal technical reviews. Formal technical reviews. External audits.

Software quality Development process for quality assurance: Change-control procedures. Measurability / measurement of results. Prototyping.

Software quality How to compare quality programmes:  Percentage of defects detected.  Cost of finding defects.  Cost of fixing defects. Typically, empirical analysis.

Software quality When to do quality assurance:  The earlier a defect is captured and fixed, the less expensive are its consequences.  Quality assurance should start together with the software project.

Software quality General principle of software quality: Improving quality reduces development costs.

Software quality Quality assurance plan checklist: Have you identified specific quality characteristics that are important to your project? Have you made others aware of the project's quality objectives? Have you differentiated between external and internal quality characteristics? Have you thought about the ways in which some characteristics might compete with or complement others?

Software quality Quality assurance plan checklist: Does your project call for the use of several different error-detection techniques suited to finding different kinds of errors? Does your project include a plan to take steps to assure software quality during each stage of software development? Is the quality measured in some way so that you can tell whether it is improving or degrading? Does management understand that quality assurance incurs additional costs up front in order to save costs later?