[IGSTK-Developers] Re: Requirements on the Bug Tracker

[M. Brian Blake]

David,

You are correct on the current process for requirements. 


You can actually set up your view of the bug tracker to see descriptions instead of just the number.  Have you set up a login to the bug tracker?  I think that once I got a personal login, I immediately was able to the the list of requirements with more detail. 

Hope this helps.

-BRian 

M. Brian Blake, Ph.D
Assistant Professor
Georgetown University
Washington, DC 20057
mb7 at georgetown.edu
http://www.cs.georgetown.edu/~blakeb/

----- Original Message -----
From: David Gobbi <dgobbi at atamai.com>
Date: Wednesday, June 8, 2005 12:35 pm
Subject: Requirements on the Bug Tracker

> Hi Brian,
> 
> In order to move forward with the tracking code, I need to 
> generate some 
> new requirements so that me and Hee-Su can add certain pieces of 
> code to 
> CVS.  I took a look at the "Requirements Process" diagram on the 
> wiki, 
> and it looks like the approach that I should take is the following:
> 
> 1) I add the requirement to the "Design Discussions" section of 
> the wiki 
> so that people can have a look
> 2) The requirement is discussed at the t-con
> 3) If the requiment is accepted, you add it to the bug tracker so 
> that 
> it can go into CVS
> 
> This is straightforward, but I have a couple questions about the 
> bug 
> tracker:
> 
> What do the bug tracker requirement numbers e.g. REQ 05.07.03 mean?
> 
> Also, when you add requirements to the bug tracker, would it be 
> possible 
> to add a short description of the requirement to the bug summary 
> like this:
> 
> REQ 05.07.04 - Each IGSTK component requires PrintSelf
> 
> instead of just the requirement number "REQ 05.07.04"?  The way 
> the 
> requirements are listed on the bug tracker right now, I have to 
> click on 
> the requirement to read a description, and it would be much more 
> convenient if requirements had a short summary like the bugs do.
> 
> - David
>