CAD Forum - tips, tricks, discussion and utilities for AutoCAD, Inventor, Revit and other Autodesk products [www.cadforum.cz] ARKANCE | CONTACT - CZ | SK | EN | DE
RSS channel - CAD tips RSS tips
RSS discussions

Discussion Discussion forum

?
CAD discussions, advices, exchange of experience

CAD Forum - Homepage CAD discussion forum - ask any CAD-related questions here, share your CAD knowledge on AutoCAD, Inventor, Revit and other Autodesk software with your peers from all over the world. To start a new topic, choose an appropriate forum.

Please abide by the rules of this forum.
This is a peer-to-peer forum. The forum doesn't replace the official direct technical support provided by ARKANCE for its customers.
How to post questions: register or login, go to the specific forum and click the NEW TOPIC button.
  FAQ FAQ  Forum Search   Events   Register Register  Login Login

Topic ClosedBug Systems That Bugged Me

 Post Reply Post Reply
Author
AliveInTheLab View Drop Down
RSS robots
RSS robots


Joined: 20.Nov.2009
Status: Offline
Points: 425
Direct Link To This Post Topic: Bug Systems That Bugged Me
    Posted: 01.Jun.2010 at 04:00
Over my years in software development I have used many defect tracking systems (e.g. Scopus, Clarify, Bugzilla). Almost without fail these systems had a "priority" (a number between 1 and 5) that is specified as part of entering a defect into the system. The problem has been that the priority value was almost always tied to one factor. My experience has been that priority is determined based on two major independent factors: Severity is a measure of how bad something is. It is normally expressed in terms of the end user experience. Does it make the system crash? Does it cause loss of data? Or is it just an annoyance? Urgency is a measure of how soon a fix is needed? Should we drop what we are doing and fix this now? Can the correction wait until later? There's actually a third factor that most of these systems rarely consider: Frequency is a measure of how often or likely something can occur. I mention all three of these factors because defects can come in many of the combinations. Severity Urgency Frequency Example HIGH HIGH HIGH The application crashes upon startup. LOW HIGH HIGH Though it's only a typo in the User Guide, the copy is supposed to go to print today. HIGH LOW HIGH Even though the problem prevents the feature from operating at all, there is time before testing of that feature begins. HIGH LOW LOW Although the problem results in incorrect feature operation, it only happens in a special case that rarely occurs. As part of developing our technology previews, the Autodesk Labs team is currently using JIRA. JIRA is a system that lends itself to an Agile development process. As one would expect, in addition to the ability to manage development tasks, JIRA has the ability to track defects. Just like all of our previous systems, defects in JIRA are assigned a priority. You can see that the Priority field in JIRA attempts to be a mix of two of these factors. Urgency - Blocker, Critical Severity - Major, Minor, Trivial This is a welcome step in the right direction. I know there are It's Alive in the Lab readers who have their own defect tracking systems, What do you use to set the priority? Discussing how defects get classified is alive in the lab.

Go to the original post...

It's Alive in ihe Lab - Autodesk Labs blog by Scott Sheppard
Back to Top

Related CAD tips:


 Post Reply Post Reply
  Share Topic   

Forum Jump Forum Permissions View Drop Down



This page was generated in 0,148 seconds.