Yesterday, Michael Chen and I explored some questions about "BMD" and "MDA", but he is not very clear about "how to assemble the application".
In fact, this is also a confusion of most MDA enthusiasts - because the MDA is focusing on "model", but this is a very vague concept. So after coming out of the "business model", although this seems to be a more abstract concept, it is really in line with the idea of the application. - Because from the customer's perspective, it pays more attention to the business description.
However, the granularity and field of the business is a problem, and a business may be composed of multiple steps, or a series of sub-process consists, or even a simple combination of simple features; at the same time, different The field of business is different - these two issues are currently affecting the bottlenecks developed by the BMD platform.
However, from the management point of view, these two points are also a core management core: different areas, determine the characteristics of enterprise management methods; while different sizes, behaviors, markets, and organizational architecture and management strategies for enterprises. Executive division has fundamentally affected.
In fact, this also determines the division of the market of course management (information) software: It is difficult to find all the markets.
It's a bit long (this is the disadvantage of essays, there is no topic before writing).
The words retired. Any management behavior or business is a combination of abstract "processing procedures". Although we can definitely in reality, the main process of business processing is more ordered, but the "fine branch" of the business process is more disorder.
This is the idea of managing management: a business main business or middle-level execution process is more rigorous, and the outermost organizational or business execution is more loose, so that the market can adapt to market and business processing. .
However, this abstraction of the business process is a big problem. Therefore, almost all BMD platforms are dominated by "providing secondary development", and all platforms provide Workflow as core modules, which are used to "connect the business process to". "
We need to understand that the business is a "processing process" ordered composition - this is the pipeline idea; Workflow will be combined with these dispersed processing, and in order to become a complete business.
Of course, the initial meaning of Workflow itself is the "logistics" "information flow" "" logistics "" "logistics" "" logistics "" "logistics", which is related to business management. So the workflow is abstracting the processing of these business flows with an orderly task point. We can understand the process of business as "process", of course, this core is Workflow. During this business process, it is to coordinate resources, maintain privileges, control costs, and process information, which is the fundamental of ensuring and maintaining a business effective implementation. This has determined that Workflow is a complex "module".
(Photos: http://www.javafox.org download)
