SYSTEMS AND METHODS FOR TRACKING SOFTWARE STANDS IN A SOFTWARE PRODUCTION LANDSCAPE

• US 20100153919A1
• Filed: 12/11/2008
• Published: 06/17/2010
• Est. Priority Date: 12/11/2008
• Status: Abandoned Application

• Current Assignee: SAP SE
• Original Assignee: SAP SE
• Inventors: Schroder, Martin, Gauges, Michael, Krueger, Uwe, Kramer, Wolfram
• Application Number:
  US12/332,663
• Publication Number:
  US 20100153919A1
• Time in Patent Office: Days
• US Class Current: 717/122
• CPC Class Codes: G06F 8/71 Version control security arrangements therefor G06F21/57; Configuration management
• CPC Class Codes: G06Q 10/06 Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling

Abstract

According to some embodiments, a first container, representing a first uniquely addressable physical location in a software production landscape, may be associated with a first series of stand snippets related to a software product. Similarly, a second container, representing a second uniquely addressable physical location in the software production landscape, may be associated with a second series of stand snippets related to the software product. Information about a sequence of stand snippets may then be automatically provided to a user, wherein the sequence may include stand snippets from both the first and second containers.

Claims

1. A method associated with a software production landscape, comprising:

associating a first container, representing a first uniquely addressable physical location in the software production landscape, with a first series of stand snippets related to a software product;

associating a second container, representing a second uniquely addressable physical location in the software production landscape, with a second series of stand snippets related to the software product; and

automatically providing, to a user, information about a sequence of stand snippets, wherein the sequence may include stand snippets from both the first and second containers.

2. The method of claim 1, wherein at least a portion of the sequence of stand snippets is associated with a linear process history of the software product including subsequent stand snippets from the same container.

3. The method of claim 1, wherein at least a portion of the sequence of stand snippets is associated with an indirect process history including subsequent stand snippets from different containers.

4. The method of claim 1, wherein each stand snippet is associated with a time interval.

5. The method of claim 4, wherein the time interval for a current stand snippet includes a start time.

6. The method of claim 5, wherein the time interval for a non-current stand snippet includes a start time and an end time.

7. The method of claim 1, wherein the first container is associated with a source version of the software product and the second container is associated with an executable derivative version of the software product built from the source version.

8. The method of claim 7, wherein the first container comprises a directory within a software configuration management tool that hosts snapshots of the software product.

9. The method of claim 1, wherein the sequence of stand snippets represents back-tracking in time from an initial stand snippet.

10. The method of claim 1, wherein the sequence of stand snippets represents forward-tracking in time from an initial stand snippet.

11. The method of claim 1, wherein the sequence of stand snippets is provided up to a designated container.

12. The method of claim 1, wherein the sequence of stand snippets is provided up to a designated stand snippet.

13. The method of claim 1, further comprising:

generating a history tree representing stand snippets from both the first and second containers.

14. The method of claim 1, further comprising:

receiving from a user, via a graphical user interface, a selection associated with a stand snippet, wherein the information about the sequence of stand snippets is provided to the user via the graphical user interface.

15. An apparatus, comprising:

an integration branch to establish a source version of a software product, wherein a first container, representing a first uniquely addressable physical location in a software production landscape, is associated with the source version and a first series of stand snippets related to a software product;

a derivative storage element to receive an executable derivative version of the software product built from the source version, wherein a second container, representing a second uniquely addressable physical location in the software production landscape, is associated with the executable derivative version and a second series of stand snippets related to a software product; and

an application server to automatically provide, to a user, information about a sequence of stand snippets, wherein the sequence may include stand snippets from both the first and second containers.

16. The apparatus of claim 15, further comprising a process log tool core to facilitate an exchange of information with the user.

17. A computer-readable medium storing processor-executable process steps that, when executed by a processor, perform a method, wherein the method comprises:

associating a first container, representing a first uniquely addressable physical location in a software production landscape, with a first series of stand snippets related to a software product;

associating a second container, representing a second uniquely addressable physical location in the software production landscape, with a second series of stand snippets related to the software product; and

automatically providing, to a user, information about a sequence of stand snippets, wherein the sequence may include stand snippets from both the first and second containers.

18. The medium of claim 17, wherein at least a portion of the sequence of stand snippets is associated with at least one of:

(i) a linear process history of the software product including subsequent stand snippets from the same container, or (ii) an indirect process history including subsequent stand snippets from different containers.

19. The medium of claim 17, wherein each stand snippet is associated with at least one of:

(i) a time interval, (ii) a current stand snippet, (iii) a start time, (iv) a non-current stand snippet, or (v) an end time.

20. The medium of claim 17, wherein the first container is associated with a source version of the software product and the second container is associated with an executable derivative version of the software product built from the source version.

21. The medium of claim 17, wherein the sequence of stand snippets represents one of:

(i) back-tracking in time from an initial stand snippet, or (ii) forward-tracking in time from an initial stand snippet.

22. The medium of claim 17, wherein the sequence of stand snippets is provided up to one of:

(i) a designated container, or (ii) a designated stand snippet.