CN101533349B - Platform-related model of large-granularity components and method of automatic code generation thereof - Google Patents

Abstract

The invention relates to a method for automatically generating codes of a platform-related model of a large-grained component, and the invention relates to a model-driven enterprise application software development method. It solves the defects of the current lack of a systematic and specific large-grained business component modeling method and the lack of flexibility and variability of software generated by the prior art. It is realized through the following steps: abstract the typical software patterns of multiple business components from the existing software with the same business content, and obtain the non-instantiated component text based on the pattern; from the obtained business components Select the software model from the typical software model, and establish the platform-related model of the business component based on the specific software model; automatically generate the platform-related model of the business component into a dry business component program; instantiate the dry business component into a reusable business for specific requirements The component program generates the final source program code; in the final software system, the business component dynamically adapts to the business needs of the enterprise by parsing the configuration file.

Description

A method for automatic code generation of platform-dependent models of large-grained components

technical field

The invention relates to a model-driven enterprise application software development method, in particular to a software development method based on a large-grained component platform-related model, which belongs to the field of information technology.

Background technique

In the face of fierce market competition around the world, enterprises always continue to improve their business models to enhance their own competitiveness, and enterprise management software must also be able to quickly and effectively adapt to changing business needs. However, the current enterprise application software has problems such as high research and development costs, high implementation costs, and long implementation cycles, which seriously hinder the rapid and low-cost development of componentized software systems with on-demand capabilities.

Model-driven software architecture (Model Driven Architecture, MDA) and software development are considered to be an effective way to develop such software. The goal of MDA is to achieve the implementability, interoperability and reusability of different levels of complex abstract systems through the structural separation of concerns, decompose the development of large software systems into different levels, divide and conquer, and reduce the overall system design. The difficulty of development effectively improves the success of complex system development. The basic idea of MDA is to separate the requirements and function specifications of the system from their implementation specifications on a specific technology platform, and respectively establish a computing-independent model describing business requirements, a platform-independent model describing software system design schemes, and a platform describing specific implementation mechanisms. The relevant model (Platform Specific Model, PSM) realizes layer-by-layer refinement and automatic generation of software systems through the mapping and conversion of model elements at each level. Modeling and model conversion are the two core issues of MDA research. The platform-dependent model PSM needs to undertake software design content and convert it into a system implementation model on a specific operating platform. Downward, it is the basis for model conversion and automatic code generation. Its correctness and optimization degree determine the performance of the software.

Model-driven software development can only be realized on the basis of relatively mature code generation technology. The purpose of the code generator is to use computer programs to write computer programs, and code generation is one of the effective means to improve the efficiency of software development. The original purpose is to generate assembly code and machine instructions after compiling from a high-level language, and it is an indispensable tool for language conversion and compilation. Code generation research has always focused on code compilation. The early code generator based on the Graham-Glanville method replaced the C language compiler, and output the generated code through pattern matching by constructing a table describing the target code. Later, code generation technology was introduced into the field of software development based on high-level languages, supporting the generation of executable code from visual models. The types of code generation can be classified into the following forms: code remodeling, inline code expansion, mixed code generation, partial class generation, hierarchical generation, and domain-wide language description. With the development of model-driven architecture technology, code generation technology is widely used in the development of enterprise application software, which supports automatic conversion from platform-dependent models to executable code. Among them, by patterning the commonality of components to improve their abstraction and reusability, the code generation method based on patterns can effectively improve the conversion efficiency and correctness of PSM models to codes. In the long-term software development and application process, people have abstracted a variety of software patterns, such as Client/Server pattern in software architecture, multi-layer structure pattern, MVC, pipeline filter, etc.; software development is divided into issues based on conceptual model specification Domain, based on the design domain of the design pattern and the solution space to realize the conceptual pattern, use the design pattern to guide the generation of the conceptual model to the service program; or establish a flexible code generator based on XML schema to generate a distributed system; or based on XSLT and Velocity template The engine implements the transformation from business model to program.

Although, the MDA idea has changed the traditional software development process, liberated software developers from complicated programming, promoted it to be model-centered, carried out model construction, transformation and refinement, and developed the system through automatic code generation. However, there is still a lack of a systematic and specific enterprise application software modeling method to guide specific software development. Moreover, the existing code generation schemes and tools also have the disadvantages of poor scalability and integration. The programs generated by most code generators lack flexibility. Once the code is generated, it is difficult for users to change its structure and style. Generation tools are difficult to be widely used, leading users to design and develop specific code generation tools according to their own models.

Contents of the invention

The purpose of the present invention is to provide a method for automatic code generation of a platform-dependent model of a large-grained component to solve the lack of a systematic and specific enterprise application software modeling method and the lack of flexibility and reliability of the software generated by the prior art. Transgender flaws. It is realized through the following steps: 1. Abstract the typical software patterns of multiple business components from the existing software with the same business content, and obtain the non-instantiated component text based on the pattern; 2. Build Modeling stage: select the software pattern from the typical software patterns of multiple business components obtained in step 1, so as to obtain the platform-related model of the business component; 3. Development stage: automatically generate the platform-related model of the business component into a dry business component program ; 4. Deployment stage: Instantiate the dry business component into a reused business component program for specific requirements, thereby generating the final source program code; in the final software system, the reused business component dynamically adapts to the business of the enterprise by parsing the configuration file need. There are three ways to adapt to the changing needs of the enterprise: one way, when the business changes reflect the related needs of permissions or personalization, adjust the deployment configuration file or personalization configuration file information through dynamic configuration to realize the business components. Reuse and adjustment of software functions. The second way is that when the business change cannot be satisfied by dynamic configuration, the component program can be partially modified to realize the adaptation and reuse of the business component. The third way, when the business changes significantly and the above two ways are not applicable, the new software business needs can be met by re-establishing the large-grained component model and regenerating it into a new business component;

The business component model is multi-generated into dry business components and reused business components in stages during the development and deployment process; in the development phase, the above model is input into the code generator, and the non-instantiated components that match the pattern are instantiated into the model Describe the executable program of the consistent dry business component; in the deployment phase, the system automatic deployment tool reads the deployment requirements and derives the dry business component into multiple instance components.

The software system generated based on this method has the ability to adapt to the ever-changing business needs of the enterprise. There are three ways to adapt to the changing needs of the enterprise: one way, when the business changes reflect the relevant needs of authority or individualization, through dynamic configuration Adjust deployment configuration file or personalization configuration file information to achieve reuse of business components and adjustment of software functions. The second way is that when the business change cannot be satisfied by dynamic configuration, the component program can be partially modified to realize the adaptation and reuse of the business component. The third way is that when the business changes greatly and the above two ways are not applicable, the new software business needs can be met by re-establishing the large-grained component model and regenerating it into a new business component. Therefore, the defects of lack of flexibility and variability of programs generated by the prior art are solved. The invention decomposes the adaptability of software into multiple stages for realization, ensuring efficient and rapid component development and reuse.

Description of drawings

Fig. 1 is a flowchart of the present invention; Fig. 2 is a schematic diagram of a business component software model structure tree of the present invention; Fig. 3 is a schematic diagram of a platform-related model of a large-grained business component of the present invention; Fig. 4 is a pattern-based large-grained component of the present invention Working principle diagram of the code generator; FIG. 5 is an implementation diagram of an embodiment of the present invention.

Detailed ways

Specific Embodiment 1: The present embodiment will be specifically described below with reference to FIG. 1 . This embodiment is realized by the following steps: 1. Abstract the typical software patterns of several business components from the existing multiple software with the same business content, and obtain the non-instantiated component text based on the pattern; 2. 1. Modeling stage: Select the software model from the typical software models of multiple business components obtained in step 1, so as to obtain the platform-related model of the business component; 3. Development stage: Automatically generate the platform-related model of the business component as a dry business Component program; 4. Deployment stage: Instantiate the dry business component into a reused business component program for specific requirements, thereby generating the final source program code; reuse the business component in the final software system to dynamically adapt to the enterprise by parsing the configuration file business needs.

The generation, characteristics and classification methods of business components in this embodiment are described in detail below:

(1) Through the analysis of the existing enterprise application software, a kind of large-grained modular component with business document data as the attribute set and document processing as the operation set is summarized. Patterned large-grained components are relative to small-grained components, which refer to basic elements that can be clearly identified in application software and cannot be subdivided, such as text boxes, drop-down list boxes, and radio buttons. Basic controls, which are business-agnostic. A component with business semantic integrity is assembled from several small-grained components and their associated processes according to the needs of users, which is called a Business Component.

(2) Business components follow typical software patterns, and have unique identifiers, stable attributes and operations, and relatively variable attributes and operations.

(3) Business components are divided into two types: stem business components and reuse business components. Stem business components (StemBusiness Component) refer to the complete set of attributes and operations included. Reused Business Component (ReusedBusiness Component) is a component after changing the variable features in dry business components into fixed features.

The business component is a software component realization result of a business object processed in the production and operation process of an enterprise, including object data information and related business activities, and is a patterned large-grained component with complete business semantics.

Business components are divided into dry business components parameterized by attribute operations and reusable business components instantiated according to requirements according to different concerns of their life cycle stages. The dry business component is a complete set of functions within the category of business documents, and the reusable business component is a subset of functions derived from the dry business component.

The business component model is multi-generated into dry business components and reused business components in stages during the development and deployment process. In the development stage, the above model is input into the code generator, and the non-instantiated components matching the pattern are instantiated into executable programs of dry business components consistent with the model description. In the deployment phase, the automatic deployment tool of the system reads the deployment requirements and derives the main business components into several instance components.

Specific Embodiment 2: The present embodiment will be specifically described below with reference to FIG. 2 . The difference between this embodiment and Embodiment 1 is that the relevant model of the business component platform obtained in step 2 uses a source code-level schema description language to define the user schema and implementation schema of the business component on the J2EE platform, wherein the schema description language is universal , can be applied to a variety of software patterns that can be realized by high-level programming languages. The expression methods include:

i, software pattern classification method, software patterns are divided into user-oriented user pattern (UserPattern, UP) and software-oriented realization pattern (Realization Pattern, RP) two categories. The user mode is reflected in the interaction style between software and client users, and the implementation mode is an implementation scheme or operating mechanism from the perspective of software development. The former is the external performance of the latter, and the latter is the technical support of the former.

ii. Realization Pattern Description Language (RPDL) at the source code level, which is defined as: <RPDL>::=<static code>|<dynamic code><dynamic code to static code conversion rule>

<static code>::=<content described in target programming language>

<Dynamic code>::=<Dynamic variable start character> <Dynamic variable to be instantiated> <Dynamic variable end character>

<dynamic variable to be instantiated>::=<variable defined in programming language A>

<Conversion rule from dynamic code to static code>::=<start character of conversion rule><content of conversion rule based on A><end character of conversion rule>

Specific Embodiment Three: The present embodiment will be specifically described below in conjunction with FIG. 3 . The difference between this embodiment and embodiment one is: the business component platform-related model obtained in step 2 is expressed by the following method: this method is a business component PSM model expression method based on the J2EE platform (well known in the art) , the method includes the following steps:

i. Taking the Brown model (well known in the art) as the layered architecture model of the business component, it is determined that the component is composed of several kinds of small-grained components and the assembly of connectors. The medium-grained components of each level are interconnected by external connectors, and each level is assembled into medium-grained components by internal connectors.

ii. Based on the above determined architecture, select a series of relevant software sub-patterns and assembly sub-patterns as the basis for business component realization. Establish the implementation model of business components for each architectural level. Establish the presentation layer component specification, the application control layer component specification, the business logic layer component specification, the relational object layer component specification and the data source layer specification in sequence, as well as the mapping and association relationship between these layers, and complete a complete business component model description.

Specific Embodiment 4: The present embodiment will be specifically described below with reference to FIG. 4 . The difference between this embodiment and Embodiment 1 is that step 3 and step 4 are realized by a pattern-based phased code generation method, and the specific step 3 is:

The generality of business components is abstracted into patterns, and non-instantiated components (templates) are defined based on the patterns, and those individual contents oriented to business semantics are described as business component models. There is a type-value relationship between schema-based non-instantiated components and models, the former provides a syntax-based description of component types, and the latter provides a description of component values oriented to business semantics. In the development stage, the two parts are fused through the code generator, and a specific business component can be converted.

The specific step four is: the deployment phase goes through two main steps: the first step is to configure the dry business components related to permissions to become executable multiplexed business components. The business component configuration file can implement the reuse mechanism of dry business components in two ways: dynamic or fixed. Dynamic acquisition of configuration information refers to reading the content of the configuration file during each operation of the business component, parsing and automatically reorganizing the internal business logic of the component based on its content to achieve reuse. Fixing configuration information refers to writing configuration information into a copy of dry business components, and generating dedicated reused business components for each user or role. The second step is to install and deploy the reused business components to the actual system operating environment. The workflow engine in the enterprise application software based on business components dynamically assembles and reuses business components under the control of the executable workflow model to provide different services for different users.

Fifth specific embodiment: The present embodiment will be specifically described below in conjunction with FIG. 5 . The technical solution of the present invention is described in detail.

The core idea of the present invention is to decompose the variability of software into each stage of software development, and implement software in each stage according to different concerns. In the business component modeling phase, the business component PSM model is established according to the business function requirements. In the development phase, the source-level non-instantiated component template is instantiated into a dry business component. In the deployment phase, the dry business component is further derived for specific requirements. Reuse business components. This method visually describes the component implementation model and converts it into code, thereby accelerating the model-scale and large-scale automatic development of software.

Referring to Figure 1, firstly, software developers establish a business component platform-related model expressing business functions on the basis of a specific software model; input the model into a code generator, and convert it into an executable program of dry business components; then, the deployment stage is oriented to specific users Requirements fully instantiate dry business components into reusable business components. The present invention is described in detail by taking the business component development process based on the J2EE application server as an example.

Referring to Figure 2, at the software appearance level, the user mode describes the external characteristics of the software from two aspects: the structure of the user interface and the flow of user operations. At the level of software implementation, the implementation pattern describes the implementation of components according to each level of the layered architecture and the relationship between them. Patterns that implement parent nodes are called child patterns. The business component pattern is an integration composed of a series of sub-patterns (user sub-pattern and implementation sub-pattern). There is an inclusion relationship between the parent pattern and the sub-pattern, and the two implementation sub-patterns need to be associated according to the interface pattern.

A source code-level implementation pattern description language RPDL (request the inventor to translate or explain Realization Pattern Description Language, RPDL) guides the development of business components from the perspective of code implementation. For example, the implementation sub-pattern description of data items in the presentation layer is shown in Table 1. Table 1 is about the code description of the JSP (ask the inventor to translate or explain) interface to display multiple data items in the form of a cell, and this fragment is from (2) to (5) lines that adopt the conversion rule content defined by the JAVA language , its main function is to perform initial assignment to the dynamic code delimited by <# and #> in line (7). Line (5) is the core function of this mode, which means that the code in line (7) will iteratively appear multiple times according to the data source cardinality, and the dynamic code will be instantiated into different static code values each time it appears.

Table 1

A business component is formed by assembling several small-grained components through internal or external connections. Thus, the business component PSM model is composed of a unique identifier, a selected component mode, a core model based on a layered structure, a configuration model for supporting variability, and an external interface model, see Figure 3. The presentation layer is an interface for direct interaction between business components and users. A business component is always composed of several interrelated user interfaces, providing users with services such as submitting requests and feedback processing results. There is a mutual call or a general link relationship among various user interfaces. The business logic layer is the core logic program that responds to and processes the user needs of the client. The implementation pattern of the business logic layer based on the J2EE platform can be expressed as: it consists of several packages and classes, among which the method implementation of routine operations can be automatically generated and acquired by the code generator according to the pattern definition, and stored in the default class file; The methods manually developed by the programmer under the constraints of the extension mechanism are stored in the extension class file; the core control class is responsible for its service arrangement and method call. The data layer model is an out-of-database model that describes business components in relational data mode, and describes the mapping relationship between the data view processed by the component business logic layer and the data view in the actual database.

The basic principle of the code generation process is as follows, input: business component model X based on a certain pattern; output: business component code. The content is as follows: (1) Analyze the pattern identification of the business component model, retrieve and obtain it in the pattern library The non-instantiated component of the corresponding mode; (2) scan the content of the non-instantiated component, and when a dynamic code is found, retrieve the corresponding data in X for code conversion; (3) repeat (1) until the non-instantiated component Until there is no dynamic code, go to (4); (4) print the final component code. Refer to Figure 4 for the working principle of the code generator, which adopts a pattern-based hybrid code generation method. Every time the code generator is started, a "tailor-made" code writer for the specified business component must be constructed inside it. The code writer uses the standard output stream "PrintWriter Out" in JAVA, and passes the Println of the Out object. (ask the inventor to translate or explain) the method realizes printing characters in the target file.

The business component life cycle is divided into stages, and the stage is mapped layer by layer, and the configuration scheme of layer grouping is shown in Figure 5. After three necessary stages of development, deployment and application. In each stage, the attributes of components that software developers pay attention to are different. In the development phase, the developer will focus on defining the fixed parts of the component according to the user's business needs, such as the constituent elements of the data set and the operation set, the life cycle state set that the corresponding business object must go through, the interface style, and the operation mode, etc.; and the deployment and the application phase, more focus on the realization of the variable part in the component, where the properties related to permissions and the properties used to meet individual needs can be instantiated in the deployment and application phases.

In the above-mentioned process of business component modeling, code generation and deployment configuration, the business component model is realized through the visual modeling tool, the business component model is converted into the dry business component code through the code generator, and the system deployment tool realizes that the dry business component is derived as Reuse component code.

Finally, it should also be noted that what is listed above is only a specific embodiment of the present invention. Obviously, the present invention is not limited to the above embodiments, and there are many variations. All deformations that can be directly derived or conceived by those skilled in the art from the content disclosed in the present invention should be considered as the protection scope of the present invention.

This large-grained component (also known as business component) provides a pattern-based way to establish a business component implementation model on the J2EE platform, and the pattern-based code generation method provides a universal and extensible code generation mechanism According to the characteristics in each stage of the life cycle of business components, it is divided into two types of components: dry business components and reused business components. The code generator constructed based on this generation mechanism can quickly obtain the initial instantiated dry business component program by reading the complete business component PSM model built by the user. During the deployment process of the component, it can be further fully instantiated into Reusable business components for specific user needs.

Claims (7)

1. A method for automatic code generation of a platform-dependent model of a large-grained component, characterized in that it is realized through the following steps: 1. From existing, multiple software with the same business content, each abstracts a plurality of business The typical software pattern of the component, and obtain the non-instantiated component text based on the pattern; 2. Modeling stage: select the software pattern from the typical software patterns of multiple business components obtained in step 1, so as to obtain the platform-related model of the business component ; 3. Development stage: automatically generate the platform-related model of the business component into a dry business component program; 4. Deployment phase: instantiate the dry business component into a reused business component program for specific requirements, thereby generating the final source program code; Reuse business components in the final software system to dynamically adapt to the business needs of the enterprise by parsing configuration files; There are three ways to adapt to the changing needs of the enterprise: one way, when the business changes reflect the related needs of permissions or personalization, adjust the deployment configuration file or personalization configuration file information through dynamic configuration to realize the business components. Reuse and adjustment of software functions; Approach 2, when business changes cannot be satisfied through dynamic configuration, component programs can be partially modified to achieve adaptation and reuse of business components; Approach 3, when business changes lead to the above two When none of these approaches is applicable, new software business requirements can be met by re-establishing a large-grained component model and regenerating it into a new business component; The business component model is multi-generated into dry business components and reused business components in stages during the development and deployment process; in the development phase, the above model is input into the code generator, and the non-instantiated components that match the pattern are instantiated into the model Describe the executable program of the consistent dry business component; in the deployment phase, the system automatic deployment tool reads the deployment requirements and derives the dry business component into multiple instance components; The dry business component refers to the complete set of attributes and operations contained in it. The reused business component is a component after changing the variable features in the dry business component into fixed features; the business component is based on the different concerns of its life cycle stage. It is divided into dry business components parameterized by attribute operations and reusable business components instantiated according to requirements. 2. The method for automatically generating code of a platform-dependent model of a large-grained component according to claim 1, wherein the business component is a software component realization result of a business object processed in the production and operation process of an enterprise , which contains object data information and related business activities, is a modelized large-grained component with complete business semantics. 3. The method for automatically generating code for a platform-related model of a large-grained component according to claim 1, wherein the business component is divided into dry business of attribute operation parameterization according to different concerns of the stage of its life cycle Components and reused business components that are instantiated according to requirements; dry business components are a complete set of functions within the scope of business documents, and reused business components are a subset of functions derived from dry business components. 4. the code automatic generation method of the platform-dependent model of a kind of large granularity component according to claim 1, it is characterized in that the platform-dependent model of the business component obtained in step 2 adopts source code level mode description language to define business component on the J2EE platform User mode and implementation mode, in which the mode description language is suitable for a variety of software modes that can be realized by high-level programming languages. 5. The method for automatically generating code of a platform-dependent model of a large-grained component according to claim 4, characterized in that, on the basis of the existing business component architecture and software model, according to the medium granularity of each architecture level The component models the platform-related model and defines the properties of the connectors to assemble a complete business component platform-related model. 6. The code automatic generation method of the platform-dependent model of a kind of large granularity component according to claim 2, it is characterized in that described business component is based on the layered architecture model of business component, multiple on each level Small-grained components are assembled using internal connectors to form medium-grained components such as presentation layer components, business logic layer components, and relational object layer components, and then external connectors are used to realize the assembly between various architecture levels to form complete business components. 7. The method for automatically generating code of a platform-dependent model of a large-grained component according to claim 1, wherein the business component modeling in step 2 and the automatic code generation in steps 3 and 4 are performed through visualization The tool is completed, and the visualization tool includes a business component platform-related model modeling tool, a code generator and an automatic system deployer, thereby supporting the automatic generation from the model to the code.

Images