System for Managing Automated Report Versions

• US 20090164970A1
• Filed: 12/20/2007
• Published: 06/25/2009
• Est. Priority Date: 12/20/2007
• Status: Abandoned Application

• Current Assignee: AT&T Knowledge Ventures, L.P. (AT&T, Inc.)
• Original Assignee: AT&T Knowledge Ventures, L.P. (AT&T, Inc.)
• Inventors: Borges, Joshua Steven, Meyers, Sean, Gentry, Adam
• Application Number:
  US11/961,633
• Publication Number:
  US 20090164970A1
• Time in Patent Office: Days
• US Class Current: 717/101
• CPC Class Codes: G06F 8/71 Version control security arrangements therefor G06F21/57; Configuration management

Abstract

Disclosed systems manage the modification of objects such as automated reports. Access to modified versions of an automated report is controlled during the modification life cycle. A developer checks out a copy of an automated report and stores minor versions of the automated report during modification. A major version of the automated report is backed up and a copy of the modified automated report is transported to a quality control agent, which may be given substantially exclusive access to the modified automated report. Upon the quality control agent indicating the automated report is a quality-compliant automated report, the quality-compliant automated report is transported to a release manager. The release manager is for determining whether the quality-compliant automated report is a releasable automated report. Upon the release manager determining the quality-compliant automated report is a releasable automated report, the releasable automated report is released to production and replaces the original automated report.

Claims

1. A method of managing object versions, the method comprising:

receiving an object related to a request for revision;

checking out the object to a developer for adaptation to a modified object;

checking in the modified object following adaptation by the developer; and

transporting the modified object to a quality control agent for determining whether the modified object is a quality-compliant object, wherein;

if the modified object is a quality-compliant object, transporting the quality-compliant object to a release manager for determining whether the quality-compliant object is a releasable object, wherein;

if the quality-compliant object is a releasable object, transporting the releasable object to production.

2. The method of claim 1, wherein:

if the modified object is not a quality-compliant object, determining whether the modified object should undergo further modification, wherein;

if the modified object should undergo further modification, checking out the modified object to the developer for further processing.

3. The method of claim 2, wherein:

if the modified object should not undergo further modification, abandoning the modified object.

4. The method of claim 1 further comprising:

determining whether a transport request is received to transport the modified object to quality control, wherein;

if the request transport request is received, checking the modified object for compliance with predetermined parameters.

5. The method of claim 4, wherein the transport request is initiated by the developer.

6. The method of claim 4, wherein if the transport request is not received, notifying the developer that the transport request has not been received.

7. The method of claim 6 further comprising:

notifying a tester associated with the developer that the transport request has not been received.

8. The method of claim 1, wherein transporting the modified object to a quality control agent includes making a back-up copy of the modified object.

9. The method of claim 1 wherein checking out the object to a developer includes:

making a backup the object; and

providing the developer with a copy of the object.

10. The method of claim 1 further comprising:

saving a plurality of versions of the object during adaptation by the developer.

11. The method of claim 1, wherein checking in the modified object includes backing up the modified object.

12. The method of claim 1, wherein receiving an object related to a request for revision includes creating the object from a template.

13. The method of claim 1, wherein if the compliant object is not a releasable object, the method further includes:

determining whether the releasable object should be abandoned, and wherein;

if the releasable object should not be abandoned, submitting the releasable object for further modification.

14. The method of claim 13, wherein if the releasable object should be abandoned, the method further includes:

abandoning the releasable object.

15. The method of claim 1 further comprising:

upon receiving the object related to the request for revision, making a backup copy of the object.

16. A computer program stored on a computer readable medium having instructions operable for:

storing a production report related to a request for revision;

providing substantially exclusive access to the production report to a developer for adaptation into a modified production report;

storing the modified production report following adaptation by the developer; and

providing substantially exclusive access to the modified production report to a quality control agent for a determination of whether the modified production report is a quality-compliant production report, wherein;

if the modified production report is a quality-compliant production report, providing substantially exclusive access to the quality-compliant production report to a release manager for determining whether the quality-compliant production report is a releasable production report, and wherein;

if the quality compliant production report is a releasable production report, substituting the production report with the releasable production report.

17. The computer program of claim 16, further including instructions operable for:

if the modified production report is not a quality-compliant production report, determining whether the modified production report requires further modification, and wherein;

if the modified production report requires further modification, providing to the developer substantially exclusive access to the modified production report for further processing.

18. The computer program of claim 17, further including instructions operable for:

if the modified production report does not require further modification, abandoning the modified production report by restricting access to the modified production report.

19. The computer program of claim 16, further including instructions operable for:

determining whether a transport request is received to transport the modified production report to quality control, and wherein;

if the transport request is received;

checking the modified production report for compliance with predetermined parameters.

20. The computer program of claim 19, wherein if the transport request is not received, instructions are further operable for:

notifying the developer that the transport request has not been received.

21. The computer program of claim 20, further including instructions operable for:

notifying a tester associated with the developer that the transport request has not been received.

22. The computer program of claim 16, further including instructions operable for:

saving a plurality of versions of the production report during adaptation by the developer.

23. The computer program of claim 16, further including instructions operable for:

if the quality-compliant production report is not a releasable production report, determining whether quality-compliant production report should be abandoned, and wherein;

if the releasable production report should not be abandoned, providing the developer with substantially exclusive access to the quality-compliant production report for further modification.

24. A software change management server comprising a machine-readable medium having instructions operable for:

copying an automated report, wherein the copied automated report is for modification by a developer;

checking out the automated report to the developer;

storing one or more minor versions of the automated report;

checking in a revised version of the automated report in response to a check-in request by the developer;

creating a major version of the automated report based on the revised version;

in response to a transport request by the developer;

copying the major version of the automated report as a modified automated report; and

transporting the modified automated report to a quality control agent to result in the quality control agent having substantially exclusive access to the modified automated report for determining whether the modified automated report is a quality-compliant report;

in response to the quality control agent indicating the modified automated report is a quality-compliant report;

copying the modified automated report as a quality-compliant automated report; and

transporting the quality-compliant automated report to a release manager to result in the release manager having substantially exclusive access to the quality-compliant automated report for determining whether the quality compliant report is a releasable automated report; and

in response to the release manager indicating the quality-compliant report is a releasable automated report;

backing up a copy of the automated report; and

replacing the automated report with the releasable report.