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

Slides:



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

Software Engineering 1. Software development – the grand view 2. Requirements engineering.
Software Engineering Software quality. Software quality characteristics:  External: user is aware of. User cares about.  Internal: programmer is aware.
Reuse and Reusability (Chapter 8 of maintenance text) Steve Chenoweth CSSE 375, Rose-Hulman Based on Don Bagert’s 2006 Lecture Image from
1 Software Architecture CSSE 477: Week 5, Day 1 Statistical Modeling to Achieve Maintainability Steve Chenoweth Office Phone: (812) Cell: (937)
軟工一 吳彥諄. * Scrum overview * What happened to the software * What is the quality attribute * ACRUM * Q&A.
1 Quality CSSE 371 Software Requirements and Specification Mark Ardis, Rose-Hulman Institute October 25, 2004.
Team Skill 6 - Building The Right System Part 2: Traceability, Change and Quality (Chapters of the requirements text) CSSE 371 Software Requirements.
1 Steve Chenoweth Tuesday, 10/04/11 Week 5, Day 2 Right – Typical tool for reading out error codes logged by your car’s computer, to help analyze its problems.
1 Steve Chenoweth Tuesday, 10/25/11 Week 8, Day 2 Right – Desktop computer usability metaphor, from
Elaboration of Use Cases CSSE 371, Software Requirements and Specification Steve Chenoweth, Rose-Hulman Institute October 21, 2004 In the book – This is.
1 CSSE 477 – Intro to Modifiability Steve Chenoweth Friday, 9/23/2011 Week 3, Day 4 Right - A modified VW beetle, from
Week 10 CSSE 375 Steve Chenoweth & Everybody. Today Get back Exam 2 This week’s schedule – this Reflection on the course Talk about final assignment Decide.
1 Maintenance Metrics and Measures (M 12) Steve Chenoweth CSSE 375, Rose-Hulman Based on Don Bagert’s 2006 Lecture.
Slide 1 Requirements Wrap-up (Chapter 31 of requirements text) and Interaction Design: Introduction (Chapters 1 of Interaction Design text) CSSE 371 Software.
1 Steve Chenoweth Tuesday, 10/18/11 Week 7, Day 2 Right – One view of the layers of ingredients to an enterprise security program. From
SE 555 Software Requirements & Specification Requirements Quality Attributes.
1 Software Change Steve Chenoweth CSSE 375, Rose-Hulman Based on Don Bagert’s 2006 Lecture Ref M , 4 - In progress -
1 The Maintenance Process Steve Chenoweth CSSE 375, Rose-Hulman Based on Don Bagert’s 2006 Lecture.
Team Skill 6 - Building The Right System Part 1: Applying Use Cases (Chapters of the requirements text) CSSE 371 Software Requirements and Specification.
1 Detailed Design Representations (Chapter 9 of Code Complete) Steve Chenoweth CSSE 375, Rose-Hulman Based on Don Bagert’s 2006 Lecture.
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.
1 Maintenance Management and Organization Steve Chenoweth CSSE 375, Rose-Hulman Based on Don Bagert’s 2006 Lecture.
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.
Handouts Software Testing and Quality Assurance Theory and Practice Chapter 17 Software Quality
Chapter 24 - Quality Management
Quality Management ISO 9001 For TM. What is Quality Quality is the degree to which product or service possesses a desired combination of attributes C:
Software Quality Chapter Software Quality  How can you tell if software has high quality?  How can we measure the quality of software?  How.
Managing Software Quality
Quality Assurance ITEC Rick Price. Expectations This course is not purely a lecture course – Classroom participation is a large portion – Everyone.
1 Software Construction Software Construction Chapter 1.
1 ICS 122: Software Specification and Quality Engineering Spring 2002Lecturers: H. Muccini and D. J. Richardson Lecture 13: Summary The three aspects:
Supplementary Specifications (Chapters 20,22 - Requirements Text) Question 1 by Steve & Chandan (Along with others in the past! - See notes, below)
Planning and Tracking Software Quality.  What Is Software Quality?  Causes of Software Defects  What is Quality Assurance?  Improving the Software.
Topics Covered: Software requirement specification(SRS) Software requirement specification(SRS) Authors of SRS Authors of SRS Need of SRS Need of SRS.
Quality Models and Quality Attributes. Outline  Process and product quality Improving the quality of the process can improve the quality of the product.
College of Engineering and Computer Science Computer Science Department CSC 131 Computer Software Engineering Fall 2006 Lecture # 1 (Ch. 1, 2, & 3)
Supplementary Specifications (Chapters 20,22 - Requirements Text) 1.
 Explain the role of a system analyst.  Identify the important parts of SRS document.  Identify the important problems that an organization would face.
Object-Oriented Software Engineering Practical Software Development using UML and Java Chapter 1: Software and Software Engineering.
Planning and Tracking Software Quality Yordan Dimitrov Telerik Corporation
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.
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.
Prepared by: Hussein Alhashimi.  This course introduces fundamental concepts related to Quality Assurance and Measurements and Metrics in the software.
SOFTWARE ENGINEERING. Objectives Have a basic understanding of the origins of Software development, in particular the problems faced in the Software Crisis.
1 Maintenance of Documentation and Documentation of Maintenance Quiz 7 Tori Bowman CSSE 375, Rose-Hulman October 1, 2006.
CS352 – Software Engineering II Lecture 17: SW Quality Assurance Landscape Slides by Mohammad El-Ramly, PhD.
Requirements. Outline Definition Requirements Process Requirements Documentation Next Steps 1.
by: Er. Manu Bansal Deptt of IT Software Quality Assurance.
 System Requirement Specification and System Planning.
16CS202 & Software Engineering
Software Quality Control and Quality Assurance: Introduction
Rekayasa Perangkat Lunak Part-10
Rekayasa Perangkat Lunak
Quality Management chapter 27.
Software Quality Assurance Software Quality Factor
Software Quality & Testing
McCall’s Quality Factors
Lecture 15: Technical Metrics
Introduction to Software Engineering: Second Edition
مقدمه اي بر مهندسي نيازمنديها
Rekayasa Perangkat Lunak
Thursday’s Lecture Chemistry Building Musspratt Lecture Theatre,
20. The Software-Quality Landscape
Software Quality Course 1 Introduction.
Overview of BSSE at Rose-Hulman Institute of Technology
Presentation transcript:

1 Quality Assurance in Construction and Maintenance (Section 13.4 of Maintenance Text; Chapter 20 of Code Complete) Steve Chenoweth CSSE 375, Rose-Hulman Based on Don Bagert’s 2006 Lecture

2 Today Team progress report & show a test case Quality Issues – this (no quiz) Tonight - Start HW3: Detailed Design. Tomorrow – Help on coding and testing - Bring your laptop Defensive Programming and Debugging – Tori

3 Review: Goal-Question-Metric Method One source of information: – kl.de/pubs/repository/basili94b/encyclo.gqm.pdf. kl.de/pubs/repository/basili94b/encyclo.gqm.pdf A short example: –Goal: To maximize customer support satisfaction –Question: Are there are consistent problems with the software? –Metric: Number of problem reports generated per day →→

4 Outline General Principle of Software Quality Software Quality Assurance Factors –External Quality Characteristics –Internal Quality Characteristics Some Software Quality Improvement Techniques

5 General Principle of Software Quality: Improving quality reduces development costs.

6 Quality Assurance Factors External quality characteristics –Attributes that can be determined from use of the software product –Functional Correctness/Reliability Accuracy –Other (“Non-Functional”) Efficiency Integrity Usability Adaptability Robustness

7 Quality Assurance Factors Internal quality characteristics –Attributes determined from examination of the artifacts –Both Development and Maintenance Characteristics Readability Understandability Reusability –Primarily a Development Characteristic Testability –Primarily Maintenance Characteristics Flexibility Portability Maintainability

8 McConnell’s caution on these – It depends on the project. You could argue, for example, that Efficiency often conflicts with all the rest of these.

9 How do these QA factors compare with Bass’s list 1 ? Here are his six “Quality Attributes”: Performance & capacity Reliability & availability Usability Security Modifiability, maintainability, & customizability Testability 1 From Software Architecture in Practice (2nd Edition), by Len Bass, et al, the book we use in CSSE 374 and 377.

10 Some Software Quality Improvement Techniques Improved Process Formal and Informal Reviews Software Quality Metrics Note that metrics relate to an improved process and reviews!

11 Exercise You work for a company that develops commercial desktop software Your team will be assigned an external quality attribute Come up with a plan on how to measure and improve that attribute Repeat for an internal quality attribute 5 min per attribute!