Dynamic versioning system for multiple users of multi-module software system

• US 5,881,292 A
• Filed: 09/26/1996
• Issued: 03/09/1999
• Est. Priority Date: 09/26/1996
• Status: Expired due to Term

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Sigal, Andrew David, Pissarra, Augusto, Bien, Daniel
• Primary Examiner(s): WACHSMAN, HAL D
• Application Number:
  US08/719,687
• Time in Patent Office: 894 Days
• Field of Search: 395/712, 395/703, 707/203, 707/201, 707/200, 364/978, 364/978.2, 364/132
• US Class Current: 717/170
• CPC Class Codes: G06F 8/71 Version control security arrangements therefor G06F21/57; Configuration management
• CPC Class Codes: Y10S 707/99952 Coherency, e.g. same view to multiple users
• CPC Class Codes: Y10S 707/99953 Recoverability

Abstract

A dynamic versioning system for synchronizing different versions of modules among different versions of a complex multi-module software system, and maintaining a consistent view of a version of the complex system for each user having access to the system. The dynamic versioning system grants a user read-only access to the multiple modules in a complex system, and promotes the access to write access only when a user is ready to save a modified module in the permanent non-volatile memory of the complex system. The dynamic versioning system manages the evolving versions of the complex system with a Dynamic Versioning Table (DVT) and master modules that identify the multiple slave modules associated with a particular version of the complex system. Old versions of modules are removed from the complex system'"'"'s permanent non-volatile memory when the last user has terminated use of the complex system.

Claims

1. A computer readable medium containing computer executable instructions to perform a method for dynamically versioning a complex system comprised of a plurality of modules accessible by a plurality of users, said method comprising:

first step of maintaining only one copy of each of said plurality of modules that comprise each of a plurality of complex system versions simultaneously existing in time, wherein said one copy is located in a non-volatile complex system memory location;

second step of maintaining, which includes maintaining an index system to identify each of said plurality of modules that comprise a version of said complex system, wherein any one of said plurality of modules can be a member of any number of said plurality of complex system versions that simultaneously exist in time; and

third step of maintaining, which includes maintaining a virtual version of said complex system for each of said plurality of users having access to said complex system, wherein said virtual version remains constant over time from a perspective of each of said plurality of users independent of any one of said plurality of users saving a modified one of said plurality of modules to said non-volatile complex system memory location, said third step of maintaining includes;

first step of granting shared read-only access to a present version of said complex system in response to a complex system access request by one of said plurality of users, wherein said present version is most recent in time of any version of said complex system prior to said complex system access request; and

second step of granting, which includes grantings write access for at least one module of said present version in response to a request to save said at least one module by a saving one of said plurality of users by way of a new version of said at least one module from said present version, and a new version of said complex system containing said new version of said at least one module, wherein said new version of said complex system is defined by a master module containing pointers to each of said plurality of modules comprising a most recent version of said complex system.

2. A method according to claim 1 wherein said step of maintaining an index system includes:

fourth step of maintaining, which includes maintaining a table to identify each of said plurality of modules that exist and each respective version thereof; and

generating a master module to define each of a plurality of slave modules that comprise a version of said complex system, wherein said master module and said plurality of slave modules are included in said plurality of modules.

3. A method according to claim 1 including:

determining a number of said plurality of users having access to a version of said complex system in response to a user request to terminate access to said complex system; and

removing old versions of said complex system from non-volatile complex system memory location following termination of complex system access by a last one of said plurality of users having access thereto.

4. A method for dynamically versioning a complex system having a plurality of modules accessible by a plurality of users, said method comprising:

first step of maintaining only one copy of each of said plurality of modules that comprise each of a plurality of complex system versions that simultaneously exist in time, wherein said one copy is located in a non-volatile complex system memory location;

second step of maintaining, which includes maintaining an index system to identify each of said plurality of modules that comprise a version of said complex system, wherein any one of said plurality of modules can be a member of any number of said plurality of complex system versions that simultaneously exist in time;

first step of granting shared read-only access to a first version of said complex system in response to a complex system access request by one of said plurality of users, wherein said first version is most recent in time of any version of said complex system prior to said complex system access request;

first step of generating a second version of said complex system in response to a request to save at least one modified module of said first version by a saving one of said plurality of users having write access for said first version, wherein said second version is at least one version more recent in time than said first version or any module within said first version; and

third step of maintaining, which includes maintaining said first version for continued access by ones of said plurality of users having originally been granted access thereto independent of said second version.

5. A method according to claim 4 including:

monotonically incrementing a version identifier for each new version of said plurality of modules and each new version of said complex system.

6. A method according to claim 4 including:

monotonically decrementing a version identifier for each new version of said plurality of modules and each new version of said complex system.

7. A method according to claim 4 including:

second step of granting, which includes granting write access for at least one module of said first version in response to a request to save said at least one module by a saving one of said plurality of users.

8. A method according to claim 4 wherein said step of maintaining an index system includes:

fourth step of maintaining, which includes maintaining a table to identify each of said plurality of modules that exist and each respective version thereof; and

second step of generating, which includes generating a master module to define each of a plurality of slave modules that comprise a version of said complex system, wherein said master module and said plurality of slave modules are included in said plurality of modules.

9. A method according to claim 4 wherein said step of generating said second version includes:

second step of generating, which includes generating a permanent copy of said at least one modified module from said first version in said non-volatile complex system memory location;

first step of assigning a version identifier to each of said at least one modified module;

first step of recording said version identifier and a module location in said index system for each of said at least one modified module;

third step of generating, which includes generating a permanent copy of a master module defining said second version in said non-volatile complex system memory location;

second step of assigning, which includes assigning said version identifier to said master module; and

second step of recording, which includes recording said version identifier and a master module location in said index system.

10. A method according to claim 9 wherein said step of generating said second version of said complex system includes:

determining, in response to a second of said plurality of users requesting to save a second modification of said first version of a module, that a first of said plurality of users has permanently saved a first modification of said first version of said module in said non-volatile complex system memory location, wherein said first modification of said first version of said module and said second modification of said first version of said module have no common module origin;

fourth step of generating, which includes generating a temporary copy of said second version of said complex system, wherein said second version is a most recent version of said complex system;

merging said second modification of said first version of said module into said temporary copy of said second version; and

saving said temporary copy of said second version in said non-volatile complex system memory location.

11. A method according to claim 9 wherein said step of generating said second version of said complex system includes:

determining a conflict between a first of said plurality of users having permanently saved a first modification of said first version of said module in said non-volatile complex system memory location and a second of said plurality of users requesting to permanently save a second modification of said first version of said module, wherein said first and second modification of said first version of said module have a common module origin;

fourth step of generating, which includes generating a temporary copy of said second version of said complex system, wherein said second version is a most recent version of said complex system;

merging non-conflicting portions of said first and second modification of said first version of said module into said temporary copy of said second version;

resolving conflicting portion of said first and second modification of said first version by user input command; and

saving said temporary copy of said second version in said non-volatile complex system memory location.

12. A method according to claim 4 including:

determining a number of said plurality of users having access to a version of said complex system in response to a user request to terminate access to said complex system; and

removing old versions of said complex system from non-volatile complex system memory following termination of complex system access by a last one of said plurality of users having access thereto.

13. A computer readable medium containing executable instructions to perform a method for dynamically versioning a complex system comprised of a plurality of modules accessible by a plurality of users, said method comprising:

maintaining a virtual version of said complex system for each of said plurality of users having access to said complex system, wherein said virtual version remains consistent over time from a perspective of each of said plurality of users independent of any one of said plurality of users saving a modified one of said plurality of modules to a non-volatile complex system memory, and wherein only one permanent copy of each of said plurality of modules is maintained in said non-volatile complex system memory independent of the number of users having access to said virtual version of said complex system, and wherein each of said plurality of user has simultaneous read/write access to said complex system; and

generating a most recent virtual version of said complex system in response to each save of at least one of said plurality of modules to said non-volatile complex system memory by any one of said plurality of users, wherein said most recent virtual version includes a most recent module version of each of said plurality of modules.

14. A method according to claim 13 including:

determining a number of said plurality of users having access to said complex system in response to a user request to terminate access to complex system; and

periodically removing unused virtual versions and old versions of said plurality of modules of said complex system from said non-volatile complex system memory, wherein only a most recent virtual version having a most recent version of said plurality of modules remains in said non-volatile complex system memory to represent said complex system.

15. A method according to claim 14 wherein periodically removing includes:

removing unused virtual versions and old versions of said plurality of modules of said complex system from said non-volatile complex system memory only in response to a last user terminating access to said complex system.

16. A dynamic versioning system for a complex system having a plurality of modules accessible by a plurality of users, said dynamic versioning system comprising:

first means for maintaining only one copy of each of said plurality of modules that comprise each of a plurality of complex system versions simultaneously existing in time, wherein said one copy is located in a non-volatile complex system memory location;

second means for maintaining, which maintains an index system to identify each of said plurality of modules that comprise a version of said complex system, wherein any one of said plurality of modules can be a member of any number of said plurality of complex system versions that simultaneously exist in time; and

third means for maintaining, which maintains a virtual version of said complex system for each of said plurality of users having access to said complex system, wherein said virtual version remains constant over time from a perspective of each of said plurality of users independent of any one of said plurality of users saving a modified one of said plurality of modules to said non-volatile complex system memory location, said third means for maintaining includes;

first means for granting shared read-only access to a present version of said complex system in response to a complex system access request by one of said plurality of users, wherein said present version is most recent in time of any version of said complex system prior to said complex system access request; and

second means for granting, which grants write access for at least one module of said present version in response to a request to save said at least one module by a saving one of said plurality of users.

17. A dynamic versioning system according to claim 16 wherein said second means for maintaining said index system includes:

fourth means for maintaining, which maintains a structure to identify each of said plurality of modules that exist and each respective version thereof; and

means for generating a master module to define each of a plurality of slave modules that comprise a version of said complex system, wherein said master module and said plurality of slave modules are included in said plurality of modules.

18. A dynamic versioning system according to claim 16 wherein said second means for granting includes:

means for generating a new version of said at least one module from said present version; and

means for generating a new version of said complex system containing said new version of said at least one module, wherein said new version of said complex system is defined by a master module containing pointers to each of said plurality of modules comprising a most recent version of said complex system.

19. A dynamic versioning system according to claim 16 including:

means for determining a number of said plurality of users having access to a version of said complex system in response to a user request to terminate access to said complex system; and

means for removing old versions of said complex system from non-volatile complex system memory location following termination of complex system access by a last one of said plurality of users having access thereto.