| Patent application number | Description | Published |
|---|
| 20080300943 | TECHNIQUES FOR PROJECT TRANSFORMATION AND MANAGEMENT - Techniques for project transformation and management are provided. A project is defined via user-defined stages associated with its lifecycle. Each stage is associated with a set of resources and a particular processing environment. Each stage is dynamically and automatically configured and the resources of each stage are dynamically and automatically managed and transitioned to and from other stages. Policy drives the management and transitions of resources between the stages. | 12-04-2008 |
| 20080300945 | TECHNIQUES FOR SHARING RESOURCES ACROSS MULTIPLE INDEPENDENT PROJECT LIFECYCLES - Techniques for sharing resources across multiple independent projects are provided. Resources, which are associated with a first project and which are managed within first stages of a first project lifecycle, are selectively shared and managed within second stages of a second project lifecycle, which is associated with a second project. The first and second project lifecycles are separately and independently managed from one another. | 12-04-2008 |
| 20080319999 | TECHNIQUES FOR PROJECT LIFECYCLE STAGED-BASED ACCESS CONTROL - Techniques for project lifecycle staged-based access control are provided. Access control rights are defined for a stage of a project's lifecycle. As requestors transition to the stage, the access control rights are enforced on top of any existing security restrictions. In an embodiment, selective resources are not visible to requesters within the stage in response to the access control rights. | 12-25-2008 |
| 20090030705 | PROJECT MANAGEMENT BLACK BOX PROTECTIONS - Techniques for project management black box protections are provided. A first principal associated with a first processing environment and a first stage of a project's lifecycle requests that an action be taken on its behalf. The first principal is authenticated and policy is evaluated when the first principal is successfully authenticated. Moreover, the action is taken on behalf of the principal when the policy permits and the when the principal was successfully authenticated. | 01-29-2009 |
| 20090037198 | TECHNIQUES FOR TEMPORARILY HOLDING PROJECT STAGES - Techniques for temporarily holding project stages are provided. Resources and configuration information associated with a source stage of project's lifecycle are imaged in a self-contained project package. The package is published to an intermediate holding area. The package is pulled to and initiated within a target stage of the project's lifecycle when release and access criteria are satisfied. | 02-05-2009 |
| 20090037921 | TECHNIQUES FOR INSTANTIATING AND CONFIGURING PROJECTS - 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. | 02-05-2009 |
| 20090048888 | TECHNIQUES FOR CLAIM STAKING IN A PROJECT STAGE-BASED ENVIRONMENT - Techniques for claim staking in a project stage-based environment are provided. A stakeholder is assigned for a project as a whole or a sub portion of the project. Access permissions are defined in response to the stakeholder, the project, and/or the sub portion. The access permissions are dynamically enforced across processing environments, stages within a same project, and stages within different projects when attempted changes are made to the project or the sub portion. | 02-19-2009 |
| 20090048894 | TECHNIQUES FOR PROPAGATING CHANGES IN PROJECTS - Techniques for propagating changes in projects are provided. A first resource associated with a first project is modified in some manner. The modification is automatically and dynamically detected. A second project is identified for notification of that change. The notification is communicated to the second project in a custom manner. | 02-19-2009 |
| 20090288062 | MECHANISM TO SUPPORT ORPHANED AND PARTIALLY CONFIGURED OBJECTS - Mechanisms to support orphaned and partially configured objects are provided. A project includes a variety of objects. At least one object is designated as an orphaned object. The orphaned object lacks complete configuration details. Other objects of the project depend on the orphaned object and yet the other objects can load and process within the project as if the orphaned object was fully configured and available. | 11-19-2009 |
| 20090288093 | MECHANISM TO BUILD DYNAMIC LOCATIONS TO REDUCE BRITTLENESS IN A TEAM ENVIRONMENT - Mechanisms to build dynamic locations to reduce brittleness in a team environment are provided. A project includes resources, each resource is assigned a key. Each key is mapped to a current location for its corresponding resource. The keys and locations are maintained in an index. Locations for the resources can change as desired throughout the lifecycle of the project and as changes occur the index is updated. When references are made within the project to the resources, the references are translated to the keys, if necessary. The keys are then used for accessing the index and dynamically acquiring the current locations for the resources at the time the references are made. | 11-19-2009 |
| 20090307278 | MECHANISMS TO SUPPORT OBJECT-ORIENTED VERSION CONTROL OPERATIONS - Mechanisms to support object-oriented version control operations are provided. A user manipulates and views a project from an object viewpoint and within an object module. The user performs version control operations using object handles. The object handles are resolved to specific file references and the specific file references are used to process legacy version control commands utilizing a legacy version control system in a manner that is transparent to the user. | 12-10-2009 |
| 20090313281 | MECHANISMS TO PERSIST HIERARCHICAL OBJECT RELATIONS - Mechanisms to persist object relations are provided. A project is defined as a series of interrelated objects having dependencies and relationships with one another. The dependencies and relationships are maintained via a storage organization for files that define the objects within a project storage environment for the project. Thus, the dependencies and relationships are not maintained via hardcoded instructions or references that are included within the files. | 12-17-2009 |
| 20100017434 | MECHANISMS TO SHARE ATTRIBUTES BETWEEN OBJECTS - Mechanisms for sharing attributes between objects are provided. An object includes a special designation for at least one component, which is identified as a shared attribute. Data associated with the shared attribute is populated and managed from a central location within a processing environment. Multiple instances of a same object or of entirely different objects can reference, declare, and use the data from the central location. | 01-21-2010 |
| 20100036869 | MECHANISMS TO SUPPORT FINE-GRAIN NAMESPACING - Mechanisms to support fine-grain namespacing are provided. When an object is to be loaded within a processing environment, a specific namespace for that object is dynamically resolved during the load. That namespace can be dynamically resolved via object inheritance, via specific object-attribute declaration, and/or via consultation with a namespace object. | 02-11-2010 |
| 20100036870 | MECHANISMS TO SUPPORT MULTIPLE NAME SPACE AWARE PROJECTS - Mechanisms to support multiple name space aware projects are provided. Multiple roots of a project declare multiple namespacing mechanisms. Resources of the project can utilize each of the multiple namespacing mechanisms. In some cases, a particular resource of the project can override and use a foreign namespace that is associated with a different project hierarchy even while that particular resource resides within a project hierarchy associated with the original project and even while the project hierarchy does not declare, at the root, the foreign namespace. | 02-11-2010 |
| 20100095268 | MANAGING COMPLEX DEPENDENCIES IN A FILE-BASED TEAM ENVIRONMENT - Techniques managing complex dependencies in a file-based team environment are provided. A software module is represented as an object. The object is defined via a file. The file includes relationships, and some of the relationships define dependencies to other objects. In some cases, attributes for the object are also included in the file and are defined via references to still other objects. The relationships and the attributes are carried with the object via the file. | 04-15-2010 |
| 20110040805 | TECHNIQUES FOR PARALLEL BUSINESS INTELLIGENCE EVALUATION AND MANAGEMENT - Techniques for parallel business intelligence and management are provided. Data is collected from a variety of disparate sources and from a variety of disparate network locations. The data is then filtered and normalized. Next, relationships between elements in the data are established and correlations are created between the elements. The elements are then tagged and integrated with other data of a distributed knowledge store to create customized business intelligence reports and customized data visualizations. | 02-17-2011 |
