Method for managing and controlling consistency of achievements and objects in whole life cycle of literature and blog informatization system

Abstract

The invention discloses a method for managing and controlling consistency of achievements and objects in the whole life cycle of a literature and blog informatization system. The method comprises the following steps: S1, constructing a special whole life cycle standardized achievement and object reference library in the literature and blog field; s2, establishing a unified version control and configuration management platform, and performing relevance management on all heterogeneous achievements; s3, setting mandatory consistency verification check points at key nodes of the project process to ensure that the process is controllable; s4, an automation and third-party verification mechanism based on objective standards is introduced, and acceptance subjectivity is reduced; wherein the reference library comprises a management type achievement list, an entity type achievement list and a quality check list. According to the method, the project output is standardized and normalized by establishing the full-life-cycle achievement list and the quality inspection standard special for the literature and blog industry, and the randomness is greatly reduced.

Description

Technical Field

[0001] This invention relates to the fields of information technology and digital management of cultural heritage, and in particular to a method for consistent control of the outputs of a cultural heritage information system throughout its entire lifecycle. Background Technology

[0002] Currently, the management of cultural heritage information projects mostly adopts general project management methods or combines some industry standards. Regarding the management of deliverables, the current technical status is as follows: General IT Project Management Methods: Several general software engineering or project management methods exist to guide project implementation, such as process control based on agile development and the waterfall model. These methods provide general frameworks for structured management and monitoring of deliverables at each stage of IT projects. The core of these frameworks is establishing the relationships between business models, requirements, design, and development deliverables, and conducting quality monitoring.

[0003] Isolated standards for cultural relic digitization: A series of industry standards have been published for the specific stage of cultural relic digitization, such as "Two-dimensional Digital Acquisition and Processing of Movable Cultural Relics" (WW / T 0114-2023), "Three-dimensional Digital Acquisition and Processing of Movable Cultural Relics" (WWT 0115-2023), "Three-dimensional Digital Acquisition and Processing of Grotto Temples" (WW / T 0117-2023), and "Systems and Software Engineering: System and Software Quality Requirements and Evaluation (SQuaRE) Part 51: Quality Requirements and Test Details for Ready-to-Use Software Products (RUSP)" (GB / T 25000.51-2016). These standards mainly regulate the technical parameters, processes, and quality requirements of a single stage (data acquisition).

[0004] Discrete tool applications: In project practice, teams use various independent tools to manage different types of deliverables. For example, they use version control systems such as Git and SVN to manage software code; they use NAS or shared servers to store digital resource files; they use tools such as Jira and Trello to track tasks and progress; and they use offline documents and forms to record acceptance checklists.

[0005] The aforementioned existing technologies have significant shortcomings and drawbacks when applied to the specific field of cultural heritage information systems: The lack of a standardized, end-to-end system adapted to the industry: General project management methods are not tailored to the cultural heritage sector. Their deliverables are generic and fail to encompass the unique digital content deliverables of cultural heritage projects (such as archaeological line maps, electronic rubbings, 3D models of artifacts, virtual reconstructions, and interactive exhibits). This leads to a disconnect between project management requirements and industry-specific outputs. Existing standards for cultural relic digitization focus only on the isolated "data acquisition" stage, failing to extend forward to project initiation and requirements analysis, or backward to content creation, system integration, and delivery acceptance. This results in a lack of unified guidelines for the management, application, and acceptance of acquired data in subsequent stages, easily creating "data silos" and process breakpoints.

[0006] Process disconnect and traceability difficulties: Due to the lack of a unified definition of deliverables covering the entire project lifecycle, it is difficult to establish an effective two-way traceability chain between the requirements and design documents in the early stages of a project and the specific deliverables in the later stages of development and production. When it is found that the final deliverable does not meet the design expectations, it is difficult to pinpoint whether the problem lies in the understanding of requirements, design deviations, or the implementation stage, resulting in high communication costs and difficulties in assigning responsibility.

[0007] Version and configuration management is chaotic: Deliverables in different formats, such as code, design documents, 3D models, and video and audio materials, are scattered across different management tools and storage locations, lacking a unified framework. This easily leads to problems such as incompatibility between digital content versions and software code versions, and failure to synchronize corresponding resource files after design document updates, resulting in inconsistencies within the deliverables.

[0008] The acceptance process is highly subjective and lacks quantifiable criteria: project acceptance relies heavily on the personal experience and subjective judgment of review experts, lacking a detailed, quantifiable, industry-standard-based checklist and objective evaluation methods. Disagreements easily arise regarding whether the quality of digital content (such as model accuracy, texture realism, and cultural accuracy) meets standards, leading to uncertainty in the acceptance process and creating potential risks to project quality.

[0009] Insufficient reuse and value mining of deliverables: Due to the decentralized management, inconsistent standards, and chaotic versions of deliverables, after the project ends, a large number of digital content deliverables (such as high-precision cultural relic models) are difficult to be effectively archived, managed, and reused in future exhibitions, research, or cultural and creative development, which reduces the long-term value of the project investment. Summary of the Invention

[0010] The purpose of this invention is to provide a method for consistency control of deliverables throughout the entire lifecycle of a cultural heritage information system. This method aims to solve the core consistency control problems caused by the lack of a unified standard that runs through both information system engineering and digital content production, the disconnect between process control and version management, and the chaos in version management throughout the entire lifecycle of cultural heritage information system construction. In particular, it focuses on solving specific technical problems that arise at the intersection of the three major processes, from the source of data collection to the construction of information systems and the production of digital content.

[0011] This invention is achieved using the following technical solution: a method for consistency management of deliverables throughout the entire lifecycle of a cultural heritage information system, comprising the following steps: S1: Construct a standardized benchmark library of full-lifecycle achievements specifically for the cultural heritage field; S2: Establish a unified version control and configuration management platform to manage the relationships between all heterogeneous results; S3: Set mandatory consistency verification checkpoints at key nodes in the project process to ensure process controllability; S4: Introduce automated and third-party verification mechanisms based on objective standards to reduce subjectivity in acceptance testing; The benchmark library includes a list of management deliverables, a list of physical deliverables, and a quality inspection checklist.

[0012] Furthermore, the management deliverables list is used to clearly define the types, content requirements, and templates of management documents that must be output at each stage of the project's entire lifecycle.

[0013] Furthermore, the list of entity deliverables is used to clearly define the technical specifications of all entity objects that are ultimately delivered by the project.

[0014] Furthermore, the list of physical deliverables includes a sub-list of digitally acquired deliverables, which is used to define in detail the outputs of the two-dimensional / three-dimensional data acquisition process for cultural relics, including their data format, data type, file format, accuracy indicators, and metadata requirements.

[0015] Furthermore, the list of physical deliverables includes a sub-list of digital content deliverables, which is used to define in detail the technical parameters, file formats, and presentation requirements of deliverables created based on the collected data.

[0016] Furthermore, the entity deliverable list includes a system deliverable sublist, which is used to define in detail the delivery requirements of the software system and hardware.

[0017] Furthermore, the quality checklist is used to define the corresponding quality inspection methods, qualification indicators, and the national / industry standards on which each type of deliverable is based.

[0018] Furthermore, step S2 specifically includes: Versioning of collected data: After data collection is completed, the original data and preprocessed data are immediately incorporated into the version control system, uniquely identified and stored, and their association with the collection task, cultural relic number, and collection technical solution is recorded. Establish relationships between deliverables: In a version control system, establish and maintain relationships between key deliverables through tags, branches, or metadata. Baseline management: At key project milestones, a complete set of interrelated deliverables in the current version repository is labeled with a baseline. All subsequent changes must be based on the latest baseline, and any changes must be reviewed and recorded to ensure that the historical state can be reproduced at any time.

[0019] Furthermore, step S3 specifically includes: Data Acquisition and Requirements Consistency Verification: After the data acquisition phase, the quality of the acquired data is verified according to the quality checklist, and the type and format of the acquired data are checked to see if they meet the subsequent development and integration requirements defined in the system requirements specification. Design and implementation consistency verification: During the development and content production stages, code review, unit testing, and integration testing are used to verify whether the code implementation is consistent with the design documents; model review and content review are used to verify whether the digital content deliverables are consistent with the design document scheme. Delivery and baseline consistency verification: During the delivery phase, all deliverables delivered by Party B will be compared one by one with the standardized deliverables benchmark library in the contract annex to check their completeness; at the same time, the records of the version control system will be used to verify whether the delivered software, content and data versions are consistent with the final tested and passed versions, and to prevent unauthorized replacements.

[0020] Furthermore, step S4 specifically includes: Automated tool validation: Develop or adopt automated tools to automatically check quantifiable metrics; Third-party evaluation: Submit the software system for third-party evaluation to obtain software product quality test reports, information security level protection evaluation reports, and commercial cryptography evaluation reports; compare the quality inspection results of digital content results with industry standards to form an objective basis for acceptance.

[0021] The beneficial effects of this invention are as follows: 1. Enhance standardization and regulation: By establishing a dedicated list of deliverables and quality inspection standards for the entire life cycle of the cultural heritage industry, project outputs will be standardized and regulated, significantly reducing arbitrariness.

[0022] 2. Ensure process controllability and traceability: Consistency control is brought forward and implemented throughout the requirements, design, development and acceptance stages, achieving an effective closed loop and two-way traceability between requirements and results, making it easier to identify the source of problems.

[0023] 3. Ensure the quality and consistency of deliverables: Through version control and baseline management, ensure that delivered deliverables are consistent with the expected version; through built-in quality checklists and third-party evaluations, provide objective and reliable assurance for the quality of deliverables.

[0024] Improved efficiency and objectivity in acceptance: It provides clear and quantifiable evidence for project acceptance, reduces subjective disagreements in the acceptance process, improves acceptance efficiency and fairness, and reduces project risks. Attached Figure Description

[0025] To more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on the structures shown in these drawings without creative effort.

[0026] Figure 1 This is a flowchart of the present invention. Detailed Implementation

[0027] To make the objectives, technical solutions, and advantages of the embodiments of the present invention clearer, the technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. The components of the embodiments of the present invention described and shown in the accompanying drawings can generally be arranged and designed in various different configurations.

[0028] It should be noted that similar labels and letters in the following figures indicate similar items. Therefore, once an item is defined in one figure, it does not need to be further defined and explained in subsequent figures.

[0029] The following detailed description of some embodiments of the present invention is provided in conjunction with the accompanying drawings. Unless otherwise specified, the following embodiments and features can be combined with each other.

[0030] See Figure 1 A method for consistency management of deliverables throughout the entire lifecycle of a cultural heritage information system includes the following steps: Step 1: Construct a standardized benchmark database of cultural heritage outputs covering the entire lifecycle of their products. First, a structured, standardized benchmark library of deliverables is defined and constructed. This library serves as the benchmark for all subsequent consistency comparisons and contains three core categories: List of Management Deliverables: Clearly define the types, content requirements, and templates of management documents (such as requirements specifications, system design documents, test reports, and acceptance reports) that must be output at each stage of the project lifecycle (project initiation, procurement, implementation, and acceptance).

[0031] List of Physical Deliverables: This list clearly defines the technical specifications of all physical objects ultimately delivered by the project. This list is further divided into: a) List of digital acquisition results: Define in detail the outputs of the two-dimensional / three-dimensional data acquisition process for cultural relics, including their data form (such as point cloud, grid), data type (such as archaeological line map, electronic rubbing), file format (such as LAS, OBJ, TIFF), accuracy indicators (such as resolution, point error) and metadata requirements (acquisition time, equipment, personnel, etc.).

[0032] b) Digital Content Deliverables Sublist: This sublist details the technical parameters, file formats, and presentation requirements of deliverables (such as 3D animation, VR content, and interactive applications) created based on the collected data.

[0033] c) System deliverables sublist: Detailed definition of the delivery requirements for software systems (such as source code, executable programs, database scripts, API interface documentation) and hardware (model, configuration).

[0034] Quality checklist: For each type of deliverable, especially digital acquisition and digital content deliverables, define the corresponding quality inspection methods, qualification indicators, and the national / industry standards on which they are based (e.g., referencing WW / T 0115-2023 to check the quality of 3D models).

[0035] Step two: Implement version control and related management throughout the entire process of data collection, production, and system development, and establish a unified version control and configuration management platform to manage the relationships between all heterogeneous results. Versioning of collected data: After data collection is completed, the original data (such as original images and scanned data) and the preprocessed data (such as generated point clouds and models) are immediately incorporated into the version control system, uniquely identified and stored, and their association with the collection task, cultural relic number, and collection technical solution is recorded.

[0036] Establish deliverable relationships: In a version control system, establish and maintain relationships between key deliverables through tags, branches, or metadata. For example, associate the code version of a software function module with the version of the 3D model asset it calls. Associate the version of a system test report with the software version and digital content version being tested at that time. Ensure that the version of the database structure script is consistent with the version of the application that depends on that structure.

[0037] Baseline management: At key project milestones (such as passing requirements review or design review), a complete set of interrelated deliverables (requirements documents, design documents, code, models, etc.) in the current version repository is tagged with a baseline. All subsequent changes must be based on the latest baseline, and any changes must be reviewed and recorded to ensure that the historical state can be reproduced at any time.

[0038] Step 3: Establish consistency verification checkpoints at key process nodes. At critical nodes in the project process, set mandatory consistency verification checkpoints to ensure process controllability. Data Acquisition and Requirements Consistency Verification: After the data acquisition phase, the quality of the acquired data is verified according to the quality checklist. At the same time, the type and format of the acquired data are checked to see if they meet the subsequent development and integration requirements defined in the system requirements specification.

[0039] Design and implementation consistency verification: In the development and content production stages, methods such as code review, unit testing, and integration testing are used to verify whether the code implementation is consistent with the design documents; model review and content review are used to verify whether the digital content deliverables are consistent with the design documents and other solutions.

[0040] Delivery and baseline consistency verification: During the delivery phase, all deliverables delivered by Party B will be compared one by one with the standardized deliverables benchmark library in the contract annex to check their completeness; at the same time, the records of the version control system will be used to verify whether the delivered software, content and data versions are consistent with the final tested and passed versions, and to prevent unauthorized replacements.

[0041] Step four: Introduce automated and third-party verification mechanisms based on objective standards. To reduce subjectivity in acceptance testing, objective verification methods are introduced. Automated tool verification: Develop or adopt automated tools to automatically check quantifiable metrics. For example, scripts can automatically verify whether the database table structure is consistent with the design document, check whether the model file format and size meet predetermined specifications, and batch verify whether the image resolution meets the standards.

[0042] Third-party evaluation: It is mandatory to submit the software system for third-party evaluation to obtain software product quality test reports, information security level protection evaluation reports, commercial cryptography evaluation reports, etc.; compare the quality inspection results of digital content products with industry standards to form an objective basis for acceptance.

[0043] Through the synergistic effect of the above four technical solutions, a complete closed loop is formed from "defining standards" to "process control" and then to "result verification," which ultimately and systematically solves the problem of consistency of deliverables throughout the entire life cycle of cultural heritage informatization projects.

[0044] The invention will be further illustrated by an example. Project Initiation Phase: Establishing the Requirements Baseline Organize business users, industry experts, and technical experts to conduct requirements demonstration, analyze existing pain points, and form a "Requirements Demonstration Report" to clarify project construction goals, platform / system functions, and other requirements; formulate a "Requirements Specification", establish the requirements baseline after being signed and confirmed by all three parties, and incorporate it into the configuration management system.

[0045] Procurement Phase: Third Parties and Data Security Constraints The procurement documents and contracts clearly state that: third-party components must provide localized installation packages and authorization letters, and internet-based dependencies are prohibited; cultural relic data must be stored on the local server designated for this project, and backup strategies must be adopted to ensure project data security; and a project team (including the construction unit, design and implementation unit, supervision unit, third-party supervision agency, and other stakeholders) must be formed.

[0046] Implementation Phase: Design Baseline, Development Baseline, and Digital Content Governance (1) Design phase: Establishment of design baseline Software design: Output the "System Preliminary Design Specification" and the "System Detailed Design Specification"; Digital content design: Collect relevant reports and research literature to form the "Basic Data Collection and Research Report"; compile the "Overall Planning Outline for Digital Content" and the "Data Acquisition Plan"; After the design documents were reviewed and approved by relevant cultural heritage experts and technical experts, the design baseline was established.

[0047] (2) Development phase: Development baseline and version management Software Development: Development branches are created, and developers write code according to coding standards and commit to the branch daily; if third-party development libraries are introduced, they must be downloaded to the local server for testing before being included in the private repository; after peer review and unit testing, the code is merged into the main branch; Digital content creation: Data Acquisition: Develop and adhere to the "Data Acquisition Plan", use relevant equipment to collect data, verify data in real time, and generate a "Data Acquisition Consistency Verification Report"; Content processing: The data was processed and optimized according to requirements and then reviewed by cultural relics experts (confirming that there was no cultural bias). Quality inspection: In accordance with Appendix C, check the data quality, and re-verify after rectifying any non-conforming items.

[0048] Delivery and Acceptance Phase: Acceptance Baseline and Consistency Verification (1) Preliminary acceptance The supervising unit checked the completeness of the deliverables (including source code, cultural relic data, and design documents) against the checklist in Appendix A; verified the platform's functions (data query and model display were normal) against the baseline requirements; output the "Preliminary Acceptance Report"; and proposed the rectification item of "adding a model rotation speed adjustment function".

[0049] (2) Trial operation Determine the number of days for trial operation, carry out trial operation work, record system failure rate and user feedback, complete rectification items, and output the "Trial Operation Report".

[0050] (3) Final acceptance Third-party assessment: Passing the requirements of third-party assessments such as information security compliance assessment, system quality assessment (conducted according to relevant quality standards and the quality inspection checklist in Appendix C), and commercial cryptography evaluation; Verification of deliverables: Compare with the acceptance baseline to confirm that the software version is consistent with the deployment version and that the MD5 value of the cultural relic data is consistent with the data acquisition stage; Expert review: The acceptance committee (including cultural relics and technical experts) unanimously agreed to pass the acceptance and issued the "Final Acceptance Report".

[0051] According to the lists in Appendix A and Appendix B, the deliverables are checked again, and the deliverables are tailored according to the actual situation of the project. After all parties reach a consensus on completeness, the deliverables are formally handed over.

[0052] Through the above implementation methods, the present invention ensures that all deliverables of cultural heritage projects, from a blueprint to the final delivery, remain clear, controllable, and consistent.

[0053] Appendix A includes a list of deliverables for each stage of the project construction. Table A.1 List of deliverables at each stage of project construction

[0054] Appendix B includes a list and description of the results of the collection and processing of cultural relic data, and a list of digital content results for display and utilization, as shown in the table.

[0055] Table B.1 List and Description of Results of Cultural Relics Data Collection and Processing

[0056] Table B.2 List and Description of Digital Content Deliverables for Cultural Relics Display and Utilization

[0057] Appendix C includes the content and methods for quality inspection of digital content production results from cultural heritage sites. Table C.1 Quality Inspection Contents and Methods for Digital Content Production Deliverables

[0058] For the foregoing embodiments, in order to simplify the description, they are all described as a series of actions. However, those skilled in the art should understand that this application is not limited to the described order of actions, because according to this application, some steps can be performed in other orders or simultaneously. Furthermore, those skilled in the art should also understand that the embodiments described in the specification are preferred embodiments, and the actions involved are not necessarily essential to this application.

[0059] The above embodiments describe the basic principles, main features, and advantages of the present invention. Those skilled in the art should understand that the present invention is not limited to the above embodiments. The embodiments and descriptions in the specification are merely illustrative of the principles of the invention. Modifications and variations made by those skilled in the art without departing from the spirit and scope of the invention should be within the protection scope of the appended claims.

Claims

1. A method for consistency management of deliverables throughout the entire lifecycle of a cultural heritage information system, characterized in that, Includes the following steps: S1: Construct a standardized benchmark library of full-lifecycle achievements specifically for the cultural heritage field; S2: Establish a unified version control and configuration management platform to manage the relationships between all heterogeneous results; S3: Set mandatory consistency verification checkpoints at key nodes in the project process to ensure process controllability; S4: Introduce automated and third-party verification mechanisms based on objective standards to reduce subjectivity in acceptance testing; The benchmark library includes a list of management deliverables, a list of physical deliverables, and a quality inspection checklist.

2. The method for consistency management of deliverables throughout the entire lifecycle of a cultural heritage information system as described in claim 1, characterized in that, The management deliverables list is used to clearly define the types, content requirements, and templates of management documents that must be output at each stage of the project's entire life cycle.

3. The method for consistency management of deliverables throughout the entire lifecycle of a cultural heritage information system as described in claim 1, characterized in that, The list of entity deliverables is used to clearly define the technical specifications of all entity objects that are ultimately delivered by the project.

4. The method for consistency management of deliverables throughout the entire lifecycle of a cultural heritage information system as described in claim 3, characterized in that, The list of physical deliverables includes a sub-list of digital acquisition deliverables, which defines in detail the outputs of the two-dimensional / three-dimensional data acquisition process for cultural relics, including their data format, data type, file format, accuracy indicators, and metadata requirements.

5. A method for consistency management of deliverables throughout the entire lifecycle of a cultural heritage information system as described in claim 3, characterized in that, The list of physical deliverables includes a sub-list of digital content deliverables, which is used to define in detail the technical parameters, file formats, and presentation requirements of deliverables for display and utilization after processing and creating based on the collected data.

6. A method for consistency management of deliverables throughout the entire lifecycle of a cultural heritage information system as described in claim 3, characterized in that, The entity deliverables list includes a system deliverables sublist, which is used to define in detail the delivery requirements of software systems and hardware.

7. A method for consistency management of deliverables throughout the entire lifecycle of a cultural heritage information system as described in claim 1, characterized in that, The quality checklist is used to define the corresponding quality inspection methods, qualification indicators, and the national / industry standards on which each type of deliverable is based.

8. A method for consistency management of deliverables throughout the entire lifecycle of a cultural heritage information system as described in claim 1, characterized in that, Step S2 specifically includes: Versioning of collected data: After data collection is completed, the original data and preprocessed data are immediately incorporated into the version control system, uniquely identified and stored, and their association with the collection task, cultural relic number, and collection technical solution is recorded. Establish relationships between deliverables: In a version control system, establish and maintain relationships between key deliverables through tags, branches, or metadata. Baseline management: At key project milestones, a complete set of interrelated deliverables in the current version repository is labeled with a baseline. All subsequent changes must be based on the latest baseline, and any changes must be reviewed and recorded to ensure that the historical state can be reproduced at any time.

9. A method for consistency management of deliverables throughout the entire lifecycle of a cultural heritage information system as described in claim 1, characterized in that, Step S3 specifically includes: Data Acquisition and Requirements Consistency Verification: After the data acquisition phase, the quality of the acquired data is verified according to the quality checklist, and the type and format of the acquired data are checked to see if they meet the subsequent development and integration requirements defined in the system requirements specification. Design and implementation consistency verification: During the development and content production stages, code review, unit testing, and integration testing are used to verify whether the code implementation is consistent with the design documents; model review and content review are used to verify whether the digital content deliverables are consistent with the design document scheme. Delivery and baseline consistency verification: During the delivery phase, all deliverables delivered by Party B will be compared one by one with the standardized deliverables benchmark library in the contract annex to check their completeness; at the same time, the records of the version control system will be used to verify whether the delivered software, content and data versions are consistent with the final tested and passed versions, and to prevent unauthorized replacements.

10. A method for consistency management of deliverables throughout the entire lifecycle of a cultural heritage information system as described in claim 1, characterized in that, Step S4 specifically includes: Automated tool validation: Develop or adopt automated tools to automatically check quantifiable metrics; Third-party evaluation: Submit the software system for third-party evaluation to obtain software product quality test reports, information security level protection evaluation reports, and commercial cryptography evaluation reports; compare the quality inspection results of digital content results with industry standards to form an objective basis for acceptance.

Images