Design the solution
Code the programme
Test the programme
Document the programme – this should be done right the way through.
Implement the programme
Show the basic layout. Draw a story board to show the general layout of the program.
Name different items using the naming standards. e.g. lblExample, btnTest. (these labels go in the name part of the properties and with the storyboard for reference.)
Logic. Explain what each item does.
Draw a flow chart
Create the interface and add naming standards to each item (physical)
Code each logical item starting with the easiest thing first. (physical)
Test plan example
A test plan contains columns for the following:
The test number
A description of the test
The test data
The expected output
*Both the actual output and suggestions are filled in by someone else.
Checking the boundries
Check how the program performs when using numbers expected e.g. 1-100
Check the performance when using numbers outside the boundry e.g. 0 or 101
Check the performance when using special characters e.g. a-z
Uses the three letter acronym followed by the chosen naming standard which always starts with a capital letter.
– What can be done to fix any problems- What actually happened in the test- What should happen in the test- The data which will be used to carry out the test- to explain what the program will be doing in the test