Method and system for server based software product release version tracking

• US 7,076,496 B1
• Filed: 09/27/2001
• Issued: 07/11/2006
• Est. Priority Date: 02/23/2001
• Status: Expired due to Fees

• Current Assignee: Hewlett-Packard Development Company, L.P. (HP Inc.)
• Original Assignee: 3Com Corporation (HP Inc.)
• Inventors: Ruizandrade, Guillermo
• Primary Examiner(s): AMSBURY, WAYNE P
• Application Number:
  US09/967,053
• Time in Patent Office: 1,748 Days
• Field of Search: 707/203, 707/102, 717/103, 717/170
• 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/959 Network
• CPC Class Codes: Y10S 707/99943 Generating database or data structure, e.g. via user interface

Abstract

A method for maintaining software product version tracking in a client/server computer system environment. The method includes the step of storing a plurality of software product versions within a database. A plurality of directories of the database are traversed to determine paths for each of the plurality of software product versions, the traversing performed by a server. At least one of the software product versions is select for updating, the selecting performed by one of a plurality of clients. The one software product version is edited using the one client and a resulting new software product version is subsequently returned to the database. Using the server, the directories of the database are updated to chronologically track the new software product version to ensure the paths for each of the plurality of software product versions and the new software product version are available to the plurality of clients.

Claims

1. A method for maintaining software product version tracking in a client/server computer system environment, the method comprising:

storing a plurality of software product versions within a single database;

traversing a plurality of directories of the single database to determine paths for each of the plurality of software product versions, the traversing performed by a server;

selecting one of the software product versions for updating, the selecting performed by one of a plurality of clients;

receiving a copy of the selected one of said software product versions at said one client, wherein the selecting and receiving of one of the software product versions for updating does not limit a second client from selecting and receiving the same one of the software product versions received by said one client from said single database;

editing the one software product version using the one client and returning a resulting new software product version to the single database; and

using the server, updating the directories of the single database to chronologically track the new software product version to ensure the paths for each of the plurality of software product versions and the new software product version are available to the plurality of clients.

2. The method of claim 1 further including:

executing a server component on the server in order to make the new software product version visible to the plurality of clients.

3. The method of claim 1 further including:

using the server, creating a file containing the paths for each of the software product versions, the file used by the clients to access to software product versions.

4. The method of claim 1 further including:

using the server, maintaining a chronological arrangement of the software product versions; and

maintaining a tree structure for tracking one or more chronological arrangements of the software product versions.

5. The method of claim 4 further including:

maintaining a plurality of tree structures for a respective plurality of software product development projects to maintain the software product version tracking.

6. The method of claim 4 further including:

using a graphical user interface of the client to access to tree structure of the chronological arrangements of the software product versions.

7. The method of claim 1 further including:

using a graphical user interface of the client to select the one software product version for updating.

8. The method of claim 1 wherein the server and the plurality of clients are communicatively coupled via a local area network.

9. The method of claim 1 wherein the server and at least one of the plurality of clients are communicatively coupled via the Internet.

10. A system for maintaining software product version tracking in a client/server computer system environment, the system comprising:

a client-server computer system coupled via a network, the client server computer system configured to execute computer readable code for implementing a method for product version tracking, the method comprising;

storing a plurality of software product versions within a single database;

traversing a plurality of directories of the single database to determine paths for each of the plurality of software product versions, the traversing performed by a server;

selecting one of the software product versions for updating, the selecting performed by one of a plurality of clients;

receiving a copy of the selected one of said software product versions at said one client, wherein the selecting and receiving of one of the software product versions for updating does not limit a second client from selecting and receiving the same one of the software product versions received by said one client from said single database;

editing the one software product version using the one client and returning a resulting new software product version to the single database; and

using the server, updating the directories of the single database to chronologically track the new software product version to ensure the paths for each of the plurality of software product versions and the new software product version are available to the plurality of clients.

11. The system of claim 10 further including:

executing a server component, on the server in order to make the new software product version visible to the plurality of clients.

12. The system of claim 10 further including:

using the server, creating a file containing the paths for each of the software product versions, the file used by the clients to access to software product versions.

13. The system of claim 10 further including:

using the server, maintaining a chronological arrangement of the software product versions; and

maintaining a tree structure for tracking one or more chronological arrangements of the software product versions.

14. The system of claim 13 further including:

maintaining a plurality of tree structures for a respective plurality of software product development projects to maintain the software product version tracking.

15. The system of claim 13 further including:

using a graphical user interface of the client to access to tree structure of the chronological arrangements of the software product versions.

16. The system of claim 10 further including:

using a graphical user interface of the client to select the one software product version for updating.

17. The system of claim 10 wherein the server and the plurality of clients are communicatively coupled via a local area network.

18. The system of claim 10 wherein the server and at least one of the plurality of clients are communicatively coupled via the Internet.

19. A computer readable media having thereon computer readable code which when executed in a client server computer system cause the computer system to implement a method for maintaining software product version tracking, the method comprising:

storing a plurality of software product versions within a single database;

traversing a plurality of directories of the single database to determine paths for each of the plurality of software product versions, the traversing performed by a server;

selecting one of the software product versions for updating, the selecting performed by one of a plurality of clients;

receiving a copy of the selected one of said software product versions at said one client, wherein the selecting and receiving of one of the software product versions for updating does not limit a second client from selecting and receiving the same one of the software product versions received by said one client from said single database;

editing the one software product version using the one client and returning a resulting new software product version to the single database; and

using the server, updating the directories of the single database to chronologically track the new software product version to ensure the paths for each of the plurality of software product versions and the new software product version are available to the plurality of clients.

20. The computer readable media of claim 19 further including:

using the server, creating a file containing the paths for each of the software product versions, the file used by the clients to access to software product versions.

21. The computer readable media of claim 19 further including:

using the server, maintaining a chronological arrangement of the software product versions; and

maintaining a tree structure for tracking one or more chronological arrangements of the software product versions.

22. The computer readable media of claim 21 further including:

maintaining a plurality of tree structures for a respective plurality of software product development projects to maintain the software product version tracking.

23. The computer readable media of claim 21 further including:

using a graphical user interface of the client to access to tree structure of the chronological arrangements of the software product versions.

24. The computer readable media of claim 19 further including:

using a graphical user interface of the client to select the one software product version for updating.