Business Use Case Diagram Vs System Use Case Diagram

These diagrams provide multiple advantages.

Business use case diagram vs system use case diagram. Business use case diagrams are used to represent the functionality provided by an organization as a whole they answer the questions what does the business do and why are we building the system they are used extensively during business modeling activities to set the context for the system and to form a foundation for creating the use cases. Let s take a look at the example below. The key elements of the diagram are.

Use case diagram and activity diagram are behavioral uml diagrams that describe the dynamic nature of a system. Physical actions by actors are not modeled in the system use case diagram. A use case diagram at its simplest is a representation of a user s interaction with the system that shows the relationship between the user and the different use cases in which the user is involved.

This is the same business use case activity diagram as figure 2 in part one of this se ries but now with all the supporting system use cases superimposed. Then we want to provide more clarity on each of the use cases and we create a use case descriptions. System use cases a business use case is to do with using a business.

A use case diagram can identify the different types of users of a system and the different use cases and will often be accompanied by other types of diagrams as well. This recognises that businesses1 are created and organised in order to do things for people mainly customers but also other actors. Business use case vs.

A system use case is normally described at the system functionality level for example create voucher and specifies the function or the service that the system provides for the user so in short business use cases are more about what the users expect the system to do and system use cases are more about what the system actually does. A uml activity diagram showing the steps activities in the business use case buc and the transitions between steps a uml use case diagram for each supporting system use case suc an association named supports from each suc to each business activity transition that it supports. Existence of secondary actor is solution dependent and not mandatory to exist in all the solutions.

Database servers brand names technologies will not be modeled in the use case. The difference between use case diagram and activity diagram is that a use case diagram helps to model the system user interactions while activity diagram helps to model the work flow of the system. This is a business use case diagram example.