Project-based configuration management method and apparatus

• US 7,475,097 B2
• Filed: 11/24/2004
• Issued: 01/06/2009
• Est. Priority Date: 11/21/2000
• Status: Expired due to Fees

• Current Assignee: SZ DJI Technology Co., Ltd. (d/b/a DJI) (iFlight Technology Company Limited)
• Original Assignee: Microsoft Corporation
• Inventors: Kaler, Christopher G., Grier, Michael J., Kruy, Steven J., Lovell, Martyn S.
• Primary Examiner(s): ROBINSON, GRETA LEE
• Application Number:
  US10/996,719
• Publication Number:
  US 20050091291A1
• Time in Patent Office: 1,504 Days
• Field of Search: 707/9, 707/200, 707/203, 707/100, 707/102, 707/8, 707/201, 707/104.1, 707/103.R, 707/103.X, 707/103.Y, 707/103.Z, 717/101, 717/102, 717/121, 717/122, 717/123
• US Class Current: 1/1
• CPC Class Codes: G06F 8/71 Version control security arrangements therefor G06F21/57; Configuration management
• CPC Class Codes: Y10S 707/99939 Privileged access
• CPC Class Codes: Y10S 707/99942 Manipulating data structure, e.g. compression, compaction, compilation
• CPC Class Codes: Y10S 707/99953 Recoverability
• CPC Class Codes: Y10S 707/99954 Version management

Abstract

A configuration management system creates (602) each configuration by assigning a configuration identifier to each configuration. In addition, relational information is computed (706) that indicates the relationships between the configuration and any configurations upon which it is based. The system then tracks (604) changes to files of the configuration by storing information associating each new file version with the configuration identifier. The system also tracks (1210) changes to file properties. A configuration is then reconstructed (608) as of a desired date, by identifying (2104, 2106) the file versions and properties associated with that configuration as of the desired date. A determination is made (2110) whether a user that has requested the file versions has access privileges by first checking a security cache (2600) for the user privileges information. If the information is not on the cache, it is computed from a security table (2800) and stored on the cache. The system automatically compresses (3118) and reconstitutes (3006) file versions that are stored in the version store.

Claims

1. A computer-readable storage medium having computer-executable instructions for performing a method for constructing a desired one of a plurality of configurations of a project, at the request of a user, each of said configurations comprising multiple files, each file having one or more versions, wherein a history of versions is separately tracked for each file in each configuration, the desired configuration being one of said plurality of configurations of the project as of a desired prior time, comprising:

determining a configuration identifier for the desired configuration;

identifying versions of the multiple files that are to be included in the desired configuration as a set of the versions that are associated with the configuration identifier at the desired prior time, wherein the history of versions separately tracked for at least one of the multiple files includes a version that is the same as a version in a history of versions separately tracked for that file in a different configuration; and

determining whether the user that has requested the desired configuration has access privileges for the file versions that comprise the desired configuration, and if so, assembling the set of versions to construct the desired configuration.

2. A system for constructing a desired one of a plurality of configurations of a project, at the request of the user, each of said configurations comprising multiple files, each file having one or more versions, wherein a history of versions is separately tracked for each file in each configuration, the desired configuration being one of said plurality of configurations of the project as of a desired prior time, comprising:

means for determining a configuration identifier for the desired configuration;

means for identifying versions of the multiple files that are to be included in the desired configuration as a set of the versions that are associated with the configuration identifier at the desired prior time, wherein the history of versions separately tracked for at least one of the multiple files includes a version that is the same as a version in a history of versions separately tracked for that file in a different configuration; and

means for determining whether the user that has requested the desired configuration has access privileges for the file versions that comprise the desired configuration; and

means for assembling the set of versions to construct the desired configuration.