1
General Board / RaQuest: Initial questions from a 1st-time user
« on: April 04, 2005, 01:08:29 pm »
Hi,
I've downloaded the trial version of v2 of RaQuest and successfully integrated it with my purchased copy of Enterprise Architect, and spent a couple hours (so far) playing with it.
I thought I'd document some questions/issues here in order to generate discussion.
First off, over-all, I like what I've seen so far, but:
- the Help file could use some (English-as-a-first-language) polishing in some places, but it could also use a chapter related to describing the workflow and defining the dividing line between the 2 tools. I do realize that documentation costs can be a significant percentage of development costs and that a young product may not be fully documented.
- As a mid-sized company with large-company software product documentation requirements, I could really use some recommendations on how to organize my requirements. At this point, I guess it'll have to be a matter of experimentation. To start I'm planning on creating packages which mimic our Product Management structure.
- I was able to figure out how to create new Requirements Types (Business & Feature) and can use them. However, when I did a 'Generate UseCases', it generated Use Cases for EVERY requirement that I entered. I would like a discuss/recommendation on what should actually be happening here. My thought is that it would be nice to be able to specify a Requirement Type (eg. Feature) as a filter for generating Use Cases.
- Having created a set of requirements in one (*.EAP) database, I wanted to move (or copy) them to another (learning) database. How do I do that ?
- Which brings me to a follow-up question: How can I share requirements between projects / products ? eg. "In the event of ...x..., a record will be written to a centralized logging facility." would be used in MANY places.
- Suggestion to user interface: when looking at the main screen which shows the tree hierarchy of requirements on the left and 'All Requirements' on the right, it would be nice if selecting a row on one side would also automatically select the same row on the other side (and visa versa).
- Also, it would be nice if (in the list of All Requirements), the Type, Priority, Risk, Difficulty, and Stability columns were all modifyable like the Status column is.
As I'm preparing for a demo to my team on 12-Apr-2005, I'm sure I'll have other questions ...
Thanks,
Steven.
I've downloaded the trial version of v2 of RaQuest and successfully integrated it with my purchased copy of Enterprise Architect, and spent a couple hours (so far) playing with it.
I thought I'd document some questions/issues here in order to generate discussion.
First off, over-all, I like what I've seen so far, but:
- the Help file could use some (English-as-a-first-language) polishing in some places, but it could also use a chapter related to describing the workflow and defining the dividing line between the 2 tools. I do realize that documentation costs can be a significant percentage of development costs and that a young product may not be fully documented.
- As a mid-sized company with large-company software product documentation requirements, I could really use some recommendations on how to organize my requirements. At this point, I guess it'll have to be a matter of experimentation. To start I'm planning on creating packages which mimic our Product Management structure.
- I was able to figure out how to create new Requirements Types (Business & Feature) and can use them. However, when I did a 'Generate UseCases', it generated Use Cases for EVERY requirement that I entered. I would like a discuss/recommendation on what should actually be happening here. My thought is that it would be nice to be able to specify a Requirement Type (eg. Feature) as a filter for generating Use Cases.
- Having created a set of requirements in one (*.EAP) database, I wanted to move (or copy) them to another (learning) database. How do I do that ?
- Which brings me to a follow-up question: How can I share requirements between projects / products ? eg. "In the event of ...x..., a record will be written to a centralized logging facility." would be used in MANY places.
- Suggestion to user interface: when looking at the main screen which shows the tree hierarchy of requirements on the left and 'All Requirements' on the right, it would be nice if selecting a row on one side would also automatically select the same row on the other side (and visa versa).
- Also, it would be nice if (in the list of All Requirements), the Type, Priority, Risk, Difficulty, and Stability columns were all modifyable like the Status column is.
As I'm preparing for a demo to my team on 12-Apr-2005, I'm sure I'll have other questions ...

Thanks,
Steven.