This is possible since V3.3.
Tests sessions now appear in the Gantt planning ,like any activity.

Dear Babynus,

thank you for your answer.

However, I think with my english I didn't expressed what I thought. I'll try hereunder to re-edit it.

how can I make complete requirement based engineering with projectorria ? Is it possible ?

The V cycle allow to manage different level of requirements (parent / child) which are not mixed together in one table. And the number of requirements is very high (thousands of).

But in projectorria, I didn't find how to manage these different level of requirements separately (and the test linked) easily, because they are all mixed in the same table of requirements or tests if I try to manage a V cycle in one project.
So with thousands of requirements, it is quite difficult to have an easy and quick view of all these requirements.

Maybe an explorer could help or other smart idea as the ones you have on projectorria.

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.

What is your point of view on the V cycle management by projectorria ?

Thank you in advance,

Luckydigit

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.

Dear Babynus,

Thank you for your answers, we will see what the result will be.

To complete our exchange :

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...

Is the hierarchical structure of parent requirements visible on the table view ?
What is the effect to affect a parent requirement to a requirement. Idem for test cases. Is there a visual effect, or a report/status effect ?
For example, I see that for activities and test sessions, it is used for gantt planning.

Maybe an explorer could help or other smart idea as the ones you have on projectorria.
What do you think about ?

It is linked to the point above : how to see the visual effect of the hierarchical structure between parents and children ?
The explorer for me is an idea to see a visual effect as the explorer of the left part of projectorria, or the explorer that we can have in gantt planning.

An other idea could be to organise the requirements or test cases in the requirement table or test cases table as in the project view with the WBS, to have a visual hierarchical structure.
But I don't know if it is technically possible ?

Thank you in advance,

Luckydigit

Is the hierarchical structure of parent requirements visible on the table view ?

Unfortunately not.

What is the effect to affect a parent requirement to a requirement.

Not much. In current version, it is only informative.

Idem for test cases. Is there a visual effect, or a report/status effect ?

Including one parent test case on a test session will automatically includ sub-tests in the session. That's all.

For example, I see that for activities and test sessions, it is used for gantt planning.

Yes, but not yet for Requirements.
Test sessions have gained this functionality in V3.3. Maybe requirement could get it in a further version (not planned yet).

An other idea could be to organise the requirements or test cases in the requirement table or test cases table as in the project view with the WBS, to have a visual hierarchical structure.
But I don't know if it is technically possible ?

It is technically possible. Global design is prepared for such possibility.
If it is a real need for you, maybe you can request an evolution, and possibly sponsor it.
Have a look at "Services" => "Evolutions" 😉