Yves,
In my humble opinion, you are doing the right thing.
We have FeaturePackages-essentially product release ids- traced to FEATures
which are then traced to PRoduct requirements and/or to Use-Cases.
For us, the PRoduct requirements include both actual product level
requirements (the product case shall be no wider than xx) and also
Supplementart requirements (a log file shall be generated for ...).
Our PRoduct requirements and Use-Cases are then traced to Test requirements.
We can find out what Features have been allocated to a particular product
release, which of those features have actually been implemented, and whether or
not the feature, use-case, or product requirement has been tested / verified.
In point of fact, the requirements structure you use is up to you and depends on
what works best for your business and technical environment.
Ask yourself these questions:
1) Does my structure let me generate useful reports or traceability matrices?
2) Can the structure be maintained or will it be ignored after a while because
its too complex?
3) Could I explain it to the head of the Company in 15 minutes so he'd
understand it?
Regards,
Mark Scott
Marconi
"Yves Gagnon" <[EMAIL PROTECTED]> on 03/30/2001 10:40:24 AM
To: "Rose Forum" <[EMAIL PROTECTED]>, "Forum RUP"
<[EMAIL PROTECTED]>, "Forum RequisitePro" <[EMAIL PROTECTED]>
cc: (bcc: Mark Scott/MAIN/MC1)
Subject: (ReqPro) How to start with requirements ?
I have some questions about the way to define requirements for our project.
It's the first time we use the RUP approach with the Rational Analyst
Studio.
We start with an existing software that we want to redesign completely. For
that reason, we don't make the Business model process since we have all the
functionalities identifies. We started to create the Vision document, and in
the section 'Product Features' i identify all the existing features (High
level description).
My first thought was to create for each a requirements of type FEAT in the
requisite pro. In the same time i created an supplementary specification
document i used to define other requirements like 'The system must have a
trace log for each action'. And i used the matrix view to trace the first
type requirements (FEAT) to the second one (SUPL).
MY QUESTION: We want to use the use case development approach. Normalement,
i need to create all use cases for the system in Requisite Pro that mean i
will have tree type of requierements (FEAT, SUPL, UCS) and probably the need
to trace the UCS with the FEAT. Is it the way to do ??? If i dont use the
FEAT, what i must say inside the vision document in the 'Product Feature'
???
Thank you
Yves Gagnon
************************************************************************
* Req_Forum is a public venue for ideas and discussions.
* For technical support, visit http://www.rational.com/support
*
* Archive of messages:
http://www.rational.com/support/usergroups/reqpro/req_forum.jsp
*
* To unsubscribe from the list, please send email
* To: [EMAIL PROTECTED]
* Subject:<BLANK>
* Body: unsubscribe req_forum
or
http://www.rational.com/support/usergroups/index.jsp
*
*************************************************************************
************************************************************************
* Rose Forum is a public venue for ideas and discussions.
* For technical support, visit http://www.rational.com/support
*
* Admin.Subscription Requests: [EMAIL PROTECTED]
* Archive of messages:
http://www.rational.com/products/rose/usergroups/rose_forum.jtmpl
* Other Requests: [EMAIL PROTECTED]
*
* To unsubscribe from the list, please send email
*
* To: [EMAIL PROTECTED]
* Subject:<BLANK>
* Body: unsubscribe rose_forum
*
*************************************************************************
