Software Evaluation Data Maintenance System

Abstract

The present invention provides a software evaluation data maintenance system, which includes: an electronic data package file set, a visual data operation interface, a data import module, and a database management interface, which can realize four main functions: input document parsing function, data classification storage function, data encryption and management function, and electronic document generation function. The present invention optimizes the entire process of software evaluation, realizes structured data management of the software evaluation process, and effectively solves the drawbacks of data management in the existing software evaluation process, such as cumbersome work, poor maintainability, data inconsistency risk, low data processing efficiency when the version of the tested component is upgraded, and high dependence on the type and version of the third-party editor. In addition, the system takes the electronic data package file set as the core and supports multi-terminal editing and review.

Description

Technical Field

[0001] Maintenance system The present invention relates to a software evaluation data maintenance system. Technical Background

[0002] The continuous development of computer technology has provided more possibilities for software evaluation data management and efficiency improvement. Traditional software evaluation data management mostly adopts two methods: paper documents and electronic documents. Among them, considering the problems of editing and printing, electronic documents are mostly processed by Word or Excel files that are convenient for multi-type data input; paper documents are mostly generated by printing electronic documents.

[0003] In actual applications, the traditional electronic documents mentioned above require manual editing and typesetting of data during the production process, which has the disadvantages of cumbersome work, poor maintainability, risk of data inconsistency, low data processing efficiency when the version of the tested device is upgraded, and high dependence on the type and version of third-party editors and device processors. For example, in a software evaluation project, evaluators need to write a set of documents such as plans, requirements, instructions, use cases, records, problem sheets, suggestion sheets, reports, etc. in sequence according to a certain template or format. The editing and typesetting of each document takes a lot of time; in the process of software evaluation, for the update or adjustment of test data, it is necessary to maintain and update all documents related to the data one by one; the data carried by all documents revolve around the core tested device. In other words, a part of the data of the tested device needs to be repeatedly presented in multiple documents. Errors in manual editing and typesetting will lead to the risk of inconsistent document data; when the version of the tested software is upgraded, the corresponding electronic documents need to be upgraded and re-edited and typeset according to the change requirements of the tested device. Traditional electronic documents are highly dependent on third-party editors and devices. Take the example of using Word office software on an i5 processor computer to edit a test case form or a test record form. Assuming the test record form is 6*14, there will be obvious lag when the number of test records exceeds 2000. If the number of forms exceeds 5000, there will be a risk of errors in opening and saving the document. Summary of the invention

[0004] In view of the above, it is necessary to propose a software evaluation data maintenance system, which can effectively complete the whole process data management of software evaluation and automatically generate complete electronic documents according to user needs.

[0005] A software evaluation data maintenance system includes: an electronic data package file set, a visual data operation interface, a data import module, and a database management interface, and can realize four main functions: input document parsing function, data classification storage function, data encryption and management function, and electronic document generation function. Hereinafter, a structured software evaluation data maintenance system for dynamic input is referred to as an evaluation data maintenance system.

[0006] The electronic data package file set mentioned above includes but is not limited to electronic documents (Word, XML, Excel, etc.), pictures, configuration files and other electronic information that can carry data information. The electronic data package file set is a collection of all data and formats that are input, generated, and output within a complete evaluation cycle of a certain software (including the first round and regression). The electronic data package file set can be used for data transfer between different users. At the same time, users are divided into permissions and levels, and users with different permissions have different parsing permissions for a certain electronic data package file set. For example, after writer A writes a record of the evaluation project, he passes the electronic file set to writer B, and writer B can open the electronic file set through the software for secondary editing. Similarly, the entire splitting function based on the electronic data package file set supports different evaluators to write and merge the same project.

[0007] The core data storage unit of the evaluation data maintenance system is the basic data structure of software evaluation. The above-mentioned electronic data package file set includes one or more complete basic data structures. The basic data structure of software evaluation is not limited to: multi-version test data (the present invention names it as test version), electronic document management (including but not limited to template documents, configuration information documents, output documents, etc., the present invention names it as test documents), other information associated with the evaluation data maintenance system or adding and expanding the system data structure function (the present invention names it as other information);

[0008] The test version data structure described above includes but is not limited to: the current tested software type (named as full set / regression flag in the present invention), the current tested software version number (named as software version number in the present invention), the actual test data structure of the current tested software (named as test method in the present invention), the data structure of all problem sheets of the current version (named as problem sheet file in the present invention), the data structure of all suggestion sheets proposed in the current version (named as suggestion sheet file in the present invention), the data structure of the traceability relationship of the test data of the current version (named as traceability table file in the present invention), the analysis data structure of the impact of the current version software change on the test status (named as impact domain analysis table in the present invention), other information data structures associated with the current version or added and extended to the system data structure function (named as other information in the present invention), and statistical information;

[0009] The test method data structure described above includes but is not limited to: a basic information data structure of the current test (including document information, personnel information, version information, etc., which is named basic information in the present invention), a data structure classified according to the test type (which is named static test and dynamic test in the present invention), a data structure recording the start and end time of the current test (which is named start time and end time respectively in the present invention), other information data structures associated with the current test method or adding and expanding the system data structure function (which is named other information in the present invention), and statistical information;

[0010] The above-mentioned static test structure is the same as the dynamic test data structure (it can be separated or combined according to the actual application), taking the static test structure as an example, it includes but is not limited to: the current test information data structure (the present invention names it as type), the basic information data structure of the current test (including document information, personnel information, version information, etc., the present invention names it as basic information), the test item data structure divided according to the test content (the present invention names it as test item), other information data structures associated with the current test type or adding and expanding the system data structure function (the present invention names it as other information), and statistical information;

[0011] The test item structure described above includes but is not limited to: a basic information data structure of the current test (including document information, personnel information, version information, etc., which is named basic information in the present invention), an identification data structure for marking the current test item (which is named test item identification in the present invention), a test case single data structure that can be used for test execution under the current test item (which is named test case in the present invention), a set of executable use cases that currently reuse other test items (which is named reused use case in the present invention), other information data structures associated with the current test item or that add and expand the system data structure function (which is named other information in the present invention), and statistical information;

[0012] The test case structure mentioned above includes but is not limited to: the number of the current test case (named as number in the present invention), the type of the current test case (named as test type in the present invention), the status information of the current test case (named as status in the present invention), the single information of the current test case (named as use case information in the present invention), other information data structures associated with the current test case or adding and extending the system data structure function (named as other information in the present invention), and statistical information;

[0013] The test status structure mentioned above includes but is not limited to: software version information of the current test case (named as software version in the present invention), description of the status of the current test case in the entire test process (including but not limited to addition, modification, use, deletion, editing, named as current status in the present invention);

[0014] The static reuse use case structure described above adopts a structure equivalent to the test method data structure;

[0015] The above-mentioned problem ticket file structure includes but is not limited to: a problem ticket data structure describing all the data in the problem ticket (the present invention refers to it as problem ticket data), statistical information of various types of information of all problem tickets in the current version (the statistics are divided into two types: number statistics and percentage statistics, which are referred to as statistics in the present invention);

[0016] The above-mentioned suggestion single data structure adopts a structure equivalent to the problem single data structure;

[0017] The traceability table file structure mentioned above includes but is not limited to: a traceability table data set structure classified according to data source (named as data in the present invention), a traceability table table data structure classified according to different stages or file requirements in the evaluation process (named as table in the present invention);

[0018] The test document data structure mentioned above includes but is not limited to: data structures of basic information of all input and output electronic documents of the system (including but not limited to number, type, confidentiality level, name, mark, author, proofreader, reviewer, approver, version, etc., which is named as document information in the present invention), complete source file information of the test document (which is named as source file in the present invention), format information data structures of the layout and style of all system-related input and output electronic documents (which is named as document style in the present invention);

[0019] The other information data structure described above adopts a dictionary query structure.

[0020] The above-mentioned visual data operation interface includes but is not limited to: a visual human-computer interaction interface and a database interface, an authentication module for identifying the identity of the operator, a data import module for importing various types of evaluation-related data, a functional module for parsing input data, an operation authority control module for editing and viewing by users of different identities or levels (for example, the control of document editing authority by different identities such as writers, proofreaders, reviewers, approvers, and the control of data acquisition authority by different levels of personnel such as software evaluators and project managers, and the operation control authority should be reflected in the visual data operation interface), a document output module for outputting evaluation documents, a module for filling in evaluation data and format settings, a data merging module for merging multiple basic data units, and a data upload module for connecting to a server. The import of data elements includes character strings including text formulas, electronic document layout and style-related format adjustment function modules, and the program segments of the function modules are used to fill the data content into the corresponding positions in the data structure; a data import module is used to read data from the electronic data package file set and display it on the visual interaction interface, and users can also edit and modify the data at the corresponding positions on the visual interaction interface.

[0021] The data import module function described above includes the program segment that completes the module function and related supporting interfaces, which is specifically embodied in, but not limited to, electronic document data import, configuration file and template data import, and interface data import. The electronic document data import requires a reserved data import extension interface to realize the parsing and import of a variety of electronic document data, including but not limited to reports generated by various software testing and analysis tools on the market, user-defined electronic data documents, etc.; the configuration file and template data import refers to the system being able to make personalized parameter and format customizations based on the user; the interface data import refers to the user editing the electronic data file set in the visual operation interface. The path selection for importing data includes static path file input and dynamic path file input, of which the static path is mostly used to input templates, configuration files and other information; the dynamic path includes but is not limited to allowing users to open related content through the path of the output electronic document or electronic data package file set in the visual human-computer interaction interface.

[0022] The above-mentioned database management interface is used to expand the connection server. On the one hand, the completed electronic data package file set can be uploaded to the server for storage; on the other hand, data can be exchanged and merged between the server and other co-evaluators; on the other hand, it provides the possibility of separating the client and the server in the future and completing remote server data editing.

[0023] The input document parsing function described above includes a program segment that completes the module function and related supporting interfaces, which is specifically embodied in the parsing of information such as reading configuration files, templates, and electronic data package file sets. The reading of configuration files refers to the program segment that reads the configuration files through a predetermined path when the document is started, and configures, displays, caches, and stores the read information through the program segment, while the visual human-computer interaction interface provides an operation method for refreshing the configuration file information, and the user modifies and saves the configuration file information through the visual human-computer interaction interface; the reading of template documents refers to the program segment that reads the template document through a predetermined path when the software is started, and stores the read template document information in the corresponding electronic data folder structure through the program segment, and displays the document information such as style and layout, font configuration, pictures and tables and other content and formats on the human-computer interaction interface, and the user can configure and modify the template document data, format and other information through the visual human-computer interaction interface and choose whether to update it to the template document.

[0024] The data classification storage function mentioned above includes the program segments that complete the functions of this module and related supporting interfaces. The implementation of this function is mainly completed around the basic data structure. Users fill the data elements in the software evaluation process into the basic data structure according to the data type and classification through the human-computer interaction interface or input documents, and together form an electronic data package file set. At the same time, the authentication of operation permissions is completed through the data classification storage function program segment to realize the control of data modification permissions.

[0025] The data encryption and management function mentioned above includes the program segments that complete the functions of this module and the related supporting interfaces. This function includes using encryption algorithms to encrypt and mark the electronic data package file set according to the confidentiality level and the permitted access level. When different users parse and view the electronic data package file set through the data maintenance system, they need to complete identity confirmation and confidentiality level proofreading before they can be displayed on the visual operation interface. At the same time, when the electronic data package file set is opened through other editors such as image viewers, decompression software, Office software, etc., password confirmation is required for viewing.

[0026] The electronic document generation function module mentioned above includes a program segment that outputs the electronic document functions and related supporting interfaces required by the user according to the user's needs, and uses the program segment to set the layout, style and font of all data elements in the electronic document, so as to generate a complete electronic document (the electronic documents that can be generated include but are not limited to plans, requirements, instructions, use case sheets, record sheets, problem sheets, suggestion sheets, reports, traceability relationship tables, etc.);

[0027] The definition of "including but not limited to" mentioned above is that the items described are basic sub-items of the general item, but in actual applications, according to user needs, deleting the sub-items or adding items that are similar to the sub-items and included in the general item should all fall within the scope of the description of the present invention.

[0028] Finally, it should be noted that the above embodiments are only used to illustrate a preferred technical solution of a structured software evaluation data maintenance system for dynamic input of the present invention and are not intended to be limiting. Although the present invention has been described in detail with reference to the preferred embodiments, those skilled in the art should understand that the counting scheme of the present invention may be modified or replaced by equivalents without departing from the spirit and scope of the technical solution of the present invention. BRIEF DESCRIPTION OF THE DRAWINGS

[0029] Figure 1 It is a system architecture diagram of the present invention. DETAILED DESCRIPTION

[0030] The embodiment of the present invention is described in detail with reference to the accompanying drawings. This embodiment is implemented based on the technical solution of the present invention, and a detailed implementation method and a specific operation process are given, but the protection scope of the present invention is not limited to the following embodiment. This embodiment is executed by a system of a full test flow of a certain software test.

[0031] See Figure 1 , a single terminal is a complete evaluation data maintenance system. It supports stand-alone operation and reserves communication interfaces with the server and other terminals.

[0032] See Figure 1 The terminal includes an electronic data package file set, a visual data operation interface, a data import module, and a database management interface, which can realize four major functions: input document parsing function, data classification storage function, data encryption and management function, and electronic document generation function.

[0033] In the core content basic data structure of the electronic data package file set, List represents that there can be multiple tables under the general item of the project; BaseTable represents that the project is reflected as a table in the data structure, and has table-related information such as table notes and numbers; NodeData represents the data element of the project as the basic data unit, which includes not only the original data information, but also the data style and other information, such as font size and attributes, formula alignment and superscript, picture format and parameters, etc.

Claims

1. A software evaluation data maintenance system, characterized in that: include: The electronic data package file set, visual data operation interface, data import module and database management interface are used to realize the four major functions of input document parsing, data classification storage, data encryption and management, and electronic document generation. The system is centered on the electronic data package file set and supports multi-terminal editing and review. In the electronic data package file set, all data in the complete software evaluation process only use one electronic data package file set, and one electronic data package file set includes one or more basic data structures; the electronic data package file set includes electronic documents, pictures and configuration files of Word, XML and Excel that carry or express data information; in terms of data sharing, it supports single-machine operation analysis to achieve interactive transmission between different clients and servers; in terms of security, when different users parse and view the electronic data package file set through the data maintenance system, they need to complete identity confirmation and confidentiality level proofreading before they can be displayed on the visual operation interface; In terms of project collaboration, the electronic data package file set supports splitting and merging, and supports different evaluators to write and merge the same project; The basic data structure includes: multiple versions of test data for the same software under test, electronic document management, maintenance system evaluation data, and other information associated with the maintenance system or that increases and expands the system data structure function; The structure of multi-version test data of the same software under test, including: the type of the current software under test, the version number of the current software under test, the actual test data structure of the current software under test, the data structure of all problem tickets of the current version, the data structure of all suggestion tickets proposed by the current version, the data structure of the traceability relationship of the test data of the current version, the analysis data structure of the impact of the changes of the current version of the software on the test status, and other information data structures and statistical information associated with the current version or added to the system data structure function; The actual test data structure of the current software under test includes: a basic information data structure of the current test, a data structure classified according to the test type, a data structure recording the start and end time of the current test, other information data structures associated with the current test method or adding and expanding the system data structure function, and statistical information; The data structure classified according to the test type includes: the static test structure and the dynamic test structure are the same, wherein the static test structure includes the current test information data structure, the basic information data structure of the current test, the test item data structure divided according to the test content, and other information data structures and statistical information associated with the current test type or added to the system data structure function; The test item data structure divided according to the test content includes: the basic information data structure of the current test, the identification data structure for marking the current test item, the test case single data structure that can be used for test execution under the current test item, the executable case set that currently reuses other test items, the other information data structure and statistical information associated with the current test item or added to the system data structure function; The test case single data structure that can be used for test execution under the current test item includes: the number of the current test case, the type of the current test case, the status information of the current test case, the current test case single information, other information data structures and statistical information associated with the current test case or adding extensions to the system data structure function; The structure of the status information of the current test case, including: the software version information of the current test case and the description of the status of the current test case during the entire test process; The test item data structure divided according to the test content also includes a static reuse case structure, and the static reuse case structure adopts the same structure as the actual test data structure of the current software under test; The current version of all problem ticket data structures includes: a problem ticket data structure describing all data in the problem ticket and statistical information of various types of information of all problem tickets in the current version; All suggestion data structures proposed in the current version adopt the same structure as all question data structures in the current version; The previous version test data traceability relationship data structure includes: a traceability table data set structure classified by data source and a traceability table table data structure classified according to different stages or file requirements in the evaluation process; The electronic document management structure includes: a data structure of basic information of all input and output electronic documents of the system, complete source file information of the test document, and a data structure of format information of the layout and style of all input and output electronic documents related to the system; The data structure of the other information adopts a dictionary query structure to facilitate quick query; The data import module includes three types: electronic document data import, configuration file and template data import, and interface data import; wherein, the electronic document data import needs to reserve a data import extension interface to realize the analysis and import of diversified electronic document data, including reports generated by various software testing and analysis tools on the market and user-defined electronic data documents; the configuration file and template data import refers to the system making personalized parameters and format customization according to the user; the interface data import refers to the user editing the electronic data file set in the visual operation interface; The visual data operation interface includes: a visual human-computer interaction interface and a database interface module, an authentication module for identifying the identity of the operator, a data import module for importing various types of evaluation-related data, a functional module for parsing input data, an operation authority control module for editing and viewing by users of different identities or levels, a document output module for outputting evaluation documents, a module for filling in evaluation data and formatting, a data merging module for merging multiple basic data units, and a data uploading module for connecting to a server; The database management interface module is used to expand the program segment of the server function. First, the completed electronic data package file set is uploaded to the server for storage; second, data interaction and merging are performed between the server and other co-evaluators; third, it is possible to separate the client from the server in the future and complete remote server data editing; The database management interface module includes: a program segment that completes the functions of the database management interface module and related supporting interfaces, which is reflected in the parsing of information on reading configuration files, templates, and electronic data package file sets; a program segment that reads configuration files through a predetermined path when the document is started, and configures, displays, and caches the read information through the program segment, while a visual human interaction interface provides an operation method for refreshing configuration file information, and a user modifies and saves configuration file information through a visual human-computer interaction interface; reading template documents refers to a program segment that reads template documents through a predetermined path when the software is started, and through the program segment The program segment stores the read template document information into the corresponding electronic data folder structure, and displays the document information including style and format, font configuration, content and format of pictures and tables on the human-computer interaction interface, and the user configures and modifies the template document data and format information through the visual human-computer interaction interface and chooses whether to update it to the template document. In addition to supporting the parsing of basic data structures, this functional module reserves an interface for parsing electronic documents exported by evaluation tools commonly used in the field of software evaluation, and supports parsing the evaluation tool conclusion file into evaluation data and importing it into the electronic data file for centralized storage; The data classification storage function module includes: a program segment that completes the functions of the data classification storage function module and related supporting interfaces. The data classification storage function is realized around the basic data structure. The user fills the data elements in the software evaluation process into the basic data structure according to the data type and classification through the human-computer interaction interface or input documents, and together constitutes an electronic data package file set; at the same time, the authentication of operation authority is completed through the data classification storage function program segment to realize the control of data modification authority; The data encryption and management function module includes: a program segment that completes the functions of the data classification storage function module and related supporting interfaces, and uses an encryption algorithm to encrypt and mark the electronic data package file set according to the confidentiality level and the allowed access level; when different users parse and view the electronic data package file set through the data maintenance system, they need to complete identity confirmation and confidentiality level proofreading before they can be displayed on the visual operation interface; at the same time, when the electronic data package file set is opened through other editors including image viewers, decompression software and Office software, password confirmation is required for viewing; The electronic document generation function includes: outputting the electronic document function and related supporting interface program segments required by the user according to the user's needs, and using the program segments to set the layout, style and font of all data elements in the electronic document, thereby generating a complete electronic document, wherein the layout, style and font format of the data elements are derived from the pre-configured template document; The support for multi-terminal editing and review includes: supporting single-machine analysis and realizing interactive transmission between different clients and servers.

Images