Subsystems Management

This article explains how to manage project subsystems in Reqode:

• view and reorder the subsystem list,
• create, edit, and delete subsystems,
• open subsystem versions,
• open Subsystem Architect from the list.

Where to find in UI

• Project Settings → Subsystems

Prerequisites

• User is a member of the project.
• Permissions scope: Project Settings.

Step-by-step

View subsystems list

1. Open Project Settings → Subsystems

Reorder subsystems

1. In the list, drag a row using the drag handle on the left.
2. Drop it in the new position.

Result: the list order is updated without a full page reload.

Create a new subsystem

1. Click + on the Subsystems list.
2. In the Subsystem Editor (General tab), fill in:Name (required)Identifier (required, 1..16, A–Z a–z 0–9 -, unique)Requirements Subsystem Manifest (optional)
3. Name (required)
4. Identifier (required, 1..16, A–Z a–z 0–9 -, unique)
5. Requirements Subsystem Manifest (optional)
6. (Optional) Open the Code tab and fill:Baseline Code Branch (optional)Implementation Subsystem Manifest (optional)
7. Baseline Code Branch (optional)
8. Implementation Subsystem Manifest (optional)
9. Click Submit.

Edit an existing subsystem

1. In the subsystem row click ….
2. Select Edit.
3. Change fields in General and/or Code tabs.
4. Click Submit.

Delete a subsystem

1. In the subsystem row click ….
2. Select Delete.
3. Confirm deletion.

Notes:

• Only Admin can delete.
• Deletion can be blocked if the subsystem is used in requirements.

Open Subsystem Versions

From the subsystem row menu … → Versions.

For details, see Subsystem Versions (Product Guide article).

Open Subsystem Architect

1. In the subsystem row click ….
2. Select Subsystem Architect.

Result

• Subsystems are created/updated and immediately visible in the list.
• You can manage subsystem metadata, AI guidance, and access versions.

Errors / Constraints

• Identifier required and must match constraints: 1..16, A–Z a–z 0–9 -, unique.
• Delete confirmation is required.
• Delete blocked if subsystem is referenced by requirements.

Best practices

• Create subsystems early (before mass requirement creation) to avoid later re-assignment.
• Use stable identifiers; treat them as a public short code within the project.
• Keep the subsystem list ordered by user value (e.g., main subsystem first).