CN112433748A - Software system version calibration method and device, storage medium and processor - Google Patents
Software system version calibration method and device, storage medium and processor Download PDFInfo
- Publication number
- CN112433748A CN112433748A CN201910789656.9A CN201910789656A CN112433748A CN 112433748 A CN112433748 A CN 112433748A CN 201910789656 A CN201910789656 A CN 201910789656A CN 112433748 A CN112433748 A CN 112433748A
- Authority
- CN
- China
- Prior art keywords
- version
- dimension
- software system
- dimensions
- identification information
- 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.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 66
- 238000003860 storage Methods 0.000 title claims abstract description 24
- 238000009434 installation Methods 0.000 claims description 45
- 230000008569 process Effects 0.000 claims description 20
- 238000013499 data model Methods 0.000 claims description 15
- 238000004590 computer program Methods 0.000 description 10
- 238000010586 diagram Methods 0.000 description 10
- 238000012545 processing Methods 0.000 description 10
- 238000007726 management method Methods 0.000 description 7
- 238000011161 development Methods 0.000 description 6
- 230000006870 function Effects 0.000 description 6
- 230000008859 change Effects 0.000 description 5
- 230000008901 benefit Effects 0.000 description 3
- 230000003287 optical effect Effects 0.000 description 3
- 238000012360 testing method Methods 0.000 description 3
- 238000005516 engineering process Methods 0.000 description 2
- 238000004519 manufacturing process Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 238000013509 system migration Methods 0.000 description 2
- 230000005540 biological transmission Effects 0.000 description 1
- 238000004140 cleaning Methods 0.000 description 1
- 230000007547 defect Effects 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 238000011900 installation process Methods 0.000 description 1
- 238000013508 migration Methods 0.000 description 1
- 230000005012 migration Effects 0.000 description 1
- 230000008520 organization Effects 0.000 description 1
- 230000008439 repair process Effects 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
- 230000001360 synchronised effect Effects 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/71—Version control; Configuration management
Abstract
The invention provides a software system version calibration method, a device, a storage medium and a processor, wherein the method comprises the following steps: acquiring identification information of the software system on at least two version dimensions, wherein the software system is in an installed state; and generating the version number of the software system based on the identification information on the at least two version dimensions. Therefore, the version number is generated based on the identification information on at least two version dimensions of the software system in the installed state, and the version of the software system is calibrated without depending on the release version number of the software system.
Description
Technical Field
The invention relates to the technical field of computers, in particular to a software system version calibration method, a software system version calibration device, a storage medium and a processor.
Background
With the development of software technology, customized software systems are usually updated according to the requirements. Newer and newer software systems require a nominal version number to identify differences between their versions.
At present, the version of the software system is usually calibrated according to the release version number of the software system.
However, in a lifecycle of a software system after release, various changes are generally caused due to needs, bugs, migration, and the like, and thus one release version number may correspond to a plurality of different software system versions under the release version number, and thus, the accuracy of calibrating the versions by the release version number of the software system is low.
Disclosure of Invention
In view of the foregoing problems, the present invention provides a method, an apparatus, a storage medium, and a processor for calibrating a software system version, which overcome the foregoing problems or at least partially solve the foregoing problems, and generate a software system version number based on identification information of at least two version dimensions by acquiring identification information of at least two version dimensions on an installed software system, thereby implementing accurate calibration of a software system version.
The invention also provides a software system version calibration device used for ensuring the actual realization and application of the method.
In order to achieve the above purpose, the embodiments of the present invention provide the following technical solutions:
a software system version calibration method comprises the following steps:
acquiring identification information of the software system on at least two version dimensions, wherein the software system is in an installed state;
and generating the version number of the software system based on the identification information on the at least two version dimensions.
Optionally, in the foregoing method, generating the version number of the software system based on the identification information in the at least two version dimensions includes:
selecting identification information on at least one target dimension from the identification information on the at least two version dimensions;
and generating a version number of the software system based on the identification information on the target dimension, wherein the version number corresponds to the identification information on the target dimension.
Optionally, the selecting, from the identification information in the at least two version dimensions, the identification information in at least one target dimension includes:
performing dimension classification on the at least two version dimensions to obtain at least two dimension types, wherein each dimension type corresponds to at least one version dimension;
selecting at least one version dimension as a target dimension from the version dimensions corresponding to at least one dimension type;
and obtaining the identification information on the target dimension.
Optionally, in the method, selecting at least one version dimension as a target dimension from the version dimensions corresponding to at least one dimension type includes:
selecting at least one version dimension as a target dimension from the version dimensions corresponding to the first dimension type and/or the second dimension type;
wherein the first dimension type is a dimension type associated with a process of the software system; the second dimension type is a dimension type associated with code of the software system.
In the foregoing method, optionally, the version dimension includes any one or a combination of any multiple of an installation package dimension, a source code dimension, an environment variable dimension, a configuration variable dimension, a middleware dimension, an external interface dimension, and a data model dimension of the software system.
Optionally, in the foregoing method, the generating a version number of the software system based on the identification information in the target dimension includes:
and coding an identification sequence consisting of the identification information on the target dimension to generate the version number of the software system.
A software system version calibration apparatus, comprising:
an obtaining unit, configured to obtain identification information of the software system in at least two version dimensions, where the software system is in an installed state;
a generating unit, configured to generate a version number of the software system based on the identification information in the at least two version dimensions.
A storage medium, comprising stored instructions, wherein when executed, the instructions control a device on which the storage medium is located to execute the software system version calibration method.
A processor, configured to run a program, wherein the program executes the software system version calibration method described above.
By means of the technical scheme, in the software system version calibration method, the software system version calibration device, the storage medium and the electronic equipment, under the condition that the software system is in the installed state, the software system version number is generated by acquiring the identification information of at least two version dimensions of the software system and further based on the identification information of at least two version dimensions. Therefore, the version number is generated based on the identification information on at least two version dimensions of the software system in the installed state, and the version of the software system is calibrated without depending on the release version number of the software system.
The foregoing description is only an overview of the technical solutions of the present invention, and the embodiments of the present invention are described below in order to make the technical means of the present invention more clearly understood and to make the above and other objects, features, and advantages of the present invention more clearly understandable.
Drawings
Various other advantages and benefits will become apparent to those of ordinary skill in the art upon reading the following detailed description of the preferred embodiments. The drawings are only for purposes of illustrating the preferred embodiments and are not to be construed as limiting the invention. Also, like reference numerals are used to refer to like parts throughout the drawings. In the drawings:
FIG. 1 is a flowchart illustrating a software system version calibration method according to an embodiment of the present invention;
FIG. 2 is a schematic flow chart illustrating the generation of the version number of the software system according to the embodiment of the present invention;
fig. 3 shows a schematic structural diagram of a software system version calibration apparatus disclosed in the embodiment of the present invention.
Detailed Description
Exemplary embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. While exemplary embodiments of the present disclosure are shown in the drawings, it should be understood that the present disclosure may be embodied in various forms and should not be limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art.
Due to various reasons, the software system is easy to change in the lifecycle of the software system after the software system is issued, so that the accuracy of calibrating the version of the software system by the issued version number is low, and the version of the software system is difficult to identify. The embodiment of the invention provides a software system version calibration method to solve the problems, and the purpose of accurately calibrating the software system version is realized by acquiring the identification information of the software system in an installed state on at least two version dimensions and generating the software system version number based on the identification information on the at least two version dimensions.
Fig. 1 is a schematic flow chart of a software system version calibration method disclosed in the embodiment of the present invention. The embodiment of the invention can be suitable for calibrating the version of the customized software system in the cloud platform environment, for example, the customized software system in the cloud platform environment can be a cloud native application system, can also be an application based on cloud platform deployment and management, and the like. The method provided by the embodiment of the present invention is also applicable to version calibration of a software system in a computer, a server or other electronic devices capable of performing data processing during development, the electronic device is provided with the software system, the software system can be a software system that has been installed when an operating system on the electronic device is initialized, and can also be a software system that is prepared for installation or is being installed or is already installed and additionally downloaded after the electronic device is initialized, for example: drawing software, calculators, chat tools, office software or financial tools, etc., which may require software version calibration due to changes in the software lifecycle due to changes in demand, bug fixes, upgrade management, system migration, etc. The method provided by the embodiment of the invention is mainly used for carrying out version calibration on the software system so as to improve the accuracy of the version calibration.
S101, acquiring identification information of the software system on at least two version dimensions, wherein the software system is in an installed state.
The version dimension may be understood as a software feature dimension in different directions on the software system, and specifically may be a feature dimension before installation of the software system, a feature dimension after installation of the software system, a feature dimension in a process of the software system, and the like.
And the identification information of the version dimension can be understood as: the software system can represent the information of the dimension attribute on different software feature dimensions, such as the installation package version number in the feature dimension before the software system is installed, the configuration variable information after the software system is installed, and the like.
It should be noted that, in the embodiment of the present invention, before calibrating the version of the software system, the software system needs to be initialized first. Initializing a software system herein may be understood as deploying a software system installation in the form of an installation package on an electronic device.
Accordingly, in this embodiment, the state of the software system after installation can be understood as: the software system can be in a state of completing installation but not starting operation, or can be in a state of completing installation and being started to operate.
In addition, in the embodiment, after the software system is initialized, in the process of obtaining the identification information, the interference between the state information and the data information in the use process of the software system on line or after upgrading can be avoided through data cleaning and the like. For example, redundant test data, user information and the like are eliminated, so that the influence of non-version characteristic factors on subsequent version calibration is avoided.
Preferably, in this embodiment, when performing version calibration of the software system, it may be selected that, at the initial stage of online deployment or upgrade deployment of the software system, identification information on at least two version dimensions is obtained at this time, so as to reduce the influence of other factors on the version calibration. .
It should be noted that the state of the software system just after deployment is not limited to the state of the software system after initialization is completed, but may be other states, such as a state of online deployment to a cloud platform, a state of upgrading deployment to a cloud platform and downloading updates to an electronic device, and so on, as long as the software system is just after deployment and is not used by a user or is configured additionally by a user.
And S102, generating the version number of the software system based on the identification information on at least two version dimensions.
In this embodiment, after further data processing is performed on the basis of the identification information of at least two version dimensions, a software system version calibration table is formulated to generate a version number of the software system, or alternatively, in this embodiment, the identification information may be directly formed into a character string to formulate a software system version calibration table to generate a version number of the software system.
In a specific application, the method provided by the embodiment of the invention can accurately calibrate the version of a software system, for example, the version of the Word software in a computer is difficult to accurately identify due to the change of the Word in the life cycle caused by various reasons such as requirement change, defect repair, upgrade management, system migration and the like, so that after the Word software is initialized, by acquiring identification information of at least two dimensions of the Word in various software characteristic dimensions before installation, after installation and in operation, and based on the identification information, performing data processing or forming a character string, formulating a software system version calibration table, generating the version number of the Word software, for example, based on the identification information of the dimensions such as an installation package, a source code, environment variable information and the like of the Word software, performing data processing or forming a character string, formulating a software system version calibration table, and generating the current version number of the Word software to realize accurate calibration of the version of the Word, wherein the version number is not limited to the release version number of the Word software at the beginning of release.
It should be noted that the method provided by the embodiment of the present invention is not limited to Word applied to a computer, and may be any software system in a device.
As can be seen from the foregoing solution, in the software system version calibration method provided in this embodiment, under the condition that the software system is in the post-installation state, the version number of the software system is generated by obtaining the identification information of at least two version dimensions of the software system and further based on the identification information of at least two version dimensions. Therefore, in the embodiment, the version number is generated based on the identification information on at least two version dimensions of the software system in the installed state, and the version of the software system is calibrated without depending on the release version number of the software system.
It should be noted that the version dimension may include any one or any combination of multiple of an installation package dimension, a source code dimension, an environment variable dimension, a configuration variable dimension, a middleware dimension, an external interface dimension, and a data model dimension of the software system. Accordingly, in this embodiment, S101 obtains, in the version dimensions, identification information in at least two version dimensions, such as information including an installation package version number in the installation package dimension, a middleware version number in the middleware dimension, and an external interface list and version number in the external interface dimension, and generates a version number of the software system based on the information.
As shown in fig. 2, which is a flowchart for implementing the S101 in generating the version number in the embodiment of the present invention, specifically, the method may include the following steps:
s201, selecting the identification information on at least one target dimension from the identification information on at least two version dimensions.
The target dimension may be understood as a feature dimension selected from at least two version dimensions for generating the software system version number. For example: and when the at least two version dimensions comprise an installation package dimension, a source code dimension and an environment variable dimension, selecting the installation package dimension as a target dimension.
The identification information of the target dimension may be understood as information that the software system can represent the attribute of the dimension in different software feature dimensions, for example, if the target dimension is an installation package dimension, the identification information of the target dimension is an installation package version number.
In the method provided by the embodiment of the present invention, when selecting the identification information in at least one target dimension from the identification information in at least two version dimensions, the method may specifically be implemented in the following manner:
firstly, performing dimension classification on at least two version dimensions to obtain at least two dimension types, wherein each dimension type corresponds to at least one version dimension. And then, selecting at least one target dimension from the version dimensions corresponding to the at least one dimension type. And finally, acquiring the identification information on the selected target dimension.
In this embodiment, performing dimension classification on at least two version dimensions may be understood as: software feature dimensions in different directions can be classified according to the properties of the feature dimensions, such as corresponding functional attributes in a software system, wherein the properties of the feature dimensions can characterize the typicality of the feature dimensions. For example, in the present embodiment, the installation package dimension, the source code dimension, the environment variable dimension, the configuration variable dimension, the middleware dimension, the external interface dimension, and the data model dimension are classified according to whether they relate to a process of the software system or a code of the software system. Accordingly, the version dimensions in this embodiment may be divided into at least two types, such as a first dimension type and a second dimension type, and even a third or other dimension types may be provided, where the first dimension type is a dimension type related to a process of the software system, such as a type related to an installation process, an online process, or an operation process of the software system, the second dimension type is a dimension type related to code of the software system, such as a type related to source code or interface code of the software system, and so on. The first dimension type corresponds to at least one version dimension, and the second dimension type corresponds to at least one version dimension, for example, the first dimension type may correspond to an installation package dimension, an environment variable dimension, a configuration variable dimension, a middleware dimension, and a data model dimension, and the second dimension type may correspond to a source code dimension, an external interface dimension, and the like.
It should be noted that the feature dimensions of the software system are classified, not only according to the properties of the feature dimensions, but also according to the importance degree of the feature dimensions in the software system or the application range of the feature dimensions, so that the dimension types can be enriched, and the accuracy of subsequent version number calibration can be improved to a certain extent.
Correspondingly, in this embodiment, after the version dimensions are classified to obtain the version dimensions of the first dimension type and the second dimension type, at least one version dimension may be selected as a target dimension from the version dimensions corresponding to the first dimension type and/or the second dimension type.
It should be noted that, the selection of the target dimension from the version dimensions corresponding to at least one dimension type is not limited to the selection of at least one version dimension as the target dimension from the version dimensions corresponding to each dimension type in the classification, at least one version dimension may be selected as the target dimension only from the version dimensions corresponding to a certain dimension type, or at least one version dimension may be selected as the target dimension from the version dimensions corresponding to any multiple dimension types in all the dimension types.
For example, at least one version dimension may be selected as a target dimension from among the version dimensions corresponding to the first dimension type only, that is: selecting one or more version dimensions as target dimensions from version dimensions corresponding to dimension types related to processes of the software system, such as installation package dimensions, environment variable dimensions, middleware dimensions and the like; at least one version dimension can be selected as a target dimension only from the version dimensions corresponding to the second dimension type, that is: selecting one or more version dimensions as target dimensions from version dimensions corresponding to dimension types related to codes of the software system, such as source code dimensions, external interface dimensions and the like; one or more version dimensions can also be selected as target dimensions from the version dimensions corresponding to the first dimension type and the version dimensions corresponding to the second dimension type, respectively, that is: one or more version dimensions are selected as target dimensions from version dimensions corresponding to the dimension types related to the processes of the software system, such as installation package dimensions, environment variable dimensions, middleware dimensions and the like, and one or more version dimensions are selected as target dimensions from version dimensions corresponding to the dimension types related to the codes of the software system, such as source code dimensions, external interface dimensions and the like.
And S202, generating the version number of the software system based on the identification information on the target dimension.
Wherein the version number corresponds to the identification information in the target dimension.
It should be noted that, in this embodiment, the version number may be directly composed of identification information on a target dimension, for example, in this embodiment, the identification information on the target dimension is composed of a character string, and is directly used as the version number of the software system. For example, in this embodiment, the installation package version number in the installation package dimension and the source code version number in the source code dimension may be combined together to form a character string, and the character string may be used as the software system version number.
However, the version number at this time may have a certain complexity and may not be easily recognized intuitively, so in this embodiment, the identification information on the target dimension may be further processed, and the version number of the software system may be generated based on the processing result.
In an implementation manner, in this embodiment, the identification information in the target dimension is processed to obtain a version number of the software system, which may be specifically implemented in the following manners:
in this embodiment, the identification information in the target dimension may be subjected to digital addition and then averaged, and the obtained result is used as the version number of the software system. For example, in this embodiment, V1.5 of the version number of the installation package and V3.1 of the version number of the source code are averaged to obtain the version number of the software system: v2.3, which corresponds to the installation package version number V1.5 and the source code version number V3.1.
Alternatively, in this embodiment, an identification sequence formed by the identification information in the target dimension may be encoded to generate a version number of the software system. That is to say, in this embodiment, the identification information in the target dimension is serialized to obtain an identification sequence composed of the identification information in the target dimension, and then these sequences are encoded to obtain the version number of the software system. For example, in this embodiment, V1.5 of the installation package version number and V3.1 of the source code version number form a sequence: and the installation package V1.5 and the source code V3.1 are coded according to the calibration sequence of the version numbers, if the previous version number of the software system is V4.8, the version number of the software system is V4.9 at the moment, and the V1.5 of the version number of the software system and the installation package corresponds to the V3.1 of the version number of the source code at the moment.
Therefore, the identification information on any dimensionality changes, and a new version number is generated, so that the version number has unique directivity, and the accuracy of version number calibration is improved.
In a specific application, when the method provided by the embodiment of the invention is applied to version calibration of Word software, one or more or all dimension types of the Word software in the installation package dimension, the environment variable dimension, the configuration variable dimension, the middleware dimension and the data model dimension of the first dimension type and the source code dimension and the external interface dimension of the second dimension type can be selected as target dimensions, identification information on the target dimensions is obtained, and then an identification sequence formed by the identification information of the target dimensions is encoded, so that a version number of a software system is generated.
For example, in this embodiment, the identification information on the version dimensions of the different dimension types may be formulated into a version calibration table of the Word software, the table includes identification information of various version dimensions in different dimension types, and when the version number needs to be generated, one or more or all of the identification information of the version dimensions may be selected and encoded after forming a sequence, so as to generate a version number of the Word, thereby accurately calibrating the version number of the Word.
Based on the technical solution provided by the embodiment of the present invention, the following example is given by taking the version designation of the customized software system in the cloud platform as an example, and the following example is given as follows:
first, in the present embodiment, a scheme for reasonably identifying the version of customized software or non-standard software is defined to avoid the situation that the accuracy is low due to the fact that only the release version number (e.g. V1.0) provided by the vendor is used as the uniqueness of the release version number. In the technical scheme of the embodiment, software features such as identification information on at least two dimensions are utilized to simultaneously analyze and identify one piece of software, the software is divided into two levels of a first dimension type and a second dimension type such as a main feature and an auxiliary feature according to the characteristic typicality, and the corresponding dimension identification is selected from different levels to meet different management fine requirements on the version of the software system.
The technical scheme in the embodiment mainly comprises the following steps:
1. initializing the software system, and then executing the following steps 2-8 to obtain the identification information on each dimension, as follows:
2. collecting the installation package version number on the installation package dimension;
3. collecting a source code version number on a source code dimension;
4. collecting environment variables on the dimension of the environment variables and distributing identification information;
5. collecting configuration variables on a configuration variable dimension and distributing identification information;
6. collecting all middleware version numbers on the dimension of the middleware;
7. collecting an external interface list and a corresponding version number on the external interface dimension;
8. collecting a data model and initial data on a data model dimension and distributing identification information;
9. generating a calibration table from the identification information on each dimension, wherein each dimension is divided into two layers in the calibration table, and each layer corresponds to a corresponding dimension type, such as a calibration table of a primary and secondary characteristic version;
10. and selecting identification information of the main and auxiliary characteristics from the calibration table to code the version number to obtain the final version number of the software.
The method comprises the following specific steps:
1. initializing software systems
In this embodiment, when calibrating the version, the software system may generally be in a state in which the customized software has just completed deployment, and must be an instance system (i.e., running state) instead of the state in which the installation package is not installed;
it should be noted that, in this embodiment, interference of state information and data information in the use process of the software system may be firstly eliminated, and extra test data, user information, and the like are particularly noticed clearly, thereby avoiding influence of non-version characteristic factors on version calibration. Therefore, the time for customizing the software version calibration should be selected as early as possible in the online (upgrading).
2. Collecting installation package version number on installation package dimension
Specifically, the version number provided by the software installation package may be a version number generally represented by a multi-level number, such as v1.4.1, and it should be noted that the installation package version number is not an internal version number of a technical team, but is a public version number.
3. Collecting source code version numbers in source code dimensions
The source code version number is based on a unique number in the code management system, and is typically a serial number, such as 69 (meaning the 69 th submission of the code library). The source code version in this embodiment has a Tag (Tag), such as a development team tagging the code version, to facilitate future content retrieval of the version.
4. Collecting environment variables on environment variable dimension and distributing identification information
The environment variable refers to variable information of an operating system environment or a virtual execution environment (such as JRE) in which the software runs. In this embodiment, the environment variables may be recorded as completely as possible during development or online deployment, such as the type of the operating system, the version number, the memory size, the file system path, and the like, and assigned with a unique identifier (which may be a unique serial number).
5. Collecting configuration variables on configuration variable dimension and distributing identification information
The configuration variables refer to some common parameters that need to be specified for correct operation of software, and generally, the configuration variables change according to changes of versions of environment variables, such as production configuration variables, development configuration variables, and the like.
It should be noted that the configuration variables generally exist in a configuration file, and when the software system is deployed, the parameter values are correctly set, specifically, a group of specific configuration variable parameter key value pairs is completely recorded, and a unique identifier (a unique serial number is available) is assigned to the group of specific configuration variable parameter key value pairs.
6. Collecting all middleware version numbers in middleware dimensions
In this embodiment, all middleware lists, such as message queues, databases, caches, load balancing, etc., on which the software system depends are obtained, and the version number of each middleware is recorded.
It should be noted that the configuration variables of the middleware can be obtained in 6.
7. Collecting external interface list and corresponding version number on external interface dimension
In this embodiment, an interface list disclosed by the software system is obtained, for example, a standard interface at least has a function description, a call address, an input/output parameter, and an interface version number; the list of interfaces may then be assigned a version number that may be synchronized with the source code version, noting that it is not a version number for each interface.
8. Collecting data model and initial data on data model dimension and distributing identification information
In this embodiment, the structure file (i.e. data model) information of the database (or other middleware) and the data table is collected, and the exported SQL file or the file with the specific format of the middleware may be imported back to the database (middleware).
In this embodiment, when the initial data information is collected, the data content in the initial state is exported as an independent file, and the two files need to be matched and assigned to the same version identifier;
9. generating a calibration table of major and minor feature versions
As shown in the following table 1, an installation package version number V1.0, a source code version number V278, an environment variable information identifier V2.0, a configuration variable information identifier V1.3, a middleware version number V1.4, an external interface list version number V278, and a data model and initial data information identifier V1.5 are filled in a calibration table, where the installation package version number V1.0, the environment variable information identifier V2.0, the configuration variable information identifier V1.3, and the middleware version number V1.4 are major feature dimensions, and the external interface list version number V278 and the source code version number V278 are minor feature dimensions.
TABLE 1 calibration chart
10. And selecting identification information of the main and auxiliary characteristics from the calibration table to code the version number to obtain the final version number of the software.
For example, when the software version number is calibrated each time, the identification information in the above dimensions, such as the version number, can be collected and filled into the calibration table, and the identification information of the main and auxiliary features is selected from the calibration table to encode the version number; or, in the upgrading process of software development or test, the identification information of each dimension in the calibration table is updated at any time, and when the software version number is calibrated each time, the updated identification information of the main and auxiliary features is selected from the calibration table to code the version number, and the like.
For software which is not manufactured in a standardized way, the version of the software state can be strictly calibrated through the version calibration table. For convenience of use, each calibrated version is assigned a "calibration version number", typically the first level varies according to the primary characteristic and the second level varies according to the secondary characteristic.
Therefore, the customized development management with orderly specifications can be realized in the embodiment, and only the main characteristics can be adopted for calibration; for the organization with poor management, the factors of the auxiliary characteristics can be considered so as to improve the accuracy of the version calibration.
As shown in fig. 3, which is a schematic structural diagram of a software system version calibration apparatus provided in an embodiment of the present invention, the apparatus in the embodiment of the present invention may be suitable for calibrating a version of a customized software system in a cloud platform environment.
Specifically, the apparatus in this embodiment may include the following structure:
an obtaining unit 301, configured to obtain identification information of the software system in at least two version dimensions, where the software system is in an installed state;
a generating unit 302, configured to generate a version number of the software system based on the identification information in the at least two version dimensions.
As can be seen, in the software system version calibration apparatus provided in this embodiment, when the software system is in an installed state, the software system version number is generated by obtaining the identification information of at least two version dimensions of the software system and further based on the identification information of at least two version dimensions. Therefore, in the embodiment, the version number is generated based on the identification information on at least two version dimensions of the software system in the installed state, and the version of the software system is not calibrated only by depending on the release version number of the software system, so that the calibration of the software version is realized by increasing the dimension of the version calibration, and the accuracy of the version calibration is improved.
Wherein the generating unit 302 is specifically configured to:
firstly, selecting identification information on at least one target dimension from the identification information on the at least two version dimensions, for example, performing dimension classification on the at least two version dimensions to obtain at least two dimension types, wherein each dimension type corresponds to at least one version dimension; selecting at least one version dimension as a target dimension from the version dimensions corresponding to at least one dimension type; and obtaining the identification information on the target dimension.
And then, generating a version number of the software system based on the identification information on the target dimension, wherein the version number corresponds to the identification information on the target dimension.
Specifically, when at least one version dimension is selected as a target dimension from among the version dimensions corresponding to at least one dimension type, the generating unit 302 may be implemented in the following manner:
selecting at least one version dimension as a target dimension from the version dimensions corresponding to the first dimension type and/or the second dimension type;
wherein the first dimension type is a dimension type associated with a process of the software system; the second dimension type is a dimension type associated with code of the software system.
The version dimension comprises any one or combination of any more of an installation package dimension, a source code dimension, an environment variable dimension, a configuration variable dimension, a middleware dimension, an external interface dimension and a data model dimension of the software system.
Accordingly, the generating unit 302 may be implemented by the following steps when generating the version number of the software system based on the identification information in the target dimension:
and coding an identification sequence consisting of the identification information on the target dimension to generate the version number of the software system.
It should be noted that, the specific implementation of each unit in the apparatus in the present embodiment may refer to the corresponding description in the foregoing and is not described in detail here.
The software system version calibration apparatus in this embodiment may include a processor and a memory, where the acquiring unit and the generating unit are both stored in the memory as program units, and the processor executes the program units stored in the memory to implement corresponding functions.
The processor comprises a kernel, and the kernel calls the corresponding program unit from the memory. One or more than one kernel can be set, and the software system version is accurately calibrated by adjusting kernel parameters.
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), and the memory includes at least one memory chip.
The embodiment of the invention provides a storage medium, wherein a program is stored on the storage medium, and the program realizes the software system version calibration method when being executed by a processor.
The embodiment of the invention provides a processor, which is used for running a program, wherein the software system version calibration method is executed when the program runs.
The embodiment of the invention provides equipment, which comprises a processor, a memory and a program which is stored on the memory and can run on the processor, wherein the processor executes the program and realizes the following steps:
acquiring identification information of the software system on at least two version dimensions, wherein the software system is in an installed state;
and generating the version number of the software system based on the identification information on the at least two version dimensions.
Optionally, the generating a version number of the software system based on the identification information in the at least two version dimensions includes:
selecting identification information on at least one target dimension from the identification information on the at least two version dimensions;
and generating a version number of the software system based on the identification information on the target dimension, wherein the version number corresponds to the identification information on the target dimension.
Optionally, the selecting, from the identification information in the at least two version dimensions, the identification information in at least one target dimension includes:
performing dimension classification on the at least two version dimensions to obtain at least two dimension types, wherein each dimension type corresponds to at least one version dimension;
selecting at least one version dimension as a target dimension from the version dimensions corresponding to at least one dimension type;
and obtaining the identification information on the target dimension.
Optionally, the selecting at least one version dimension as a target dimension from the version dimensions corresponding to the at least one dimension type includes:
selecting at least one version dimension as a target dimension from the version dimensions corresponding to the first dimension type and/or the second dimension type;
wherein the first dimension type is a dimension type associated with a process of the software system; the second dimension type is a dimension type associated with code of the software system.
Optionally, the version dimension includes any one or a combination of any multiple of an installation package dimension, a source code dimension, an environment variable dimension, a configuration variable dimension, a middleware dimension, an external interface dimension, and a data model dimension of the software system.
Optionally, the generating a version number of the software system based on the identification information on the target dimension includes:
and coding an identification sequence consisting of the identification information on the target dimension, formulating a software system version calibration table, and generating a version number of the software system.
The device herein may be a server, a PC, a PAD, a mobile phone, etc.
The present application further provides a computer program product adapted to perform a program for initializing the following method steps when executed on a data processing device:
acquiring identification information of the software system on at least two version dimensions, wherein the software system is in an installed state;
and generating the version number of the software system based on the identification information on the at least two version dimensions.
Optionally, the generating a version number of the software system based on the identification information in the at least two version dimensions includes:
selecting identification information on at least one target dimension from the identification information on the at least two version dimensions;
and generating a version number of the software system based on the identification information on the target dimension, wherein the version number corresponds to the identification information on the target dimension.
Optionally, the selecting, from the identification information in the at least two version dimensions, the identification information in at least one target dimension includes:
performing dimension classification on the at least two version dimensions to obtain at least two dimension types, wherein each dimension type corresponds to at least one version dimension;
selecting at least one version dimension as a target dimension from the version dimensions corresponding to at least one dimension type;
and obtaining the identification information on the target dimension.
Optionally, the selecting at least one version dimension as a target dimension from the version dimensions corresponding to the at least one dimension type includes:
selecting at least one version dimension as a target dimension from the version dimensions corresponding to the first dimension type and/or the second dimension type;
wherein the first dimension type is a dimension type associated with a process of the software system; the second dimension type is a dimension type associated with code of the software system.
Optionally, the version dimension includes any one or a combination of any multiple of an installation package dimension, a source code dimension, an environment variable dimension, a configuration variable dimension, a middleware dimension, an external interface dimension, and a data model dimension of the software system.
Optionally, the generating a version number of the software system based on the identification information on the target dimension includes:
and coding an identification sequence consisting of the identification information on the target dimension, formulating a software system version calibration table, and generating a version number of the software system.
As will be appreciated by one skilled in the art, 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 flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams 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 a typical configuration, a computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.
The memory may include forms of volatile memory in a computer readable medium, Random Access Memory (RAM) and/or non-volatile memory, such as Read Only Memory (ROM) or flash memory (flash RAM). The memory is an example of a computer-readable medium.
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 computer storage media 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 that can be used to store information that can be accessed by a computing device. As defined herein, computer readable media does not include transitory computer readable media (transmyedia) 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 an … …" does not exclude the presence of other identical elements in the process, method, article, or apparatus that comprises the element.
As will be appreciated by one skilled in the art, 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 above are merely examples of the present application and are not intended to limit the present application. Various modifications and changes may occur to those skilled in the art. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application should be included in the scope of the claims of the present application.
Claims (10)
1. A software system version calibration method is characterized by comprising the following steps:
acquiring identification information of the software system on at least two version dimensions, wherein the software system is in an installed state;
and generating the version number of the software system based on the identification information on the at least two version dimensions.
2. The method of claim 1, wherein generating a version number for the software system based on the identification information in the at least two version dimensions comprises:
selecting identification information on at least one target dimension from the identification information on the at least two version dimensions;
and generating a version number of the software system based on the identification information on the target dimension, wherein the version number corresponds to the identification information on the target dimension.
3. The method of claim 2, wherein the selecting the identification information in at least one target dimension from the identification information in the at least two version dimensions comprises:
performing dimension classification on the at least two version dimensions to obtain at least two dimension types, wherein each dimension type corresponds to at least one version dimension;
selecting at least one version dimension as a target dimension from the version dimensions corresponding to at least one dimension type;
and obtaining the identification information on the target dimension.
4. The method of claim 3, wherein selecting at least one version dimension as a target dimension from among the version dimensions corresponding to the at least one dimension type comprises:
selecting at least one version dimension as a target dimension from the version dimensions corresponding to the first dimension type and/or the second dimension type;
wherein the first dimension type is a dimension type associated with a process of the software system; the second dimension type is a dimension type associated with code of the software system.
5. The method of claim 1 or 2, wherein the version dimension comprises any one or any combination of installation package dimensions, source code dimensions, environment variable dimensions, configuration variable dimensions, middleware dimensions, external interface dimensions, and data model dimensions of the software system.
6. The method of claim 2, wherein generating the version number of the software system based on the identification information in the target dimension comprises:
and coding an identification sequence consisting of the identification information on the target dimension to generate the version number of the software system.
7. A software system version calibration apparatus, comprising:
an obtaining unit, configured to obtain identification information of the software system in at least two version dimensions, where the software system is in an installed state;
a generating unit, configured to generate a version number of the software system based on the identification information in the at least two version dimensions.
8. The apparatus according to claim 7, wherein the generating unit is specifically configured to:
selecting identification information on at least one target dimension from the identification information on the at least two version dimensions; and generating a version number of the software system based on the identification information on the target dimension, wherein the version number corresponds to the identification information on the target dimension.
9. A storage medium, characterized in that the storage medium comprises stored instructions, wherein when the instructions are executed, a device on which the storage medium is located is controlled to execute the software system version calibration method according to any one of claims 1 to 6.
10. A processor, characterized in that the processor is configured to run a program, wherein the program is configured to execute the software system version calibration method according to any one of claims 1 to 6 when running.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910789656.9A CN112433748A (en) | 2019-08-26 | 2019-08-26 | Software system version calibration method and device, storage medium and processor |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910789656.9A CN112433748A (en) | 2019-08-26 | 2019-08-26 | Software system version calibration method and device, storage medium and processor |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112433748A true CN112433748A (en) | 2021-03-02 |
Family
ID=74690080
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910789656.9A Pending CN112433748A (en) | 2019-08-26 | 2019-08-26 | Software system version calibration method and device, storage medium and processor |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112433748A (en) |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20100318968A1 (en) * | 2009-06-15 | 2010-12-16 | Microsoft Corporation | Catalog-based software component management |
| CN109614137A (en) * | 2018-11-30 | 2019-04-12 | 北京字节跳动网络技术有限公司 | Software version control method, device, equipment and medium |
| CN109684414A (en) * | 2018-12-26 | 2019-04-26 | 百度在线网络技术（北京）有限公司 | Synchronous method, device, equipment and the storage medium of block data |
-
2019
- 2019-08-26 CN CN201910789656.9A patent/CN112433748A/en active Pending
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20100318968A1 (en) * | 2009-06-15 | 2010-12-16 | Microsoft Corporation | Catalog-based software component management |
| CN109614137A (en) * | 2018-11-30 | 2019-04-12 | 北京字节跳动网络技术有限公司 | Software version control method, device, equipment and medium |
| CN109684414A (en) * | 2018-12-26 | 2019-04-26 | 百度在线网络技术（北京）有限公司 | Synchronous method, device, equipment and the storage medium of block data |
Non-Patent Citations (1)
| Title |
|---|
| 余颖, 董旭源, 高宏: "C/S模式管理信息系统实现自动升级和维护的方法", 佳木斯大学学报(自然科学版), vol. 23, no. 02, pages 201 - 203 * |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10990365B2 (en) | Container image building using dependency container images | |
| CN110673924B (en) | Multi-architecture container cloud mirror image selection method, device, equipment and storage medium | |
| CN107357721B (en) | Method and device for testing system | |
| CN115185550A (en) | Service deployment method, device, computer equipment and storage medium | |
| CN109871593B (en) | Information inheritance method and device based on BIM platform and storage device | |
| CN111984666A (en) | Database access method and device, computer readable storage medium and computer equipment | |
| CN111722995A (en) | Data processing method and device | |
| CN112631763A (en) | Program changing method and device of host program | |
| CN110201397B (en) | Game resource allocation method and device and electronic equipment | |
| CN114816772B (en) | Debugging method, debugging system and computing device for application running based on compatible layer | |
| CN112433748A (en) | Software system version calibration method and device, storage medium and processor | |
| CN113626342B (en) | Model online testing method and device | |
| CN115757172A (en) | Test execution method and device, storage medium and computer equipment | |
| CN109857450A (en) | A kind of verification service orchestration method and device | |
| CN113672349A (en) | Mirror image updating method, device, equipment and medium | |
| CN112559346A (en) | Service testing method and device | |
| CN110471708B (en) | Method and device for acquiring configuration items based on reusable components | |
| CN113867778A (en) | Method and device for generating mirror image file, electronic equipment and storage medium | |
| CN112559444A (en) | SQL (structured query language) file migration method and device, storage medium and equipment | |
| CN107291494B (en) | Method and device for generating application program installation package | |
| CN116700840B (en) | File execution method, device, electronic equipment and readable storage medium | |
| CN116700841B (en) | Method and device for calling native API (application program interface) | |
| CN117251234B (en) | Function calling method and device based on patches | |
| CN110019034A (en) | Formfile loading method and device | |
| CN110471782B (en) | Configuration information consistency processing method and device and electronic equipment |
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 |