Development strategies: Difference between revisions
(Created page with "Students must be able to formulate a development strategy for testing programs prior to writing any code. The development strategies include debugging, readability, alpha test...") |
No edit summary |
||
| Line 1: | Line 1: | ||
Students must be able to formulate a development strategy for testing programs prior to writing any code. The development strategies include debugging, readability, alpha testing, beta testing and exception handling. | === Students must be able to formulate a development strategy for testing programs prior to writing any code. The development strategies include debugging, readability, alpha testing, beta testing and exception handling. === | ||
Students must be able to apply different debugging techniques to fix a program, including tracing (print debugging), interactive debugging using a debugger, and understanding the behaviour of a program after it has crashed (post-mortem debugging) through analysing program output. | === Students must be able to apply different debugging techniques to fix a program, including tracing (print debugging), interactive debugging using a debugger, and understanding the behaviour of a program after it has crashed (post-mortem debugging) through analysing program output. === | ||
Students must be able to demonstrate good and consistent programming style throughout their programs including effective comments, naming conventions, and indentation of code to show program structure. | === Students must be able to demonstrate good and consistent programming style throughout their programs including effective comments, naming conventions, and indentation of code to show program structure.=== | ||
=== Students must be able to conduct alpha testing to evaluate whether system requirements are met and to determine any deficiencies in a program. === | |||
Students must be able to | === Students must be able to explain how to analyse data gathered through alpha testing to fix any discovered issues, modify program features, and evaluate when a program is beta test-ready. === | ||
Students must be able to explain how to | === Students must be able to explain how to determine what kinds of exceptions can occur in a program. === | ||
Students must be able to explain how to | === Students must be able to explain how, why, and where programs catch or throw exceptions and how to write the appropriate instructions in each case. They must be able to discuss the advantages and disadvantages of catching or throwing exceptions. === | ||
=== Students must be able to plan and implement a beta testing strategy to identify flaws and bugs in the program from the users’ point of view. === | |||
Students must be able to | === Students must be able to explain the roles of the two types of Beta tester and the nature of the feedback they generate. === | ||
=== Students must be able to demonstrate the different ways beta testing feedback can impact the development of an update/fix to the product prior to it being publicly released. === | |||
Students must be able to demonstrate the different ways beta testing feedback can impact the development of an update/fix to the product prior to it being publicly released. | |||