Quality Factors.

Slides:



Advertisements
Similar presentations
Slide 1 Shall Lists. Slide 2 Shall List Statement Categories  Functional Requirements  Non-Functional Requirements.
Advertisements

System Integration Verification and Validation
Software project management (intro) Quality assurance.
R&D SDM 1 Metrics How to measure and assess software engineering? 2009 Theo Schouten.
SE 555 Software Requirements & Specification Requirements Quality Attributes.
OHT 3.1 Galin, SQA from theory to implementation © Pearson Education Limited 2004 The need for comprehensive software quality requirements Classification.
Non-Functional Requirements
Cloud Usability Framework
Configuration Management
Non-functional requirements
Factor Of Software Quality
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.
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)
Topics Covered: Software requirement specification(SRS) Software requirement specification(SRS) Authors of SRS Authors of SRS Need of SRS Need of SRS.
CSE 303 – Software Design and Architecture
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.
Service Transition & Planning Service Validation & Testing
Software Engineering Quality What is Quality? Quality software is software that satisfies a user’s requirements, whether that is explicit or implicit.
Other Quality Attributes Other Important Quality attributes Variability: a special form of modifiability. The ability of a system and its supporting artifacts.
Question To know that quality has improved, it would be helpful to be able to measure quality. How can we measure quality?
Drexel University CS 451 Software Engineering Winter Yuanfang Cai Room 104, University Crossings
Software Quality : The Elusive Target
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.
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 Models in Software Engineering Literature: An Analytical and Comparative Study Rafa E. Al-Qutaish, PhD Al Ain University of Science and Technology.
CMSC 345 Fall 2000 Requirements Overview. Work with customers to elicit requirements by asking questions, demonstrating similar systems, developing prototypes,
LESSON 3. Properties of Well-Engineered Software The attributes or properties of a software product are characteristics displayed by the product once.
Prepared by: Hussein Alhashimi.  This course introduces fundamental concepts related to Quality Assurance and Measurements and Metrics in the software.
SEN 460 Software Quality Assurance
CSE 303 – Software Design and Architecture
ISQB Software Testing Section Meeting 10 Dec 2012.
TOTAL QUALITY MANAGEMENT
SOFTWARE TESTING Date: 29-Dec-2016 By: Ram Karthick.
Rekayasa Perangkat Lunak Part-10
Non Functional Requirements (NFRs)
Rekayasa Perangkat Lunak
Evolutionary requirements
Evaluation Forms for Blockchain- Based System ver. 1.0
SEVERITY & PRIORITY RELATIONSHIP
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
Software engineering.
مقدمه اي بر مهندسي نيازمنديها
Rekayasa Perangkat Lunak
Software Quality Engineering CS- 449
UNIT II.
Charakteristiky kvality
Thursday’s Lecture Chemistry Building Musspratt Lecture Theatre,
Evolutionary Requirements
Software Quality Assurance Lecture 3
Chapter # 2 Software Quality Factors
ISO/IEC Systems and software Quality Requirements and Evaluation
Tomaž Špeh SURS TF SERV, Luxembourg,
Presentation transcript:

Quality Factors

Hvad er Kvalitet? Conformance to specification: Quality that is defined as a matter of products and services Meeting customer needs: Quality that is identified independent of any measurable characteristics.

Hvad er Kvalitet? Del 2 Walter A. Shewhart defines quality The consideration of the quality of a thing as an objective reality independent of the existence of man. (Kvantitative – tit tæt på kvalitets faktorer) What we think, feel or sense as a result of the objective reality. In other word, there is a subjective side of quality. (Kvalitative – sværere at beskrive)

Kvalitet faktorer Et redskab til Afklare bruger krav Et bedre system udvikling forløb Et fokuseret system udvikling forløb Afklare bruger krav Bør indgå i krav specifikationen NB! Det er nemmere at specificere ‘objektive’ krav end subjektive

Kvalitet faktorer DEL 2 En række Kvalitets Modeller McCall (conform to specification) Boehm (You can conform in diff. degree) FURPS (Same but fewer categories – Described in Larman) ISO – international Standardisation Organisation 900x – focus on process 9126 – a la McCall, Boehm, FURPS 25010 – Newest version of SW Product Quality

McCall - Major Perspectives Portability kan det køre på andre platforme Reusability kan jeg genbruge dele af SW Interoperability kan det kobles til andre systemer Product Operation Product Revision Product Transition Maintability Kan jeg rette i det Flexsability Kan det ændres Testability Kan det testes Correctness Gør vi det rigtigt Reliability Gør vi det nøjagtigt hele tiden Efficiency Kører det optimalt på min HW Integrity Er det sikkert Usability Kan jeg køre det (brugervenligt)

McCall - Kvalitets Faktorer Correctness Reliability Efficiency Integrity Usability Maintainability Testability Flexibility Portability Reusability Interoperability

Product Operation

Product Revision

Product Transition

FURPS Functional features, capabilities, security. Usability human factors, help, documentation. Reliability frequency of failure, recoverability, predictability. Performance response times, throughput, accuracy, availability, resource usage. Supportability adaptability, maintainability, internationalization, configurability.

FURPS+ Implementation resource limitations, languages and tools, hardware, ... Interface constraints imposed by interfacing with external systems. Operations system management in its operational setting. Packaging for example, a physical box. Legal licensing and so forth.

ISO - 26010 Source:: http://iso25000.com/index.php/en/iso-25000-standards/iso-25010?limit=3&limitstart=0

ISO – 26010 – Functional Suitability 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. Source:: http://iso25000.com/index.php/en/iso-25000-standards/iso-25010?limit=3&limitstart=0

ISO – 26010 – Performance efficiency Time behaviour.  Degree to which the response and processing times and throughput rates of a product or system, when performing its functions, meet requirements. Resource utilization.  Degree to which the amounts and types of resources used by a product or system, when performing its functions, meet requirements. Capacity.  Degree to which the maximum limits of a product or system parameter meet requirements. Source:: http://iso25000.com/index.php/en/iso-25000-standards/iso-25010?limit=3&limitstart=0

ISO – 26010 – Compatibility Co-existence. Degree to which a product can perform its required functions efficiently while sharing a common environment and resources with other products, without detrimental impact on any other product. Interoperability. Degree to which two or more systems, products or components can exchange information and use the information that has been exchanged. Source:: http://iso25000.com/index.php/en/iso-25000-standards/iso-25010?limit=3&limitstart=0

ISO – 26010 – Usability Appropriateness recognisability. Degree to which users can recognize whether a product or system is appropriate for their needs. Learnability. Degree to which a product or system can be used by specified users to achieve specified goals of learning to use the product or system with effectiveness, efficiency, freedom from risk and satisfaction in a specified context of use. Operability. Degree to which a product or system has attributes that make it easy to operate and control. User error protection. Degree to which a system protects users against making errors. User interface aesthetics. Degree to which a user interface enables pleasing and satisfying interaction for the user. Accessibility. Degree to which a product or system can be used by people with the widest range of characteristics and capabilities to achieve a specified goal in a specified context of use. Source:: http://iso25000.com/index.php/en/iso-25000-standards/iso-25010?limit=3&limitstart=0

ISO – 26010 – Reliability Maturity. Degree to which a system, product or component meets needs for reliability under normal operation. Availability. Degree to which a system, product or component is operational and accessible when required for use. Fault tolerance. Degree to which a system, product or component operates as intended despite the presence of hardware or software faults. Recoverability. Degree to which, in the event of an interruption or a failure, a product or system can recover the data directly affected and re-establish the desired state of the system. Source:: http://iso25000.com/index.php/en/iso-25000-standards/iso-25010?limit=3&limitstart=0

ISO – 26010 – Security Confidentiality. Degree to which a product or system ensures that data are accessible only to those authorized to have access. Integrity. Degree to which a system, product or component prevents unauthorized access to, or modification of, computer programs or data. Non-repudiation. Degree to which actions or events can be proven to have taken place, so that the events or actions cannot be repudiated later. Accountability. Degree to which the actions of an entity can be traced uniquely to the entity. Authenticity. Degree to which the identity of a subject or resource can be proved to be the one claimed. Source:: http://iso25000.com/index.php/en/iso-25000-standards/iso-25010?limit=3&limitstart=0

ISO – 26010 – Maintainability 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. 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. Modifiability. Degree to which a product or system can be effectively and efficiently modified without introducing defects or degrading existing product quality. 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. Source:: http://iso25000.com/index.php/en/iso-25000-standards/iso-25010?limit=3&limitstart=0

ISO – 26010 – Portability Adaptability. Degree to which a product or system can effectively and efficiently be adapted for different or evolving hardware, software or other operational or usage environments. Installability. Degree of effectiveness and efficiency with which a product or system can be successfully installed and/or uninstalled in a specified environment. Replaceability. Degree to which a product can replace another specified software product for the same purpose in the same environment. Source:: http://iso25000.com/index.php/en/iso-25000-standards/iso-25010?limit=3&limitstart=0