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.

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.

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.

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.

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.

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.

In one or more embodiments of the invention, functional data analysts may use a functional data authoring module to capture functional metadata in a consistent manner. Conflict reports for the business processes may be generated for a subset of the business processes or as an overall report across all business processes. One or more embodiments of the invention may provide early detection of data usage and type conflicts from functional data requirements, automated detection of conflicts from functional data requirements, reports listing detected conflicts, conflicts resolution tracking mechanism, ongoing notification regarding changes in functional data requirements or detected conflicts, and avoidance of conflicting functional requirement in the realization phase, thereby reducing costs and project risks and avoiding project delays.

The present invention relates to a method and apparatus for the analysis, particularly, of computing systems. The invention implements an architecture based analysis. The architecture of the system to be analysed is first of all modelled, using a hierarchical model comprising Connections, Components, and other entities. The modelling requires the steps of obtaining the architecture of the system and populating a database or file with the architecture model. The modelled architecture is then evaluated, probably by running simulations of operation of the architecture and also by visualising the architecture using a number of different visualisations. Following the evaluation, changes may be imposed to the architectural model and to the system in order to meet non-functional requirements.

The invention discloses a cockpit display control system software architecture management platform including a modeling toolset. The modeling toolset includes an application instance architecture definition tool, an AADL / MARTE / SYSML model transformation tool, a non-functional requirement analysis tool, a display and control design pattern customization tool and a code integration tool. The invention provides a software architecture management platform with a friendly man-machine interface and easy to set up and maintain the software framework for the development of the cockpit display system software architecture of the modern large and medium-sized civil aircraft.

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 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.

The invention provides a QoS prediction-based service combination method and a QoS prediction-based service combination device. The method comprises the following steps: acquiring a workflow model meeting the functional requirement and non-functional requirement of a user, and resolving the workflow model to obtain each structural body, wherein the structural body comprises at least one alternative service; obtaining predicted QoS values of the alternative services corresponding to each structural body at a preset execution time, and taking the alternative services with optimal predicted QoS values as executed services of the corresponding structural bodies, wherein the executed service is the alternative service to be selected for execution when the structural body is executed; and at the preset execution time, executing the executed services of each structural body in the workflow model by a service execution engine. The technical scheme of the invention performs service combinationbased on QoS prediction so as to execute the services at future execution times according to predicted service combinations, reduce service combination execution time and improve service combination execution efficiency.

In one or more embodiments of the invention, functional data analysts may use a functional data authoring module to capture functional metadata in a consistent manner. Conflict reports for the business processes may be generated for a subset of the business processes or as an overall report across all business processes. One or more embodiments of the invention may provide early detection of data usage and type conflicts from functional data requirements, automated detection of conflicts from functional data requirements, reports listing detected conflicts, conflicts resolution tracking mechanism, ongoing notification regarding changes in functional data requirements or detected conflicts, and avoidance of conflicting functional requirement in the realization phase, thereby reducing costs and project risks and avoiding project delays.

A goal and scene-based use case-driven requirement elicitation method includes the following steps: (1) goals and scenes are divided into a four-layered structure, which includes a business layer, a service layer, an interaction layer and an internal layer; (2) a user is guided to fill in a table, so that requirements are elicited; (3) the requirements elicited in step 2 are converted into a goal-scene table, which is converted into a use case table; (4) the use case table is converted into a use case diagram, and by means of the use case diagram, an activity diagram, a sequence diagram and a state diagram are generated; (5) the non-functional requirements and the functional requirements are correlated, and the non-functional requirement templates added by the user are converted into a visualized non-functional requirement diagram and a soft goal tree. The goal-scene four-layered structure is designed and realized, so that requirement analyzers can conveniently interact with the user; the requirements elicited from goals and scenes are converted into a use case model; and the conversion from the use case model to a UML (Unified Modeling Language) requirement model is provided.

The invention relates to the field of computers, in particular to a business process management method, apparatus and device. The method comprises the steps that a server obtains a business demand and decomposes the business demand into M functional demands and N non-functional demands, thereby realizing fine granularity division of a business process; the server performs screening in an atomic process library to obtain M alterative atomic process groups; the server performs screening in the M alterative atomic process groups to obtain N target atomic process sets, thereby realizing reuse of the business process and resources; and the server activates atomic processes in the N target atomic process sets obtained by screening, and establishes corresponding atomic process combination instances by adopting the N activated atomic process sets. Finally not only the functional demands but also the non-functional demands are met and the atomic process combination instances are flexibly constructed, so that business demands of users can be better met and the overall efficiency of a system is improved.

Systems and associated methods for capturing and storing asset analysis details are described. Systems and methods provide for building a model of the particular asset requirement for a specific purpose and a model of the range of capabilities that a particular asset can provide. The mapping of these two models allows for the identification of the best asset for a particular solution requirement. An asset match may occur when an asset capability model whose functional and non-functional capabilities subsume the functional and non-functional requirements specified in the asset requirements model.

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.