Regardless of industry or company size, when deploying Jama Connect, teams must decide how best to structure information in their Jama projects. Typically, the following two approaches are considered:
- Functional Product Structure: Projects are structured to align with the hierarchical breakdown of product definition (e.g., system/subsystems) and/or the organization of teams/disciplines.
- Document-centric Structure: Projects are structured to align with documentation needs, whereby the project's Explorer tree basically becomes the Table of Contents for the document.
In the example below, the Functional Product Structure is organized by levels of requirement abstraction and disciplines. Contrast that with the Document-centric Structure, where components in the Explorer are essentially "documents".