TWI530873B - A configuration method and system - Google Patents

Description

Configuration method and configuration system

The present invention relates to software systems, and more particularly to a method and a system for configuring a software system.

In a complex software system, there are usually more than two object interactions to complete the software function. Each object must obtain its own data or objects that can work for itself. These materials or objects are dependencies. This leads to a very high degree of coupled system software and is difficult to maintain. To this end, a concept of Dependency Injection (DI) is proposed, which avoids excessive coupling between objects and objects by externally defined methods. In addition, the configuration is usually used to improve the flexibility of the software system, and the external data or object structure is defined by file.

However, the existing configuration system is generally a single-layer structure. Due to the upgrade and evolution of the software system, different branches will be generated. In the process of continuous evolution of the product, no matter what evolution mode, only the same configuration file will be used. Or the unit is modified, which will make the configuration system unable to remain relatively stable, which will cause inconvenience in the management, maintenance and application of the configuration system. Moreover, in the single-layer structure, the carrier of the configuration file is single and the storage location is single, which affects its compatibility and scalability.

In view of this, how to design a configuration method and configuration system to make the configuration system easy to manage, maintain, and improve its scalability and compatibility is a technical problem to be solved by relevant technical personnel in the industry.

In order to solve the above technical problem, an aspect of the present invention provides a configuration method for a software system, and a configuration system is referenced when the software system is executed, including the following steps: analyzing the evolution of the software system. And arranging the configuration system according to the result of the analysis, the divided layer includes at least a system level and an expansion level, wherein the system level corresponds to a native system configuring the software system, and the expansion level corresponds to a configuration The expansion of the software system.

In an embodiment of the invention, the system level or the extension level may be further divided into at least one level.

In an embodiment of the invention, the expansion stage includes an enhancement level corresponding to a secondary development or industry of the software system.

In an embodiment of the invention, the expansion stage includes a global level, and the global level corresponds to a common function or common data of the software system.

In an embodiment of the invention, the expansion level includes a set of accounts, and the set of books corresponds to a user group of the software system.

In an embodiment of the invention, the user level of the software system corresponds to a user of the software system.

In an embodiment of the invention, the evolution of the software system is a version change of the software system.

In an embodiment of the invention, the evolution is a change in the software system due to a change in business function or user demand.

In an embodiment of the invention, the configuration system has A configuration resource corresponding to the system level and the expansion level, and each of the configuration resources provides a function or data required to be configured by the software system.

In an embodiment of the present invention, each of the configuration resources is one of a file, an object in a memory, a data in a database, and a Dynamic-Link Library (DLL).

In an embodiment of the present invention, when the configuration resource is a file, the directory structure is divided according to the hierarchical division of the configuration system.

Another aspect of the present invention provides a configuration system for use in a software system, and referring to the configuration system when executing the software system, the configuration system includes: a system level and an expansion level, wherein The system level corresponds to the native system of the software system, and the expansion level corresponds to the expansion of the software system.

In an embodiment of the invention, the system level or the extension level may be further divided into at least one level.

In summary, the configuration method and configuration system proposed by the present invention divides the configuration system hierarchically, and configures the configuration resources to the software system independently at each level, that is, each level maintains its independence, which is convenient for management and maintenance. In addition, when changes are required at each level, it is only necessary to change the level of change, not all changes in the prior art. Moreover, since the configuration system is hierarchically partitioned, the configuration manner and storage location of the configuration resources are not limited, thereby improving compatibility and scalability.

In order to make the technical solutions proposed by the present invention clearer, the present invention will be further described in detail below with reference to the accompanying drawings.

Please refer to FIG. 1 , which is a block diagram of a configuration system according to an embodiment of the present invention.

As shown in FIG. 1, the configuration system 100 includes a system level 110 and an expansion stage 120.

In this embodiment, the configuration system 100 is used in a software system, such as an enterprise resource planning (ERP) system, but not limited thereto, and may be other software systems. When the software system is executed, it refers to the configuration system 100. Specifically, when the software system is executed, the configuration system 100 configures the function or data parameter in the configuration resource to the software system, so that the software system operates normally and implements the corresponding function.

Generally, the software system is constantly evolving from its original system of original shape, that is, it is constantly expanding. For example, software version changes, software system business functions, and user demand changes are all in the evolution of software systems, due to the software system. The evolution of evolution requires constant updates to implement new features, which often requires simultaneous updates to its configuration resources.

In this embodiment, the configuration system 100 adopts a hierarchical design and divides it into a system level 110 and an expansion level 120. The system level 110 corresponds to a native system of the software system, that is, the system level 110 is used to native to the software system. The system is configured; the expansion level 120 corresponds to the expansion of the configuration software system, that is, the expansion level 120 configures the expansion of the software system, such as software. If the system needs to expand the new function, the configuration resource corresponding to the new function can be configured to the software system through the expansion level 120, so that the software system implements the new function.

In this embodiment, the system level 110 and the expansion level 120 can be further divided into at least one level.

Referring again to FIG. 2, a block diagram of an embodiment of the configuration system 100 of FIG. 1 is illustrated.

As shown in FIG. 2, the configuration system 100 includes a system level 110 and an expansion level 120. The expansion level 120 includes an enhancement level 121, a global level 122, a set of books level 123, and a user level 124. In this case, the configuration system 100 has multiple levels. The structure and the level of each level correspond to the configuration parameters of each level in the corresponding software system.

The system level 110 corresponds to the native version developed by the software system vendor, and is the basic level of all other levels of work. Generally, the system level 110 is made into an embedded resource and is placed in the runtime library, but not limited thereto. It can also be a file in the form of cipher text or plain text.

The enhancement level 121 corresponds to the secondary development or industry of the software system, but is not limited thereto, and can be flexibly set according to the functional requirements of the software system.

The global level 122 corresponds to the common function or common data of the software system, and specifically corresponds to the commonality of the multiple set of layers 123.

The account set level 123 corresponds to the user group of the software system. Compared with the global level 122, it corresponds to the characteristics of each set of books. For example, when the global level corresponds to the group, the account set level corresponds to the group. The company under.

The user level 124 corresponds to the user (user) of the software system.

In this embodiment, the priority order of performing configuration is system level 110, enhancement level 121, global level 122, account set level 123, and user level 124, that is, system level 110 is preferentially configured, and user level 124 is finally configured.

It should be noted that, in this embodiment, the expansion stage 120 is divided into the enhancement level 121, the global level 122, the account set level 123, and the user level 124. However, in other embodiments, the expansion stage 120 may only be the enhancement level 121. It may be only the global level 122, or may be a combination of the enhanced level 121 and the global level 122. Of course, it may also be a combination of the enhanced level 121, the global level 122, and the accounting level 123, without the user level 124. It may also be a combination of more than enhanced level 121, global level 122, set of books level 123, and user level 124. In summary, the expansion stage 120 can be flexibly divided according to the evolution process of the software system.

Please refer to FIG. 3, which is a flow chart of a configuration method of another embodiment of the present invention.

The arrangement method will be described below with reference to Fig. 1, Fig. 2, and Fig. 3.

First, in step 310, the evolution of the software system is analyzed. In this embodiment, the evolution may be a version change of the software system, or may be a change caused by a software system due to a change in a business function or a user demand.

Then, in step 320, the configuration system 100 is hierarchically divided according to the result of the analysis, and the divided hierarchy includes at least a system level 110 and an expansion stage 120, wherein the system level 110 corresponds to the native system of the configuration software system, and the expansion level 120 corresponds to the expansion of the configuration software system. for example, When the software system changes the business function of the software system due to secondary development, the expansion level 120 can be defined as the enhancement level 121 at this time. Of course, it can also be defined as other levels, depending on actual needs.

In this embodiment, the system level 110 or the expansion level 120 may be further divided into at least one level. For example, the expansion level 120 may be divided into an enhancement level 121, a global level 122, a set of books level 123, and a user level 124. Corresponding to the configuration parameters of each level in the corresponding software system.

It can be seen from the above that in the above embodiments, since the configuration system 100 is divided into multiple levels, when the data or functions provided by each level are changed, only the level is affected, and the development and design achievements of each layer are effectively retained. Easy to manage and maintain. In addition, the number of levels is not limited, and the layers can still be layered and extensible. And, from the existing needs to deploy all the configuration, change to a configuration that only needs to deploy the change level, the release is smaller and the cost is lower.

In each of the above embodiments, after the configuration system 100 performs the hierarchical division, each level has a corresponding configuration resource, for example, a configuration resource corresponding to the system level 110 and the expansion level 120, and each configuration resource is provided to the software. The function or data parameter that the system needs to configure.

Each of the above configuration resources may be a file, such as an XML file, or an object in a memory, or may be a data in a database and a Dynamic-link Library (DLL), or they may be Any combination, such as one level of configuration resources for files, and another level of configuration resources for objects in memory. In short, the configuration resource can be carried There are many options to increase compatibility. Moreover, it can be stored in different physical locations and has strong scalability.

Moreover, when the resource file is configured, since the configuration system 100 performs hierarchical division, correspondingly, the directory structure of the configuration resource can be hierarchically designed. For details, please refer to the following.

Referring to FIG. 4, a schematic diagram of a directory structure of a configuration resource according to still another embodiment of the present invention is shown.

The directory structure and reading of the configuration resources will be described in detail below with reference to FIGS. 2 and 4.

As shown in FIG. 4, under the root directory, there are management domain objects (Domain Objects), industry directories (Industry), and secondary development directories (Customization). The Domain Objects directory carries the corresponding configuration resources of the system level 110, and has multiple subdirectories under it, such as an employee directory (Employee), an order directory (Sales Order), and of course, other subdirectories that are omitted. The Employee directory also has an A language package storage directory (Culture A), a B language package storage directory (Culture B), a Layout.bin configuration resource, and a Layout.subName.bin configuration resource (where .bin is the file end code name, but not only Limited to this), for the Culture A directory and the Culture B directory, it may also have subdirectories or configuration resources below, but for the sake of brief description, it is not shown. The configuration system reads the configuration resources in hierarchical order. At the same level, it can be decomposed according to the hierarchy of the directory. The deeper the directory, the higher the level of representation and the lower the priority. The longer the name of the same directory can be decomposed according to the English dot "." and the base name, the higher the level of representation. The lower the priority, for example, the Layout.bin configuration resource and the Layout.subName.bin configuration resource, both in the directory hierarchy, at the same level, and because the base name is Layout.bin, then according to English The dot "." and the base name decomposition show that Layout.subName.bin is longer than Layout.bin. Therefore, the Layout.subName.bin configuration resource has a higher level and lower priority than the Layout.bin configuration resource. The Industry directory and the Customization directory correspond to the enhancement level 121 (as shown in FIG. 2), and both may have subdirectories or configuration resources, respectively, but are not fully illustrated for the sake of brevity. It should be noted that only a directory structure is schematically illustrated herein, but is not limited to the directory structure. The directory structure may also be other structures, which may be flexibly set according to the hierarchical division of the configuration system 100.

Moreover, the configuration system 100 can determine which configuration resource to read according to the key identifier (ConfigurationId) of the configuration resource, and the key identifier can include: a domain object identifier (such as Employee), a configuration object identifier (such as a layout), and a language pack information (such as Culture A) and resource extension name (such as subName).

When the configuration resource identifier specifies that the Layout configuration resource under the Employee realm identifier is to be read, and the requirement is CultureA language, the configuration system 100 first reads Layout.bin in hierarchical order, then reads Layout.subName.bin, and then Then read the configuration resources in the CultureA directory. If there is also a definition of the Employee configuration information in the Industry or Customiaztion, the system will read the configuration resources of the Industry and Customization that match this identifier.

Preferably, in this embodiment, the configuration system 100 may collect all relevant configuration resources by using an aspect according to the key identifier, add to the resource container, and perform appropriate caching, and open the file monitor to monitor the file of the disk directory. Change and improve performance. In addition, the configuration system 100 can also check the compatibility according to the key identifier and the operating environment, and filter out the configuration resources that do not meet the conditions. The configuration system can also read and merge the configured configuration resources in sequence according to the predefined configuration objects to generate a configuration object.

In summary, the configuration method and configuration system proposed by the present invention divides the configuration system hierarchically, and configures the configuration resources to the software system independently at each level, that is, each level maintains its independence, which is convenient for management and maintenance. In addition, when changes are required at each level, it is only necessary to change the level of change, not all changes in the prior art. Moreover, since the configuration system is hierarchically partitioned, the configuration manner and storage location of the configuration resources are not limited, thereby improving compatibility and scalability.

Although the present invention has been disclosed in the above embodiments, it is not intended to limit the present invention, and the present invention can be modified and modified without departing from the spirit and scope of the present invention. The scope is subject to the definition of the scope of the patent application attached.

100‧‧‧Configuration System

110‧‧‧System level

120‧‧‧Extension level

121‧‧‧Enhanced

122‧‧‧Global level

123‧‧‧Account sets

124‧‧‧User level

310‧‧‧Steps

320‧‧‧Steps

The above and other objects, features, advantages and embodiments of the present invention will become more <RTIgt;

2 is a block diagram showing an embodiment of the configuration system 100 in FIG. 1.

3 is a flow chart showing a configuration method of another embodiment of the present invention.

4 is a schematic diagram showing a directory structure of a configuration resource according to still another embodiment of the present invention.

100‧‧‧Configuration System

110‧‧‧Extension level

120‧‧‧System level

Claims (11)

A configuration method for a software system, and referring to a configuration system when executing the software system, comprising the following steps: analyzing an evolution of the software system; hierarchically dividing the configuration system according to the analysis result, and dividing the hierarchy At least one system level and one expansion level, wherein the system level corresponds to a native system configuring the software system, the expansion level corresponding to the expansion of the software system is configured; and after the hierarchical division, the system level and the expansion level respectively have Corresponding a plurality of configuration resources, the configuration system collects the configuration resources by using a slice according to a key identifier, adds the resource to the resource container, and opens the file monitor to monitor the file change of the disk directory. The system checks the compatibility according to the key identifier and the operating environment, and filters at least one configuration resource that does not meet the compatibility condition from the configuration resources. The configuration method of claim 1, wherein the system level or the extension level can further divide at least one level. The configuration method of claim 1, wherein the expansion level further comprises an enhancement level corresponding to secondary development or industry of the software system. The configuration method of claim 1, wherein the expansion stage further comprises a global level, the global level corresponding to a common function or common data of the software system. The configuration method of claim 1 or 4, wherein the expansion level further comprises a set of accounts, the set of accounts corresponding to the user group of the software system. The configuration method of claim 5 includes a user-level user corresponding to the software system. The configuration method of claim 1, wherein the evolution of the software system is a version change of the software system. The configuration method of claim 1, wherein the evolution of the software system is a change of the software system due to a change in a business function or a user demand. The configuration method of claim 1, wherein the configuration system has at least one configuration resource corresponding to the system level and the extension level, and each of the configuration resources provides a function or data required to be configured by the software system. The configuration method of claim 9, wherein each of the configuration resources is one of a file, an object in a memory, a data in a database, and a dynamic link library or a combination thereof. The configuration method of claim 10, wherein when the configuration resource is a file, hierarchically dividing the directory structure with the configuration system Corresponding division.