CN110716740A - Distributed embedded software resource integration platform and use method - Google Patents
Distributed embedded software resource integration platform and use method Download PDFInfo
- Publication number
- CN110716740A CN110716740A CN201910906781.3A CN201910906781A CN110716740A CN 110716740 A CN110716740 A CN 110716740A CN 201910906781 A CN201910906781 A CN 201910906781A CN 110716740 A CN110716740 A CN 110716740A
- Authority
- CN
- China
- Prior art keywords
- software
- software package
- package
- conf
- log
- 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
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 belongs to the technical field of application software downloading, and particularly relates to a distributed embedded software resource integration platform and a use method thereof, wherein the platform comprises a software package warehouse module sw _ store, a compatibility check module mat _ module, a software package configurator conf _ gen, a software package integrator pack _ gen and an independently arranged software package log analyzer log _ anal which are arranged at a network server end and are sequentially connected; the invention integrates all the software packages into one or a group of homogenous compiling units at last, can be compiled by using the same compiling environment, is convenient for quickly establishing projects on various tool chains and architectures, and really realizes the cross-architecture and cross-environment universality of the software packages.
Description
Technical Field
The invention belongs to the technical field of application software downloading, and particularly relates to a distributed embedded software resource integration platform and a use method.
Background
At present, functions of the embedded system are more and more diversified, the number of used software modules is increased day by day, and the difficulty of software package resource integration is also rapidly increased.
The current embedded software platform cannot well integrate various software resources, which causes the management confusion of software packages and greatly increases the difficulty of configuration and the possibility of configuration errors.
The existing embedded software package management platform usually downloads the software package to the local and then manually configures and compiles the software package by a user, so that the following defects exist:
1. version management is chaotic, and version compatibility among software packages is difficult to guarantee, so that a plurality of errors which are difficult to check and unpredictable in compiling, linking and running are caused.
2. The software package has the advantages of large number of small files, slow downloading, slow engineering migration, pressure on a server and a local storage system, and difficult software package upgrading.
3. The lack of a uniform description and construction strategy for each software package leads to increased interface incompatibility and frequent errors resulting therefrom.
4. The compiling environments of the software packages are very complex and different from each other, so that the software packages are bound on two architectures and tool chains and are difficult to be truly universal.
5. Complicated scripts need to be executed or commands need to be input manually when the software package is pulled from the warehouse, so that user experience is greatly deteriorated, and the error probability of pulling the software package by a user is increased.
6. When a software package encounters an error during use, it is very difficult to locate the error because it is difficult to determine which software package failed and therefore it is difficult for the development team to fix the error.
For example, the Chinese patent application number is: the patent of CN201310484666.4 discloses an intelligent downloading method, device and system for application software; the intelligent downloading method of the application software comprises the following steps: receiving an application software downloading request sent by terminal equipment, wherein the application software downloading request bears an application software icon; acquiring an application software icon from the application software downloading request; carrying out image matching on the application software icon in a preset application software icon set; and under the condition that the matched application software icon exists in the application software icon set, acquiring the application software corresponding to the matched application software icon according to the preset corresponding relation between the application software icon and the application software, and downloading the application software to the terminal equipment.
Disclosure of Invention
The invention aims to provide a distributed embedded software resource integration platform and a use method thereof aiming at the defects of the prior art so as to integrate various software resources.
The platform of the invention comprises: the system comprises a software package warehouse module sw _ store, a compatibility check module, a software package configurator conf _ gen, a software package integrator pack _ gen and an independently arranged software package log analyzer log _ anal which are arranged at a network server end and connected in sequence;
the software package warehouse module sw _ store is used for storing a source code src and a description file sw _ desc of the software package;
the compatibility checking module, namely, the complex _ module, is used for checking the interface compatibility between the software packages and the architecture compatibility of the software packages;
the software package configurator conf _ gen is used for configuring each software package sw _ pack;
the software package integrator pack _ gen is used for generating a final software package sw _ final;
and the software package log analyzer log _ anal is used for collecting and analyzing the logs sw _ log and the software package configuration list sw _ conf returned by the software runtime, analyzing the errors of various software packages in the logs sw _ log according to an error analysis flow dev _ filter provided by a software package developer, and generating an operation error analysis report anal _ report and sending the operation error analysis report to the developer.
The software package warehouse module sw _ store supports the login of multiple software package developers, each software package developer has read permission and write permission, and participates in the editing of one or more software packages; the edited content is uploaded to a software package warehouse module sw _ store and downloaded by other collaborators for editing, and a formal version of the software package is released after the editing is completed or reaches a certain stage, wherein the formal version of the software package comprises a source code src and a description file sw _ desc, and the description file sw _ desc comprises a configuration mode supported by software, and a compatible interface and framework;
one or more software package warehouse modules sw _ store are arranged in the distributed embedded software resource integration platform, or the distributed embedded software resource integration platforms share the same software package warehouse module sw _ store.
The compatibility check module, the compot _ module, is also used to read the software module list sw _ list provided by the end software user and generate an appropriate configuration list sw _ conf for the software package that is compatible with each other and with the user's hardware.
The software package configurator conf _ gen is used for reading the configuration list sw _ conf and correctly configuring the source code for the software package.
The software package integrator pack _ gen is used for reading the software packages configured by the software package configurator conf _ gen, generating a final software package sw _ final and supplying the final software package to the end software user for downloading through network transmission.
The use method of the distributed embedded software resource integration platform comprises the following steps:
step 1, storing a source code and a description file of a software package by adopting a software package warehouse module sw _ store;
step 2, adopting a compatibility checking module, namely, a complex _ module to check the interface compatibility between the software packages and the architecture compatibility of the software packages; the specific flow of the compatibility check module, namely, the component _ module, comprises the following steps:
step 21, reading a software module list sw _ list provided by a final software user or other components which do not belong to the platform, confirming the name of the selected software package, the required hardware platform and the selected configuration thereof, and writing the configuration list sw _ conf according to the requirement of the selected software package on the required hardware platform;
step 22, downloading a description file sw _ desc of the selected software package from the software package warehouse module sw _ store, determining a dependent package of the selected software package by scanning the description file sw _ desc, and adding configuration information of the dependent package into a configuration list sw _ conf; further downloading a description file sw _ desc of the dependent package from the software package warehouse module sw _ store, scanning and confirming the secondary dependent package, and adding the configuration information of the secondary dependent package into a configuration list sw _ conf; repeating the step until all the directly or indirectly depended software packages are configured and added into the list sw _ conf;
step 23, when the software package can not be configured correctly to be compatible with other software packages or hardware platforms, replacing the software package with other software packages with the same function; when the software package which can be replaced or the alternative solution cannot be found finally, prompting configuration error information conf _ err to a final software user;
step 24, when the configuration mode passes, determining the content of the sw _ conf and outputting the content to a file;
step 3, reading the configuration list sw _ conf by adopting a software package configurator conf _ gen, and correctly configuring the software package;
step 4, reading the software package configured by the software package configurator conf _ gen by adopting a software package integrator pack _ gen, generating a final software package sw _ final and transmitting the final software package sw _ final through a network to supply software users for downloading; the specific flow of the software package integrator pack _ gen comprises the following steps:
step 41, reading a software package configuration file sw _ conf, and completing the construction of a dependency directed tree or graph among software packages, wherein a father node in the tree or the graph depends on all child nodes directly connected with the father node;
step 42, reading the source code of each software package configured by the software package configurator conf _ gen;
step 43, connecting header files and source files in the software package into a new source file which is used as one or a group of homogeneous compiling units according to the designation of the configuration list sw _ conf of the software package, and determining the connection sequence according to a certain method, wherein the method comprises but is not limited to the subsequent traversal of a dependency tree, as long as all the dependencies of the software package are ensured to be connected or declared to be in front of the software package in the source file generated by the method;
step 44, packaging the configuration list sw _ conf description file of the software package and the single source file to generate a new final software package sw _ final;
step 5, collecting and analyzing a log sw _ log returned by software operation and a software package configuration list sw _ conf by using a software package log analyzer log _ anal, analyzing errors of various software packages in the log sw _ log according to an error analysis process dev _ filter provided by a software package developer, generating an operation error analysis report anal _ report and sending the operation error analysis report to the developer, wherein the specific process of the software package log analyzer log _ anal comprises the following steps:
step 51, a final software user collects a software running log sw _ log from an embedded device of the final software user and uploads the software running log to a distributed embedded software resource integration platform end;
and 52, uploading the software package configuration list sw _ conf to the distributed embedded software resource integration platform end by the final software user.
Step 53, the software package log analyzer log _ anal reads the running log sw _ log and the software package configuration list sw _ conf and analyzes the related independent software package sw _ pack;
step 54, the log analyzer log _ anal of the software package reads the error analysis flow dev _ filter of each related software package;
step 55, the software package log analyzer respectively operates the error analysis processes dev _ filter specified by the developers of the individual software packages sw _ pack on the operation log sw _ log and the software package configuration list, and obtains an analysis report anal _ report aiming at each individual software package sw _ pack;
and 56, the software package log analyzer log _ anal respectively sends the running error analysis report anal _ report of each independent software package sw _ pack to the software package developers subscribing the analysis reports.
The invention has the beneficial effects that:
1. the distributed embedded software resource integration platform has simple version management, and because the dependence and compatibility are completely managed by the platform, a user does not need to worry about the problem that the self-downloaded discrete software packages are incompatible, thereby reducing the burden of the user.
2. The distributed embedded software resource integration platform has simple software package downloading, and because all software packages are finally integrated into a source file with one or a group of homogeneous compiling units to be provided as a final software package, a user only needs to download an integrated final software package without downloading a separate software package, thereby reducing the pressure of local storage and server bandwidth.
3. According to the distributed embedded software resource integration platform, each software package has an independent and homogeneous description file and the same construction strategy, and the possibility of interface incompatibility is reduced, so that the chance of unpredictable errors in compatibility is reduced.
4. According to the distributed embedded software resource integration platform, all software packages are integrated into one or a group of homogeneous compiling units, namely one or a few homogeneous source files, so that the same compiling environment can be used for compiling, engineering can be conveniently and rapidly established on various tool chains and architectures, and cross-architecture and cross-environment universality of the software packages is really realized.
5. According to the distributed embedded software resource integration platform, the software package is pulled from the warehouse only by providing the software list by the end user, the dependent software package which is not indicated by the user in the software list is determined by automatic dependent analysis, the configuration of the software package is automatically determined by the hardware information input by the user, the software package pulling and configuration burden of the user is reduced, and the error probability is reduced.
6. According to the distributed embedded software resource integration platform, when the software runs and encounters an error, the running log is printed, and the log is uploaded by a user, so that the difficulty of submitting an error report to a developer team by the user is greatly reduced; the process also greatly facilitates the software package upgrading of the user, and the user does not need to manually complete the process of replacing the software package at will because the software package is finally regenerated, thereby saving the time of the user and reducing the possibility of wrong version or error in the upgrading process.
7. The distributed embedded software resource integration platform also provides a log analyzer, and a software developer can extract interested parts or description modes suitable for a team from a large number of logs of a client without directly facing mails or problem lists of the user, so that the problem positioning speed of the embedded software developer is greatly reduced, and the possibility of understanding ambiguity caused by direct communication with the client is reduced.
Drawings
FIG. 1 is a schematic structural diagram of a distributed embedded software resource integration platform according to the present invention;
FIG. 2 is a schematic data flow diagram of a software resource integration platform of the distributed embedded software resource integration platform according to the present invention;
FIG. 3 is a schematic diagram of the content structure of the software package sw _ pack according to the present invention;
FIG. 4 is a schematic content structure diagram of a description file sw _ desc of the software package according to the present invention;
FIG. 5 is a diagram illustrating a content structure of a configuration list sw _ conf according to the present invention;
FIG. 6 is a diagram illustrating the content structure of the configuration error message conf _ err according to the present invention;
FIG. 7 is a diagram illustrating the content structure of the final software package sw _ final according to the present invention;
FIG. 8 is a diagram illustrating a content structure of a log sw _ log according to the present invention;
FIG. 9 is an algorithm flow of the error analysis flow dev _ filter according to the present invention;
FIG. 10 is a diagram illustrating the content structure of the running error analysis report, and _ report, according to the present invention;
FIG. 11 is a flowchart of embodiment 1 of the present invention;
fig. 12 is a schematic diagram of a software module list sw _ list 110 in embodiment 1 of the present invention;
fig. 13 is a schematic diagram of a configuration list sw _ conf 160 in embodiment 1 of the present invention;
FIG. 14 is a schematic operational flow diagram of the software package configurator conf _ gen 210 according to embodiment 1 of the present invention;
FIG. 15 is a flowchart illustrating the operation of the package integrator pack _ gen 240 according to embodiment 1 of the present invention;
FIG. 16 is a flowchart of embodiment 2 of the present invention;
fig. 17 is a schematic diagram of a software module list sw _ list 410 in embodiment 2 of the present invention;
fig. 18 is a schematic operation flow chart of the cloud-side tool in embodiment 2 of the present invention;
FIG. 19 is a flowchart of the operation of the log analyzer log _ anal 500 in phase 1 according to embodiment 2 of the present invention;
fig. 20 is a flowchart illustrating the operation of the log analyzer log _ anal 500 in the phase 2 according to the embodiment 2 of the present invention.
Detailed Description
The invention is further described below with reference to the accompanying drawings.
As shown in fig. 1, a distributed embedded software resource integration platform includes: the system comprises a software package warehouse module sw _ store, a compatibility check module, a software package configurator conf _ gen, a software package integrator pack _ gen and an independently arranged software package log analyzer log _ anal which are arranged at a network server end and connected in sequence;
the software package warehouse module sw _ store is used for storing a source code src of the software package and a description file sw _ desc shown in fig. 4;
the compatibility checking module, namely, the complex _ module, is used for checking the interface compatibility between the software packages and the architecture compatibility of the software packages;
a software package configurator conf _ gen for configuring each software package sw _ pack shown in fig. 3;
a software package integrator pack _ gen for generating a final software package sw _ final as shown in FIG. 7;
the software package log analyzer log _ anal is used for collecting and analyzing the log sw _ log shown in fig. 8 and the configuration list sw _ conf shown in fig. 5 returned by the software runtime, analyzing errors of various software packages in the log sw _ log according to the error analysis flow dev _ filter provided by the software package developer and shown in fig. 9, and generating a running error analysis report anal _ report shown in fig. 10 and sending the running error analysis report to the developer.
The software package warehouse module sw _ store supports the login of multiple software package developers, and each software package developer has certain authority to participate in the editing of one or more software packages; the edited content is uploaded to a software package warehouse module sw _ store and downloaded by other collaborators for editing, and a formal version of the software package is released after the editing is completed or reaches a certain stage, wherein the formal version of the software package comprises a source code src and a description file sw _ desc, and the description file sw _ desc comprises a configuration mode supported by software, and a compatible interface and framework;
one or more software package warehouse modules sw _ store are arranged in the distributed embedded software resource integration platform, or the distributed embedded software resource integration platforms share the same software package warehouse module sw _ store.
The compatibility check module, the compot _ module, is also used to read the software module list sw _ list provided by the end software user and generate an appropriate configuration list sw _ conf for the software package that is compatible with each other and with the user's hardware.
The software package configurator conf _ gen is used for reading the configuration list sw _ conf and correctly configuring the source code for the software package.
The software package integrator pack _ gen is used for reading the software packages configured by the software package configurator conf _ gen and generating a final software package sw _ final, the codes of the final software package sw _ final are logically one or a group of homogeneous source files and can be compiled as one or a group of homogeneous compiling units, and the final software package sw _ final is transmitted through a network and supplied to a final software user for downloading.
As shown in fig. 2, a method for using a distributed embedded software resource integration platform includes the following specific steps:
step 1, storing a source code and a description file of a software package by adopting a software package warehouse module sw _ store;
step 2, a compatibility checking module, namely, a complex _ module, is adopted to check the interface compatibility between the software packages and the architecture compatibility of the software packages, and the specific flow comprises the following steps:
1) reading a software module list sw _ list provided by a final software user or other components which do not belong to the platform, confirming the name of the selected software package, the required hardware platform and the selected configuration thereof, and writing the software module list sw _ conf into the configuration list sw _ conf according to the requirement of the selected software package on the required hardware platform;
2) downloading a description file sw _ desc of the selected software package from the software package warehouse module sw _ store, determining a dependent package of the selected software package by scanning the description file sw _ desc, and adding configuration information of the dependent package into a configuration list sw _ conf; further downloading a description file sw _ desc of the dependent package from the software package warehouse module sw _ store, scanning and confirming the secondary dependent package, and adding the configuration information of the secondary dependent package into a configuration list sw _ conf; repeating the step until all the directly or indirectly depended software packages are configured and added into the list sw _ conf;
3) when a software package cannot be correctly configured to be compatible with other software packages or hardware platforms, replacing the software package with other software packages with the same function; when a replaceable software package or a replaceable solution cannot be found finally, prompting a configuration error message conf _ err shown in fig. 6 to an end software user;
4) and when the configuration mode passes, determining the content of the sw _ conf and outputting the content to a file.
Step 3, reading the configuration list sw _ conf by adopting a software package configurator conf _ gen, and correctly configuring source codes for the software package;
step 4, reading the software package configured by the software package configurator conf _ gen by using the software package integrator pack _ gen, generating a final software package sw _ final and transmitting the final software package sw _ final through a network for a software user to download, wherein the specific flow comprises the following steps:
1) reading a software package configuration file sw _ conf, and completing the construction of a dependency directed tree or a graph among software packages, wherein a father node in the tree or the graph depends on all child nodes directly connected with the father node;
2) reading the source codes of the software packages configured by the software package configurator conf _ gen;
3) connecting header files and source files in the software package into a new source file which is used as one or a group of homogeneous compiling units according to the designation of a configuration list sw _ conf of the software package, and determining the connection sequence of the source files according to a set method, wherein the method comprises but is not limited to the subsequent traversal of a dependency tree, as long as all the dependencies of the software package are ensured to be connected or declared to be in front of the software package in the source files generated by the method;
4) and packaging the configuration list sw _ conf description file of the software package and the single source file to generate a new final software package sw _ final.
Step 5, collecting and analyzing a log sw _ log and a software package configuration list sw _ conf returned by software running by using a software package log analyzer log _ anal, analyzing errors of various software packages in the log sw _ log according to an error analysis process dev _ filter provided by a software package developer, and generating a running error analysis report anal _ report and sending the running error analysis report to the developer; the specific process comprises the following steps:
1) a final software user collects a software running log sw _ log from an embedded device of the final software user and uploads the software running log to the distributed embedded software resource integration platform end;
2) and finally, the software user uploads the software package configuration list sw _ conf to the end of the distributed embedded software resource integration platform.
3) The software package log analyzer log _ anal reads the running log sw _ log and the software package configuration list sw _ conf and analyzes the related independent software packages sw _ pack;
4) reading error analysis processes dev _ filter of each involved software package by a software package log _ anal;
5) the software package log analyzer respectively operates error analysis processes dev _ filter specified by developers of all the independent software packages sw _ pack on the operation log sw _ log and the software package configuration list, and obtains an analysis report and report of each independent software package sw _ pack;
6) and the software package log analyzer log _ anal respectively sends the running error analysis report anal _ report of each discrete software package sw _ pack to a software package developer subscribing the analysis report, so that the software package log analyzer can conveniently find out the fault.
Example 1
The list of software modules sw _ list 110 shown in FIG. 12 includes two initially selected software packages, one is the network protocol stack 120 and one is the file system 130, and also contains a characterization of the hardware platform.
As shown in fig. 11:
step 300: and finally, the software user submits the software module list sw _ list 110 to the server side.
Step 310: the configuration parser module, compat _ module, 200 on the server side reads the list of software modules 110.
Step 320: the configuration analyzer module 200 first determines that the network protocol stack module 120 needs to rely on a certain network card driver and the file system 130 needs to rely on a certain Flash driver by reading the software package descriptions shown in fig. 4 of the two software packages.
Step 330: the configuration analyzer module 200 then determines the network card driver 140 and the Flash driver 150 suitable for use according to the hardware platform feature description file contained in the software module list sw _ list 110, and outputs the suitable configuration of each software package to the configuration list sw _ conf 160 shown in fig. 5 and fig. 13.
Step 340: as shown in fig. 14, the software package configurator conf _ gen 210 reads the configuration list sw _ conf 160, downloads the network protocol stack 120, the file system 130, the network card driver 140 and the Flash driver 150 from the remote warehouse sw _ store 220 and the remote warehouse sw _ store 230, respectively, and correctly configures the source code of the corresponding software package according to the configuration list sw _ conf 160.
Step 350: as shown in FIG. 15, the package integrator pack _ gen 240 reads the configuration list sw _ conf 160 and the correctly configured packages in step 340, concatenates the source code into a single compilation unit, and integrates into the final package sw _ final 170 as shown in FIG. 7.
Step 360: the user downloads the generated final software package sw _ final 170, and the compilable part of the software package only has one source file and one header file.
In this embodiment, the distributed embedded software resource integration platform correctly configures the used four software packages through an analysis process.
Finally, the distributed embedded software resource integration platform integrates the four software packages into a final software package which only comprises one compiling unit and is used for downloading by a user, so that the process of downloading the discrete software package by the user is omitted, the network bandwidth and the energy and time of the user are saved, and the user can conveniently establish a project for compiling. The difficulty of software package configuration and downloading and the difficulty of engineering establishment are greatly simplified, and the efficiency of embedded system configuration is greatly improved.
The order of the above steps is not absolute, and when there is no interdependence between the two steps, it is allowed to exchange the order arbitrarily.
Example 2
The software module list sw _ list 410 shown in FIG. 17 includes three software packages: a motion control software package 420, a communications software package 430, and a system management software package 440, and the software module list sw _ list 410 also contains a characterization of the hardware platform.
As shown in fig. 16:
step 600: as shown in fig. 18, the end software user transmits the software module list sw _ list 410 to the cloud tool, and after configuration by the cloud tool, a final software package sw _ final 450 finally suitable for the end software user is generated, which includes integration of the motion control software package 420, the communication software package 430, and the system management software package 440.
Step 610: the end software user downloads the end software package sw _ final 450 to the local and uses it in the project.
Step 620: and finally, the software user observes that the system fails in operation and collects an operation log sw _ log 460.
Step 630: the end software user uploads a run log sw _ log460 to the server.
Step 640: starting a log analyzer log _ anal 500 in the server, reading an operation log sw _ log460 uploaded by the end software user, and analyzing that 3 discrete software packages are used in a final software package sw _ final 460 of the end software user: a motion control software package 420, a communications software package 430, and a system management software package 440.
Step 650: as shown in fig. 19, the log analyzer log _ anal 500 downloads the error analysis processes corresponding to the 3 discrete software packages from the software package warehouse sw _ store 510: motion control software package error analysis flow 520, communication software package error analysis flow 530, and system management software package error analysis flow 540.
Step 660: as shown in fig. 20, the log analyzer log _ anal 500 runs a motion control software package error analysis process 520, a communication software package error analysis process 530 and a system management software package error analysis process 540 on a running log sw _ log460, respectively, and generates three error reports: motion control package error report 550, communication package error report 560, and system management package error report 570.
Step 670: the log analyzer log _ anal 500 sends the three error reports to the motion control software package development team 580, the communication software package development team 585 and the system management software package development team 590, respectively.
Step 680: the three development teams receive the error report and correct the errors in the software package, and the end software user transmits the sw _ conf of the old end software package sw _ final 450 obtained in the step 600 to the server to obtain a new end software package sw _ final 470 without errors, so that the debugging and upgrading of the software package are completed.
In the embodiment, the final software package sw _ final 460 initially containing an error prints a running log sw _ log460 capable of being analyzed by the log analyzer log _ anal 500 when the error occurs, the running logs are respectively sent to three teams for error correction, and after the error correction, the final software user reruns and generates a software package without problems.
From the perspective of the final software user, the steps greatly simplify the difficulty of submitting an error report to a developer team by the final software user, and because the operation log sw _ log460 is automatically generated, the final software user does not need to intervene, the software package upgrading by the final software user is greatly facilitated, and because the final software package can be regenerated, the final software user does not need to manually complete the process of replacing the software package, the time of the final software user is saved, and the possibility of version error or error in the upgrading process is reduced. From the perspective of an embedded software development team, a customized and objective analysis process is provided, interested parts or description modes suitable for the team can be extracted from a large number of logs of a client, a mail or a problem list of a final software user does not need to be directly faced, and direct communication with the final software user is not needed, so that the time of useless labor of an embedded software developer is greatly reduced, the problem positioning speed is greatly increased, and the possibility of understanding ambiguity caused by direct communication with the client is reduced.
The order of the flow of the respective steps of the above embodiment is not absolute, and when there is no interdependence between the two steps, the order is allowed to be arbitrarily interchanged with each other.
It will be apparent to those skilled in the art that various modifications and variations can be made in the embodiments of the present invention without departing from the spirit or scope of the embodiments of the invention. It is intended that the present invention cover the modifications and variations of this embodiment provided they come within the scope of the appended claims and their equivalents.
Claims (10)
1. A distributed embedded software resource integration platform is characterized by comprising: the system comprises a software package warehouse module sw _ store, a compatibility check module, a software package configurator conf _ gen, a software package integrator pack _ gen and an independently arranged software package log analyzer log _ anal which are arranged at a network server end and connected in sequence;
the software package warehouse module sw _ store is used for storing a source code src and a description file sw _ desc of the software package;
the compatibility checking module, namely, the complex _ module, is used for checking the interface compatibility between the software packages and the architecture compatibility of the software packages;
the software package configurator conf _ gen is used for configuring each software package sw _ pack;
the software package integrator pack _ gen is used for generating a final software package sw _ final;
and the software package log analyzer log _ anal is used for collecting and analyzing the logs sw _ log and the software package configuration list sw _ conf returned by the software runtime, analyzing the errors of various software packages in the logs sw _ log according to an error analysis flow dev _ filter provided by a software package developer, and generating an operation error analysis report anal _ report and sending the operation error analysis report to the developer.
2. The distributed embedded software resource integration platform as claimed in claim 1, wherein the software package warehouse module sw _ store supports login of multiple software package developers, each software package developer has read rights and write rights including but not limited to, and participates in editing one or more software packages; and uploading the edited content to a software package warehouse module sw _ store, downloading the content by other collaborators for editing, and releasing a formal version of the software package after the editing is finished or reaches a certain stage, wherein the formal version of the software package comprises a source code src and a description file sw _ desc, and the description file sw _ desc comprises a configuration mode supported by software, and a compatible interface and a compatible framework.
3. The distributed embedded software resource integration platform according to claim 1, wherein one or more software package warehouse modules sw _ store are disposed in the distributed embedded software resource integration platform, or a plurality of distributed embedded software resource integration platforms share a same software package warehouse module sw _ store.
4. A distributed embedded software resource integration platform according to claim 1, wherein said compatibility check module, match _ module, is further configured to read a list of software modules sw _ list provided by an end software user and generate a list of appropriate configurations sw _ conf for software packages that are compatible with each other and with the user hardware.
5. The distributed embedded software resource integration platform as claimed in claim 1, wherein the software package configurator conf _ gen is configured to read the configuration list sw _ conf and correctly configure the source code for the software package.
6. The distributed embedded software resource integration platform as claimed in claim 1, wherein the software package integrator pack _ gen is configured to read the software package configured by the software package configurator conf _ gen, generate the final software package sw _ final and provide the final software package for downloading by the final software user through network transmission.
7. The use method of the distributed embedded software resource integration platform aiming at the claim 1 is characterized by comprising the following specific steps:
step 1, storing a source code and a description file of a software package by adopting a software package warehouse module sw _ store;
step 2, adopting a compatibility checking module, namely, a complex _ module to check the interface compatibility between the software packages and the architecture compatibility of the software packages;
step 3, reading the configuration list sw _ conf by adopting a software package configurator conf _ gen, and correctly configuring the software package;
step 4, reading the software package configured by the software package configurator conf _ gen by adopting a software package integrator pack _ gen, generating a final software package sw _ final and transmitting the final software package sw _ final through a network to supply software users for downloading;
and 5, collecting and analyzing the logs sw _ log and the software package configuration list sw _ conf returned by the software runtime by using a software package log analyzer log _ anal, analyzing the errors of various software packages in the logs sw _ log according to an error analysis process dev _ filter provided by a software package developer, and generating an operation error analysis report anal _ report and sending the operation error analysis report to the developer.
8. The method as claimed in claim 7, wherein in the step 2, the specific process of the compatibility check module, that is, the component _ module, comprises the following steps:
1) reading a software module list sw _ list provided by a final software user or other components which do not belong to the platform, confirming the name of the selected software package, the required hardware platform and the selected configuration thereof, and writing the software module list sw _ conf into the configuration list sw _ conf according to the requirement of the selected software package on the required hardware platform;
2) downloading a description file sw _ desc of the selected software package from the software package warehouse module sw _ store, determining a dependent package of the selected software package by scanning the description file sw _ desc, and adding configuration information of the dependent package into a configuration list sw _ conf; further downloading a description file sw _ desc of the dependent package from the software package warehouse module sw _ store, scanning and confirming the secondary dependent package, and adding the configuration information of the secondary dependent package into a configuration list sw _ conf; repeating the step until all the directly or indirectly depended software packages are configured and added into the list sw _ conf;
3) when a software package cannot be correctly configured to be compatible with other software packages or hardware platforms, replacing the software package with other software packages with the same function; when the replaceable software package or the replaceable solution cannot be found finally, prompting configuration error information conf _ err to a final software user;
4) and when the configuration mode passes, determining the content of the sw _ conf and outputting the content to a file.
9. The method according to claim 7, wherein in the step 4, the specific process of the software package integrator pack _ gen includes the following steps:
1) reading a software package configuration file sw _ conf, and completing the construction of a dependency directed tree or a graph among software packages, wherein a father node in the tree or the graph depends on all child nodes directly connected with the father node;
2) reading the source codes of the software packages configured by the software package configurator conf _ gen;
3) connecting header files and source files in the software package into a new source file which is used as one or a group of homogeneous compiling units according to the designation of a configuration list sw _ conf of the software package, and determining the connection sequence according to a certain method, wherein the method comprises but is not limited to the subsequent traversal of a dependency tree, as long as all the dependencies of the software package are connected or declared to be in front of the software package in the source file generated by the method;
4) and packaging the configuration list sw _ conf description file of the software package and the single source file to generate a new final software package sw _ final.
10. The method as claimed in claim 7, wherein in step 5, the specific process of the package log analyzer log _ anal includes the following steps:
1) a final software user collects a software running log sw _ log from an embedded device of the final software user and uploads the software running log to the distributed embedded software resource integration platform end;
2) and finally, the software user uploads the software package configuration list sw _ conf to the end of the distributed embedded software resource integration platform.
3) The software package log analyzer log _ anal reads the running log sw _ log and the software package configuration list sw _ conf and analyzes the related independent software packages sw _ pack;
4) reading error analysis processes dev _ filter of each involved software package by a software package log _ anal;
5) the software package log analyzer respectively operates error analysis processes dev _ filter specified by developers of all the independent software packages sw _ pack on the operation log sw _ log and the software package configuration list, and obtains an analysis report and report of each independent software package sw _ pack;
6) and the software package log analyzer log _ anal respectively sends the running error analysis report anal _ report of each independent software package sw _ pack to a software package developer subscribing the analysis report.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910906781.3A CN110716740A (en) | 2019-09-24 | 2019-09-24 | Distributed embedded software resource integration platform and use method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910906781.3A CN110716740A (en) | 2019-09-24 | 2019-09-24 | Distributed embedded software resource integration platform and use method |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN110716740A true CN110716740A (en) | 2020-01-21 |
Family
ID=69210797
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910906781.3A Pending CN110716740A (en) | 2019-09-24 | 2019-09-24 | Distributed embedded software resource integration platform and use method |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110716740A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115766164A (en) * | 2022-11-08 | 2023-03-07 | 云南电网有限责任公司信息中心 | Unified authentication management's automation instrument sharing platform |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101515232A (en) * | 2008-02-21 | 2009-08-26 | 卓望数码技术（深圳）有限公司 | Software continuous integration system and method |
| CN104820602A (en) * | 2015-05-18 | 2015-08-05 | 北京瑞星信息技术有限公司 | Method, device and system for publishing software package |
| US20160210126A1 (en) * | 2015-01-15 | 2016-07-21 | Xerox Corporation | Methods and systems for crowdsourcing software development project |
| CN110045982A (en) * | 2019-03-28 | 2019-07-23 | 宋子杰 | A kind of embedded system configuration method based on source code polymerization |
-
2019
- 2019-09-24 CN CN201910906781.3A patent/CN110716740A/en active Pending
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101515232A (en) * | 2008-02-21 | 2009-08-26 | 卓望数码技术（深圳）有限公司 | Software continuous integration system and method |
| US20160210126A1 (en) * | 2015-01-15 | 2016-07-21 | Xerox Corporation | Methods and systems for crowdsourcing software development project |
| CN104820602A (en) * | 2015-05-18 | 2015-08-05 | 北京瑞星信息技术有限公司 | Method, device and system for publishing software package |
| CN110045982A (en) * | 2019-03-28 | 2019-07-23 | 宋子杰 | A kind of embedded system configuration method based on source code polymerization |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115766164A (en) * | 2022-11-08 | 2023-03-07 | 云南电网有限责任公司信息中心 | Unified authentication management's automation instrument sharing platform |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US6983400B2 (en) | Distributed test harness model | |
| CN110851135A (en) | Automatic application program building and uploading method and device, computer equipment and storage medium | |
| CN110380939B (en) | Consistency test method and system for local communication protocol in electricity consumption information acquisition system | |
| CN106155724B (en) | Upgrading method and device | |
| CN109768970B (en) | Configurable universal protocol generation method | |
| CN107632829A (en) | A kind of App automation continuous integration systems and method based under iOS system | |
| US7210120B2 (en) | CLI configuration dump command support generation | |
| CN109614109B (en) | Application deployment method, device and system | |
| EP1179776A1 (en) | Test automation framework | |
| CN112953983A (en) | SFTP transmission method and device | |
| CN110716740A (en) | Distributed embedded software resource integration platform and use method | |
| CN111832273A (en) | Method and device for determining destination message, storage medium and electronic device | |
| JPH11143730A (en) | Method for testing computer system device | |
| WO2020000810A1 (en) | Application component construction packaging method and device, and computer storage medium | |
| CN113495750B (en) | Upgrade detection method and device for equipment and server | |
| CN115914055A (en) | Distributed network testing method, device, medium and equipment | |
| CN114020604A (en) | Workflow-based automatic testing method and device | |
| Vučnik et al. | Integrating research testbeds into social coding platforms | |
| Bracciali et al. | Adapting components with mismatching behaviours | |
| CN111082984A (en) | Method and device for simulating login of network equipment to carry out command line interaction | |
| CN112445513A (en) | Installation package processing method and device | |
| CN116700771B (en) | Remote development management method, remote development management apparatus, and readable storage medium | |
| Wincierz | A Tool Chain for Test-driven Development of Reference Net Software Components in the Context of CAPA Agents. | |
| CN117743059A (en) | Processor testing method and device, electronic equipment and readable storage medium | |
| Lange et al. | Integrating OPC UA Devices in EPICS |
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 |