Browse Prior Art Database

Method and system to traverse/obtain/present massive version evolution data for element/resource in SCM system

IP.com Disclosure Number: IPCOM000198636D
Publication Date: 2010-Aug-11

Publishing Venue

The IP.com Prior Art Database

Abstract

As we know, the SCM (Software Configuration Management) system has provided process/functionality/data storage to support the parallel software development. But there are some problems and insufficiency when the software product grows bigger and bigger after several years’ development/release/maintenance works. Some problem has been exposed in SCM system when it is trying to handle the massive version-controlled data, such as some elements contain mass of versions on mass of different branches with mass of contributing relationships to organize the entire evolution progresses and results in parallel software product development/release. In this situation, obtaining and presenting the element’s versions information will be much complicated and jumbled, so caused the worse HCI(Human Computer Interaction) user experience: complicated relationship and growing relationship makes user to be insane. On the other hand, it will cause the low efficiency and bad performance: lots of redundant data obtained/transmitted/presented consumes extra CPU/memory/network bandwidth consumption. The new solution to those problem is providing an optimized method to traverse or obtain the required data from the entire bunch of versions/branches/relationships for element. Using this way, it can provide a new method to help SCM system deal with massive version data. Provide better usability and consumability to end user who using version tree presenting. Provide less work load to SCM server when loading/searching among massive version data.

This text was extracted from a PDF file.
At least one non-text object (such as an image or picture) has been suppressed.
This is the abbreviated version, containing approximately 23% of the total text.

Page 1 of 19

Method and system to traverse /

The background:

Currently, there're 4 different models adopted for software application/product development and release. From the perspective of SCM(Software Configuration Management) adoption complexity, these are:

1). single developer works for one release;

2). multiple developers work for one release: they share the same code in single thread;
3). multiple developers work for one release on their own workspace/thread for code development, and do merge work timely;
4). Multiple developers work for several releases for one product with reusable asset from former releases; the different releases development production would deliver to each others release content; this is the most complicated scenario for software parallel development and release.

The issue we met in current software and configuration management (SCM) system:

As we know, the SCM (Software Configuration Management) system has provided process/functionality/data storage to support the parallel software development. But there are some problems and insufficiency when the software product grows bigger and bigger after several years' development/release/maintenance works. Some problem has been exposed in SCM system when it is trying to handle the massive version-controlled data.

Problem: Some elements contain mass of versions on mass ofdifferent branches with mass of contributing relationships to organize the entire evolution progresses and results in parallel software product development/release. In this situation, obtaining and presenting the element's versions information will be much complicated and jumbled as shown in FIG.1. This makes some troubles in:
-worse HCI(Human Computer Interaction) user experience: complicated relationship and growing relationship makes user to be insane;
-low efficiency and bad performance: lots of redundant data obtained/transmitted/presented consumes extra CPU/memory/network bandwidth consumption.

1

/obtain

obtain/

/present massive version evolution data for element

present massive version evolution data for element /

/resource in SCM system

resource in SCM system

Page 2 of 19

FIG.

.1

1

2

Page 3 of 19

3

[This page contains 1 picture or other non-text object]

Page 4 of 19

Currently known solution to this problem and drawbacks:

As we know, currently SCM(Software Configuration Management) system can only provide user filter function to help them filtrate some particular version control data of one element resource. The filter function need user to specify some properties and values which contained in version control data, then filtrate the version control data which meet the condition. But this method also have some drawbacks as below:
1.The version control data in SCM system is consisted with many version elements' data and version elements' relationships data. So the filter function can onlydeal with the version elements' data. It can not help on version elements' relationships data processing.
2.The filter fun...