Web Application. Try TEAM plan. This is a preview version for evaluation of the latest features. What are the differences between web and native applications? Where is my project data stored? How can I update ReqView? Branches Tags. Could not load branches. Could not load tags. Latest commit. Git stats commits. Failed to load latest commit information. View code. Desktop Application v1. Follow 'Create and Install new database' and 'Import database contents' sections steps in [Installation manual] Make sure to update connection.
Users support If you found any problem review here if your issue is not published yet or create request to fix the issue. For defects create new request to fix with the following information: detailed steps to reproduce; E.
Generate expected result and actual results. They should be put right after steps to reproduce; screenshots; system logs which can be found in OSRMT installation folder. For feature requests provide with the following information: detailed description of the feature; mockups if needed or examples screenshots. There is a project infrastructure including a git repository, bug-tracker, news and forums.
It is currently used in commercial and open source projects all over the world. Because there were no bug reports or user requests for some time, there were no new releases for some month now. Included in the rmtoo package is a set of requirements that describe the rmtoo functionality itself. This provides a good overview of rmtoo and is a good starting point for working with rmtoo. This is a good starting point to get an impression of how rmtoo can be used in your projects.
The first presentation gives an rough overview about all the features of rmtoo and reasons why and when rmtoo should be used in a project. The second presentation goes in much more detail.
This explains the input and configuration files which are used. It gives also an overview over the different output artifacts. Because the document was created with the help of rmtoo this can be seen as an example of an output document, including backlog, list of requirements that must be further elaborated upon and all requirement descriptions. The requirements document for rmtoo describes every feature in detail.
The document also includes a roadmap, which describes the planned but not yet implemented features. The requirements dependency graph is one rmtoo output artifact. There is a requirements dependency graph available which describes the current state of rmtoo itself. The topic based requirements dependency graph is similar to the standard requirements dependency graph, except that the requirements for one topic are clustered.
0コメント