Re: JIRA as a requirement management tool

Hi,
at the moment (in the beta version that will be released in few days)
you can link test to functional requirements, and have search/monitor facilities to see if all your requirements are covered by tests, and test creation shortcuts..

In the alpha version a lot of new features about technical writings, issues creation and requirements will be added.

With PeRM (Peak Requirements
Manager), Peak Solution offers
JIRA users a powerful plugin for
the professional management of
requirements. The easy-to-use
dialog interface enables
systematic administration and a
clear representation of
requirements in tree structures
and freely definable tables, as well
as allowing the user to specify
different detailed views for
individual requirements. To
provide a structure for more
extensive projects, requirements
can be divided into groups and
linked to one another.
Administration of the application is done entirely in JIRA: The projects are set up, access
authorization for various users is determined and attributes for the description of
requirements are defined. Generic access to JIRA is granted through the PeRM client via
WebServices on the basis of SOAP.
To supplement textual requirements with graphic UML models, as well as generating
specialist concepts and detailed specifications, the information from PeRM can be forwarded
via a standardized interface to the Enterprise Architect modeling tools of the company Sparx
Systems.
Overall, the low administrative effort and the straightforward licensing costs make PeRM a
solution that can be used quickly and simply, even by small project teams, to implement
professional requirement management.
Since all requirements are stored in the JIRA as a ticket, the solution also guarantees a
seamless transition from requirement management to task and release management. This
makes PeRM an important component in an integrated software lifecycle process.
A fully functional evaluation license for PeRM can be requested via the corresponding contact
form on the homepage of Peak Solution.
--
Post by peak_solution - online at:
http://forums.atlassian.com/thread.jspa?forumID=46&threadID=26331_______________________________________________
Jira-user mailing list
[hidden email]To unsubscribe or change your options visit this page:
http://lists.atlassian.com/mailman/listinfo/jira-user

1. Capture: Jira UI is quite customizable, so it's a good tool to capture information in a manual way through forms. But modern RM tools can import many document formats (mainly MS Word) allowing to capture requirements (issues) on them. Jira not. Well, you may use Confluence to view MS Word documents and relate issues from Confluence....

2. Analisys/Engineering: Jira does nothing. Of course, Jira is extensible and you may use some plugins for that. For example, you might use Gliffy for User Case diagrams.

4. Traceability: Jira allows Issues to be related but it does not provides a powerful UI to explore those relationships (no matrix, no tree,...). Since Jira 4.x, complex queries can be answered using the new query feature.

5. Validation: You may create some sort of Issue to support test cases and relate them with requirements. Workflows may also help. But there is not much help for validation out of the box.

6. Reporting: quite enough?

7. Baselines: are they supported? You may track the changes/history at issue level, but is it also possible at project level? And comparing two states of a project?

1. Capture: Jira UI is quite customizable, so it's a good tool to capture information in a manual way through forms. But modern RM tools can import many document formats (mainly MS Word) allowing to capture requirements (issues) on them. Jira not. Well, you may use Confluence to view MS Word documents and relate issues from Confluence....

2. Analisys/Engineering: Jira does nothing. Of course, Jira is extensible and you may use some plugins for that. For example, you might use Gliffy for User Case diagrams.

4. Traceability: Jira allows Issues to be related but it does not provides a powerful UI to explore those relationships (no matrix, no tree,...). Since Jira 4.x, complex queries can be answered using the new query feature.

5. Validation: You may create some sort of Issue to support test cases and relate them with requirements. Workflows may also help. But there is not much help for validation out of the box.

6. Reporting: quite enough?

7. Baselines: are they supported? You may track the changes/history at issue level, but is it also possible at project level? And comparing two states of a project?

Re: JIRA as a requirement management tool

Thanks. I use my own solution. At the present I'm focused in writing the most flexible and powerful tool to manage document content. So I'm integrating the best available software to achieve that.

I've already written a piece of code to integrate Subversion as documentation repository, OpenOffice as document server, Flash as document viewer and Jira as document content management. It is finished and I'm waiting for the Jira plugin approval in order to officially publish it.

As I've a strong tech skill but not a marketing skill, I guess it will be ignored for a long time by the community :(, though really it is a nice piece of code able to convert Jira in the best place to manage requirements.