© 2001 Hans Schaefer Slide no. 1 Fast reviews Fast reviews for small immature organizations Hans Schaefer Software Test Consulting N-5281 Valestrandsfossen,

Slides:



Advertisements
Similar presentations
Damian Gordon.  Static Testing is the testing of a component or system at a specification or implementation level without execution of the software.
Advertisements

Static Technique. Static Technique - Review  A way of testing software work products  Program code, requirement spec., design spec.  Test plan, test.
Testing Without Executing the Code Pavlina Koleva Junior QA Engineer WinCore Telerik QA Academy Telerik QA Academy.
 Every stage from phase DESIGN in Software Development Process will have “design document” especially in analysis and design phases.  “Design document”
Learning to program. One learns to program by doing. – Writing your own programs – Reading others programs – Studying good programs written by others.
1 Software Testing and Quality Assurance Lecture 2 Software Verification & Validation.
Code Inspections CSSE 376, Software Quality Assurance Rose-Hulman Institute of Technology March 22, 2007.
Fall, 2006SW Eng Standalone Progs, Univ of Colorado Boulder 1 Wk 11 Glass Box Testing, Flow Graphs, Test Coverage SW Engineering of Standalone Programs.
Applied Software Project Management Andrew Stellman & Jennifer Greene Applied Software Project Management Applied Software.
Validating and Improving Test-Case Effectiveness Author: Yuri Chernak Presenter: Lam, Man Tat.
Applied Software Project Management 1 Introduction Dr. Mengxia Zhu Computer Science Department Southern Illinois University Carbondale.
 QUALITY ASSURANCE:  QA is defined as a procedure or set of procedures intended to ensure that a product or service under development (before work is.
Preparing for Your Performance Review Prepared by: PUC Human Resources Department.
SQA Architecture Software Quality.
12 Steps to Useful Software Metrics
1 Software Inspections and Walkthroughs Author: A. Frank Ackerman Presented by Cynthia Johnson EEL6883.
1CMSC 345, Version 4/04 Verification and Validation Reference: Software Engineering, Ian Sommerville, 6th edition, Chapter 19.
Active Design Reviews Doug Paida Roy Mammen Sharan Mudgal Jerry Cheng.
Applied Software Project Management Andrew Stellman & Jennifer Greene Applied Software Project Management Applied Software.
Clickers in the Classroom Monday Models Spring 08 source:
Modified from a PowerPoint found at
SQA Architecture Software Quality By: MSMZ.
Software Engineering Process I
Software Inspections and Walkthroughs By. Adnan khan.
University of Palestine software engineering department Testing of Software Systems Fundamentals of testing instructor: Tasneem Darwish.
© 2000 Hans Schaefer Slide no. 1 Integration between reviews and test Can you save test work after inspections? Self assessment about how you do inspections.
University of Palestine software engineering department Testing of Software Systems Fundamentals of testing instructor: Tasneem Darwish.
Process Modeling CS 4320 Fall Process Difficulties SW not a production line Each project is different—even within the same company No universally.
Software Reviews. Introduction/Motivation When creating written documents, it is a good idea to have someone else proof read your work. Oftentimes an.
Software Inspections. Defect Removal Efficiency The number of defects found prior to releasing a product divided by The number of defects found prior.
Lecture 16 Formal Technical Reviews (FTRs) (also know as inspections) FOR0383 Software Quality Assurance 9/19/20151Dr Andy Brooks Don´t review in your.
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.
Why do we … Life cycle processes … simplified !!!.
1. 2 IMPORTANCE OF MANAGEMENT Some organizations have begun to ask their contractors to provide only project managers who have been certified as professionals.
©2014 The McGraw-Hill Companies, Inc. All rights reserved Planning, Writing, and Revising Module Four Copyright © 2014 by The McGraw-Hill Companies, Inc.
University of Sunderland Professionalism and Personal Skills Tutorial Presentation Skills.
1.  Describe an overall framework for project integration management ◦ RelatIion to the other project management knowledge areas and the project life.
Software Testing. What is Testing? The process consisting of all life cycle activities, both static and dynamic, concerned with planning, preparation.
INFO 637Lecture #101 Software Engineering Process II Review INFO 637 Glenn Booker.
By Adrian Lupian.  Self-awareness and listening techniques- 2 way street. Will improve your job- effectiveness and work relationships  Assertive Communication-
1 Presentation Template: Instructor Comments u The following template presents a guideline for preparing a Six Sigma presentation. An effective presentation.
Software Testing and Maintenance 1 Code Review  Introduction  How to Conduct Code Review  Practical Tips  Tool Support  Summary.
©Ian Sommerville 2000Software Engineering, 6th edition. Chapter 19Slide 1 Chapter 19 Verification and Validation.
Security Engineering Assurance & Control Objectives Priyanka Vanjani ASU Id #
Ch 22 Verification and Validation
1 TenStep Project Management Process ™ PM00.9 PM00.9 Project Management Preparation for Success * Manage Quality *
Successfully Conducting Employee Performance Appraisals Wendy L. McCoy Director HR & Benefits Florida Conference of The United Methodist Church.
October 2004J. B. Wordsworth J4ISDPAD1 Information Systems Development Processes and documents.
Course summary TDT4235 Tor Stålhane IDI / NTNU. What we try to do QA – Create trust to a product or service SPI – Solve fuzzy problems by –Identifying.
Chapter 1: Fundamental of Testing Systems Testing & Evaluation (MNN1063)
THE POSTMORTEM Chapter 10 Introduction to Team Software Process.
Differentiating Your Instruction Through Guided Reading.
Advances In Software Inspection
ICME Interdisciplinary Case Management Experience.
Reviews Chapter 5 Applied Software Project Management, Stellman & Greene See also:
Software Engineering 2 Term Project by: Feras Batarseh Nestor Rivera.
Writing a Research Paper: Generating Questions & Topics Ashley Velázquez Brought to you in cooperation with the Purdue Online Writing Lab.
Improve Own Learning and Performance This is a very important skill If you can analyse how you work – you can make improvements, which will help you in.
1 Software Testing and Quality Assurance Motivation and Review of Software Verification & Validation (2)
How to Write a Book Review. Before You Begin Remember, there is no right way to write a book review. Book reviews are highly personal and reflect the.
Reading and Writing to Succeed on the EAS (Educating All Students) Exam: Beating the Clock & Answering the Question A Student Workshop by Writing Across.
CIS 375 Bruce R. Maxim UM-Dearborn
Verification and Validation
How to critique a journal article
Verification and Validation
The Decision Making Model
Applied Software Project Management
Interdisciplinary Case Management Experience
Testing and Inspection Present and Future
Software Reviews.
Presentation transcript:

© 2001 Hans Schaefer Slide no. 1 Fast reviews Fast reviews for small immature organizations Hans Schaefer Software Test Consulting N-5281 Valestrandsfossen, Norway http//:home.c2i.net/schaefer/ How to analyze documents and find errors An initial review process without bureaucracy How to improve over time

© 2001 Hans Schaefer Slide no. 2 Fast reviews Why this presentation Reviews are THE most important technique to detect defects INSPECTION is the most effective review technique. BUT: Inspections need infrastructure and organizational maturity, which is not always given. Here, I present a review technique to be used by immature organizations. It does not find as many defects as inspections. But over time, it can be developed.

© 2001 Hans Schaefer Slide no. 3 Fast reviews Inspection process Two meetings Moderator needed Checklists available Material meets entry criteria Evaluation and improvement of the Inspection process itself In practice, inspection often deteriorates.

© 2001 Hans Schaefer Slide no. 4 Fast reviews Fast Review Process The two most important factors in inspections are: get qualified people to attend let them use enough time to prepare For a faster process, I leave out the meetings and let the author control the process: Fast review = Active Author Reader Cycle.

© 2001 Hans Schaefer Slide no. 5 Fast reviews The Process Author finds reviewer(s) Overview with reviewer Reviewer reading Focus on important defects to find Reviewer returns findings to author Controlled by author, surveilled by project manager

© 2001 Hans Schaefer Slide no. 6 Fast reviews About the process (1) Finding reviewers: Author chooses one or more people Project manager makes sure there IS a review Project manager follows up their qualification Project manager makes sure they take the time Project manager involved only if problems occur!

© 2001 Hans Schaefer Slide no. 7 Fast reviews About the Process (2) Overview with reviewer: Author informs about risk factors Maybe, author makes a checklist Maybe no physical meeting, just written info

© 2001 Hans Schaefer Slide no. 8 Fast reviews About the Process (3) Reviewer reading: Just like any other inspection preparation. Problem: Not so good checklist - Try to replace this by qualification. Read document, find problems, describe problems. Project manager follows up time use. In inspection, it is HERE you find the problems!

© 2001 Hans Schaefer Slide no. 9 Fast reviews About the Process (4) Feedback to author: Written or in meeting. Author should ask reviewer for clarification. Reviewer signature. No large meeting. No bureaucracy, no need for moderator, no ”loosing face”. Fast feedback But less control with reviewers and no synergy effect.

© 2001 Hans Schaefer Slide no. 10 Fast reviews The technique in Extreme Programming Pair programming, testing and design Continuous review of what is produced Continuous active involvement of a second view No special preparation, as questions are asked continuously.

© 2001 Hans Schaefer Slide no. 11 Fast reviews How to improve over time Prepare SOME checklists Get an idea about time use Introduce inspections where more than two reviewers needed.

© 2001 Hans Schaefer Slide no. 12 Fast reviews Problems with author reader cycles Lack of control: Author may not be interested Reader may not be qualified or have no time Focus may be wrong (not on main risk factors) No data between reviews No learning of better review process

© 2001 Hans Schaefer Slide no. 13 Fast reviews How to overcome problems SOME project manager involvement. Buddy system forcing everyone to participate. Discuss major defects found too late (in testing). Expect a minimum number of defects to be found! A minimum education in review techniques (half day).

© 2001 Hans Schaefer Slide no. 14 Fast reviews Review Quality Criteria The right (qualified) readers are chosen They have time to read They find at least some errors Concentration on MAJOR issues (EDUCATE!) Reviews are not an option Follow up of major defects not found in reviews Assess what you do yourself!