E MBEDDED S YSTEMS S OFTWARE T RAINING C ENTER I NTRODUCTION TO Q UALITY A SSURANCE C OPYRIGHT © 2012 DSR C ORPORATION.

Slides:



Advertisements
Similar presentations
E MBEDDED S YSTEMS S OFTWARE T RAINING C ENTER T EST D ESIGN T ECHNIQUES C OPYRIGHT © 2012 DSR C ORPORATION.
Advertisements

Formal Process of QA and quality related certifications Formal Process of QA and quality related certifications MIM 3 rd year – Sem V Abhishek Mishra –
Kai H. Chang COMP 6710 Course NotesSlide CMMI-1 Auburn University Computer Science and Software Engineering Capability Maturity Model Integration - CMMI.
Group 7 - Chapter 3 Steven Shroyer - Introduction, ad hoc, level 2 Xiao Jingshan - Levels 3 and 4 Dusting Marker - Level 5 and example companies Definintions.
Software Construction
CPIS 357 Software Quality & Testing I.Rehab Bahaaddin Ashary Faculty of Computing and Information Technology Information Systems Department Fall 2010.
Software Quality Assurance (SQA). Recap SQA goal, attributes and metrics SQA plan Formal Technical Review (FTR) Statistical SQA – Six Sigma – Identifying.
Stepan Potiyenko ISS Sr.SW Developer.
Software Development Process Models. The Waterfall Development Model.
Overview Lesson 10,11 - Software Quality Assurance
SE curriculum in CC2001 made by IEEE and ACM: Overview and Ideas for Our Work Katerina Zdravkova Institute of Informatics
School of Computing, Dublin Institute of Technology.
Creating Architectural Descriptions. Outline Standardizing architectural descriptions: The IEEE has published, “Recommended Practice for Architectural.
CMM Overview - 1 © Paul Sorenson CMPUT Software Engineering refs. IEEE Software, March 1988, 73-79, and IEEE Software, July 1993, (Capability.
Embedded Systems Software Training Center
Software Quality Assurance. CS351 - Software Engineering (AY2004)2 Software engineering processes Systems vs. Software –Terms often used interchangeably.
1 Software Testing and Quality Assurance Lecture 1 Software Verification & Validation.
 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.
Software Verification and Validation (V&V) By Roger U. Fujii Presented by Donovan Faustino.
1 Software Inspections and Walkthroughs Author: A. Frank Ackerman Presented by Cynthia Johnson EEL6883.
Project Quality Management
OHT 2.1 Galin, SQA from theory to implementation © Pearson Education Limited 2004 Software Quality assurance (SQA) SWE 333 Dr Khalid Alnafjan
Managing Project Quality
Software Project Management
1 L U N D S U N I V E R S I T E T Projektledning och Projektmetodik, VBEF01 Kristian Widén Tekn. Doktor Avd. För Byggproduktion Inst. För Byggvetenskaper.
Tsvetelina Kovacheva, Quality Manager Musala Soft June 19, 2007 Implementing Models and Standards for Software Development Benefits and Risks.
Software Project Management
S T A M © 2000, KPA Ltd. Software Trouble Assessment Matrix Software Trouble Assessment Matrix *This presentation is extracted from SOFTWARE PROCESS QUALITY:
Software Quality assurance SQA – SWE 333
UNIT-II Chapter : Software Quality Assurance(SQA)
Guide to the Software Engineering Body of Knowledge Chapter 1 - Introduction.
Introduction to Software Quality Assurance (SQA)
Software Inspections and Walkthroughs By. Adnan khan.
COURSE TITLE: 1 Software Quality Assurance. Course Aims Introduction to software quality assurance. Software testing terminology. Role and responsibility.
Software Quality Assurance Activities
Unit 8 Syllabus Quality Management : Quality concepts, Software quality assurance, Software Reviews, Formal technical reviews, Statistical Software quality.
By: Md Rezaul Huda Reza 5Ps for SE Process Project Product People Problem.
CS3100 Software Project Management Week 26 - Quality Dr Tracy Hall.
SOFTWARE ENGINEERING1 Introduction. Software Software (IEEE): collection of programs, procedures, rules, and associated documentation and data SOFTWARE.
The Guide to the Software Engineering Body of Knowledge
E MBEDDED S YSTEM S OFTWARE B ASICS D IAGRAMS E MBEDDED S YSTEMS S OFTWARE T RAINING C ENTER 1.
E MBEDDED S YSTEMS S OFTWARE T RAINING C ENTER S OFTWARE D ESIGN C OPYRIGHT © 2011 DSR C ORPORATION.
S Q A.
Software Quality Assurance SE Software Quality Assurance What is “quality”?
CS 3610: Software Engineering – Fall 2009 Dr. Hisham Haddad – CSIS Dept. Chapter 2 The Software Process Discussion of the Software Process: Process Framework,
Quality Concepts within CMM and PMI G.C.Reddy
E MBEDDED S YSTEMS S OFTWARE T RAINING C ENTER P ROJECT M ANAGEMENT P ROCESSES C OPYRIGHT © 2012 DSR C ORPORATION.
CSE4002CMMI Capability Maturity Model Integration (CMMI) CMMI is replacing the well established CMM rating for software developers and systems engineers.
Process Improvement. It is not necessary to change. Survival is not mandatory. »W. Edwards Deming Both change and stability are fundamental to process.
SOFTWARE ENGINEERING1 Introduction. SOFTWARE ENGINEERING2 Software Q : If you have to write a 10,000 line program in C to solve a problem, how long will.
Anton Krbaťa Ján Budáč  Verification: "Are we building the product right ?„  Validation: "Are we building the right product ?"
Verification and Validation Assuring that a software system meets a user's needs.
An Introduction. Objective - Understand the difference between CMM & CMMI - Understand the Structure of CMMI.
1 Lecture 12: Chapter 16 Software Quality Assurance Slide Set to accompany Software Engineering: A Practitioner’s Approach, 7/e by Roger S. Pressman Slides.
UNIT 5.
SE513 Software Quality Assurance Lecture12: Software Reliability and Quality Management Standards.
E MBEDDED S YSTEMS S OFTWARE T RAINING C ENTER T EST D ESIGN T ECHNIQUES C OPYRIGHT © 2012 DSR C ORPORATION.
P ERSONAL & TEAM PROCESS MODELS Lecture 05 Part -2.
Introduction Edited by Enas Naffar using the following textbooks: - A concise introduction to Software Engineering - Software Engineering for students-
Software Quality Assurance
Chapter 10 Software Quality Assurance& Test Plan Software Testing
Introduction SOFTWARE ENGINEERING.
Information Technology Project Management – Fifth Edition
Definitions.
Introduction Edited by Enas Naffar using the following textbooks: - A concise introduction to Software Engineering - Software Engineering for students-
Quality management standards
ارائه كننده: شاهين انتصاري
Verification and Validation Unit Testing
Software Design & Production Methodologies
Presentation transcript:

E MBEDDED S YSTEMS S OFTWARE T RAINING C ENTER I NTRODUCTION TO Q UALITY A SSURANCE C OPYRIGHT © 2012 DSR C ORPORATION

Objectives  Understand what is quality  Understand the software quality assurance basic notions, processes, and techniques C OPYRIGHT © 2012 DSR C ORPORATION 2

Class Materials  Software Engineering Introduction diagrams are available here:   Hands-on Exercises are available here: C OPYRIGHT © 2012 DSR C ORPORATION 3

Agenda 1.Software Quality Fundamentals 2.Software Quality Management Processes 3.Software Quality Management Techniques 4.Software Quality Measures C OPYRIGHT © 2012 DSR C ORPORATION 4

E MBEDDED S YSTEMS S OFTWARE T RAINING C ENTER S OFTWARE Q UALITY F UNDAMENTALS S OFTWARE Q UALITY F UNDAMENTALS C OPYRIGHT © 2012 DSR C ORPORATIONS

Capability Maturity Model Integration C OPYRIGHT © 2012 DSR C ORPORATION

Quality Improvement  Building quality through:  The prevention and early detection of errors  Continuous improvement  Customer focus  Total Quality Management (TQM) approach  The Six Sigma process  % of the products manufactured are statistically expected to be free of defects (3.4 defects per million)  Management sponsorship  Identifying actions and improvement projects to be addressed in a feasible time frame  Identify resources to achieve the goal defined for it  Proactive activities C OPYRIGHT © 2012 DSR C ORPORATION

E MBEDDED S YSTEMS S OFTWARE T RAINING C ENTER S OFTWARE Q UALITY M ANAGEMENT P ROCESSES S OFTWARE Q UALITY M ANAGEMENT P ROCESSES C OPYRIGHT © 2012 DSR C ORPORATIONS

Code Review  Performed during Inspection or Walk-through  Finds the faults that are difficult to find by testing. Latent defect discovery rate:  Formal inspection is in the 60-65% range, at most 85%  For informal walk-through, the figure is less than 50%  For most forms of testing is about 30%  Does not replace testing  Up to 75% of code review defects affect software maintainability rather than functionality  Typical rate is about 150 lines of code per hour  Handled according to code review rules C OPYRIGHT © 2012 DSR C ORPORATION

E MBEDDED S YSTEMS S OFTWARE T RAINING C ENTER S OFTWARE Q UALITY M EASURES S OFTWARE Q UALITY M EASURES C OPYRIGHT © 2012 DSR C ORPORATIONS

Software Complexity Metrics (cont.) C OPYRIGHT © 2012 DSR C ORPORATION Complexity Analysis of Real Time Software Using Software Complexity Metrics to Improve the Quality of Real Time Software. Armin Krusko 11

Summary  Software quality has a definite value and cost.  Software quality management processes intended to ensure the that quality is built-in into the software. Validation, Verification, and Review processes are the most intensive among them.  Various techniques are involved to achieve the Software Quality Management Goals. Static and dynamic are most useful among them.  Software quality measures allow us to estimate product quality as well as to plan, control, and improve the quality processes. C OPYRIGHT © 2012 DSR C ORPORATION 12

Questions 1.What is software quality? Why quality is so important? What the software quality cost consists of? 2.What are main software quality characteristics? 3.What are the main software quality management processes? 4.Give the short characteristic of Verification & Validation processes. Provide the examples of the applying of these processes on every stage of Software Life Cycle. Which Software Quality Management techniques are used in these processes? 5.What Reviews and Audits are used for? Which Software Quality Management techniques are used in these processes? 6.Characterize the Software Quality Management techniques. What the every technique allows to achieve and what it its limitaiton? 7.What are the Quality Measurement objectives? What the Software Quality Metrics do you know? C OPYRIGHT © 2012 DSR C ORPORATION 13

References 1.SWEBOK. Guide to the Software Engineering. Body of Knowledge Version / A project of the IEEE Computer Society Professional Practices Committee 2.IEEE Std , IEEE Standard Glossary of Software Engineering Terminology 3.TickITplus certification scheme. 4.Capability Maturity Model Integration (CMMI) 5.ISO 9001:2008. Quality management systems — Requirements 6.ISO/IEC Software engineering — Product quality 7.IEEE/EIA Standard for Information Technology – Software Life Cycle Processes 8.IEEE IEEE Standard for Software Quality Assurance Plan 9.IEEE IEEE Guide for Software Verification and Validation Plans 10.ISO/IEC :2001. Software engineering -- Product quality -- Part 1: Quality model 11.IEEE IEEE Standard for Software Reviews Jones, Capers; Christof, Ebert (April 2009). "Embedded Software: Facts, Figures, and Future“"Embedded Software: Facts, Figures, and Future“ 12.Complexity Analysis of Real Time Software – Using Software Complexity Metrics to Improve the Quality of Real Time Software. Armin Krusko 13.Software Engineering Code of Ethics and Professional Practice (Version 5.2) as recommended by the ACM/IEEE-CS. C OPYRIGHT © 2012 DSR C ORPORATION 14