JapaneseEnglish

Contact Us

Configuration Management

Achieving traceability via version management linked with deliverables

SHIFT solves these problems!

  • Version management is insufficient for documents and the customer does not know the reasons for change when source code is reviewed
  • Difficulty in understanding where the changes occurred because requests have been made to multiple development vendors
  • Degradation occurs during maintenance work but the customer cannot identify its cause
SHIFT

Configuration Management

Features
  • Managing history with tickets indicating when, why, and who made changes

    By managing change information with tickets, we provide swift answers to questions such as what changes in edits to the source code will reflect on to the specifications, what the impact scope for bugs will be, and when changes to documentation/source code will be released to the test environment so that testing can start when bugs or specification changes occur.

  • Eliminating the reliance on individual skills for configuration management and constructing a unified management method

    When multiple development vendors participate in a project, integrity cannot be maintained with the entire system if each vendor performs version management separately. SHIFT can propose common configuration management policies, planning, and operation for an entire system. This unifies the configuration management method of the entire system to ensure that management methods do not differ and achieves smooth operation.

  • Improving the speed of identifying causes of failure

    SHIFT performs version management of design documents and source code to swiftly identify the latest specifications and revision history. Even when an unexpected failure occurs during a change, the version of the test environment where the problem occurred, when it occurred, the scope of impact, and the cause can be swiftly investigated.

Three Distinctive Features Shift Provides

01

Proposing configuration management suitable for the project status

Proposing configuration management suitable for the project status

SHIFT has accumulated configuration management knowledge from a large number of actual projects. Rather than proposing a homogeneous configuration management, we use this knowledge to flexibly propose a configuration management method according to the project status of the customer.

02

Linking project management and version management tools

Linking project management and version management tools

We perform configuration management by linking project management tools (such as Redmine and JIRA) with version management tools (such as Git and SVN). This enables smooth tracking of the various phases, from documentation/source code editing to testing, when bugs or specification changes occur.

03

We support configuration management according to the customer’s budget

We support configuration management according to the customer’s budget

SHIFT is able to support partial configuration management. When the customer has a limited budget and cannot afford to perform configuration management for all deliverables, we can support partial configuration management, such as configuration management support for bug management only.

Related service