We think you have liked this presentation. If you wish to download it, please recommend it to your friends in any social system. Share buttons are a little bit lower. Thank you!
Presentation is loading. Please wait.
Published byAshly Medley
Modified about 1 year ago
© 2006 Macrovision Corporation | Company Confidential Continuous Testing in an Agile Environment Nan Krull Manager, Software Quality
2© 2006 Macrovision Corporation | Company Confidential Macrovision enables businesses reliant on the deployment of software or content to secure, adapt and optimize their offering among digital distribution channels and destination devices. Who is Macrovision? NASDAQ: MVSN, founded 1983, public since 1997 Global leader in Digital Value Management Solutions Best-of-breed solutions include technologies such as: –FLEXnet (Software Licensing) –InstallShield/InstallAnywhere (Software Distribution) –ActiveReach / Trymedia / eMeta (DRM) 70,000+ customers 1,200+ patents Offices in the US, UK, France, Germany, Korea, Hong Kong, Japan
3© 2006 Macrovision Corporation | Company Confidential FLEXnet AdminStudio Enterprise suite of applications for repackaging, customizing, testing and deploying application packages in Windows Installer (MSI) environments Enterprise clients include international banks, airlines, software companies – their needs are complex and urgent. AdminStudio must maintain the highest quality standards in order to exceed client expectations.
4© 2006 Macrovision Corporation | Company Confidential Approaches to Quality Linear, Sequential QA planning occurs late No test case review Emphasis on bug fixing
5© 2006 Macrovision Corporation | Company Confidential Approaches to Quality – Continuous Testing QA begins at Requirements, Design QA test planning parallels Dev Feature Test Plan reviewed Feature Test Execution starts sooner Cost-effective bug removal Requires integrated QA and Dev effort
6© 2006 Macrovision Corporation | Company Confidential Approaches to Quality
7© 2006 Macrovision Corporation | Company Confidential Good – but not good enough Defects fixed after Feature Development is complete The “big picture” view of certain risk areas may not be clear until the end of Feature Development Late defect fixing creates risk of breakage Late identification of defects and breakage means a higher number of defects in the released product
8© 2006 Macrovision Corporation | Company Confidential Approaches to Quality – Agile Environment QA begins at Requirements, Design QA test planning parallels Dev Feature Test Plan reviewed Feature Test Execution starts sooner Cost-effective bug removal Requires integrated QA and Dev effort In an Agile environment, as the process is compressed these benefits are accelerated.
9© 2006 Macrovision Corporation | Company Confidential Agile Environment Granular: User Stories, not Features Daily stand-up meetings keep information flowing Code is tested as soon as it’s done Code is fixed before more code is written Agile may appear more casual – but executing “Agile” requires discipline, communication and teamwork.
10© 2006 Macrovision Corporation | Company Confidential Continuous Testing in an Agile Environment
11© 2006 Macrovision Corporation | Company Confidential What difference does really it make? Significantly improved product quality Reduced Risk Production Cost Savings
12© 2006 Macrovision Corporation | Company Confidential Assessing Quality 83%* of bugs originate in the Requirements and Design stages of a project. Approx. half of software development effort is spent on testing. *Quality Assurance Institute, 2006 **Economics of Continuous Testing, Stephen A. Bender, The Quality Connection, 2006
13© 2006 Macrovision Corporation | Company Confidential AdminStudio – Improved Product Quality
14© 2006 Macrovision Corporation | Company Confidential AdminStudio – Improved Product Quality
15© 2006 Macrovision Corporation | Company Confidential Economics of Continuous Testing* Requirements (50%) 20 errors injected Defect cost=$1 Design (50%) 20 errors injected Defect cost=$1 Code (50%) 20 errors injected Defect cost=$1 Test 80% errors detected Defect cost=$10 Production ”0” Defects Defect cost=$100 Continuous Testing Accumulated Accumulated Errs Remaining Total Cost 10 $10 15 $25 18 $42 4 $182 0 $582 Traditional Testing Accumulated Test Cost Errs Remaining $0 20 0 40 0 60 $480 12 $1680 0 *Economics of Continuous Testing, Stephen A. Bender, The Quality Connection, 2006
16© 2006 Macrovision Corporation | Company Confidential Agile maximizes Continuous models Early QA involvement prevents defects: –Fixing defects costs less than releasing them –Preventing defects cost less than fixing them! Agile results in earliest possible ID of: –Critical Issues –Breakage Development gets immediate feedback on quality of each piece of code – and fixes it before coding the next piece! System Test results in more stable builds and less time handling issues
17© 2006 Macrovision Corporation | Company Confidential Results Higher quality product Lower risk of releasing defects Lower defect handling costs Earlier flagging of issues which impact the schedule Better Quality = Satisfied Customers, Increased Demand Everybody Wins!
Software Process CS 414 – Software Engineering I Donald J. Bagert Rose-Hulman Institute of Technology December 17, 2002.
Agenda: Overview of Agile testing Difference between Agile and traditional Methodology Agile Development Methodologies Extreme Programming Test Driven.
(c) 2007 Mauro Pezzè & Michal Young Ch 1, slide 1 Software Test and Analysis in a Nutshell.
Accelerating Product and Service Innovation © 2013 IBM Corporation IBM Integrated Solution for System z Development (ISDz) Henk van der Wijk 23 Januari.
Object-Oriented Analysis and Design Iterative Development and the Unified Process.
1 Object-Oriented Analysis and Design with the Unified Process Figure 13-1 Implementation discipline activities.
DNN LOVES JENKINS FOR CONTINUOUS INTEGRATION Steffen & Simon.
INFO 636 Software Engineering Process I Prof. Glenn Booker Week 9 – Quality Management 1INFO636 Week 9.
Extreme Programming Team Members Gowri Devi Yalamanchi Sandhya Ravi.
Manage your technology for optimal return on investment (ROI) The Tivoli ® Configuration & Operations management solution from IBM.
VCU Information Systems Institute Advanced Delivery Methodology Courtesy of Data Management That Works.
The software systems must do what they are supposed to do. “do the right things” They must perform these specific tasks correctly or satisfactorily.
SAM for Virtualizatio n Presenter Name. Virtualization: a key priority for business decision makers Technavio forecasts that the global virtualization.
Levels of Software Applications Up to now we have focused on testing techniques at the unit (or program) level. In any medium to large software systems,
Motorola Mobility Services Platform Management Software: Stage Edition.
© 2014 IBM Corporation Smarter Workforce Services Business Process Innovation.
© 2009 IBM Corporation Maximize Cost Savings While Improving Visibility Into Lines of Business Wendy Tam, CDC Product Marketing Manager
12. 2 Object-Oriented Analysis and Design with the Unified Process Objectives Describe implementation activities Describe various types of software.
CS 3500 SE - 1 Software Engineering: It’s Much More Than Programming! Sources: “Software Engineering: A Practitioner’s Approach - Fourth Edition” Pressman,
Mantychore FP7 WP4 (SA1) - Software Refinement. Objectives Main duties – Analysis of User Requirements – Implementation – Support and bug fixing This.
1 Software Process Models Lecture Waterfall Model for Development Here, steps (phases) are arranged in linear order –A step take inputs from previous.
Software Quality Assurance Chip Ene, February 14, 2015.
Computer Engineering 203 R Smith Agile Development 1/ Agile Methods What are Agile Methods? – Extreme Programming is the best known example – SCRUM.
Industry SDLCs and Business Climate. Justin Kalicharan Credentials Director and Senior Technology Officer Over 14 years of coding experience in various.
1 COMP 350: Object Oriented Analysis and Design Lecture 2Iterative, Evolutionary and Agile References: Craig Larman Chapters 1-2.
Copyright 2002, Medical Present Value, Inc. All rights reserved. Copyright © 2010 Texas Education Agency. All rights reserved. TEA confidential and proprietary.
Chapter 4 Quality Assurance in Context SE Software Testing and Quality Assurance 1.
MIS 2000 Class 20 System Development Process Updated 2014.
Object-oriented Analysis and Design Stages in a Software Project Requirements Writing Analysis Design Implementation System Integration and Testing Maintenance.
Rational Unified Process Mr Hisham AlKhawar. Iterative versus Waterfall We need to use a life cycle model in order to approach developing a system easily,
Agile-SCRUM. Introduction to SCRUM Sanil Xavier What is Scrum?
Chapter 15 GIS Design and Implementation Management Information Systems –Systems Analysis –Systems Design –Systems Implementation.
WATERFALL DEVELOPMENT MODEL. Waterfall model is LINEAR development lifecycle. This means each phase must be completed before moving onto the next!!! WHAT.
The Long Tail Why the future of business is selling less of more ▫ISBN = ▫Chris Anderson Low Distribution and Inventory costs allow companies.
1. Windows Vista Enterprise And Mid-Market User Scenarios 2. Customer Profiling And Segmentation Tools 3. Windows Vista Business Value And Infrastructure.
Review: Agile Software Testing in Large-Scale Project Talha Majeed COMP 587 Spring 2011.
Chapter 3: Software Maintenance Process Omar Meqdadi SE 3860 Lecture 3 Department of Computer Science and Software Engineering University of Wisconsin-Platteville.
SE382 Software Engineering Lecture 21b Review Techniques (1)
QA Transformation “Get on board or risk NOW!” Ray Scott QA Transformation Consultant
Software Design & Production Methodologies STRUCTURED & OBJECT-ORIENTED METHODS for SYSTEMS ANALYSIS & DESIGN Vassilka Kirova Computer & Information Science.
Week # 4 Quality Assurance Software Quality Engineering 1.
Iterative development and The Unified process Chapter 2 Applying UML and Patterns -Craig Larman.
Software Quality Assurance Inspection by Ross Simmerman Software developers follow a method of software quality assurance and try to eliminate bugs prior.
Short Customer Presentation September The Company Storgrid delivers a secure software platform for creating secure file sync and sharing solutions.
Chapter 05 Quality Planning SaigonTech – Engineering Division Software Project Management in Practice By Pankaj Jalote © 2003 by Addison Wesley.
Software Testing Software Testing – is a process of software analysis and defect detecting. Actions of defect detecting are directed to defining as many.
Herriman High Computer Programming 1A Software Development Cycle Things to Know.
This has been created by QA InfoTech. Choose QA InfoTech as your Automated testing partner. Visit for more information.
Chapter 2 Iterative, Evolutionary, and Agile You should use iterative development only on projects that you want to succeed. - Martin Fowler 1CS
SOA Management Packs & Governance Cheat Sheet (Shared under OPN NDA - Last Updated: 8/3/2009)OPN NDA Target Account Profile Enterprises that: Have IT infrastructure.
© 2017 SlidePlayer.com Inc. All rights reserved.