OSRMT

Overview

OSRMT is an open-source tool for defining and managing software requirements, with workflows that connect requirements to design, implementation and test cases. It suits teams that want to manage traceability across projects using a desktop or self-hosted web deployment. Its main appeal is a free, configurable workflow; the trade-off is that deployment calls for compatible runtime and database choices.

Key features

OSRMT covers the path from features and use cases through design, implementation and testing, while tracing the links between those work items. That makes it a fit for teams that need to follow how requirements move through a project, rather than keep requirements in isolation.

Teams can organize work by phase, configure the tool and manage multiple projects simultaneously. The desktop option supports a single user; a centralized-server web deployment supports multiple users through desktop or web clients. The latter offers a shared working environment, but requires a JBoss deployment.

Pricing

The OSRMT plan costs nothing and can be used or distributed at no cost. There is no free-trial distinction to weigh: OSRMT is free software, not a time-limited trial. The plan requires hardware to run it, so free licensing does not remove the practical costs of hosting or maintaining a deployment.

Platforms

OSRMT supports Linux, macOS and Windows, and can be deployed on-premises. Desktop installation requires JRE 1.8 or later. The web application runs on JBoss and is accessible locally on port 8080, making it a more involved choice than a standalone desktop install.

For external databases, the README names Oracle, MySQL, MS SQL and PostgreSQL, while noting no additional database setup is needed for initial use. The project identifies GNU GPL-2.0 as its license. Support paths include issue reports, requests, an FAQ, online source and documentation, and a community email address. The project makes no security certification or compliance claims.

Who it's for

OSRMT is best suited to software teams that need requirements traceability across phases and projects, can manage a desktop runtime or JBoss server, and value a no-cost open-source tool. It is less suitable for teams that want to avoid deployment work or need stated security or compliance credentials.

Pros and cons

• Pro: Requirements, design, implementation and test cases can be connected, helping teams follow requirement flow through development.
• Pro: Single-user desktop and multiuser web deployment options accommodate different working arrangements.
• Pro: The free plan permits use and distribution at no cost, and the project names four external database options.
• Con: Desktop use requires JRE 1.8 or later, while web deployment requires JBoss; teams must be prepared to handle those dependencies.
• Con: The project states no security certifications or compliance claims, which may rule it out where those assurances are required.

Alternatives

For a broader comparison, see Requirements Management Software.

• MATLAB Grader is another free option, but requires a MATLAB license current under maintenance; LMS integration requires a qualifying academic license.
• ReqView may suit users who want a free plan with a defined cap of one document, 150 objects per document and one custom attribute, or a paid per-user plan at €440 a year.
• Doorstop is another open-source, free choice for teams comfortable with its Python and version-control-system requirements.
• Innoslate offers a free plan for educators and students who sign up with a .edu account; its Enterprise plan uses custom pricing.
• RequirementONE has a free Try plan limited to one user and three sources from a shortlist, with predefined topic filters and a personalised newsletter.
• NETVIBES is an alternative.
• QSC QS1 is an alternative.
• Siemens Polarion REQUIREMENTS is an alternative with custom pricing.

Verdict

Choose OSRMT if your team needs cross-phase requirements traceability and can support its desktop or JBoss deployment: the no-cost license and multi-project workflow are compelling for that use. Look elsewhere if setup dependencies are a poor fit or your procurement requires security and compliance credentials.