Systems and methods for providing metric data for patterns in a modeling environment are disclosed. In some aspects, contexts for generating metric data for a pattern are constructed. The pattern represents one or more computations executable in the modeling environment and associated with operation or behavior of a real-world system. The contexts include information about the pattern. The metric data is associated with one or more objectives with which the use of the pattern is associated. Code for the pattern for each context is generated. Metric data is generated for the pattern and under each context. The metric data of the pattern under each context is associated with the objectives. The metric data and the association are stored for use in providing information about or based on the metric data when the pattern is to be or is used in a model representing the real-world system.

Systems and methods for providing metric data for patterns in a modeling environment are disclosed. In some aspects, contexts for generating metric data for a pattern are constructed. The pattern represents one or more computations executable in the modeling environment and associated with operation or behavior of a real-world system. The contexts include information about the pattern. The metric data is associated with one or more objectives with which the use of the pattern is associated. Code for the pattern for each context is generated. Metric data is generated for the pattern and under each context. The metric data of the pattern under each context is associated with the objectives. The metric data and the association are stored for use in providing information about or based on the metric data when the pattern is to be or is used in a model representing the real-world system.

The present disclosure extracts contextual product feature model from requirement specification documents where the conventional methods fail to perform. Initially, the system receives a plurality of requirement specification documents pertaining to a product, a domain dictionary, a plurality of configuration parameters, and a plurality of extraction patterns. A product feature model is generated using a NLP based feature extraction technique. The product feature model includes a plurality of product feature elements comprising a feature area, a major feature and a plurality of features arranged hierarchically and classified into feature types. Further, a plurality of ContextType associations like core, client, geography and market are extracted for each of the plurality of features using a ContextType extraction technique. Finally, the plurality of ContextType associations is updated in the product feature model to obtain a contextual product feature model. Various types of feature exports can be generated using a natural language interface.

The present disclosure provides a holistic model for feature specification and dependency representation for requirement specification documents where the conventional models fail to provide. The present disclosure receives a plurality of requirement specification documents and a related data. A product feature model is generated based on the plurality of requirement specification documents and the related data using a feature model generation technique. The product feature model includes a plurality of product feature elements. The plurality of product feature elements includes a feature area, a major feature and a plurality of features. A specification model is generated further for each of the plurality of features using a specification extraction technique. Post generating the specification model, a plurality of dependency associations are generated for each of a plurality of specification elements of the specification model using a dependency extraction technique. Finally, the plurality of dependency associations are updated in the specification model.

The present disclosure provides a holistic model for feature specification and dependency representation for requirement specification documents where the conventional models fail to provide. The present disclosure receives a plurality of requirement specification documents and a related data. A product feature model is generated based on the plurality of requirement specification documents and the related data using a feature model generation technique. The product feature model includes a plurality of product feature elements. The plurality of product feature elements includes a feature area, a major feature and a plurality of features. A specification model is generated further for each of the plurality of features using a specification extraction technique. Post generating the specification model, a plurality of dependency associations are generated for each of a plurality of specification elements of the specification model using a dependency extraction technique. Finally, the plurality of dependency associations are updated in the specification model.

A system configuration derivation device 90 includes a storage unit 91 that stores a concretization rule in which a method is specified for concretizing abstract configuration information by confirming an unconfirmed portion of the abstract configuration information, which is information indicating configuration of a system in which the unconfirmed portion is included, and a generation unit 92 that concretizes the abstract configuration information included in configuration requirements of the system using the concretization rule stored to generate system configuration information, which is information indicating the configuration of the system in which the unconfirmed portion is not included, on the basis of the configuration requirements.

A system configuration derivation device 90 includes a storage unit 91 that stores a concretization rule in which a method is specified for concretizing abstract configuration information by confirming an unconfirmed portion of the abstract configuration information, which is information indicating configuration of a system in which the unconfirmed portion is included, and a generation unit 92 that concretizes the abstract configuration information included in configuration requirements of the system using the concretization rule stored to generate system configuration information, which is information indicating the configuration of the system in which the unconfirmed portion is not included, on the basis of the configuration requirements.

Designers create user experience designs using external design systems. An Experience Design Codification and Management System (EDCMS) retrieves a user experience definition based on the user experience design from the external design system, and generates a comprehensive user experience specification from the user experience definition. Part of the comprehensive user experience specification includes JSON, XML, or YAML code created based on the user experience definition. The EDCMS then packages and encodes the comprehensive user experience specification to create a codified user experience from the comprehensive user experience specification. The codified user experience is then versioned and digitally signed, and the versioned and signed codified user experience is stored in a user experience design repository.

Designers create user experience designs using external design systems. An Experience Design Codification and Management System (EDCMS) retrieves a user experience definition based on the user experience design from the external design system, and generates a comprehensive user experience specification from the user experience definition. Part of the comprehensive user experience specification includes JSON, XML, or YAML code created based on the user experience definition. The EDCMS then packages and encodes the comprehensive user experience specification to create a codified user experience from the comprehensive user experience specification. The codified user experience is then versioned and digitally signed, and the versioned and signed codified user experience is stored in a user experience design repository.

Disclosed herein are system, method, and computer program product embodiments for providing an auto-mapping recommendation between a source asset and a target asset in an integration flow design tool. Because the number of fields passed from a source asset to a target asset may be multitudinous, by auto-recommending mappings between fields provided by the source asset to the target asset, an integration flow design tool may save time developers a significant amount of time and optimize the integration flow design process.