57 results about "Non-functional requirement" patented technology

A system and method for allocating resources in a cloud environment includes providing an abstraction layer between a cloud environment and one or more data centers by generating a virtual hypervisor as an application programming interface. Responsive to a workload request by the one or more data centers, resources are partitioned and virtual machines are instantiated in the one or more data centers using the virtual hypervisor such that non-functional requirements of the workload are addressed at the abstraction level using the virtual hypervisor.

The present invention discloses a system that automates the creation of architectural design models for information services. Such a system can include a data model written in a formal modeling language, a set of non-functional requirements about the information service, and an information service architecture generation tool. The information service architecture generation tool can be configured to utilize the data model, the set of non-functional requirements, and application patterns to create an architectural design model for the information service. The information service can be implemented in a service-oriented architecture (SOA) environment.

The present invention discloses a system that provides automated guidance for making architectural decisions when designing information services in a service-oriented architecture (SOA). Such a system can include a requirements manager, a reusable asset repository, and an asset advisory tool. The requirements manager can be configured to capture non-functional requirements for information services. The reusable asset repository can be configured to store design assets. The design assets can be stored according to a unique data model that associates each design asset with a non-functional requirement. The asset advisory tool can be configured to determine a list of recommended design assets for a user-selected non-functional requirement and document the architectural decision made from the list of recommended design assets.

A method for modeling requirements of a product includes defining an abstract use case for each feature of said product; hierarchically decomposing each abstract use case until concrete use cases are specified for each feature; depicting every actor who would use said product as communicating with a concrete use case through a boundary; and programmatically extracting requirements from said use case diagram. Programmatically extracting requirements further includes converting use case diagrams into directed acyclic graphs, wherein each use case corresponds to a node of a graph, and each relationship between a pair of use cases is represented by a directed edge between the corresponding pair of nodes in said graph, wherein a directed edge points from a parent node to a child node, converting said directed acyclic graph into a tree, and searching said tree to extract said requirements.

A system and method for allocating resources in a cloud environment (100) includes providing an abstraction layer (130) between a cloud environment and one or more data centers (120, 121, 122) by generating a virtual hypervisor (132) as an application programming interface Responsive to a workload request by the one or more data centers, resources are partitioned and virtual machines (144) are instantiated in the one or more data centers using the virtual hypervisor such that non- functional requirements of the workload are addressed at the abstraction level using the virtual hypervisor.

A method for automating the deployment and lifecycle management of an integration solution by using a deployment solution template to gather deployment information, where the integration solution combines components developed separately or on different platforms. The deployment information gathered includes the computing environment topology into which the integration solution is being deployed, as well as the resource requirements and non-functional requirements of the integration solution and its components. The method provides computer implemented models for analyzing the gathered deployment information, and identifying and optimizing deployment options. Choices for selection among identified and optimized options based on non-functional requirements of the integration solution may be displayed to a user of the deployment method. The deployment template may be customized to modify the information being gathered in view of the analysis provided by the models, and in order to use the template and models in subsequent deployments and for the management of the integration solution.

A system for automatically creating a desired software application design. In response to an input to create a desired software application design, functional requirements for the desired software application design are retrieved. Then, non-functional requirements associated with each retrieved functional requirement are retrieved. In addition, software models associated with the retrieved functional requirements are retrieved. Further, software patterns associated with the retrieved non-functional requirements are retrieved. Then, the retrieved software models are transformed into software code for the desired software application design. Also, the retrieved software patterns are applied to associated code sequences in the software code to automatically create an architecture for the desired software application design. Finally, the architecture for the desired software application design is outputted for use by a user. The decisions made during the software application design process are also captured for analysis for future improvement of the desired software application design.

A method for modeling requirements of a product includes defining an abstract use case for each feature of said product, hierarchically decomposing each abstract use case until concrete use cases are specified for each feature, depicting every actor who would use the product as communicating with a concrete use case through a boundary, and programmatically extracting requirements from the use case diagram. Programmatically extracting requirements further includes converting use case diagrams into directed acyclic graphs, where each use case corresponds to a node of a graph and each relationship between a pair of use cases is represented by a directed edge between the corresponding pair of nodes in the graph where a directed edge points from a parent node to a child node, converting the directed acyclic graph into a tree, and searching the tree to extract the requirements.

Automatic deployment of an information technology (TT) system instance having hardware and software components. An application model of the software components is generated based on use cases and is associated with functional and non-functional requirements. An infrastructure model of the hardware components is generated based on the application model. The same software component modeling language represents both the application and infrastructure models. A markup language computer file is generated to include a design of the IT system instance and instructions for accessing library-stored assets that specify the hardware and software components. The computer file is exported to a deployment tool for automatic deployment of the IT system instance based on carrying out the instructions. In one embodiment, the impact of a proposed change is identified and managed in real time prior to a deployment of the proposed change.

A method for improving execution efficiency of a software package customization is disclosed. The method includes identifying one or more components from a configuration table to implement at least one of a use case flow or a non functional requirement (NFR) or an interface document or combinations thereof derived using an use case of the software project, sequencing the identified one or more components to prioritize execution of the use case of the software project and attributing complexity of the identified one or more components to determine the effort estimation for execution of the use case, wherein the attributing complexity includes using an unit effort table for determining the effort estimation requirement for execution of each component of the use case. The method further includes identifying a usage type, attributing the reuse level and resolving the dependencies among the identified components. The usage type of the identified component is selected from the group consists of build afresh, customization, an out of box (OOB) or duplicate. The effort estimation required for customization or OOB of the identified components is percentage indicative of the effort estimation required for build a fresh type. The reuse level of the identified component is determined based on the availability the components in past use cases. The method also includes identifying the additional activities required for developing the identified components or the use case or the software project. In another embodiment of the present invention, a method to perform the gap analysis post requirements gathering of a software project to act as a precursor for a detailed design of the software project is disclosed. In yet another embodiment of the present invention, the method of enhancing the efficiency of a project planning of a software project is also disclosed.

Modelling a computer based business process having a number of functional steps, involves providing software candidate models (740) of the business process, each specifying the functional steps (750), an arrangement of software application components (770) for carrying out the functional steps, and a design of computing infrastructure (780), for running the software application components, to meet given non functional requirements, and suitable for automated deployment. For each of the candidate models, operation of the business process is simulated (730) according to the respective candidate model and their simulated operation is evaluated against the non-functional requirements. The simulation can help the search for a suitable or optimum deployment to be more efficient and can lead to more efficient usage of shared resources.

A method and appertaining system provide that an integrated Service Oriented Architecture (SOA) repository stores functional and non-functional requirements and associated data and results of associated with software services across the software lifecycle, thereby permitting access at a common point or in a common way by a user to all relevant information about the software service at least during the development, testing, and run-time stages of the software service. Thus, all design documents, testing requirements and results, and run-time policies and contracts can be provided in a common location to facilitate development in the service oriented architecture.

The invention relates to a method of designing a system. The system includes an application having software components and an architecture having hardware components on which the application is run. The system has to satisfy at least one functional and one non-functional requirement. The functional analysis step (11) obtains a breakdown of the functional need relating to the application. A step defines the architecture (12). A step for designs hardware components (13) according to the architecture. A step design software components (14) based on the breakdown of the functional need. A step for integrates the software components in the hardware components (15). A step validates the functional requirements of the system (16). A step validates the non-functional requirement of the system (17). An upstream step (21) validates the non-functional requirement of the system, preceding the steps for designing hardware components (13) and software components (14).

A modelling system to provide a computer based business process for an enterprise, allows the enterprise to input values for a plurality of non functional requirements (760) for the deployment, and allows at least some of the values to be varied independently of others of the values, and creates a design of software application components (770) and a design of computing infrastructure (780), for running the software application components, so that the business process operates according to the values input for the non functional requirements of the business process. By modelling the underlying computing infrastructure, it becomes feasible to create models with greater certainty that they will deploy successfully, and with greater predictability of how well they will meet given non functional requirements. This enables more freedom to be allowed to vary the values of these non functional requirements and get greater customisation to suit the needs of the enterprise.

The present invention discloses a system that provides automated guidance for making architectural decisions when designing information services in a service-oriented architecture (SOA). Such a system can include a requirements manager, a reusable asset repository, and an asset advisory tool. The requirements manager can be configured to capture non-functional requirements for information services. The reusable asset repository can be configured to store design assets. The design assets can be stored according to a unique data model that associates each design asset with a non-functional requirement. The asset advisory tool can be configured to determine a list of recommended design assets for a user-selected non-functional requirement and document the architectural decision made from the list of recommended design assets.