| Tip | ||||
|---|---|---|---|---|
| Excerpt | ||||
| ||||
This page presents an example of what can be built to integrate with Requirement Yogi. This is what you can do with the ReqIF extension and Requirement Yogi. |
This tool is an example of what can be built to integrate with Requirement Yogi. It is an open-source demonstration of how to import external documents into Requirement Yogi (sold separately).
Manage ReqIF documents in Requirement Yogi
Import ReqIF documents
ReqIF is an open XML standard. Integrate those documents with Requirement Yogi in Confluence.
Define mappings
Map each requirement type and property.
Extend
Open-source. Download, fork and support your own format!
| Widget Connector | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
This tool is a demonstration of how the Requirement Yogi API can be used:
Import ReqIF documents to Confluence,
Define mappings to create requirements,
Reference those requirements from Confluence pages.
It requires Requirement Yogi (commercial product).
Features:
Dependencies can be defined from requirements to ReqIF (one-way),
Baselines are supported,
Requirements can be mentioned from Jira.
Limitations:
Internal dependencies in the external document are ignored,
Only text formats are supported for data types,
This plugin implements 80% of the use cases, but this is not an entire implementation of the ReqIF specification.
Developers:
Developers can use this reference implementation to build their own product around Requirement Yogi.
The source is available on BitBucket: https://bitbucket.org/playsql/extensions-reqif
API documentation for Requirement Yogi: https://developer.requirementyogi.com
Support:
This tool is supported by Play SQL,
Known limitations are not supported (notably, internal dependencies),
https://requirementyogi.atlassian.net/servicedesk/customer/portals