Se ha denunciado esta presentación.
Utilizamos tu perfil de LinkedIn y tus datos de actividad para personalizar los anuncios y mostrarte publicidad más relevante. Puedes cambiar tus preferencias de publicidad en cualquier momento.

change management

708 visualizaciones

Publicado el

Publicado en: Tecnología, Empresariales
  • Sé el primero en comentar

change management

  1. 1. Change management and bug tracking, with emphases on using Bugzilla as an example tool<br />By Ian Vaughan<br />(<br />
  2. 2. Overview<br />Explain what is<br />A bug<br />bug report and <br />a bug-tracking system<br />Explain the Bug Lifecycle <br />Question time<br />can also be asked throughout the talk<br />2<br />
  3. 3. Bug report<br />A Bug is a report <br />raised<br />reported by<br />and filled in by stakeholders of a system<br />A Bug is <br />anything that needs a conclusion recorded<br />3<br />
  4. 4. Bugzilla<br />Bug-tracking system<br />Web based front end<br />SQL database backend<br />4<br />
  5. 5. Bugzilla<br />Open source software (OSS)<br />Mozilla Public License<br />Released in 1998<br />Still actively developed<br />Version 4.0 just released in Feb 2011<br />5<br />
  6. 6. Why Bugzilla<br />Alternatives :-<br />Email<br />Excel<br />COTS<br />Bugzilla :-<br />Free<br />Configurable<br />Customisable<br />6<br />
  7. 7. Why Bugzilla<br />Advantages :-<br />powerful search<br />email notifications<br />change history<br />many reporting options<br />Disadvantages :- <br />Free-form text description field<br />7<br />
  8. 8. Bug Lifecycle<br />8<br />
  9. 9. Find/discover bug<br />Found a problem?<br />Using latest release?<br />Always search first<br />Avoids duplication<br />9<br />
  10. 10. Simple Search<br />10<br />
  11. 11. Search Results<br />11<br />
  12. 12. New bug fields<br />Product<br />Component<br />Version<br />Summary<br />Description<br />12<br />
  13. 13. Other fields<br />Severity <br />Blocker / Critical <br />Major <br />Normal <br />Minor <br />Trivial / Enhancement<br />Hardware & OS<br />13<br />
  14. 14. Raise new bug<br />14<br />
  15. 15. Actioningnew bugs<br />Bug gets assigned to someone<br />They get emailed<br />They decide what should be done<br />Will set it as Assigned, and set the<br />Target Milestone<br />Priority<br />15<br />
  16. 16. Assigned<br />Active / In-progress<br />More information might be required<br />Gets fixed “Resolved”<br />Comments added stating the Changes made<br />16<br />
  17. 17. Resolved<br />Fixed <br />Invalid <br />Wontfix<br />Duplicate <br />Worksforme<br />17<br />
  18. 18. Verified<br />Very important stage<br />Validates everything done<br />Tested<br />18<br />
  19. 19. Reopened<br />Reassigned back to the engineer that stated it was Fixed<br />The Fixed-Reopened loop can continue<br />19<br />
  20. 20. Closed<br />Final state of the bug lifecycle<br />A record of what was raised and fixed for reporting and historical searches<br />20<br />
  21. 21. Conclusion<br />I have covered :-<br />What a bug and bug report is<br />What Bugzilla is, and<br />A basic overview of how it works<br />A bug Lifecycle, and how it relates to Bugzilla<br />Any questions?<br />21<br />
  22. 22. Sources<br /><br /><br /><br /><br /><br /><br /><br />22<br />
  23. 23. Thank you<br />Contact: Ian Vaughan<br /><br />23<br />