Computer implemented request to integrate (RTI) system for managing change control in software release stream

• US 5,907,705 A
• Filed: 10/31/1996
• Issued: 05/25/1999
• Est. Priority Date: 10/31/1996
• Status: Expired due to Fees

• Current Assignee: Sun Microsystems Incorporated (Oracle Corporation)
• Original Assignee: Sun Microsystems Incorporated (Oracle Corporation)
• Inventors: Carter, Bruce
• Primary Examiner(s): Trammell, James P.
• Assistant Examiner(s): Chavis, John Q.
• Application Number:
  US08/741,819
• Time in Patent Office: 936 Days
• Field of Search: 395/701, 395/702, 395/703
• 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

Change control in a software release stream is managed by a computer implemented Request To Integrate (RTI) system, including at least one user unit having an input unit and a display. A server unit which is connected to the user unit(s) creates and stores RTI files representing requests to integrate changes into the software release stream, and enables a selected RTI file to be displayed on the display unit under control of the input unit. The server unit includes a database in which the RTI files are stored under the Source Code Control System (SCCS), and a search engine for searching the database and displaying selected RTI files and their histories. The RTI files are in World Wide Web (WWW) HyperText Markup Language (HTML) text format, and are accessible through a WWW browser in the user unit(s) and a cooperating WWW server in the server unit. The server unit stores and executes a program including a WWW home page, and developer, evaluator and gatekeeper pages which are accessible through the home page. RTI files are created, edited, viewed, approved, placed on hold, canceled and integrated into the software release stream through the WWW page hierarchy by entering data through the input unit(s). The system further includes a software bug database which is accessible through hyperlinks in the WWW pages, and a user database which limits access to verified users.

Claims

1. A computer implemented Request To Integrate (RTI) system configured to manage change control in a software release stream, comprising:

a user unit including an input unit and a display; and

a server unit which is connected to the user unit and configured to create and store RTI files representing requests to integrate changes into the software release stream, and to cause a selected RTI file to be displayed on the display unit under control of the input unit, in which;

the server unit is configured to create the RTI files in a World Wide Web (WWW) text format;

the user unit comprises a WWW browser;

the server unit comprises a WWW server which communicates with the WWW browser;

the input unit communicates with the WWW server through the WWW browser;

the WWW server communicates with the display through the WWW browser;

the server unit stores and executes a program which includes a WWW page, communicates with the WWW server, and is configured to create and store the RTI files through the WWW page; and

the WWW page comprises;

a home page; and

a developer page, an evaluator page, and a gatekeeper sage which are accessible through the home page under control of the input unit.

2. A system as in claim 1, in which the server unit is further configured to enable editing of a selected RTI file under control of the input unit.

3. A system as in claim 1, in which the server unit comprises a database in which the RTI files are stored.

4. A system as in claim 3, further comprising a search engine which is configured to search the database under control of the input unit.

5. A system as in claim 4, in which the RTI files are stored in the database under the Source Code Control System (SCCS).

6. A system as in claim 5, in which the server unit is further configured to enable a change history of a selected RTI file to be displayed on the display unit under control of the input unit.

7. A system as in claim 1, in which the developer page, the evaluator page and the gatekeep page each enable a selected RTI to be viewed under control of the input unit.

8. A system as in claim 1, in which the developer page and the evaluator page each enable a selected RTI to be edited under control of the input unit.

9. A system as in claim 1, in which the developer page enables a new RTI to be created under control of the input unit.

10. A system as in claim 1, in which the evaluator page enables a selected RTI to be selectively approved for release into the software release stream, placed on hold, or canceled under control of the input unit.

11. A system as in claim 1, in which the gatekeeper page enables a selected RTI to be integrated into the software release stream under control of the input unit.

12. A system as in claim 1, further comprising a software bug database, in which:

the WWW page includes hyperlinks configured to enable the software bug database to be accessed under control of the input unit.

13. A system as in claim 1, further comprising a user name database, in which:

the WWW page is further configured to access the user name database to verify a user name input through the input unit, and to prevent RTI files from being displayed on the display unit until a user name is verified.

14. A computer implemented method for managing change control in a software release stream, comprising the steps of:

(a) providing a computer system including;

at least one input unit; and

a server unit which is connected to said at least one input unit and is configured to create Request To Integrate (RTI) files representing requests to integrate changes into the software release stream, and to perform operations specified by developer data, evaluator data and gatekeeper data which is input through said at least one input unit;

(b) creating an RTI file by inputting developer data through said at least one input unit; and

(c) approving the RTI file by inputting evaluator data through said at least one input unit, in which;

the server unit is configured to create the RTI files in a World Wide Web (WWW) text format;

the user unit comprises a WWW browser;

the server unit comprises a WWW server which communicates with the WWW browser;

the input unit communicates with the WWW server through the WWW browser;

the WWW server communicates with the display through the WWW browser;

the server unit stores and executes a program which includes a WWW page, communicates with the WWW server, and is configured to create and store the RTI files through the WWW page; and

the WWW page comprises;

a home page; and

a developer page, an evaluator page, and a gatekeeper page which are accessible through the home page under control of the input unit.

15. A method as in claim 14, further comprising the step of:

(d) enabling the changes represented by the RTI file to be integrated into the software release stream by inputting gatekeeper data through said at least one input unit.

16. A method as in claim 14, further comprising the step, performed between steps (b) and (c), of:

(d) placing the RTI file on hold be inputting evaluator data through said at least one input unit.

17. A method as in claim 14, further comprising the step of:

(d) canceling the RTI file by inputting evaluator data through said at least one input unit.

18. A digital data storage structure which stores a computer program for managing change control in a software release stream for implementation using a computer system which includes at least one input unit, and a server unit which is connected to said at least one input unit and is configured to create Request To Integrate (RTI) files representing requests to integrate changes into the software release stream, and to perform operations specified by developer data, evaluator data and gatekeeper data which is input through said at least one input unit, the computer program being executed by the server unit and including instructions for performing the steps of:

(a) creating an RTI file in response to developer data input through said at least one input unit; and

(b) approving the RTI file in response to evaluator data input through said at least one input unit, in which;

the server unit is configured to create the RTI files in a World Wide Web (WWW) text format;

the user unit comprises a WWW browser;

the server unit comprises a WWW server which communicates with the WWW browser;

the input unit communicates with the WWW server through the WWW browser;

the WWW server communicates with the display through the WWW browser;

the server unit stores and executes a program which includes a WWW page, communicates with the WWW server, and is configured to create and store the RTI files through the WWW page; and

the WWW page comprises;

a home page; and

a developer page, an evaluator page, and a gatekeeper page which are accessible through the home page under control of the input unit.

19. A structure as in claim 18, in which the program further includes instructions for performing the step of:

(c) enabling the changes represented by the RTI file to be integrated into the software release stream in response to gatekeeper data input through said at least one input unit.

20. A structure as in claim 18, in which the program further includes instructions for performing the step, performed between steps (a) and (b), of:

(c) placing the RTI file on hold in response to evaluator data input through said at least one input unit.

21. A structure as in claim 18, in which the program further includes instructions for performing the step of:

(c) canceling the RTI file in response to evaluator data input through said at least one input unit.

22. A structure as in claim 18, comprising an electronic memory configured to store the computer program.

23. A structure as in claim 18, comprising at least one digital recording medium configured to store the computer program.