Browse Prior Art Database

Change Flagging Delta System

IP.com Disclosure Number: IPCOM000106256D
Original Publication Date: 1993-Oct-01
Included in the Prior Art Database: 2005-Mar-20
Document File: 4 page(s) / 85K

Publishing Venue

IBM

Related People

Conzemius, CP: AUTHOR

Abstract

A process of capturing source code changes to provide a history of the changes is disclosed. Each time a source code part is edited the changes are kept in a change history file. This information allows the developers to view and print changes by edit session, reason, version, or a complete history. Also, this information allows the project management team to obtain Software Metrics by reason for all types of source code.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 52% of the total text.

Change Flagging Delta System

      A process of capturing source code changes to provide a history
of the changes is disclosed.  Each time a source code part is edited
the changes are kept in a change history file.  This information
allows the developers to view and print changes by edit session,
reason, version, or a complete history.  Also, this information
allows the project management team to obtain Software Metrics by
reason for all types of source code.

      The Change Flagging Delta System (CFDS) uses a new technology
wherein each source part has an associated source part known as the
Change History File.  The Change History File contains information
for each and every change to the source part.  This information
allows the developer to view and print all changes to the source part
by edit session, reason, version, or in total.  In addition, the
developer can merge the source back to the way it was before a given
edit session.  And the information in the Change History File
provides the project management team with the Software Metrics
information by reason for all types of source code.

      The Change History File contains the necessary information to
allow the programmers an option to insert change flags into their
source part and to be able to view the placement of the change flags
before committing their changes.

      Changed LOC is available down to the PTR or DCR level of
granularity for much more accurate reporting and training in
estimating skills.

      Using the Change History File technique speeds up the build
process and saves CPU resources because the source part in the
library is ready for compilation and does not need to be recreated as
is required by some delta systems.

      The Change Flagging Delta System (CFDS) via the Change History
File supports "all" source parts and the users "editor-of-choice".

      A programmer can recreate the source part at any level of
granularity down to a specific edit session.

      Programmers may easily view and/or print the changes for a
specific edit session, reason, version, or in total.

Sample Change History File.

  /*--*Edit0003 Change History - PartId PARTX        *--*/
  /*--*$B1= P2389         R091  910408  CLAUDE    :  *--*/
  /*--*New_F  Old_F  ACDMR  Flag  Old/New Data       *--*/
  /*--*00001  00001  00084  @A0A
  /*--*00085  00085  00001  @A1A
  /*--*00086  00086  00024  @A0A
  /*--*00110  00000  00001  @B1D   Fieldm = 'M';
  /*--*00111  00110  00341  @A0A
  /*--*Edit0002 Change History - PartId PARTX        *--*/
  /*--*$A1= P1234         R091  910408  CLAUDE    :  *--*/
  /*--*New_F  Old_F  ACDMR  Flag  Old/New Data       *--*/
  /*--*00001  00001  00084  @A0A
  /*--*00085  00085  00001  @A1A   Fieldb = 'B';
  /*--*00086  00086  00001  @A0A
  /*--*00087  00087  00001  @...