Bugzilla for beginners how to#
Bugzilla for beginners software#

Bugzilla for beginners software#

Requirements management also includes tracking the status of individual requirements and tracing requirements both backward to their origins and forward into design elements, code modules, and tests' (Karl Wiegers, More About Software Requirements, Microsoft Press, 2006, pp. Maybe it will help the discussion to include one expert's definition of requirements management in order to evaluate whatever tool or methodology you are considering: 'The central purpose of requirements management is to manage changes to a set of agreed-upon requirements that have been committed to a specific product release. (Note that it is possible to keep the NIRG file in a project and under version control.) One imports requirements into NIRG to facilitate traceability and generate reports based on the links one establishes. Yes, Chris, I glossed over the important distinction that one doesn't, for instance, write requirements in NIRG.

Bugzilla for beginners how to#

Jeff will be uploading his NI-Week presentation soon which will explain that a little further, and how to include it into your process. I RG, and we use it here, but it doesn't manage your requirements, it traces them. Real quick note: Requirements Gateway isn't a requirement management tool - it's a requirement traceability tool. Traceability is demanding to do even with the right tools for the job!

In short, I would recommend using a requirements management tool designed for the job (DOORS, Requirements Gateway, traceability within Enterprise Architect), which I think one will need for a project of any significant complexity. On the other hand, this is not document-centric and thus it would be difficult, if not impossible, to generate a report indicating which requirements one has linked to design, or to a test plan, or to test results, or to code.Ģ) While some level of hierarchy is also possible (JIRA lets the user define subtasks) simply entering issues does not allow the issue tracker to present the requirements in a single structured document (especially if one adds or removes requirements later!). (We can do this in the issue tracker we use, JIRA). Mind you, my first inclination was that it wasn't a good idea, but I decided to try and figure out what the advantages and disadvantages were.ġ) It may be possible to establish some sort of traceability in certain issue tracking tools if you can link issues to one another. I found the idea of using a bug tracker for requirements management intriguing.