CN111552459B - Service arrangement flow management system and method - Google Patents
Service arrangement flow management system and method Download PDFInfo
- Publication number
- CN111552459B CN111552459B CN202010301322.5A CN202010301322A CN111552459B CN 111552459 B CN111552459 B CN 111552459B CN 202010301322 A CN202010301322 A CN 202010301322A CN 111552459 B CN111552459 B CN 111552459B
- Authority
- CN
- China
- Prior art keywords
- business
- service
- flow
- logic
- definition
- 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
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/20—Software design
-
- 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
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02P—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN THE PRODUCTION OR PROCESSING OF GOODS
- Y02P90/00—Enabling technologies with a potential contribution to greenhouse gas [GHG] emissions mitigation
- Y02P90/30—Computing systems specially adapted for manufacturing
Landscapes
- Engineering & Computer Science (AREA)
- Business, Economics & Management (AREA)
- Human Resources & Organizations (AREA)
- Strategic Management (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- Entrepreneurship & Innovation (AREA)
- Software Systems (AREA)
- General Physics & Mathematics (AREA)
- Operations Research (AREA)
- Tourism & Hospitality (AREA)
- General Business, Economics & Management (AREA)
- Quality & Reliability (AREA)
- Marketing (AREA)
- Economics (AREA)
- Data Mining & Analysis (AREA)
- Stored Programmes (AREA)
Abstract
The invention relates to the technical field of computer software development, in particular to a business arrangement flow management system and a business arrangement flow management method, wherein the business arrangement flow management method is applied to the system, the system comprises a server, and the server comprises the following modules: an initial creation module: the method comprises the steps of creating a FlowDefinition function, creating a business arrangement flow according to the FlowDefinition function, and packaging input and output of the business arrangement flow; the flow creation module: the method comprises the steps of creating Definition functions, defining a business arrangement flow through the Definition functions and concrete business implementation contents; the flow definition module: a step for creating a business process execution unit to define a business orchestration process; the flow construction module: and the method is used for calling the Build function to complete the construction of the whole business orchestration flow after the creation of the business flow execution unit is completed, so as to form an executable FlowDefinition function. The invention can carry out flow management on the business arrangement, standardizes the style of writing codes by developers, and solves the problems of poor readability and maintainability of business flow codes.
Description
Technical Field
The invention relates to the technical field of computer software development, in particular to a business arrangement flow management system and method.
Background
With development and change of programming services, the changing requirements of programming service logic codes are continuously increased, programming capability of programmers is different and habits are different, so that service code redundancy and bug occurrence frequency are high, the problems of low programming efficiency, slower investigation and higher learning difficulty are also caused, people pay attention to the moment, although programmers all have respective optimization methods to solve the programming related problems, service scenes are gradually complicated, most application scenes have additional data sources to be added to further increase new codes, and the problem of new code redundancy is continuously caused after the optimization of the former step, so that the existing requirements of light weight, standardization, flow, high readability and maintainability for service programming are difficult to meet. Therefore, the business process is perfected by writing and arranging the business codes in a flow manner, so that the problems of poor readability and maintainability of the business process codes are solved.
Disclosure of Invention
One of the main purposes of the invention is to provide a business arrangement flow management system which can carry out flow management on business arrangement, standardize the style of code written by developers and solve the problems of poor readability and maintainability of business flow codes.
In order to achieve the above purpose, the present invention provides a business arrangement flow management system, which comprises a server, wherein the server comprises the following modules:
an initial creation module: the method comprises the steps of creating a FlowDefinition function, creating a business arrangement flow according to the FlowDefinition function, and packaging input and output of the business arrangement flow;
the flow creation module: the method comprises the steps of creating Definition functions, defining a business arrangement flow through the Definition functions and concrete business implementation contents;
the flow definition module: the method comprises the steps of creating a business process execution unit to define a business arrangement process, wherein the business process execution unit comprises a business start unit, a plurality of basic business logic units and an end business unit which are sequentially executed, and then giving specific business implementation contents of the business arrangement process of the basic business logic units; the basic service logic units are used for dividing specific service implementation contents into a plurality of sub-services, and the basic service logic units are used for defining service definitions of the sub-services and execution logic of the sub-services;
the flow construction module: and the method is used for calling the Build function to complete the construction of the whole business orchestration flow after the creation of the business flow execution unit is completed, so as to form an executable FlowDefinition function.
The invention has the advantages that:
1. the flow Definition function created by the initial creation module and the Definition function created by the flow creation module are convenient for building a large framework of the whole service, and after the large framework is built, the steps of the service arrangement flow and specific service implementation content can be defined in the large framework.
2. The setting of the flow definition module utilizes a business flow execution unit to concretely divide the steps of the business arrangement flow, and the business flow execution unit comprises a business start unit, a plurality of basic business logic units and an end business unit which are sequentially executed. The method comprises the steps of dividing specific service implementation content into a plurality of sub-services by a plurality of basic service logic units, dividing the whole large service into a plurality of sub-services, and refining and differentiating the whole service step continuously through the sub-services. The realization of the whole large service is conveniently completed, and new service can be conveniently expanded by adding sub-service modes in a later large frame. When the sub-service is added to the whole large service, only the basic service logic unit is added to the basic service logic unit, and the large-scale modification is not needed, so that the addition and deletion are more convenient, and the arrangement is more regular. Therefore, the service is more standardized and flowered in the actual code programming process, and has good readability and convenient maintenance.
3. The initial creation module, the flow definition module and the flow construction module are convenient for carrying out precise and modularized arrangement on the whole business arrangement flow, and when the sub business is added to the whole large business, only the basic business logic unit is needed to be added to the basic business logic unit, the large-scale modification is not needed, the sub business addition and deletion are more convenient, and the arrangement is more regular. Programmers with different capacities program codes which are also simplified and standardized, so that the service writing capacity of the programmers is effectively improved, the style of writing codes by the programmers can be standardized by the mode, the code redundancy and the bug occurrence space are reduced, the use is simple, the operation is easy, and no extra learning cost exists.
Further, the service initiation unit is used for constructing a framework of a service orchestration flow, and the construction of the service initiation unit is realized through a service initiation construction module;
and a service initiation construction module: the method is used for constructing a framework of the business orchestration flow through the Start function and editing the name of the business orchestration flow.
The setting of the service initiation construction module facilitates the construction of the service initiation unit.
Further, when the basic service logic unit is created, service definition of the sub-service and execution logic of the sub-service are completed through a Step interface and an Invoke interface of the SteoBuilder Step constructor.
The Step interface and Invoke interface of the Step constructor can conveniently edit the sub-business to realize the corresponding functions, so that the whole structure is unified, and the coding, the consulting and the maintenance of codes are convenient.
Further, the basic service logic unit is constructed by a service content definition module and a service logic construction module;
the business content definition module: the method comprises the steps of creating a Step interface after framework construction is completed, and defining service definition of sub-services;
and a business logic construction module: and the method is used for creating Invoke interfaces after the service definition is completed, inputting specific expressions of the sub-services and constructing execution logic.
The service content definition module and the service logic construction module are arranged to facilitate definition and assembly of service logic. The coding structure of each sub-service is unified, and the coding structure is convenient for coding, consulting and maintaining.
Further, the ending service unit is used for ending the service arrangement flow, and the construction of the ending service unit is realized through a service ending module;
and a service ending module: and the end function is called after the service logic is constructed and assembled, definition of the basic service logic unit is ended, logic construction is executed, and construction of the whole service orchestration flow is completed by calling the Build function.
And the service ending module is convenient for ending the service arrangement flow.
The second main objective of the present invention is to provide a business arrangement flow management method, based on which the above system comprises the following steps:
s1, creating a FlowDefinition function, creating a business arrangement flow according to the FlowDefinition function, and packaging input and output of the business arrangement flow;
s2, creating Definition functions, and defining steps of a business arrangement flow and specific business implementation contents through the Definition functions;
s3, creating a business process execution unit to define a business arrangement process, wherein the business process execution unit comprises a business start unit, a plurality of basic business logic units and an end business unit which are sequentially executed, and then giving specific business implementation contents of the business arrangement process of the basic business logic units; the basic service logic units are used for dividing specific service implementation contents into a plurality of sub-services, and the basic service logic units are used for defining service definitions of the sub-services and execution logic of the sub-services;
and S4, after the creation of the business process execution unit is completed, calling a Build function to complete the construction of the whole business orchestration process, so as to form an executable FlowDefinition function.
The invention has the advantages that:
1. the setting of the basic service logic unit conveniently completes the realization of the whole service by dividing the specific service implementation content into a plurality of sub-services, and can conveniently expand the service in a mode of adding the sub-services in the later period, so that the service code programming is normalized, flow and readability are good, and the maintenance is convenient.
The FlowDefinition function, the Definition function and the Build function are convenient to construct the whole framework of the business arrangement flow, the business starting unit, the basic business logic units and the business ending unit are convenient to carry out simplified setting on the whole business arrangement flow, business writing capacity can be effectively improved, code redundancy and bug appearance space are reduced, and the style of writing codes by developers is standardized. And the use is simple, the upper hand is easy, and no extra learning cost exists.
Further, in the step S3, the construction of the service initiation unit specifically includes the following steps:
s301, constructing a framework of the business arrangement flow through a Start function, and editing the name of the business arrangement flow.
The framework of the whole business arrangement flow can be realized through the Start function, so that the writing of the subsequent flow is convenient.
Further, in the Step S3, the basic service logic unit completes the service definition of the sub-service and the execution logic of the sub-service through the Step interface and Invoke interface of the stepbuilder Step constructor when creating.
The sub-business functions can be conveniently realized through the Step interface and Invoke of the SteoBuilder Step constructor, the whole structure is uniform, and the code writing, the reference and the maintenance are convenient.
Further, the construction of the basic service logic unit in the step S3 specifically includes the following steps:
s302, after framework construction is completed, creating a Step interface, and defining service definition of sub-services;
s303, after the service definition is completed, creating Invoke interfaces, inputting specific expressions of sub-services, and constructing execution logic.
And the definition and the assembly of the business logic are convenient.
Further, the purchasing machine for ending the service unit in the step S3 specifically includes the following steps:
s303, after the service logic is constructed and assembled, an end function is called, definition of a basic service logic unit is ended, logic construction is executed, and construction of the whole service orchestration flow is completed by calling a Build function.
The end of the business orchestration flow is facilitated, thereby facilitating the subsequent execution of the programming program.
Drawings
FIG. 1 is a logic block diagram of a business orchestration flow management system according to an embodiment of the present invention.
Detailed Description
The following is a further detailed description of the embodiments:
example 1
A business orchestration flow management system, substantially as shown in figure 1: the server comprises the following modules:
an initial creation module: the method comprises the steps of creating a FlowDefinition function, creating a business arrangement flow according to the FlowDefinition function, and packaging input and output of the business arrangement flow; a flow definition language (Flow Definition Language, FDL) is used to describe and define business logic, similar to functions in a programming language.
The flow creation module: the method comprises the steps of creating Definition functions, defining a business arrangement flow through the Definition functions and concrete business implementation contents;
the flow definition module: a step for creating a business process execution unit to define a business orchestration process; the business process execution unit comprises a business start unit, a plurality of basic business logic units and an end business unit which are sequentially executed; definition and execution content of the service initiation unit are given, and specific service implementation content of the service arrangement flow of the basic service logic units is given; the basic service logic units are used for dividing specific service implementation contents into a plurality of sub-services, and the basic service logic units are used for defining service definitions of the sub-services and execution logic of the sub-services; and giving definition and execution content of the ending business unit.
The business starting unit is used for constructing a framework of a business arrangement flow, and the construction of the business starting unit is realized through a business starting construction module;
and a service initiation construction module: the method is used for constructing a framework of the business orchestration flow through the Start function and editing the name of the business orchestration flow.
When the basic business logic unit is created, the business definition of the sub business and the execution logic of the sub business are completed through a Step interface and an Invoke interface of the SteoBuilder Step constructor. The construction of the basic service logic unit is realized through a service content definition module and a service logic construction module;
the business content definition module: the method comprises the steps of creating a Step interface after framework construction is completed, and defining service definition of sub-services;
and a business logic construction module: and the method is used for creating Invoke interfaces after the service definition is completed, inputting specific expressions of the sub-services and constructing execution logic.
The ending business unit is used for ending the business arrangement flow, and the construction of the ending business unit is realized through a business ending module;
and a service ending module: and the method is used for calling the end function after the assembly of the constructed service logic, ending the definition of the basic service logic unit and executing the logic construction.
The flow construction module: and the method is used for calling the Build function to complete the construction of the whole business orchestration flow after a plurality of business flow execution units are created.
The specific embodiment is as follows:
(1) The initial creation module creates a FlowDefinition function; specific examples are as follows:
public FlowDefinition<CreditInfoIdQueryContext,CreditInfoIdQueryRespDto>。
(2) The flow creation module creates Definition functions, and specific examples are as follows:
definition(){}。
(3) The business Start construction module constructs a framework of a business arrangement flow through a Start function in definition () { }, and edits the name of the business arrangement flow; specific examples are as follows:
start (name: "acquire info") FlowDefinitionBuilder < CreditInfoIdQueryContext, creditInfoIdQueryRespDto >.
(4) When the basic service logic unit is created, the service definition of the sub-service and the execution logic of the sub-service are completed through a Step interface and an Invoke interface of the SteoBuilder Step constructor; the business content definition module creates a Step interface to define business definition of sub business; the business logic construction module creates Invoke interfaces, inputs concrete expressions of sub-businesses, and constructs execution logic, and concrete examples are as follows:
step (name: "examination of local library information") StepBuilder < CreditInfoIdQueryContext, creditInfoIdQueryRespDto >
invoke(this::queryUnification)DefaultStepBuilder<CreditInfoIdQueryContext,CreditlnfoIdQueryRespDt
step (newStep: "judgment result examination") stepkuild er < CreditInfoIdQueryContext, creditInfoIdQueryRespDto >
invoke(this::query Inf old)DefaultStepBuilder<CreditInfoIdQueryContext,CreditlnfoIdQueryRespDto>
step (newStep: "acquire: return parameter") stepwilder < CreditInfoIdQueryContext, creditlnfoIdQueryRespDto >.
(5) After the service end module builds the service logic, the end function is called, the definition of the basic service logic unit is ended, and the logic building is executed, and the specific example is as follows:
end(this::getOutcome)EndStepBuilder<CreditInfoIdQueryContextz CreditlnfoIdQueryRespDto>。
(6) The building function is called to complete the construction of the whole business arrangement flow, and specific examples are as follows: build ().
The initial creation module, the flow definition module and the flow construction module are convenient for carrying out the precise and modularized arrangement on the whole business arrangement flow, dividing the specific business implementation content into a plurality of sub-businesses, conveniently completing the realization of the whole business, expanding the business in a mode of adding the sub-businesses at a later stage, for example, creating a Step interface through the business content definition module, and creating an Invoke interface by the business logic construction module to realize the addition and editing of the sub-businesses, so that the programming standardization, the flow and the readability of the business codes are good, and the maintenance is convenient. The method can effectively improve the service writing capability, reduce the code redundancy and bug appearance space, and standardize the style of writing codes for developers. And the use is simple, the upper hand is easy, and no extra learning cost exists.
The business arrangement flow management method is applied to the system and comprises the following steps,
s1, creating a FlowDefinition function, creating a business arrangement flow according to the FlowDefinition function, and packaging input and output of the business arrangement flow;
s2, creating Definition functions, and defining steps of a business arrangement flow and specific business implementation contents through the Definition functions;
s3, creating a business process execution unit to define a business arrangement process, wherein the business process execution unit comprises a business start unit, a plurality of basic business logic units and an end business unit which are sequentially executed, and then giving specific business implementation contents of the business arrangement process of the basic business logic units; the basic service logic units are used for dividing specific service implementation contents into a plurality of sub-services, and the basic service logic units are used for defining service definitions of the sub-services and execution logic of the sub-services;
the construction of the service initiation unit in step S3 specifically includes the following steps:
s301, constructing a framework of the business arrangement flow through a Start function, and editing the name of the business arrangement flow.
The construction of the basic service logic unit in the step S3 specifically comprises the following steps:
s302, after framework construction is completed, creating a Step interface, and defining service definition of sub-services;
s303, after the service definition is completed, creating Invoke interfaces, inputting specific expressions of sub-services, and constructing execution logic.
The purchasing machine body for ending the service unit in the step S3 comprises the following steps:
s303, after the service logic is constructed and assembled, an end function is called, and definition of the basic service logic unit and logic construction are finished.
S4, after a plurality of business process execution units are created, calling a Build function to complete the construction of the whole business arrangement process.
The foregoing is merely an embodiment of the present invention, and details of structures and features well known in the art are not described herein, so that those skilled in the art will be able to ascertain all prior art in the field, and will not be able to ascertain any prior art to which this invention pertains by using the general knowledge of the technical details of this invention before the filing date or the priority date. It should be noted that modifications and improvements can be made by those skilled in the art without departing from the structure of the present invention, and these should also be considered as the scope of the present invention, which does not affect the effect of the implementation of the present invention and the utility of the patent. The protection scope of the present application shall be subject to the content of the claims, and the description of the specific embodiments and the like in the specification can be used for explaining the content of the claims.
Claims (4)
1. The business arrangement flow management system is characterized in that: the server comprises the following modules:
an initial creation module: the method comprises the steps of creating a FlowDefinition function, creating a business arrangement flow according to the FlowDefinition function, and packaging input and output of the business arrangement flow;
the flow creation module: the method comprises the steps of creating Definition functions, defining a business arrangement flow through the Definition functions and concrete business implementation contents;
the flow definition module: the method comprises the steps of creating a business process execution unit to define a business arrangement process, wherein the business process execution unit comprises a business start unit, a plurality of basic business logic units and an end business unit which are sequentially executed, and then giving specific business implementation contents of the business arrangement process of the basic business logic units; the basic service logic units are used for dividing specific service implementation contents into a plurality of sub-services, and the basic service logic units are used for defining service definitions of the sub-services and execution logic of the sub-services; when the basic service logic unit is created, service definition of sub-service and execution logic of the sub-service are completed through a Step interface and an Invoke interface of a SteoBuilder Step constructor;
the business starting unit is used for constructing a framework of a business arrangement flow, and the construction of the business starting unit is realized through a business starting construction module; and a service initiation construction module: the method comprises the steps of constructing a framework of a business arrangement flow through a Start function, and editing names of the business arrangement flow;
the basic service logic unit is constructed by a service content definition module and a service logic construction module;
the business content definition module: the method comprises the steps of creating a Step interface after framework construction is completed, and defining service definition of sub-services;
and a business logic construction module: the business definition method comprises the steps of creating Invoke interfaces after business definition is completed, inputting concrete expressions of sub-businesses, and constructing execution logic;
the flow construction module: and the method is used for calling the Build function to complete the construction of the whole business orchestration flow after the creation of the business flow execution unit is completed, so as to form an executable FlowDefinition function.
2. The business orchestration flow management system according to claim 1, wherein: the ending business unit is used for ending the business arrangement flow, and the construction of the ending business unit is realized through a business ending module;
and a service ending module: and the end function is called after the service logic is constructed and assembled, definition of the basic service logic unit is ended, logic construction is executed, and construction of the whole service orchestration flow is completed by calling the Build function.
3. The business arrangement flow management method is characterized in that: comprises the steps of,
s1, creating a FlowDefinition function, creating a business arrangement flow according to the FlowDefinition function, and packaging input and output of the business arrangement flow;
s2, creating Definition functions, and defining steps of a business arrangement flow and specific business implementation contents through the Definition functions;
s3, creating a business process execution unit to define a business arrangement process, wherein the business process execution unit comprises a business start unit, a plurality of basic business logic units and an end business unit which are sequentially executed, and then giving specific business implementation contents of the business arrangement process of the basic business logic units; the basic service logic units are used for dividing specific service implementation contents into a plurality of sub-services, and the basic service logic units are used for defining service definitions of the sub-services and execution logic of the sub-services; when the basic service logic unit is created, the service definition of the sub-service and the execution logic of the sub-service are completed through a Step interface and an Invoke interface of the SteoBuilder Step constructor;
in the step S3, the construction of the service initiation unit specifically includes the following steps:
s301, constructing a framework of a business arrangement flow through a Start function, and editing the name of the business arrangement flow;
the construction of the basic service logic unit specifically comprises the following steps:
s302, after framework construction is completed, creating a Step interface, and defining service definition of sub-services;
s303, after the service definition is completed, creating Invoke interfaces, inputting specific expressions of sub-services, and constructing execution logic;
and S4, after the creation of the business process execution unit is completed, calling a Build function to complete the construction of the whole business orchestration process, so as to form an executable FlowDefinition function.
4. A business orchestration flow management method according to claim 3, wherein: the machine purchasing body for ending the service unit in the step S3 specifically comprises the following steps:
s304, after the business logic is built, an end function is called, definition of a basic business logic unit is ended, logic building is executed, and building of the whole business arrangement flow is completed by calling a Build function.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010301322.5A CN111552459B (en) | 2020-04-16 | 2020-04-16 | Service arrangement flow management system and method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010301322.5A CN111552459B (en) | 2020-04-16 | 2020-04-16 | Service arrangement flow management system and method |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111552459A CN111552459A (en) | 2020-08-18 |
| CN111552459B true CN111552459B (en) | 2023-04-28 |
Family
ID=71998249
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010301322.5A Active CN111552459B (en) | 2020-04-16 | 2020-04-16 | Service arrangement flow management system and method |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111552459B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114356295B (en) * | 2021-12-24 | 2023-05-26 | 北京有竹居网络技术有限公司 | Three-dimensional model construction method and device and electronic equipment |
Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103513976A (en) * | 2012-06-29 | 2014-01-15 | 中兴通讯股份有限公司 | Service process modeling method and device |
Family Cites Families (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101739619B (en) * | 2010-01-04 | 2012-05-30 | 北京航空航天大学 | Method and device for establishing business process |
| US9904898B2 (en) * | 2010-03-05 | 2018-02-27 | Oracle International Corporation | Distributed order orchestration system with rules engine |
| US20140095361A1 (en) * | 2012-09-28 | 2014-04-03 | Oracle International Corporation | Supply chain financial orchestration system with trade accounting |
| CN110310034B (en) * | 2019-06-28 | 2022-06-07 | 京东科技控股股份有限公司 | Service arrangement and business flow processing method and device applied to SaaS |
| CN110442481B (en) * | 2019-07-10 | 2023-09-22 | 创新先进技术有限公司 | Service processing method, service component container and electronic equipment |
| CN110766375A (en) * | 2019-09-18 | 2020-02-07 | 武汉空心科技有限公司 | Work platform task construction system and construction method |
-
2020
- 2020-04-16 CN CN202010301322.5A patent/CN111552459B/en active Active
Patent Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103513976A (en) * | 2012-06-29 | 2014-01-15 | 中兴通讯股份有限公司 | Service process modeling method and device |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111552459A (en) | 2020-08-18 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN100487645C (en) | Automatically generating method based on data driving interface | |
| CN111488145B (en) | Micro-service code generation system and method based on service domain data model library | |
| KR100633478B1 (en) | System and its method for developing software based on business operating system | |
| CN101777004B (en) | Method and system for realizing BPEL sub-process multiplexing based on template in service-oriented environment | |
| CN110147225A (en) | A kind of code generating method, device and computer equipment, storage medium | |
| EP3367234A2 (en) | Systems and methods for arbitrary software logic modeling | |
| KR20050063402A (en) | Componentization method for re-engineering of legacy system | |
| CN110262794A (en) | A kind of AADL behaviour expanding method and tool based on specification with description language | |
| CN111813814A (en) | Universal model management method and device supporting multiple machine learning frameworks | |
| CN102455903B (en) | Method for generating user application interface | |
| CN111552459B (en) | Service arrangement flow management system and method | |
| CN105335161B (en) | It is a kind of from TASM time abstractions state machine to extension NTA automatic machines conversion method | |
| CN111176658B (en) | Automatic conversion method from AADL (architecture analysis and design language) to Simulink model based on meta-object mechanism | |
| CN111309378A (en) | Machine learning model life cycle management system and method | |
| Giachetti et al. | Integration of domain-specific modelling languages and UML through UML profile extension mechanism. | |
| CN115469860A (en) | Method and system for automatically generating demand-to-software field model based on instruction set | |
| CN112199075B (en) | Intelligent information processing method and framework system based on micro-service | |
| Gogolla et al. | On combining semi-formal and formal object specification techniques | |
| CN112817571B (en) | Man-machine object fusion application modeling method based on scene storyboard | |
| Ostadzadeh et al. | An MDA-based generic framework to address various aspects of enterprise architecture | |
| US20230418994A1 (en) | Method and system for modularized modeling of equipment entities in simulation field based on meta-model | |
| Sun et al. | Research on Application Ecological Architecture Technology of Digital Substation System | |
| Sunitha et al. | Translation of behavioral models to source code | |
| JP2551935B2 (en) | Graphical language processing method | |
| CN110532028B (en) | Method for generating interface document based on eclipse |
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 |