Redmine

Hm..., Redmine is a project management web application that is not tied to the software development only. It could be used, par example, to distribute tasks to people in an administration dept, to workers in a workshop e tc. So, IMHO, if such functionality is needed it should be implemented as a plugin.

+1. I think this is very important.

Redmine is used by many software development - hence this is really a must feature. Of course, there would be teams that might not do design process or might not be related to sw dev. However, in this case this module (Like news, documents etc.) can come as a selectable under project modules. So it won't bother those who don't need.

Critical features this modules should be able to provide:

1. Should allows for requirement listings. Each requirement point can be listed and editable.
2. Requirements Like unique issue #issueid it should be unique and it can be referrable in any issues, notes, wikis.
3. Provide class and other UML diagrams - either they can be drawn on the page or can be uploaded.
4. Classes can be referenced under categories.
5. Issues can be linked with Class/Design items - and correpondingly also with requirements.
6. So for example. on a design page - I can click on A Requirement#2014 - and list all issues (along with their versions) that affects the given requirements.
7. Similarly under a class diagram - one can list down all corresponding issues.
8. Association can be done by a widget from issue page as well.
9. Requirements and design can be amended (as child requirements) or can be revised.
10. Requirements and Design assets can have notes that allow people to list why changes are made.
11. Detailed, documentation - docs can be attached under the design and requirements assets.
12. We can have state flow - where we can show how many requirements are completely fulfilled and what is pending based on whether the corresponding issues %complete.
13. Also, where the requirement is complete, we can identify post which version, the given requirement version is complete.
14. The same can be applied for design assets - we can identified how many design elements are fully implemented or pending.
15. Requirements and designs can have approval workflow. Hence, when and only when requirement and design is approved - the issues beneath them automatically moves to one more stage.

Essentially, this will allow complete requirement management and design process to be tracked