heres a copy paste job from one of the Software Design And Devlopment notes:
-[FONT="] [/FONT][FONT="]Defining the problem[/FONT][FONT="] involves attaining a thorough understanding of the problem and then detailed documentation of the exact requirements to be met. Fixing problems at this stage is far more cost effective than doing so at a later stage.[/FONT]
-[FONT="] [/FONT][FONT="]Planning the solution[/FONT][FONT="] involves further understanding of the needs of the users and choosing the method(s) to solve the problem. Data needs to be collected to support decisions.[/FONT]
-[FONT="] [/FONT][FONT="]Building the solution[/FONT][FONT="] assumes all team members have a full understanding of the problem. The program is usually coded according to the algorithms.[/FONT]
-[FONT="] [/FONT][FONT="]Checking the solution[/FONT][FONT="] is a continuous part of the process. If after testing it is determined it meets the requirements, it will be implemented. Once it has been coded, it is necessary to check that it works correctly.[/FONT]
-[FONT="] [/FONT][FONT="]Modifying the solution[/FONT][FONT="] often occurs before or after the solution has been implemented because of bugs, efficiency issues, and changes in hardware of software. Generally changes made at this stage are expensive, and if they are major ones, the system analyst may decide it is best to start from scratch"[/FONT]
im not too sure if those would apply for D&T seeing as i cant recall a single think ive learnt during junior years that were relevant to...well...anything.
really appreciated.