Abstract: A method includes analyzing operational code to determine identifiers used within the operational code. The method further includes grouping like identifiers based a relational aspect of the identifiers. The method further includes, for one or more identifier groups, determining potential feature(s) of the identifier group(s). The method further includes testing the potential feature(s) based on a corresponding feature test suite to produce feedback regarding meaningfulness of the potential feature(s). The method further comprises, when the meaningfulness is above a threshold, adding the potential feature(s) to a feature set. The method further includes, when the meaningfulness is at or below the threshold, adjusting analysis parameter(s), grouping parameter(s), feature parameter(s), and/or testing parameter(s).

Abstract: A method includes analyzing operational code to determine identifiers used within the operational code. The method further includes grouping like identifiers based a relational aspect of the identifiers. The method further includes, for one or more identifier groups, determining potential feature(s) of the identifier group(s). The method further includes testing the potential feature(s) based on a corresponding feature test suite to produce feedback regarding meaningfulness of the potential feature(s). The method further comprises, when the meaningfulness is above a threshold, adding the potential feature(s) to a feature set. The method further includes, when the meaningfulness is at or below the threshold, adjusting analysis parameter(s), grouping parameter(s), feature parameter(s), and/or testing parameter(s).

Abstract: A method begins by generating application system state transitions from inputted requirements and parameters. For a current implementation of generating application code, the method continues by entering a loop. The loop begins by generating a current intermediate result based on a previous implementation and in accordance with current application code development factors. The loop continues by generating at least one test case based on the one or more of the application system state transitions. The loop continues by testing the current intermediate result in accordance with the at least one test case. When the testing is unfavorable, the loop continues by modifying one or more of: the one or more of the plurality of application system state transitions, the one or more of the parameters, and the one or more implementation tools. The loop then continues by repeating the loop using the modified current application code development factors.

Abstract: A method includes analyzing operational code to determine identifiers used within the operational code. The method further includes grouping like identifiers based a relational aspect of the identifiers. The method further includes, for one or more identifier groups, determining potential feature(s) of the identifier group(s). The method further includes testing the potential feature(s) based on a corresponding feature test suite to produce feedback regarding meaningfulness of the potential feature(s). The method further comprises, when the meaningfulness is above a threshold, adding the potential feature(s) to a feature set. The method further includes, when the meaningfulness is at or below the threshold, adjusting analysis parameter(s), grouping parameter(s), feature parameter(s), and/or testing parameter(s).

Abstract: A method begins by generating application system state transitions from inputted requirements and parameters. For a current implementation of generating application code, the method continues by entering a loop. The loop begins by generating a current intermediate result based on a previous implementation and in accordance with current application code development factors. The loop continues by generating at least one test case based on the one or more of the application system state transitions. The loop continues by testing the current intermediate result in accordance with the at least one test case. When the testing is unfavorable, the loop continues by modifying one or more of: the one or more of the plurality of application system state transitions, the one or more of the parameters, and the one or more implementation tools. The loop then continues by repeating the loop using the modified current application code development factors.

Abstract: A method begins by generating application system state transitions from inputted requirements and parameters. For a current implementation of generating application code, the method continues by entering a loop. The loop begins by generating a current intermediate result based on a previous implementation and in accordance with current application code development factors. The loop continues by generating at least one test case based on the one or more of the application system state transitions. The loop continues by testing the current intermediate result in accordance with the at least one test case. When the testing is unfavorable, the loop continues by modifying one or more of: the one or more of the plurality of application system state transitions, the one or more of the parameters, and the one or more implementation tools. The loop then continues by repeating the loop using the modified current application code development factors.

Abstract: A system includes a requirements unit, an implementation unit, and a testing unit. The requirements unit generates application requirements from inputted requirements and parameters and output them in accordance with a system communication protocol. The implementation unit generates application code based on the application requirements, the parameters, and feedback and outputs the application code in accordance with the system communication protocol. The testing unit tests the application code based on the application requirements and the parameters to produce the feedback.

Abstract: A method for execution by a processing module begins by receiving inputted requirements and parameters. The method continues by generating application requirements based on the inputted requirements, the parameters, and verification feedback. For one or more application requirements, the method continues by determining whether the generating of the one or more application requirements is consistent with valid system states and correctness criteria to produce one or more verification results. For the one or more application requirements, the method continues by comparing the one or more verification results with one or more verification thresholds to produce the verification feedback.

Abstract: A testing unit includes an input/output module and a processing module. The input/output module receives application requirements and parameters. The processing module generates a set of test cases based on the application requirements and the parameters; adjusts at least some of the set of test cases based on a code generation progression to produce targeted progression test cases; and tests a developing application code based on the targeted progression test cases, wherein the code generation progression indicates a level of development of the developing application code.

Abstract: A method begins by generating application system state transitions from inputted requirements and parameters. For a current implementation of generating application code, the method continues by entering a loop. The loop begins by generating a current intermediate result based on a previous implementation and in accordance with current application code development factors. The loop continues by generating at least one test case based on the one or more of the application system state transitions. The loop continues by testing the current intermediate result in accordance with the at least one test case. When the testing is unfavorable, the loop continues by modifying one or more of: the one or more of the plurality of application system state transitions, the one or more of the parameters, and the one or more implementation tools. The loop then continues by repeating the loop using the modified current application code development factors.

Abstract: A method, apparatus, and electronic device for optimizing a media presentation to a group. A memory may store a personal media user profile for a user. A processor may create a group media user profile from the personal media user profile and associated individual media user profiles. A network interface may send a request to a digital media content source for a set of digital media content with a digital media content profile that matches the group media user profile.

Abstract: A method, apparatus, and electronic device for optimizing content acquisition are disclosed. A memory may store usage of a previous set of media content by the mobile device. An input/output device may receive a request for a current set of media content. A processor may create a user profile based on the usage and provides a first recommendation of a first digital rights agreement based on the user profile.

Abstract: A system [100] includes a database [130] to store a user profile for a user [140]. The user profile contains user-specific information. An intelligent agent [120] monitors a conversation involving the user for at least one keyword. In response to detecting the at least one keyword, the intelligent agent: (a) searches the user profile for at least one item corresponding to the at least one keyword; (b) retrieves the at least one item from the user profile; and (c) determines a relevance between the at least one keyword and the at least one item. An application communication element [135] communicates application information corresponding to the at least one item to an application program in response to the relevance exceeding a predetermined threshold.