Business use case diagrams are used to represent the functionality provided by the organization as a whole. They answer the question "What does a business do?" and "Why are we building systems?" They are used extensively during business modeling activities to set the system context and form the basis for creating use case diagrams.


The Business Use Case diagram is taken from an organizational perspective. They do not differentiate between manual and automated processes. The Business Use Case diagram shows the interactions between business use cases and business people. Business use cases represent the processes that a business performs, and business people represent roles that a business interacts with, such as customers or vendors. In other words, business actors represent anyone


Use case diagram is a graphical representation of possible user interactions with the system. Use case diagrams show the different use cases and types of users a system has and will often be accompanied by other types of diagrams as well. Use cases are represented by circles or ellipses. The actors are often presented as stick figures.


While the use cases themselves may dig up a lot of detail about each possibility, use case diagrams can help provide a higher-level view of the system. It has been said before that "A use case diagram is a blueprint for your system".


Due to its simplicity, use case diagrams can be a good communication tool for stakeholders. The pictures try to imitate the real world and provide views for stakeholders to understand how the system will be designed. Siau and Lee conducted research to determine whether there are valid situations for use case diagrams at all or when they are not needed. What they found was that use case diagrams conveyed the intent of the system in a more simplified manner to stakeholders and that they were "interpreted more fully than class diagrams".


Originally developed by Ivar Jacobson while still at Erickson, the Use Case Diagram is a visual model that depicts the main system functions accessed by those outside the system and the actors who interact with those functions. It is one of the most widely used UML models and most business analysts should be familiar enough with it to at least use it casually.


Use Case Diagrams are often among the earliest models or diagrams created during enterprise analysis or requirements elicitation work. This initial use case diagram is then elaborated, supplemented, and expanded through (descriptive) use cases (non-diagram use cases), additional models and diagrams (such as UML Activity, Sequence, and Class Diagrams), or others that are more detailed. requirements artifacts (detailed functional and non-functional requirements) as more information is learned and as more detailed requirements are defined.


The above material was delivered by a presenter from Indonesia in an international visiting lecturer held by STEKOM University in collaboration with Universities from Ukraine. The title of the presentation is "Engineering in the Software Development Model". The name of the presenter is Migunani Hudayatullah, S.Kom., M.Kom. Mr. Migunanani is an active lecturer and head of the Information Systems study program at STEKOM University.


This international webinar activity is part of the implementation of STEKOM University's commitment to increase various international activities. This was done in order to realize the vision to become an international-class university. Various international activities carried out by STEKOM University continue from year to year. There are international activities that are sustainable and there are also some international activities that are not sustainable. All types of international activities are accommodated and regulated by the International department of STEKOM University.