Projects
Overview
Section titled “Overview”A workspace can have multiple requirements projects. Each project includes a name, a key, and a description.
Pro Tip: If you enable AI features, the description will be used as context. Therefore, provide a detailed explanation, including the meaning of internal abbreviations, if applicable.
Managing Projects
Section titled “Managing Projects”Adding Team Members
Section titled “Adding Team Members”After creating a project, remember to add your team members. By default, only you have access to the project. Workspace owners can also view the project and grant themselves access.
Organizing Requirements
Section titled “Organizing Requirements”Each project features a folder/module structure to help you organize your requirements:
- For smaller projects, we recommend using only modules without folders.
- For larger projects, you can structure your modules into folders for better organization.
Note: Modules are not sorted alphabetically but follow the order in which they are created or reordered. This ordering impacts several aspects:
- Numbering of requirement headings (if module numbering is enabled).
- Ordering of requirement elements in the graph view.
Best Practices
Section titled “Best Practices”We recommend placing higher-level or external requirements at the top, with increasing detail as you move downward. This approach ensures clarity and logical progression.
Project Settings
Section titled “Project Settings”In the project settings, you can:
- Export the project.
- Enable or disable AI features.
- Enable or disable the numbering of elements across modules.