Luis-- The main advantage of associating Rose use cases to Req Pro requirements is that you establish a direct electronic link between requirements and design. When a programmer is working in Rose, he can, with a few clicks, directly access detailed requirements for the module on which he is working. Before we used Req Pro and Rose, the programmer would have to call the business analyst and ask WHICH requirement addressed whatever the programmer was working on. Then both people would page through 100+ pages of paper documentation to find the relevant requirement. Another big advantage is that it makes it easier for us to demonstrate direct traceability between requirements and design to the FDA, who audits our software engineering processes (we build software for medical uses.) Disadvantages: The work of establishing and maintaining the associations throughout the life cycle of the software. We haven't been using Rose/Req Pro long enough to know how difficult this will be. Donna Ellis Development Analyst Sunquest Information Systems, Inc. 4801 E. Broadway Blvd. Tucson, AZ 85711 [EMAIL PROTECTED] voice: 520-733-6356 fax: 520-733-6626
Hi all. I'd like to know the real advantages and disadvantages, on the day-by-day, of associating Rose use cases to RequisitePro requirements. Does it bring a new way for seeing uc or requirements? TIA, Luis ************************************************************************ * 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 * *************************************************************************
