Hello Richard,
I'm using trac (of course) and svn. My problem about tracking a
requirement is basic: i need to know the classes involved in the
implementation of a requirement.
With svn you can label using a serial but there is no "direct way" to
track a "requirement thread". I keep searching for a answer.
Thanks!.
Richard Mixon schrieb:
Before deciding on a solution, what are you going to do with this
information.
If it just for the next person working on the source to see? In that case,
just come up with a standard format to include in the comment - e.g.
/*
* CHANGE_ID: XXXXXX
* CHANGE_DESC: This change was to support ...
*/
But this is so 1970's - reminds me of all the assembler and COBOL programs
in years past :)
I think there are two better approaches:
1) Most source config and control systems (CVS, Subversion, etc) support
some kind of tagging that will create comments for the latest revision. You
might look at your SCCS and see what similar tags it has that might allow
you to provide the comment associated with a particular revision when it was
checked in. When you check in your comment would have to include a reference
to the requirements ID.
2) A better solution is something like Trac or JIRA. They associate issues
(which could be requirements in your case) with check-ins to source. You can
go to any issue and see what source was checked in aginst the issue ID and
you can go to any source module and see all the issues that have worked on
that source.
You can set rule so that an issue reference is required when you check in
the source.
Here are links for JIRA (a commercial product) and Trac (open source, free):
JIRA - works with CVS, Subversion and others it think
http://www.atlassian.com/software/jira/
TRAC - mostly works with Subversion
http://trac.edgewall.org/
I am sure there are other solutions out there also.
Hope this helps.
From: "Leo Barrientos C." <[EMAIL PROTECTED]>
Reply-To: <[email protected]>
Date: Tue, 03 Jun 2008 16:48:25 +0200
To: <[email protected]>
Subject: [appfuse-user] Requirements tracking tag
Hello, i need to track requirement-related methods in the source code.
All my requirements has a ID - like: Requirement 120, Requirement 140, etc.
I was thinking in a javadoc tag like @requirements to use like usual
javadoc documentation, but i think javadoc tags is not easy to extends
...[i think]
Any idea?
Thks a lot.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
