Thank you for a great tool. We are evaluating version 4.1 I have read all the PDF tutorials on version 4.1, and mail list archives in respect to exporting requirements. We would like to use Topcased to capture requirements from use cases, then export these to a tool to track development tasks.
The approach to requirements in Topcased appears to assume that 1. requirements are created outside Topcased 2. these are imported as 'upstream' requirements 3. current requirements are created on aspects of the model 4. upstream requirements are mapped to current requirements (bidirectionally in the UI) 5. the requirements matrix with this mapping can be exported - making evident which showing upstream requirements have not been mapped to current requirements We do not want to create upstream requirements and import them, we want to build use cases in Topcased and capture the requirements from them in Topcased, we can do this and end up with 'current' requirements. We then want to export the 'current' requirements, the export format of the export traceability matrix is fine, then import them into another tool Is there a way to export current requirements when no upstream requirements exist? If not, can we somehow turn 'current' requirements into upstream requirements? thanks very much
_______________________________________________ Topcased-users mailing list [email protected] http://lists.gforge.enseeiht.fr/mailman/listinfo/topcased-users
