CN117270898A - Large software construction method, device and medium based on assembly - Google Patents

Large software construction method, device and medium based on assembly Download PDF

Info

Publication number
CN117270898A
CN117270898A CN202311566876.8A CN202311566876A CN117270898A CN 117270898 A CN117270898 A CN 117270898A CN 202311566876 A CN202311566876 A CN 202311566876A CN 117270898 A CN117270898 A CN 117270898A
Authority
CN
China
Prior art keywords
component
application
software
industry
determining
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.)
Granted
Application number
CN202311566876.8A
Other languages
Chinese (zh)
Other versions
CN117270898B (en
Inventor
徐同明
鹿海洋
魏代森
王思源
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Inspur General Software Co Ltd
Original Assignee
Inspur General Software Co Ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Inspur General Software Co Ltd filed Critical Inspur General Software Co Ltd
Priority to CN202311566876.8A priority Critical patent/CN117270898B/en
Publication of CN117270898A publication Critical patent/CN117270898A/en
Application granted granted Critical
Publication of CN117270898B publication Critical patent/CN117270898B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00Arrangements for software engineering
    • G06F8/60Software deployment
    • G06F8/61Installation

Abstract

The application discloses a large-scale software construction method, equipment and medium based on assembly, which relate to the field of electric digital data processing, wherein the method comprises the following steps: extracting and obtaining a common function and a variable function corresponding to the application scene based on the execution function in each application scene; determining the dimension corresponding to the basic element aiming at the commonality function, packaging to obtain an application service library and a pre-assembled service template library, and assembling to obtain standard application; obtaining a standard kernel corresponding to the large software; based on industry characteristics and personalized requirements corresponding to clients, obtaining corresponding expansion components; constructing an end-to-end flow corresponding to the large software; and constructing and obtaining large-scale software. The method for constructing the large software by the standard kernel and the extension component realizes the separation of the standard function and the extension function of the large software, reduces the operation and maintenance cost and the labor cost of software service providers and software use enterprises, and supports the flexible adjustment and optimization of the service function after the software delivery.

Description

Large software construction method, device and medium based on assembly
Technical Field
The application relates to the field of electric digital data processing, in particular to a large-scale software construction method, equipment and medium based on assembly.
Background
The traditional software deployment mode generally adopts a whole package deployment mode of packaged software, and meanwhile, a large number of nonstandard secondary development is required according to industry characteristics and individual requirements of clients. After the software is deployed, the operation and maintenance cost of software service providers and software use enterprises is high, quality problems such as downtime and the like of the software are difficult to be subjected to standardized investigation, the requirements on the number of operation and maintenance personnel and the capability are high, the problems such as difficulty in optimizing and adjusting the software caused by tight coupling are prominent, and the requirements on efficient and standardized delivery and flexible optimization are difficult to be ensured.
Meanwhile, secondary development work is often independently developed and completed by a small number of people, the dependency of related software logic on specific developers is strong, and a great deal of time is required to be input when maintenance personnel conduct quality check or software upgrading, so that unnecessary human resource waste is caused.
Disclosure of Invention
In order to solve the above problems, the present application proposes a large-scale software construction method based on assembly, including:
determining all application scenes corresponding to large software, determining corresponding execution functions in the application scenes according to each application scene, and refining and obtaining common functions and variable functions corresponding to the application scenes based on the execution functions in each application scene;
determining the corresponding basic element dimension of the common function, encapsulating the common function through a plurality of preset basic element dimensions to obtain an application service library and a pre-assembled service template library, and assembling the application service library and the pre-assembled service template library to obtain standard application;
obtaining a standard kernel corresponding to the large-scale software according to the basic element dimension, the application service library, the pre-assembled service template library and the standard application;
based on a plurality of component types which are preset according to the corresponding industry characteristics of each application scene and the corresponding personalized requirements of the clients, classifying and extracting the variable functions to obtain corresponding expansion components;
constructing an end-to-end flow corresponding to the large software based on an external input node or an external output node of the large software;
and assembling according to the standard kernel, the expansion assembly and the end-to-end flow, and constructing to obtain the large software.
In another aspect, the present application also proposes an assembly-based large software construction apparatus comprising:
at least one processor; the method comprises the steps of,
a memory communicatively coupled to the at least one processor; wherein,
the memory stores instructions executable by the at least one processor to enable the at least one processor to perform operations such as: the large software construction method based on assembly described in the above example.
In another aspect, the present application also proposes a non-volatile computer storage medium storing computer-executable instructions configured to: the large software construction method based on assembly described in the above example.
The large-scale software construction method based on assembly can bring the following beneficial effects:
the separation of the standard function and the extension function of the large software is realized by a large software construction method of the standard kernel and the extension component. The stable standard functions can be optimized through continuous precipitation of the standard kernel, flexible extended functions can be selectively assembled, excessive nonstandard secondary development of a software service provider in the software deployment process is reduced, the software quality stability, the standardization degree and the deployment efficiency are improved, the operation and maintenance cost and the labor cost of software service providers and software use enterprises are reduced, and flexible adjustment and optimization of service functions after software delivery are supported.
Drawings
The accompanying drawings, which are included to provide a further understanding of the application and are incorporated in and constitute a part of this application, illustrate embodiments of the application and together with the description serve to explain the application and do not constitute an undue limitation to the application. In the drawings:
FIG. 1 is a flow diagram of a method of building large software based on assembly in an embodiment of the present application;
FIG. 2 is a schematic diagram of a method of building large software based on assembly in one scenario in an embodiment of the present application;
FIG. 3 is a schematic diagram of an assembly-based large software construction device in an embodiment of the present application.
Detailed Description
For the purposes, technical solutions and advantages of the present application, the technical solutions of the present application will be clearly and completely described below with reference to specific embodiments of the present application and corresponding drawings. It will be apparent that the described embodiments are only some, but not all, of the embodiments of the present application. All other embodiments, which can be made by one of ordinary skill in the art without undue burden from the present disclosure, are within the scope of the present disclosure.
The following describes in detail the technical solutions provided by the embodiments of the present application with reference to the accompanying drawings.
As shown in fig. 1, an embodiment of the present application provides a large software construction method based on assembly, including:
s101: determining all application scenes corresponding to large software, determining corresponding execution functions in the application scenes according to each application scene, and refining and obtaining common functions and variable functions corresponding to the application scenes based on the execution functions in each application scene.
The application scene mainly comprises corresponding application industries and client requirements. Different services are typically involved in different application industries and may therefore need to perform different functions, e.g., using different devices, flows, computational models, etc.
The common function refers to a function which needs to be included in any application scenario, for example, the common function may be a function of a form control, a flow control, etc., and in any industry and any customer requirement, the form and the flow need to be controlled by the execution function.
Variable functionality refers to functionality that is not required in all industries in different application scenarios due to its industry characteristics or the personalized needs of the customer.
Based on this, all the execution functions in each application scenario are determined, among all the execution functions, the execution functions contained in the application scenario exceeding the preset proportion (for example, 95%) are used as the common functions corresponding to the application scenario, and the remaining execution functions are used as the variable functions corresponding to the application scenario.
S102: and aiming at the commonality function, determining the corresponding basic element dimension, packaging through a plurality of preset basic element dimensions to obtain an application service library and a pre-assembled service template library, and assembling through the application service library and the pre-assembled service template library to obtain standard application.
As shown in fig. 2, the base element dimension is used to adj ust the base element in multiple dimensions, including: technical components, business objects, domain models, business processes for describing commonality functions in different directions. And the application service library and the pre-assembled service template library can be obtained by encapsulation through the dimension of the basic element, the application service library can comprise corresponding services so as to support the realization of various functions in software, and the pre-assembled service template library comprises corresponding service templates, so that the service modules in the software can be quickly assembled and generated. And further assembling through the application service library and the pre-assembled business template library to obtain corresponding standard application (such as ERP standard application) serving as a sub-application in the large-scale software.
Wherein the technical components are used to describe components of the general technology, including: permission checking, log recording, form controls, flow controls, rule controls, help controls, and the like. A business object for describing components of a particular business, comprising: sales orders, project contracts, purchase orders, collaborative transactions, inventory vouchers, production orders, and the like. The domain model is used for describing components of industry domain features, and comprises: rolling budget models, inventory planning models, centralized purchasing models, unified talk and separate signature models, and the like. The business process is used for describing the process of the specific business, and comprises the following steps: item flow, planning flow, purchasing flow, checking flow, warehousing flow, etc.
S103: and obtaining a standard kernel corresponding to the large-scale software according to the basic element dimension, the application service library, the pre-assembled service template library and the standard application.
As shown in FIG. 2, the basic element dimension, the application service library, the pre-assembled service template library and the standard application are taken as three different granularities and are simultaneously incorporated into a standard kernel, free selection can be performed based on actual requirements in the subsequent large-scale software construction process, if the proper standard application exists, the standard application can be directly used, the packaging and assembly processes are omitted, and if the proper standard application does not exist, the basic element dimension or the application service library and the pre-assembled service template library with finer granularity can be selected for rapid packaging and assembly, so that the kernel construction is realized.
The standard kernel may be divided into multiple levels, so as to further divide the components contained therein (including basic element dimensions, application service libraries, pre-assembled business template libraries, and standard applications).
Specifically, for each component, it is determined whether it has a business attribute or an industry attribute.
If none of the software components is available, the component is considered to be the bottommost and most basic component, and the component is taken as the bottom standard kernel, so that almost all large software can be used for the component in the bottom standard kernel.
If the service attribute or the industry attribute is provided, the component part is considered to belong to the kernel, but still has a certain degree of commonality, the component part is used as an upper standard kernel, and most large software can use the component part in the upper standard kernel.
Further, in determining whether a component part contains a business attribute or an industry attribute, for each component part, when it is a basic element dimension, if it contains only a technology component, it can be considered that it does not have a business attribute or an industry attribute because it is a component describing a general technology. If the service library is an application service library or a pre-assembled service template library, and is only encapsulated by a technical component, the service attribute and the industry attribute can be considered to be absent without passing through other basic element dimensions. If the method is a standard application, and is only obtained by packaging and then assembling technical components, the method is not obtained by sequentially packaging and assembling other basic element dimensions, and the method can also be considered to have no business attribute and no industry attribute.
A component is considered to have business and/or industry properties when it is made up of multiple base element dimensions, i.e., includes other base element dimensions in addition to technical components.
Otherwise, the component has business or industry attributes. If it is a business object, business process, or is packaged or assembled from business objects, business processes, it is considered to have business attributes. If it is a domain model, or is assembled and packaged by a domain model, it is considered to have industry attributes.
S104: based on a plurality of component types which are preset according to the corresponding industry characteristics of each application scene and the corresponding personalized requirements of the clients, the variable functions are classified and extracted, and corresponding expansion components are obtained.
Different application scenarios have different industry characteristics or personalized requirements, for example, as shown in fig. 2, in a full-flow solution of a typical industry, for each industry such as aerospace industry, large-scale ship industry, engineering equipment industry, electric power equipment industry and the like, special industry equipment in the industry needs to be controlled, and the special industry equipment can be used as corresponding industry characteristics. The personalized requirements of the customer can include requirements on flow and operation interface in the control process of the equipment, and requirements on docking with different external platform data interfaces.
Based on the above, the corresponding expansion components are required to be configured for perfecting different industry characteristics and individuation requirements.
Specifically, determining a plurality of component types preset according to the industry characteristics corresponding to each application scene and the personalized requirements corresponding to the clients includes: industry components, intelligent components, data components, ecological components. At this time, the component type corresponding to the variable function may be determined, and the extension component corresponding to the variable function may be generated according to the component type.
Wherein, industry subassembly is used for embodying industry characteristic's extension subassembly, includes: quality return components in the aerospace field, sub-packaging management components in the engineering equipment field, outfitting process components in the large ship field, high-voltage detection components in the electric power equipment field and the like. The intelligent subassembly is used for embodying intelligent extension subassembly, includes: digital employee components, intelligent invoice auditing, behavior recognition, intelligent scheduling and the like. The data component is used for embodying the expansion component of each scene data analysis capability, and comprises: inventory forecasting, investment forecasting, cost analysis, asset analysis, generation analysis, sales forecasting, vendor valuation, and the like. The ecological component is used for reflecting an open source and an integrated extension component and supporting the access of an external component, and comprises: supervision integration, bank-enterprise direct connection, e-commerce system integration, tax system integration and the like.
S105: and constructing an end-to-end flow corresponding to the large software based on the external input node or the external output node of the large software.
One end in an end-to-end flow refers to an external input node or external output node, which may include customer nodes, market nodes, third party authority nodes (e.g., third party regulatory authorities, third party detection authorities, etc.), benefit-related nodes (e.g., data providing nodes, collaboration nodes, etc.), and the like.
While the end-to-end process refers to a process template required for the large software to communicate with other nodes, as shown in fig. 2, it may include: marketing to collection, source to payment, cost to expenditure, investment to operation, etc., and according to the end-to-end flow, the establishment of the data interaction channel between the ends is rapidly completed.
S106: and assembling according to the standard kernel, the expansion assembly and the end-to-end flow, and constructing to obtain the large software.
In the above process, the standard kernel, the extension component and the end-to-end flow are established and stored. When the construction requirement of the large-scale software exists, the content in the large-scale software can be taken out for constructing the large-scale software.
As shown in fig. 2, when large-scale software is built, at least part of the large-scale software needs to be selected from standard kernels to be used as kernel components of the large-scale software, and then required extension components and required end-to-end flow are determined based on industry characteristics corresponding to the current application scene and personalized requirements corresponding to clients, and the large-scale software is obtained through assembly.
For large software, the content of the standard kernel is almost necessary, while the content of the extension component is not necessary, but is selected based on own needs. Of course, after the large-scale software is built, if the service adjustment is performed later or the external environment change is generated, the expansion assembly or the end-to-end flow can be respectively recombined at any time.
In addition, as shown in fig. 2, in the assembly process of the large-scale software, the support provided by the assembly support platform is required, for example, the support platform provides corresponding support for assembly rules, assembly tools, assembly technology and integration interfaces, so that the assembly of the large-scale software is completed.
The separation of the standard function and the extension function of the large software is realized by a large software construction method of the standard kernel and the extension component. The stable standard functions can be optimized through continuous precipitation of the standard kernel, flexible extended functions can be selectively assembled, excessive nonstandard secondary development of a software service provider in the software deployment process is reduced, the software quality stability, the standardization degree and the deployment efficiency are improved, the operation and maintenance cost and the labor cost of software service providers and software use enterprises are reduced, and flexible adjustment and optimization of service functions after software delivery are supported.
As shown in fig. 3, the embodiment of the present application further proposes a large-scale software construction apparatus based on assembly, including:
at least one processor; the method comprises the steps of,
a memory communicatively coupled to the at least one processor; wherein,
the memory stores instructions executable by the at least one processor to enable the at least one processor to perform operations such as: the method of large software construction based on assembly of any of the embodiments described above.
The embodiments of the present application also provide a non-volatile computer storage medium storing computer executable instructions configured to: the method of large software construction based on assembly of any of the embodiments described above.
All embodiments in the application are described in a progressive manner, and identical and similar parts of all embodiments are mutually referred, so that each embodiment mainly describes differences from other embodiments. In particular, for the apparatus and medium embodiments, the description is relatively simple, as it is substantially similar to the method embodiments, with reference to the section of the method embodiments being relevant.
The devices and media provided in the embodiments of the present application are in one-to-one correspondence with the methods, so that the devices and media also have similar beneficial technical effects as the corresponding methods, and since the beneficial technical effects of the methods have been described in detail above, the beneficial technical effects of the devices and media are not described in detail herein.
It will be appreciated by those skilled in the art that embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the application. It will be understood that each flow and/or block of the flowchart illustrations and/or block diagrams, and combinations of flows and/or blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
In one typical configuration, a computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.
The memory may include volatile memory in a computer-readable medium, random Access Memory (RAM) and/or nonvolatile memory, such as Read Only Memory (ROM) or flash memory (flash RAM). Memory is an example of computer-readable media.
Computer readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of storage media for a computer include, but are not limited to, phase change memory (PRAM), static Random Access Memory (SRAM), dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), read Only Memory (ROM), electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices, or any other non-transmission medium, which can be used to store information that can be accessed by a computing device. Computer-readable media, as defined herein, does not include transitory computer-readable media (transmission media), such as modulated data signals and carrier waves.
It should also be noted that the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one … …" does not exclude the presence of other like elements in a process, method, article or apparatus that comprises the element.
The foregoing is merely exemplary of the present application and is not intended to limit the present application. Various modifications and changes may be made to the present application by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc. which are within the spirit and principles of the present application are intended to be included within the scope of the claims of the present application.

Claims (10)

1. A method of large software construction based on assembly, comprising:
determining all application scenes corresponding to large software, determining corresponding execution functions in the application scenes according to each application scene, and refining and obtaining common functions and variable functions corresponding to the application scenes based on the execution functions in each application scene;
determining the corresponding basic element dimension of the common function, encapsulating the common function through a plurality of preset basic element dimensions to obtain an application service library and a pre-assembled service template library, and assembling the application service library and the pre-assembled service template library to obtain standard application;
obtaining a standard kernel corresponding to the large-scale software according to the basic element dimension, the application service library, the pre-assembled service template library and the standard application;
based on a plurality of component types which are preset according to the corresponding industry characteristics of each application scene and the corresponding personalized requirements of the clients, classifying and extracting the variable functions to obtain corresponding expansion components;
constructing an end-to-end flow corresponding to the large software based on an external input node or an external output node of the large software;
and assembling according to the standard kernel, the expansion assembly and the end-to-end flow, and constructing to obtain the large software.
2. The method according to claim 1, wherein the extracting and obtaining the common function and the variable function corresponding to each application scene based on the execution function in each application scene specifically comprises:
determining execution functions in each application scene;
among all the execution functions, the execution functions contained in the application scenes exceeding the preset proportion are used as common functions corresponding to the application scenes, and the rest execution functions are used as variable functions corresponding to the application scenes.
3. Method according to claim 1, characterized in that for the commonality function, determining its correspondence to a base element dimension, in particular comprises:
determining a plurality of preset basic element dimensions, and determining corresponding basic element dimensions aiming at the commonality function;
wherein the base element dimension comprises: technical components, business objects, domain models, and business processes;
the technical component is used for describing the component of the general technology and comprises the following components: at least one of permission checking, log recording, form control, flow control, rule control and help control;
the service object is used for describing components of a specific service, and comprises: at least one of a sales order, a project contract, a purchase order, a collaborative transaction, an inventory voucher, and a production order;
the domain model is used for describing components of industry domain features, and comprises: at least one of a rolling budget model, an inventory planning model, a centralized purchasing model and a unified talking and signing model;
the business process is used for describing the process of a specific business, and comprises the following steps: at least one of standing flow, planning flow, purchasing flow, checking flow and warehousing flow.
4. The method of claim 3, wherein obtaining the standard kernel corresponding to the large software according to the basic element dimension, the application service library, the pre-assembled service template library and the standard application specifically comprises:
determining, for each component, whether it has a business attribute or an industry attribute; the component part comprises at least one of the basic element dimension, the application service library, the pre-assembled business template library and the standard application;
if not, taking the component part as a bottom standard kernel;
and if the business attribute or the industry attribute is provided, the component is used as an upper standard kernel.
5. The method according to claim 4, wherein determining for each component whether it has a business attribute or an industry attribute, comprises:
for each component, if the component only comprises the technical component, or is encapsulated by the technical component, or is assembled by the technical component, determining that the component does not have business attributes and industry attributes;
otherwise, determining that the component has business attributes or industry attributes.
6. The method according to claim 1, wherein the classifying and extracting the variable function based on a plurality of component types set in advance according to industry characteristics corresponding to each application scenario and personalized requirements corresponding to clients, to obtain corresponding extension components, specifically includes:
the determining of the multiple component types preset according to the industry characteristics corresponding to each application scene and the personalized requirements corresponding to the clients comprises the following steps: industry components, intelligent components, data components, ecological components;
determining the component type corresponding to the variable function, and obtaining an expansion component corresponding to the variable function according to the component type;
the industry component is used for embodying an expansion component of the industry characteristics, and comprises: at least one of a quality return component in the aerospace field, a sub-packaging management component in the engineering equipment field, an outfitting process component in the large ship field and a high-voltage detection component in the electric power equipment field;
the intelligent component is used for embodying an intelligent extension component and comprises: at least one of digital employee components, intelligent invoice auditing, behavior recognition and intelligent scheduling;
the data component is used for embodying expansion components of each scene data analysis capability, and comprises: at least one of inventory forecasting, investment forecasting, cost analyzing, asset analyzing, generation analyzing, sales forecasting, and supplier evaluating;
the ecological component is used for reflecting an open source and integrated expansion component and supporting the access of an external component, and comprises: at least one of supervision integration, bank-enterprise direct connection, e-commerce system integration and tax system integration.
7. The method of claim 1, wherein the end-to-end flow comprises: at least one of marketing to collection, sourcing to payment, cost to expenditure, investment to operation;
the external input node and the external output node include: at least one of a customer node, a market node, a third party authority node, and a benefit-related node.
8. The method according to claim 1, wherein the large software is built by assembling the standard kernel, the extension component and the end-to-end process, and specifically comprises:
selecting at least one part of the standard kernel as a kernel component of large-scale software;
based on the industry characteristics corresponding to the current application scene and the personalized requirements corresponding to the clients, determining the required expansion components and the required end-to-end flow, and assembling to obtain the large-scale software;
and respectively reorganizing the expansion assembly or the end-to-end flow based on subsequent business adjustment or external environment change.
9. An assembly-based large software construction apparatus, comprising:
at least one processor; the method comprises the steps of,
a memory communicatively coupled to the at least one processor; wherein,
the memory stores instructions executable by the at least one processor to enable the at least one processor to perform operations such as: an assembly-based large software construction method as claimed in any one of claims 1 to 8.
10. A non-transitory computer storage medium storing computer-executable instructions, the computer-executable instructions configured to: an assembly-based large software construction method as claimed in any one of claims 1 to 8.
CN202311566876.8A 2023-11-23 2023-11-23 Large software construction method, device and medium based on assembly Active CN117270898B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202311566876.8A CN117270898B (en) 2023-11-23 2023-11-23 Large software construction method, device and medium based on assembly

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202311566876.8A CN117270898B (en) 2023-11-23 2023-11-23 Large software construction method, device and medium based on assembly

Publications (2)

Publication Number Publication Date
CN117270898A true CN117270898A (en) 2023-12-22
CN117270898B CN117270898B (en) 2024-02-20

Family

ID=89203079

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202311566876.8A Active CN117270898B (en) 2023-11-23 2023-11-23 Large software construction method, device and medium based on assembly

Country Status (1)

Country Link
CN (1) CN117270898B (en)

Citations (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2002163106A (en) * 2000-11-24 2002-06-07 Mitsui Mining & Smelting Co Ltd Basic business integrated application system, basic business support method, and computer readable storage medium storing program executing the method on computer
US20030167234A1 (en) * 2002-03-01 2003-09-04 Lightsurf Technologies, Inc. System providing methods for dynamic customization and personalization of user interface
US20050149558A1 (en) * 2003-12-26 2005-07-07 Yefim Zhuk Knowledge-Driven Architecture
US20100023920A1 (en) * 2008-07-22 2010-01-28 International Business Machines Corporation Intelligent job artifact set analyzer, optimizer and re-constructor
CN101706738A (en) * 2009-10-29 2010-05-12 中国联合网络通信集团有限公司 Flow application system
CN102332123A (en) * 2011-10-24 2012-01-25 北京派得伟业科技发展有限公司 Method for constructing agriculture intelligent system development platform based on domestic basic software
CN102622675A (en) * 2012-03-14 2012-08-01 浙江大学 Method and system for realizing interoperation of enterprises under cluster supply chain environment
CN110851114A (en) * 2019-10-24 2020-02-28 山东中创软件工程股份有限公司 Business system development method and device, electronic equipment and storage medium
CN112416571A (en) * 2020-10-19 2021-02-26 杭州未名信科科技有限公司 Resource management method, operating system and management device for industrial Internet of things nodes
CN114879939A (en) * 2022-04-27 2022-08-09 深圳市惟客数据科技有限公司 Method, system, electronic device and storage medium for generating micro service

Patent Citations (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2002163106A (en) * 2000-11-24 2002-06-07 Mitsui Mining & Smelting Co Ltd Basic business integrated application system, basic business support method, and computer readable storage medium storing program executing the method on computer
US20030167234A1 (en) * 2002-03-01 2003-09-04 Lightsurf Technologies, Inc. System providing methods for dynamic customization and personalization of user interface
US20050149558A1 (en) * 2003-12-26 2005-07-07 Yefim Zhuk Knowledge-Driven Architecture
US20100023920A1 (en) * 2008-07-22 2010-01-28 International Business Machines Corporation Intelligent job artifact set analyzer, optimizer and re-constructor
CN101706738A (en) * 2009-10-29 2010-05-12 中国联合网络通信集团有限公司 Flow application system
CN102332123A (en) * 2011-10-24 2012-01-25 北京派得伟业科技发展有限公司 Method for constructing agriculture intelligent system development platform based on domestic basic software
CN102622675A (en) * 2012-03-14 2012-08-01 浙江大学 Method and system for realizing interoperation of enterprises under cluster supply chain environment
CN110851114A (en) * 2019-10-24 2020-02-28 山东中创软件工程股份有限公司 Business system development method and device, electronic equipment and storage medium
CN112416571A (en) * 2020-10-19 2021-02-26 杭州未名信科科技有限公司 Resource management method, operating system and management device for industrial Internet of things nodes
CN114879939A (en) * 2022-04-27 2022-08-09 深圳市惟客数据科技有限公司 Method, system, electronic device and storage medium for generating micro service

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
朱翠丽;谢益武;: "面向特征的领域建模方法研究与应用", 计算机技术与发展, no. 11 *
陈华光;: "基于微内核架构的业务基础平台设计", 电子世界, no. 17 *

Also Published As

Publication number Publication date
CN117270898B (en) 2024-02-20

Similar Documents

Publication Publication Date Title
US11823072B2 (en) Customer behavior predictive modeling
WO2009126280A1 (en) Infrastructure and architecture for development and execution of predictive models
CN110222104A (en) Data extraction method, equipment and storage medium
CN110766545A (en) Bank accounting entry generation method
KR20210114224A (en) System for providing demand and supply matching service of appratus and part for win-win partnership and cooperation between manufacturers
Kolb et al. Industrial application of blockchain technology–erasing the weaknesses of vendor managed inventory
da Silva et al. SPReaD: service-oriented process for reengineering and DevOps: Developing microservices for a Brazilian state department of taxation
CN115878092A (en) Code generation method, device and medium based on micro-service architecture
US20100122258A1 (en) Versioning and effectivity dates for orchestration business process design
CN103186384A (en) Business-component-oriented software designing and analyzing system and using method thereof
CN117270898B (en) Large software construction method, device and medium based on assembly
Deng et al. Computational operations research exchange (core): A cyber-infrastructure for analytics
CN112631763A (en) Program changing method and device of host program
Psyrris et al. MNOs business models and roles enabled by 5G technologies and use cases: Transformation, challenges and strategies
CN116993519A (en) Bill generation method and device
CN114327376A (en) IT architecture establishing method, IT architecture establishing device, processor and electronic equipment
US10509659B1 (en) Input processing logic to produce outputs for downstream systems using configurations
Bhagavan et al. C3HSB: A transparent supply chain for multi-cloud and hybrid cloud assets powered by blockchain
Matejaš et al. Building a BPM application in an SOA-based legacy environment
Panduwiyasa et al. Performance evaluation of ERP based to ISO/IEC 25010: 2011 quality model (a case study)
Czwalina et al. Processes in a Digital Environment
Schuh et al. Design of an integrated model for the real-time disturbance management in transportation supply networks
CN113052675B (en) Data display method and device
Seth et al. Testing and evaluation of service oriented systems
US20240070354A1 (en) System and methods for auditable corporate emission balancing

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