Methods, systems, media, and products for multi-role behavior evidence storage in software factories

By building a decentralized trust network and differentiated storage strategies within the software factory platform, and adopting an aggregated signature consensus mechanism, parallel alliance chains are established for management, development, testing, and operation and maintenance teams, solving the problems of node collusion to tamper with data and insufficient storage in the software factory, and achieving efficient and secure behavior evidence storage.

CN123123357APending Publication Date: 2026-11-17NAT UNIV OF DEFENSE TECH
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202611182784.3
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2026-08-05
Publication Date
2026-11-17

AI Technical Summary

Technical Problem

Existing technologies cannot effectively build decentralized trust in software factories, leading to nodes colluding to tamper with evidence of data storage. Furthermore, traditional blockchain solutions are insufficient in terms of performance and storage, failing to meet the high efficiency, energy saving, and tamper-proof requirements of software factories.

Method used

A decentralized trust network is built within the software factory platform, employing consortium blockchains and aggregated signature consensus mechanisms. Parallel consortium blockchains are established for management, development, testing, and operations teams, and transactions are initiated uniformly through differentiated storage strategies and a centralized platform to ensure efficient and secure data storage.

Benefits of technology

It enables efficient and secure behavior evidence storage in centralized platforms, prevents nodes from colluding to tamper with data, reduces storage overhead, improves the standardization and reliability of transaction processing, and builds an efficient and trustworthy evidence storage system.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN123123357A_ABST
    Figure CN123123357A_ABST
Patent Text Reader

Abstract

This invention discloses a method, system, medium, and product for multi-role behavior evidence storage in software factories. The method involves constructing a decentralized trust network composed of nodes from management, development, testing, and operations teams within the software factory. Each team builds a consortium blockchain based on blockchain technology. When evidence storage of a member's behavior within a specific team is required, the software factory platform node of the management team initiates transaction packaging and block generation. The corresponding team verifies the business logic, while other team nodes provide signature endorsement. The transaction is confirmed through a consensus mechanism based on aggregated signatures across the four teams. The generated block is only submitted to the consortium blockchain constructed by the team nodes after confirmation from all four teams. This invention aims to solve the technical problem of building decentralized trust and achieving efficient and reliable behavior evidence storage in a centralized environment.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This invention relates to the field of blockchain technology, specifically to a method, system, medium, and product for storing evidence of multi-role behaviors in software factories. Background Technology

[0002] The software factory model is the core collaborative paradigm of modern software engineering. Multiple roles, such as development, testing, operation and maintenance, and management, need to collaborate on a unified platform to complete the entire life cycle of software development activities. In this process, it is crucial to ensure that the behavior of each team member (such as code submission, test execution, and deployment) is immutable and traceable, especially when problems such as online failures occur, to clearly define responsibilities and avoid disputes. In the existing technology, although there are various behavior evidence storage schemes, they all have significant limitations: (1) Centralized evidence storage system (such as database-based audit logs): Data is stored in a central database, which has the risk of single point of failure and internal tampering. Its credibility depends on the single credit of the platform operator. (2) Traditional blockchain evidence storage schemes often adopt public chain or large consortium chain architectures. The former has low performance and public data, which is not suitable for enterprise scenarios; the latter has huge communication complexity and storage overhead when the number of nodes is large (such as the PBFT consensus algorithm, which requires at least 3f+1 nodes to tolerate f malicious nodes). More importantly, in a software factory scenario with clearly defined roles and a fixed number of nodes, if the PBFT consensus algorithm is directly applied, assuming 4 nodes (f=1), then theoretically, only one malicious node can be tolerated at most. However, in a real organizational environment, the risk of collusion between two or more nodes cannot be ignored. Traditional consensus algorithms can only detect data inconsistencies after the fact and cannot prevent collusion from being tampered with in terms of mechanism. (3) Although existing user behavior analysis systems can record behavior, their technical focus is mostly on behavior collection, classification, or AI-based analysis. Their underlying evidence storage mechanism still relies on centralized or traditional trust assumptions and has not fundamentally solved the problem of the original trustworthiness of evidence storage data. Therefore, in view of the characteristics of multi-role and small-scale node collaboration in software factories, how to embed decentralized trust, be efficient and energy-saving, and fundamentally defend against node collusion in behavior evidence storage within a centralized platform has become a key technical problem that urgently needs to be solved. Summary of the Invention

[0003] The technical problem to be solved by this invention is to provide a method, system, medium, and product for multi-role behavior evidence storage in software factories, addressing the aforementioned problems of the prior art. This invention aims to solve the technical problem of building decentralized trust and achieving efficient and reliable behavior evidence storage in a centralized environment.

[0004] To solve the above-mentioned technical problems, the technical solution adopted by the present invention is as follows: A method for storing evidence of multi-role behaviors in software factories includes the following steps: S101, which forms a decentralized trust network by combining the software factory platform node of the management role team of the software factory, the development team node of the development role team, the test team node of the testing role team, and the operation and maintenance team node of the operation and maintenance role team. S102, based on blockchain technology, builds consortium chains for each team to store evidence of team members' behavior, including a platform chain for the management behavior of the management team, a development chain for the development behavior of the development team, a test chain for the testing behavior of the testing team, and an operation and maintenance chain for the operation and maintenance behavior of the operation and maintenance team. S103 When a role needs to perform behavior verification, the software factory platform node of the management role team initiates transaction packaging and block generation. The business logic is verified through the corresponding role's behavior and endorsed by other role team nodes. The transaction is confirmed through a consensus mechanism based on aggregate signature by the team nodes of the four roles: software factory platform node, development team node, testing team node, and operations and maintenance team node. The generated block is submitted to the consortium blockchain built by each team node only after the transaction is confirmed by the four role team nodes.

[0005] Optionally, in step S102, when building consortium blockchains for each team based on blockchain technology to record the behavior of team members, the consortium blockchains of each role team adopt differentiated data storage strategies. Specifically, the consortium blockchain of the management role team stores the full block data of the platform chain, development chain, test chain, and operation and maintenance chain, while the consortium blockchains of other team nodes store the full block data of the platform chain and the consortium blockchain of their own team node, and only store the block header data of the consortium blockchains of other team nodes.

[0006] Optionally, Step S103 includes recording the managerial behavior of the management team: S201, the software factory platform node obtains data on the management actions performed by the user, and the software factory platform node constructs platform transactions from the management action data, packages them into blocks and signs them; S202, the software factory platform node sends the packaged complete block to the development team node of the development role team, the test team node of the testing role team, and the operation and maintenance team node of the operation and maintenance role team respectively, requesting verification and signature; S203, the development team node of the development role team, the test team node of the test role team, and the operation and maintenance team node of the operation and maintenance role team respectively perform merge verification on the received complete block. The merge verification includes transaction logic legality verification and platform signature validity verification. S204: After verification and confirmation, the development team node of the development role team, the test team node of the test role team, and the operation and maintenance team node of the operation and maintenance role team shall attach their signatures and return them to the software factory platform node respectively. S205, the software factory platform node aggregates all the signatures received to generate an aggregate signature, fills the block header of the packaged block with the aggregate signature, and puts the complete final block containing the aggregate signature onto the platform chain; S206, the software factory platform node broadcasts the complete final block containing the aggregate signature to the development team node of the development role team, the test team node of the testing role team, and the operations team node of the operations role team. S207, the development team node of the development role team, the test team node of the test role team, and the operation and maintenance team node of the operation and maintenance role team verify the aggregate signature in the complete final block, and after the aggregate signature is verified, store the complete final block containing the aggregate signature in the consortium chain of their respective teams.

[0007] Optionally, step S103 includes non-management behaviors constituting development behaviors of the development team, testing behaviors of the testing team, or operation and maintenance behaviors of the operation and maintenance team, and recording these non-management behaviors: S301, the software factory platform node obtains data on non-management behavior, constructs platform transactions from the data on non-management behavior, packages blocks and signs them; S302, the software factory platform node sends the packaged complete block to the node of the corresponding role team based on non-management behavior, requesting business verification; S303, the corresponding role team node executes the verification business logic for the packaged complete block, and after confirming the business logic, attaches the signature of this node and returns the signature to the software factory platform node; S304. After receiving the signature from the node of the corresponding role team, the software factory platform node forwards the block header of the packaged complete block and the existing signature to the nodes of other role teams. The other role teams refer to role teams other than non-management behavior management role teams and non-management behavior role teams. S305, Other role team nodes verify the validity of the existing signature, and after confirming the validity of the existing signature, append the signature of this node and return the signature to the software factory platform node; S306, the software factory platform node aggregates the signatures returned by all other role team nodes to generate an aggregate signature, fills the block header of the packaged block with the aggregate signature, and puts the complete final block containing the aggregate signature onto the platform chain; S307, the software factory platform node broadcasts the complete final block containing the aggregate signature to the development team node of the development role team, the test team node of the testing role team, and the operations team node of the operations role team. S308, the development team node of the development role team, the test team node of the test role team, and the operation and maintenance team node of the operation and maintenance role team verify the aggregate signature in the complete final block. After the aggregate signature is verified, the node of the corresponding role team stores the complete final block containing the aggregate signature in the local consortium chain, and the nodes of other role teams store the block header of the complete final block containing the aggregate signature in their own team's consortium chain.

[0008] Optionally, the function expression for generating the aggregate signature is: ; in, For aggregate signature, ~ These are the signatures returned by the team nodes for the four roles: software factory platform node, development team node, testing team node, and operations and maintenance team node.

[0009] Optionally, the signature is a signature generated using the Boneh-Lynn-Shacham signature algorithm.

[0010] Optionally, verifying the aggregate signature in the complete final block means verifying whether the following formula holds true: ; in, It is a bilinear mapping. For aggregate signature, For public key groups generators in It is a hash-to-curve hash function. ~ This includes the identity information of team nodes for four roles: software factory platform node, development team node, testing team node, and operations and maintenance team node. ~ These are the public keys of the team nodes for the four roles: software factory platform node, development team node, testing team node, and operations and maintenance team node. Furthermore, the public key of any i-th node... satisfy .

[0011] Furthermore, the present invention also provides a multi-role behavior evidence storage system for software factories, including an interconnected microprocessor and a memory, wherein the microprocessor is programmed or configured to execute the multi-role behavior evidence storage method for software factories.

[0012] Furthermore, the present invention also provides a computer-readable storage medium storing a computer program or instructions that are programmed or configured to execute the multi-role behavior evidence storage method for software factories via a processor.

[0013] Furthermore, the present invention also provides a computer program product, including a computer program or instructions that are programmed or configured to execute the multi-role behavior evidence storage method for software factories via a processor.

[0014] Compared with existing technologies, this invention mainly achieves the following beneficial effects: Addressing the problems of complex networking and operation methods in existing blockchain platforms, and the potential disruption of the original software factory platform's operational logic upon introduction, this invention proposes a method to simplify the networking and operation of blockchain platforms. This allows for the introduction of blockchain technology without affecting the original operational logic of the existing software factory platform, reducing blockchain integration costs and adaptation risks. Addressing the difficulty in balancing security and efficiency in special scenarios such as physically centralized software factories, small node counts, and excellent centralized platform network conditions, this invention proposes a method that combines the decentralized characteristics of blockchain logic to improve the consensus mechanism and uses aggregated signatures to replace the traditional BFT algorithm. This achieves a high degree of adaptability to the software factory scenario, significantly improving the security and execution efficiency of the consensus process. To address the issues of insufficient disaster recovery capabilities for core data and excessive storage overhead for non-core data resulting from the unified storage model of traditional blockchains, this paper proposes a method of dividing blocks into managed and non-managed blocks and implementing differentiated storage: managed blocks are fully stored by all nodes, ensuring disaster recovery and tamper-proof capabilities for core public data; non-managed blocks are fully stored only by the relevant nodes, with other nodes storing only the block header, reducing overall storage overhead while ensuring tamper-proof data of concern to each node. To address the problem of data redundancy and difficulty in guaranteeing data consistency caused by distributed transaction initiation by nodes in traditional blockchains, this paper proposes a method where a centralized platform initiates all transactions uniformly on demand, reducing data redundancy, resolving data inconsistency issues caused by distributed transaction initiation, and improving the standardization and reliability of transaction processing. Addressing the collaborative characteristics of multi-role, small-scale nodes in software factories, this invention constructs a decentralized trust network within a centralized software factory platform, consisting of full nodes representing four roles: management, development, testing, and operations. Each role has its own independent parallel consortium chain for recording and verifying its actions. Transaction packaging and block generation are initiated by the platform management node, and become effective only after the action execution node completes business logic verification and the remaining nodes complete signature endorsement. A consensus mechanism based on aggregated signatures is adopted, requiring each transaction to obtain signatures from all four nodes for confirmation, thus fundamentally preventing node collusion. This invention embeds a decentralized trust mechanism within a centralized platform, achieving efficient, energy-saving, tamper-proof, and collusion-proof behavior verification. Ultimately, it utilizes blockchain technology to construct an efficient, reliable, and secure trusted verification system within the centralized software factory platform. Attached Figure Description

[0015] Figure 1 This is a schematic diagram of the basic process of the method in an embodiment of the present invention.

[0016] Figure 2 This is a schematic diagram illustrating the differentiated data storage strategy in an embodiment of the present invention.

[0017] Figure 3This is a flowchart illustrating the transaction initiation, verification, and consensus process for management-related behaviors in this embodiment of the invention.

[0018] Figure 4 This is a flowchart illustrating the transaction initiation, verification, and consensus process for development, testing, and operation / maintenance activities in this embodiment of the invention. Detailed Implementation

[0019] To enable those skilled in the art to better understand the technical solution of the present invention, the technical solution of the present invention will be further described in detail below with reference to the accompanying drawings in the embodiments of the present invention.

[0020] like Figure 1 The multi-role behavior evidence preservation method for software factories described in this embodiment includes the following steps: S101, which forms a decentralized trust network by combining the software factory platform node of the management role team of the software factory, the development team node of the development role team, the test team node of the testing role team, and the operation and maintenance team node of the operation and maintenance role team. S102, based on blockchain technology, builds consortium chains for each team to store evidence of team members' behavior, including a platform chain for the management behavior of the management team, a development chain for the development behavior of the development team, a test chain for the testing behavior of the testing team, and an operation and maintenance chain for the operation and maintenance behavior of the operation and maintenance team. S103 When a role needs to perform behavior verification, the software factory platform node of the management role team initiates transaction packaging and block generation. The business logic is verified through the corresponding role's behavior and endorsed by other role team nodes. The transaction is confirmed through a consensus mechanism based on aggregate signature by the team nodes of the four roles: software factory platform node, development team node, testing team node, and operations and maintenance team node. The generated block is submitted to the consortium blockchain built by each team node only after the transaction is confirmed by the four role team nodes.

[0021] This embodiment of the multi-role behavior notarization method for software factories constructs a consortium blockchain network within a centralized software factory platform. This network consists of full nodes maintained by four role teams: management, development, testing, and operations. For each of the four team roles' key behaviors, an independent parallel consortium blockchain, platform blockchain, development blockchain, testing blockchain, and operations blockchain are established, forming an embedded decentralized trust architecture that does not affect the original business of the software factory platform. When notarization of a role's behavior is required, the software factory platform node of the management role team initiates transaction packaging and block generation. The corresponding role team verifies the business logic, and other role team nodes provide signature endorsement. The transaction is confirmed through a consensus mechanism based on aggregated signatures among the four role teams: the software factory platform node, development team node, testing team node, and operations team node. The generated block is only submitted to the consortium blockchain constructed by each team node after receiving transaction confirmation from all four role teams.

[0022] In this embodiment, a decentralized trust network is constructed, consisting of the software factory platform node of the management team, the development team node of the development team, the testing team node of the testing team, and the operations team node of the operations team. Each team builds a consortium blockchain based on blockchain technology to record key actions of its members. This embedded decentralized network architecture, without altering the existing centralized organizational and system architecture of the software factory, deploys a full node for each of the four core roles (management, development, testing, and operations) to construct a logically decentralized four-color consortium blockchain. This architecture "embeds" decentralized trust into the centralized platform, achieving a transformation of the foundation of trust.

[0023] like Figure 2As shown, in step S102, when constructing consortium blockchains for each team based on blockchain technology to record the behavior of team members, the consortium blockchains of each role team adopt differentiated data storage strategies. Specifically, the consortium blockchain of the management role team stores the full block data of the platform chain, development chain, test chain, and operation and maintenance chain. The consortium blockchains of other team nodes store the full block data of the platform chain and their own team node's consortium blockchain, and only store the block header data of other team node's consortium blockchain. By adopting differentiated data storage strategies, the full node corresponding to the management role stores the complete data of all four parallel chains; the full nodes corresponding to the development, testing, and operation and maintenance roles fully store the parallel chain and platform chain data of their own roles. For other parallel chains that are not their own, they only store their block header data. Therefore, the management node stores the full data, while other role nodes only fully store their own chain data, platform public data, and the block headers of other chains. A differentiated storage strategy reduces storage overhead for development, testing, and operations nodes compared to full backups. Simultaneously, by storing full data on management nodes and nodes within the same role, it ensures that all data has at least two independent backups, maximizing data redundancy and saving storage space. Management nodes (software factory platform nodes) store complete data for all parachains, acting as supervisors and arbitrators. Development, testing, and operations nodes only store complete data for their own role's chain and the platform chain; for other chains, they only store block headers (containing key information such as Merklegen hashes). This strategy significantly reduces storage overhead on non-management nodes (estimated to save 40% of storage space) while ensuring that all data has complete backups on at least two physical nodes (the node within the role and the management node).

[0024] The evidence storage transaction is initiated uniformly by the management node (software factory platform node) on behalf of the platform. The transaction needs to be routed to the corresponding action implementation node for business logic authenticity verification, and the relevant node performs signature endorsement according to a preset strategy. The software factory platform node utilizes aggregated signature technology, requiring each transaction to obtain signatures from all four types of full nodes. Only after aggregating into a valid signature is the transaction considered valid and recorded on the chain. The transaction process on the four consortium chains proceeds in parallel. This embodiment adopts a platform-initiated and layered verification evidence storage mechanism: the evidence storage transaction is uniformly initiated by the management node to ensure the standardization and auditability of the behavior. The transaction is then routed to the relevant role node (e.g., development behavior is sent to the development node). This node not only performs the signature but also verifies the business logic authenticity of the transaction content (e.g., developers verify whether the code hash is correct). Other nodes (e.g., testing and operation nodes) mainly verify the validity of the transaction signature and the compliance of the endorsement strategy. This achieves separate verification of business authenticity and transaction validity. This embodiment adopts a full-member aggregated signature consensus: abandoning the traditional voting consensus based on the assumption of the number of fault-tolerant nodes. This invention requires each transaction to obtain signatures from all four nodes, and uses aggregate signature technology (such as BLS signature) to combine these signatures into a single, compact signature. Without the signature of any one node, the transaction cannot be confirmed or recorded on the blockchain. This mechanism completely eliminates the possibility of a few nodes (such as two) colluding to tamper with data at the algorithmic level, elevating security to the highest level of "unanimous agreement."

[0025] This embodiment of the multi-role behavior notarization method for software factories constructs a consortium blockchain network composed of full nodes maintained by four role teams: management, development, testing, and operations. This forms an embedded decentralized trust architecture that does not affect the original platform business of the software factory. The management node, i.e., the software factory platform node, maintains the full data of the platform chain, development chain, testing chain, and operations chain. The development, testing, and operations nodes, in addition to maintaining the full data of the platform chain and their own full data, only maintain the block headers of other chains, reducing storage requirements. When a role performs a critical action, such as code submission, code merging, or document finalization, a transaction block will be generated for that critical action. All blocks require the full signatures of all four roles to notarize the critical action. Figure 3 and Figure 4Taking management and development roles as examples, when a key action occurs, the user submits the action to the management node, and the management node constructs the platform transaction, packages the block and signs it. (1) For management actions, the management node sends the complete block to the development, testing and operation nodes and requests a signature; each node verifies the legality of the block and confirms and signs it back; the management node aggregates the signature, puts it on the chain and broadcasts it; the other three nodes receive the broadcast information, verify the aggregated signature and store the complete block; (2) For business (development, testing, operation) operations, the management node sends the complete block to the corresponding node (development, testing, operation) and performs business verification. After the verification is passed, the business node signs it; after the business node returns the signed block to the management node, the management node forwards the block to other business nodes and requests a signature. Each node verifies the legality of the block, confirms and signs it back, and the management node aggregates the signature, puts it on the chain and broadcasts it. The other three nodes receive the broadcast information and verify the aggregated signature. Except for the corresponding business node storing the complete block, the other business nodes only store the block header.

[0026] like Figure 3 As shown, step S103 in this embodiment includes recording the management behavior of the management team: S201, the software factory platform node obtains data on the management actions performed by the user, and the software factory platform node constructs platform transactions from the management action data, packages them into blocks and signs them; S202, the software factory platform node sends the packaged complete block to the development team node of the development role team, the test team node of the testing role team, and the operation and maintenance team node of the operation and maintenance role team respectively, requesting verification and signature; S203, the development team node of the development role team, the test team node of the test role team, and the operation and maintenance team node of the operation and maintenance role team respectively perform merge verification on the received complete block. The merge verification includes transaction logic legality verification and platform signature validity verification. S204: After verification and confirmation, the development team node of the development role team, the test team node of the test role team, and the operation and maintenance team node of the operation and maintenance role team shall attach their signatures and return them to the software factory platform node respectively. S205, the software factory platform node aggregates all the signatures received to generate an aggregate signature, fills the block header of the packaged block with the aggregate signature, and puts the complete final block containing the aggregate signature onto the platform chain; S206, the software factory platform node broadcasts the complete final block containing the aggregate signature to the development team node of the development role team, the test team node of the testing role team, and the operations team node of the operations role team. S207, the development team node of the development role team, the test team node of the test role team, and the operation and maintenance team node of the operation and maintenance role team verify the aggregate signature in the complete final block, and after the aggregate signature is verified, store the complete final block containing the aggregate signature in the consortium chain of their respective teams.

[0027] In this embodiment, blocks are divided into two types: managed and unmanaged. Different storage methods are used for each type. Managed blocks require all nodes to store the complete block, ensuring disaster recovery and tamper-proofing of core shared data. Unmanaged blocks only require relevant nodes to store the complete block, while other nodes store the block header, reducing storage overhead and ensuring tamper-proofing of data that each node cares about. Disaster recovery is the responsibility of each node itself. This embodiment leverages the decentralized nature of blockchain logic in the unique physically centralized scenario of a software factory. It fully considers the small number of nodes and the good network conditions of the centralized platform, improving the consensus mechanism by using aggregate signatures instead of the traditional BFT algorithm to enhance security and efficiency. In this embodiment, all transactions are initiated on demand by the centralized platform, reducing data redundancy and inconsistency issues caused by traditional distributed initiation by individual nodes. This embodiment significantly simplifies the networking and operation of existing blockchain platforms, and the introduction of blockchain does not affect the operating logic of existing software factory platforms.

[0028] like Figure 4 As shown, step S103 in this embodiment includes non-management behaviors constituting the development behaviors of the development team, the testing behaviors of the testing team, or the operation and maintenance behaviors of the operation and maintenance team, and the non-management behaviors are documented: S301, the software factory platform node obtains data on non-management behavior, constructs platform transactions from the data on non-management behavior, packages blocks and signs them; S302, the software factory platform node sends the packaged complete block to the node of the corresponding role team based on non-management behavior, requesting business verification; S303, the corresponding role team node executes the verification business logic for the packaged complete block, and after confirming the business logic, attaches the signature of this node and returns the signature to the software factory platform node; S304, after receiving the signature from the node of the corresponding role team, the software factory platform node forwards the block header of the packaged complete block and the existing signature to the nodes of other role teams. These other role teams refer to role teams other than the non-management behavior management role team and other non-management behavior role teams; for example... Figure 4The corresponding role team in the text refers to the development role team. The nodes for other role teams refer to the test team node of the testing role team and the operations team node of the operations role team. In the transaction initiation and verification process, for a transaction corresponding to a development activity, the development node must verify the authenticity of its business logic (such as the correctness of the code hash), and the management node and development node must jointly sign and endorse it. Then, the test node and operations node verify the validity of the signature and attach the signature. The transaction processing method for testing and operations activities is similar. S305, Other role team nodes verify the validity of the existing signature, and after confirming the validity of the existing signature, append the signature of this node and return the signature to the software factory platform node; S306, the software factory platform node aggregates the signatures returned by all other role team nodes to generate an aggregate signature, fills the block header of the packaged block with the aggregate signature, and puts the complete final block containing the aggregate signature onto the platform chain; S307, the software factory platform node broadcasts the complete final block containing the aggregate signature to the development team node of the development role team, the test team node of the testing role team, and the operations team node of the operations role team. S308, the development team node of the development role team, the test team node of the test role team, and the operation and maintenance team node of the operation and maintenance role team verify the aggregate signature in the complete final block. After the aggregate signature is verified, the node of the corresponding role team stores the complete final block containing the aggregate signature in the local consortium chain, and the nodes of other role teams store the block header of the complete final block containing the aggregate signature in their own team's consortium chain.

[0029] In this embodiment, the function expression for generating the aggregate signature is: ; in, For aggregate signature, ~ These are the signatures returned by the team nodes representing four roles: the software factory platform node, the development team node, the testing team node, and the operations and maintenance team node. The addition operation follows the BLS12-381 curve group addition rule, does not involve the private key, and only public data is used for the operation.

[0030] In this embodiment, the signature is generated using the Boneh-Lynn-Shacham signature algorithm, specifically by selecting the LS12-381 elliptic curve and defining a bilinear mapping. , For signature groups, For public key groups, For the target group. The software factory platform nodes receive the generated single signatures from each node. ~ ,in ~ These refer to the factory platform node, development team node, testing team node, and operations and maintenance team node, respectively; each node has a single signature. , Use the corresponding node's public key ,information The equation is verified using bilinear mapping: , Message Mapped to signature group The elements in, where For public key groups generators in Verify the Hash-to-Curve hash function. It is a bilinear mapping; signatures that fail are discarded.

[0031] In this embodiment, verifying the aggregate signature in the complete final block refers to verifying whether the following formula holds true: ; in, It is a bilinear mapping. For aggregate signature, For public key groups generators in It is a hash-to-curve hash function. ~ This includes the identity information of team nodes for four roles: software factory platform node, development team node, testing team node, and operations and maintenance team node. ~ These are the public keys of the team nodes for the four roles: software factory platform node, development team node, testing team node, and operations and maintenance team node. Furthermore, the public key of any i-th node... satisfy If the equation is true, the aggregate signature is valid, and all node signatures are valid.

[0032] In summary, this embodiment of the multi-role behavior evidence storage method for software factories constructs a decentralized trust network within a centralized software factory platform, consisting of full nodes corresponding to four role teams: management, development, testing, and operations. Addressing the issues of complex blockchain networking and easy intrusion into existing business processes, it innovatively adopts a lightweight, low-intrusion networking architecture, embedding a blockchain trust mechanism without altering the existing operational logic of the software factory. An independent parallel consortium chain is established for each role, separately storing the corresponding role's behavior. A differentiated data storage strategy is employed, innovatively dividing blocks into management and non-management categories and implementing differentiated storage. Management nodes store all data, while other role nodes... This method stores only its own chain data, platform public data, and block headers from other chains, ensuring multiple data backups and saving storage space. It innovatively uses a centralized platform to initiate transactions on demand, avoiding data redundancy and consistency issues caused by distributed transaction initiation. Transaction packaging and block generation are initiated by the platform's management nodes, requiring business logic verification by the behavior implementation nodes and signature endorsement from other nodes. It innovatively uses aggregate signatures based on elliptic curve bilinear mapping to replace the traditional BFT consensus algorithm, adapting to the characteristics of software factories with physical centralization, small node scale, and good network conditions. The consensus mechanism based on aggregate signatures requires each transaction to obtain signatures from all four nodes for confirmation, thus preventing node collusion. This embodiment of the multi-role behavior evidence storage method for software factories has the following advantages: 1. Trust model innovation: A decentralized trust anchor point is successfully built within the centralized platform, solving the problems of internal data tampering and repudiation. 2. Extremely high security: Through the all-member signature consensus mechanism, it fundamentally defends against small-scale node collusion attacks, which is impossible for traditional consensus algorithms in small networks. 3. Excellent storage efficiency: The differentiated storage strategy significantly reduces the total storage cost and operational burden of the system while ensuring data reliability. 4. Clear responsibilities and convenient auditing: The role-based parachain design naturally isolates data, making audit traceability clear; unified transaction initiation on the platform strengthens process management.

[0033] Furthermore, the present invention can also provide a multi-role behavior evidence storage system for software factories, including a microprocessor and a memory interconnected, wherein the microprocessor is programmed or configured to execute the multi-role behavior evidence storage method for software factories. The present invention can also provide a computer-readable storage medium storing a computer program or instructions programmed or configured to execute the multi-role behavior evidence storage method for software factories via a processor. The present invention can also provide a computer program product including a computer program or instructions programmed or configured to execute the multi-role behavior evidence storage method for software factories via a processor.

[0034] The above description is merely a preferred embodiment of the present invention. The scope of protection of the present invention is not limited to the above embodiments. All technical solutions falling within the scope of the present invention's concept are within the scope of protection of the present invention. It should be noted that for those skilled in the art, any improvements and modifications made without departing from the principles of the present invention should also be considered within the scope of protection of the present invention.

Claims

1. A method for storing evidence of multi-role behaviors in a software factory, characterized in that, Includes the following steps: S101, which forms a decentralized trust network by combining the software factory platform node of the management role team of the software factory, the development team node of the development role team, the testing team node of the testing role team, and the operation and maintenance team node of the operation and maintenance role team. S102, based on blockchain technology, builds consortium chains for each team to store evidence of team members' behavior, including a platform chain for the management behavior of the management team, a development chain for the development behavior of the development team, a test chain for the testing behavior of the testing team, and an operation and maintenance chain for the operation and maintenance behavior of the operation and maintenance team. S103 When a role needs to perform behavior verification, the software factory platform node of the management role team initiates transaction packaging and block generation. The business logic is verified through the corresponding role's behavior and endorsed by other role team nodes. The transaction is confirmed through a consensus mechanism based on aggregate signature by the team nodes of the four roles: software factory platform node, development team node, testing team node, and operations and maintenance team node. The generated block is submitted to the consortium blockchain built by each team node only after the transaction is confirmed by the four role team nodes.

2. The multi-role behavior evidence storage method for software factories according to claim 1, characterized in that, In step S102, when building consortium blockchains for each team based on blockchain technology to record the behavior of team members, the consortium blockchains of each role team adopt differentiated data storage strategies. Specifically, the consortium blockchain of the management role team stores the full block data of the platform chain, development chain, test chain, and operation and maintenance chain, while the consortium blockchains of other team nodes store the full block data of the platform chain and the consortium blockchain of their own team node, and only store the block header data of the consortium blockchains of other team nodes.

3. The multi-role behavior evidence storage method for software factories according to claim 1, characterized in that, Step S103 includes recording the managerial behavior of the management team: S201, the software factory platform node obtains data on the management actions performed by the user, and the software factory platform node constructs platform transactions from the management action data, packages them into blocks and signs them; S202, the software factory platform node sends the packaged complete block to the development team node of the development role team, the test team node of the testing role team, and the operation and maintenance team node of the operation and maintenance role team respectively, requesting verification and signature; S203, the development team node of the development role team, the test team node of the test role team, and the operation and maintenance team node of the operation and maintenance role team respectively perform merge verification on the received complete block. The merge verification includes transaction logic legality verification and platform signature validity verification. S204: After verification and confirmation, the development team node of the development role team, the test team node of the test role team, and the operation and maintenance team node of the operation and maintenance role team shall attach their signatures and return them to the software factory platform node respectively. S205, the software factory platform node aggregates all the signatures received to generate an aggregate signature, fills the block header of the packaged block with the aggregate signature, and puts the complete final block containing the aggregate signature onto the platform chain; S206, the software factory platform node broadcasts the complete final block containing the aggregate signature to the development team node of the development role team, the test team node of the testing role team, and the operations team node of the operations role team. S207, the development team node of the development role team, the test team node of the test role team, and the operation and maintenance team node of the operation and maintenance role team verify the aggregate signature in the complete final block, and after the aggregate signature is verified, store the complete final block containing the aggregate signature in the consortium chain of their respective teams.

4. The method for storing evidence of multi-role behaviors in a software factory according to claim 1, characterized in that, Step S103 includes non-management behaviors constituting development behaviors of the development team, testing behaviors of the testing team, or operation and maintenance behaviors of the operation and maintenance team, and recording these non-management behaviors: S301, the software factory platform node obtains data on non-management behavior, constructs platform transactions from the data on non-management behavior, packages blocks and signs them; S302, the software factory platform node sends the packaged complete block to the node of the corresponding role team based on non-management behavior, requesting business verification; S303, the corresponding role team node executes the verification business logic for the packaged complete block, and after confirming the business logic, attaches the signature of this node and returns the signature to the software factory platform node; S304. After receiving the signature from the node of the corresponding role team, the software factory platform node forwards the block header of the packaged complete block and the existing signature to the nodes of other role teams. The other role teams refer to role teams other than non-management behavior management role teams and non-management behavior role teams. S305, Other role team nodes verify the validity of the existing signature, and after confirming the validity of the existing signature, append the signature of this node and return the signature to the software factory platform node; S306, the software factory platform node aggregates the signatures returned by all other role team nodes to generate an aggregate signature, fills the block header of the packaged block with the aggregate signature, and puts the complete final block containing the aggregate signature onto the platform chain; S307, the software factory platform node broadcasts the complete final block containing the aggregate signature to the development team node of the development role team, the test team node of the testing role team, and the operations team node of the operations role team. S308, the development team node of the development role team, the test team node of the test role team, and the operation and maintenance team node of the operation and maintenance role team verify the aggregate signature in the complete final block. After the aggregate signature is verified, the node of the corresponding role team stores the complete final block containing the aggregate signature in the local consortium chain, and the nodes of other role teams store the block header of the complete final block containing the aggregate signature in their own team's consortium chain.

5. The method for storing evidence of multi-role behaviors in a software factory according to claim 3 or 4, characterized in that, The function expression for generating the aggregate signature is: ; in, For aggregate signature, ~ These are the signatures returned by the team nodes for the four roles: software factory platform node, development team node, testing team node, and operations and maintenance team node.

6. The multi-role behavior evidence storage method for software factories according to claim 5, characterized in that, The signature is generated using the Boneh-Lynn-Shacham signature algorithm.

7. The method for storing evidence of multi-role behaviors in a software factory according to claim 6, characterized in that, Verifying the aggregate signature in the complete final block refers to verifying whether the following formula holds true: ; in, It is a bilinear mapping. For aggregate signature, For public key groups generators in It is a hash-to-curve hash function. ~ This includes the identity information of team nodes for four roles: software factory platform node, development team node, testing team node, and operations and maintenance team node. ~ These are the public keys of the team nodes for the four roles: software factory platform node, development team node, testing team node, and operations and maintenance team node. Furthermore, the public key of any i-th node... satisfy .

8. A multi-role behavior evidence storage system for software factories, comprising interconnected microprocessors and memory, characterized in that, The microprocessor is programmed or configured to execute the multi-role behavior evidence storage method for software factories as described in any one of claims 1 to 7.

9. A computer-readable storage medium storing a computer program or instructions, characterized in that, The computer program or instructions are programmed or configured to execute, via a processor, the multi-role behavior evidence storage method for software factories as described in any one of claims 1 to 7.

10. A computer program product, comprising a computer program or instructions, characterized in that, The computer program or instructions are programmed or configured to execute, via a processor, the multi-role behavior evidence storage method for software factories as described in any one of claims 1 to 7.