Copyright © Jerzy R. Nawrocki ISO 9126 and Non-functional Requirements Requirements.

Slides:



Advertisements
Similar presentations
Product strategy Product analysis and description Lecture 7.
Advertisements

Page 1 DELTA Danish Electronics, Light & Acoustics SQuaRE Next Generation of ISO/IEC 9126 & ISO/IEC JTC1/SC7/WG6 Budapest, June 2001 Jørgen Bøegh.
Software Testing #IRL Agenda Why Software Testing Software Testing Principles – Exhaustive testing is impossible – Early Testing.
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.
軟工一 吳彥諄. * Scrum overview * What happened to the software * What is the quality attribute * ACRUM * Q&A.
Software project management (intro) Quality assurance.
CS 325: Software Engineering March 26, 2015 Software Quality Assurance Software Metrics Defect Injection Software Quality Lifecycle Measuring Progress.
Non-Functional Requirements
Ch 3 Usability page 1CS 368 Usability Models the authors compare three usability models and introduce their own “the extent to which a product can be used.
Non-functional requirements
Software Quality SEII-Lecture 15
Software Project Management Fifth Edition
COURSE TITLE: 1 Software Quality Assurance. Course Aims Introduction to software quality assurance. Software testing terminology. Role and responsibility.
 The software systems must do what they are supposed to do. “do the right things”  They must perform these specific tasks correctly or satisfactorily.
1 ICS 122: Software Specification and Quality Engineering Spring 2002Lecturers: H. Muccini and D. J. Richardson Lecture 13: Summary The three aspects:
Requirements specification Copyright, 2001 © Jerzy R. Nawrocki Quality Management.
Copyright © Jerzy R. Nawrocki Requirements Review Requirements Engineering & Project.
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)
Quality Models and Quality Attributes. Outline  Process and product quality Improving the quality of the process can improve the quality of the product.
Amirkabir University of Technology, Computer Engineering Faculty, Intelligent Systems Laboratory 1 Overview of Requirements Engineering Section One Version:
1 Software Quality CIS 375 Bruce R. Maxim UM-Dearborn.
Software Quality Assurance SE Software Quality Assurance What is “quality”?
Requirements Engineering ments_analysis.
Other Quality Attributes Other Important Quality attributes Variability: a special form of modifiability. The ability of a system and its supporting artifacts.
Software Quality : The Elusive Target
University of Palestine software engineering department Testing of Software Systems Testing throughout the software life cycle instructor: Tasneem.
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.
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.
CS551 - Lecture 5 1 CS551 Lecture 5: Quality Attributes Yugi Lee FH #555 (816)
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.
CSSE Software Engineering Process and Practice Lecture 5 Q UALITY A SSURANCE.
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.
Software Quality in Use Characteristic Mining from Customer Reviews Warit Leopairote, Athasit Surarerks, Nakornthip Prompoon Department of Computer Engineering,
Requirements Specification Copyright, 2001 © Jerzy R. Nawrocki Requirements Engineering.
Chapter 2 Object-Oriented Paradigm Overview. Getting Acquainted with the Class Project Read the requirements specification carefully Make note of any.
Requirements Engineering ments_analysis.
SOFTWARE ENGINEERING MCS-2 LECTURE # 2. ATTRIBUTES OF GOOD S/W  Maintainability;  S/w should be written in such a way that it may evolve to meet the.
EMI INFSO-RI Software Quality Assurance in EMI Maria Alandes Pradillo (CERN) SA2.2 Task Leader.
Requirements Engineering
Project Management Quality Management. Introduction Project planning Gantt chart and WBS Project planning Network analysis I Project planning Network.
Daniel Siahaan February Content Introduction to Requirements Engineering Stakeholder Perpective Scenario Requirements Elicitation Requirements Analysis.
ISQB Software Testing Section Meeting 10 Dec 2012.
Chapter 2 Object-Oriented Paradigm Overview
TOTAL QUALITY MANAGEMENT
16CS202 & Software Engineering
Software Verification and Validation
Source & Courtesy: Doc. S. Dapkūnas
Quality Exercise 2 Instructions
McCall’s Quality Factors
Lecture 15: Technical Metrics
Usability engineering
Usability engineering
Quality Exercise 2 Instructions
Quality Exercise 2 Instructions
Software engineering.
مقدمه اي بر مهندسي نيازمنديها
Software engineering Lecturer: Nareena.
Charakteristiky kvality
and Jose-Norberto Mazón University of Alicante
Software Quality Assurance Lecture 3
Human Computer Interaction
Quality Factors.
Requirements Engineering Lecture 6
ISO/IEC Systems and software Quality Requirements and Evaluation
Tomaž Špeh SURS TF SERV, Luxembourg,
Presentation transcript:

Copyright © Jerzy R. Nawrocki ISO 9126 and Non-functional Requirements Requirements Engineering & Project Management Lecture 4

J.Nawrocki, ISO 9126 Introduction Project Vision Business Process Descr. / Operational Scenarios Functional Requirements Non-functional Requirements Development, Implem. & Testing Transition

J.Nawrocki, ISO 9126 Introduction Project Vision Business Process Descr. / Operational Scenarios Functional Requirements Non-functional Requirements Development, Implem. & Testing Transition ISO 9126

J.Nawrocki, ISO 9126 Introduction ISO 9126: Software Engineering – Product Quality Part 1: Quality Model Part 2: External Metrics Part 3: Internal Metrics Part 4: Quality-in-use Metrics

J.Nawrocki, ISO 9126 Agenda Introduction Quality Model Quality in Use Internal and External Quality

J.Nawrocki, ISO 9126 Quality in the lifecycle Process quality Internal quality attributes External quality attributes Quality in use attributes Impacts Development process Software productEffect of using product

J.Nawrocki, ISO 9126 Quality in the lifecycle Internal quality External quality Quality in use Indicates Software productEffect of using product Indicates

J.Nawrocki, ISO 9126 External and Internal Quality Maintainability Functionality Reliability Usability Efficiency Portability External and Internal Quality Characteristics

J.Nawrocki, ISO 9126 Quality-in-use Effectiveness Productivity Safety Satisfaction Quality-in-use Characteristics

J.Nawrocki, ISO 9126 Agenda Introduction Quality Model Quality in Use Internal and External Quality

J.Nawrocki, ISO 9126 Quality-in-use Effectiveness Productivity Safety Satisfaction Quality-in-use Characteristics

J.Nawrocki, ISO 9126 Quality-in-use Metrics Task effectiveness – What proportion of the goals of the tasks is achieved correctly? Task completion – What proportion of the tasks is completed (number of tasks completed / total number of tasks attempted)? Error frequency – What is the frequency of errors? Effectiveness

J.Nawrocki, ISO 9126 Quality-in-use Metrics Task time – How long does it take to complete a task? Task efficiency – How efficient are the users (Task effectiveness / Task time)? Economic productivity – How cost-effective is the user (Task effectiveness / total cost of the task)? Productivity

J.Nawrocki, ISO 9126 Quality-in-use Metrics User health and safety – What is the incidence of health problems among users of the product? Economic damage – What is the incidence of economic damage? Safety

J.Nawrocki, ISO 9126 Quality-in-use Metrics Satisfation scale – How satisfied is the user? Satisfation questionnaire – How satisfied is the user with specific software features? Satisfaction

J.Nawrocki, ISO 9126 Agenda Introduction Quality Model Quality in Use Internal and External Quality

J.Nawrocki, ISO 9126 External and Internal Quality Maintainability Functionality Reliability Usability Efficiency Portability External and Internal Quality Characteristics

J.Nawrocki, ISO 9126 Functionality Suitability Accuracy Interoperability Security Functionality compliance

J.Nawrocki, ISO 9126 Reliability Maturity Fault tolerance Recoverability Compliance

J.Nawrocki, ISO 9126 Usability Uderstandability Learnability Operability Attractiveness Compliance

J.Nawrocki, ISO 9126 Efficiency Time behaviour Resource utilization Compliance

J.Nawrocki, ISO 9126 Maintainability Analysability Changeability Stability Tastability Compliance

J.Nawrocki, ISO 9126 Portability Adaptability Installability Co-existance Replaceability Compliance

J.Nawrocki, ISO 9126 Homework Prepare a spreadsheet that would support collection of non-functional requirements based on ISO Usability UnderstandabilityH LearnabilityH OperabilityL

J.Nawrocki, ISO 9126 Summary Quality views: Quality-in-use, External & Internal quality Quality characteristics: External & Internal subcharacteristics Quality metrics – Examples