Abstract: A request including audio data is received from a voice-enabled device. A string of phonemes present in the utterance is determined through speech recognition. At a later time, a subsequent user input corresponding to the request may be received, in which the user input is associated with one or more text keywords. The subsequent user input may be obtained in response to an active request. Alternatively, feedback may not be actively elicited, but rather collected passively. However it is obtained, the one or more keywords associated with the subsequent user input may be associated with the string of phonemes to indicate that the user is saying or mean those words when they product that string of phonemes. A user-specific speech recognition key for the user account is then updated to associate the string of phonemes with these words. A general speech recognition model can also be trained using the association.

Abstract: In various embodiments, a voice command is associated with a plurality of processing steps to be performed. The plurality of processing steps may include analysis of audio data using automatic speech recognition, generating and selecting a search query from the utterance text, and conducting a search of database of items using a search query. The plurality of processing steps may include additional or different steps, depending on the type of the request. In performing one or more of these processing steps, an error or ambiguity may be detected. An error or ambiguity may either halt the processing step or create more than one path of actions. A model may be used to determine if and how to request additional user input to attempt to resolve the error or ambiguity. The voice-enabled device or a second client device is then causing to output a request for the additional user input.

Abstract: A speech processing system uses contextual data to determine the specific domains, subdomains, and applications appropriate for taking action in response to spoken commands and other utterances. The system can use signals and other contextual data associated with an utterance, such as location signals, content catalog data, data regarding historical usage patterns, data regarding content visually presented on a display screen of a computing device when an utterance was made, other data, or some combination thereof.

Abstract: A speech processing system uses contextual data to determine the specific domains, subdomains, and applications appropriate for taking action in response to spoken commands and other utterances. The system can use signals and other contextual data associated with an utterance, such as location signals, content catalog data, data regarding historical usage patterns, data regarding content visually presented on a display screen of a computing device when an utterance was made, other data, or some combination thereof.

Abstract: A request including audio data is received from a voice-enabled device. A string of phonemes present in the utterance is determined through speech recognition. At a later time, a subsequent user input corresponding to the request may be received, in which the user input is associated with one or more text keywords. The subsequent user input may be obtained in response to an active request. Alternatively, feedback may not be actively elicited, but rather collected passively. However it is obtained, the one or more keywords associated with the subsequent user input may be associated with the string of phonemes to indicate that the user is saying or mean those words when they product that string of phonemes. A user-specific speech recognition key for the user account is then updated to associate the string of phonemes with these words. A general speech recognition model can also be trained using the association.

Abstract: A method of test integration for early application development is provided. The method comprises defining a business case, identifying a plurality of systems to enable the business case, identifying at least one control document including handshakes for the systems, and generating test cases for each of the systems, the test cases including the handshakes useful to test applications. A testing integration system for early application development is also provided. The system comprises an input module operable to permit selection of a plurality of systems defining a business case, a control document defining handshakes between the systems, a template operable to receive information related to the control document and further operable for arranging the systems to enable the business case, and a generator operable to generate test cases including the handshakes based on the arrangement of the systems in the template.

Abstract: A system and method for engineering data into interface control documents is provided. The method includes creating and loading an interface control document by selecting features of an interface control document to create, providing a standards document having interface control document standards, and providing a case tool for maintaining interface control documents. The method provides for generating the interface control document using the standards document and based upon the selected features, and storing the interface control document in the case tool. The method includes designating a document having data attributes for the interface control document, reading at least some of the data attributes from the document, loading at least some of the data attributes read from the document into the interface control document, and storing the interface control document having at least some of the data attributed in the case tool.

Abstract: A device for modeling an integrated enterprise includes a first tool for constructing a model of the integrated enterprise and a second tool which validates compliance of documents constructed by the first tool with a set of standards. The documents which may be constructed by the first tool include an analysis interface control document (“ICD”) and a design ICD document. The second tool may then be used to selectively compare either the analysis ICD or the design ICD with selected ICD standards and generate an analysis ICD document standards exception report and a design ICD document standards exception report, respectively, which lists each variation of the analysis and design ICD documents from the selected ICD standards. The analysis and/or design ICD standards exception reports may subsequently be used as guides to correct errors in the analysis and/or design ICD documents causing the exceptions.

Abstract: A selected scenario of a design ICD document for an integrated enterprise is validated by examining each IDL call of each sequence diagram forming part of the selected scenario. A list of data attributes contained in one or more of the IDL calls are generated and each IDL call associated therewith is generated. A physical location to which each such IDL call is mapped is then associated with the IDL call. By analyzing the IDL calls and associated physical locations on a data attribute-by-data attribute basis, inconsistencies in the physical mapping of the data attributes to the databases forming an IIS for the integrated enterprise may be identified and subsequently corrected.