Creating and managing projects

A project bundles everything that belongs to an undertaking: the configuration (artifact types, attributes, link types), the modules with the requirements, the links, baselines, reviews and change requests. Each project belongs to exactly one group; your role in the group determines what you may do in the project (Roles and permissions).

Creating a project

Projects → New project offers four ways:

1. New project with profile. The profile creates the basic configuration:
2. ISO/IEC/IEEE 29148 with heading, information, stakeholder requirement, system requirement, constraint, test case and glossary term, the attributes status, priority, verification method, acceptance criterion and more, and six link types.
3. Empty with only heading, information and requirement, for a completely custom configuration.

You adapt both afterwards under Properties. 2. From ReqIF. A requirements specification from DOORS, Polarion, Jama, Codebeamer or another tool is imported. Before importing, you check how types and attributes are mapped (Data exchange). Group admins start this way. 3. From backup. A complete ETRM backup (JSON) is restored as a new project, with configuration, modules, artifacts, links, comments and baselines. 4. Demo project. Loads the demo data set battery management system into one of your groups: configuration, modules, artifacts, links and two baselines. Ideal for trying things out; you can change everything in it.

After creating the project, the project overview opens. There you create the first module.

The project overview

The overview shows the modules with the number of their artifacts and leads to all areas of the project: all artifacts as a table, traceability (with the number of suspect links), baselines, reviews, change requests, metrics, glossary, data exchange and trash. Admins also see Properties. You edit the project description directly in the overview.

Projects in the project list

In the project list you find for each project:

• Rename (role EDIT and above),
• Copy into the same or another group, optionally with comments. The copy includes configuration, modules, artifacts, links and baselines. This is also how you create your own templates: set up a project with your configuration and basic outline and copy it for each new undertaking.
• Export as JSON (complete backup),
• Archive (ADMIN): the project is moved read-only to the list of archived projects and can be reactivated there.
• Delete (ADMIN).

The group filter hides projects of other groups; the filter is remembered.

Trash

Deleted artifacts end up in the project's trash. From there you restore them, including their former position in all modules.

Tip: Create a baseline or export a complete backup before major restructuring. Both take only one click.