How to integrate requirements with JDeveloper

Question

It is widely considered helpful to be able to track certain parts of the code or of a model back to the original requirements.
As I understand, JDeveloper does not deal with bare requirements at all, so I have to maintain them in some other software or a bunch of documents. When I begin designing a business application in JDeveloper, how do I link this design and the resulting code to the original requirements?
<ul><li>     Any thoughts?</li>
<li>Any best practices?</li>
<li>Any reaction from the JDeveloper developers?</li>
<li>Or am I just getting it wrong?</li>
</ul>
Thank you for your responses,
Matt

Answer 1

So JavaDoc and TODO-like tags seem to be the only ways to reference requirements. I can imagine this requires a lot of discipline in large teams.
Shay, could you provide me with some more information, maybe a presentation about the planned ALM features of the next release? I'm working on my diploma/master thesis at an oracle partner company, comparing the development features of JDeveloper and ADF to the state of research. As the current version is behind on support for proper requirements management and change management, I'd like to give a perspective on your future developments.
Vik, the idea is to be able to trace a certain requirement ("user must be able to alter limit at any time") to all affected parts of the code and vice versa, so that when the requirement is (about to) being changed, the impact can be evaluated and all necessary changes can be made easily. Also, quality management can trace tricky code back to the reqiurements and replan them. This is of most interest to companies with a rather structured software engineering process.