Computer method and apparatus for managing software configurations using change flow hierarchies

1. Computer apparatus with a storage medium for managing configurations of programming models, comprising:

a user workspace respective to a user, the user workspace holding a programming model configuration specified by the user, the configuration being formed of one or more model elements; and

one or more change-flow hierarchies defining, for each user workspace, flow of changes to the model elements;

wherein the change-flow hierarchies define default source projects and target projects of accept operations issued from the user workspaces;

wherein the change-flow hierarchies define default source projects and target projects of deliver operations;

further comprising an intermediate workspace between the user workspace and a subject project, the user workspace deferring acceptance of the subject project checkpoint by delivering a change-set to the intermediate workspace instead of delivering a configuration to the project;

wherein the change-flow hierarchies employ indications of primary change flow and supplementary change flow; wherein primary change flow is defined such that accept and deliver operations issued from one workspace apply changes to a release or a project within the change-flow hierarchy; and supplementary change flow can be defined to ensure that a workspace sees changes made by other workspaces which its change-flow hierarchy or in another hierarchy.

2. Computer apparatus as claimed in claim 1 wherein the Change-flow hierarchies enable a user workspace to defer accepting a project checkpoint.

3. A computer method for managing configurations of programming models, comprising the steps of:

providing a workspace respective to a user, the workspace holding a programming model configuration specified by the user, the configuration being formed of one or more model elements; and

defining for each user workspace flow of changes to the model elements using one or more change-flow hierarchies;

wherein the change-flow hierarchies define default source projects and target projects of accept operations issued from the user workspaces;

wherein the change-flow hierarchies define default source projects and target projects of deliver operations;

further comprising the step of deferring acceptance of a subject project checkpoint by delivering a change set to an intermediate workspace instead of delivering a configuration to the project;

wherein the change-flow hierarchies employ indications of primary change flow and supplementary change flow; wherein primary change flow is defined such that accept and deliver operations issued from one workspace apply changes to a release or a project within the change-flow hierarchy; and supplementary change flow can be defined to ensure that a workspace sees changes made by other workspaces which its change-flow hierarchy or in another hierarchy.

4. A method as claimed in claim 3 wherein the change-flow hierarchies enable a user workspace to defer accepting a project checkpoint.

5. A method as claimed in claim 3 wherein the intermediate workspace is an integration workspace.

6. A programming model configuration management system comprising:

a processor;

a workspace means for providing respective workspaces per user, each user workspace holding a programming model configuration specified by the respective user, and the configuration being formed of one or more model elements; and

change-flow hierarchy means for defining, for at least each user workspace, flow of changes to model elements;

wherein the change-flow hierarchy means defines default source projects and target projects of accept operations issued from the user workspaces;

wherein the change-flow hierarchy means defines default source projects and target projects of deliver operations;

wherein the change-flow hierarchy means includes hierarchies defining flow of changes for intermediate workspaces and/or sub-projects;

wherein the change-flow hierarchy means provide hierarchies employing indications of primary change flow and supplementary change flow;

wherein the change-flow hierarchies employ indications of primary change flow and supplementary change flow; wherein primary change flow is defined such that accept and deliver operations issued from one workspace apply changes to a release or a project within the change-flow hierarchy; and supplementary change flow can be defined to ensure that a workspace sees changes made by other workspaces which its change-flow hierarchy or in another hierarchy.

7. A programming model configuration management system as claimed in claim 6 wherein the change-flow hierarchy means enables a user workspace to defer accepting a project checkpoint.

8. A computer program product comprising a computer usable storage medium having a computer readable program, wherein the computer readable program when executed in a digital processor causes the processor to:

provide a respective user workspace for different users, the user workspace holding a programming model configuration specified by the user, the configuration being formed of one or more model elements; and

define for each user workspace flow of changes to the model elements using one or more change-flow hierarchies;

wherein the change-flow hierarchy defines default source projects and target projects of accept operations issued from the user workspaces;

wherein the change-flow hierarchy defines default source projects and target projects of deliver operations;

wherein the change-flow hierarchy includes hierarchies defining flow of changes for intermediate workspaces and/or sub-projects;

wherein the change-flow hierarchy provides hierarchies employing indications of primary change flow and supplementary change flow;

wherein the change-flow hierarchies employ indications of primary change flow and supplementary change flow; wherein primary change flow is defined such that accept and deliver operations issued from one workspace apply changes to a release or a project within the change-flow hierarchy; and supplementary change flow can be defined to ensure that a workspace sees changes made by other workspaces which its change-flow hierarchy or in another hierarchy.