Software testing techniques Testing Maturity Model Presentation on the seminar Kaunas University of Technology.

Slides:



Advertisements
Similar presentations
Software Engineering CSE470: Process 15 Software Engineering Phases Definition: What? Development: How? Maintenance: Managing change Umbrella Activities:
Advertisements

More CMM Part Two : Details.
©2006 OLC 1 Process Management: The Foundation for Achieving Organizational Excellence Process Management Implementation Worldwide.
Software Process Improvement Robin B. Hunter, Ph.D. Vol 2., p Presented by: Andrew Wheeler.
Process Improvement.
R R R CSE870: Advanced Software Engineering (Cheng): Intro to Software Engineering1 Advanced Software Engineering Dr. Cheng Overview of Software Engineering.
SEI White Paper: Process Maturity Model Present by Hui Huang November 16, 2000 ® CMM is Registered in the US Patent and Trademark Office.
Capability Maturity Model (CMM) Done By :Delayel Alhajeree.
Computer Engineering 203 R Smith Agile Development 1/ Agile Methods What are Agile Methods? – Extreme Programming is the best known example – SCRUM.
Iterative development and The Unified process
Chapter 3 The Structure of the CMM
Quality evaluation and improvement for Internal Audit
CMMI Overview Quality Frameworks.
Software Process CS 414 – Software Engineering I Donald J. Bagert Rose-Hulman Institute of Technology December 17, 2002.
Organizational Project Management Maturity: Roadmap to Success
Cleanroom Software Engineering Crystal Donald. Origins Developed by Dr. Harlan Mills in 1987 Developed by Dr. Harlan Mills in 1987 Name derived from hardware.
Standardization. Introduction A standard is a document. It is a set of rules that control how people should develop and manage materials, products, services,
Lecture 11 CMM CSCI – 3350 Software Engineering II Fall 2014 Bill Pine.
8/27/20151NeST Controlled. 2 Communication Transportation Education Banking Home Applications.
Integrated Capability Maturity Model (CMMI)
Strengthening the quality of research for policy engagement in the African context – achievements and aspirations Tebogo B. Seleka Botswana Institute for.
COMPGZ07 Project Management Presentations Graham Collins, UCL
Capability Maturity Model. Reflection Have you ever been a part of, or observed, a “difficult” software development effort? How did the difficulty surface?
Org Name Org Site CMM Assessment Kick-off Meeting Dates of assessment.
Dillon: CSE470: SE, Process1 Software Engineering Phases l Definition: What? l Development: How? l Maintenance: Managing change l Umbrella Activities:
N By: Md Rezaul Huda Reza n
1 Chapter 2 The Process. 2 Process  What is it?  Who does it?  Why is it important?  What are the steps?  What is the work product?  How to ensure.
J. R. Burns, Texas Tech University Capability Maturity Model -- CMM n Developed by the Software Engineering Institute (SEI) in 1989 –SEI is a spinoff.
Software Engineering - Spring 2003 (C) Vasudeva Varma, IIITHClass of 39 CS3600: Software Engineering: Standards in Process Modeling CMM and PSP.
Software Engineering Lecture # 17
CSI - Introduction General Understanding. What is ITSM and what is its Value? ITSM is a set of specialized organizational capabilities for providing value.
Design engineering Vilnius The goal of design engineering is to produce a model that exhibits: firmness – a program should not have bugs that inhibit.
University of Sunderland CIFM03Lecture 2 1 Quality Management of IT CIFM03 Lecture 2.
Adaptive Processes Overview Adaptive Processes©. Adaptive Processes © Adaptive ProcessesSimpler, Faster, Better2 Objective To provide an over view of.
Quality Concepts within CMM and PMI G.C.Reddy
Software Requirements: Overview and Motivation Gruia-Catalin Roman and Christopher Gill CSE 436 January 2007 Department of Computer Science and Engineering.
© 2001 Change Function Ltd USER ACCEPTANCE TESTING Is user acceptance testing of technology and / or processes a task within the project? If ‘Yes’: Will.
SWEN 5130 Requirements Engineering 1 Dr Jim Helm SWEN 5130 Requirements Engineering Requirements Management Under the CMM.
©Ian Sommerville 2004 Software Engineering. Chapter 28Slide 1 Chapter 28 Process Improvement.
The Role of Experience in Software Testing Practice Zahra Molaei Soheil Hedayatitezengi Comp 587 Prof. Lingard 1 of 21.
CMMI. 1.Initial - The software process is characterized as ad hoc, and occasionally even chaotic. Few processes are defined, and success depends on individual.
Introduction to the Continual Service Improvement Toolkit Welcome.
Ch-1 Introduction The processes used for executing a software project have major effect on quality of s/w produced and productivity achieved in project…
Level 1 Level 1 – Initial: The software process is characterized as ad hoc and occasionally even chaotic. Few processes are defined, and success depends.
Page 1 The Capability Maturity Model (CMM) distinguishes between immature and mature software organizations. Immature software organizations are typically.
27/3/2008 1/16 A FRAMEWORK FOR REQUIREMENTS ENGINEERING PROCESS DEVELOPMENT (FRERE) Dr. Li Jiang School of Computer Science The.
Testing Maturity Model (TMM). Introduction For the past decade, the software industry has put substantial effort in improving the quality of its products.
Making knowledge work harder Process Improvement.
SOFTWARE PROCESS IMPROVEMENT SHARATH CHANDAR REDDY ALETI CSC 532 TERM PAPER.
SOFTWARE PROCESS IMPROVEMENT
Unit – I Presentation. Unit – 1 (Introduction to Software Project management) Definition:-  Software project management is the art and science of planning.
COMPGZ07 Project Management CMMI Project Planning Lecture 5b Graham Collins, UCL.
MSA Orientation – v203a 1 What’s RIGHT with the CMMI?!? Pat O’Toole
UNIT 5.
CMMI Overview Quality Frameworks. Slide 2 of 146 Outline Introduction High level overview of CMMI Questions and comments.
Done By: Asila AL-harthi Fatma AL-shehhi Fakhriya AL-Omieri Safaa AL-Mahroqi.
1 These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 5/e and are provided with permission by.
1 Software Engineering Muhammad Fahad Khan Software Engineering Muhammad Fahad Khan University Of Engineering.
Advanced Software Engineering Dr. Cheng
Transforming Organizations to achieve TMMi certification
Mgt Project Portfolio Management and the PMO Module 8 - Fundamentals of the Program Management Office Dr. Alan C. Maltz Howe School of Technology.
EITS Planning & Decision Support
CMMI Overview Quality Frameworks.
The Project Management Framework
Level 1 Level 1 – Initial: The software process is characterized as ad hoc and occasionally even chaotic. Few processes are defined, and success depends.
CMMI Overview.
Ethical and Sustainable Sourcing
Software Quality Assurance
Software Engineering Lecture 16.
Software Engineering I
Presentation transcript:

Software testing techniques Testing Maturity Model Presentation on the seminar Kaunas University of Technology

Introduction For the past decade, the software industry has put substantial effort in improving the quality of its products. This has been a difficult job, since the size and complexity of software increases rapidly while customers and users are becoming more and more demanding. Despite encouraging results with various quality improvement approaches, the software industry is still far from zero defects. To improve product quality, the software industry has much focused on improving their development processes. The TMM is a detailed model for test process improvement and is positioned as being complementary to the CMM.

Scope of the TMM Software and System Engineering Test levels TMM and CMM Assessments Improvement Approach

Software and System Engineering The TMM is intended to support testing activities and test process improvement in both the systems engineering and software engineering discipline. Systems engineering covers the development of total systems, which may or may not include software. Software engineering covers the development of software systems.

Test levels Whereas some models for test process improvement focus mainly on high-level testing or address only one aspect of structured testing e.g. the test organization, The TMMi addresses all test levels (including static testing) and aspects of structured testing. With respect to dynamic testing, both low-level testing and high-level testing are within the scope of the TMMi. Studying the model more in detail one will learn that the model addresses all four cornerstones for structured testing (lifecycle, techniques, infrastructure and organization).

TMM and CMM It is also important to note that TMM is positioned as a complementary model to the CMM. In many cases a given TMM level needs specific support from process areas at its corresponding CMM level or from lower CMM levels. In exceptional cases there is even a relationship to higher CMM levels. Process areas and practices that are elaborated within the CMM are mostly not repeated within TMM; they are only referenced. For example the process area configuration management, which is of course also applicable to test (work) products / test ware, is not elaborated upon in detail within the TMM; the practices from CMM are referenced and implicitly re-used.

Assessments Many organizations find value in benchmarking their progress in test process improvement for both internal purposes and for external customers and suppliers. Test process assessments focus on identifying improvement opportunities and understanding the organization’s position relative to the selected model or standard. The TMM provides an excellent reference model to be used during such assessments. Assessment teams use TMM to guide their identification and prioritization of findings. These findings with guidance of TMM practices are used to plan improvements for the organization. The assessment framework itself is not part of the TMM.

Improvement Approach The TMMi provide a full framework to be used as a reference model during test process improvement. It does not provide an approach for test process improvement such as the IDEAL4 (Initiating, Diagnosing, Establishing, Acting, And Learning) model. Practical experiences have shown that the most powerful initial step to test process improvement is to build strong organizational sponsorship before investing in test process assessments. Given sufficient senior management sponsorship, establishing a specific, technically competent test process group that represents relevant stakeholders to guide test process improvement efforts had proved to be an effective approach.

TMM Maturity Levels

Level 1 Initial Testing is chaotic and undefined process Testing is often considered a part of debugging The organization usually does not provide a stable environment to support the processes

Level 2 Managed The process areas at TMM level 2 are: 2.1 Test Policy and Strategy 2.2 Test Planning 2.3 Test Monitoring and Control 2.4 Test Design and Execution 2.5 Test Environment

Level 3 Defined The process areas at TMM level 3 are: 3.1 Test Organization 3.2 Test Training Program 3.3 Test Lifecycle and Integration 3.4 Non-Functional Testing 3.5 Peer Reviews

Level 4 Management and Measurement The process areas at TMMi level 4 are: 4.1 Test Measurement 4.2 Product Quality Evaluation 4.3 Advanced Peer Reviews

Level 5 Optimization Process areas at level 5 are: 5.1 Defect Prevention 5.2 Test Process Optimization 5.3 Quality Control

Conclusion Test process improvement is a journey. The TMM just makes that journey easier. Test process improvement should not be considered as being in addition to any other process improvement initiative, but should work in conjunction with that initiative. The TMM is laid out in incremental steps because that is the best way to make the improvements. Very few companies have the resources to try to do everything at one time. Experience has shown the incremental approach is the most successful. Just because it is laid out incrementally does not mean that you cannot start working on an improvement at the next level.

Literature TMMi® TMMi® Reference Model ( pdf) pdf Introduction to the Testing Maturity Model Enhanced (TMMe) ( 0to%20the%20Testing%20Maturity%20Model%20Enhance.pdf) 0to%20the%20Testing%20Maturity%20Model%20Enhance.pdf

Thank you.