Requirements

Hi,

I’ve been trying SDE these days (while waiting for a response to my previus bug-post - http://forums.visual-paradigm.com/posts/list/1317.html :wink: ) and I’m not been able to find an important feature.
It’s the requirement management, and it’s relations with Use-Case diagrams, classes, etc…

I’ve seen the Text Analysis, but this is not what I’m looking for. What I’d like to see is somethink like a “requirements tree” (high level and low level requirements), with full documentation, and the posibility to create relations with UseCases and classes. So if a requirement changes you can see what is affected by this change.

Does this already exists in SDE? If not implemented this could be a nice new feature, isn’t it? 8)

As an alternative, is there a way to make the same links with the Team Foundation Server Work items? This is not exactly the same, but could be enought in most cases. Again, could be a nice feature. :smiley:

Thank you in advance for any information related with this.

Hi Luis,

I regret that we do not support requirements tree at this moment. But what you said sound meaningful. Could you provide me with more information on it? Where could I know more about requirements tree? We will consider to support it if we find it useful. I appreciate for your great help.

Best Regards,
Jick

Hi Jick,

What I mean is something like the Rational RequisitePro requirements tree. (http://www-306.ibm.com/software/awdtools/reqpro/). I’m sorry, but I don’t have it installed to take some screenshots.

I’m not an UML expert (althought I use it very much) so I can’t give you an “erudite” explanation about it. Basically what I was thinking about was:
· Requirements: With an Automatic code (“R01”, “R01.01”, “R02”, etc…), a short name and a long description or word attachments. A requirement can have child requirements, created while advancing during the analisys cicle. Requirements could have too schedules, completion status (0%-100%), etc…
· Use-Case, Classes, Diagrams, etc… can be “linked” to any requirement. So, if a requirement must be changed you can know the impact (classes changes).
· Of course, a lot of reports with current project status, changes impact, etc…

I think the most difficult part is to do it more than a simple “ToDo list”. But probably a good UML documentation could be much more usefull that my explanation :slight_smile: .

I’d really like to see something like this well done and simple.

Thank you for your interest.

Hi Luis,

Thank you for the notes. I will forward your opinion to our development team for further feasibility studies.

Best Regards,
Jick

Hi Luis,

I would like to notify you about the release of VP Suite version 2.3. The new version supports Requirement Diagrams. I think you will find it useful. For more information, please read:
http://resource.visual-paradigm.com/vpsuite2.3/requirement_diagram.html

Best Regards,
Jick