Your first project

With the concepts in hand, here’s how to go from an empty workspace to a project you can build in.

Create the project

From the project selector, create a new project and give it a clear name — typically the product, product line, or variant it represents. Depending on your organization’s setup, you may start from a template that comes preconfigured with item types, workflows, and settings aligned to your process, so you’re working to your standards from the first record.

Choose its modules

A project uses the modules that suit its work. Confirm that the modules you need — Requirements, Architecture, Tests, Risks, SBOM, and the rest — are enabled for the project. Module access is configured per project, so you can keep a project focused on what’s relevant.

Add your first records

Open the Requirements module and create a requirement. Notice that it’s a full record — fields to complete, a lifecycle state, and a version history that begins immediately. Add a few requirements to give yourself something to build on.

Start the thread

Now connect your work. Create a test case and link it to a requirement it verifies; add an architecture element and link it to the requirement it realizes. As you add links, the thread takes shape — and the Traceability module and your dashboards begin to show live coverage.

Where to go next

From here, dive into the module for whatever you’re working on. Each section of this documentation covers one module in depth, starting from its overview. A good next stop is Requirements, where most programs begin.