06/12/2007SE 652 - 2007_6_12_Design.ppt1 Design Phase Outputs: Completed & Inspected SDS & Integration Test Plan Completed & Inspected System Test Plan.

Slides:



Advertisements
Similar presentations
Object Oriented Analysis And Design-IT0207 iiI Semester
Advertisements

Testing Workflow Purpose
Test Yaodong Bi.
DETAILED DESIGN, IMPLEMENTATIONA AND TESTING Instructor: Dr. Hany H. Ammar Dept. of Computer Science and Electrical Engineering, WVU.
Software Failure: Reasons Incorrect, missing, impossible requirements * Requirement validation. Incorrect specification * Specification verification. Faulty.
Project Estimation: Metrics and Measurement
Physical Architecture Layer Design
Software Quality Assurance Inspection by Ross Simmerman Software developers follow a method of software quality assurance and try to eliminate bugs prior.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 23 Slide 1 Software testing.
6/19/2007SE _06_19_Overview_Inspections.ppt1 Team Software Project (TSP) June 19, 2007 High Level Designs, Code Inspections & Measurement.
6/19/2007SE _6_19_TSPImp_SVT_Lecture.ppt1 Implementation Phase Inputs: Development strategy & plan Completed, inspected & baselined SRS & SDS.
Copyright © 2006 Software Quality Research Laboratory DANSE Software Quality Assurance Tom Swain Software Quality Research Laboratory University of Tennessee.
5/29/2007SE TSP Launch1 Team Software Project (TSP) May 29, 2007 Launch/Strategy Team Formation.
Introduction to Software Testing
Software Integration and Documenting
Testing. What is Testing? Definition: exercising a program under controlled conditions and verifying the results Purpose is to detect program defects.
1 Software Testing (Part-II) Lecture Software Testing Software Testing is the process of finding the bugs in a software. It helps in Verifying and.
TESTING.
Cmpe 589 Spring Software Quality Metrics Product  product attributes –Size, complexity, design features, performance, quality level Process  Used.
SE 501 Software Development Processes Dr. Basit Qureshi College of Computer Science and Information Systems Prince Sultan University Lecture for Week 8.
© 2012 IBM Corporation Rational Insight | Back to Basis Series Chao Zhang Unit Testing.
INFO 637Lecture #61 Software Engineering Process II Designing with Teams INFO 637 Glenn Booker.
Software Testing.
INFO 637Lecture #41 Software Engineering Process II Development Plan INFO 637 Glenn Booker.
Software Inspection A basic tool for defect removal A basic tool for defect removal Urgent need for QA and removal can be supported by inspection Urgent.
Chapter 6 : Software Metrics
FCS - AAO - DM COMPE/SE/ISE 492 Senior Project 2 System/Software Test Documentation (STD) System/Software Test Documentation (STD)
1 Software testing. 2 Testing Objectives Testing is a process of executing a program with the intent of finding an error. A good test case is in that.
Testing Basics of Testing Presented by: Vijay.C.G – Glister Tech.
Software Life Cycle Requirements and problem analysis. –What exactly is this system supposed to do? Design –How will the system solve the problem? Coding.
Testing Workflow In the Unified Process and Agile/Scrum processes.
Lecture 4 Software Metrics
INFO 637Lecture #101 Software Engineering Process II Review INFO 637 Glenn Booker.
Team Software Process (TSPi) CS4320 Fall TSP Strategy Provide a simple process framework based on the PSP. Use modest, well-defined problems. Develop.
16 October Reminder Types of Testing: Purpose  Functional testing  Usability testing  Conformance testing  Performance testing  Acceptance.
Software Testing and Quality Assurance Software Quality Assurance 1.
Introduction to Software Project Estimation I (Condensed) Barry Schrag Software Engineering Consultant MCSD, MCAD, MCDBA Bellevue.
CS 350, slide set 9 M. Overstreet Old Dominion University Spring 2006.
1 Introduction to Software Testing. Reading Assignment P. Ammann and J. Offutt “Introduction to Software Testing” ◦ Chapter 1 2.
1 Ch. 1: Software Development (Read) 5 Phases of Software Life Cycle: Problem Analysis and Specification Design Implementation (Coding) Testing, Execution.
Software Engineering 2004 Jyrki Nummenmaa 1 BACKGROUND There is no way to generally test programs exhaustively (that is, going through all execution.
Software testing techniques Software testing techniques Object-oriented software testing Presentation on the seminar Kaunas University of Technology.
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.
INFO 637Lecture #71 Software Engineering Process II Product Implementation INFO 637 Glenn Booker.
PRODUCT IMPLEMENTATION Chapter 8 Tawatchai Iempairote September 23, 2041.
Software Engineering Saeed Akhtar The University of Lahore.
Focus on design principles and on a process for doing design = To produce a precise, complete, high- quality foundation for product implementation.
540f07cost12oct41 Reviews Postmortem u Surprises? u Use white background on slides u Do not zip files on CD u Team leader should introduce team members.
Test Plan: Introduction o Primary focus: developer testing –Implementation phase –Release testing –Maintenance and enhancement o Secondary focus: formal.
CS 350, slide set 9 M. Overstreet Old Dominion University Fall 2005.
HNDIT23082 Lecture 09:Software Testing. Validations and Verification Validation and verification ( V & V ) is the name given to the checking and analysis.
1 Phase Testing. Janice Regan, For each group of units Overview of Implementation phase Create Class Skeletons Define Implementation Plan (+ determine.
Testing Overview Software Reliability Techniques Testing Concepts CEN 4010 Class 24 – 11/17.
CS 350, slide set 10 M. Overstreet Old Dominion University Spring 2005.
SOFTWARE TESTING Date: 29-Dec-2016 By: Ram Karthick.
Approaches to ---Testing Software
C++ Plus Data Structures
Object-oriented software testing
Chapter 8 – Software Testing
Chapter 13 & 14 Software Testing Strategies and Techniques
Introduction to Software Testing
Lecture 09:Software Testing
SQA Role during Software Code and Unit Test Phase
Software metrics.
CSE 1020:Software Development
Chapter 7 Software Testing.
Overview Activities from additional UP disciplines are needed to bring a system into being Implementation Testing Deployment Configuration and change management.
Think about your view of QA
COCOMO MODEL.
Chapter 13 & 14 Software Testing Strategies and Techniques 1 Software Engineering: A Practitioner’s Approach, 6th edition by Roger S. Pressman.
Presentation transcript:

06/12/2007SE _6_12_Design.ppt1 Design Phase Outputs: Completed & Inspected SDS & Integration Test Plan Completed & Inspected System Test Plan Completed Inspection forms (INS) Completed & Inspected Design, Coding & Naming Standards Updated SUMP form & measurement data collected Time, defect & size data collected Updated project notebook Note: On baselining SDS, the document should be placed under change control

06/12/2007SE _6_12_Design.ppt2 Software Design Specification (SDS) Input Conceptual Design Requirements (SRS) Design Objectives Principal parts How the parts interact How they are put together Recommendation: assign only 1 to 2 developers to produce SDS

06/12/2007SE _6_12_Design.ppt3 Design Standards Naming conventions Function, File, Variable, Parameter Names Defines, Globals, Public, Statics, etc. Interface formats Variable handling Error codes System & Error messages Defect standards Severities Defect types Root cause bucketing LOC counting

06/12/2007SE _6_12_Design.ppt4 Design for Reuse Reusable functions should be: Self contained Cleanly isolated Clearly & concisely documented (usage, interfaces, returns, errors) Examples of successful reusable components?

06/12/2007SE _6_12_Design.ppt5 Design for Testability Unit test harnesses Simulation testing Black box testing Verify program’s external interfaces White box testing Also considers program’s logical paths & structure Typically requires special tools (e.g. code coverage) Typically requires supporting code

06/12/2007SE _6_12_Design.ppt6 Integration Test Plan Objective Verify all system component interfaces Activity Review all interfaces (as defined in SDS) Specify how to test them Recommend: inspecting SDS & Integration Test Plan simultaneously Could also combine into a single document

06/12/2007SE _6_12_Design.ppt7 System Test Plan Areas to cover: Installation Start-up All required functions available & working as specified Diabolical (e.g. power failures, corner cases, incorrect handling) Performance Usability Includes: Test cases you plan to run (numbered / named) Expected results Ordering of testing & dependencies Supporting materials needed Traceability to requirements

06/12/2007SE _6_12_Design.ppt8 Due Next Week System Test Plan draft for inspection Draft to Product Team by COB Tuesday SRS Inspection Quality Records High Level Design (SDS), Design Standards & Integration Test Plan Inspected & Baselined TSPi Planning forms Team & Engineer schedule updates Updated SUMP & SUMS forms

Backup Slides

06/12/2007SE _6_12_Design.ppt10 Inspections Estimating Defects Capture-ReCapture Example Catch 20 fish in lake, tag & release them Catch 25 more, 5 are tagged How many fish are in the lake? 5 out of 25 = 20 out of Total Population Total = ?

06/12/2007SE _6_12_Design.ppt11 Capture-ReCapture Formula Fishing example: 5 out of 25 = 20 out of Total C = # from both fishing tries (e.g. 5) A = # from first fishing try (e.g. 20) B = # from second fishing try (e.g. 25) So, C out of B = A out of Total C/B = A/Total Total = A*B/C

06/12/2007SE _6_12_Design.ppt12 Estimating Defects 2 Developer Case C = # from both tries = # found by both developers A = # from first try = # found by developer A B = # from second try = # found by developer B Total # defects = # A * # B / # both found Yield = # found / Total # defects expressed as percentage = 100 * (A*B-C) / (A*B/C) = 100 * (A*B-C)*C / A*B Humphrey 2 Developer Example: Two developers, A found 7, B found 5, common defects 3 Total estimated # defects = (7*5)/3 = 12 Yield = 9 / 12 = 75%

06/12/2007SE _6_12_Design.ppt13 Estimating Defects 3 Developer Example Three developers in an inspection identified 10 unique defects (# from 1 to 10). Harry found defects 1, 2, 3, 4 & 5 Chapin found defects 1, 2, 4, 6 & 7 Sue found defects 4, 6, 7, 8, 9 & 10 Estimate total # of defects in product prior to inspection. Estimate total inspection yield. Sue identified the most unique defects (3) = 6 identified Combine Harry’s & Chapin’s defects = 7 identified, 3 in common w/ Sue Total Product Defects = 6 * 7 / 3 = 14 Yield % = 100 * 10/14 = 71%

06/12/2007SE _6_12_Design.ppt14 Capture-ReCapture Assumptions & Cautions Population is homogeneous Population is randomly distributed Sample #s are reasonably large

06/12/2007SE _6_12_Design.ppt15 Probabilities Extra-Credit Problem Assuming birthdays are uniformly distributed across 365 days, what is the minimum number of people needed in a room for the probability of two people having the same birth date (day of year) to be greater than ½?