How to get familiar with business

Here I would like to talk about a new business system that has not been in contact with the approach, of course, when it comes to the need to have some other business systems in the IT industry experience, including business and technical accumulation of two aspects, then in this case, how to quickly cut into a new business system, There is a need to pay attention to the relevant ways and means of problems.

Coarse-grained global understanding

Contact a new business system, first of all to figure out what the business system is mainly supporting what kind of business? And for the supporting business itself has two core content, namely the core business process is how? What is the core business object model? With this understanding, you can continue to understand what the core business functions of this business system are, and how the business modules relate to each other. How it's been linked.

Sometimes it may not be enough to know that the business system may be part of supporting an end-to-end business process or sharing business data, and you need to know where the business system or supported business is located in the end-to-end process, the relationship between the business system and the upstream business and the downstream business. Synergies and interfaces between each other.

Business systems support what kind of business, what core business objects and data are stored, which is the most basic global understanding of a business system.

Dynamic Understanding-Process Model

After a global understanding of the business system, it is necessary to begin to consider further the content of the process model. Note that the process model referred to here is not a workflow or a human approval flow model, but a business process model. Or, understand the business modeling aspects of the business system itself in the analysis design.

Understanding the business modeling or business process model the question that needs to be addressed is why a business system has these business modules, and how these business modules work together to support the business process. Any business module will have input and output, understand the input and output of the business module can be more clear how the business module is connected and integrated to support the top of the core business.

If a business system is built on the SOA mindset, you may see what the top core business modules are, the core domain service layer and the underlying data model layer, and how the core business modules themselves invoke the core Domain Services for collaboration and cohesion. It's only clear that business processes can understand the synergy and integration relationships between business modules, otherwise you see isolated business modules, breakpoints between business modules and business processes that don't really figure out how business modules work together to support the business.

If a business system itself is a process-oriented business system, and these processes are largely approval flow, then even if the approval flow definition is complex, the entire business system itself is simple, because there is no such a large number of business modules between the coordination situation.

Static Understanding-Data Model

The complexity of a business system is often embodied in two aspects, one aspect is the coordination and interaction between the business module itself is complex, one is the underlying data model and the relationship is complex. After solving the problem of dynamic analysis at the first level, it is necessary to begin to consider the second level of the data model to understand the level of the problem.

In any business process, the dynamic collaboration between modules will eventually persist into the database, becoming an association dependency between the data table and the data table in the database and the mapping relationship. Business systems that are referred to as process-centric business systems or data-centric business systems must understand the underlying data model for a data-centric business system. The first understanding of this data model is to understand the meta-model structure, which is not a simple single data object, but a correlation between multiple data objects, mapping relationships, hierarchical relationships, and so on. It is because of these relationships between the data that a complex data network is formed.

The understanding of the data model can be divided into the following types, one is the structure of a single object, including the master-slave, hierarchical and other structures, and then the object and the object of the association between the dependency structure, such as a pair of many, many-to-many structures. For more complex business systems, you may also see that in order to ensure the scalability and flexibility of the underlying data model, often the data model layer will be based on the object-oriented thinking of the further abstraction, then in this case it must be the OO object model and the structure-oriented database model together to reference understanding, To analyze and understand how the final data is stored, and how the data is ultimately presented after it is stored.

Dynamic combination-critical business analysis

Personal understanding, for the new into a new business system, if you can understand this step, the basic can have a more comprehensive understanding of a business system. The first is to understand the business process and the inter-module collaboration, then to understand the data model and the relationship between the data, and finally the real core business to further understand the final data in the process of the end of the storage. The storage of final static data driven by dynamic business processes is grounded and the relationship is established. Only in this way can the analysis of processes and data eventually converge into a single whole.

For critical business analysis you will see that for these key businesses you need to understand exactly what modules are involved in collaboration, what core data will eventually be produced in the collaborative process of the module, or what the state of the core data will change or the relationship between the data. What you really need to focus on is not the changes and modifications that are familiar to some data in a single data object, but more about the changes in the state of the data objects driven by the core business process, the modification of the relationship between data objects, and the adjustment of the mapping model among the data.

For a complete business system, as long as there is basic data object maintenance function, but to really support the business, you will see the data objects in the key attributes, the key dependency changes, and ultimately by the upper layer of business modules and processes to support, Then you have to be able to really understand how all the core business processes ultimately affect the underlying data model.

How to get familiar with business