OpenReq Live is the primary tool being produced by OpenReq. This platform is a culmination of the microservices produced by this project, custom built for the end-user experience. If you are interested in jumping right into the tool to get an understanding of what the OpenReq project can do for your requirements process, then this is the way to do it!
The OpenReq Plugins is one of the three major technical outputs of the OpenReq project. The purpose of this output is to provide specific use-cases to common requirements-related contexts. The contexts are focused on tools/environments such as Eclipse, Jire, GitHub Issues, etc. Listed below are all of the OpenReq Add-Ons, with more in development.
The Eclipse Plug-in offers the following features: A view which shows bug reports and feature requests (requirements) from bugs.eclipse.org personalized for the current user, a view which show the most discussed bugs in the last 30 days from bugs.eclipse.org, and a Tip of the day extension with personalized tips for a better usage of the Eclipse IDE.
The OpenReq Issue Link Map visualizes existing links between issues in Jira. In the future the add-on will have the functionality to suggest dependencies which should be added. This helps project managers & owners to find duplicates, dependencies and other relations between issues supporting them in the release planning process.
(In Progress! Links to come)
Alter Way is looking to improve the customer support process through the inclusion and adaptation of OpenReq technologies into the Redmine Issue Tracker. In Alter Way, the support team is composed of technical engineers who provide both issues classification and resolution. Automating those processes is a top priority.
OpenReq researchers and industrial partners are working together to transform research outcomes into useable functionality. This functionality is open source and accessible at GitHub. Each of the components is built as a stand-alone component that can be deployed as a microservice. The primary common technology used is Docker. Take a moment to explore the microservices available below using the directory of swagger files below, or, dive right into the code on our GitHub page.