Software Engineering Modern Approaches Eric Braude and Michael Bernstein 1.

Slides:



Advertisements
Similar presentations
1.Quality-“a characteristic or attribute of something.” As an attribute of an item, quality refers to measurable characteristics— things we are able to.
Advertisements

Quality Management COMP 3663 Daniel L. Silver.
Software Engineering CSE470: Process 15 Software Engineering Phases Definition: What? Development: How? Maintenance: Managing change Umbrella Activities:
Chapter 4 Quality Assurance in Context
Software Engineering Process
Chapter 7: Key Process Areas for Level 2: Repeatable - Arvind Kabir Yateesh.
These slides are designed to accompany Software Engineering: A Practitioner’s Approach, 6/e (McGraw-Hill 2005). Slides copyright 2005 by Roger Pressman.1.
Stepan Potiyenko ISS Sr.SW Developer.
Software Engineering Modern Approaches Eric Braude and Michael Bernstein 1.
Software Engineering Modern Approaches Eric Braude and Michael Bernstein 1.
Overview Lesson 10,11 - Software Quality Assurance
Software Quality Metrics
SE 555 Software Requirements & Specification Beyond Requirements Based on Weigers Chapter17.
OHT 7.1 Galin, SQA from theory to implementation © Pearson Education Limited 2004 Software development methodologies: - The software development life cycle.
OHT 7.1 Galin, SQA from theory to implementation © Pearson Education Limited 2004 Software development methodologies: - The software development life cycle.
1 REQUIREMENTS ENGINEERING and SYSTEMS ANALYSIS Elements and Definitions.
1 Software Testing and Quality Assurance Lecture 1 Software Verification & Validation.
Software Process and Product Metrics
Software Verification and Validation (V&V) By Roger U. Fujii Presented by Donovan Faustino.
Process: A Generic View
Quality of Information systems. Quality Quality is the degree on which a product satifies the requirements Quality management requires that : that requirements.
S T A M © 2000, KPA Ltd. Software Trouble Assessment Matrix Software Trouble Assessment Matrix *This presentation is extracted from SOFTWARE PROCESS QUALITY:
Introduction to Software Quality Assurance (SQA)
Software Quality Assurance By: Faraz Ahmed. Contents 0 Course Outline 0 Marks Distribution 0 Fundamentals of Quality Assurance 0 Discussion 0 Reference.
Software Engineering Modern Approaches
Dillon: CSE470: SE, Process1 Software Engineering Phases l Definition: What? l Development: How? l Maintenance: Managing change l Umbrella Activities:
N By: Md Rezaul Huda Reza n
Software Engineering Modern Approaches
Cybersecurity: Engineering a Secure Information Technology Organization, 1st Edition Chapter 7 Software Supporting Processes and Software Reuse.
Software Quality Assurance Activities
Software Engineering Modern Approaches
Plan project Integrate & test system Analyze requirements Design Maintain Test unitsImplement Software Engineering Roadmap: Chapter 1 Focus Identify corpor-
S Q A.
Capability Maturity Models Software Engineering Institute (supported by DoD) The problems of software development are mainly caused by poor process management.
Software Quality Assurance SE Software Quality Assurance What is “quality”?
Software Project Management Lecture # 10. Outline Quality Management (chapter 26)  What is quality?  Meaning of Quality in Various Context  Some quality.
Lecture 3 Software Engineering Models (Cont.)
Software Engineering Modern Approaches Eric Braude and Michael Bernstein 1.
Software Project Management Lecture # 3. Outline Chapter 22- “Metrics for Process & Projects”  Measurement  Measures  Metrics  Software Metrics Process.
INFO 636 Software Engineering Process I Prof. Glenn Booker Week 9 – Quality Management 1INFO636 Week 9.
KS3 Phase4 Client Server Monitoring System October 1, 2008 by Stephen, Seema, Kam, Shpetim.
This chapter is extracted from Sommerville’s slides. Textbook chapter
Lecture Introduction to Software Development SW Engg. Development Process Instructor :Muhammad Janas khan Thursday, September.
Chapter 3: Software Project Management Metrics
CSC 480 Software Engineering
Cmpe 589 Spring 2006 Lecture 2. Software Engineering Definition –A strategy for producing high quality software.
Software Engineering1  Verification: The software should conform to its specification  Validation: The software should do what the user really requires.
Software Engineering Modern Approaches Eric Braude and Michael Bernstein 1.
Winter 2011SEG Chapter 11 Chapter 1 (Part 1) Review from previous courses Subject 1: The Software Development Process.
Software Engineering Modern Approaches Eric Braude and Michael Bernstein 1.
CSE SW Metrics and Quality Engineering Copyright © , Dennis J. Frailey, All Rights Reserved CSE8314M13 8/20/2001Slide 1 SMU CSE 8314 /
Copyright , Dennis J. Frailey CSE Software Measurement and Quality Engineering CSE8314 M00 - Version 7.09 SMU CSE 8314 Software Measurement.
This chapter is extracted from Sommerville’s slides. Textbook chapter 22 1 Chapter 8 Validation and Verification 1.
Software Engineering Modern Approaches Eric Braude and Michael Bernstein 1.
by: Er. Manu Bansal Deptt of IT Software Quality Assurance.
©Ian Sommerville 2000Software Engineering, 6th edition. Chapter 19Slide 1 Verification and Validation l Assuring that a software system meets a user's.
Software Engineering Modern Approaches Eric Braude and Michael Bernstein 1.
CSC 480 Software Engineering
Software Quality Control and Quality Assurance: Introduction
Software Verification and Validation
Chapter 10 Software Quality Assurance& Test Plan Software Testing
CHAPTER.2: Requirements Engineering Processes
The Systems Engineering Context
IEEE Std 1074: Standard for Software Lifecycle
LEVEL OF TESTING J.ALFRED DANIEL, AP/CSE.
Progression of Test Categories
Chapter 1. Introduction Eric Braude and Michael Bernstein.
Software Engineering I
Metrics for process and Projects
Integrating quality activities in
Presentation transcript:

Software Engineering Modern Approaches Eric Braude and Michael Bernstein 1

© 2010 John Wiley & Sons Ltd. Chapter 2. Software Quality 2

The Software Development Lifecycle What does “software quality” mean? What are “defects” in applications What is the difference between verification and validation in software development? How do you measure software quality? Requirements analysis Design Implementation Testing Maintenance Planning 3

© 2010 John Wiley & Sons Ltd. Software Quality The more closely a software product meets its specified requirements, and those requirements meet the wants and needs of its customers, the higher its quality. 4

The Meaning of “Software Quality” 100% 0% Graphics courtesy Corel Requirements (explicit and implicit) Typical quality focus © 2010 John Wiley & Sons Ltd. 5

Software Quality (cont.) Software will contain defects Defect: deviation from requirement Software quality concerns the severity and extent of defects 6

© 2010 John Wiley & Sons Ltd. Software Quality (cont.) Quality goals: 1.Remove as many defects as is reasonably possible before project is completed 2.Remove as many of these defects as early in the development process as possible  Cost to repair increases the later a defect is discovered 7

© 2010 John Wiley & Sons Ltd. Software Quality (cont.) Moral of the story: –Finding defects early is easier and saves $$$ 8

Defect Repair Cost Requirements Design ImplementationTest Maintenance © 2010 John Wiley & Sons Ltd. 9

Phases Requiring Quality and Metrics Design Integration and System Testing Planning Requirements Analysis Maintenance Implementation and Unit Testing Process 10

© 2010 John Wiley & Sons Ltd. Verification and Validation (V&V) Verification: Ensuring that each artifact is built in accordance with its specifications - “Are we building the product right?” -Mostly inspections and reviews Validation: Checking that each completed artifact satisfies its specifications - “Are we building the right product?” - Mostly testing 11

© 2010 John Wiley & Sons Ltd. Creation, Verification and Validation Partially completed artifact Artifact under construction Completed artifact creationvalidation process verification Software engineer Graphics courtesy of Corel 12

© 2010 John Wiley & Sons Ltd. Quality Documentation  Software Quality Assurance Plan (SQAP) –IEEE Std –Overall approach to quality  Software Verification and Validation Plan (SVVP) –IEEE Std –V &V practices 13

© 2010 John Wiley & Sons Ltd. Metrics  Numerical measures that quantify the degree to which software or a process possesses a certain attribute –e.g. Defects/KLOC –e.g. Average module size  Collected and analyzed throughout software project 14

© 2010 John Wiley & Sons Ltd. Metrics (cont.)  Benefits and uses: –Measure software quality level –Estimate project schedules –Track schedule progress –Measure software size and complexity –Determine project cost –Process improvement 15

© 2010 John Wiley & Sons Ltd. Quality Metrics  Defect density  Mean time to failure  Customer problems  Customer satisfaction 16