Hello all! Anyone, experience or ideas about the following case.
We are modeling a new release of a product family. Previously the functionality described in the use cases was designed and implemented as such. With this new release a high degree of configurability has come into the picture so that business designers can use a specific tool to create and configure the business processes using what we call process components. These can be added, removed or changed. Some of them are mandatory, some optional. In some cases the order of steps in the flow can be changed. The software should be able to function and these processes should go the way the system has been configured. So the question is, with systems that almost everything can be configurable, what would be the ideal approach to describe the use cases? Here are some ideas: - Describe with use cases how the configuration is done (well, this is obvious) - Describe with use cases how the functionality will be after configuration has been done (end user functionality)? The difficulty is that the possiblities are numerous because the processes are designed and configured, not implemented as a part of the product. - We thought of identifying examples of most likely end user functionality and model these as use cases? But these would be only configuration examples. - Processes are product specific and also products are created from product components and highly configurable as the processes. How to map these with the processes and also identify simililarities between processes of different products. We have modeled the product structure and process structure so that they are very modular. Any thoughts? This message is for the designated recipient only and may contain privileged, proprietary, or otherwise private information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the email by you is prohibited. ************************************************************************ * Rose Forum is a public venue for ideas and discussions. * For technical support, visit http://www.rational.com/support * Only plain-text messages are supported. * HTML or Rich-Text messages may be rejected. * * Post or Reply to: [EMAIL PROTECTED] * Subscription Requests: [EMAIL PROTECTED] * Archive of messages: * http://www.rational.com/support/usergroups/rose/rose_forum.jsp * Other Requests: [EMAIL PROTECTED] * * To unsubscribe from the list, please send email * To: [EMAIL PROTECTED] * Subject: <BLANK> * Body: unsubscribe rose_forum *************************************************************************
