A time-based grid that shows tasks and resources to accomplish a job.
1 of 22
Task
A piece of work that has to be done.
2 of 22
Sub-Task
A task that is performed to allow you to complete a larger more complex task.
3 of 22
Implementation
The process of putting a plan into effect
4 of 22
Prototyping
Prototyping is a test model of the product or system before the final version is released. It can be used to identify the issues with a design so it can be improved.
5 of 22
Normal Data
Data that is within the boundaries of the validation of the field.
6 of 22
Boundary Data
It is data that is at a boundary of the validation of the field. (The edge of what should be accepted)
7 of 22
Erroneous Data
It is data entered that shouldn’t fit the validation of the field. It’s not always possible to fully test this because there could be lots of different erroneous data.
8 of 22
5 things a test plan should prove
• That validation checks work. • That verification checks work. • That the system has the required fields. • That the system has error messages. • That the system meets client requirements.
9 of 22
Transcription Error
Can occur when data is being transferred manually, usually from a paper-based document. For example, an examination mark written on the sheet as 87 might be entered as 57 perhaps because the number wasn't written clearly enough
10 of 22
How will the client requirements be tested?
Use a test table to show which requirement has been tested and take screenshots for proof that the test has been done.
11 of 22
Why should scrolling be kept to a minimum on electronic based forms?
Scrolling should be kept to a minimum so the user doesn’t get lost and confused about where they should enter the data. Also it makes it easier to read if it is all on one page.
12 of 22
Why is it important that the user and not just the client’s requirements are tested?
The client may want the system to do something however they may not be using it. The users are the people who are going to be using the system so they also need it to fit their requirements, e.g. easy to use.
13 of 22
Why is it important to test the output on the same equipment, for example monitor size and printer, as what will be used by the user?
To check that the software is suitable for use on their system. If the system doesn’t work on their output equipment, the system will have to be changed and improved.
14 of 22
Why would it be beneficial to give the user a set of tests to carry out and let them use the system unaided?
It lets you see what the user can and can’t do on the system you’ve created. This then means that the system can be changed so that they can use it perfectly before implementing it into a business.
15 of 22
Why is it important to go back over the client requirements at this stage of the evaluation?
To make sure that all the client requirements have been met.
16 of 22
For what 3 reasons might the design of a product change by the time it comes to evaluating the completed solution?
• The original design didn’t work. • A better method suggested itself as the work was being carried out. • The client changed their mind about what they wanted, perhaps as a result of seeing the implementation as it was worked on.
17 of 22
Why is self-evaluation done?
Self-evaluation is done so you can see if you planned things well and managed your time effectively etc. You can use to self-evaluation to try and improve yourself in the next process of designing a solution.
18 of 22
Is the solution an effective one? (What questions need to be asked to evaluate whether the solution is effective or not)
• How long does it take? • How efficient are the controls? • How intuitive is the solution? • How accurate is the input data? • How efficient is the processing? • How appropriate are the outputs? • How robust is the solution?
19 of 22
What is an intuitive solution?
One that feels natural and logical to the user.
20 of 22
What is an efficient solution?
One where the user does not waste time or effort when using it.
21 of 22
What is a robust solution?
One that works reliably without failing or causing system errors.
Comments
Report
Report