[IGSTK-Developers] Extracting requirements from the bug trackerto latex file

[Kevin Cleary]

Hi everyone:

I just wanted to comment that this is very nice progress on the requirements
document. As we have mentioned, requirements documentation is very important
to the overall project and it is good to see this evolving.

I am flying back from Berlin on Sunday and will be on the tcon next week.

Kevin
  
------------------------------------------------------------------
Kevin Cleary, Ph.D.                        Work phone: 202-687-8253
Associate Professor                        Work fax: 202-784-3479
Deputy Director  
                            
Imaging Science and Information Systems (ISIS) Center
Department of Radiology                    Pager: 202-901-2033
Georgetown University Medical Center       Cell phone: 202-294-3409
2115 Wisconsin Avenue, Suite 603           Home phone: 301-299-0788
Washington, DC, 20007                      Home fax: 301-299-0789
 
ISIS center: www.isis.georgetown.edu
Research group: www.caimr.georgetown.edu
WashCAS: www.washcas.org
Email: cleary at georgetown.edu
-------------------------------------------------------------------

-----Original Message-----
From: igstk-developers-bounces+cleary=georgetown.edu at public.kitware.com
[mailto:igstk-developers-bounces+cleary=georgetown.edu at public.kitware.com]
On Behalf Of David Gobbi
Sent: Thursday, June 23, 2005 8:59 PM
To: Andy Cedilnik
Cc: IGSTK-developers
Subject: Re: [IGSTK-Developers] Extracting requirements from the bug
trackerto latex file

Hi Andy,

The latex requirement document was discussed at the IGSTK t-con, and we 
decided to move ahead with it.  The python script just needs to be 
completed so that it produces a complete latex document (see attached), 
and so that it runs pdflatex to produce a .pdf file and then posts that 
file somewhere on the web.

The pdf file could go into the nightly doxygen documentation, into the 
nightly dashboard directory, or somewhere on the wiki.

If you can dedicate the time, there was also an interest in adding 
section headings according to the attached taxonomy document.  These 
were not considered to be absolutely necessary, but would be a very nice 
feature.

 - David

Andy Cedilnik wrote:

>Hi All,
>
>Here is script that I can run every night. It produces the attached
>file. Let me know if the format is ok.
>
>Current problems:
>
>* Handle special characters
>* Do something with NEW_REQ_TEXT
>
>#!/usr/bin/env python
>
>import MySQLdb
>import sys
>
>HOST      = '****'
>DATABASE  = '****'
>USER      = '****'
>PASSWORD  = '****'
>
>
>sql = MySQLdb.connect(db=DATABASE, host=HOST, user=USER, passwd=PASSWORD)
>cursor = sql.cursor()
>cursor.execute("SELECT bug_id, title, description FROM phpbt_bug WHERE
>project_id = 10;")
>
>bugs = {}
>comments = {}
>
>while 1:
>  res = cursor.fetchone()
>  if not res:
>    break
>  if not bugs.has_key(res[1]):
>    bugs[res[1]] = res
>  else:
>    print "Problem!! Found two bugs with the same requirement:\n%s\n%s"
>% (`res`, `bugs[res[1]]`)
>    sys.exit(1)
>  comments[res[1]] = []
>
>ks = bugs.keys()
>ks.sort()
>
>for a in ks:
>  if a.startswith("REQ"):
>    bug = bugs[a]
>    print "\section{%s - %d}" % (a, bug[0])
>    print "%s" % bug[2]
>    print ""
>    cursor.execute("SELECT comment_text FROM phpbt_comment WHERE bug_id
>= %d;" % bug[0])
>    while 1:
>      res = cursor.fetchone()
>      if not res:
>        break
>      print res[0]
>
>  
>