Artifact: Business Event
|
A Business Event represents a significant occurrence in the activities of the business that requires immediate action. |
|---|---|
| Other Relationships: |
Part Of Business Analysis Model
|
| Role: | Business Designer |
| Optionality/Occurrence: | Can be excluded. Business Events are unnecessary when Business Use Cases are not being modeled. |
| Templates and Reports: |
|
| Examples: | |
| UML Representation: | Signal, stereotyped as <<business event>>. |
| More Information: |
| Input to Activities: | Output from Activities: |
Purpose
Business Events represent the important things that happen in business and as such help manage complexity. Business Events are triggered and received by Business Actors, Business Workers, and Business Entities, while interacting to realize Business Use Cases. Business Events are used to trigger Business Use Cases, to signal changes of state of the business, and to pass information between Business Use Cases.
Stakeholders and business-process analysts use Business Events to better understand and describe the activities of the business. Business designers are responsible for identifying and detailing Business Events. Business Events are also used by systems analysts to help identify software system actors and use cases, and by software architects to help make software systems more flexible and maintainable.
Properties
|
Property Name |
Brief Description |
UML Representation |
|---|---|---|
| Name | The name of the Business Event. | The attribute "Name" on model element. |
| Brief Description | A brief description of the Business Event. | Tagged value, of type "short text". |
| Event Type | Whether it is a Signal Event, a Call Event, a Time Event, or a Change Event. | enum |
| Relationships | The relationships, such as generalizations, associations, and aggregations, in which the Business Event participates. | Owned by an enclosing package, via the aggregation "owns". |
| Operations | The operations defined by the Business Event. | operation |
| Attributes | The attributes defined by the Business Event. Used to describe information relevant to the occurrence of the Business Event. | attribute |
Timing
Business Events are identified during the Inception phase, as part of finding
business actors and use cases and describing Business Use-Case Realizations. During
the Elaboration phase, Business Events are detailed, and some may be identified.
Responsibility
A business-process analyst identifies candidate events while finding business actors and use cases but is not responsible for a Business Event in itself. A business designer is responsible for a specific Business Event, ensuring that it is consistent and complete.
Tailoring
Attributes are often useful to explicitly define what information is relevant. Operations can be used but are not really useful during business modeling, and therefore are not often employed. Business Events are usually represented in models of software systems. These software system representations of Business Events usually do have operations.
|
This content developed or partially developed by  Empulsys BV.
|
