ISO/IEC Software Testing

Slides:



Advertisements
Similar presentations
Software Quality Assurance Plan
Advertisements

QuEdge Testing Process Delivering Global Solutions.
New Technologies for Tuberculosis Control: Programme Perspective Draft Definitions Retooling Task Force Meeting Geneva, Switzerland January 2008.
International Standards for Software & Systems Documentation Ralph E. Robinson R 2 Innovations.
Ossi Taipale, Lappeenranta University of Technology
1 Software Requirement Analysis Deployment Package for the Basic Profile Version 0.1, January 11th 2008.
Stepan Potiyenko ISS Sr.SW Developer.
COMP8130 and 4130Adrian Marshall 8130 and 4130 Test Design & Documentation Adrian Marshall.
SECURITY SIG IN MTS 28 TH JANUARY 2015 PROGRESS REPORT Fraunhofer FOKUS.
COMP8130 and 4130Adrian Marshall 8130 and 4130 Test Management Adrian Marshall.
Quality Manual for Interoperability Testing Morten Bruun-Rasmussen Presented by Jos Devlies, Eurorec.
ISO/IEC Software Testing
Software testing standards ISO/IEC and 33063
Test Design Techniques
OHT 2.1 Galin, SQA from theory to implementation © Pearson Education Limited 2004 Software Quality assurance (SQA) SWE 333 Dr Khalid Alnafjan
Pre-Project Activities Text Chapters 5 and 6. Pre-Project Activities 1.Contract Review 2.Development Plan 3.Quality Plan.
Software Testing Lifecycle Practice
University of Palestine software engineering department Testing of Software Systems Fundamentals of testing instructor: Tasneem Darwish.
Implementing ISO/IEC in your workplace (And why should technical communicators care about standards, anyway?) George Hayhoe Mercer University School.
Software Testing Life Cycle
OHT 25.1 Galin, SQA from theory to implementation © Pearson Education Limited 2004 The quality assurance organizational framework Top management’s quality.
CO2403 and CO3808 – Quality Management Systems Quality process definition, administration and accreditation.
ETICS2 All Hands Meeting VEGA GmbH INFSOM-RI Uwe Mueller-Wilm Palermo, Oct ETICS Service Management Framework Business Objectives and “Best.
Introduction to the ISO series ISO – principles and vocabulary (in development) ISO – ISMS requirements (BS7799 – Part 2) ISO –
Project Management Practices Vesa Tenhunen University of Eastern Finland LUMA Centre
D1.HGE.CL7.01 D1.HGA.CL6.08 Slide 1. Introduction Design, prepare and present reports  Classroom schedule  Trainer contact details  Assessments  Resources:
INFO 637Lecture #101 Software Engineering Process II Review INFO 637 Glenn Booker.
P1516.4: VV&A Overlay to the FEDEP 20 September 2007 Briefing for the VV&A Summit Simone Youngblood Simone Youngblood M&S CO VV&A Proponency Leader
Information Security 14 October 2005 IT Security Unit Ministry of IT & Telecommunications.
Requirements Management with Use Cases Module 10: Requirements Across the Product Lifecycle Requirements Management with Use Cases Module 10: Requirements.
Specific Safety Requirements on Safety Assessment and Safety Cases for Predisposal Management of Radioactive Waste – GSR Part 5.
SAM-101 Standards and Evaluation. SAM-102 On security evaluations Users of secure systems need assurance that products they use are secure Users can:
SwCDR (Peer) Review 1 UCB MAVEN Particles and Fields Flight Software Critical Design Review Peter R. Harvey.
P3 Business Analysis. 2 Section F: Project Management F1.The nature of projects F2. Building the Business Case F4. Planning,monitoring and controlling.
MIS Project Management Instructor: Sihem Smida Project Man agent 3Future Managers1.
Models of Security Management Matt Cupp. Overview What is Security Management? What is Security Management? ISO/IEC ISO/IEC NIST Special Publication.
Report to IEEE CS SESC of IEEE CS/SC7 Liaison1 Report to IEEE CS SESC: Report of IEEE CS / SC7 Liaison James W. Moore Liaison Representative IEEE.
ISO/IEC Software Testing The New International Software Testing Standard By Tafline Murnane and Stuart Reid ISO/IEC JTC1/SC7 WG26 Software Testing.
Software Engineering — Software Life Cycle Processes — Maintenance
Introduction for the Implementation of Software Configuration Management I thought I knew it all !
ISO/IEC Software Testing
Jürgen Großmann, Fraunhofer FOKUS
BIL 424 NETWORK ARCHITECTURE AND SERVICE PROVIDING.
Project Plan <Publish Date>
2012 Spring Simulation Interoperability Workshop
James W. Moore Liaison Representative IEEE Computer Society June 2004
Learn Your Information Security Management System
Security SIG in MTS 05th November 2013 DEG/MTS RISK-BASED SECURITY TESTING Fraunhofer FOKUS.
Testing Process Roman Yagodka ISS Test Leader.
Chapter 10 Software Quality Assurance& Test Plan Software Testing
TechStambha PMP Certification Training
Quality Management Perfectqaservices.
Flooding Walkdown Guidance
Standards Development: An Overview
Activities affecting HSSC
Engineering Processes
Software Measurement Process ISO/IEC
[Project Name] Project Report
Standards.
Fundamental Test Process
[Project Name] Project Report
Safety Management System Implementation
ISO TC67/SC4 Annual Meeting
X-DIS/XBRL Phase 2 Kick-Off
Engineering Processes
Software Testing Lifecycle Practice
Configuration Management

DRAFT ISO 10007:2017 Revision Overview Quality management – Guidelines for configuration management ISO/TC176 TG 01.
DRAFT ISO 10013:20XX Overview Quality management – Guidelines for quality management system documented information ISO/TC176 TG 01.
Presentation transcript:

ISO/IEC 29119 Software Testing The New International Software Testing Standard By Tafline Murnane and Stuart Reid ISO/IEC JTC1/SC7 WG26 Software Testing

Scope Overview of ISO/IEC 29119 Applicability Recent developments Timeline

Motivation for ISO/IEC 29119 Conflicts in definitions & procedures Plethora of standards to be replaced by one IEEE 829, IEEE 1008, BS 7925-1/-2, IEEE 1028 Missing in current standards: Organizational Test Policy & Strategy Project Test Management Common System & Acceptance Testing techniques Non-functional testing 3

ISO 29119 – Scope & Structure Documentation Part 3 Testing Techniques Processes Part 2 Concepts & Vocabulary Part 1 BS 7925-1 BS 7925-2 IEEE 1008 BS 7925-2 IEEE 829

Part 1: Concepts & Vocabulary Software testing concepts Introduction to software testing Relationship between testing, development & maintenance Implications of lifecycle models Approaches to testing Testing vocabulary 5

Part 2: Testing Processes Test Management Processes Static Test Processes Organisational Test Process Dynamic Test Processes

Instantiating Testing Processes

Organisational Test Process Develop test specification [Major revision required] [No change required] Draft Test Specification [No issues identified with Test Specification] Gain consensus on test specification Monitor and control use of test specification Review test specification [Issues identified or Scheduled review due Major organizational change] [Minor revision required] Approved Test Specification Publish test specification Updated Test Specification Update test specification Published Test Specification

Test Management Processes Organisational Test Process Organisational Test Documentation Feedback on Organisational Test Documentation Test Management Processes Test Plan Updates Test Completion Report Test Planning Test Plan Test Monitoring & Control Test Completion Test Plan, Control Directives Test Plan, Control Directives Test Plan, Test Completion Report, Test Measures Test Plan, Control Directives Test Measures Test Measures Static Test Processes Test Management Processes Dynamic Test Processes

Test Planning Process Understand Context Organise Test Plan Scope Organise Test Plan Development Identify & Analyze Risks Analysed Risks Identify Risk Treatment Approaches Treatment Approaches Design Test Strategy Schedule, Staffing Profile Determine Staffing and Scheduling Test Strategy Draft Test Plan Document Test Plan Approved Test Plan Gain Consensus on Test Plan Test Plan Publish Test Plan

Test Monitoring & Control Process Test Status Report Test Progress Information Test Control Information Report [Testing Incomplete] Test Plan Set-Up Test Measures Monitor Control [Testing Complete] Test Progress Info Control Directives Measures ...Test Processes... Dynamic/Static/Management

Dynamic Test Processes Test Specification [No Issues Noticed] Test Environment Readiness Report Test Environment Requirements Incident Report Test Design & Implementation Test Environment Set-up Test Execution Test Incident Reporting (Phase) Test Management Process [Issue Noticed or Retest Result] Test Results Control Directives Test Measures (Phase) Test Plan

(Phase) Test Management Process Static Test Processes (Phase) Test Management Process (Phase) Test Plan Control Directives Test Measures Static Test Processes Preparation Review Follow-Up

Example Test Process Description Described using a standard template (following ISO 24774), for example: Purpose The purpose of the Test Design & Implementation Process is to derive test procedures that will be executed during the Test Execution Process. Test conditions, test coverage items and test cases are created as part of this process. Outcomes As a result of the successful implementation of the Test Design & Implementation Process: the features to be tested are decomposed into Feature Sets; the Test Conditions are derived; the Test Coverage Items are derived; Test Cases are derived; Test Sets are assembled; Test Procedures are derived. Activities and tasks The tester shall implement the following activities and tasks in accordance with applicable organization policies & procedures with respect to the Test Design & Implementation Process. Identify Feature Sets (TD1) … Derive Test Conditions (TD2) … Derive Test Coverage Items (TD3) … Derive Test Cases (TD4) … Assemble Test Sets (TD5) … Derive Test Procedures (TD6) … Information Items As a result of carrying out this process, the following information items shall be produced: Test specifications (test design specifications, test case specifications and test procedure specifications) and related traceability information; Test data requirements; Test environment requirements.

Part 3: Documentation Organisational Project Appendices Testing Test policy Test strategy Project Project test plan Test completion report Appendices examples of documents at each level of testing Testing Test specification Test results Incident reports Test environment report Test status report Test completion report

Part 4: Techniques Test case design techniques Static Inspections, walkthroughs, etc. Dynamic Black-box, white-box, etc. Non-functional Security, performance, usability, etc. Test measurement (e.g. coverage) Appendices Examples Effectiveness

Applicability Generic standard to support all domains Some are more standards-oriented (safety, telecoms) Some will become more regulated (e.g. financial) Needs trialing in all domains & project types Waterfall, iterative, agile New & maintenance projects Information systems & embedded systems When wouldn’t you be selecting and using techniques? When wouldn’t you plan?

Typical ISO standards take over 7 years When can I start using 29119? Typical ISO standards take over 7 years ISO 12207 conceived in 1988, published in 1995, represents 17,000 person hours (8.5 person years) BS 7925-1/2 took 8 years to develop IEEE estimates 2-4 years to develop a standard, at a cost of between $2,000 and $10,000 per page [1998]

Timelines … Parts 2 & 3 Parts 1 & 4 May 08 May 09 May 10 May 11 May 12 Working Draft (WD) Committee Draft (CD) Final Committee Draft (FCD) Final Draft International Standard (FDIS) Final International Standard (FIS) Parts 2 & 3 Parts 1 & 4 May 08 May 09 May 10 May 11 May 12 … WD CD FCD FDIS FIS WD CD FCD FDIS FIS

Do you want to be involved? Join the working group through your national standards body 6 day meetings, every 6 months contribute between meetings Join the national working group in your country to: contribute materials review drafts

Conclusions International standard will provide practitioners with guidelines for testing that cover all aspects of life cycle Consistent definitions, processes, procedures & techniques for testing Will be adopted by IEEE, ISO, Standards Australia and other national standards bodies Currently has representation from 18 nations & is being reviewed by software testing professionals world-wide We need to ensure widespread applicability

Thanks….