KR20060069576A - Software integration tool for configuration management system - Google Patents

Abstract

The software integration tool of the configuration management system according to the spirit of the present invention detects a change in the internal software and SCM for notifying the developer of the change, the change occurred in the developer when source code obtained from an external developer is changed It includes a SIT that informs the developer that the software will be referenced for development.

In the case of using the system to which the present invention is applied, the external manager automatically delivers the external change contents to the developer in charge by the system even if the integrated manager does not directly manage the change of the external source code, thereby reducing the time and effort required for software integration. More importantly, automated tools are forced to track external shape changes in the internal SCM, thus improving the quality of the software.

Software configuration management, software integration

Description

Software Integration Tool for Configuration Management System

1 is a diagram representing an SCM process according to the spirit of the present invention.

2 is a view showing the operation of the SIT according to the spirit of the present invention.

3 is a view showing the operation of the SCM and SIT in accordance with the spirit of the present invention.

4 is a flow chart representing a method of implementing a software integration tool of a configuration management system according to the spirit of the present invention.

<Explanation of symbols for the main parts of the drawings>

200: SIT 201: Geometry Change Tracker

202: integrator 240: SCM

241: Activity List 250: Internal Organization Integration Stream

260: Nth baseline 270: N + 1st baseline

The present invention complements the conventional Software Configuration Management System (SCM), and is a sub-system of the SCM for managing software development processes involving a large number of organizations. It is about.

Conventional SCM defines management in an organization that shares one system, but such an SCM cannot be used between organizations that cannot share a system such as different developers. The present invention defines the principle and implementation method of the software integration tool as a subsystem that can complement the conventional SCM to complement this disadvantage.

Traditional SCM focuses on managing changes that occur within an organization. However, as changes in the software development environment change more rapidly than in the past, software changes frequently occur outside the organization. In other words, if the source code obtained from other developers is changed, it is not practical to share the same SCM between the company and the company, and thus changes made by other developers cannot be managed by the SCM.

For example, suppose that Company A develops with source code from Company B. When Company B distributes a higher version of the software, the developers of Company A will not be able to Whether or not there is a conflict with the changes that occurred has to be determined without the assistance of the SCM. In large projects this can be very time consuming, allowing developers to focus on applying external changes internally, rather than focusing on developing enhanced features, and also failing to track geometry changes from outside. This may cause deterioration of the quality.

The present invention is a software integration tool (Software Integration Tool, which can provide a support function for developers to search and document the shape change in the external organization that can not be managed by the SCM, and integrate it with the shape change occurred in the internal organization It aims to propose the following SIT).

The software integration tool of the configuration management system according to the spirit of the present invention detects a change in the internal software and SCM for notifying the developer of the change, the change occurred in the developer when source code obtained from an external developer is changed It includes a SIT that informs the developer that the software will be referenced for development.

In the case of using the system to which the present invention is applied, the external manager automatically delivers the external change contents to the developer in charge by the system even if the integrated manager does not directly manage the change of the external source code, thereby reducing the time and effort required for software integration. More importantly, automated tools are forced to track external shape changes in the internal SCM, thus improving the quality of the software.

On the other hand, Software Configuration Management System is a management tool that defines and supports models of Software Configuration Management Standard Procedures and Software Configuration Management plans (SCMP). Say.

In other words, it manages the shape of various outputs such as source code, setting, management document, authentication, etc. generated in the software development process, and controls and manages the changes made to the software.

This is an important element of software quality assurance, which aims to supervise and control changes to minimize confusion in development process and to improve maintenance and productivity.

Commercially available SCM systems include Microsoft's Visual Source Safe and IBM's Rational ClearCase. These systems have the ability for developers to share source code, record, manage, and document changes. In particular, Rational ClearCase supports Unified Change Management (UCM), which allows multiple development teams from one project to work on their own development streams.

Hereinafter, exemplary embodiments of the present invention will be described in detail with reference to the accompanying drawings. The present invention is not limited to the embodiments presented below, and the same scope of the invention will be presented by the addition, limitation, deletion, addition, etc. of components within the scope obvious to those skilled in the art. Could be.

1 is a diagram representing an SCM process according to the spirit of the present invention.

As shown in FIG. 1, the SCM process 100 includes a configuration identification process 110, a configuration control process 120, a configuration auditing process 130, and a shape. Configuration Status Accounting (140).

The shape identification process 110 determines which items are to be controlled. The items include a project plan document, a requirements specification, a design specification, a source code, test data, and the like.

The shape control process 120 is a control on changes occurring over the life cycle of the software. When a change occurs, the change control 121 and the change are authenticated based on the next development cycle through a formal procedure. It consists of a version control 122 to track the contents of.

The shape audit process 130 refers to a quality control activity for evaluating a shape object including characteristics not considered in the shape control process.

The shape state recording process 140 is a process for improving communication between developers by recording the contents of the change.

By controlling and managing changes occurring in one organization through the above process, it is possible to reduce the confusion that may occur in the development process and to increase the work efficiency.

2 is a view illustrating an operation process of the SIT according to the spirit of the present invention.

As shown in FIG. 2, when the software of an external organization is upgraded from an old version to a new version, the SIT 200 collects the difference information between the versions in the SIT 200 and sends the collected information to a developer. This change is then reflected in the software under development by the internal organization.

In more detail, the shape change tracker 201 of the SIT 200 searches for an older version of the software 210 being developed by an external organization and a new version of the software 211 that upgrades the old version of the software 210. . The shape change tracker 201 compares and determines the searched software of the scene 211 and the old version 210, and finds an improvement in the new version of the software 211 by comparing the software with the old version 210. .

The shape change tracker 201 identifies the differences between the scene 211 and the old version 210 software and communicates the differences to the integrator 202. The integrator 202 is also a component of the SIT 200, which communicates the differences between the new 211 and old 210 software to the developer's activity stream. That is, the integrator 202 analyzes the difference of the source code, finds an activity stream related to the difference, and delivers the difference of the source code to the stream. A developer working on the stream will produce new software in view of the difference. Activity refers to a unit of work in progress on SCM 240 by a particular developer. Each activity in the stream is a unit for tracking a set of shape changes.

To integrate the difference into an already active stream, the developer uses a merging tool. The integration tool refers to an application program that analyzes differences between two files to be integrated and integrates them into a single shape according to a developer's designation.

The shape change tracker 201 stores the old version of the software 210 source code in a source code repository, and when the new version of the source code 211 is obtained from the outside, the new version of the source code. 211 is compared with an older version of the source code 210 to extract a directory structure change list and a list of change files.

The shape change tracker 201 implements an application program for documenting the shape change made from the outside so that the internal SCM 240 can be tracked, and a UI for querying the document.

The integration tool is applied to each individual stream in action. For example, the A and B streams 251 and 252, which are separated from the integrated stream 250 and are being developed, are intended to integrate the differences between the scene 211 and the old version 210 software retrieved through the shape change tracker 201. When used. The A and B streams 251 and 252 are separated from the integrated stream 250 after the Nth baseline 260 and merged back into the integrated stream 250 before the N + 1st baseline 270 is formed.

The baseline is a standard or output representing the shape of the software during the development process, and means a technical control point at which all changes are evaluated, adjusted, and processed. In other words, it refers to a specific point in time that can be used as the basis for development by the actors involved in the development.

3 is a view illustrating an operation process of the SCM and the SIT according to the spirit of the present invention.

Referring to FIG. 3, an SCM 240 focusing on managing changes occurring within an organization and an SIT 200 for searching and documenting shape changes in external tissues that cannot be managed by the SCM 240 are described. To understand the relationship between

More specifically, when the source code obtained from the SCM 240 and the external developer to detect the change of the internal software and notify the developer to change the development of the software by notifying the developer of the change occurred in the developer It is possible to grasp the data movement process between the SIT (200) to be referred to.

The SIT 200 provides a support function for a developer to integrate a shape change occurring in an external organization with a shape change occurring in an internal organization.

The SCM 240 is used in the process of making a new version of the source code by internally improving the conventional source code. In order to develop new source code, each developer develops source code of a field that he or she is responsible for in a separate stream separated from the integrated stream 250.

The list of active streams is stored in the activity list 241 inside the SCM 240, and the list of activity streams stored in the activity list 241 contains an external source code change item retrieved from the SIT 200. It is used during integration with the organization's source code.

In more detail, referring to the operation process of the SCM 240 and the SIT 200, through the shape change tracker 201 retrieves the changed source code from the outside, and the list of the retrieved change source code to the integrator 202 Will be delivered.

The integrator 202 tracks the shape change from the outside identified by the shape change tracker 201 and extracts a list of the source code having the shape change being tracked by the SCM 240 among the changed source codes. It is an application engine that implements the function. At this time, a list of source codes having a shape change in the internal organization is provided in the activity list 241 in the SCM 240.

The list of change source codes provided in the activity list 241 and the change source code list retrieved through the shape change tracker 201 are compared with each other to analyze the correlated source codes.

Through the above process, externally changed source codes A 'and B' associated with active source codes A and B are filtered out. Thereafter, the source codes A and B active in the SCM 240 are integrated with the source codes A 'and B' retrieved by the SIT 200.

In order to perform the integration process, the source codes A and B are checked out from the individual streams in the SCM 240 and integrated with externally changed source codes A 'and B'. The check out refers to the task of assigning a particular file to a particular activity and locking it to prohibit making a shape change for another activity.

After the checkout, the new source code that is integrated is checked back into the individual stream inside the SCM 240. The check-in refers to a task of returning a file whose shape has been changed to a state that can be checked out again by another activity on the stream.

4 is a flowchart illustrating a method of implementing a software integration tool of a configuration management system according to the spirit of the present invention.

Referring to FIG. 4, the software integration tool (SIT) 200 of the present invention integrates the shape change made outside the SCM 240 into the internal SCM 240 through the following steps.

First, a new Nth baseline (Baseline: 260) is distributed in the SCM 240 in the organization (S100). In the organization, the shape change of the source code is made during the Nth baseline 260 (S110).

The software is also changed in the external organization during the period (S120), and after the period elapses, the source code changed from the external organization is obtained in the SIT 200 (S130).

The shape change tracker 201 of the SIT 200 compares the source code obtained from the outside with the source code of the version before changing the source code in the external organization (S140). The source change history extracted by the shape change tracker 201 of the SIT 200 is documented and stored in the SCM 240 inside the organization.

Through the activity list 241 of the SCM 240, it is determined the activity of the individual stream (S150).

The active stream through the above step is notified of the change of the source through the integrator 202 (S160).

In more detail, the integrator 202 may compare the source code managed by the SCM 240 among the change source code list generated by the shape change tracker 201 with a development stream having activity on the corresponding source code. Send a notification to the stream. The stream refers to a unit for tracking a series of related activities. In one stream, one activity occurs at a time.

In step S150, the source code without activity is regarded as a normal shape change and overwrites the previous version with the new version without the notification signal (S170).

That is, the integrator 202 is a shape change is made from the outside, the source code with the shape change in the SCM 240, and sends a notification signal to the stream owning the activity corresponding to the shape change, Implement the function to automatically check out the source code from the stream. At this time, the checkout activity is automatically generated by the integrator 202. The checked out source code and the source code that has been changed externally are integrated on the integrator 202 (S180).

In this step, when the integration of the source code is completed and approved by the developer, a UI (User Interface) is provided to enable check-in. Based on the UI, the new source code is checked in to the individual stream (S190).

The individual streams that are developed through the above steps are integrated into the integration stream 250 (S200), and an N + 1st baseline 270 is generated by an integration manager. The integrated stream refers to a stream that generates a baseline by integrating changes in the activity transmitted from each individual stream.

The shape change made externally through the above process is integrated into the internal SCM 240.

When using the system to which the present invention is applied, the integration manager (Integration Manager) is automatically delivered to the responsible developer by the system, even if you do not directly manage the change of the external source code, so the time required for software integration and The effort is reduced. More importantly, automated tools are forced to track external shape changes in the internal SCM, thus improving the quality of the software.

In particular, the present invention can be applied to a project that processes software purchased from an external organization for its platform.

Claims (11)

SCM for detecting a change in the internal software to notify the developer of the change; If the source code obtained from an external developer is changed, SIT for notifying the developer of the internal organization of the change occurred in the developer to refer to the development of the software; software integration tool of the configuration management system comprising a . The method of claim 1, In the SCM, a software configuration management standard procedure, a model of a software configuration management plan, a process of defining and supporting the software integration tool, characterized in that the process is made. Shape identification to determine items to be controlled, such as project plan documents, requirements specifications, design specifications, source code, and test data; Shape control process for performing control over changes occurring throughout the software life cycle; A shape audit process of evaluating a shape object including characteristics not considered in the shape control process; And And a configuration state recording process for recording the changes to improve communication between development agents. The integrated software tool of the configuration management system comprising the SCM is performed. The method of claim 3, wherein When a change occurs in the shape control process, a change control process for authenticating it based on the next development cycle through a formal procedure; And a SCM in which a version control process for tracking the contents of the change is performed. A shape change tracker for tracking the difference between the new and old version software by tracking an old version of the software developed by an external organization and a new version of the software upgraded from the old version of the software; A software integration tool of the configuration management system comprising: an SIT configured to analyze differences of the software, find an activity stream related to the differences, and deliver the differences of the software to the stream. . The method of claim 5, The shape change tracker stores the old version of the software source code in a source code repository, and when the new version of the source code is obtained from outside, the structure of the directory is compared by comparing the new version of the source code with the old version of the source code. Software integration tool for the configuration management system characterized by extracting a list of changes and a list of changes. The method of claim 5, The shape change tracker implements an application program for documenting the shape change made from the outside to be traceable in the internal SCM, and a UI for viewing the document. The method of claim 5, The integrator tracks the shape change from the outside, and extracts a list of the source code with the shape change in the SCM among the changed source code. The method of claim 8, And the list of source codes with shape changes in the SCM is extracted through a set of changes being tracked by activities in the SCM. The method of claim 5, The integrator made a change externally, tracks the source code with the shape change in the SCM, sends a notification signal to the stream owning the activity corresponding to the shape change, Software integration tool of the configuration management system, characterized in that the function to automatically check-out the source code from the stream. The method of claim 10, The checkout generated by the integrator cannot be canceled, and the software integration tool of the configuration management system, characterized in that the check-in can only be completed after the shape change and integration from the outside through the integration tool.

Images