1 Software Testing & Quality Assurance Lecture 15 Created by: Paulo Alencar Modified by: Frank Xu.

Slides:



Advertisements
Similar presentations
Making the System Operational
Advertisements

1 Integration Testing CS 4311 I. Burnstein. Practical Software Testing, Springer-Verlag, 2003.
SOFTWARE DEVELOPMENT METHODOLOGIES Methodologies Waterfall Prototype model Incremental Iterative V-Model Spiral Scrum Cleanroom RAD DSDM RUP.
1 Software Processes A Software process is a set of activities and associated results which lead to the production of a software product. Activities Common.
Soft. Eng. II, Spring 2002Dr Driss Kettani, from I. Sommerville1 CSC-3325: Chapter II Chap1: Software Engineering Models (Review) Mandatory reading: chapter.
The software process A software process is a set of activities and associated results which lead to the production of a software product. This may involve.
Chapter 2 – Software Processes
Sommerville, I., Software Engineering, Pearson, 9th Ed., 2010.
CMSC 345, Version 11/07 SD Vick from S. Mitchell Software Testing.
Software Testing and Quality Assurance
1 Software Testing and Quality Assurance Lecture 30 - Introduction to Software Testing.
Illinois Institute of Technology
Software Development Overview CPSC 315 – Programming Studio Spring 2009.
Software Development Overview CPSC 315 – Programming Studio Spring 2008.
1 Software Testing and Quality Assurance Lecture 1 Software Verification & Validation.
Software Testing Levels Philippe CHARMAN Last update:
CMSC 345, Version 1/03 An Overview of Software Processes Reference: Software Engineering, by Ian Sommerville, 6 th edition, Chapter 3.
Software System Integration
BY RAJESWARI S SOFTWARE TESTING. INTRODUCTION Software testing is the process of testing the software product. Effective software testing will contribute.
Software Life Cycle Model
Software Testing Testing Process. Agenda Determining the test methodology Planning the tests 2.
©Ian Sommerville 1995 Software Engineering, 5th edition. Chapter 22Slide 1 Verification and Validation u Assuring that a software system meets a user's.
1 Advanced Computer Programming Project Management: Software Life Cycle Copyright © Texas Education Agency, 2013.
1 CSE 403 Software Lifecycle Models Reading: Rapid Development Ch. 7, 25 (further reading: Ch. 21, 35, 36, 20) These lecture slides are copyright (C) Marty.
Overview Integration Testing Decomposition Based Integration
CompSci 230 Software Design and Construction
Lecture # 04 & 05 CS314 Introduction To Software Development Software Development Process (SDP) Instructor :Muhammad Janas khan
The Software Development Life Cycle: An Overview Presented by Maxwell Drew and Dan Kaiser Southwest State University Computer Science Program.
CS 360 Lecture 3.  The software process is a structured set of activities required to develop a software system.  Fundamental Assumption:  Good software.
OHT 7.1 Galin, SQA from theory to implementation © Pearson Education Limited 2004 Chapter 7.1.
CS CS 5150 Software Engineering Lecture 3 Software Processes 2.
INT-Evry (Masters IT– Soft Eng)IntegrationTesting.1 (OO) Integration Testing What: Integration testing is a phase of software testing in which.
University of Palestine software engineering department Testing of Software Systems Testing throughout the software life cycle instructor: Tasneem Darwish.
Testing Basics of Testing Presented by: Vijay.C.G – Glister Tech.
TESTING LEVELS Unit Testing Integration Testing System Testing Acceptance Testing.
Software Engineering II Lecture 3 Fakhar Lodhi. Software Life-Cycle Steps Life-cycle model (formerly, process model) –Requirements phase –Specification.
Chapter 4 프로세스 모델 Process Models
Software Development Overview CPSC 315 – Programming Studio Spring 2013.
1 ECE 453 – CS 447 – SE 465 Software Testing & Quality Assurance Instructor Kostas Kontogiannis.
Software Engineering - Abdul Majeed. What is software? Definition of Software Engineering Software Process Generic view of Software Engineering Software.
Software Life Cycle The software life cycle is the sequence of activities that occur during software development and maintenance.
Chapter 2 – Software Processes Lecture 1 Chapter 2 Software Processes1.
1 Integration Testing CS 4311 I. Burnstein. Practical Software Testing, Springer-Verlag, 2003.
Chapter 2: Testing in Software Life Cycle MNN1063 System Testing and Evaluation.
Assoc. Prof. Dr. Ahmet Turan ÖZCERİT.  System and Software  System Engineering  Software Engineering  Software Engineering Standards  Software Development.
CSC 480 Software Engineering Test Planning. Test Cases and Test Plans A test case is an explicit set of instructions designed to detect a particular class.
Integration testing Integrate two or more module.i.e. communicate between the modules. Follow a white box testing (Testing the code)
Software Engineering Issues Software Engineering Concepts System Specifications Procedural Design Object-Oriented Design System Testing.
Integration Testing Beyond unit testing. 2 Testing in the V-Model Requirements Detailed Design Module implementation Unit test Integration test System.
 Many models have been proposed to deal with the problems of defining activities and associating them with each other  The first model proposed was the.
©Ian Sommerville 2006Software Engineering, 8th edition. Chapter 4 Slide 1 Software Processes.
HNDIT23082 Lecture 09:Software Testing. Validations and Verification Validation and verification ( V & V ) is the name given to the checking and analysis.
Software Development Process CS 360 Lecture 3. Software Process The software process is a structured set of activities required to develop a software.
CS 325: Software Engineering February 16, 2016 Designing a Design Class Diagram Design Class Diagrams DCD: Restaurant Example DCD: ATM Example Software.
A framework that describes the activities performed at each stage of a software development project. A life-cycle or a software process is the organisational.
Systems Development Life Cycle
1 Chapter 2 SW Process Models. 2 Objectives  Understand various process models  Understand the pros and cons of each model  Evaluate the applicability.
1 slc5 TTYP – C++ revisited 1 Which of the following statements are reasonable after the following statement: char* fred = new char[5]; a. fred = bill;
Software Testing.
These slides are based on:
CS 5150 Software Engineering
V-Shaped SDLC Model Lecture-6.
Levels Of Testing and Special Tests
Definition of Integration Testing
Lecture 09:Software Testing
Integration Testing CS 4311
SOFTWARE LIFE-CYCLES Beyond the Waterfall.
Integration Reading: McConnell, Code Complete, Ch. 29
Software System Integration
Overview Activities from additional UP disciplines are needed to bring a system into being Implementation Testing Deployment Configuration and change management.
Presentation transcript:

1 Software Testing & Quality Assurance Lecture 15 Created by: Paulo Alencar Modified by: Frank Xu

2 Overview  Functional Testing  Structural Testing  Integration and System Testing  Process Models and Software Testing  Integration Testing  System Testing

3 Testing in the V-Model Requirements Detailed Design Module implementation Unit test Integration test System test Acceptance test Run tests Write tests Customer Developer Functional (BB) Structural (WB) Architectural Design

4 Unit testing –Testing of individual components Integration testing –Testing to expose problems arising from the combination of components System testing –Testing the complete system prior to delivery Acceptance testing –Testing by users to check that the system satisfies requirements. Sometimes called alpha testing Testing stages

5 Layered Tests /

6 Integration Testing Objectives: To expose problems arising from the combination To quickly obtain a working solution from components. Problem areas –Internal: between components Invocation: call/message passing/… Parameters: type, number, order, value Invocation return: identity (who?), type, sequence –External: Interrupts (wrong handler?) I/O timing –Interaction

7 Integration Testing Types of integration –Structural “Big bang”  no error localization Bottom-up: terminal, driver/module, (driver  module) Top-down: top, stubs, (stub  module), early demo –Behavioral

8 System Testing Concerns with the app’s externals Much more than functional –Load/stress testing –Usability testing –Performance testing –Resource testing

9 Waterfall Model and Integration Testing The Waterfall model is closely associated with top-down development and functional decomposition Top down integration testing will start from the main and use stubs Bottom up integration testing will start from lower level functions and use drivers Big-bang integration testing will test all components at once Traditional integration testing integrates previously tested units with respect to the functional decomposition tree

10 Incremental Models and Integration Testing DesignCodingTestDeploymentDesignCodingTestDeploymentDesignCodingTestDeployment Requirements Release 1 Release 2 Release 3 Each release adds more functionality, i.e., a new increment Incremental Builds: Regression Testing Progression Testing

11 Evolutionary Models and Integration Testing DesignCodingTestDeploymentRequirementsDesignCodingTestDeploymentRequirementsDesignCodingTestDeploymentRequirements Feedback Version 1 New versions implement new and evolving requirements Incremental Builds: Regression Testing Progression Testing

12 Spiral Model and Integration Testing Rapid prototyping brings the operational / behavioral profile of the system in the requirements phase