MS Word – Import and Export
There are various ways requirements reach a project – for example, through MS Word documents. objectiF RPM makes it quick and easy to import requirements from MS Word. This video shows how it works:
Specification sheets are still especially common in client-contractor projects. Use objectiF RPM to generate specification sheets from your requirements (including dashboard elements, queries, diagrams, glossary) as MS Word documents following ISO/IEC/IEEE 29148:2011. Customizable standard templates are provided that can be easily adapted for your corporate identity, allowing you to create flawless, up-to-date documentation with MS Word at any time (or in PDF format).
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
The Requirements Interchange Format (ReqIF) is used to exchange requirements between various applications. It is mainly used in the automotive industry for standardized data exchange between OEMs and suppliers, especially for the import and export of data to and from DOORS. As an alternative to DOORS, objectiF RPM possesses an interface for ReqIF import and export which can manage complex data structures including picture files and OLE objects.
In this video, you’ll see how importing requirements from ReqIF works.
Exporting requirements from objectiF RPM into a Req-IF file is also supported.
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.
René Rönisch is glad to answer them and help you create a data migration strategy that fits your situation.