SYSTEM AND METHOD FOR TRACKING COMPLIANCE INFORMATION FOR A BUILD-SYSTEM PRODUCT

• US 20130326479A1
• Filed: 06/01/2012
• Published: 12/05/2013
• Est. Priority Date: 06/01/2012
• Status: Abandoned Application

• Current Assignee: 2236008 Ontario Inc. (Blackberry Limited)
• Original Assignee: QNX Software Systems Limited (Canada) (Blackberry Limited)
• Inventors: RUSSELL, Keith Roderick, JOHNSON, Eric Anthony, MICHALYSHYN, Michael Paul
• Application Number:
  US13/486,113
• Publication Number:
  US 20130326479A1
• Time in Patent Office: Days
• US Class Current: 717/121
• CPC Class Codes: G06F 8/70 Software maintenance or management

Abstract

Systems and methods for tracking compliance information for a build-system product are described. The compliance information is associated with one or more source code files used to build the build-system product. Tracking information is created for the build-system product including a source code identifier for each source code file that contributes to the build-system product. The tracking information can be utilized to identify the source codes files that contributed to the build-system product and identify the associated compliance information.

Claims

1. A method, executable on one or more processors, for tracking compliance information associated with a plurality of source code files that contribute to building a build-system product, the method comprising:

generating a unique compliance identifier for each of a plurality of compliance information items; and

associating one or more compliance identifiers with each of a plurality of source code files;

creating tracking information related to the build-system product, the tracking information including a source code identifier for each of the plurality of source code files that contribute to the building of the build-system product.

2. The method of claim 1, where each of the plurality of compliance information items includes any one or more of:

a software license agreement, software distribution restrictions, export restrictions, and an intellectual property rights identifier.

3. The method of claim 1, further comprising:

storing each of the plurality of compliance information items in a compliance information repository;

where each of the plurality of compliance information items is retrievable from the compliance information repository using the corresponding compliance identifier.

4. The method of claim 3, further comprising:

retrieving the compliance information items associated with each of the source code files that contribute to the build-system product from the compliance information repository using the source code identifiers included in the tracking information and the compliance identifiers associated with each of the source code files.

5. The method of claim 1, where the build-system product is any of:

a processor executable file, a binary file, an object file, a static library file, and a linkable library file.

6. The method of claim 1, where the build-system product is built by a build system including any one or more of:

a compiler, assembler and a linker.

7. The method of claim 1, where each source code identifier includes a source code file name identifier and a source code file version identifier.

8. The method of claim 7, where each of the plurality of source code files is stored in a source code repository and is accessible in the source code repository using the corresponding source code identifier.

9. The method of claim 1, wherein the compliance items are used to generate a software license guide for the build-system product.

10. The method of claim 1, where the tracking information is embedded in the build-system product or is contained in a debug information file related to the build-system product.

11. The method of claim 1, where each of the source code files comprises any of a source code file, a header file, a make file, a static library file or a linkable library file.

12. The method of claim 1 where each of the plurality of source code files identifiers is associated in a database with compliance identifiers, the compliance identifiers retrieved from the database to identify the associated compliance information items.

13. The method of claim 1, where each source code identifier comprises a hash code.

14. The method of claim 1, where each source code identifier is encrypted.

15. A system for tracking compliance information associated with a plurality of source code files that contribute to a build-system product, the system comprising:

a compliance information repository containing a unique compliance identifier for each of a plurality of compliance information items;

a source code repository containing the plurality of source code files used for creating the build-system product, each of the plurality of source code files having an associated one or more compliance identifiers from the compliance information repository; and

a build component for creating tracking information related to the build-system product, the tracking information including a source code identifier for each of the plurality of source code files to identify a respective source code file that contributes to the building of the build-system product.

16. The system of claim 15, where each of the plurality of compliance information items includes any one or more of:

a software license agreement, software distribution restrictions, export restrictions, and an intellectual property rights identifier.

17. The system of claim 15 where each of the plurality of compliance information items is stored in a compliance information repository and is retrievable from the compliance information repository using the corresponding compliance identifier.

18. The system of claim 17 where each of the plurality of source code file identifiers is associated in a database with the compliance identifiers, the compliance identifiers retrieved from the database to identify the associated compliance information items.

19. The system of claim 17, further comprising:

a trace component for retrieving the compliance information items associated with each of the source code files that contribute to the build-system product from the compliance information repository using the source code identifiers included in the tracking information and the compliance identifiers associated with each of the source code files.

20. The system of claim 15, where the build-system product is any of:

a processor executable file, a binary file, an object file, a static library file, a linkable library file and a debug file.

21. The system of claim 15, where the build-system product is built by a build system including any one or more of:

a compiler, assembler and a linker.

22. The system of claim 15, where each source code identifier includes a source code file name identifier and a source code file version identifier.

23. The system of claim 22, where each of the plurality of source code files is stored in a source code repository and is accessible in the source code repository using the corresponding source code identifier.

24. The system of claim 15, where the tracking information is embedded in the build-system product.

25. The system of claim 15, where the tracking information is contained in a debug information file related to the build-system product.

26. The system of claim 15, wherein the compliance items are used to generate a software license guide for the build-system product.

27. The system of claim 15, where each of the source code files comprises any of a source code file, a header, a make file, a static library file or a linkable library file.

28. The system of claim 15, where each source code identifier comprises a hash code.

29. The system of claim 15, where each source code identifier is encrypted.

30. A computer readable memory containing instructions for execution on one or more processors, the instructions for tracking compliance information associated with a plurality of source code files that contribute to a build-system product, the instructions comprising:

generating a unique compliance identifier for each of a plurality of compliance information items; and

associating one or more compliance identifiers with each of a plurality of source code files;

creating tracking information related to the build-system product, the tracking information including a source code identifier for each of the plurality of source code files that contribute to the building of the build-system product.