The V cycle allow to manage different level of requirements (parent / child)
Project'Or RIA also allows it.
which are not mixed together in one table
This is not aV Cycle contraint, just a Project'Or RIA technical approach.
But in projectorria, I didn't find how to manage these different level of requirements separately (and the test linked)
You can use :
1) Parent Requirement to define hierachcal structure
2) Type of requirement to define a cycle base structure
3) A mix of both...
because they are all mixed in the same table of requirement
You can easily filter on the type ...
Consider the type as a logical way to split table information.
For instance, on Tickets, you can set a "Support" ticket type and a "Bug" ticket type. Even is they are stored in the same table, they have different functional meaning.
Maybe an explorer could help or other smart idea as the ones you have on projectorria.
What do you think about ?
The only on solution I found is to manage the different level of the V cycle using sub-projects of my main project. But I don't think it is very clean.
Is it the way you created projectorria on this subject.
No. Using types should be better.