Versioning model for software program development

• US 7,428,559 B2
• Filed: 03/28/2002
• Issued: 09/23/2008
• Est. Priority Date: 12/13/2001
• Status: Expired due to Term

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Beachman, Bruce J., Hill, Timothy J.
• Primary Examiner(s): AL HASHEMI, SANA A
• Application Number:
  US10/108,652
• Publication Number:
  US 20030120688A1
• Time in Patent Office: 2,371 Days
• Field of Search: 717168-174, 707/104.1
• US Class Current: 1/1
• CPC Class Codes: G06F 8/71 Version control security arrangements therefor G06F21/57; Configuration management

Abstract

A system and method for generating run-time images of a software program, such as an operating system, builds a run-time image from a plurality of selected software program components, each of which is a discrete packet of functionality. Each component not only specifies its properties and resources but also provides script for its own build behavior. To build the run-time image, a configuration is constructed to include instances of selected components, and the scripts of the instances are invoked such that each component instance builds itself into the run-time image. A general framework is provided for managing the components and the build process. A prototyping scheme is provided for a component to inherit its properties, resources, and script from other components. Each component may also specify dependency data in terms of component inclusion in the run-time image and the orders in which the components are built into the run-time image. A versioning scheme facilitates the tracking of various revisions and upgrades of components.

Claims

1. A method comprising:

modifying version information of a software item by;

modifying the software item, the software item having description data representing a version-independent identifier unchanged by revisions and upgrades to the software item, a version-specific identifier unchanged by revisions but changed by upgrades to the software item, a revision number, and a release flag indicating that the software item has been released;

incrementing the revision number;

checking whether the release flag is set; and

changing the version-specific identifier to a new value if the release flag is set; and

building a runtime image of the software item.

2. A method as in claim 1, wherein the version-independent and version-specific identifiers are globally unique identifiers.

3. A method as in claim 1, wherein the software item is a software program components for use in building the run-time image.