RBT Framework Coupled with Keyword-driven Test Design Approach
|
|
- Aron Price
- 8 years ago
- Views:
Transcription
1 RBT Framework Coupled with Keyword-driven Test Design Approach Authors : Arindam Bhattacharyya Test Manager Zeba Khan Technical Consultant Dr. Anil Kumar Thacker Manager Technology Solution
2 ABSTRACT Testing is potentially a risk-based activity. The fact is, one can t test everything equally, and even if one could, it would be too expensive. The Risk Based Testing (RBT) approach helps in identification of risk factors associated with the testing. Various RBT models and approaches available today talk about assessing and calculating risks associated with the test scenarios for a system under test. These studies have described risk calculation for test cases by considering various factors from both business and technical perspectives. Once identified, the risks are prioritized based on their impact and likelihood of occurrence and relevant test cases are designed and executed accordingly. This paper presents an approach for risk analysis, prioritization, and combines keyword driven test scenario design using an extended RBT approach. This approach enables risk monitoring and continuous adjustment of testing effort and resources. The paper also briefly reviews various RBT approaches, discusses associated challenges, and describes the benefits of the extended RBT approach, and possible future enhancements. KEYWORDS Risk based testing, Keyword driven approach, Testing framework, Test scenario design INTRODUCTION Testing is a time and effort intensive activity. Studies indicate that about 40 percent of the effort is spent during pre-testing phase, 40 percent in testing phase, and about 20 percent of the effort is consumed in post-testing phase. In many organizations, software testing accounts for 30 to 50 percent of software development costs. Yet most people believe that software is not well tested before it is delivered 1 According to Boehm about 80 percent of the defects come from 20 percent of the modules, and about half the modules are defect free. 2 Therefore, in order for a project to be successful, testers must decide which parts of the system need to be thoroughly tested, and this requires careful analysis of the risks involved. 1 2 Heumann Jim, Generating Test Cases from Use Cases, 2001, _cases_jh.html Boehm B.W., and V.R. Basili (2001, January). Software Defect Reduction Top 10 List. Computer, 34, Software testing is a quality control and engineering activity to ensure the correctness, completeness and reliability of any program or software application. The main purpose of testing is to evaluate the attributes and capabilities of a program, or a software application or a system and determine that it meets expected results, and user requirements. 3 However, often testing is carried out late in the development lifecycle, and under constrained time and budget. As a result, everything planned cannot be tested. In this context, it becomes important to determine the amount of testing to be performed based on the risks associated with the application components. This requires careful analysis of the risks involved. These risks can arise from the newness and reliability of the technology being used, the nature of the application, or from the priority of the business functions under test. The amount of testing that should be performed is directly related to the amount of risk involved. Understanding the risk-based nature of testing is also the key to dealing with chronic problem of inadequate test resources. Risk must be used as the basis for allocating the test time that is available, and for helping to make the selection of what to test and how to allocate resources. 4 Many researchers are investigating Risk Based Testing approach and techniques. Their research spans a wide variety of topics. There are several ways to carryout Risk Based Testing. Some of the prominent RBT approaches or models are discussed below. RBT consists of a set of activities regarding risk factors identification related to software requirements and testing. Once identified, the risks are prioritized according to their likelihood and impact. The test cases are designed based on the strategies for treatment of the identified risk factors. The testing efforts are continuously adjusted according to risk monitoring. 5 Software testing consultant Stale Amland in a case study on risk based testing described: The probability of fault for each function P(f) were estimated. This depended on whether the code was changed, if there was new functionality, the design Hetzel, William C., The Complete Guide to Software Testing, 2nd ed. Publication info: Wellesley, Mass.: QED Information Sciences, ISBN: Physical description: ix, 280 p. Guide CSTE Common Body Of Knowledge, V6.1 Ellen Souza, Cristine Gusmao, Julio Venancio, "Risk-Based Testing: A Case Study," pp , 2010 Seventh International Conference on Information Technology, 2010
3 quality, the size and the complexity. These factors were given weights from one to five, where the higher are the most important indicator of a function with poor quality. Then, for each function of the system the probability for all indicators is then considered given values from one to three. The weights and values for each function are multiplied. The probability is calculated as the Weighted Average of a weighted function divided by the highest Weighted Average of all functions. This gave a probability numbers between zero and one. The risk exposure for each function RE(f) was calculated by multiplying the cost of fault and the probability using the formula: RE(f) = P(f) * ( C(c) + C(v) ) / 2 The testing resources where focused on the functions with the highest risk exposures. 6 Once the Risk Exposure is computed, testing risks are prioritized based on RE value. Then steps to control the risk are planned. Software testing guru James Bach in his seminal work Heuristic Risk Based Testing, stresses on human experience to find the most risky areas. Bach presents two approaches to heuristic Risk-Based testing, inside-out and outside-in. In inside-out the tester studies the product together with the developer and asks questions such as What can go wrong here? For each part of the product the tester will look for vulnerabilities, threats and victims. Outside-in begins with a set of potential risks and matches them to the details of the situation. A list of predefined risks is consulted and used to determine whether they apply here and now. Finally, Bach prescribes three ways to organize testing risk, viz., risk watch list (lists of quality criteria categories), risk task list (generic risk list), and component risk metrics (risk catalogues). He concluded in his study report: Management may assume that you did a sloppy job, and they may not be impressed with the standard argument that all testing is incomplete. That s when it s nice to have that risk list or matrix. With risk-based testing, you can show management that you strive to make the best use of the resources they invest. They ll respect you for that. 7 Stephen Besson, Research and Development Director of Karat Software (and now Freeborders) describes how to carry out Risk-Based testing by prioritizing the most vital functions. The method starts by identifying vital functions that may have faults of high severity. The severity is defined by measuring the negative impact a fault has on the business, high, medium or low. If the user cannot work with the software and wastes time and money because of the failure, the severity is considered to be high. Besson says, However, if you see testing as an investment, the strategy becomes: What is the minimum testing effort that I should invest in order to maximize risk reduction? 8 Chen a computer science graduate from School of Information Technology and Engineering, Canada and software engineering scholar at IBM has presented a specification-based (black box) regression test selection technique. This technique is customeroriented and also risk-based. It provides methods to obtain both Targeted Tests and Safety Tests. The case study indicates that the technique is effective in finding defects. Regression testing is terminated whenever we run out of time and resources. The final selected regression test suite is the union of the Targeted Tests and Safety Test 9 Other scholarly studies by Garrard talks about the RBT for testing of e-business apps and Schaefer has given approach for prioritizing tests against deadlines. The studies reviewed above uses risk priority to identify critical tests. Most of them use similar methods as described by Amland, where the factors that can increase the cost and consequences of failure for some parts of the product are found. Cost in respect of maintenance, legal issues, and reputation for the vendor and loss of customer is considered. Schaefer and Besson look at what functions have the highest importance and cause bigger inconveniences of failure for the user. Schaefer used defect generators to predict the most defective parts of the system and applied risk based testing. Besson verified the degree of failure that could prevent the user from using the system and frequencies of use to prioritize what to test. Chen used similar ideas as Amland and focused on test cases and not functions of the applications. The risk analysis helps decide what functions to put extra effort for testing, but could also be used to decide what functions not to test. This paper gives an overview of the different Risk Based Testing approaches currently present. 6 7 Stale Amland, Risk Based Testing and Metrics, November 1999, James Bach, Heuristic Risk-Based Testing, Software Testing and Quality Engineering Magazine, 11/99, Besson Stephen, A Strategy for Risk-Based Testing, StickyMinds.com, 2013 Chen Y, Probert R L, Sims D P, Specificationbased Regression Test Selection with Risk Analysis, Tech Journal IBM Canada, 2002.
4 CURRENT RBT APPROACH Most of the RBT approaches available today emphasize on assessing and calculating the risks associated with the test scenarios for a SUT (System under test). Various factors are considered from both business and technical aspects to prioritize test scenarios. These approaches have described Risk factor calculation for test cases in scope. This paper presents a unified approach of how RBT can be implemented in collaboration with business, technical and quality personnel in an organization. It also shows the value-ads in terms of earned confidence of the SUT at each milestone of the execution cycle. RBT in conjunction with Keyword- Driven Test Scenario design approach helps in improvement of review efficiency and reusability. This approach can be adopted by an organization irrespective of domain and technology. The following sections in this paper explain the approach with an example for an Airlines Reservation System. KEYWORD-DRIVEN Coupled with RISK BASED TESTING APPROACH This paper presents a concept of an extended approach to implementing a risk-based testing approach around following areas; a) Test Scenario Design using Keyword driven approach b) Risk Analysis c) Risk-based test prioritization d) Resource management e) System Confidence level at each interval What is a Risk? The possibility of an unfavorable event occurring is defined as a Risk. It can be defined in terms of two components: the probability that this situation may occur and its impact. Why Risk Based Testing? Risk based testing approach assesses all the test scenarios in scope for the risk associated with these scenarios not being tested. High priority scenarios can be tested earlier for an increased confidence in the system leading to possible early go-live targets. Risk Based Testing Assumptions Not all the tests have the same importance o Some tests significantly reduce the risks associated with going live o Other tests provide little value Confidence in the system is driven by executing the important tests and removing defects, not by running thousands of low value tests successfully Projects can go live quicker and at a lower cost if focus (i.e. time, priority, resources) is spent on highest risk areas, and not wasted on areas where failures are low impact and least probable. a) Keyword Driven Test Scenario Design Approach This approach provides a simple and effective way to design test cases for a given testing project based on the key attributes defining the scope of the project. All these attributes are then listed down along with their possible values. A combination of these values would define a high-level test scenario. An example of this approach is as stated below: Online Airline Reservation Application Key-word options Benefits of using Keyword Driven approach for test scenario design: Figure 2 Figure 1 Less time consuming and easy to understand approach Easy to review Provides a good coverage of all the possible test scenarios Easy to maintain Once the High Level Test Scenario design is complete, we would move to our next step of conducting a workshop with the Business Analysts/Business Architects and Technical Architects. b) Workshop on Risk Based Testing with BAs and TAs
5 This workshop should be conducted with the Business Analysts and the Technical Architects to discuss the overall Risk Based Testing Approach and their role in achieving accurate risk evaluation on the High-level Test Scenarios. Business Analysts should define the Impact of Failure for the high-level test scenarios under evaluation. Following factors are to be considered for defining the Impact: Halt - when there is no workaround for the business process in case of any failure. Visible when the failure of a particular business would be very visible. However, there can be a workaround for the same. Minor when the failure of a business case does not directly impact the customer. Technical Architects should define the Likelihood of Failure for the high-level test scenarios under evaluation. Following factors are to be considered for defining the Likelihood: Maturity of Technology, Integration of Technology, Complexity of Solution, Areas of heavy load, Complexity of code, High number of Interfaces. Once this evaluation is complete, the output should be fed into the next step, Build Matrix to analyze the Risk based on BA/TA evaluation. c) Risk Analysis Risk Analysis is at the heart of risk-based testing. This is performed using a 3x3 grid to distinguish high value tests (top right) from low value tests (bottom left). Each area of functionality or non-functionality is assessed in terms of likelihood of failure (If not tested) and impact of failure (as perceived by the end customer). The Analysis is to be performed on highlevel scenarios. i. Step (b) should be repeated with BAs and TAs ii. Once revised evaluation is received, Step (c) should be repeated. iii. Project Scope/Requirements should be assessed for a need to be tested. d) Prioritize Test Scenarios Scope Identification Based on the Analysis done in the previous step, the High-level Test Scenarios are then prioritized considering the factors defined in the grid explained above (Figure 3). Following grid (Figure 4) extends the analysis by prioritizing the high-level scenarios. Prioritization will depend on the project. For example, when a project uses commonly used code/components, Highly Probable-Visible scenarios may have higher priority over Probable-Halt scenarios. In general, top-right is more important than bottom-left where 1 being the highest on priority and 5 being the lowest. The most important tests should be tested thoroughly, perhaps with additional ad hoc tests. Priority 3s may have normal testing, while priority 4 tests could be simplified to touch or identification tests. Priority 5 tests may be de-scoped. This MUST be agreed between the Project and Business, who must accept the trade-off between an earlier go-live versus 100% testing. Figure 4 Figure 3 All the High-level Scenarios are categorized in each of these cells (in Figure 3) based on the evaluation from previous step. After Categorization, the number of scenarios in each of the cells is to be assessed. Most of the Scenarios should fall in top right half of the grid. In case an inverted trend is observed, following steps should be followed: e) Build Test Schedule After a thorough analysis on the risk associated with all the scenarios and their prioritization, a test schedule is prepared planning for the high-priority scenarios during the initial phases of testing and then moving on the low-priority test cases providing an efficient coverage of test scope. f) Resource Planning The Resource allocation should be aligned with the Test Scenario Prioritization Grid (Figure 5). The most experienced resources should be aligned with the high priority test scenarios, with new/less experienced resources being their backup. However, less experienced resources should be aligned with the lower priority scenarios and more experienced
6 resources being their back up. The following grid provides a pictorial view for Resource Allocation. Placing your best people (whether designers, developers or testers) on the most important tests can improve the chances that 1) designs will be through, complete and unambiguous, 2) code will be accurate and c) tests will be effective. g) Checkpoints Figure 5 Checkpoints should be established to assess the test coverage vs. the earned confidence. The test coverage would give the number of test cases executed, whereas, the earned confidence would give the confidence level in the system based on successful execution of high priority scenarios earlier. The graph (Figure 6) gives some more detail on the earned confidence vs. test completion. As the graph suggests, higher level of confidence can be achieved with lesser test coverage to enable incremental and early delivery of the well-tested system. Future Enhancements Risk-based testing is mistakenly thought of as an execution prioritization technique. In fact, it can provide a range of benefits across all phases of a project. It is never too late to perform a risk analysis, to prioritize work, allocate resources, expedite or report confidence in the system. RBT is SDLC Agnostic The Risk-based testing is consistent with prioritybased methodologies including Agile, Waterfall etc.: The emphasis is on supplying working software The approach encourages the business and technical communities to collaborate and share a collective view of risks, impacts and priorities. Risk based analysis provides a prioritized list of test scenarios (not a Test Plan) that can drive iteration priorities, resource allocation and level of testing conducted. The approach ensures that the most important tests are conducted first. Confidence in the system is gained fast. Figure 6
7 Although the case results are encouraging, implementing this approach may require fine-tuning for production fixes and minor enhancements. CONCLUSION Figure 7 This paper has introduced a new testing risk prediction technique that works at granularity level in combination with the key word driven testing. The metrics collected after implementing Keyword Driven approach reveals about 60% reduction in the review effort, and 48% improvement in reusability. The data collected during execution cycle by implementing RBT shows that 99% confidence was achieved by executing 65% of the test cases. Additionally, this work provides an evaluation of the relative contributions of various RBT approaches. ACKNOWLEDGEMENT Authors would like to acknowledge and extend heartfelt gratitude to all the Business partners, Technical architects and the Testing team for implementing this approach. And lastly to our family and friends who made this possible. About HTC HTC Global Services Inc., is an IT solutions provider, focusing on providing business value to our clients through information Technology (IT) and Business Process Outsourcing (BPO) services and solutions. An Inc 500 Hall of Fame Company and Certified Minority-Owned Business, HTC delivers business solutions to customers through combination of process excellence, quality frameworks, and service delivery innovation.
Adopting Agile Testing
Adopting Agile Testing A Borland Agile Testing White Paper August 2012 Executive Summary More and more companies are adopting Agile methods as a flexible way to introduce new software products. An important
More informationQuality Assurance - Karthik
Prevention is better than cure Quality Assurance - Karthik This maxim perfectly explains the difference between quality assurance and quality control. Quality Assurance is a set of processes that needs
More informationAgile Scrum Workshop
Agile Scrum Workshop What is agile and scrum? Agile meaning: Able to move quickly and easily. Scrum meaning: a Rugby play Agile Scrum: It is an iterative and incremental agile software development framework
More informationTesting Metrics. Introduction
Introduction Why Measure? What to Measure? It is often said that if something cannot be measured, it cannot be managed or improved. There is immense value in measurement, but you should always make sure
More informationCalculation of Risk Factor Using the Excel spreadsheet Calculation of Risk Factor.xls
Calculation of Risk Factor Using the Excel spreadsheet Calculation of Risk Factor.xls Events, Impact and Software Validation Table of Contents Many software products in complex computer systems like LIS
More informationThe Software Process. The Unified Process (Cont.) The Unified Process (Cont.)
The Software Process Xiaojun Qi 1 The Unified Process Until recently, three of the most successful object-oriented methodologies were Booch smethod Jacobson s Objectory Rumbaugh s OMT (Object Modeling
More informationAn Agile Methodology Based Model for Change- Oriented Software Engineering
An Agile Methodology Based Model for Change- Oriented Software Engineering Naresh Kumar Nagwani, Pradeep Singh Department of Computer Sc. & Engg. National Institute of Technology, Raipur nknagwani.cs@nitrr.ac.in,
More informationTransforming Software Quality Assurance &Testing
Transforming Software Quality Assurance &Testing 2012 Last Mile Consultants Technology Solutions Pvt. Ltd. Course Description of Transformation Programs Who we are With a focus on business objectives,
More informationCreating Business Value with Mature QA Practices
perspective Creating Business Value with Mature QA Practices Abstract The IT industry across the globe has rapidly evolved in recent times. The evolution has been primarily driven by factors like changing
More informationExpert Reference Series of White Papers. Intersecting Project Management and Business Analysis
Expert Reference Series of White Papers Intersecting Project Management and Business Analysis 1-800-COURSES www.globalknowledge.com Intersecting Project Management and Business Analysis Daniel Stober,
More informationTest Management and Techniques
These slides are distributed under the Creative Commons License. In brief summary, you may make and distribute copies of these slides so long as you give the original author credit and, if you alter, transform
More informationApplication Security in the Software Development Lifecycle
Application Security in the Software Development Lifecycle Issues, Challenges and Solutions www.quotium.com 1/15 Table of Contents EXECUTIVE SUMMARY... 3 INTRODUCTION... 4 IMPACT OF SECURITY BREACHES TO
More informationSoftware Testing, Mythology & Methodologies
Software, Mythology & Methodologies Sonali Waje 1, Vandana Gaikwad 2, Pranchal Chaudhari 3 1,3 B.E. Information Technology, 2 B.E.Computer Engineering Abstract - It is generally believed that phases of
More informationWhat really drives customer satisfaction during the insurance claims process?
Research report: What really drives customer satisfaction during the insurance claims process? TeleTech research quantifies the importance of acting in customers best interests when customers file a property
More informationTransitioning Your Software Process To Agile Jeffery Payne Chief Executive Officer Coveros, Inc. jeff.payne@coveros.com www.coveros.
Transitioning Your Software Process To Agile Jeffery Payne Chief Executive Officer Coveros, Inc. jeff.payne@coveros.com www.coveros.com 1 About Coveros Coveros helps organizations accelerate the delivery
More informationExample Software Development Process.
Example Software Development Process. The example software development process is shown in Figure A. The boxes represent the software development process kernels. The Software Unit Testing, Software Component
More informationThe Dangers of Use Cases Employed as Test Cases
The Dangers of Use Cases Employed as Test Cases Bernie Berger This document is intended to provide background support and additional information to the slide presentation at STARWest 2001. I don t consider
More informationImproved Software Testing Using McCabe IQ Coverage Analysis
White Paper Table of Contents Introduction...1 What is Coverage Analysis?...2 The McCabe IQ Approach to Coverage Analysis...3 The Importance of Coverage Analysis...4 Where Coverage Analysis Fits into your
More informationAn Overview of Quality Assurance Practices in Agile Methodologies
T-76.650 SEMINAR IN SOFTWARE ENGINEERING, SPRING 2004 1 An Overview of Quality Assurance Practices in Agile Methodologies Olli P. Timperi Abstract The focus of literature and debates of agile methodologies
More informationThe following is intended to outline our general product direction. It is intended for information purposes only, and may not be incorporated into
The following is intended to outline our general product direction. It is intended for information purposes only, and may not be incorporated into any contract. It is not a commitment to deliver any material,
More informationReduce QA Cost by Improving Productivity & Test Optimization
Reduce QA Cost by Improving Productivity & Test Optimization Author(s) Rajesh Kumar (rajesh_kumar_5@uhc.com) and Ajay K Chhokra (ajay_k_chhokra@uhc.com) UnitedHealth Group Information Systems, Unitech
More informationAn Introduction to. Metrics. used during. Software Development
An Introduction to Metrics used during Software Development Life Cycle www.softwaretestinggenius.com Page 1 of 10 Define the Metric Objectives You can t control what you can t measure. This is a quote
More informationAdvancements in the V-Model
Advancements in the V-Model Sonali Mathur Asst. Professor, CSE Dept. ABES Institute of Technology Ghaziabad, U.P-201009 Shaily Malik Lecturer, CSE Dept. Maharaja Surajmal Institute of Tech. Janakpuri,
More informationThe most suitable system methodology for the proposed system is drawn out.
3.0 Methodology 3.1 Introduction In this chapter, five software development life cycle models are compared and discussed briefly. The most suitable system methodology for the proposed system is drawn out.
More informationSoftware Testing. Knowledge Base. Rajat Kumar Bal. Introduction
Software Testing Rajat Kumar Bal Introduction In India itself, Software industry growth has been phenomenal. IT field has enormously grown in the past 50 years. IT industry in India is expected to touch
More informationKarunya University Dept. of Information Technology
PART A Questions 1. Mention any two software process models. 2. Define risk management. 3. What is a module? 4. What do you mean by requirement process? 5. Define integration testing. 6. State the main
More informationAgile QA Process. Anand Bagmar Anand.Bagmar@thoughtworks.com abagmar@gmail.com http://www.essenceoftesting.blogspot.com. Version 1.
Agile QA Process Anand Bagmar Anand.Bagmar@thoughtworks.com abagmar@gmail.com http://www.essenceoftesting.blogspot.com Version 1.1 Agile QA Process 1 / 12 1. Objective QA is NOT the gatekeeper of the quality
More informationComparative Study of Agile Methods and Their Comparison with Heavyweight Methods in Indian Organizations
International Journal of Recent Research and Review, Vol. VI, June 2013 Comparative Study of Agile Methods and Their Comparison with Heavyweight Methods in Indian Organizations Uma Kumari 1, Abhay Upadhyaya
More informationThe role of integrated requirements management in software delivery.
Software development White paper October 2007 The role of integrated requirements Jim Heumann, requirements evangelist, IBM Rational 2 Contents 2 Introduction 2 What is integrated requirements management?
More informationTest Plan Template (IEEE 829-1998 Format)
Test Plan Template (IEEE 829-1998 Format) Test Plan Identifier Some type of unique company generated number to identify this test plan, its level and the level of software that it is related to. Preferably
More informationISTQB Certified Tester. Foundation Level. Sample Exam 1
ISTQB Certified Tester Foundation Level Version 2015 American Copyright Notice This document may be copied in its entirety, or extracts made, if the source is acknowledged. #1 When test cases are designed
More informationFundamentals of Information Systems, Fifth Edition. Chapter 8 Systems Development
Fundamentals of Information Systems, Fifth Edition Chapter 8 Systems Development Principles and Learning Objectives Effective systems development requires a team effort of stakeholders, users, managers,
More informationAgile Based Software Development Model : Benefits & Challenges
Agile Based Software Development Model : Benefits & Challenges Tajinder Kumar Assistant Professor, IT Department JMIT Radaur, Haryana Vipul Gupta Assistant Professor, IT Department JMIT Radaur, Haryana
More informationProcess Models and Metrics
Process Models and Metrics PROCESS MODELS AND METRICS These models and metrics capture information about the processes being performed We can model and measure the definition of the process process performers
More informationWhy Test Automation Fails
Why Test Automation Fails in Theory and in Practice Jim Trentadue Enterprise Account Manager- Ranorex jtrentadue@ranorex.com Thursday, January 15, 2015 Agenda Agenda Test Automation Industry recap Test
More informationPeriodic risk assessment by internal audit
Periodic risk assessment by internal audit I Introduction The Good Practice Internal Audit Manual Template, developed by the Internal Audit CoP of Pempal, defines the importance and the impact that an
More informationLatest Trends in Testing. Ajay K Chhokra
Latest Trends in Testing Ajay K Chhokra Introduction Software Testing is the last phase in software development lifecycle which has high impact on the quality of the final product delivered to the customer.
More informationTESTING FRAMEWORKS. Gayatri Ghanakota
TESTING FRAMEWORKS Gayatri Ghanakota OUTLINE Introduction to Software Test Automation. What is Test Automation. Where does Test Automation fit in the software life cycle. Why do we need test automation.
More informationWhite Paper IT Methodology Overview & Context
White Paper IT Methodology Overview & Context IT Methodologies - Delivery Models From the inception of Information Technology (IT), organizations and people have been on a constant quest to optimize the
More informationAdvanced Software Test Design Techniques Use Cases
Advanced Software Test Design Techniques Use Cases Introduction The following is an excerpt from my recently-published book, Advanced Software Testing: Volume 1. This is a book for test analysts and test
More informationReaching CMM Levels 2 and 3 with the Rational Unified Process
Reaching CMM Levels 2 and 3 with the Rational Unified Process Rational Software White Paper TP174 Table of Contents INTRODUCTION... 1 LEVEL-2, REPEATABLE... 3 Requirements Management... 3 Software Project
More informationBenefits of Test Automation for Agile Testing
Benefits of Test Automation for Agile Testing Manu GV 1, Namratha M 2, Pradeep 3 1 Technical Lead-Testing Calsoft Labs, Bangalore, India 2 Assistant Professor, BMSCE, Bangalore, India 3 Software Engineer,
More informationRequirements-Based Testing: Encourage Collaboration Through Traceability
White Paper Requirements-Based Testing: Encourage Collaboration Through Traceability Executive Summary It is a well-documented fact that incomplete, poorly written or poorly communicated requirements are
More informationEffective Software Security Management
Effective Software Security Management choosing the right drivers for applying application security Author: Dharmesh M Mehta dharmeshmm@mastek.com / dharmeshmm@owasp.org Table of Contents Abstract... 1
More informationIn this Lecture you will Learn: Systems Development Methodologies. Why Methodology? Why Methodology?
In this Lecture you will Learn: Systems Development Methodologies What a systems development methodology is Why methodologies are used The need for different methodologies The main features of one methodology
More information4.1 Identify what is working well and what needs adjustment. 4.1.1 Outline broad strategies that will help to effect these adjustments.
(Overview) Step 1 Prepare 1.1 Identify specific issues or choices that the planning process should address. 1.2 Develop an organizational profile. 1.3 Identify any information that must be collected to
More informationIdentifying & Implementing Quick Wins
Identifying & Implementing Quick Wins 1 Executive Summary........3 2 Introduction....... 5 3 Key Steps to Quick Wins....... 7 4 Sample Quick Wins...8 4.1 People Quick Wins... 8 4.2 Process Quick Wins......9
More informationHow To Write An Impactful Audit Report
IIA Chicago Chapter 53 rd Annual Seminar April 15, 2013, Donald E. Stephens Convention Center @IIAChicago #IIACHI How To Write An Impactful Audit Report The role of Audit adds increasingly more value Susan
More informationRisk Analysis and Quantification
Risk Analysis and Quantification 1 What is Risk Analysis? 2. Risk Analysis Methods 3. The Monte Carlo Method 4. Risk Model 5. What steps must be taken for the development of a Risk Model? 1.What is Risk
More informationStrategic View on Various Sub-paradigms of Agile Methodology and Sig Sigma Approach
International Journal of Information and Computation Technology. ISSN 0974-2239 Volume 3, Number 3 (2013), pp. 153-162 International Research Publications House http://www. irphouse.com /ijict.htm Strategic
More informationISTQB Advanced Level. Certification Exam. Self Study E-Book
ISTQB Advanced Level Certification Exam Self Study E-Book Chapter Chapter Title Page No. 1 Testing during the Lifecycle 3 2 Test Process Generic Test Process Test Planning Test Specification 13 Test Execution
More informationBasic Testing Concepts and Terminology
T-76.5613 Software Testing and Quality Assurance Lecture 2, 13.9.2006 Basic Testing Concepts and Terminology Juha Itkonen SoberIT Contents Realities and principles of Testing terminology and basic concepts
More informationFive Testing Best Practices And How These Practices Can Help You
And How These Practices Can Help You Tp5T Top Testing Best tpractices A best practice is an approach to doing something that generally gives good results when applied appropriately and thoughtfully For
More informationCombining Security Risk Assessment and Security Testing Based on Standards
Combining Security Risk Assessment and Security Testing Based on Standards Jürgen Großmann 1(&) and Fredrik Seehusen 2 1 Fraunhofer FOKUS, Berlin, Germany juergen.grossmann@fokus.fraunhofer.de 2 SINTEF
More informationITIL CSI 2011 Vernon Lloyd
ITIL CSI 2011 Vernon Lloyd 12 th December 2011 Implementing or Improving? Vernon Lloyd International Client Director Fox IT Without change there is no innovation, creativity, or incentive for improvement
More informationPreparation Basics for Productive Contract Negotiations
Preparation Basics for Productive Contract Negotiations Submitted to: National Public Employer Labor Relations Association Labor Relations Certification Academy Prepared by: Lorna Ingenthron City of Battle
More informationResults Based Testing
Using Gain-Sharing Pricing Model for Testing Ayal Zylberman Summary Results Based Testing (RBT) is a new software testing pricing model that sets forth the expected value to be delivered by the Testing
More informationFrom Traditional Functional Testing to Enabling Continuous Quality in Mobile App Development
From Traditional Functional Testing to Enabling Continuous Quality in Mobile App Development Introduction Today s developers are under constant pressure to launch killer apps and release enhancements as
More informationSoftware Development Processes. Software Life-Cycle Models. Process Models in Other Fields. CIS 422/522 Spring 1998 1
1 Software Development Processes Sequential, Prototype-based RAD, Phased, Risk-based Spiral (c) 1998 M Young CIS 422/522 1/10/99 1 Software Life-Cycle Models Breaking projects down into pieces for... Planning
More informationBalancing the Hybrid Development Process. The role of the Business Analyst
The role of the Business Analyst This document is intended as a guide only. Readers are advised that before acting on any matter arising from this document, they should consult FINNZ. 2013 FINNZ Limited.
More informationLEAN AGILE POCKET GUIDE
SATORI CONSULTING LEAN AGILE POCKET GUIDE Software Product Development Methodology Reference Guide PURPOSE This pocket guide serves as a reference to a family of lean agile software development methodologies
More informationEnterprise Release Management
Enterprise Release Management Plutora helps organizations manage complex IT Feature Pipeline, IT Releases and IT Test Environments in a simple and transparent manner. Enterprise Releases Transparency and
More informationComparing Plan-Driven and Agile Project Approaches
Comparing Plan-Driven and Agile Project Approaches A Personal Perspective Presented by: Craig D. Wilson Matincor, Inc. Copyright 2006-2010 2010 Outline Introduction to System Development Methodology Contrasting
More informationHow to Structure Your First BPM Project to Avoid Disaster
How to Structure Your First BPM Project to Avoid Disaster Table of Contents Table of Contents...2 Introduction...3 Pick The Right Process and Avoid the Wrong Ones...4 Field the Right Team and Include a
More informationSupporting information technology risk management
IBM Global Technology Services Thought Leadership White Paper October 2011 Supporting information technology risk management It takes an entire organization 2 Supporting information technology risk management
More informationTechnology. Accenture Application Testing Services. Embedding quality into the application development life cycle
Technology Accenture Application Testing Services Embedding quality into the application development life cycle 1 Quality First for Better Outcomes IT costs are continuing to climb. Technology is getting
More informationAnatomy of an Enterprise Software Delivery Project
Chapter 2 Anatomy of an Enterprise Software Delivery Project Chapter Summary I present an example of a typical enterprise software delivery project. I examine its key characteristics and analyze specific
More informationBest-Practice Software Engineering: Software Processes to Support Project Success. Dietmar Winkler
Best-Practice Software Engineering: Software Processes to Support Project Success Dietmar Winkler Vienna University of Technology Institute of Software Technology and Interactive Systems Dietmar.Winkler@qse.ifs.tuwien.ac.at
More informationMarketing strategy questionnaire
Marketing strategy questionnaire Prepared by: Date: Purpose Use this template to capture the key information that you need to develop a thorough marketing strategy. Then use the information that you collect,
More informationCourse Title: Managing the Agile Product Development Life Cycle
Course Title: Managing the Agile Product Development Life Cycle Course ID: BA25 Credits: 28 PDUs Course Duration: 4 days (with optional Executive session) Course Level: Intermediate/Advanced Course Description:
More informationAgile Testing. What Students Learn
Agile Testing Transition sound traditional test practices into an Agile development environment. By using a step-by-step approach, this course documents how to transition from traditional test practices
More informationOracle Insurance Policy Administration System Quality Assurance Testing Methodology. An Oracle White Paper August 2008
Oracle Insurance Policy Administration System Quality Assurance Testing Methodology An Oracle White Paper August 2008 Oracle Insurance Policy Administration System Quality Assurance Testing Methodology
More informationQuality Meets the CEO
Quality Meets the CEO Jeffery E. Payne jepayn@rstcorp.com Reliable Software Technologies Corporate management does not care about quality. This is the cold, hard reality of the software world. Management
More informationQ1 What is systems development?
Q1 What is systems development? The process of creating and maintaining information systems is called systems development or systems analysis and design. This diagram shows that it involves all five components
More informationEvolving a Ultra-Flow Software Development Life Cycle Model
RESEARCH ARTICLE International Journal of Computer Techniques - Volume 2 Issue 4, July - Aug Year Evolving a Ultra-Flow Software Development Life Cycle Model Divya G.R.*, Kavitha S.** *(Computer Science,
More informationThe Handbook of Program Management: How to Facilitate Project Success with Optimal Program Management. Dr. James T. Brown, McGraw Hill, 2008
The Handbook of Program Management: How to Facilitate Project Success with Optimal Program Management Dr. James T. Brown, McGraw Hill, 2008 I received this book unsolicited in the mail from Dr. Brown.
More informationSoftware Engineering. Introduction. Software Costs. Software is Expensive [Boehm] ... Columbus set sail for India. He ended up in the Bahamas...
Software Engineering Introduction... Columbus set sail for India. He ended up in the Bahamas... The economies of ALL developed nations are dependent on software More and more systems are software controlled
More informationProject Management for Process Improvement Efforts. Jeanette M Lynch CLSSBB Missouri Quality Award Examiner Certified Facilitator
Project Management for Process Improvement Efforts Jeanette M Lynch CLSSBB Missouri Quality Award Examiner Certified Facilitator 2 Project and Process Due to the nature of continuous improvement, improvement
More informationAGILE - QUICK GUIDE AGILE - PRIMER
AGILE - QUICK GUIDE http://www.tutorialspoint.com/agile/agile_quick_guide.htm Copyright tutorialspoint.com AGILE - PRIMER Agile is a software development methodology to build a software incrementally using
More informationHow do you manage the growing complexity of software development? Is your software development organization as responsive to your business needs as
How do you manage the growing complexity of software development? Is your software development organization as responsive to your business needs as it could be? Borland Core SDP enables your IT organization
More information5 Reasons Learning and Adoption Programs Fail And What To Do About Them
5 Reasons Learning and Adoption Programs Fail And What To Do About Them Product Lifecycle Management (PLM) solutions deliver extensive business advantages. These include lower time-to-manufacture, greater
More informationKeywords document, agile documentation, documentation, Techno functional expert, Team Collaboration, document selection;
Volume 4, Issue 4, April 2014 ISSN: 2277 128X International Journal of Advanced Research in Computer Science and Software Engineering Research Paper Available online at: www.ijarcsse.com A Document Driven
More informationManaging Agile Projects in TestTrack GUIDE
Managing Agile Projects in TestTrack GUIDE Table of Contents Introduction...1 Automatic Traceability...2 Setting Up TestTrack for Agile...6 Plan Your Folder Structure... 10 Building Your Product Backlog...
More informationCodeless Test Automation for Web Apps
Codeless Test Automation for Web Apps Webinar by TestingWhiz December 11, 2012 1PM EST Agenda Functional Test Automation for Agile Teams Developing and Implementing Codeless Automation Frameworks Achieving
More informationA Risk-based Approach to Performance Auditing
CCAF-FCVI Fellow 2009/2010 A Risk-based Approach to Performance Auditing Strategic Paper by Levina Rusk Kishimba TANZANIA CANADA Table of Contents Page Acknowledgements Executive Summary v vii Introduction
More informationPRINCE2:2009 Glossary of Terms (English)
accept (risk response) acceptance acceptance criteria activity agile methods approval approver assumption assurance A risk response to a threat where a conscious and deliberate decision is taken to retain
More informationTesting and Scrum. Agenda. Fall 2007 Scrum Gathering
Testing and Scrum Fall 2007 Scrum Gathering Ralph van Roosmalen Agenda Introduction The Classical Test Approach Organization Test Documentation Test Activities Recruitment Reporting Test Automation Lessons
More informationAccelerating Time to Market with Agile Testing
WHITEPAPER Accelerating Time to Market with Agile Testing By Balaji Uppili To discover how GAVS can help you innovate and bring greater value to your business, write to inquiry@gavstech.com or visit www.gavstech.com.
More informationHigher Focus on Quality. Pressure on Testing Budgets. ? Short Release Cycles. Your key to Effortless Automation. OpKey TM
Pressure on Testing Budgets Higher Focus on Quality Short Release Cycles Your key to Effortless Automation OpKey TM Most of the CTOs face a common challenge i.e. the need to go to Market in shortest possible
More informationMeasuring ROI of Agile Transformation
Measuring ROI of Agile Transformation Title of the Paper: Measuring Return on Investment (ROI) of Agile Transformation Theme: Strategic & Innovative Practices Portfolio, Programs & Project (PPP) Management
More informationA Survey of Software Development Process Models in Software Engineering
, pp. 55-70 http://dx.doi.org/10.14257/ijseia.2015.9.11.05 A Survey of Software Development Process Models in Software Engineering Iqbal H. Sarker 1, Faisal Faruque 1, Ujjal Hossen 2 and Atikur Rahman
More informationHow to achieve excellent enterprise risk management Why risk assessments fail
How to achieve excellent enterprise risk management Why risk assessments fail Overview Risk assessments are a common tool for understanding business issues and potential consequences from uncertainties.
More informationBusiness Process Validation: What it is, how to do it, and how to automate it
Business Process Validation: What it is, how to do it, and how to automate it Automated business process validation is the best way to ensure that your company s business processes continue to work as
More informationTen steps to better requirements management.
White paper June 2009 Ten steps to better requirements management. Dominic Tavassoli, IBM Actionable enterprise architecture management Page 2 Contents 2 Introduction 2 Defining a good requirement 3 Ten
More informationA. Waterfall Model - Requirement Analysis. System & Software Design. Implementation & Unit Testing. Integration & System Testing.
Processing Models Of SDLC Mrs. Nalkar Sanjivani Baban Asst. Professor, IT/CS Dept, JVM s Mehta College,Sector 19, Airoli, Navi Mumbai-400708 Nalkar_sanjivani@yahoo.co.in Abstract This paper presents an
More informationBusiness resilience: Providing targeted resilience solutions for the enterprise
IBM Global Technology Services Thought Leadership White Paper May 2011 Business resilience: Providing targeted resilience solutions for the enterprise Develop a best-practices resilience strategy using
More informationPlanning a Basel III Credit Risk Initiative
Risk & Compliance the way we see it Planning a Basel III Credit Risk Initiative How to Achieve Return on Investment Contents 1 Introduction 3 2 Banks need a strong data foundation 4 3 A new focus on models
More informationAgile Notetaker & Scrum Reference. Designed by Axosoft, the creators of OnTime the #1 selling scrum software.
Agile Notetaker & Scrum Reference Designed by Axosoft, the creators of OnTime the #1 selling scrum software. Scrum Diagram: Team Roles: roduct Owner: Is responsible for what goes into the product backlog
More informationTable of contents. Performance testing in Agile environments. Deliver quality software in less time. Business white paper
Performance testing in Agile environments Deliver quality software in less time Business white paper Table of contents Executive summary... 2 Why Agile? And, why now?... 2 Incorporating performance testing
More informationCertification Authorities Software Team (CAST) Position Paper CAST-15
Certification Authorities Software Team (CAST) Position Paper CAST-15 Merging High-Level and Low-Level Requirements Completed February 2003 NOTE: This position paper has been coordinated among the software
More information