Business Use Case And System Use Case
Typically any software development begins with a business case which is to say what is the business reason behind the development or why is the software required.
Business use case and system use case. It is written in low level. However one area that causes problems is distinguish. A business use case has a name.
System use case represents the use cases which are done by the system not manually. The good news is that business rules and use cases are fundamentally different considerations. Both use case types can be represented by diagrams or text.
A business use case instance is a sequence of actions performed in a business that produces a result of observable value to an individual actor of the business. A use case specifies the flow of events in the system. It is not necessarily done by the system.
This involves use case for solutions developed on computer systems. A business use case defines a set of business use case instances. When a use case is depicted as using functionality of another functionality of another use case this relationship between the use cases is named as an include or uses relationship.
14 may 2008 abstract use cases are now all but universal as the basic concept for specifying requirements of commercial information systems. System use casessupportbusiness use cases meaning that the system use case provides some automated means of doing part or all of the business use case. Use cases are primarily about actor interactions.
Business use case represents the use cases which are done manually. So the booking is a system use case and the user is a system user. The second way is to pull them out of the use case altogether.