Jean Claude,

well, everyone should provide input for the testers!

It's more the thinking about who owns the requirements that are to be
tested.
Every role in your team provides/influences requirements:
- analysts (e.g. business rules, 'boundary' requirements, ..)
- designers (e.g. RDBMS mechanisms, Messaging requirements, ..)
- developers (e.g. coding conventions, implementation requirements, ..)

My suggestion would be that every role provides specific requirements.
Every (testable) requirement type has an attribute 'Test: yes/no'.

The testers then can filter the requirements and implement the 'requested'
tests. With some integration, empty test scenarios can be 'precreated', and
the tester also has access to further needed documentation (e.g. a
UC-scenario
can be used to navigate to the use case document).

With best regards,
Volker
TIPS & TRICKS:
Try 'Help:Extended Help' in any Rational Tool
********************************************************************
                          Volker Kopetzky
  Senior Systems Engineer/Expert       Phone: +49 / 89 - 62838 - 293
  Rational Software                    eFax:  +49 / 89 - 62838 - 593
  Keltenring 15                        Fax:   +49 / 89 - 62838 - 269
  D-82041 Oberhaching                   MailTo:[EMAIL PROTECTED]
  Germany               URL: http://www.rational-software.de/exp/vzk
********************************************************************
Rational...
-> Suite:                        
   http://www.rational.com/products/rs/index.jtmpl
-> Requisite Pro:            
   http://www.rational.com/products/reqpro/index.jtmpl
-> Unified Process:             
   http://www.rational.com/products/rup/index.jtmpl
-> Rose - unoffical website:                       
   http://www.rationalrose.com
-> Upgrades: 
   http://www.rational.com/sitewide/support/upgrades/ 
 

-----Ursprüngliche Nachricht-----
Von: Antonio Jean Claude [mailto:[EMAIL PROTECTED]]
Gesendet: Mittwoch, 14. Februar 2001 11:11
An: [EMAIL PROTECTED]
Betreff: (ROSE) Test scenarios



Hi all,

This is more a question of organisation than a Rose question.
Our project is divided into 4 groups:
- analysts
- designers
- developpers
- testers

The analysts are working on Use Case description and Conceptual Diagrams
(Class diagram representing Domain concepts). They describe use cases with a
flow or events.

Should they take care of the creation of the Test scenarios?
If not, who are the best candidates to create them?

Thanks,

Jean-Claude
************************************************************************
* 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
*
*************************************************************************
************************************************************************
* 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
*
*************************************************************************

Reply via email to