Hi,
In our project Our process owner has defined some guide lines for modeling System use cases. He says "we have to show only those sysetm use cases which can bu automated by the system". But Iam not convinced with that even the team. My queries are 1 .Is this correct guide line? 2.Are there any thumb rules or guide lines to identify the System use cases.? 3.For the enterprise applications do system use cases give any value addition? 4.Is it a must that we have to go for Business use cases and system use cases even though we know 90% of them will be the same. 5.An example or case study for identifying system use cases from the Business use cases. Lots of hopes on u r eply and please reslove our dead lock. Cheers Anil Emmadi System Analyst & Designer Ulysses Simulation Requirements Analysis and Design (WP499) Mail id :[EMAIL PROTECTED] Location : Hinckley Contact no : 01455 - 232800 Internal : 33177
The Information contained and transmitted by this E-MAIL is proprietary to Wipro and/or its Customer and is intended for use only by the individual or entity to which it is addressed, and may contain information that is privileged, confidential or exempt from disclosure under applicable law. If this is a forwarded message, the content of this E-MAIL may not have been sent with the authority of the Company. If you are not the intended recipient, an agent of the intended recipient or a person responsible for delivering the information to the named recipient, you are notified that any use, distribution, transmission, printing, copying or dissemination of this information in any way or in any manner is strictly prohibited. If you have received this communication in error, please delete this mail & notify us immediately at [EMAIL PROTECTED]
