Browse Prior Art Database

System and Method for Maintaining a Versioned Database using External Globally Managed Software Configurations Disclosure Number: IPCOM000228136D
Publication Date: 2013-Jun-08
Document File: 3 page(s) / 306K

Publishing Venue

The Prior Art Database


Disclosed is a system and method to manage a flat application database containing multiple versions of concept resources using an external, globally managed software configuration database.

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

Page 01 of 3

System and Method for Maintaining a Versioned Database using External Globally Managed Software Configurations

Version control systems (VCS) have been invented and reinvented several times throughout the history of computing. All these systems focus on maintaining

configurations of resources - where different versions of the same concept resources are organized into a meaningful, logical manner to depict the various stages in a software's lifecycle. An example of concept resources, related versions, and configurations is shown in Figure 1.

Figure 1: Background - Version Control Systems

Traditional VCS have one major drawback: in order for the systems to work for the end-user, a particular configuration needs to be mapped to separate storage first . For example, in any traditional VCS, the end-user must check-out all the particular versions of resources from a specific branch configuration before the user can modify or query those particular versions of resources.

Figure 2a: Problem 1: Check-out Before Use


Page 02 of 3

Another requirement to the workflow in Software as a Service (SaaS) systems is for multiple application services to share configuration information. For example, a traditional generic VCS allows end-users to store any kind of file in the configurations. A single stream or branch in in a VCS may contain requirement

documents, design blueprints, application source code, test scripts, etc.

On the other hand, SaaS systems are focused around functionality, where each

service provides a specific function and that function only. Currently, all SaaS systems that provide "live" revision control work independently. This poses a problem where users have several configurations across client applications that logically depict the same phase in the development lifecycle. When each of these individual application services provides revision control, there needs to be a way to unify the resources into system-wide logical configurations for the end-user. This eases the use and administration of configurations as a...