Re: (ROSE) Business Modeling

[Richard Howlett]

Hi Anurag,   Picture the business as a black box that reacts to business events. The scope of the business analysis effort is the business itself, and the unit for decomposing the overall behavior of the business are scenarios - business use cases.   Once you have worked out the services the business offers customers and partners via your business use case model, you will need to peer inside this black box, describing how the business operates. Activity diagrams are great for this purpose.    In your activity model you will find certain business activities that could benefit from, or in fact may only exist through the application of information technology. These activities become names for system use cases. The scope of the analysis effort has now shifted from the business to an information system needed to support business activities.    As far as modeling the cell phone: during business and systems requirements analysis I would focus instead on modeling the roles of those who will be using the service. I would defer the device-related decisions to architectural analysis. Sounds like an interesting project. If you haven't yet, you should look into Microsoft .NET Alerts services.   Regards, -Richard ----- Original Message ----- From: Anurag Shah-Edventure Systems To: [EMAIL PROTECTED] ; [EMAIL PROTECTED] Sent: Thursday, March 28, 2002 6:19 AM Subject: (ROSE) Business Modeling Hi All,   I am in the process of  generating a Business Use Case Model for a project. The Project is mainly to develop a system which can enable users to be notified by WAP/SMS on their cell phone regarding their preferred stock prices, important Emails, news, weather etc., Now question is using which element do I show the "Cell Phone" in the diagram. AS an business actor or business worker or business entity or as an use case.? Also can we show Business entities in Business use case diagrams?   Thanks in advance Anurag