At a high level, the data model (domain model) connects three major areas in project management: People, Work and Plans.
People, or users, can be allocated to multiple projects and assigned to many teams. The user’s team and/or project membership determines which work items will be visible to them and what they will be able to modify.
In simple cases, such as when each team only works on one project, using teams is not necessarily required. For more complex cases, such as when many teams work on a single project or one team works on multiple projects, it is necessary to create teams in Targetprocess. Additionally, make sure you assign the teams to the projects they will be working on. It will not be possible to assign work to a team without this Team-Project relation. Read more about Teams and Projects relations.
The different work entities are organized into a hierarchy as shown in the picture above. This gives you the ability to track the progress of higher level entities (such as projects) based on the progress of lower level entities (such as features and user stories).
You can customize what different entities are called by changing your Process's terms, and it's possible to setup custom workflows to map your own unique process.
Planning entities represent a set period of time during which a defined scope of work should be completed. The diagram above describes what planning entities are available in Targetprocess.
Also included is an integrated testing module. This allows you to create and manage test cases at the user story level, organize them into test plans that cover the required testing on a feature, release, or project, and execute them as many times as required. With the ability to link test cases and test plans, you can reuse the existing tests without copying them. Read more about the Test Area in Targetprocess.
A complete diagram of data hierarchy and structure can be found here.