AOIT Introduction to Programming Unit 4, Lesson 11 Documenting Bugs and Fixes Copyright © 2009–2012 National Academy Foundation. All rights reserved.

Slides:

Advertisements

Similar presentations

1 Case Study: Purchase Ticket. 2 Purchase Ticket by Check Use case Actor: Customer (initiator), clerk Purpose: Reserve seats on an airplane and capture.

Advertisements

Ch-11 Project Execution and Termination. System Testing This involves two different phases with two different outputs First phase is system test planning.

Unit 1, Lesson 4 Software Development Cycle AOIT Introduction to Programming Copyright © 2009–2012 National Academy Foundation. All rights reserved.

Welcome to RAI, the future of collaborative Project Risk Management Overview of Project Risk and Issue Management RAI for the Project Manager RAI for the.

Use Case Diagram © copyright 2001 SNU OOPSLA Lab..

Source Control in MATLAB A tool for tracking changes in software development projects. Stuart Nelis & Rachel Sheldon.

Improving Process for Better Software. Who We Are An experiential learning program that provides technology solutions for our partners, and real- world.

SE 450 Software Processes & Product Metrics Reliability: An Introduction.

Oct. 18, 2002 Copyright © Manfred Lange All rights reserved. Permission granted to make copies for the Agile Workshop October 21, 2002 in Munich.

Ch7: Software Production Process. 1 Questions  What is the life cycle of a software product?  Why do we need software process models?  What are the.

IT Learning Programme The Evaluations Tool Pilot Project 19 th July 2010.

Preforming Mail Merges Lesson 11 © 2014, John Wiley & Sons, Inc. Microsoft Official Academic Course, Microsoft Word Microsoft Word 2013.

Swami NatarajanJuly 14, 2015 RIT Software Engineering Reliability: Introduction.

Copyright © 2006 by The McGraw-Hill Companies, Inc. All rights reserved. McGraw-Hill Technology Education Copyright © 2006 by The McGraw-Hill Companies,

The National Healthy Schools Programme is a long term initiative that aims to help young people and their schools to be healthy, making a difference to.

Software Configuration Management

“GENERIC SCRIPT” Everything can be automated, even automation process itself. “GENERIC SCRIPT” Everything can be automated, even automation process itself.

Introduction to Database using Microsoft Access 2013 Part 1 November 4, 2014.

Welcome to the Minnesota SharePoint User Group. Introductions / Overview Project Tracking / Management / Collaboration via SharePoint Multiple Audiences.

Scenario testing Tor Stålhane. Scenario testing – 1 There are two types of scenario testing. Type 1 – scenarios used as to define input/output sequences.

Project Team Meeting May 16, How Do I’s How Do I’s –What are they? –Why are they important? –What will be done with them?

Unit 1, Lesson 2 What Is a Database? AOIT Database Design Copyright © 2009–2012 National Academy Foundation. All rights reserved.

Software Systems Verification and Validation Laboratory Assignment 3 Integration, System, Regression, Acceptance Testing Assignment date: Lab 3 Delivery.

Lorie Stolarchuk Learning Technology Trainer 1 What has changed with the 2.7.X Upgrade to CLEW?

1 Web Basics Section 1.1 Compare the Internet and the Web Compare Web sites and Web pages Identify Web browser components Describe types of Web sites Section.

Lesson 12: Kitting and De-Kitting

Copyright © 2009 Waiting Room Solutions Billing Training: Activity Reports.

 To explain the importance of software configuration management (CM)  To describe key CM activities namely CM planning, change management, version management.

1 Software Development Configuration management. \ 2 Software Configuration  Items that comprise all information produced as part of the software development.

Accelerating Development Using Open Source Software Black Duck Software Company Presentation.

By Touseef Tahir Software Testing Basics. Today's Agenda Software Quality assurance Software Testing Software Test cases Software Test Plans Software.

© 2014 cPrime Inc., All Rights Reserved JIRA User Essentials.

Project proposal for ISO :2011 implementation Subtitle or presenter.

Testing E001 Access to Computing: Programming. 2 Introduction This presentation is designed to show you the importance of testing, and how it is used.

Scripting Language A scripting language or script language is a programming language that supports the writing of scripts. The term script is typically.

17-Oct-15 © 2007 IBM Corporation Compact models Design proceeds simultaneously at multiple levels of abstraction Libraries.

Requirements and Estimation Process From a CMM Level 5 Organization Alan Prosser.

Project proposal for ITIL implementation Subtitle or presenter.

INFO 638Lecture #21 Software Project Management WBS Approaches.

QUALITY ASSURANCE PRACTICES. Quality Plan Prepared and approved at the beginning of project Soft filing system approach followed. Filing location – –

Copyright © 2006 by The McGraw-Hill Companies, Inc. All rights reserved. McGraw-Hill Technology Education Programming Languages and the Programming Process.

TM Copyright © 2009 NMQA Ltd. Behaviour Driven Testing with.

Lesson 3-1 Example Example 2 Find the sum of 311 and 452 using expanded form. 1.Write the first number in expanded form

Introduction to Computer Operating Systems

Job Application Letters

Herriman High Computer Programming 1A Software Development Cycle Things to Know.

Rational Unified Process Fundamentals Module 4: Core Workflows II - Concepts Rational Unified Process Fundamentals Module 4: Core Workflows II - Concepts.

Copyright 2010, The World Bank Group. All Rights Reserved. Recommended Tabulations and Dissemination Section B.

1 Alma Migration Form How to fill in the Non-Ex Libris Migration Form.

Software Requirements Specification. Requirements Specification: An Overview Basic goal: To understand the problem as perceived by the user. Activities.

INTRODUCTION  Lifestyle is nothing but a web based software related with cloth shop.  The use of this software is user can do shopping of clothes. 

AOIT Introduction to Programming Unit 2, Lesson 6 Arithmetic Operators and Operator Precedence Copyright © 2009–2012 National Academy Foundation. All rights.

0 Glencoe Accounting Unit 1 Chapter 2 Copyright © by The McGraw-Hill Companies, Inc. All rights reserved. Chapter 2, Section 2 Accounting: The Universal.

Copyright © 2006 by The McGraw-Hill Companies, Inc. All rights reserved. McGraw-Hill Technology Education Copyright © 2006 by The McGraw-Hill Companies,

Pre-Conference Training Demonstrations TaiRox Productivity Tools Don Thomson, CEO.

Marco Cattaneo, 6th July Remedy bug tracking tool CERN Problem Report Management System (PRMS)

Project Tools TestTrackPro. Made by a small company, SeaPine Software Have used the Issues Management modules for many years to manage changes and bug.

Chapter 7: Delivery, Installation, and Documentation Ronald J. Leach Copyright Ronald J. Leach, 1997, 2009, 2014,

Security Chapter Demo Sprint meeting – Chapter Leader – Pascal Bisson Chapter Architect – Cyril Dangerville (presenter)

Preforming Mail Merges

Unit 2, Lesson 5 Windows User Accounts

Unit 3, Lesson 8 Making Presentations That Get Attention

Preforming Mail Merges

Dynamic Process for Source Control

Project proposal for ISO 9001:2008 implementation

Decisions In today’s lesson we will look at:

Decisions In today’s lesson we will look at:

Presentation transcript:

AOIT Introduction to Programming Unit 4, Lesson 11 Documenting Bugs and Fixes Copyright © 2009–2012 National Academy Foundation. All rights reserved.

How are bug/fix lists used in professional programming environments? As status information and an educational tool for internal purposes: As status information and an educational tool for external purposes: For each of these: - How similar is this to what you’ve done in this class? - What information would you include? - Where would you put the information? - Would you put the information in the program? # "internal" means inside the programming organization # "external" means for users or customers

Professional programmers are not likely to put bug/fix information in their programs There isn’t room: professional applications (even ones well tested) generate hundreds or thousands of bugs. Some programs are part of many products. Professional programming organizations take a “statistical” approach to their bugs and fixes: how many bugs, which chunks of code, how important, which release, which programmer, and who tested? Why would this data be important? What kind of software would you use to hold and report on this information?

Software companies keep internal and external bug/fix lists Typically bug/fix lists include the following types of data: Bug unique identifier or name Which release of the product has the bug Date the bug was reported Who reported the bug Who owns the bug (The person who will fix it) How important the bug is If the bug was fixed, when Would these items be part of an internal or external bug list (or both)?

Bug/fix lists are used for multiple purposes Bug/fix lists can be used for: Educational tools Status information for internal use Status information for external use You have used bug lists since the beginning of this course. For the culminating project, you will expand your bug/fix list format and focus.