IP Library Granted Patent US 8,370,792
Granted Patent B2
US 8,370,792 · App. 13/108,321 · Granted Feb 5, 2013

Techniques for instantiating and configuring projects

View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 8,370,792
App. No.
13/108,321
Granted
Feb 5, 2013
Kind
B2
Abstract

Techniques for project management instantiation and configuration are provided. A master project includes policy directives that drive the dynamic instantiation and configuration of resources for a project. The resources are instantiated and configured on demand and when resources are actually requested, in response to the policy directives.

Claims (26)

1. A method implemented and residing in a non-transitory machine-readable medium for execution on a machine, the method comprising:

acquiring, by the machine, a project definition for a project within a first processing environment associated with a first stage of a lifecycle for the project, the lifecycle including multiple other stages and each other stage associated with different processing environments from one another and from the first processing environment, wherein acquiring further includes

recognizing sub project definitions within the project definition, each sub project definition includes configuration information for a subset of the selective resources, wherein recognizing includes identifying at least one sub project definition that is masked or hidden from view and access within the project definition, and

recognizing the project definition as a series of definitions for multiple independent projects that are combined within the project definition to define a meta project representing the project; and

dynamically instantiating and configuring, by the machine, selective resources of the project that are associated with the first stage on demand and when the resources are requested using the project definition.

2. The method of claim 1 , wherein acquiring further includes acquiring the project definition as one or more of the following: a data structure, metadata, a virtual project definition that logically defines the project, and configuration data.

3. The method of claim 2 , wherein acquiring further includes identifying triggers, events, and policies within the virtual project definition that conditionally defines when some of the selective resources are to be instantiated within the first stage.

4. The method of claim 1 , wherein dynamically instantiating further includes configuring at least some resources for access within the first stage, wherein those resources are located in a second stage associated with the project lifecycle.

5. A method implemented and residing in a non-transitory machine-readable medium for execution on a machine, the method comprising:

monitoring, by the machine, a lifecycle for a project via a virtual project definition;

detecting, by the machine, attempted access to a sub portion of the project defined within the virtual project definition, wherein the attempted access is detected within a particular stage of the lifecycle and within a particular processing environment, and each stage of the lifecycle have its own unique processing environment different from the other sages;

dynamically instantiating, by the machine, the sub portion of the project for access within that particular stage;

using, by the machine, policy to initially instantiate selective other portions of the project when the project is first transitioned to an initial stage of the lifecycle; and

hiding, by the machine, a selective different portion of the project from view within the particular stage; and

deploying, by the machine, the sub portion to one or more other independent projects associated with other stages different from the particular stage of the lifecycle.

6. The method of claim 5 , wherein detecting further includes recognizing the attempted access as a condition or event defined within the virtual project definition that is satisfied and that triggers the attempted access.

7. The method of claim 5 , wherein detecting further includes recognizing the sub portion as an independent project having its own different virtual project definition.

8. The method of claim 5 , wherein detecting further includes configuring and instantiating logical and physical resources associated with the sub portion when the attempted access is made.

9. A method implemented and residing in a non-transitory machine-readable medium for execution on a machine, the method comprising:

interpreting, by the machine, a virtual project definition to manage a master project having a plurality of stages associated with a lifecycle of the master project, each stage associated with a different processing environment;

hiding, by the machine, nested virtual project definitions associated with the virtual project definition from viewing by a user when sub projects associated with the nested project definitions are not accessible to the user;

deploying, by the machine, selective resources of the master project based on directives and policies defined in the virtual project definition, deployment is for an initial stage of the lifecycle; and

delaying, by the machine, deployment of other resources until deployment is indicated by the policies.

10. The method of claim 9 further comprising, identifying, by the machine, sub projects defined with the virtual project definition.

11. The method of claim 10 further comprising, assembling, by the machine, sub resources for the sub projects for deployment within a particular stage when indicated by the policies.

12. The method of claim 10 further comprising, deploying, by the machine, each of the sub projects to a variety of different stages for the lifecycle and re-assembling the sub projects as the master project within a particular stage.

Assignments (7)
RELEASE OF SECURITY INTEREST REEL/FRAME 035656/0251 Recorded Feb 2, 2023
From: JPMORGAN CHASE BANK, N.A.
To: BORLAND SOFTWARE CORPORATION; ATTACHMATE CORPORATION; NETIQ CORPORATION; MICRO FOCUS (US), INC.; MICRO FOCUS SOFTWARE INC. (F/K/A NOVELL, INC.)
Reel/Frame 062623/0009 →
RELEASE OF SECURITY INTEREST REEL/FRAME 044183/0718 Recorded Feb 2, 2023
From: JPMORGAN CHASE BANK, N.A.
To: MICRO FOCUS LLC (F/K/A ENTIT SOFTWARE LLC); BORLAND SOFTWARE CORPORATION; MICRO FOCUS (US), INC.; SERENA SOFTWARE, INC; ATTACHMATE CORPORATION; MICRO FOCUS SOFTWARE INC. (F/K/A NOVELL, INC.); NETIQ CORPORATION
Reel/Frame 062746/0399 →
CORRECTIVE ASSIGNMENT TO CORRECT THE TO CORRECT TYPO IN APPLICATION NUMBER 10708121 WHICH SHOULD BE 10708021 PREVIOUSLY RECORDED ON REEL 042388 FRAME 0386. ASSIGNOR(S) HEREBY CONFIRMS THE NOTICE OF SUCCESSION OF AGENCY. Recorded Jul 26, 2018
From: BANK OF AMERICA, N.A., AS PRIOR AGENT
To: JPMORGAN CHASE BANK, N.A., AS SUCCESSOR AGENT
Reel/Frame 048793/0832 →
SECURITY INTEREST Recorded Oct 11, 2017
From: ATTACHMATE CORPORATION; BORLAND SOFTWARE CORPORATION; NETIQ CORPORATION; MICRO FOCUS (US), INC.; MICRO FOCUS SOFTWARE, INC.; ENTIT SOFTWARE LLC; ARCSIGHT, LLC; SERENA SOFTWARE, INC.
To: JPMORGAN CHASE BANK, N.A.
Reel/Frame 044183/0718 →
NOTICE OF SUCCESSION OF AGENCY Recorded May 2, 2017
From: BANK OF AMERICA, N.A., AS PRIOR AGENT
To: JPMORGAN CHASE BANK, N.A., AS SUCCESSOR AGENT
Reel/Frame 042388/0386 →
CHANGE OF NAME Recorded Sep 13, 2016
From: NOVELL, INC.
To: MICRO FOCUS SOFTWARE INC.
Reel/Frame 040020/0703 →
SECURITY INTEREST Recorded May 13, 2015
From: MICRO FOCUS (US), INC.; BORLAND SOFTWARE CORPORATION; ATTACHMATE CORPORATION; NETIQ CORPORATION; NOVELL, INC.
To: BANK OF AMERICA, N.A.
Reel/Frame 035656/0251 →