objectiF RM 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 RM On-Premise

How to use objectiF RPM with your local Infrastructure.

Architecture of objectiF RM on premise

objectiF RM 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 EC2 configuration we recommend “m4.xlarge” with 2 CPUs and 8 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 RM

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 RM in a cloud
If needed, you can combine on-premise and cloud solution in a common virtual private network (VPN) for maximum flexibility.

Interfaces

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

MS Word

MS Excel

MS PowerPoint

Requirements management

ReqIF (Requirements Interchange Format)

Collaboration

Active Directory

Atlassian Jira

Azure DevOps

Software development

MS Visual Studio Code

Standard formats

XMI

XML

XPS

CSV

MS Word

MS Excel

PDF

Import

N
N
N
N
N
N
N
N
N
N

Export

N
N
N
N
N
N
N
N
N
N
N
N
N
N

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 RM, 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 RM 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.

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 RM, 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 Active Directory – Import

Import members of your organization and projects in objectiF RM quickly and easily via the interface to Microsoft Active Directory.

Jira – Synchronization

Are your requirements defined and structured in backlogs so that development can get started? But the development teams use Atlassian Jira? No problem. Synchronize requirements and issues easily via interface. Generate a Jira Cloud API token and then select the appropriate projects in Jira. Requirements and their references are exchanged quickly and easily between objectiF RM and Jira.

Azure DevOps – Synchronization

Many development teams use Azure DevOps. objectiF RM offers you an interface through which you can import work items into a project or export requirements. The import or export is carried out 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 RM’s task manager, for example by defining a fixed interval for a regular synchronization.

REST API – Import and Export

Use the REST API to exchange data between objectiF RM and other systems. Simply define your own interface-related JSON schema for import and export. You can use a form to define the amount of data to be transferred and thus optimize the data transfer.

Implement your own interfaces using extensions

You want to connect another application via interface? Then simply create your own extension using a request/response schema in JSON format for synchronizing data in objectiF RM. 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.