CN117611095B - Design method of multifunctional combination collocation system applied to supply chain - Google Patents
Design method of multifunctional combination collocation system applied to supply chain Download PDFInfo
- Publication number
- CN117611095B CN117611095B CN202311660179.9A CN202311660179A CN117611095B CN 117611095 B CN117611095 B CN 117611095B CN 202311660179 A CN202311660179 A CN 202311660179A CN 117611095 B CN117611095 B CN 117611095B
- Authority
- CN
- China
- Prior art keywords
- chain
- logic
- entity
- business
- point
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 238000000034 method Methods 0.000 title claims abstract description 28
- 230000006870 function Effects 0.000 claims abstract description 58
- 230000008569 process Effects 0.000 claims description 9
- 238000010586 diagram Methods 0.000 claims description 6
- 230000004927 fusion Effects 0.000 claims description 5
- 230000011218 segmentation Effects 0.000 claims description 5
- 230000000694 effects Effects 0.000 claims description 4
- 238000002372 labelling Methods 0.000 claims description 3
- 230000009471 action Effects 0.000 description 1
- 238000012550 audit Methods 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 238000003306 harvesting Methods 0.000 description 1
- 238000002955 isolation Methods 0.000 description 1
- 230000007246 mechanism Effects 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/10—Office automation; Time management
- G06Q10/103—Workflow collaboration or project management
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/06—Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
- G06Q10/063—Operations research, analysis or management
- G06Q10/0633—Workflow analysis
Landscapes
- Business, Economics & Management (AREA)
- Human Resources & Organizations (AREA)
- Engineering & Computer Science (AREA)
- Strategic Management (AREA)
- Entrepreneurship & Innovation (AREA)
- Economics (AREA)
- General Business, Economics & Management (AREA)
- Marketing (AREA)
- Operations Research (AREA)
- Quality & Reliability (AREA)
- Tourism & Hospitality (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Theoretical Computer Science (AREA)
- Data Mining & Analysis (AREA)
- Development Economics (AREA)
- Educational Administration (AREA)
- Game Theory and Decision Science (AREA)
- Stored Programmes (AREA)
Abstract
The invention discloses a design method of a multifunctional combination collocation system applied to a supply chain, which comprises the following steps: when subsystems of any two different service scenes are matched, determining one subsystem as a main chain and the other subsystem as a secondary chain according to the corresponding service flow function of the subsystem and the position of the service flow function in the service overall logic; the context semantic rules of the entity components corresponding to the main chain and the auxiliary chain are deduced one by one through the logic analysis model, and whether any entity component on the auxiliary chain and any entity component on the main chain have relevance of connection by taking the context semantic rules as the connection is judged, and parameters between the entity components are transferred by context semantics, so that functions which can be realized by different platforms can be matched and used practically, namely, the combination of subsystem and subsystem of a system can be defined.
Description
Technical Field
The invention relates to the technical field of combination collocation design of supply chain systems, in particular to a design method of a multifunctional combination collocation system applied to a supply chain.
Background
The requirement of many logistics enterprises is across-field, and according to industry specifications, different application platforms are usually manufactured according to different fields. Therefore, enterprises have to use systems in various scenes to complete operations of different functions, exchange among the systems is easy to generate errors, and in the traditional technology, for example WMS, TMS, OMS, the three are not separated, so that all the operations can be completed in one application system. However, because the programming languages used by different operation platforms are different, the functions of the different platforms cannot be completely embedded in the same platform.
Disclosure of Invention
In view of the above, in order to solve the problems in the prior art, the present invention provides a design method of a multifunctional combination collocation system applied to a supply chain.
The main technical scheme is as follows:
the design method of the multifunctional combination collocation system applied to the supply chain comprises the following steps:
Acquiring subsystems under different service scenes and service flow diagrams corresponding to the subsystems, obtaining a system structure of the subsystems according to the service flow diagrams, dividing the subsystems into a plurality of entity components according to the system structure, and acquiring service rules and logic chains corresponding to the entity components;
Corresponding labeling is carried out on business rules among entity components through the logic chain, so that each chain point on the logic chain is matched with a corresponding context semantic rule;
When subsystems of any two different service scenes are matched, determining one subsystem as a main chain and the other subsystem as a secondary chain according to the corresponding service flow function of the subsystem and the position of the service flow function in the service overall logic;
The method comprises the steps that context semantic rules of entity components corresponding to a main chain and a secondary chain are estimated one by one through a logic analysis model, whether any entity component on the secondary chain and any entity component on the main chain are in association with each other or not is judged, when the association exists, a chain point corresponding to the entity component on the secondary chain and a logic chain corresponding to the chain point are extracted through the context semantic rules, the corresponding logic chain is segmented through the chain point serving as a segmentation point, an embedded logic chain taking the chain point as a starting point is obtained, and the embedded logic chain is input to the main chain through the context semantic; when the service is not available, fusion cannot be performed, and the subsystems of two different service scenes cannot be collocated.
Further, the business flow chart is divided into a plurality of information flow nodes according to the execution task nodes, and each information flow node is used as a benchmark for demarcating business boundaries, wherein each information flow node corresponds to one entity component.
Further, each executing task node is represented as a task flow, and the task flow has uniqueness.
Further, the system structure is a flow structure representing a task flow formed by arranging a plurality of entity components in a business flow.
Further, the business rules of the entity components are defined by script components, and a subsystem uses one script component to define the business rules of all entity components contained in the subsystem;
Wherein, the business rule comprises the following two parts:
A first part: defining association relations with other entity components through natural semantic functions;
a second part: defining the entity components and other entity components to form unique association under different scenes through standard semantics so as to achieve the effect of exclusive association;
The standard semantics are used for limiting the directions of the association relations through standard natural semantic functions, and the directions are set to be unique.
Further, the logic chain is used to represent control logic of business rules among all the linked entity components in the subsystem in the sense of task flow.
Further, the logical chain has a number of chain points, each chain point comprising:
① : the matching relation between the entity components is formed through the first label;
② : business rules corresponding to the entity components and matching the business rules with the entity components by a first label;
③ : and the context semantic rule is formed by a natural semantic function and a standard natural semantic function and is analyzed by the business rule.
Further, the business process function and the position of the business process function in the business overall logic are expressed as: the subsystem is used for realizing the business functions in the whole system, judging the sequence of the business functions according to the up-down association functions which are butted by the business functions, and judging at least one function position according to the sequence.
Further, the logic analysis model has:
The logic library is used for storing context semantic rules;
the analysis unit is used for calling the logic library to infer whether unique association exists between any two entity components through context natural semantics;
And the output unit is used for outputting the analysis result.
Further, the method for linking the embedded logic chain to the main chain through the context semantics comprises the following steps: and acquiring an associated chain point corresponding to the chain point and the main chain, taking a next-stage chain point corresponding to the associated chain point as a embedding point, writing conditional semantics formed by natural semantic functions into a business rule of the next-stage chain point, and setting a logic path formed by limiting the basis conditions of two natural semantic functions in the next-stage chain point by the conditional semantics.
The application has the following beneficial effects:
The method for arranging the business process is utilized in the application, so that all the used entity components are parameter-free, namely, the inlet and outlet parameters of the entity components are standardized, and no specific parameters are needed. The parameters between the entity components are transferred by context semantics, so that the functions which can be realized by different platforms can be matched and used in practice, namely, the combination of subsystem in the system can be defined.
In order to enable collocation to be realized, when a plurality of subsystems are matched, firstly, determining which subsystem is used as a main chain and which subsystem is used as a secondary chain according to a service flow function corresponding to the subsystem and the position of the service flow function in service overall logic, performing gradual speculation on context semantic rules of entity components corresponding to the main chain and the secondary chain through a logic analysis model, judging whether any entity component on the secondary chain and any entity component on the main chain are in association with each other by taking the context semantic rules as connection, and when the association exists, extracting a chain point corresponding to the entity component on the secondary chain and a logic chain corresponding to the chain point by taking the chain point as a segmentation point, so as to obtain an embedded logic chain taking the chain point as a starting point, and linking the embedded logic chain to the main chain through the context semantic rules; when the service is not available, fusion cannot be performed, and the subsystems of two different service scenes cannot be collocated.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings required for the description of the embodiments will be briefly described below, and it is apparent that the drawings in the following description are only some embodiments of the present invention, and other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.
FIG. 1 is a flow chart of a method provided by the present invention.
Detailed Description
For the purpose of making the objects, technical solutions and advantages of the present invention more apparent, the embodiments of the present invention will be described in further detail with reference to the accompanying drawings.
Example 1
Referring to fig. 1, the application provides a design method of a multifunctional combination collocation system applied to a supply chain, comprising the following steps:
Acquiring subsystems under different service scenes and service flow diagrams corresponding to the subsystems, obtaining a system structure of the subsystems according to the service flow diagrams, dividing the subsystems into a plurality of entity components according to the system structure, and acquiring service rules and logic chains corresponding to the entity components;
Corresponding labeling is carried out on business rules among entity components through the logic chain, so that each chain point on the logic chain is matched with a corresponding context semantic rule;
When subsystems of any two different service scenes are matched, determining one subsystem as a main chain and the other subsystem as a secondary chain according to the corresponding service flow function of the subsystem and the position of the service flow function in the service overall logic;
The method comprises the steps that context semantic rules of entity components corresponding to a main chain and a secondary chain are estimated one by one through a logic analysis model, whether any entity component on the secondary chain and any entity component on the main chain are in association with each other or not is judged, when the association exists, a chain point corresponding to the entity component on the secondary chain and a logic chain corresponding to the chain point are extracted through the context semantic rules, the corresponding logic chain is segmented through the chain point serving as a segmentation point, an embedded logic chain taking the chain point as a starting point is obtained, and the embedded logic chain is input to the main chain through the context semantic; when the service is not available, fusion cannot be performed, and the subsystems of two different service scenes cannot be collocated.
In the above, by dividing the service flow chart into a plurality of information flow nodes according to the execution task node, each information flow node is used as a benchmark for defining a service boundary, where each information flow node corresponds to one entity component, where the entity component is programmed by using a Vue tool (no code tool platform), an access port of the entity component is set as a standard parameter, and parameters between the entity components are transferred by context semantics, so that in any scenario, the entity components with the association can be associated by context semantics.
In some embodiments, for example, taking the harvested business process as an example, the corresponding execution task nodes include a start-new creation button action-pop-up new harvest sheet-new save button-create order process-enable button action-enable flow expression-audit button action … …, and these execution task nodes are information flow nodes. Each executing task node is represented as a task flow, and the task flow has uniqueness.
Further, the system structure is a flow structure representing a task flow formed by arranging a plurality of entity components in a business flow.
Further, the business rules of the entity components are defined by script components, and a subsystem uses one script component to define the business rules of all entity components contained in the subsystem;
Wherein, the business rule comprises the following two parts:
A first part: defining association relations with other entity components through natural semantic functions;
a second part: defining the entity components and other entity components to form unique association under different scenes through standard semantics so as to achieve the effect of exclusive association;
The standard semantics are used for limiting the directions of the association relations through standard natural semantic functions, and the directions are set to be unique.
Further, the logic chain is used to represent control logic of business rules among all the linked entity components in the subsystem in the sense of task flow.
Further, the logical chain has a number of chain points, each chain point comprising:
① : the matching relation between the entity components is formed through the first label;
② : business rules corresponding to the entity components and matching the business rules with the entity components by a first label;
③ : and the context semantic rule is formed by a natural semantic function and a standard natural semantic function and is analyzed by the business rule.
Further, the business process function and the position of the business process function in the business overall logic are expressed as: the subsystem is used for realizing the business functions in the whole system, judging the sequence of the business functions according to the up-down association functions which are butted by the business functions, and judging at least one function position according to the sequence.
Further, the logic analysis model has:
The logic library is used for storing context semantic rules;
the analysis unit is used for calling the logic library to infer whether unique association exists between any two entity components through context natural semantics;
And the output unit is used for outputting the analysis result.
Further, the method for linking the embedded logic chain to the main chain through the context semantics comprises the following steps: and acquiring an associated chain point corresponding to the chain point and the main chain, taking a next-stage chain point corresponding to the associated chain point as a embedding point, writing conditional semantics formed by natural semantic functions into a business rule of the next-stage chain point, and setting a logic path formed by limiting the basis conditions of two natural semantic functions in the next-stage chain point by the conditional semantics.
The method for arranging the business process is utilized in the application, so that all the used entity components are parameter-free, namely, the inlet and outlet parameters of the entity components are standardized, and no specific parameters are needed. The parameters between the entity components are transferred by context semantics, so that the functions which can be realized by different platforms can be matched and used in practice, namely, the combination of subsystem in the system can be defined.
In order to enable collocation to be realized, when a plurality of subsystems are matched, firstly, determining which subsystem is used as a main chain and which subsystem is used as a secondary chain according to a service flow function corresponding to the subsystem and the position of the service flow function in service overall logic, performing gradual speculation on context semantic rules of entity components corresponding to the main chain and the secondary chain through a logic analysis model, judging whether any entity component on the secondary chain and any entity component on the main chain are in association with each other by taking the context semantic rules as connection, and when the association exists, extracting a chain point corresponding to the entity component on the secondary chain and a logic chain corresponding to the chain point by taking the chain point as a segmentation point, so as to obtain an embedded logic chain taking the chain point as a starting point, and linking the embedded logic chain to the main chain through the context semantic rules; when the service is not available, fusion cannot be performed, and the subsystems of two different service scenes cannot be collocated.
In some embodiments, because the parameters of the gateway of the entity assembly do not need to be reset, the parameters between the entity assembly and the entity assembly are transferred by context semantics, so that the business process arrangement does not need to form hooks with programming languages. In combination with hot refreshing, the online service does not need to issue second change logic, wherein the rules support xml, json, yml three rule file writing modes.
In some embodiments, since the parameters of the gateway of the entity component do not need to be reset, the parameters between the entity component and the entity component are transferred by context semantics, when the application scene changes, the corresponding business rule also changes, but the application does not need to be restarted, and the executing rule does not have any disorder due to the refresh rule under high concurrency.
In some embodiments, the entity components and other entity components form unique association under different scenes by defining standard semantics among different association relations, so as to achieve the effect of exclusive association. Therefore, the present application has a reliable context isolation mechanism without worrying about data streaming in high concurrency situations.
In some embodiments, although the present application defines that an entity component has unique association with other entity components, it does not represent that an entity component cannot form an association with other entity components under an application flow, and the present application defines association relationships with other entity components by a natural semantic function through a rule part, and the association relationships are not unique, and can define a logical path formed by writing conditional semantics formed by the natural semantic function in a business rule part in a script file and setting the conditional semantics in accordance with conditions of two natural semantic functions in one business rule.
In some embodiments, the subsystems in the original system are generally used as a main chain, and the embedded subsystem is used as a secondary chain, if multiple subsystems are collocated in one system at the same time, the next subsystem is fused after the subsystems are fused in a pairwise collocation mode.
The foregoing description of the preferred embodiments of the invention is not intended to limit the invention to the precise form disclosed, and any such modifications, equivalents, and alternatives falling within the spirit and scope of the invention are intended to be included within the scope of the invention.
Claims (3)
1. The design method of the multifunctional combination collocation system applied to the supply chain is characterized by comprising the following steps of:
Acquiring subsystems under different service scenes and service flow diagrams corresponding to the subsystems, obtaining a system structure of the subsystems according to the service flow diagrams, dividing the subsystems into a plurality of entity components according to the system structure, and acquiring service rules and logic chains corresponding to the entity components;
Corresponding labeling is carried out on business rules among entity components through the logic chain, so that each chain point on the logic chain is matched with a corresponding context semantic rule;
When subsystems of any two different service scenes are matched, determining one subsystem as a main chain and the other subsystem as a secondary chain according to the corresponding service flow function of the subsystem and the position of the service flow function in the service overall logic;
the method comprises the steps that context semantic rules of entity components corresponding to a main chain and a secondary chain are estimated one by one through a logic analysis model, whether any entity component on the secondary chain and any entity component on the main chain are in association with each other or not is judged, when the association exists, a chain point corresponding to the entity component on the secondary chain and a logic chain corresponding to the chain point are extracted through the context semantic rules, the corresponding logic chain is segmented through the chain point serving as a segmentation point, an embedded logic chain taking the chain point as a starting point is obtained, and the embedded logic chain is input to the main chain through the context semantic; when the two subsystems of the two different service scenes cannot be matched, fusion cannot be carried out;
The system structure is a flow structure which is formed by arranging a plurality of entity components in a business flow and represents a task flow;
the business rules of the entity components are defined through script components, and a subsystem uses one script component to define the business rules of all entity components contained in the subsystem;
Wherein, the business rule comprises the following two parts:
A first part: defining association relations with other entity components through natural semantic functions;
a second part: defining the entity components and other entity components to form unique association under different scenes through standard semantics so as to achieve the effect of exclusive association;
The standard semantics are used for limiting the direction of the association relation through a standard natural semantic function, and setting the direction to be unique;
the logic chain is used for representing control logic of business rules among all the linked entity components in the subsystem in the direction of task flows;
The logic chain has a number of chain points, each chain point comprising:
① : the matching relation between the entity components is formed through the first label;
② : business rules corresponding to the entity components and matching the business rules with the entity components by a first label;
③ : a context semantic rule formed by a natural semantic function and a standard natural semantic function which are analyzed by the business rule;
the position of the business process function in the business overall logic is expressed as: the subsystem is used for realizing the business functions in the whole system, judging the sequence of the business functions according to the up-down association functions which are butted by the business functions, and judging at least one function position according to the sequence;
The logic analysis model has:
The logic library is used for storing context semantic rules;
the analysis unit is used for calling the logic library to infer whether unique association exists between any two entity components through context natural semantics;
The output unit is used for outputting an analysis result;
the method for linking the embedded logic chain to the main chain through the context semantics comprises the following steps:
and acquiring an associated chain point corresponding to the chain point and the main chain, taking a next-stage chain point corresponding to the associated chain point as a embedding point, writing conditional semantics formed by natural semantic functions into a business rule of the next-stage chain point, and setting a logic path formed by limiting the basis conditions of two natural semantic functions in the next-stage chain point by the conditional semantics.
2. The method for designing a multifunctional combined collocation system applied to a supply chain according to claim 1, wherein each information flow node is used as a benchmark for defining a service boundary by dividing the service flow chart into a plurality of information flow nodes according to execution task nodes, and each information flow node corresponds to one entity component.
3. The method of claim 2, wherein each task executing node is represented as a task flow, and the task flow is unique.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311660179.9A CN117611095B (en) | 2023-12-06 | 2023-12-06 | Design method of multifunctional combination collocation system applied to supply chain |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311660179.9A CN117611095B (en) | 2023-12-06 | 2023-12-06 | Design method of multifunctional combination collocation system applied to supply chain |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN117611095A CN117611095A (en) | 2024-02-27 |
| CN117611095B true CN117611095B (en) | 2024-04-26 |
Family
ID=89959632
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202311660179.9A Active CN117611095B (en) | 2023-12-06 | 2023-12-06 | Design method of multifunctional combination collocation system applied to supply chain |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN117611095B (en) |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110389748A (en) * | 2019-06-17 | 2019-10-29 | 平安银行股份有限公司 | Business data processing method and terminal device |
| CN111199381A (en) * | 2019-11-25 | 2020-05-26 | 江苏艾佳家居用品有限公司 | Intelligent work order approval method based on process engine |
| CN114817499A (en) * | 2022-04-18 | 2022-07-29 | 重庆长安汽车股份有限公司 | Method and system for flexibly constructing service scene multi-turn conversations |
| WO2022237334A1 (en) * | 2021-05-12 | 2022-11-17 | 华为技术有限公司 | Knowledge representation and deduction method and apparatus for service logic |
| CN116661978A (en) * | 2023-08-01 | 2023-08-29 | 浙江云融创新科技有限公司 | Distributed flow processing method and device and distributed business flow engine |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US11436544B2 (en) * | 2014-09-03 | 2022-09-06 | CloudLeaf, Inc. | System for managing an industrial workflow |
-
2023
- 2023-12-06 CN CN202311660179.9A patent/CN117611095B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110389748A (en) * | 2019-06-17 | 2019-10-29 | 平安银行股份有限公司 | Business data processing method and terminal device |
| CN111199381A (en) * | 2019-11-25 | 2020-05-26 | 江苏艾佳家居用品有限公司 | Intelligent work order approval method based on process engine |
| WO2022237334A1 (en) * | 2021-05-12 | 2022-11-17 | 华为技术有限公司 | Knowledge representation and deduction method and apparatus for service logic |
| CN114817499A (en) * | 2022-04-18 | 2022-07-29 | 重庆长安汽车股份有限公司 | Method and system for flexibly constructing service scene multi-turn conversations |
| CN116661978A (en) * | 2023-08-01 | 2023-08-29 | 浙江云融创新科技有限公司 | Distributed flow processing method and device and distributed business flow engine |
Also Published As
| Publication number | Publication date |
|---|---|
| CN117611095A (en) | 2024-02-27 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN106919434B (en) | Code generation method and device | |
| CN103441900B (en) | Centralized cross-platform automatization test system and control method thereof | |
| CN102541521B (en) | Automatic operating instruction generating device based on structured query language and method | |
| CN107885499A (en) | A kind of interface document generation method and terminal device | |
| CN110287052A (en) | A kind of root of abnormal task determines method and device because of task | |
| CN104133772A (en) | Automatic test data generation method | |
| CN101617292A (en) | Programming and execution towards producer graph | |
| CN108197027B (en) | Software performance optimization method, storable medium, computer program | |
| CN108846660B (en) | Method and system for identifying abnormal fund | |
| CN109522005A (en) | Cross-platform GRAPHICAL PROGRAMMING method | |
| CN112328488A (en) | Control object identification method for UI (user interface) automatic test | |
| CN113641739B (en) | Spark-based intelligent data conversion method | |
| CN117611095B (en) | Design method of multifunctional combination collocation system applied to supply chain | |
| CN101894317B (en) | System and method for driving business logic through data changes | |
| Blake et al. | Systems simulation with digital computers | |
| CN104503733A (en) | Merging method and device for state machine | |
| CN104731900A (en) | Hive scheduling method and device | |
| CN115205030A (en) | Wind-controlled user portrait system based on configurable big data analysis | |
| CN115509904A (en) | Assertion generation method and device of interface test case | |
| CN116450246A (en) | Event stream configurable method based on state machine | |
| CN113918165A (en) | Method and system for compiling text description type flow description into application automatic operation script | |
| CN115033280A (en) | Knowledge graph-based automatic generation method for requirement specification document and storage medium | |
| US6385763B1 (en) | Methodology for mapping use cases to operations for operational profile development | |
| CN110297773B (en) | Visualization method, storage medium and terminal for assertion synthesis in formal verification | |
| US20090138249A1 (en) | Defining operational elements in a business process model |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |