Evaluation of digitally authored systems

Question 1

What is evaluation?

Answer 1

Testing and reviewing the system to ensure that it meets the user requirements and is a full, robust and efficient solution

It should be carried out throughout the development

A range of people should take part including developers and users

Should contain evidence to support any statements made about the quality of the system - things such as outcomes from testing and observations can be used as a source

Question 2

What is an efficient solution?

Answer 2

Includes code written in small re-usable sections and has acceptable response times when operated by the user

Question 3

What are user requirements?

Answer 3

A document that details what the end user expects the system to do, it often forms part of a contract between the developer and the end user

Question 4

What is robustness?

Answer 4

A measure of the systems ability to continue to run when high volumes of valid, exceptional or invalid data are entered

If the system does not crash when processing large amounts of valid, invalid or exceptional data then we can say its robust

A good test plan can help predict the robustness of the system

Question 5

What are the two types of user requirements?

Answer 5

Functional and non-functional

Question 6

What are functional user requirements?

Answer 6

Describe the things that the system should be able to do, for example produce a total value or output a particular report. These can be easily identified by examining the user requirements

Question 7

What are non-functional user requirements?

Answer 7

Describe the way in which a system should work, for example the performance of a system in terms of user response time, the usability of the system and the reliability of the system