You may want to have a dedicated project for Test (and Pre-Condition and Test Set) issues. In this scenario, Test Executions are the responsibility of other projects.
This separation allows you to manage permissions more effectively, so maybe only a few testers have permission to write tests and others only have permission to execute.
Of course, this use case can also be combined with the previous one by having separate projects for managing Requirements and Defects.
Architecture
| Number projects | 3 |
|---|---|
| Entities Organization | Requirements Test, Pre-Conditions & Test Sets Test Plan, Test Executions & Defects |
| Team Organization | QA team may be divided into users who write tests and users that execute test |
Advantages (Pros)
- This separation allows you to manage permissions more effectively, so maybe only a set of testers have permission to write tests and others to execute
- Keeps your existing requirements and defects project as-is, completely separated from testing related tasks
- Isolates Test specification and organization
Disadvantages (Cons)
- Requires manually synchronizing versions from the requirements project to the other ones
- More projects to manage
- More projects to maintain
- May promote team separation