Use cases

Most teams already have some of their ALM: a tracker, a code host, a wiki. Here is how ALM OS fills in the rest in eight real set-ups — which plugin does what, what the team gains across tools, and which licence it needs.

Jira and Google Drive, nothing for requirements

How the tools connect

Already in use

  • Jira
  • Google Drive (planned)
ALM OS core links · Needs review · impact · baselines · evidence report

Added with ALM OS

  • ReqManTool · free
  • Test results · paid
  • Documents · paid

Starting point

A product team plans and tracks its work in Jira and keeps specifications and plans as files on Google Drive. Requirements live in documents and spreadsheets; test results stay in CI.

What is missing

No managed requirements, no link from a requirement to the Jira story that implements it or the test that verifies it, and no frozen record of what was released.

Licence

Free: the core, ReqManTool (up to 5 modules), sign-in, My work and the calendar. Paid: Jira, Test results and Documents.

How ALM OS fills it

  • ReqManTool, inside ALM OS, holds the requirements and test cases: modules, attributes, links, ReqIF and Word export.
  • The Jira plugin reads epics, stories, tasks and bugs — and Xray or Zephyr Scale tests, if the team uses them. New issues can be created in Jira from ALM OS.
  • The Test results plugin reads the JUnit XML or Robot Framework files the CI writes.
  • Documents keeps the controlled versions of plans and specifications. A Google Drive plugin is planned; until it is available, the files that need control are uploaded to Documents (whole folders can be dragged in).
  • People sign in with Google Workspace through OpenID Connect; their meetings come into My work from Google Calendar’s secret iCal address.

What they gain

  • Each requirement traced to the Jira stories that implement it and the tests that verify it, with the coverage and the gaps in one matrix.
  • The links appear in Jira as remote links, so developers see the requirement on the issue.
  • When a story or a requirement changes, its links turn to Needs review.
  • One release baseline across ReqManTool, Jira, the test results and Documents, signed off by independent people, with an evidence report for the assessor.
  • My work lists each person’s Jira issues and requirement reviews next to their meetings.

Open this set-up in the configurator →

A team that lives in GitLab

How the tools connect

Already in use

  • GitLab
ALM OS core links · Needs review · impact · baselines · evidence report

Added with ALM OS

  • ReqManTool · free
  • Test results · paid

Starting point

Code, merge requests, issues and CI pipelines are all in GitLab. Requirements are written in issue descriptions or wiki pages; test reports are pipeline artifacts.

What is missing

No managed requirements, no requirement-to-merge-request trace an assessor can follow, and no record of which tests passed for a release.

Licence

Free: the core, ReqManTool (up to 5 modules), sign-in through GitLab and My work. Paid: GitLab and Test results.

How ALM OS fills it

  • ReqManTool for the requirements and test cases.
  • The GitLab plugin reads merge requests, commits and issues, creates issues from ALM OS, and signs people in with their GitLab accounts.
  • The pipelines copy their JUnit reports to a folder the Test results plugin reads.

What they gain

  • Requirements linked to the merge requests and commits that implement them; each link is written as a note on the merge request.
  • Coverage of the requirements by passing tests, with the gaps.
  • A baseline pins the repository at a commit and records the merge requests, issues, requirements and test results together.
  • Requirements reviewed and approved in ALM OS: review packages, findings, votes and independence.
  • My work lists each person’s GitLab issues and the merge requests waiting for their review.

Open this set-up in the configurator →

Azure DevOps and SharePoint

How the tools connect

Already in use

  • Azure DevOps
  • SharePoint
  • Entra ID
ALM OS core links · Needs review · impact · baselines · evidence report

Added with ALM OS

  • ReqManTool · free
  • Microsoft 365 calendar · free

Starting point

Work items, repositories and test plans are in Azure DevOps; specifications, plans and reports are in a SharePoint site; everyone has a Microsoft 365 account.

What is missing

Nothing ties a SharePoint document to the work items and tests it covers, and nothing freezes Azure DevOps and SharePoint together for a release.

Licence

Free: the core, sign-in with Entra ID, My work with the Microsoft 365 calendar, ReqManTool (up to 5 modules). Paid: Azure DevOps and SharePoint.

How ALM OS fills it

  • The Azure DevOps plugin reads Boards work items, Repos pull requests and commits, and Test Plans test cases, runs and results, from Azure DevOps Services or Server.
  • The SharePoint plugin reads the documents of the site’s libraries through Microsoft Graph, or from a library synced by OneDrive.
  • Both plugins only read: work items and documents are still changed in Azure DevOps and SharePoint.
  • People sign in with Microsoft Entra ID, and My work shows their Teams and Outlook meetings. ReqManTool can be added for requirements managed DOORS-style.

What they gain

  • Documents linked to the work items, pull requests and test results they concern; a document’s links turn to Needs review when its content changes.
  • One baseline across Azure DevOps and SharePoint: each work item at its revision, each document identified by its content hash.
  • Impact analysis across both tools before a change is approved.
  • An evidence report per baseline for the assessor.

Open this set-up in the configurator →

An on-premise railway supplier: Redmine, Jenkins and JFrog

How the tools connect

Already in use

  • Redmine
  • Jenkins
  • JFrog
  • LDAP / Active Directory
ALM OS core links · Needs review · impact · baselines · evidence report

Added with ALM OS

  • ReqManTool · free
  • Gerrit · paid
  • Risk & Safety · paid
  • Documents · paid

Starting point

A signalling supplier runs everything on its own servers: Redmine for tasks and problem reports, Jenkins for builds, JFrog Artifactory for binaries, plain git repositories and Active Directory. Some sites have no internet access.

What is missing

Requirements, the hazard log and code reviews with independence by SIL are kept by hand, and nothing shows which requirements, reviews, test results and binaries make up a delivered release.

Licence

Free: the core, ReqManTool (up to 5 modules), Redmine (starter licence), sign-in and My work. Paid: Gerrit, Jenkins, JFrog, Risk & Safety and Documents.

How ALM OS fills it

  • Redmine stays the tracker: tasks are edited and assigned from ALM OS, and each person’s tasks come into My work.
  • Gerrit, which ALM OS runs inside its own image, takes over code review with review rules by SIL: independent reviewers, a Verified vote from CI, no unresolved comments. The repositories are pushed into it.
  • The Jenkins plugin reads jobs, builds with their stages and JUnit reports; the JFrog plugin reads build-info, artifacts with their SHA-256, Release Bundles and Xray security issues.
  • ReqManTool for requirements, Risk & Safety for the hazard log, FMEA and SRAC register, Documents for controlled documents.
  • Installed from one package, air-gapped if needed; people sign in through LDAP or Active Directory.

What they gain

  • A release baseline that holds the requirements, the Redmine tasks, the Gerrit changes with their votes, the Jenkins builds and test results, and every delivered binary by its SHA-256.
  • Hazards linked to their mitigations, the safety requirements and the tests that verify them.
  • Sign-off by an independent reviewer, verifier and approver, and an evidence report for the assessor.
  • Redmine tasks show their ALM OS links in a custom field.

Open this set-up in the configurator →

Requirements stay in DOORS or Polarion

How the tools connect

Already in use

  • ReqIF (DOORS, Polarion, Codebeamer)
  • Jira
  • GitLab
ALM OS core links · Needs review · impact · baselines · evidence report

Added with ALM OS

  • Test results · paid

Starting point

Systems engineering keeps the requirements in IBM DOORS, DOORS Next or Polarion. Software teams work in Jira and GitLab; tests run in CI.

What is missing

The requirements tool cannot see the issues, merge requests and test results, so the trace is a spreadsheet rebuilt for every release.

Licence

Free: the core, sign-in and My work. Paid: ReqIF, Jira, GitLab and Test results.

How ALM OS fills it

  • The ReqIF plugin reads the ReqIF exports (.reqif, .reqifz) the requirements tool already produces. Each export is a delivery, compared with the one before: what was created, changed or deleted.
  • Jira, GitLab and Test results connect the software side.
  • ALM OS writes nothing back to the requirements tool.

What they gain

  • DOORS or Polarion requirements traced to Jira stories, GitLab merge requests and test results, with coverage.
  • A new delivery that changes a requirement turns its links to Needs review.
  • A baseline names the exact export file by its SHA-256, so an earlier baseline can be taken again from the kept files.

Open this set-up in the configurator →

A small team on the free package

How the tools connect

Already in use

  • Redmine
ALM OS core links · Needs review · impact · baselines · evidence report

Added with ALM OS

  • ReqManTool · free
  • My work · free
  • ICS calendar · free
  • LDAP / Active Directory · free

Starting point

Up to ten people, Redmine for tasks and bugs, requirements in Word or a spreadsheet, and a company directory.

What is missing

No requirements tool, no trace, no baselines — and little budget.

Licence

Free, with no time limit, for up to 10 registered people. The Redmine plugin needs the free starter licence, requested once.

How ALM OS fills it

  • ReqManTool for requirements and test cases, up to 5 modules, imported from CSV or ReqIF.
  • Redmine with the free starter licence: tasks created, edited and assigned from ALM OS.
  • Sign-in through LDAP, Active Directory, Entra ID or any OpenID Connect provider; My work with each person’s calendar.

What they gain

  • Requirements linked to Redmine tasks and to test cases, with coverage, and Needs review when either side changes.
  • Requirements reviewed and approved with findings, votes and independence.
  • Baselines with sign-off and the evidence report.
  • Room to grow: a 25-user tier, then ReqManTool Pro for more modules and paid plugins one at a time.

Open this set-up in the configurator →

A safety team adds Risk & Safety

How the tools connect

Already in use

  • ReqManTool
  • Test results
ALM OS core links · Needs review · impact · baselines · evidence report

Added with ALM OS

  • Risk & Safety · paid
  • Work · paid

Starting point

A project already traces its requirements in ReqManTool and its test results from CI in ALM OS. The hazard log, the FMEA and the SRAC list are spreadsheets kept by the safety engineer.

What is missing

Hazards and their mitigations are not linked to the requirements and tests that carry them, so a change to a requirement never reaches the hazard log.

Licence

Paid: Risk & Safety (and Work, if used), on top of what the project already has.

How ALM OS fills it

  • Risk & Safety keeps the hazard log with an EN 50126 risk matrix (initial and residual risk), mitigations and safety requirements with their SIL, FMEA worksheets with RPN and criticality, fault trees (FTA), the SRAC register (EN 50129) and cybersecurity threats with SL-T and SL-A and a threat analysis and risk assessment (TARA, CLC/TS 50701).
  • Optionally, Work runs the project on its CENELEC railway template: lifecycle phases with gates, verification and validation independent by SIL, change control.

What they gain

  • Each hazard linked to its mitigations, the safety requirements and the tests that verify them; impact analysis reaches from a changed requirement to the hazards it concerns.
  • When the risk matrix changes, every hazard whose class would differ is marked for re-assessment.
  • The registers go into the release baseline and its evidence report next to the requirements and tests; every change is recorded as a commit.

Open this set-up in the configurator →

Specifications in Confluence

How the tools connect

Already in use

  • Confluence
  • Jira
ALM OS core links · Needs review · impact · baselines · evidence report

Added with ALM OS

  • ReqManTool · free

Starting point

Engineering writes plans, specifications and test reports as Confluence pages and attachments; the work is tracked in Jira.

What is missing

A Confluence page keeps changing after its review. The assessor needs exactly the version that was released, and how it relates to the requirements and tests.

Licence

Free: the core, ReqManTool (up to 5 modules), sign-in and My work. Paid: Confluence and Jira.

How ALM OS fills it

  • The Confluence plugin reads the pages, blog posts and attachments (PDF, DOCX…) of the chosen spaces, on Confluence Cloud or Data Center. It only reads: pages are still written in Confluence.
  • ReqManTool for the requirements; Jira for the work, with Atlassian sign-in on Jira Cloud.

What they gain

  • Baselines keep controlled copies: each page at its exact version with the SHA-256 of what Confluence stores, each attachment with the SHA-256 of its file. A kept version can be fetched again later and its hash checked.
  • Pages linked to the requirements they specify and the Jira issues that implement them; a new page version turns its links to Needs review.
  • Notification rules on new page versions in the project’s spaces.

Open this set-up in the configurator →

Planned, not built yet

These are on the roadmap. They are not in ALM OS today, and we give no dates.

  • Google Drive: a plugin for documents kept on Google Drive (planned).
  • Google Calendar sign-in for My work (planned). Today Google Calendar works through its secret iCal address.
  • Writing changes back into the tools ALM OS only reads today (planned).

ALM OS is built for tool qualification under EN 50128 / EN 50716 and ISO 26262-8, and each release comes with its qualification kit. It is not certified: each project qualifies the tool for its own use, and a pre-release (beta) is not for qualified use.

Tool qualification (T2) →

How licensing works →

Your set-up is different?

Pick the tools you have, area by area, and see how ALM OS would work with them — or tell us about your project.