Abstract: In a software development system, a method for assisting a user in creating source code for a computer program in a high-level programming language. The method comprises: at a current user inputting location within a piece of source code under development, detecting a need for assisting the user with input for the creation of the piece of source code under development; determining fitting source code elements suitable for input at said current inputting location; and providing, e.g. displaying to the user said list of fitting source code elements, wherein, in order to determine the fitting source code elements, for each fitting source code element a respective fitting probability of the source code element in the current inputting location is determined, and wherein the user is provided with the list of fitting source code elements by associating to each fitting source code element in the list an indication of the respective fitting probability.

Abstract: A method for facilitating the management of a test process is proposed. For this purpose, the different test scenarios included in the process and their execution dependencies are represented by means of a customized UML activity diagram (300a). An execution weight is also associated with each test scenario (for example, defined by the man-hours required for its execution). In this way, it is possible to identify critical test scenarios (315g), which may impair the execution of the whole test process when they fail (because many other test scenarios depend on their successful completion). The order of execution of the test scenarios is then arranged into a test plan, so as to minimize the time required to reach the critical test scenarios. Preferably, the same process is repeated whenever any runtime condition changes (such when a test scenario fails).

Abstract: In a software development system, a method for assisting a user in creating source code for a computer program in a high-level programming language. The method comprises: at a current user inputting location within a piece of source code under development, detecting (405,410) a need for assisting the user with input for the creation of the piece of source code under development; determining (415) fitting source code elements suitable for input at said current inputting location; and providing, e.g. displaying (420) to the user said list of fitting source code elements, wherein, in order to determine the fitting source code elements, for each fitting source code element a respective fitting probability of the source code element in the current inputting location is determined, and wherein the user is provided with the list of fitting source code elements by associating to each fitting source code element in the list an indication of the respective fitting probability.

Abstract: A method for facilitating the management of a test process is proposed. For this purpose, the different test scenarios included in the process and their execution dependencies are represented by means of a customized UML activity diagram (300a). An execution weight is also associated with each test scenario (for example, defined by the man-hours required for its execution). In this way, it is possible to identify critical test scenarios (315g), which may impair the execution of the whole test process when they fail (because many other test scenarios depend on their successful completion). The order of execution of the test scenarios is then arranged into a test plan, so as to minimize the time required to reach the critical test scenarios. Preferably, the same process is repeated whenever any runtime condition changes (such when a test scenario fails).