Abstract: A system and method is described for using a component business model to partition a business into non-overlapping components, and then allocating different components to appropriate organizing strategies, based on attribute values assigned to each component. In the best mode of implementation there are two attributes: whether or not the component differentiates the business within the market place; and whether the component is industry standard or is tailored by the organization. These attributes and their values map the components of the business to a matrix. Based on the combination of attribute values in each cell of the matrix, available organizing strategies are also mapped to the matrix, thereby identifying for each component an appropriate organizing strategy.

Abstract: Security levels are assigned to a shared component. A workflow manager receives a workflow request that corresponds to a plurality of workflow steps. For each workflow step, the workflow manager determines whether the workflow step uses a shared component or an unshared component for execution. If the workflow step uses a shared component, the workflow manager invokes the step, and stores the step and its corresponding security level in a security tracking table. When the workflow manager encounters a shared component, the workflow manager uses the security tracking table entries in order to determine a security level to assign the shared component. The workflow manager assigns the determined security level to the shared component, and invokes the shared component to execute the corresponding process step.

Abstract: Maintaining functionality during component failures is presented. During application registration, a recovery engine generates a recovery plan for the application. The recovery plan includes recovery actions that correspond to each component that the application intends to access. When an application encounters an unavailable component, the recovery engine provides a recovery action to the application which instructs the application how to proceed, such as accessing a backup component. The recovery engine tracks unavailable components and, when a subsequent application registers that intends to use an unavailable component, the recovery engine provides the subsequent application a recovery action, instructing the subsequent application how to proceed.

Abstract: The method and system uses the component business model as a framework for locating business activities. Business value drivers are identified, related in an influence model, and structured into a prioritized driver tree. The driver tree is used to determine the relative contributions of leaf drivers to the overall value of the business. Business activities contributing to the leaf drivers are then identified, and the relative contributions of the leaf drivers are allocated to the business activities and then rolled up to the components for display as a heat map overlay on a component map.

Abstract: A method and system are described for using the structure and relationships between components in a component business model of an enterprise to assign components providing monitoring data to a management component. In response to the monitoring data, the management component executes a business rule invoking a service that alters a behavior of the enterprise. The management component contains data rules limiting the information provided by the assigned components, analysis rules defining the interaction between components, and report rules for consolidating recommendations for altering behavior of the enterprise, including decisions to invest in certain aspects of the business, to reengineer certain processes of the business, and to alter operation of certain aspects of the business.

Abstract: Security levels are assigned to a shared component. A workflow manager receives a workflow request that corresponds to a plurality of workflow steps. For each workflow step, the workflow manager determines whether the workflow step uses a shared component or an unshared component for execution. If the workflow step uses a shared component, the workflow manager invokes the step, and stores the step and its corresponding security level in a security tracking table. When the workflow manager encounters a shared component, the workflow manager uses the security tracking table entries in order to determine a security level to assign the shared component. The workflow manager assigns the determined security level to the shared component, and invokes the shared component to execute the corresponding process step.

Abstract: A system and method are described for using a Component Business Model (CBM) to transform a business. A CBM map is used to identify components that collaborate to provide a specified capability, and a repository supporting the CBM map is filtered to provide a view of the identified components that highlights how they collaborate. The view is used to identify component features contributing to the specified capability. The specified capability is then enhanced by a transformation strategy that includes re-engineering particular components, identifying a pattern characterizing the collaboration between components and adding a component to perform the collaborative pattern, and/or adding an additional feature to the collaboration and adding component to perform the additional feature. The CBM repository provides exemplar best practices that can be adapted for use in a re-engineered component.

Abstract: Assigning security levels to a shared component is presented. A workflow manager receives a workflow request that corresponds to a plurality of workflow steps. For each workflow step, the workflow manager determines whether the workflow step uses a shared component or an unshared component for execution. If the workflow step uses a shared component, the workflow manager invokes the step, and stores the step and its corresponding security level in a security tracking table. When the workflow manager encounters a shared component, the workflow manager uses the security tracking table entries in order to determine a security level to assign the shared component. The workflow manager assigns the determined security level to the shared component, and invokes the shared component to execute the corresponding process step.

Abstract: Candidate services are identified using goal-service modeling or other techniques. A candidate service is tested using a business alignment test, a composability test, an externalized service description test, and a redundancy test. When all tests are successfully passed, the candidate service is exposed for use in a client solution, such as implementation as a service-oriented architecture.

Abstract: The invention provides a method for designing an architecture for e-business solutions. A business description of the e-business solution is developed. The business description describes each actor and each business function in the e-business solution. The business description further describes each interaction among one or more actors and one or more business functions. A pictorial representation of the business description is developed. Business pattern(s), integration pattern(s), composite pattern(s), and application pattern(s) that are identifiable within the pictorial representation are established. Each business pattern is indicative of each grouping of one or more actors and one or more business functions based on a nature of the interaction among the one or more actors and the one or more business functions. Each integration pattern is indicative of an integration of two or more business patterns.

Abstract: A system and method for maintaining functionality during component failures is presented. During application registration, a recovery engine generates a recovery plan for the application. The recovery plan includes recovery actions that correspond to each component that the application intends to access. When an application encounters an unavailable component, the recovery engine provides a recovery action to the application which instructs the application how to proceed, such as accessing a backup component. The recovery engine tracks unavailable components and, when a subsequent application registers that intends to use an unavailable component, the recovery engine provides the subsequent application a recovery action, instructing the subsequent application how to proceed.

Abstract: Software services for a business are identified. The goals for the business to meet its objectives are identified. Sub-goals are then identified recursively until services can be identified for fulfilling each of the sub-goals. Performance indicators are identified for each of the sub-goals. Each indicator has a metric identifying the type of measurements that need to be collected to assess the state of the corresponding indicator. Services and indicators are entered in a services portfolio database. A services solution for the business is then implemented using a services oriented architecture using the services in the portfolio.

Abstract: The invention provides a method for designing an architecture for e-business solutions. A business description of the e-business solution is developed. The business description describes each actor and each business function in the e-business solution. The business description further describes each interaction among one or more actors and one or more business functions. A pictorial representation of the business description is developed. Business pattern(s), integration pattern(s), composite pattern(s), and application pattern(s) that are identifiable within the pictorial representation are established. Each business pattern is indicative of each grouping of one or more actors and one or more business functions based on a nature of the interaction among the one or more actors and the one or more business functions. Each integration pattern is indicative of an integration of two or more business patterns.