EP0840212A1 - Rechnerimplementiertes System für Anforderungen zur Integration zur Änderungsverwaltung in einem Softwareausgabestrohm - Google Patents

Rechnerimplementiertes System für Anforderungen zur Integration zur Änderungsverwaltung in einem Softwareausgabestrohm Download PDF

Info

Publication number
EP0840212A1
EP0840212A1 EP97118160A EP97118160A EP0840212A1 EP 0840212 A1 EP0840212 A1 EP 0840212A1 EP 97118160 A EP97118160 A EP 97118160A EP 97118160 A EP97118160 A EP 97118160A EP 0840212 A1 EP0840212 A1 EP 0840212A1
Authority
EP
European Patent Office
Prior art keywords
rti
page
www
user
unit
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Withdrawn
Application number
EP97118160A
Other languages
English (en)
French (fr)
Inventor
Bruce Carter
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Sun Microsystems Inc
Original Assignee
Sun Microsystems Inc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Sun Microsystems Inc filed Critical Sun Microsystems Inc
Publication of EP0840212A1 publication Critical patent/EP0840212A1/de
Withdrawn legal-status Critical Current

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00—Arrangements for software engineering
    • G06F8/70—Software maintenance or management
    • G06F8/71—Version control; Configuration management
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00—Administration; Management
    • G06Q10/06—Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling

Definitions

  • the present invention generally relates to the art of computer software development, and more specifically to a computer implemented request to integrate (RTI) system for managing change control in a software release stream.
  • RTI request to integrate
  • Group workspace hierarchies are used to manage the development, integration and release of software. It is essential to minimize development overhead yet provide the necessary change control needed to track software releases based upon bug fixes, code changes, feature releases, product enhancements and documentation changes.
  • 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.
  • RTI Request To Integrate
  • 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.
  • SCCS Source Code Control System
  • 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.
  • WWW World Wide Web
  • HTML HyperText Markup Language
  • 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 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.
  • the present invention is especially suited to a medium to large software organization with a number of software projects.
  • the invention is a software engineering tool used by developers, integrators and managers to manage the software release change control process, and is used as an adjunct to "TeamWare” (development group) software integration tools.
  • the overall business objective which is accomplished by a system according to the present invention is maintaining a fluid and controlled software release cycle.
  • TeamWare workspace hierarchies are used to manage the development, integration and release of software. Integration consists of merging the changes made by individual developers with one or more release streams.
  • Request-To-Integrate is a mechanism by which change control can be managed.
  • An important strategy is to minimize development overhead yet provide the necessary change control needed to track software releases based upon bug fixes, code changes, feature releases, product enhancements and documentation changes.
  • the present invention implements the RTI mechanism and process, provides a change review team with data for making decisions regarding change management and quality control, and further provides a release engineering team with data for building components for software release.
  • the present RTI system provides a form fill-in method for Developers to create RTIs to identify proposed changes to the code base.
  • the data provided in the RTI provides the CRT with the information needed to assess whether or when an RTI will be accepted.
  • An RTI typically includes: a list of source file changes, creates, deletions or renames; list of bugids (software bug identifications); a pointer to the unit test plan and results; a code review sign-off; a project-specific checklist of completed tasks required before check-in; the name of the project or release stream into which the integration is to occur; the name of the originator.
  • RTIs belong to one of two super-states: Open or Closed.
  • Open super-state an RTI can be New, Approved or on Hold.
  • Closed super-state an RTI can be either Canceled or Integrated.
  • the system checks the validity of certain fields within the RTI and refuses the submission when errors are detected.
  • the system further checks the bug tracking system to verify that all bugids listed in the RTI have the bug state of "evaluated", as listed in TABLE I below.
  • the system sends an e-mail notification to the originator, the Evaluator and the Gatekeeper for the project.
  • the system may optionally copy other interested parties.
  • the system stores the RTI as an ASCII file and names it using the next available RTI number.
  • New RTIs can transition to one of 3 states: Approved, Hold or Canceled. Transition is based upon the careful scrutiny and action taken by the Evaluator(s). A regular meeting is held by the CRT to collectively evaluate RTIs that have been submitted.
  • the CRT consists of members of development engineering, release engineering, test engineering and technical publications.
  • the project RTI Evaluators will have received system notification of any new RTIs or state changes to existing RTIs since the previous meeting.
  • each project RTI Evaluator is able to summarize for the team and provide an opinion for approval action or disposition for RTIs under review.
  • the system provides an RTI summary report for the purposes of the CRT meeting.
  • An Evaluator will examine the information provided in the RTI, and based upon several factors make a decision whether to approve the RTI or not.
  • One of the strategies used includes cross-checking information found in the bug reports identified by the bugids in the RTI with other information in the RTI such as the list of affected source files.
  • Another strategy is to consult with the code reviewer identified in the RTI regarding the proposed changes.
  • the Evaluator may follow a strategy to check for software interface compliance. The test plan and results are reviewed and examined for completeness. A project-specific check-in checklist is reviewed to assess software readiness.
  • the system changes the state of the RTI to "Approved” and sends e-mail notification to the interested parties, marks the bugids listed in the RTI as "committed” within the bug tracking system, and logs the action.
  • the principal target of the approval notification is the project Gatekeeper who upon receipt of the approval notification opens the gate and permits the Developer to putback his changes and merge them with the release stream.
  • the Evaluator determines the RTI is not ready for approval, he may place the RTI in a "Hold" state. Again, the system sends e-mail notification to the interested parties. The Evaluator may add information to the RTI by using the Update action. As with the state change actions, an Update action will result in the system sending an e-mail notification to the interested parties.
  • the Evaluator may choose to Cancel an RTI when it is in any of the Open states.
  • the Evaluator may only approve an RTI for the current integration build and not for any future builds.
  • the system allows Developers or Evaluators to update an RTI as long as it is in the Open super-state. Updates are performed in a free-form edit mode with access to all fields of information.
  • the system When an update action has been submitted, the system sends an e-mail notice to the interested parties.
  • the system maintains a history log of all RTI changes, and provides a way to review the history log.
  • the log identifies who made the change based upon: e-mail address, remote host name and remote host address.
  • the system utilizes a file locking mechanism to prevent overwriting due to simultaneous updates by different users.
  • the system makes it possible for more than one person to work on an RTI, including Developers other than the originator.
  • the Gatekeeper opens the gate and grants permission for the putback to occur.
  • the Gatekeeper knows who to open the gate for by reading the RTI and identifying the RTI originator.
  • the Gatekeeper buildstamps the RTI with the name of the build, and moves the RTI to an Integrated state. This transition places the RTI into the Closed super-state. All bugids listed in the RTI are marked within the bug tracking system as "Fixed in” and "Integrated in” for the name of the release build. The system sends an e-mail notification to all the interested parties upon the state transition, and logs the action.
  • An RTI may be placed into a "Hold" state by the Evaluator.
  • the Evaluator may place the RTI on hold if the state is New or Approved.
  • the hold state is useful if project circumstances are changing and it is not clear when the RTI can be approved for a current integration build, yet the situation is not bad enough to warrant a cancellation if there is a chance that the RTI can be integrated soon.
  • the system sends an e-mail notification to all the interested parties upon the state transition, and logs the action.
  • the system sends an e-mail notification to all the interested parties, and logs the action.
  • the system provides a number of reporting mechanisms, including the following.
  • the system organizes and stores RTIs in a hierarchical fashion as separate ASCII files under SCCS, which provides the file locking and file history mechanisms.
  • RTIs are organized by project. Under each project, there is a secondary level corresponding to the RTI super-states --Open and Closed.
  • the format of the RTI file can be project-specific to allow for variances in project requirements. Although each project could in theory use a different file format, in practice it is efficient and useful to use the same format for all projects if possible. Except during the RTI Create process, where form fill-in is used, variances in RTI file formats should be transparent to the user and not be reflected in or impact the overall RTI system User Interface model.
  • a computer implemented Request To Integrate (RTI) system 10 for managing change control in a software release stream includes at least one user unit or terminal 12 which is typically implemented as a personal computer workstation.
  • a preferred workstation is a SUN SPARC terminal running a version of the UNIX operating system, although the invention can be practiced using a variety of other personal computers and operating systems.
  • the terminal 12 includes an input unit 12a having one or more input devices such as a keyboard and a mouse which enable a user to input commands and data into the system 10. Although not explicitly illustrated, the terminal 12 is further provided with a processor unit, volatile and non-volatile data storage units, and other conventional devices.
  • a display unit 12b such as a cathode ray tube or liquid crystal monitor displays alphanumeric and graphical data which is required for implementing the system 10, and a text editor 12c.
  • the terminal 12 further includes a World Wide Web (WWW) browser 12d such Netscape that enables the terminal 12 to directly read WWW page files which are preferably clear text ASCII files written HyperText Markup Language (HTML).
  • WWW World Wide Web
  • HTML HyperText Markup Language
  • the browser 12d utilizes the text editor 12c, which is preferably Java based, to edit RTI files are created by a developer.
  • the Java text editor 12c enables the terminal 12 to be based on other than a SPARC/UNIX configuration, for example an IBM PC platform runing Microsoft Windows.
  • the system 10 further comprises a server unit 14 which is connected to the terminal 12. Although only one terminal 12 is illustrated in the drawing, in a practical application a plurality of terminals 12 will be provided at locations remote from the server unit 14, and connected thereto by a Wide Area Network (WAN), Local Area Network (LAN), etc. as indicated at 16.
  • WAN Wide Area Network
  • LAN Local Area Network
  • each programmer or developer will have an individual terminal 12 which is used for developing program code as well as creating and managing RTIs, sending and receiving e-mail, and performing a variety of other tasks. Management and supervisory personnel will also be provided with their own terminals. For simplicity of description, however the terminal 12 will be referred to in the singular, keeping mind that in a preferred application there will be a plurality of terminals 12.
  • the server unit 14 includes a WWW (httpd) server 18 which communicates with the browser 12d of the terminal 12. This enables a user to input a form or query to the server 18, and receive data back as HTML code for display on the display unit 12b.
  • WWW httpd
  • the program code which implements the functionality of the invention includes a "Rtitool" 20 which is stored in memory and executed by a processor (not shown) of the server unit 14.
  • the Rtitool 20 includes a WWW page hierarchy which will be described in detail below.
  • the server unit 14 further includes an RTI database 22 which preferably stores RTI files under the Source Code Control System (SCCS) protocol.
  • the Rtitool 20 includes program code which enables it to access the database 22 using a conventional Wide Area Information System (WAIS) server 24 via a WAIS database unit 26 which includes a WAIS database 26a and an indexer 26b.
  • WAIS Wide Area Information System
  • the Rtitool 20 further includes program code which enables it to communicate with a software bug database 30 and a names database 32 via the WAN 16, and an action log 28 which lists actions performed by the system 10.
  • the bug database 30 is preferably a Sybase system, and is queried by the Rtitool 20 using conventional SQL or dbwrite language.
  • FIG. 2 illustrates the basic information flow through the Rtitool 20, the web server 18, and the client or user via the terminal 12.
  • a Common Gateway Interface provides communication between a gateway of the Rtitool 20 and the web server 18.
  • the web browser 12d sends keystrokes captured from the user to the httpd server 18.
  • the httpd server 18 accepts the input, starts up the Rtitool 20, and hands the input to the Rtitool 20 via the CGI.
  • the user's keystrokes are passed to Rtitool 20 either via environment variables (called the GET method) or using standard input (called the POST method).
  • the Rtitool 20 then parses the input and processes it.
  • the Rtitool 20 may generate HTML output, which is returned to the httpd server 18 to pass to the user, or it may save data to a file or database or send e-mail to a relevant person.
  • the Rtitool 20 gateway is preferably written in Perl.
  • the system 10 as viewed by the user on the display unit 12b is a hierarchical configuration of web pages and RTI files which are arranged as illustrated in FIGs. 3 and 4.
  • the Rtitool 20 includes a WWW home page, and developer, evaluator, and gatekeeper pages which are accessible through the home page.
  • the developer page enables access to subpages which enable a developer to create, view, edit and list the history of a selected RTI in response to developer data which is applied as user inputs to the input unit 12a of the terminal 12.
  • the evaluator page enables an evaluator to approve, place on hold, cancel, view, edit, and list the history of an RTI.
  • the gatekeeper page enables a gatekeeper to integrate or view an RTI.
  • RTIs are stored as WWW (.html) files in the database 22, and are organized by project.
  • a project normally corresponds to a single TeamWare workspace.
  • RTIs are always in one of 2 super-states: Open or Closed. Their location within the file organization parallels the super-state of the RTI.
  • FIGs. 5a and 5b illustrate how an RTI file is stored in the database 22.
  • An RTI file is created by a developer as a clear text ASCII file in HTML format via the web page hierarchy which is collectively designated as 20a in FIG. 5, with a file extension of .html.
  • a SCCS system 22a which manages the database 22 creates, in addition to the .html source files 22b, an SCCS file 22c.
  • the SCCS system 22a stores original RTI files, but does not store changed RTI files per se. Instead, the system 22a stores changes to an original .html file in the SCCS file 22c as a "delta", which consists of only the changes themselves.
  • the SCCS file 22c lists the change history of the RTI in the form of a list of the "deltas", including the name of the person making a change, the items that were changed, and other relevant data.
  • FIG. 6 is a simplified view of the home page 40 of the Rtitool 20.
  • the home page 40 is viewed using the browser 12d in the same manner as viewing any other page on the World Wide Web (WWW), and includes a number of generic submit buttons 42 which enable a user to navigate through a web site.
  • the home page 40 is accessed by means of a location window 44 which enables a user to locate the home page 40 by typing its Uniform Resource Locator (URL) therein.
  • URL Uniform Resource Locator
  • a button 46 is provided which enables the user to select a role (developer, evaluator, gatekeeper) by means of a pointing device (e.g. mouse) of the input unit 12a. Although not explicitly illustrated, clicking on the button 46 causes a dialog box to be displayed which includes a list of roles from which the user can select.
  • a role developer, evaluator, gatekeeper
  • clicking on the button 46 causes a dialog box to be displayed which includes a list of roles from which the user can select.
  • a similar button 48 is provided to open a dialog box list display which enables the user to select a project from a list which is structured as shown in FIG. 4.
  • a box 50 enables a user to identify himself by typing in his e-mail address, which represents a user name to the system 10.
  • the home page 40 further preferably includes hypertext links 54 to, for example, the home page 40 itself, a webmaster (the system administrator) function, the search engine (WAIS server 24), a report generator of the Rtitool 20, and a help system.
  • hypertext links 54 to, for example, the home page 40 itself, a webmaster (the system administrator) function, the search engine (WAIS server 24), a report generator of the Rtitool 20, and a help system.
  • FIG. 7 illustrates the developer page which is designated as 40a, in which like elements are designated by the same reference numerals as in FIG. 6.
  • the developer page 40a includes a "picklist" box 58 which displays a list of RTIs which have been previously selected or opened. An RTI can be selected by clicking on its name in-the box 58 (e.g. 1234628 N ddi,el).
  • a refresh button 60 enables the list in the box 58 to be updated.
  • buttons 62 enable a new RTI to be created, or an RTI which was selected from the box 58 to be viewed, edited, or its history displayed. It will be noted that the buttons 62 correspond to the subpages listed in FIG. 3.
  • buttons 62 brings up a create, view, edit or history subpage which includes options for performing a corresponding function via inputs from the input unit 12a.
  • the evaluator and gatekeeper pages and their corresponding subpages are also accessible through the home page 40. These pages preferably include hyperlinks which enable access to, for example, the bug database 30.
  • FIGs. 8a to 8f in combination constitute a flowchart of the operation of the hierarchical structure of the Rtitool 20 WWW pages.
  • FIG. 8a is a top level flow diagram illustrating how the user inputs are parsed to determine which page is to be processed.
  • FIG. 8b illustrates how inputs to the home page are processed, and a subpage selected in response thereto.
  • FIG. 8c illustrates how inputs to the developer page are processed, and a create, display, edit, history or refresh operation is performed in response thereto.
  • FIG. 8d illustrates how inputs to the create page are processed to create a new RTI.
  • FIG. 8e illustrates how inputs to the evaluator page are processed, and an approve, hold, cancel, view, edit, history or refresh function is performed in response thereto.
  • FIG. 8f illustrates how inputs to the gatekeeper page are processed, and an integrate, display or refresh operation is performed in response thereto.
  • the Rtitool 20 is accessed by the web browser 12d (e.g. Netscape. A text-only mode will not be supported.
  • the web browser 12d used must support multiple submit buttons in a single form to access the Rtitool 20.
  • the system 10 will detect if a browser cannot meet this requirement during system login through the Rtitool home page, and will give the user an error message with a description of the problem and a suggested resolution.
  • the RTI system 10 provides an authentication function at login to verify who the user is by accessing the names database 32. This database contains official information on every employee who is authorized to access the system 10.
  • the authentication function compares the e-mail address entered by the user with the e-mail address in the database 32, and refuses system access to the user if the comparison fails.
  • the RTI Process Workflow identifies 6 distinct user profiles.
  • the primary users of the system 10 are the Developer, Evaluator and Gatekeeper. Primary users are able to cause RTI state transitions. Secondary users of the system are mainly hunter/gather-type browsers.
  • each primary user has a dedicated home page that is tailored for the tasks to be performed. Only the functions which that user can perform appear on the page. The system places the user at this page following system login. Common to all primary user home pages is an RTI picklist.
  • the picklist displays RTIs which the user can perform some action on.
  • the data shown in the picklist includes: RTI number, State, Keywords.
  • This function enables the user to create an RTI by using a forms-based submittal.
  • the system 10 displays a form which the user fills out by typing text into text boxes.
  • the user can also cut and paste information from OpenWindows applications into the form such as output from a TeamWare putback command.
  • the user presses a submit button and the form is sent to the RTI system for validation.
  • a validation function Upon receipt of the RTI create submission, a validation function processes the form, and based upon project-defined criteria, determines if the RTI can be accepted into the system.
  • RTI If the RTI is accepted into the system, a number will be assigned to the RTI by a number generator function. The RTI will be placed under SCCS and assigned the RTI state of "New".
  • the system 10 will then refresh the RTI picklist and give the user an informational message confirming the RTI creation.
  • This function enables a user to view an RTI file.
  • the user selects an RTI to view from the RTI picklist by clicking on the RTI and then pressing the View button.
  • the system 10 then gets the RTI and displays it on the display unit 12b.
  • An RTI may include embedded hyperlinks to other documents.
  • each bugid is a hyperlink which when followed will display the bug report from the bug database 30. Users may wish to embed hyperlinks to test plans and other documents.
  • This function enables a user to edit an RTI to make additions, deletions or changes.
  • the user selects an RTI to edit from the RTI picklist and presses the Edit button.
  • the system 10 then checks-out the file under SCCS and launches the text editor 12c. If the file cannot be checked out, the user will receive a file busy message.
  • the user can begin editing the RTI.
  • the user can use the save option and quit the text editor 12c.
  • the system 10 will ask if the user wants to continue, or cancel the edit operation. If the user responds 'quit', the file will be unchecked-out and the user will be returned back to the Developer or Evaluator page.
  • the file will be checked-in, and the user will be returned back to the Developer or Evaluator page.
  • the system 10 will place a delta comment into the RTI SCCS history file 22c indicating who made the change and send a notification message.
  • This function enables a user to see the RTI SCCS history comments, and to select any delta from the SCCS history file 22c for viewing.
  • the user selects an RTI from the RTI picklist, and presses the History button.
  • the system 10 displays on the display unit 12b the output of a 'sccs print file' command in html format.
  • the SCCS delta number is a hyperlink which the user can select, and the system 10 will then retrieve the version of the RTI file selected and display it on the screen.
  • This function enables the user to refresh the RTI picklist display. On each primary user screen there is a button to refresh the RTI picklist display. Since the Rtitool is a web application and the picklist display is not a real time display, the user needs a refresh function to cause the web server to update the display in certain situations.
  • the picklist will be up to date because Rtitool 20 will re-examine the RTIs whenever the page is redisplayed. If the user has not taken any actions that would have repainted the displayed, or used the back button to a previous page, the picklist could be out of date. Pressing the Refresh button causes the picklist to be updated. An example of how this function could be used is if a user left the page up for some period of time, then returned, and wanted to see if there were any changes in the picklist.
  • This function enables a user to change an RTI state to Approved.
  • the user selects an RTI to approve from the RTI picklist, and presses the Approve button.
  • the system 10 then checks-out the file under SCCS. If the file cannot be checked out, the user will receive a file busy message.
  • the system 10 asks the user if he wants to provide any comments for the delta commentary. If so, the user can type comments into a text box which will be placed into the file history. The system 10 will delta the file, changing the state to 'Approved', and send a notification message. The system 10 marks each bugid listed in the RTI as 'commit to fix' in the bug database.
  • This function enables the user to change an RTI state to Hold.
  • the user selects an RTI to hold from the RTI picklist, and presses the Hold button.
  • the system 10 then checks-out the file under SCCS. If the file cannot be checked out, the user will receive a file busy message.
  • the system 10 asks the user if he wants to provide any comments for the delta commentary. If so, the user can type comments into a text box which will be placed into the file history. The system 10 will then delta the file, changing the state to 'Hold', and send a notification message.
  • This function enables the user to change an RTI state to Canceled.
  • the user selects an RTI to cancel from the RTI picklist, and presses the Cancel button.
  • the system 10 then checks-out the file under SCCS. If the file cannot be checked out, the user will receive a file busy message.
  • the system 10 will ask the user if he wants to provide any comments for the delta commentary. If so, the user can type comments into a text box which will be placed into the file history. The system 10 will delta the file, changing the state to 'Canceled', and send a notification message.
  • This function enables a user to change an RTI state to Integrated.
  • the user selects an RTI to integrate from the RTI picklist, and presses the Integrate button.
  • the system 10 then checks-out the file under SCCS. If the file cannot be checked out, the user will receive a file busy message.
  • the user selects which build to buildstamp the RTI from a pop-up list of release names.
  • the system 10 will delta the file, changing the state to 'Integrated' and send a notification message.
  • the system 10 marks each bugid listed in the RTI as 'fixed' and 'integrated' in the bug database 30.
  • the web browser 12d provides file print, save, mail and other functions useful to the user, but are not described further herein.
  • This function enables the user to search and display RTIs in the RTI database 22 based upon keyword matching using the WAIS server 24 and WAIS database 26.
  • the user can enter a list of keywords with optional search modifiers which are to be searched for in the RTI database 22.
  • the scope of the search can be adjusted by selecting which projects are searched.
  • Search results returned include the RTI number, and a short synopsis derived from the RTI to give the user a sense of what the RTI contains.
  • the RTI number is used as a hyperlink which the user can click on, and the system 10 displays the full text of the RTI.
  • This function enables a user to generate a report from a menu selection of pre-defined report formats.
  • pre-defined reports are provided for the most frequently requested types of data.
  • the help page provides details on how to use the Rtitool 20 that covers the most frequently asked questions such as what the RTI state transitions mean, how to begin using Rtitool, etc.
  • This function validates an RTI submission based upon project-specific criteria. At a minimum, the validation function verifies that the bugids listed in the RTI have been evaluated, and will reject the submission if any bugids have not been evaluated.
  • This function gets the next available RTI number for a new RTI.
  • the system 10 keeps a record of the last RTI number that was used. When a new RTI number is needed, the system 10 retrieves the last RTI number and increments it for the new number.
  • a locking mechanism is used to prevent simultaneous users from getting the same RTI number.
  • This function informs the user that a change to an RTI has occurred.
  • the system 10 sends an e-mail message to the Originator of the RTI, the project Evaluator and Gatekeeper, and e-mail addresses listed in the RTI Interest list field whenever one of the following events occurs.
  • the change notice indicates what type of change occurred, and useful information from the RTI header such as: file id, state, project, originator, build.
  • System messages provide status to the user and system administrator. Three message categories are defined.
  • Informational messages are used to give the user positive feedback about some action he has taken such as approving an RTI.
  • An informational message is a one-line message that appears directly under the Rtitool navigation bar.
  • Warning messages are used to tell a user that he has taken some action which requires remedial action such as mistyping his e-mail address during login.
  • the warning message appears on a separate page.
  • Fatal messages are used to tell a user and the system administrator that a serious internal system error has occurred. The user will see a message that tells him to contact the system administrator. The system administrator will find the fatal error message in the web server error log file.
  • the Rtitool 20 maintains the action log 28 to track the usage of the system 10 by the users.
  • the action log file preferably contains the following data: date, type of action, project, RTI selected, user e-mail address, user remote host name, user remote host address. This information is formatted in a one-line record within the action log file.
  • This function cleans up old RTI files that may have been checked-out for editing, but not checked-in after a pre-set time limit. It is possible that a user took some action which resulted in an RTI file being checked out but never checked back in.
  • the housekeeping function periodically sweeps the system 10 of such files by performing an 'sccs unedit' on the files. This type of function can run on the web server 18 and be set up and maintained by the system administrator.
  • This function enables login to a primary user home page to be restricted. It may be desirable to restrict the login to certain primary user pages such as Evaluator or Gatekeeper. This can be accomplished by checking a security flag in the project configuration file, and if security is turned on, the system 10 will compare the user e-mail address with the name in the project configuration file. A second level of security can be arranged so that a password is required to access the primary user pages.
  • the present invention provides innovative features and advantages including the following.
  • the Java text editor 12c in each terminal 12 can be omitted, and a text editor which is used by all terminals can be provided in the server unit 14.
  • WAIS server 24 and database 26 can be replaced by another search engine such as "Harvest”, which is available from the University of Colorado.
  • This invention is applicable to a medium to large software organization with a number of software projects.
  • the invention is a software engineering tool used by developers, integrators and managers to manage the software release change control process.
EP97118160A 1996-10-31 1997-10-20 Rechnerimplementiertes System für Anforderungen zur Integration zur Änderungsverwaltung in einem Softwareausgabestrohm Withdrawn EP0840212A1 (de)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US741819 1985-06-06
US08/741,819 US5907705A (en) 1996-10-31 1996-10-31 Computer implemented request to integrate (RTI) system for managing change control in software release stream

Publications (1)

Publication Number Publication Date
EP0840212A1 true EP0840212A1 (de) 1998-05-06

Family

ID=24982345

Family Applications (1)

Application Number Title Priority Date Filing Date
EP97118160A Withdrawn EP0840212A1 (de) 1996-10-31 1997-10-20 Rechnerimplementiertes System für Anforderungen zur Integration zur Änderungsverwaltung in einem Softwareausgabestrohm

Country Status (3)

Country Link
US (1) US5907705A (de)
EP (1) EP0840212A1 (de)
JP (1) JPH10222351A (de)

Cited By (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
GB2339311A (en) * 1998-04-01 2000-01-19 Multex Systems Inc Storage and retrieval of documents using markup languages
WO2000051018A2 (en) * 1999-02-23 2000-08-31 Planet-Intra.Com Java editor
EP1195675A1 (de) * 2000-07-14 2002-04-10 Sun Microsystems, Inc. Kommentargesteuerte Verarbeitung
EP1288805A1 (de) * 2001-08-24 2003-03-05 Accenture Global Services GmbH Ecommerce Benchmarking
EP1296232A2 (de) * 2001-09-24 2003-03-26 Siemens Energy & Automation, Inc. Vorrichtung und Verfahren zum Programmieren von programmierbaren Steuerungen und zum Generieren von Konfigurationsdaten aus einem zentralen Server
EP1342170A1 (de) * 1999-11-29 2003-09-10 Interwoven Inc. Verfahren und gerät, um daten zwischen datenzielen für webseitenentwicklung und -wartung zu bewegen
EP1688835A1 (de) * 2005-02-03 2006-08-09 Sap Ag Verfahren und Computersystem zur Steuerung eines Softwareaktualisierungsprozess in einer Softwaresystemumgebung
EP1881447A1 (de) * 2006-07-21 2008-01-23 Microsoft Corporation Verwaltung von Softwareversionen
WO2009154928A1 (en) * 2008-06-18 2009-12-23 The Boeing Company Supplier build status visibility tool

Families Citing this family (59)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5978836A (en) 1997-07-28 1999-11-02 Solectron Corporation Workflow systems and methods
US7546346B2 (en) * 1997-07-28 2009-06-09 Juniper Networks, Inc. Workflow systems and methods for project management and information management
US6626953B2 (en) * 1998-04-10 2003-09-30 Cisco Technology, Inc. System and method for retrieving software release information
US6167568A (en) * 1998-06-30 2000-12-26 Sun Microsystems, Inc. Method and apparatus for implementing electronic software distribution
US6385763B1 (en) * 1998-12-29 2002-05-07 At&T Corp. Methodology for mapping use cases to operations for operational profile development
US6895551B1 (en) 1999-09-23 2005-05-17 International Business Machines Corporation Network quality control system for automatic validation of web pages and notification of author
US7146608B1 (en) * 1999-09-28 2006-12-05 Cisco Technology, Inc. Method and system for a software release process
US6848080B1 (en) 1999-11-05 2005-01-25 Microsoft Corporation Language input architecture for converting one text form to another text form with tolerance to spelling, typographical, and conversion errors
US7165019B1 (en) 1999-11-05 2007-01-16 Microsoft Corporation Language input architecture for converting one text form to another text form with modeless entry
US7403888B1 (en) * 1999-11-05 2008-07-22 Microsoft Corporation Language input user interface
US7047493B1 (en) * 2000-03-31 2006-05-16 Brill Eric D Spell checker with arbitrary length string-to-string transformations to improve noisy channel spelling correction
US7657872B2 (en) * 2000-10-23 2010-02-02 Nintendo Of America Inc. Product testing and bug tracking system
EP1351108B1 (de) * 2000-11-24 2015-06-24 Mitsubishi Denki Kabushiki Kaisha Verfahren und vorrichtung zur programmierung
WO2002054219A2 (en) * 2000-12-29 2002-07-11 Arc Second, Inc. Portable computer aided design apparatus and method
US7234131B1 (en) * 2001-02-21 2007-06-19 Raytheon Company Peer review evaluation tool
WO2002088944A1 (en) * 2001-05-01 2002-11-07 Tonbu, Inc. System and method for interactive collaborative process management and project management
US20030200248A1 (en) * 2001-12-19 2003-10-23 Ge Mortgage Holdings, Llc Methods and apparatus for design of processes and monitoring performance of those processes
US20030195754A1 (en) * 2002-04-10 2003-10-16 Ford John E. Product deviation request tracking system
US7076312B2 (en) * 2002-08-02 2006-07-11 Fisher-Rosemount Systems, Inc. Integrated electronic signatures for approval of process control and safety system software objects
US7676387B2 (en) 2002-10-31 2010-03-09 Computer Sciences Corporation Graphical display of business rules
US7451148B2 (en) * 2002-10-31 2008-11-11 Computer Sciences Corporation Method of modifying a business rule while tracking the modifications
US7689442B2 (en) 2002-10-31 2010-03-30 Computer Science Corporation Method of generating a graphical display of a business rule with a translation
US7240077B1 (en) 2002-12-30 2007-07-03 Amazon.Com, Inc. Web site content change management
US7373594B1 (en) 2003-04-30 2008-05-13 Amazon.Com, Inc. Managing the release of electronic content using a template without version logic
US7237226B2 (en) * 2003-05-09 2007-06-26 Intentional Software Corporation Method and system for storing pending changes to data
US7454744B2 (en) * 2003-07-03 2008-11-18 International Business Machines Corporation Private source code commenting
US7895064B2 (en) 2003-09-02 2011-02-22 Computer Sciences Corporation Graphical input display in an insurance processing system
US8171474B2 (en) * 2004-10-01 2012-05-01 Serguei Mankovski System and method for managing, scheduling, controlling and monitoring execution of jobs by a job scheduler utilizing a publish/subscription interface
US7748033B2 (en) * 2005-02-25 2010-06-29 Microsoft Corporation Windows remote debugger service
US7657871B2 (en) 2005-07-22 2010-02-02 Sbc Knowledge Ventures, L.P. Method and system of managing configuration profiles of a plurality of deployed network elements
US20070266371A1 (en) * 2005-12-30 2007-11-15 Ramakrishnan Suraj Multiple correction requests occurring from a single request
US7873944B2 (en) * 2006-02-22 2011-01-18 International Business Machines Corporation System and method for maintaining and testing a software application
US9047164B2 (en) * 2006-09-12 2015-06-02 Opshub, Inc. Calculating defect density by file and source module
US7908601B2 (en) * 2006-11-01 2011-03-15 International Business Machines Corporation Computer method and apparatus for merging software configurations when a change set spans multiple artifacts
US20080216056A1 (en) * 2007-03-01 2008-09-04 Stephen Bate Fully integrated software change request system which includes but not limited to the following modules: change request, migration request, work flow engine project, collaboration, code movement, document tracking, code execution, status notification and database schema snapshot as well as various reporting capabilities.
US10402757B1 (en) * 2007-03-16 2019-09-03 Devfactory Fz-Llc System and method for outsourcing projects
US8196100B2 (en) * 2007-04-06 2012-06-05 International Business Machines Corporation Content management system for computer software with dynamic traceability between code and design documents
US8010389B2 (en) 2007-06-04 2011-08-30 Computer Sciences Corporation Multiple policy claims processing
US8000986B2 (en) * 2007-06-04 2011-08-16 Computer Sciences Corporation Claims processing hierarchy for designee
US8010391B2 (en) * 2007-06-29 2011-08-30 Computer Sciences Corporation Claims processing hierarchy for insured
US8010390B2 (en) 2007-06-04 2011-08-30 Computer Sciences Corporation Claims processing of information requirements
US20090037883A1 (en) * 2007-08-01 2009-02-05 International Business Machines Corporation Testing framework to highlight functionality component changes
US20090187431A1 (en) 2008-01-18 2009-07-23 Frank Scalet Adjusting general damages values using equalization values
US20090192884A1 (en) * 2008-01-28 2009-07-30 Ren-Yi Lo Method and system for incentive-based knowledge-integrated collaborative change management
US7840597B2 (en) * 2008-01-31 2010-11-23 Intuit Inc. Method and apparatus for managing metadata associated with entities in a computing system
US8341600B2 (en) * 2008-02-15 2012-12-25 Microsoft Corporation Tagging and logical grouping of items in source code change lists
US8776020B2 (en) * 2008-12-11 2014-07-08 Sap Ag Software configuration control wherein containers are associated with physical storage of software application versions in a software production landscape
US20100153919A1 (en) * 2008-12-11 2010-06-17 Wolfram Kramer Systems and methods for tracking software stands in a software production landscape
US8266477B2 (en) * 2009-01-09 2012-09-11 Ca, Inc. System and method for modifying execution of scripts for a job scheduler using deontic logic
US9116778B2 (en) * 2010-04-29 2015-08-25 Microsoft Technology Licensing, Llc Remotable project
US9311056B2 (en) * 2010-08-06 2016-04-12 International Business Machines Corporation Automated analysis of code developer's profile
US9430359B1 (en) 2013-11-06 2016-08-30 Amazon Technologies, Inc. Identifying and resolving software issues
US10089213B1 (en) * 2013-11-06 2018-10-02 Amazon Technologies, Inc. Identifying and resolving software issues
US9430748B1 (en) * 2016-01-29 2016-08-30 International Business Machines Corporation Verifying historical artifacts in disparate source control systems
US9747098B2 (en) 2016-01-29 2017-08-29 International Business Machines Corporation Verifying source code in disparate source control systems
JP6960216B2 (ja) * 2016-10-12 2021-11-05 株式会社日立製作所 計算機システム及びプログラムのリリース管理方法
US10671519B2 (en) * 2018-04-27 2020-06-02 Microsoft Technology Licensing, Llc Unit testing for changes to version control
US11048500B2 (en) 2019-07-10 2021-06-29 International Business Machines Corporation User competency based change control
US11797430B2 (en) 2021-12-03 2023-10-24 T-Mobile Usa, Inc. Configuration-driven data conversion and hosting for software development systems and methods

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP0541875A1 (de) * 1991-11-15 1993-05-19 International Business Machines Corporation Verfahren zur Erleichterung der Konfiguration von Programmen

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5752246A (en) * 1995-06-07 1998-05-12 International Business Machines Corporation Service agent for fulfilling requests of a web browser
US5745754A (en) * 1995-06-07 1998-04-28 International Business Machines Corporation Sub-agent for fulfilling requests of a web browser using an intelligent agent and providing a report

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP0541875A1 (de) * 1991-11-15 1993-05-19 International Business Machines Corporation Verfahren zur Erleichterung der Konfiguration von Programmen

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
GARLAND J K ET AL: "IMPROVED CHANGE TRACKING FOR SOFTWARE MAINTENANCE", 15 October 1991, PROCEEDINGS OF THE CONFERENCE ON SOFTWARE MAINTENANCE, SORRENTO, OCT. 15 - 17, 1991, NR. -, PAGE(S) 32 - 41, INSTITUTE OF ELECTRICAL AND ELECTRONICS ENGINEERS, XP000315010 *
REUTER J ET AL: "Distributed revision control via the World-Wide Web", SOFTWARE CONFIGURATION MANAGEMENT. ICSE'96 SCM-6 WORKSHOP. SELECTED PAPERS, SOFTWARE CONFIGURATION MANAGEMENT. ICSE'96 SCM-6 WORKSHOP, BERLIN, GERMANY, 25-26 MARCH 1996, ISBN 3-540-61964-X, 1996, BERLIN, GERMANY, SPRINGER-VERLAG, GERMANY, PAGE(S) 166 - 174, XP000617828 *

Cited By (17)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
GB2339311A (en) * 1998-04-01 2000-01-19 Multex Systems Inc Storage and retrieval of documents using markup languages
US6912529B1 (en) 1998-04-01 2005-06-28 Multex Systems, Inc. Method and system for storing and retrieving documents
GB2339311B (en) * 1998-04-01 2003-06-04 Multex Systems Inc Method and system for storing and retrieving documents
WO2000051018A2 (en) * 1999-02-23 2000-08-31 Planet-Intra.Com Java editor
WO2000051018A3 (en) * 1999-02-23 2000-12-14 Planet Intra Com Java editor
EP1342170A1 (de) * 1999-11-29 2003-09-10 Interwoven Inc. Verfahren und gerät, um daten zwischen datenzielen für webseitenentwicklung und -wartung zu bewegen
EP1342170A4 (de) * 1999-11-29 2006-01-25 Interwoven Inc Verfahren und gerät, um daten zwischen datenzielen für webseitenentwicklung und -wartung zu bewegen
US7103885B2 (en) 2000-07-14 2006-09-05 Sun Microsystems, Inc. Comment driven processing
EP1195675A1 (de) * 2000-07-14 2002-04-10 Sun Microsystems, Inc. Kommentargesteuerte Verarbeitung
EP1288805A1 (de) * 2001-08-24 2003-03-05 Accenture Global Services GmbH Ecommerce Benchmarking
EP1296232A3 (de) * 2001-09-24 2003-08-06 Siemens Energy & Automation, Inc. Vorrichtung und Verfahren zum Programmieren von programmierbaren Steuerungen und zum Generieren von Konfigurationsdaten aus einem zentralen Server
EP1296232A2 (de) * 2001-09-24 2003-03-26 Siemens Energy & Automation, Inc. Vorrichtung und Verfahren zum Programmieren von programmierbaren Steuerungen und zum Generieren von Konfigurationsdaten aus einem zentralen Server
EP1688835A1 (de) * 2005-02-03 2006-08-09 Sap Ag Verfahren und Computersystem zur Steuerung eines Softwareaktualisierungsprozess in einer Softwaresystemumgebung
CN100414499C (zh) * 2005-02-03 2008-08-27 Sap股份公司 在软件系统环境中控制软件维护处理的方法和计算机系统
US8051407B2 (en) 2005-02-03 2011-11-01 Sap Ag Method for controlling a software maintenance process in a software system landscape and computer system
EP1881447A1 (de) * 2006-07-21 2008-01-23 Microsoft Corporation Verwaltung von Softwareversionen
WO2009154928A1 (en) * 2008-06-18 2009-12-23 The Boeing Company Supplier build status visibility tool

Also Published As

Publication number Publication date
US5907705A (en) 1999-05-25
JPH10222351A (ja) 1998-08-21

Similar Documents

Publication Publication Date Title
US5907705A (en) Computer implemented request to integrate (RTI) system for managing change control in software release stream
US7640165B2 (en) Web based methods and systems for managing compliance assurance information
Power et al. Building Web-based decision support systems
US6704015B1 (en) Methods and apparatus for providing a quality control management system
US6772098B1 (en) Systems and methods for managing inspections
US6964044B1 (en) System and process for management of changes and modifications in a process
US20030126001A1 (en) Process for managing requests for work within an organization through a centralized workflow management system
US6591258B1 (en) Method of incorporating knowledge into a knowledge base system
US20040186758A1 (en) System for bringing a business process into compliance with statutory regulations
JP2006506743A (ja) エンタープライズ・アーキテクチャを生成し管理するための方法、システム、および記録媒体
Johnson et al. Improving software quality through computer supported collaborative review
US20030172082A1 (en) Method and system for accessing action item information
US7590606B1 (en) Multi-user investigation organizer
US7120632B2 (en) Methods and systems for managing business information on a web site
US20030212518A1 (en) System and method for quality performance evaluation and reporting
US20100049723A1 (en) Spreadsheet risk reconnaissance network for automatically detecting risk conditions in spreadsheet documents within an organization using principles of objective-relative risk analysis
US20020198725A1 (en) Method and system for managing a relationship with a venture company
Nasution et al. The Web-Based Inventory Data Processing Information System At The Regional Development Planning Agency (Bappeda) North Sumatra Province
Paszko et al. Considerations in selecting a laboratory information management system (LIMS)
WO2001059626A1 (en) Comprehensive web site management system and processes therefore
US20020099584A1 (en) System management tool and method
Callahan et al. Web-based issue tracking for large software projects
Barnard et al. Compas: A Development‐Process Support System
Findlay Computers and the internet in sensory quality control
Chee et al. F-metric: a WWW-based framework for intelligent formulation and analysis of metric queries

Legal Events

Date Code Title Description
PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AT BE CH DE DK ES FI FR GB GR IE IT LI LU MC NL PT SE

AX Request for extension of the european patent

Free format text: AL;LT;LV;RO;SI

AKX Designation fees paid
RBV Designated contracting states (corrected)
STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE APPLICATION IS DEEMED TO BE WITHDRAWN

18D Application deemed to be withdrawn

Effective date: 20000502

REG Reference to a national code

Ref country code: DE

Ref legal event code: 8566