CSC 4700 Software Engineering

Slides:

Advertisements

Similar presentations

INTRODUCTION 1. Business systems and QA Department business systems 2. All the bug reports and all the bug tracking systems are very similar.

Advertisements

Object Oriented Analysis And Design-IT0207 iiI Semester

Task List a standardised Task List represents the different tasks involved in the proposal writing procedure, and allows a clear designation of responsibilities.

Configuration Management

Acceptance Testing.

INTRODUCTION 1. QA Department business systems 2. All the bug reports and all the bug tracking systems are very similar.

Project Management with TFS 1. What TFS offers for Project Management? Work Item tracking 2 Portfolio backlog Backlog Issue tracking Feature Product Backlog.

Software Delivery. Software Delivery Management  Managing Requirements and Changes  Managing Resources  Managing Configuration  Managing Defects 

1 Problem Tracking CSSE 376 Software Quality Assurance Rose-Hulman Institute of Technology March 14, 2007.

Paul Coffey Employee Central Engineering Manager

The Solution to Your Product Problems. Overview - What is PDS? ➲ Project Management System ➲ Web Based Easy to use Scalable ➲ Streamlined tools for software.

PowerPoint Presentation for IS-207 Copyright 2006 © Michael W. Schaffer. All rights reserved. Slide 1 System Analysis & Design Shrink-wrap Tools and Techniques.

Software Testing Prasad G.

1 CMPT 275 Software Engineering Revision Control.

Chapter 25 – Configuration Management 1Chapter 25 Configuration management.

Planning. SDLC Planning Analysis Design Implementation.

Configuration Management Avoiding Costly Confusion mostly stolen from Chapter 27 of Pressman.

CS4723 Software Validation and Quality Assurance Lecture 9 Bug Report Management.

Brainstorming & Project Management

H2K Infosys is business based in Atlanta, Georgia – United States Providing Online IT training services world wide. USA - +1-(770) ,

TEAM FOUNDATION SERVER (TFS) By Sunny Niranjana Devi. M.

Engineering H193 - Team Project Gateway Engineering Education Coalition P. 1Spring Quarter Project Management Week 2 Day 2.

Software Testing Online Training DEFECT TRACKING & CORRECTION

Dr. Tom WayCSC Software Processes CSC 4700 Software Engineering.

Scrum’s Product Owner Role Jeff Patton Agile Product Design

-Nikhil Bhatia 28 th October What is RUP? Central Elements of RUP Project Lifecycle Phases Six Engineering Disciplines Three Supporting Disciplines.

Software Testing Life Cycle

© 2012 IBM Corporation Rational Insight | Back to Basis Series Work on a Defect from QA Liu Xue Ning.

Painless Bug Tracking Michael Tsai 2011/9/30. Reference  html 2.

SERVICE MANAGER 9.2 CHANGE PRESENTATION JUNE 2011.

Tracking The Problem  By Aaron Jackson. What’s a Problem?  A suspicious or unwanted behavior in a program  Not all problems are errors as some perceived.

Deliverable Readiness Review LexEVS 5.1 December 17, 2009.

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

Improving engineering productivity APEGGA. Improving Productivity Mega Projects  History  What is needed  How will it be done  Division of Labour.

Copyright © 2003 by Trend Micro Inc. 建立世界級的軟體研發中心 Trend Micro Inc. Jeremy Liang NTU Seminar.

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

Rational Unified Process Mr Hisham AlKhawar. Iterative versus Waterfall  We need to use a life cycle model in order to approach developing a system easily,

Chair of Software Engineering Exercise Session 6: V & V Software Engineering Prof. Dr. Bertrand Meyer March–June 2007.

Test status report Test status report is important to track the important project issues, accomplishments of the projects, pending work and milestone analysis(

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.

European Middleware Initiative (EMI) The Software Engineering Model Alberto Di Meglio (CERN) Interim Project Director.

Eriq Muhammad Adams J | 03 |QA and Testing (1) Eriq Muhammad Adams J |

© 2012 Václav Rajlich Software Engineering: The Current Practice Ch Conclusion of software change The last phase of software change The activities.

CSC444F'07Lecture 41 CSC444 Software Engineering Top 10 Practices.

Agenda: Overview of Agile testing Difference between Agile and traditional Methodology Agile Development Methodologies Extreme Programming Test Driven.

Practice Array Web Process By Shengli Hu. Wads Practice 1 review wads everyday morning. mail assignment everyday. keep the status of wads reflect.

T Project Review Muuntaja I1 Iteration

ITEC 370 Lecture 20 Testing. Review Questions? Project update on F Test plan –Sections –How / when to use it.

JRA1 Meeting – 09/02/ Software Configuration Management and Integration EGEE is proposed as a project funded by the European Union under contract.

CSC 480 Software Engineering Team Issues. Essence of a Successful Team To be successful, teams must  Plan their projects  Track their progress  Coordinate.

Softheme Service Model Software Outsourcing Solutions.

Chapter 2- Software Development Process  Product Components  Software Project Staff  Software Development Lifecycle Models.

Software Testing-STLC

QA process for Business Catalyst projects.. Starting a project What QA needs to start testing::  Specifications – A detailed description of the product,

Chapter 25 – Configuration Management 1Chapter 25 Configuration management.

BU Power Tools & Accessories – PT&A Task management – Definitions

Introduction to CAST Technical Support

Configuration Management

SaralTA Batch-07 Software Testing Presented By - Chittaranjan M.

Software Testing Lab 1.

Improving the Defect Life Cycle Management Process

Configuration Management

The Software Development Cycle

Software Quality Engineering

Introduction to CAST Technical Support

© University of Liverpool

The Software Development Cycle

Software Testing Software Testing is a process of evaluating a system by manual or automatic means and verify that it satisfies specified requirements.

Presentation transcript:

CSC 4700 Software Engineering Bug Tracking CSC 4700 Software Engineering Dr. Tom Way CSC 4700

What is Bug Tracking Maintain a list of bugs in software Also maintain a list of features and tasks to be done Assign responsibility for each bug, feature & task Organize the work to be done Break up the work into “releases” or other deadlines Dr. Tom Way CSC 4700

Good Bug Report Steps to reproduce What you expected to see What you saw instead Dr. Tom Way CSC 4700

Bug Life Cycle Dr. Tom Way CSC 4700

A Bug’s Life 1) New: When QA files new bug. 2) Deferred: If the bug is not related to current build or can not be fixed in this release or bug is not important to fix immediately then the project manager can set the bug status as deferred. 3) Assigned: ‘Assigned to’ field is set by project lead or manager and assigns bug to developer. Dr. Tom Way CSC 4700

A Bug’s Life 4) Resolved/Fixed: Necessary code changes done, verified, bug status set as ‘Fixed’ and the bug is passed to testing team. 5) Could not reproduce: Developer is not able to reproduce the bug, markes as CNR. QA needs action to check if bug is reproduced and can assign to developer with detailed reproducing steps. 6) Need more information: If bug reproduce steps are not clear, mark it as “Need more information’. QA then needs to provide clearer description of steps. Dr. Tom Way CSC 4700

A Bug’s Life 7) Reopen: If QA is not satisfy with the fix and if bug is still reproducible even after fix then QA can mark it as ‘Reopen’ so that developer can take appropriate action. 8 ) Closed: If bug is verified by the QA team and if the fix is ok and problem is solved then QA can mark bug as ‘Closed’. 9) Rejected/Invalid: Some times developer or team lead can mark the bug as Rejected or invalid if the system is working according to specifications and bug is just due to some misinterpretation. Dr. Tom Way CSC 4700

What’s it good for? Works great for large teams – communication! For small teams, good organizational tool even if everybody knows what is going on anyway Great for planning releases and other deadlines Also is good documentation for work being done – creates an automatic “paper trail” Dr. Tom Way CSC 4700