Requirements Driven Testing

Slides:



Advertisements
Similar presentations
Course: e-Governance Project Lifecycle Day 1
Advertisements

Test Execution and Defect management. 2 Module Objectives Introduction to Test Execution Checklist of Test Execution Defect management Defect Classification.
Software Process Models
Software Engineering CSE470: Process 15 Software Engineering Phases Definition: What? Development: How? Maintenance: Managing change Umbrella Activities:
Software Modeling SWE5441 Lecture 3 Eng. Mohammed Timraz
ITIL: Service Transition
Validata Release Coordinator Accelerated application delivery through automated end-to-end release management.
SYSC System Analysis and Design
Incorporating Automation into an End-to-End Accessibility Program Thomas Logan, HiSoftware – VP Product Management 12 April 2010.
Requirements - Why What and How? Sriram Mohan. Outline Why ? What ? How ?
SwE 434. Rational Quality Manager Rational Quality Manager is a collaborative, Web-based tool that offers comprehensive test planning, test construction,
SE 450 Software Processes & Product Metrics 1 Defect Removal.
Tester’s Role in Software Development and Acquisition Best Practice By Gabriel Rodriguez.
Unified Software Development Process (UP) Also known as software engineering process SEP describes how requirements are turned into software Defines who,
1 IBM Software Group ® Mastering Object-Oriented Analysis and Design with UML 2.0 Module 1: Best Practices of Software Engineering.
Dillon: CSE470: SE, Process1 Software Engineering Phases l Definition: What? l Development: How? l Maintenance: Managing change l Umbrella Activities:
Why use RequisitePro RequisitePro is a comprehensive tool that supports any of today's requirements management processes. The predominant requirements.
1 “ Understanding leads to perfection” Author: Herb Isenberg Ph.D A Bird’s Eye View Quality Foundations January 2011.
© 2014 Equity Administration Solutions, Inc. All rights reserved. 1 Four Fundamentals of Financial Reporting for Equity Compensation Kathy Biddle, CEP.
CS 360 Lecture 3.  The software process is a structured set of activities required to develop a software system.  Fundamental Assumption:  Good software.
INTRODUCTION What is software? What is software engineering?
SOFTWARE PROTOTYPING Anil Kumar.Arikepudi.
Requirements Management with Use Cases Module 2: Introduction to RMUC Requirements Management with Use Cases Module 2: Introduction to RMUC.
Principles of Information Systems, Sixth Edition Systems Design, Implementation, Maintenance, and Review Chapter 13.
Software Requirements Engineering: What, Why, Who, When, and How
Sampleminded® Support Overview Last Updated: 1/22/
Software Development Cycle What is Software? Instructions (computer programs) that when executed provide desired function and performance Data structures.
Rational Requirements Management with Use Cases v5.5 Copyright © Rational Software, all rights reserved 1 Requirements Management with Use Cases.
Review of Software Process Models Review Class 1 Software Process Models CEN 4021 Class 2 – 01/12.
REQUIREMENTS - WHY WHAT AND HOW? Steve Chenoweth & Chandan Rupakheti CSSE 371 Chapters Requirements Text. Question 6.
Software Engineering process models
TM Copyright © 2009 NMQA Ltd. Behaviour Driven Testing with.
Chapter 4 프로세스 모델 Process Models
1 TenStep Project Management Process ™ PM00.9 PM00.9 Project Management Preparation for Success * Manage Quality *
Cmpe 589 Spring 2006 Lecture 2. Software Engineering Definition –A strategy for producing high quality software.
Principles of Information Systems, Sixth Edition 1 Systems Design, Implementation, Maintenance, and Review Chapter 13.
Chapter 1: Fundamental of Testing Systems Testing & Evaluation (MNN1063)
1 Technology Infusion of the Software Developer’s Assistant (SDA) into the MOD Software Development Process NASA/JSC/MOD/Brian O’Hagan 2008 Software Assurance.
LOGO TESTING Team 8: 1.Nguyễn Hoàng Khánh 2.Dương Quốc Việt 3.Trang Thế Vinh.
SLIDE: 1 © COPYRIGHT 2014 MARKLOGIC CORPORATION. ALL RIGHTS RESERVED.
1 The Requirements Problem Chapter 1. 2 Standish Group Research Research paper at:  php (1994)
Homework #1a Lifecycle Paper For each stage of the life cycle provide a list of items you think should be there. There should be at a minimum of five items.
INCOSE IW12 MBSE Workshop 15 INCOSE (MBSE) Model Based System Engineering Integration and Verification Scenario Ron Williamson, PhD Raytheon
Integrated ALM with Cross-Tool Reporting Kovair Marketing Kovair Software Copyright ©
Presented by Rob Carver
SOFTWARE TESTING Date: 29-Dec-2016 By: Ram Karthick.
Cisco Compliance Management and Configuration Service
Software Project Configuration Management
Michael J. Salé, Seidenberg School of CSIS, Westchester DPS 2016
Software Verification and Validation
Chapter 10 Software Quality Assurance& Test Plan Software Testing
Project Management Processes
TechStambha PMP Certification Training
Tutorial 10 Quality Management.
V-Shaped SDLC Model Lecture-6.
E2E Testing in Agile – A Necessary Evil
Requirements and the Software Lifecycle
Advantages OF BDD Testing
Engineering Processes
Foundation Degree IT Project
Unit 2:-Test Planning and Management
Fundamental Test Process
Quality Assurance in an Agile Development Team Michelle Wu 2018 PNSQC
CHAPTER 10 METHODOLOGIES FOR CUSTOM SOFTWARE DEVELOPMENT
Baisc Of Software Testing
Project Management Processes
Engineering Processes
Testing Workshop.
Test Tools Tools can be useful but are they worth it? Cost
Unit IV – Chapter 2 V-Test Model.
Presentation transcript:

Requirements Driven Testing First Step to Automation Prashanth Shidlaghatta

Business / IT Problem 30% of all defects, found by a customer, are requirements defects : Quality Impact Fixing a Requirement issue in maintenance phase costs a factor 200 more than fixing it in requirements phase : Cost impact Requirements errors are likely to consume 25% of the total project budget/Time : Time Impact The Standish Group

Business / IT Problem – At Practitioner Level The IT Challenge (for Practitioners): Business not effectively participating in the requirements definition process Excessive time spent maintaining requirements/Test Cases within various forms of documentation Documentation can be misrepresented, misunderstood or misinterpreted, particularly in other lifecycle processes Remote stakeholders (e.g., offshore teams) not effectively engaged in the requirements/Test Design process IT struggles with validating process and regulatory compliance

A Visible Approach to Requirements Capture A pragmatic, structured approach to the capture, definition and management of requirements across the life cycle Concurrent visibility to all stakeholders of requirements in output relevant to them

Aspects of simulation Roles Process Usecase UI Service Class Rules Requirements Live simulation Roles Process Usecase UI Service Class Rules UI prototyping & Pageflow simulation Data-manipulation & service-simulation Business Rules simulation Use-case simulation Process & Security simulation

Requirements Driven Testing Business IT Structured Requirements Natural Lang. Simulation User experience Functional specification Generate Test Cases Generate Automated Tests Test Specification System Testing User Acceptance Test User Test

The Results.. Guaranteed Requirements Coverage Early Detection of Requirements flaws More time to execute Manual or Automated Tests More Tests Executed Increasing Coverage and Lowering Risk Happy Customers!!