Ticket #1226 (new enhancement)

Opened 2 years ago

Last modified 2 weeks ago

Plugin for writing requirements and specifications of a software

Reported by: Daniel Werner <dwarf007 ... moesbar ... net> Assigned to: anybody
Priority: high Component: Request-a-Hack
Severity: normal Keywords: requirements, specifications, plugin
Cc: fcorreia@gmail.com Trac Release: 0.10

Description

It would be unsefull to have a plugin allowing to write requirements and specifications of a software (in the way the ticketing system of trac is working).

The requirements could than later (during the project management) be linked to software problem reports or to the source code etc..

Attachments

Change History

02/20/07 07:20:52 changed by athomas

  • owner changed from athomas to anybody.
  • component changed from TracHacks to Request-a-Hack.

05/17/07 19:55:23 changed by anonymous

Yup, this would indeed be a very useful feature..

05/30/07 10:09:39 changed by anonymous

I support this also.

03/05/08 16:27:41 changed by leeus

Me too ... it would be great

05/12/08 05:30:33 changed by anonymous

I vote for this

05/12/08 05:31:14 changed by anonymous

  • priority changed from normal to high.

05/23/08 11:47:31 changed by yoheeb@gmail.com

I think a good model for this, might be a combination of tools. a macro to export requirements from other tool, specific to requirements management (example Telelogic DOORS), then a tool to import then, update them dynamically etc., and jam them into the wiki as linkable objects. I.e., export requirements to xml from tool X, check into /requirements of project subversion repository. new magic post commit hook script that updates Trac that a requirements document was "modified" or created in this example. extract requirements, formats them into a wiki-page, or set of pages. cross-links requirements where referenced by other requirements, etc. I used xml in my example, since I am thinking the next step is to allow meta data decoration of the data (section headings for the wiki format, tracibility information across different levels, or even across documents (system req to software req, to software design, to component req, etc.) Maybe I am thinking to big, but why not shoot for the moon?

08/04/08 05:24:14 changed by anonymous

This should also hook into the TestCaseManagementPlugin since in most workflows they are connected.

08/23/08 13:06:49 changed by anonymous

  • cc set to fcorreia@gmail.com.

Add/Change #1226 (Plugin for writing requirements and specifications of a software)




Change Properties
Action