Unit IV – Chapter 2 V-Test Model.

Slides:



Advertisements
Similar presentations
Software Quality Assurance Plan
Advertisements

Presentation by Prabhjot Singh
14-1 © Prentice Hall, 2004 Chapter 14: OOSAD Implementation and Operation (Adapted) Object-Oriented Systems Analysis and Design Joey F. George, Dinesh.
Software Quality Assurance Plan
1 Information Systems Development (ISD) Systems Development Life Cycle Overview of Analysis Phase Overview of Design Phase CP2236: Information Systems.
©Ian Sommerville 2000Software Engineering, 6th edition. Chapter 19Slide 1 Verification and Validation l Assuring that a software system meets a user's.
SE 555 Software Requirements & Specification Requirements Validation.
Validating and Improving Test-Case Effectiveness Author: Yuri Chernak Presenter: Lam, Man Tat.
Software Test Plan Why do you need a test plan? –Provides a road map –Provides a feasibility check of: Resources/Cost Schedule Goal What is a test plan?
Software Life Cycle Model
Introduction to Computer Technology
QUALITY MANAGEMENT SYSTEM ACCORDING TO ISO
S/W Project Management
Introduction to Software Quality Assurance (SQA)
Unified Software Development Process (UP) Also known as software engineering process SEP describes how requirements are turned into software Defines who,
Managing the development and purchase of information systems (Part 1)
Applying the Inspection Process. What Software Artifacts Are Candidates for Inspection? Software Requirements Software Designs Code Test Plans.
CMSC 345 Fall 2000 Unit Testing. The testing process.
Software Testing.
Topics Covered: Software requirement specification(SRS) Software requirement specification(SRS) Authors of SRS Authors of SRS Need of SRS Need of SRS.
14-1 © Prentice Hall, 2004 Chapter 14: OOSAD Implementation and Operation Object-Oriented Systems Analysis and Design Joey F. George, Dinesh Batra, Joseph.
CEN rd Lecture CEN 4021 Software Engineering II Instructor: Masoud Sadjadi Phases of Software.
14-1 © Prentice Hall, 2004 Chapter 14: OOSAD Implementation and Operation Object-Oriented Systems Analysis and Design Joey F. George, Dinesh Batra, Joseph.
Apply Project Scope Management Techniques Project Scope Processes – Part 2 Certificate IV in Project Management Qualification Code BSB41507 Unit.
Project Proposal Document Optimization 15 February 2007 Team members: Chris Catalano Chun-Yu Chang Chris Joson David Matthes.
1 Introduction to Software Engineering Lecture 1.
Business Analysis. Business Analysis Concepts Enterprise Analysis ► Identify business opportunities ► Understand the business strategy ► Identify Business.
Requirements Validation
Software Engineering Lecture # 1.
Software Engineering1  Verification: The software should conform to its specification  Validation: The software should do what the user really requires.
©2007 · Georges Merx and Ronald J. NormanSlide 1 Chapter 9 Software Quality Assurance.
Software Engineering Saeed Akhtar The University of Lahore.
Software Testing and Quality Assurance 1. What is the objectives of Software Testing?
 Software Testing Software Testing  Characteristics of Testable Software Characteristics of Testable Software  A Testing Life Cycle A Testing Life.
Software Development Process CS 360 Lecture 3. Software Process The software process is a structured set of activities required to develop a software.
1 Software Testing and Quality Assurance Lecture 17 - Test Analysis & Design Models (Chapter 4, A Practical Guide to Testing Object-Oriented Software)
Pertemuan 14 Matakuliah: A0214/Audit Sistem Informasi Tahun: 2007.
Copyright 2015, Robert W. Hasker. Classic Model Gathering Requirements Specification Scenarios Sequences Design Architecture Class, state models Implementation.
Systems Analysis & Design David Walkiewicz March 31, 2012.
MANAGEMENT INFORMATION SYSTEM
Software Testing Strategies for building test group
Software Testing.
How To Apply Quality Management
Software Quality Engineering
Software Verification and Validation
Principles of Information Systems Eighth Edition
Requirements Engineering (continued)
Software Quality Engineering
Systems Analysis and Design
Quality Management Perfectqaservices.
V-Shaped SDLC Model Lecture-6.
Some Simple Definitions for Testing
Verification and Validation
CHAPTER 2 Testing Throughout the Software Life Cycle
SQA Role during Software Requirements Phase
Managing the development of information systems (Part 1)
Engineering Processes
Introduction to Software Testing
Test Planning Mike O’Dell (some edits by Vassilis Athitsos)
Lecture 09:Software Testing
Baisc Of Software Testing
Software Verification, Validation, and Acceptance Testing
MANAGING THE DEVELOPMENT AND PURCHASE OF INFORMATION SYSTEMS
QA Reviews Lecture # 6.
Engineering Processes
Software Testing Lifecycle Practice
Information Systems Development (ISD) Systems Development Life Cycle
© Oxford University Press All rights reserved.
Software Reviews.
SDLC (Software Development Life Cycle) Role Play
Presentation transcript:

Unit IV – Chapter 2 V-Test Model

V- Model Structured Approach to Testing: Test policy and Test Strategies. Activities during each phase of Software Development Life Cycle: 5 Ws(What, Where, When, Why and Who and How) Analyse Structures Produced during development phase for adequacy and testability: Coverage's, Artifacts, Documents

Generate Test Sets based on Structures: Functional Testing, Structural Test, Requirements/Designs, Validation Testing Additional Activities during Design and Coding: High level design and Low level design ensure complete coverage of requirements. Determine that structures are consistent with previously generated structures: Consistency between various phases. Refine and Redefine test sets generated earlier: changes in requirements, designs and artifacts.

Testing during Proposal Stage A proposal is created when the customer asks for information, quotation and proposal. Feasibility study, Economic feasibility, implementation feasibility, organizational fit, process fit and people fit.

Testing during Requirement stage Adequate Clear Verifiable/ Testable Measurable Feasible Not conflicting with each other

Testing during Test Planning Phase Generate test plan to support development activities: development methodology, schedule and deliverables, test strategy, test objectives, assumptions, risks. Generate Test cases: functional and non-functional requirements, test cases and test data. Analyse requirements/Design Coverage: requirement coverage, design coverage.

Testing during Testing phase Consistency with respect to requirements Analyse design for errors Analyse error handling Developers verify information flow and logical structure Testers inspect design in detail

Aspects to be checked Missing test cases Faulty Logic Module Interface mismatch Data Structure inconsistency Erroneous Input / Output User interfaces inadequacies Correctness of decisions and conditions along all paths Inconsistency with respect to requirements and high level design

Testing during coding phase Aspects to be checked: Coding standards/Guidelines Implementations Coding Optimization Coding Interpreting Design Unit Testing

VV Model Requirements Requirements Verification Requirements Validations Design Design Verification Design validation Coding Coding Verification

Critical roles and responsibilities Development: Project Planning, resourcing, Interacting with customer, Defining policies, supporting testing team, doing development related activities. Testing: Test planning, resourcing, Interacting with customer, defining policies, supporting development team, doing acceptance testing. Customer: specifying requirements, participating in acceptance testing, review and approve