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