CIS-74 Computer Software Quality Assurance Systematic Software Testing Chapter 1: An Overview of the Testing Process.

Slides:



Advertisements
Similar presentations
Software Process Models
Advertisements

Designing and Developing Decision Support Systems Chapter 4.
CS 325: Software Engineering January 13, 2015 Introduction Defining Software Engineering SWE vs. CS Software Life-Cycle Software Processes Waterfall Process.
Sommerville, I., Software Engineering, Pearson, 9th Ed., 2010.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 17 Slide 1 Rapid software development.
Chapter 6 SYSTEMS DEVELOPMENT Phases, Tools, and Techniques
Lab/Sessional -CSE-374. SYSTEM DEVELOPMENT LIFE CYCLE.
Chapter 15 Design, Coding, and Testing. Copyright © 2005 Pearson Addison-Wesley. All rights reserved Design Document The next step in the Software.
© Prentice Hall CHAPTER 9 Application Development by Information Systems Professionals.
Software Processes: Traditional CSCI102 - Systems ITCS905 - Systems MCS Systems.
SDLC. Information Systems Development Terms SDLC - the development method used by most organizations today for large, complex systems Systems Analysts.
Implementation. We we came from… Planning Analysis Design Implementation Identify Problem/Value. Feasibility Analysis. Project Management. Understand.
Software Testing Name: Madam Currie Course: Swen5431 Semester: Summer 2K.
Chapter 2- Software Process Lecture 4. Software Engineering We have specified the problem domain – industrial strength software – Besides delivering the.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 17 Slide 1 Rapid software development.
Design, Implementation and Maintenance
Chapter 16 Maintaining Information Systems
SOFTWARE QUALITY ASSURANCE Asst. Prof. Dr. Selim BAYRAKLI Maltepe University Faculty of Engineering SE 410.
Introduction to Computer Technology
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 17 Slide 1 Extreme Programming.
Extreme Programming Software Development Written by Sanjay Kumar.
Software Project Management
Pertemuan 5 Pengembangan Teknologi Informasi Matakuliah: H0402/PENGELOLAAN SISTEM KOMPUTER Tahun: 2005 Versi: 1/0.
System Analysis and Design
CS 360 Lecture 3.  The software process is a structured set of activities required to develop a software system.  Fundamental Assumption:  Good software.
Chapter 3: Software Maintenance Process Omar Meqdadi SE 3860 Lecture 3 Department of Computer Science and Software Engineering University of Wisconsin-Platteville.
Software Testing Course Shmuel Ur
Capability Maturity Models Software Engineering Institute (supported by DoD) The problems of software development are mainly caused by poor process management.
Extreme/Agile Programming Prabhaker Mateti. ACK These slides are collected from many authors along with a few of mine. Many thanks to all these authors.
Rapid software development 1. Topics covered Agile methods Extreme programming Rapid application development Software prototyping 2.
© 2006 ITT Educational Services Inc. System Analysis for Software Engineers: Unit 3 Slide 1 Chapter 16 Maintaining Information Systems.
Introduction to Systems Analysis and Design
1 CS 501 Spring 2004 CS 501: Software Engineering Lecture 2 Software Processes.
Cmpe 589 Spring 2006 Lecture 2. Software Engineering Definition –A strategy for producing high quality software.
Developed by Reneta Barneva, SUNY Fredonia The Process.
Introduction to Testing. Topics Who are we? Who are we? Software Testing Definition and Goals Software Testing Definition and Goals Facts and Numbers.
Chapter 1: Fundamental of Testing Systems Testing & Evaluation (MNN1063)
Chapter 2: Testing in Software Life Cycle MNN1063 System Testing and Evaluation.
WATERFALL DEVELOPMENT MODEL. Waterfall model is LINEAR development lifecycle. This means each phase must be completed before moving onto the next!!! WHAT.
Software Engineering Jon Walker. What is Software Engineering? Why do we call it Software Engineering? Why not just call it programming or software development?
Software Engineering At Glance. Why We Need Software Engineering? The aim of software engineering is to solve the software crisis Software is delivered.
Software Engineering1  Verification: The software should conform to its specification  Validation: The software should do what the user really requires.
Software Testing and Quality Assurance 1. What is the objectives of Software Testing?
1 These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 5/e and are provided with permission by.
1)History of water fall model. 2)Features of water fall model. 3)Phase of water fall model. 4)Brief description of phases. 5)Advantages. 6)Disadvantages.
PI2134 Software Engineering IT Telkom.  Software definition  Characteristic of software  Software myths  Software Engineering definition  Generic.
Software Development Process CS 360 Lecture 3. Software Process The software process is a structured set of activities required to develop a software.
Lectures 2 & 3: Software Process Models Neelam Gupta.
WATERFALL METHOD Robbie Campbell WHAT IS IT  Considered the classic approach to the SDLC.  It is a linear method with goals for each development phase.
Object-Oriented and Classical Software Engineering Eighth Edition, WCB/McGraw-Hill Stephen R. Schach 1.
Welcome to Software Project Management. CONVENTIONAL SOFTWARE MANAGEMENT The BEST and WORST thing about software is its flexibility. 1.Software development.
Chapter 16 Maintaining Information Systems. Objectives:  Explain and contrast four types of system maintenance.  Describe factors affecting maintenance.
Software Lifecycle Models Place of Testing in Software Lifecycle 1.
Week # 4 Quality Assurance Software Quality Engineering 1.
What is a software? Computer Software, or just Software, is the collection of computer programs and related data that provide the instructions telling.
Industrial Software Development Process Bashar Ahmad RISC Software GmbH.
Chapter 9 Testing the System 9.1 Principles of System Testing Focus A: The objective of unit and integration ensure the code implemented the design.
MANAGEMENT INFORMATION SYSTEM
IEEE Std 1074: Standard for Software Lifecycle
Quality Management Perfectqaservices.
Iterative Waterfall Model
The V Model The V Model Damian Gordon Damian Gordon.
SDLC Model A framework that describes the activities performed at each stage of a software development project.
Chapter 2 Software Processes
“Would I have to do this all by myself …….?”
CHAPTER 10 METHODOLOGIES FOR CUSTOM SOFTWARE DEVELOPMENT
CS310 Software Engineering Lecturer Dr.Doaa Sami
Rapid software development
Chapter 16 Maintaining Information Systems
Unit IV – Chapter 2 V-Test Model.
Presentation transcript:

CIS-74 Computer Software Quality Assurance Systematic Software Testing Chapter 1: An Overview of the Testing Process

History of the Definition of “Testing” 1979: Executing a program in order to find bugs 1983: Evaluating program attributes in order to measure quality 2002: “A concurrent lifecycle process of engineering, using, and maintaining testware in order to measure and improve the quality of the software being tested.”

Preventive Testing Requires test cases to validate the requirements so that problems can be found as early as possible Added benefit: test cases document the software

Waterfall Model Most famous of sequential models of software development: 1.Initial concept 2.Requirements analysis 3.Analysis & architectural design 4.Detailed design 5.Development & unit/integration testing 6.System & acceptance testing 7.Implementation 8.Maintenance

Advantages of Waterfall Resources are focused on one activity at a time Each activity has the completed artifact from the previous stage to use as a basis

Disadvantages of Waterfall A lot of backing up to earlier phases, which is very expensive Can lead to dangerous shortcuts No testing until the end (which contributes to the “backing up” problem) Testers are often on critical path

STEP Systematic Test and Evaluation Process Built upon IEEE standards for software test documentation and software unit testingIEEE Stresses the prevention potential of testing Views testing as a parallel process with software development, not a later one

STEP Phases Plan the strategy Acquire the testware Measure the behavior

STEP Output Testware: test plans, test specification documents, test cases, test data files, etc. Intentionally analogous to software in order to reflect the parallel development processes

STEP Testing Roles Manager - communicates, plans, and coordinates Analyst - plans, inventories, designs, and evaluates Technician - implements, executes, and checks Reviewer - examines and evaluates

Review Questions

What is the name for any document or product created as part of the testing effort, such as test cases, test plans, bug reports, etc.?

Testware

What does STEP stand for?

Systematic Test and Evaluation Process

What is the generic name for the software development model in which the requirements are built first, followed by the design, then the code, and lastly, the testing?

Sequential model

What is the most famous of the sequential models of software development?

Waterfall

What is the name for program testing done in a programmer’s personal development library?

Unit testing

What are a couple of advantages to the Waterfall model?

1.Resources are focused on one activity at a time. 2.Each activity has the completed artifact from the previous stage to use as a basis.

What was the focus of testing in the late 1970s?

Finding errors

What are two disadvantages to the Waterfall method?

1.It causes a lot of “starting over.” 2.Testers are usually on the critical path of delivery.

When must test cases be written in order to practice preventive testing?

Before the code is written (in order to validate the requirements).

What are the three phrases in STEP?

1.Plan the Strategy 2.Acquire the Testware 3.Measure the Behavior

What industry standards for documentation and software unit testing is STEP built upon?

IEEE

What are the four major testing roles defined by STEP?

Manager Analyst Technician Reviewer

End of Chapter 1