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.

Slides:



Advertisements
Similar presentations
E.g Act as a positive role model for innovation Question the status quo Keep the focus of contribution on delivering and improving.
Advertisements

Lecture 1: Introduction to Software Engineering CSC301 – Winter 2011
Project management Project manager must;
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.
The Farsight Integrated Leadership Model & Diagnostic A new model for leadership that brings together all the best thinking and research over the last.
軟工一 吳彥諄. * Scrum overview * What happened to the software * What is the quality attribute * ACRUM * Q&A.
Soft. Eng. II, Spr. 02Dr Driss Kettani, from I. Sommerville1 CSC-3325: Chapter 6 Title : The Software Quality Reading: I. Sommerville, Chap: 24.
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
Chapter#7.  Part 1: Quality Management ◦ ƒ Understand the definition of quality and the different methodologies to provide quality ◦ ƒ Know quality management.
1 CMPT 275 Software Engineering Requirements Analysis Process Janice Regan,
Issues on Software Testing for Safety-Critical Real-Time Automation Systems Shahdat Hossain Troy Mockenhaupt.
Non-functional requirements
Chapter 24 - Quality Management
Lecture 3.
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.
Product Quality, Testing, Reviews and Standards
 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 Chapter 2 Socio-technical Systems (Computer-based System Engineering)
1 IS 8950 Managing and Leading a Networked IT Organization.
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)
Amirkabir University of Technology, Computer Engineering Faculty, Intelligent Systems Laboratory 1 Overview of Requirements Engineering Section One Version:
SOFTWARE ENGINEERING1 Introduction. Software Software (IEEE): collection of programs, procedures, rules, and associated documentation and data SOFTWARE.
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.
Basic of Software Testing Presented by The Smartpath Information System An ISO 9001:2008 Certified Organization
Software Quality : The Elusive Target
Human Computer Interaction
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.
University of Sunderland COM369 Unit 6 COM369 Project Quality Unit 6.
About Quality Pre paired By: Muhammad Azhar. Scope What is Quality Quality Attributes Conclusion on software Quality Quality Concepts Quality Costs.
Manag ing Software Change CIS 376 Bruce R. Maxim UM-Dearborn.
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.
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)
1 EE29B Feisal Mohammed EE29B: Introduction to Software Engineering Feisal Mohammed Ph: x3156.
Software Testing for Intelligent Robots Justin Peckner Maria Velasquez November 13, 2012.
CSSE Software Engineering Process and Practice Lecture 5 Q UALITY A SSURANCE.
Chapter 13: Software Quality Project Management Afnan Albahli.
Chapter 2 Object-Oriented Paradigm Overview. Getting Acquainted with the Class Project Read the requirements specification carefully Make note of any.
Kathy Corbiere Service Delivery and Performance Commission
 System Requirement Specification and System Planning.
ISQB Software Testing Section Meeting 10 Dec 2012.
Chapter 2 Object-Oriented Paradigm Overview
TOTAL QUALITY MANAGEMENT
BIL 424 NETWORK ARCHITECTURE AND SERVICE PROVIDING.
Introduction Edited by Enas Naffar using the following textbooks: - A concise introduction to Software Engineering - Software Engineering for students-
Quality Exercise 2 Instructions
CIF301 Project Quality Unit 6
SYSTEM ANALYSIS AND DESIGN
McCall’s Quality Factors
Introduction SOFTWARE ENGINEERING.
Usability engineering
Quality Exercise 2 Instructions
Quality Exercise 2 Instructions
Software engineering.
Introduction Edited by Enas Naffar using the following textbooks: - A concise introduction to Software Engineering - Software Engineering for students-
Software Quality Engineering CS- 449
Charakteristiky kvality
and Jose-Norberto Mazón University of Alicante
Software Quality Assurance Lecture 3
ISO/IEC Systems and software Quality Requirements and Evaluation
Tomaž Špeh SURS TF SERV, Luxembourg,
Presentation transcript:

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 we build a Test Managers toolkit to help? What would it contain? Paul Godsafe

UKTMF 27 th January 2010 Non-Functional Testing2 Reliability - The capability of software to maintain its level of performance under stated conditions for a stated period of time. –Maturity, Recoverability, Fault Tolerance Usability - The effort needed for use, and the individual assessment of such use, by a stated or implied set of users. –Learnability, Understandability, Operability Efficiency - The relationship between the level of performance of the software and the amount of resources used, under stated conditions. –Time Behaviour, Resource Behaviour Maintainability - The effort needed to make specified modifications. –Stability, Analyzability, Changeability, Testability Portability - The ability of software to be transferred from one environment to another. –Installability, Replaceability, Adaptability, Conformance (e.g. to a particular database standard) Ref. ISO 9126

UKTMF 27 th January 2010 Non-Functional Testing3 Why is Non-Functional Testing so often done badly or not at all? Need not clearly defined or understood Creates problems, not solutions –Need to define requirements –Where do you start (or end)? –Often hard to understand and/or interpret results Expensive to do –People, kit, software, time Risk/reward is hard to quantify in advance –Are you an optimist or pessimist? Solutions rarely available on demand –Cost, lead times, reliability, access to skills……. –Intermittent need

UKTMF 27 th January 2010 Non-Functional Testing4 Oh what to do, what to dooooo? what to dooooo?

UKTMF 27 th January 2010 Non-Functional Testing5 Well, we could……… Maintain an idealistic view Just complain Do nothing and accept the status quo Talk to other TMs and agree that nobody loves us Develop some pragmatic solutions based on……….

UKTMF 27 th January 2010 Non-Functional Testing6 Genuine Need, Realistic Demand and Access to solutions (tools/skills/services) Attitude to risk Commercial/operational drivers Attitude towards testing Centralised/devolved organisation What can be realistically delivered Attitude may be influenced by: –Past experience –The way you provide advice, guidance & solutions

UKTMF 27 th January 2010 Non-Functional Testing7 So can we build a Toolkit to Help? Possibly but………. A toolkit can only be used on a defined problem. Are you looking for, analysing or solving non-functional defects? In addition you may need: A strategic objective to drive the scale/scope Demand to use your toolkit –Where will the non-functional requirements come from? An interface to development projects A strategy for delivering your toolkit - self-service, internal or 3 rd party –Scalability and demand management –A delivery policy/mandate A means of payment

UKTMF 27 th January 2010 Non-Functional Testing8 Does your toolkit address the causes of inertia…. Does it define need and improve understanding? Does it provide a complete solution? Is it cost-effective? Does it deliver value-add? Is it available when needed? Virtual NFT – the power of suggestion

UKTMF 27 th January 2010 Non-Functional Testing9 The End of the Beginning