Abstract:
Automated service level management of applications can include automated deployment, monitoring, forecasting, and/or predicting based on a plurality of service levels comprising application level, application server platform level, virtual machine level, and/or infrastructure level, and optimizations at multiple levels using a plurality of techniques including automated dynamic application migration. Automated deployment of applications in a cloud computing environment using deployment descriptors comprises receiving values for service level parameters for an application, creating a deployment descriptor based on the parameters, identifying application servers that satisfy the deployment descriptors, and deploying the application to the identified application servers. Automated dynamic migration of applications in a cloud computing environment comprises deciding to migrate an application, obtaining application resource requirements, identifying application server candidates, selecting an application server from one of the candidates, and migrating the application.
Abstract:
A method for developing a process roadmap for a business system is disclosed. The method includes identifying a business process and determining business goals and key process metrics for the business process. The method further includes measuring process maturity levels of the business process and identifying business process improvement initiatives based on the process maturity levels. Furthermore, the method includes linking the business process to at least one of the business goals and key process metrics, the process maturity levels, and the business process improvement initiatives for developing the process roadmap for the business system.
Abstract:
An access system in one embodiment that first determines that someone has correct credentials by using a non-biometric authentication method such as typing in a password, presenting a Smart card containing a cryptographic secret, or having a valid digital signature. Once the credentials are authenticated, then the user must take at least two biometric tests, which can be chosen randomly. In one approach, the biometric tests need only check a template generated from the user who desires access with the stored templates matching the holder of the credentials authenticated by the non-biometric test. Access desirably will be allowed when both biometric tests are passed.
Abstract:
A system and method for generating architecture for a business system is disclosed. The method comprises, in one embodiment, modeling a plurality of viewpoints adapted for describing the architecture of the business system in form of a collection of views and viewpoints and creating a software organization viewpoint adapted for providing architecture guidelines. An exemplary method further comprises creating a first plurality of notations for each of the plurality of viewpoints for describing the plurality of viewpoints and creating a second plurality of notations for capturing design rationale indicative of the first plurality of notations. Furthermore, an exemplary method comprises generating the architecture of the business system using at least one of the plurality of viewpoints or the software organization viewpoint, or at least the second plurality of notations, or combinations thereof.
Abstract:
A system and method for improving modularity of a software source code is provided. The system comprises of a user interface for receiving source code; a source code model extractor for parsing and forming a model of the source code; a source code model database for storing the source code model, refactoring operators, and a record of refactoring changes; a modularity improvement analyzer for reading the source code model and modularity problem diagnosis data and generating a set of prescriptions; an optimal improvement suggestion selector for evaluating and selecting prescriptions; and a refactoring engine for receiving selected prescriptions and applying them on the source code.
Abstract:
A software testing architecture can comprise a three-level framework. The three-level framework can comprise a first level (comprising a first data source), a second level (comprising a second data source), and a third level (comprising a third data source). The framework can further comprise an intermediate entity data source. The first data source can specify test pages, the second test cases for the test pages, and the third test data for the test cases. Each of the three levels can be associated with respective scripts. A method for testing multi-staged scenarios can select test pages and, for the test pages, determine and execute test cases and save intermediate entities. A method for testing multi-staged scenarios using a three-level framework can execute a first test case for a first test page, save an intermediate entity, and execute a second test case for a second test page using the saved intermediate entity.
Abstract:
Tasks for a business process can be decomposed into subtasks represented by messages. Message processing can be throttled in a heterogeneous environment. For example, message processing at subtask nodes can be individually throttled at the node level by controlling the number of instances of subtask processors for the subtask node. An infrastructure built with framework components can be used for a variety of business process tasks, separating business logic from the framework logic. Thus, intelligent scalability across platform types can be provided for large scale business processes with reduced development time and resources.
Abstract:
Software system facts comprising concepts, concept instances and relationships within the software system are identified and stored in a repository. The software system facts are extracted from artifacts comprising the software system or are provided through explicit definition. Architectures of the software system are recovered from the stored software system facts. Layered views of the recovered architectures are generated. The stored software system facts are checked against architectural rules to ensure architectural compliance of the software system. The impact of proposed changes to the software system is assessed by querying the identified software system facts.
Abstract:
A method of storing semantically similar documents on proximally located peers in a structured peer to peer overlay network, where each peer is assigned a unique identifier and each document includes one or more words belonging to at least one hierarchical structured collection of words. A method of searching and retrieving documents, corresponding to a search query, from a structured peer to peer overlay network is also provided.
Abstract:
The financial impact of the implementation of a business framework can be predicted. Shifted business condition metrics associated with business activities for implementing the business framework can be applied to model financial impact for a business entity. Impact on financial condition according to income statement and balance sheet can be modeled based on financial data for the business entity. Impact can be modeled per activity. Activities can be prioritized based on modeled impact.