Christopher Taylor wrote:
> On Thu, Aug 28, 2008 at 6:45 AM, Ted Gifford wrote:
>
>> ...
>> To associate the
>> requirement attributes with a given text, you could create a macro to
>> interpret something like this
>>
>> {{{
>> #!Requirement
>> #!type: functional | nonfunctional | security | etc.
>> #!heading: Requirement Title
>> #!summary: A brief description of the requirement.
>> The paragraph(s) describing the requirement, containing __WikiFormatting__
>> or [Macros]
>> }}}
> Here's another idea:
>
> define a ticket type called requirements. Use master tickets to
> associate Requirement <= Architectural Component <= Design Component
> <= Unit Test Case <= Integration Test Case ... etc you get the idea
>
> Then create a plugin to create the document from the tickets. You'll
> get things like traceability etc from doing it this way.
>
The OP didn't want to enter requirements as separate tickets. If we add
your idea, the workflow might look like
1. Write the requirements in the wiki.
2. Create requirements tickets from the wiki (via macro or otherwise).
3. Use master tickets or a ticket workflow system to aid creation of the
component and test case tickets.
Ted
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Trac
Users" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/trac-users?hl=en
-~----------~----~----~----~------~----~------~--~---
