Charakteristiky kvality

Slides:



Advertisements
Similar presentations
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.
Advertisements

軟工一 吳彥諄. * Scrum overview * What happened to the software * What is the quality attribute * ACRUM * Q&A.
CHAPTER 1 Introduction to SQA.
Software project management (intro) Quality assurance.
OHT 3.1 Galin, SQA from theory to implementation © Pearson Education Limited 2004 The need for comprehensive software quality requirements Classification.
CS 325: Software Engineering March 26, 2015 Software Quality Assurance Software Metrics Defect Injection Software Quality Lifecycle Measuring Progress.
Non-Functional Requirements
Non-functional requirements
Software Quality SEII-Lecture 15
Software Project Management Fifth Edition
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.
Requirements specification Copyright, 2001 © Jerzy R. Nawrocki Quality Management.
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)
CSE 303 – Software Design and Architecture
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.
Topic (1)Software Engineering (601321)1 Introduction Complex and large SW. SW crises Expensive HW. Custom SW. Batch execution.
Copyright © Jerzy R. Nawrocki ISO 9126 and Non-functional Requirements Requirements.
1 Software quality - Definition IEEE 1. The degree to which a system, component, or process meets specified requirements. 2. The degree to which a system,
Other Quality Attributes Other Important Quality attributes Variability: a special form of modifiability. The ability of a system and its supporting artifacts.
ICare Software Architecture Description: Principles, Decisions and Contradictions Team A Aggarwal Ashutosh Alungh Suman Appiah Stella Baddam Bhaskar Baghaie.
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?
Software Quality : The Elusive Target
University of Palestine software engineering department Testing of Software Systems Testing throughout the software life cycle instructor: Tasneem.
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.
Software Methods Mö/ slide 1 Methods and Techniques of Software Quality Management ICEL Quality Management Systems: Methods and Techniques of Software.
21-22 May 2004IMPROQ 2004 / Impact of SW Processes on Quality Workshop 1 Quality for Components: Component and Component- Based Software Quality Issues.
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.
Modelling Support for Quality of Service Eclipse ECESIS Project Modelling Support for Quality of Service Department for Cooperative and Trusted Systems.
Software quality factors
CS551 - Lecture 5 1 CS551 Lecture 5: Quality Attributes Yugi Lee FH #555 (816)
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?
Software Testing for Intelligent Robots Justin Peckner Maria Velasquez November 13, 2012.
LESSON 3. Properties of Well-Engineered Software The attributes or properties of a software product are characteristics displayed by the product once.
Chapter 13: Software Quality Project Management Afnan Albahli.
UKTMF 27 th January 2010 Non-Functional Testing1 Non-Functional Testing Non-Functional Testing Why is this so often done badly or not done at all? Can.
Chapter 2 Object-Oriented Paradigm Overview. Getting Acquainted with the Class Project Read the requirements specification carefully Make note of any.
SEN 460 Software Quality Assurance
ISQB Software Testing Section Meeting 10 Dec 2012.
Chapter 2 Object-Oriented Paradigm Overview
TOTAL QUALITY MANAGEMENT
16CS202 & Software Engineering
SOFTWARE TESTING Date: 29-Dec-2016 By: Ram Karthick.
Software Quality Control and Quality Assurance: Introduction
Rekayasa Perangkat Lunak Part-10
Non Functional Requirements (NFRs)
Rekayasa Perangkat Lunak
Evaluation Forms for Blockchain- Based System ver. 1.0
Security SIG in MTS 05th November 2013 DEG/MTS RISK-BASED SECURITY TESTING Fraunhofer FOKUS.
Source & Courtesy: Doc. S. Dapkūnas
Software Quality Assurance Software Quality Factor
Quality Exercise 2 Instructions
McCall’s Quality Factors
Lecture 15: Technical Metrics
Quality Exercise 2 Instructions
Quality Exercise 2 Instructions
Software engineering.
مقدمه اي بر مهندسي نيازمنديها
Rekayasa Perangkat Lunak
UNIT II.
and Jose-Norberto Mazón University of Alicante
Software Quality Assurance Lecture 3
Quality Factors.
ISO/IEC Systems and software Quality Requirements and Evaluation
Tomaž Špeh SURS TF SERV, Luxembourg,
Presentation transcript:

Charakteristiky kvality

ISO 25011 Quality Characteristic Functional suitability   Reliability Quality Characteristic Maturity Functional suitability Availability Functional completeness Fault tolerance Functional correctness Recoverability Functional appropriateness Security Performance efficiency Confidentiality Time behaviour Integrity Resource utilization Non-repudiation (nepopiratelnost) Capacity Accountability Compatibility Authenticity Co-existence Maintainability Interoperability Modularity Usability Reusability Appropriateness recognizability Analysability Learnability Modifiability Operability Testability User error protection Portability User interface aesthetics Adaptability Accessibility Installability Replaceability

ISO 25011 SW Quality Characteristics Functional suitability Functional completeness Functional correctness Functional appropriateness Performance efficiency Time behaviour Resource utilization Capacity

Na SOA to moc nepasuje (úplnost?) functional suitability degree to which a product or system provides functions that meet stated and implied needs when used under specified conditions Note 1 to entry: Functional suitability is only concerned with whether the functions meet stated and implied needs, not the functional specification. functional completeness degree to which the set of functions covers all the specified tasks and user objectives functional correctness degree to which a product or system provides the correct results with the needed degree of precision functional appropriateness degree to which the functions facilitate the accomplishment of specified tasks and objectives Na SOA to moc nepasuje (úplnost?)

ISO 25011 SW Quality Characteristics Reliability Maturity Availability Fault tolerance Recoverability Security Confidentiality Integrity Non-repudiation Accountability Authenticity

ISO 25011 SW Quality Characteristics Compatibility Co-existence Interoperability Usability Appropriateness recognizability Learnability Operability User error protection User interface aesthetics Accessibility

ISO 25011 SW Quality Characteristics Maintainability Modularity Reusability Analysability Modifiability Testability Portability Adaptability Installability Replaceability

maintainability degree of effectiveness and efficiency with which a product or system can be modified by the intended maintainers Modifications can include corrections, improvements or adaptation of the software to changes in environment, and in requirements and functional specifications. Modifications include those carried out by specialized support staff, and those carried out by business or operational staff, or end users. Maintainability includes installation of updates and upgrades. Maintainability can be interpreted as either an inherent capability of the product or system to facilitate maintenance activities, or the quality in use experienced by the maintainers for the goal of maintaining the product or system

modularity degree to which a system or computer program is composed of discrete components such that a change to one component has minimal impact on other components[viz: ISO/IEC/IEEE 24765] reusability degree to which an asset can be used in more than one system, or in building other assets analysability degree of effectiveness and efficiency with which it is possible to assess the impact on a product or system of an intended change to one or more of its parts, or to diagnose a product for deficiencies or causes of failures, or to identify parts to be modified Implementation can include providing mechanisms for the product or system to analyze its own faults and provide reports prior to a failure or other event.

modifiability degree to which a product or system can be effectively and efficiently modified without introducing defects or degrading existing product quality Implementation includes coding, designing, documenting and verifying changes. Modularity (and analysability can influence modifiability Modifiability is a combination of changeability and stability. testability degree of effectiveness and efficiency with which test criteria can be established for a system, product or component and tests can be performed to determine whether those criteria have been met

ISO 25011 kvalita pro užívání Effectiveness Efficiency Satisfaction Usefulness Trust Pleasure Comfort Freedom from risk Economic risk mitigation (zmírnění, redukce) Health and safety risk mitigation Environmental risk mitigation Context coverage Context completeness Flexibility