Author: vpadmin

This is a sequence diagram example for order management.

The Company has decided to undertake an effort to build a new application for sales and order management. To explore the needs of the organization, and also to align the way business is done throughout the organization, the first step is to build a set of business models. The departments of The Company that will not actively use the new order application are considered external to the model, and are represented with business actors.

Order Process: This process describes how The Company takes appropriate actions to deliver a solution to a Customer as defined by a set of customer requirements. The process starts when there is a business decision to proceed with an agreed solution. This may often be in the form of The Company receiving a purchase order from a Customer. It ends when the Customer is satisfied with the instalment and commission of the solution and payment is received. The objective is to in a profitable way satisfy customer requirements.

Proposal Process: This is the process of generating a proposal(s) in response to customer requirements. The process is triggered by an inquiry from a Customer and ends when the Customer accepts (or rejects) any of the quote(s) in the proposal. The objective is to reach agreement on a quote that is acceptable both to the Customer and to The Company.

Quote Process: The Quote Process is an abstract business use case that is included in both the Proposal Process and the Order Process. The process begins when there are customer requirements that need a quote produced for it. The objective of the Quote Process is to produce a solution meeting the customer requirements, and to provide it along with a price.

This is a business use case diagram example. 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.

Note That:

Business Use Case diagrams are drawn from the organizational perspective. They do not differentiate between manual and automated processes. (Use Case diagrams, which will be discussed next, focus on the automated processes.) Business Use Case diagrams show the interactions between business use cases and business actors. Business use cases represent the processes that a business performs, and business actors represent roles with which the business interacts, such as customers or vendors. In other words, business actors represent anyone

An example of a simplified Business Use Case diagram for a financial institution is shown in Figure.

This use case diagram example illustrates the login account use case is shared among all the base use cases with two extension points to handle invalid process and abort request.

This is a use case diagram example that shows the use of extension in a use case diagram.

Browse catalog with security user cases in electronic commerce product line.

This is a use case diagram example of Structuring Use Cases with Stereotype

This is a use case diagram example of Structuring Use Cases with Stereotype.

This is a use case diagram example of Using Extension Point

This is a use case diagram example of Expressing Multiple Projects Using System Boundaries.

This is a use case diagram example of Online Examination System.

This is a use case diagram example of Passenger Service.