objectiF RPM offers a client-server architecture with a central database. Via the web and windows client you can access your data externally and internally. The connection to other systems for data exchange is done via export/import, REST API or via the supplied interfaces. Decide for yourself whether you want to use objectiF RM on-premise or in the cloud.

System Requirements

Hardware and Software Requirements

Hardware Requirements Server

CPU: Quad-Core or higher
At least 8 GB RAM
2 GB free hard drive space is recommended

Hardware Requirements Client

CPU: Dual-Core or higher
6 GB RAM recommended
1 GB free hard drive space is recommended

Software Requirements Server

MS Windows Server 2016 or higher

MS .NET Framework 4.8

Microsoft SQL Server 2016, 2017 or 2019

Software Requirements Client

MS Windows 10 or higher

MS .NET Framework 4.8

MS Word 2012 or higher is recommended

MS Visual Studio Tools for Office Runtime 4.0

objectiF RPM On-Premise

How to use objectiF RPM with your local Infrastructure

Architecture of objectiF RPM on premise

objectiF RPM in the Cloud

Various cloud solutions are possible.

Amazon Web Services
You need:

  • ein Amazon Web Services Account
  • an Elastic Compute Cloud (EC2) with virtual Windows Server and MS SQL Server
  • A license for objectiF RM

The Elastic Compute Cloud EC2 should include:

  • a MS Windows Server 2019 with manual installation of MS SQL Server Express.
  • or a MS Windows Server 2019 and a MS SQL Server Standard.

As a EC2 configuration we recommend at least 4 CPUs and 16 GB memory. MS SQL Server Express 2019 is limited to 2 GB RAM and 10 GB data volume, for larger requirements we recommend MS SQL Server Standard.

Amazon Web Services offers scaling of the Elastic Compute Cloud, i.e. you can adjust the configuration according to your needs.

Microsoft Azure
You need:

  • a Microsoft Azure account
  • a virtual Windows server with SQL Server
  • a license for objectiF RM

The virtual server should include

  • a MS Windows Server 2019 with manual installation of MS SQL Server 2019 Express.
  • or a MS Windows Server 2019 and a MS SQL Server 2019 Standard.

As configuration we recommend at least 4 CPUs and 16 GB memory. The MS SQL Server Express is limited in terms of RAM and data volume, for larger requirements we recommend the MS SQL Server Standard or higher.

Azure offers scaling of the virtual servers, i.e. you can adjust the configuration according to your needs.

Your cloud solution

You need:

  • Microsoft Windows operating system
  • a virtual Windows server with SQL Server
  • A license for objectiF RPM

As configuration we recommend at least 4 CPUs and 16 GB memory. The MS SQL Server Express is limited in terms of RAM and data volume, for larger requirements we recommend the MS SQL Server Standard or higher.

Whether it’s AWS, Microsoft Azure, or your cloud, here’s how to get connected.

Architecture of objectiF RPM in a cloud
If needed, you can combine on-premise and cloud solution in a common virtual private network (VPN) for maximum flexibility.


This overview shows you which programs objectif RPM can integrate and exchange data with via import or export. In addition, objectif RPM has a REST API interface that enables communication with programs that are not listed here.

MS Word

MS Excel

MS PowerPoint

MS Visio

Requirements management

ReqIF (Requirements Interchange Format)

Project planning

MS Project


Active Directory

Atlassian Jira

Azure DevOps

MS Outlook

Software development

MS Visual Studio Code

Standard formats





MS Word

MS Excel






Here You Can Find Videos with Technical Introductions to the Interfaces

MS Excel – Import and Export

Unfortunately still not a rarity: Requirements Engineering with MS Excel. However, MS Excel is not so well suited for tracing requirements and their relationships, for rights and role concepts neither for team collaboration.
Why not switch to objectiF RPM, which offers you all this plus modeling and standardization? Simply import your requirements from MS Excel and export all artifacts and queries to MS Excel when needed.
In the video you can see how importing requirements from MS Excel works.

MS Word – Import and Export

Good requirements engineering needs more than MS Word. Traceability and revision conrol are indispensable in regulated industries and cannot be properly achieved with it.
Import requirements (including dashboard elements, queries, diagrams, glossary) from MS Word into objectiF RPM quickly and easily. Generate up-to-date requirements specifications according to ISO/IEC/IEEE 29148:2011 or vision documents at any time with an agile approach. Configurable templates, which you can easily adapt to your corporate design, help you to perfectly document your results.
In the video you can see how the import of requirements from MS Word works.

MS Project – Import

objectiF RPM facilitates teamwork between the members of one or several projects based on agile or hybrid planning methodologies. When you plan a project with objectiF RPM you can get real-time information about the current status of requirements, tests, bugs, components and more at any time, as well as costs, resources and KPIs. But what can you do if a project or subproject has already been planned with MS Project? In that case, you can avoid unnecessary time and effort by importing the activities with their assigned resources to objectiF RPM. It only takes a few seconds, as shown in this video.

ReqIF – Import and Export

Do you work in the automotive sector and exchange requirements in the Requirements Interchange Format (ReqIF)? This standardized data exchange between OEM and supplier is often used for the import and export of data from and to DOORS.
Get to know objectiF RPM, an inexpensive alternative which also has a ReqIF import/export interface and can process complex data structures, including image files and OLE objects.
This video shows what data import from ReqIF looks like.

MS Visio – Generate Precedence Diagrams

Gantt charts are a key instrument for project planning in objectiF RPM. If you or your stakeholders also like working with precedence diagrams, objectiF RPM also has you covered. This video shows how quickly and easily you can get from a Gantt Chart in objectiF RPM to a precedence diagram which can be further edited with MS Visio according to your needs.

MS Active Directory – Import

For planning your projects you need information about the employees in your organization – especially when it comes to costs and resources. You can add employees to your projects using the organization-wide staff management system. But what if you also need to add employees to an organization? The quickest way is by using objectiF RPM’s Active Directory interface. This video shows you how:

Jira – Synchronization

Atlassian’s Jira is widely used among agile development teams. If you’re working with teams that need to work with Jira, objectiF RPM has you covered. To synchronize between requirements in objectiF RPM and Jira Issues, simply use the included interface.
To configure, generate a Jira Cloud API token and choose the corresponding project in Jira. From objectiF RPM, requirements and their references (for example, dependent user stores in other team backlogs) can be quickly exchanged with Jira. They don’t need to be newly defined. You can even automate synchronization using objectiF RPM’s task manager with a fixed time interval.

Azure DevOps – Synchronization

Many teams use Azure DevOps to collaborate in software development projects. objectiF RPM offers you an interface to import work items into a project or export requirements. The import or export is performed via a configuration.
To do this, simply generate an Azure DevOps token, select an Azure DevOps project and then determine the assignment of stereotypes and properties during import and export via mapping.
You can perform the synchronization manually or automate it via objectiF RPM’s task manager, for example by defining a fixed interval for a regular synchronization.

REST API – Import and Export

A REST API is provided for integrating objectiF RPM with other applications and for automatically importing and exporting data to and from objectiF RPM. This can be used for easy data transfer. To do this, instead of defining a fixed schema, you can define your own interface-related JSON schema for data exchange in objectiF RPM. This reduces the complexity of the interface and the amount of data to be transferred.

Implement your own interfaces using extensions

If you need an interface to another application, objectiF RPM makes it possible to create your own extensions that can be used to implement custom interfaces. As with the provided REST API, you can create your own JSON schema for extensions for synchronizing data with objectiF RPM. Extension functions can be executed manually, time-based or state-based, allowing you, for example, to transfer a requirement whenever a particular state change takes place.

Do You Have Any Questions?

René Rönisch microTOOL GmbH

René Rönisch will answer your questions about our tools and help you develop a strategy for migrating your data.