1. Modeling
By establishing an abstract method of objective things to characterize things and gain an understanding of the things themselves, at the same time, this understanding is conceptual and these logical concepts are organized, it constitutes an easy-to-understand expression of the internal structure and working principle of the observed object.
(1) how to build -- participant goal
Different abstract angles determine different modeling directions. When you try to model the real world, the first thing you need to determine is the abstract angle, that is, what is the purpose of this model. Once the abstract angle is determined, the rest of the things will become logical, rather than disorder.
Object-oriented users want you to break things into small pieces from the abstract perspective, and the problem becomes simple.
The first goal is not to figure out how the business is completed step by step, but to figure out how many participants are involved in the business? What are the goals of each participant? The goal of the participants is your abstract perspective. Compared with analyzing a complex business process, it is much easier to analyze the participants individually. In fact, this is the use case, which is one of the reasons why regular meetings become a business modeling method.
(2) What is a model?
It depends on scenario simulation from the abstract perspective. Once the abstract angle is determined, a goal is determined.
Find out who initiated what actions, what actions they acted on, and what consequences they would have. The purpose is to find out the things that contribute to the scenario's goals and how these things contribute to the scenario.
Scenario Simulation helps us find abstract objects, and the scenario itself is a specific result of interaction under certain conditions.
A goal determined from the abstract angle needs to be completed by a specific scenario generated under static things + specific conditions.
Specific scenarios (events) = static things (things) + specific conditions (Rules) + specific actions (driven by participants)
Person = business protagonist, business worker, and participant
Incidents = business and System Use Cases
Things = business entities and entities
2. Modeling Formula