COncORDE Teting of Integrated System (D6.8)

Name of tester *

Partner organisation *

COncORDE Module being tested: *


Functional completeness *

1234
1. Completeness of functionality with regard to functional specifications.
If other, precise:

Functional correctness *

1234
1. Correct implementation of data and information transfers through the interface functions.
2. Low frequency of failures to exchange data between the module and other involved modules/services.
If other, precise:

Functionality appropriateness *

1234
1. No deviation between the actual and reasonably expected results.
2. Low frequency of encountering inaccurate results/behaviour.
If other, precise:

Availability *

1234
1. Degree to which the module was operational and available when required for use.
If other, precise:

Maturity *

1234
1. Degree to which the module satisfied your needs for using it under normal operation.
2. Degree to which you felt that the module’s functionality was not giving expected results or not at expected time, etc..
If other, precise:

Fault Tolerance *

1234
1. Low frequency of breaks of the module.
2. Degree of appearance of failures/faults during the testing/evaluation period.
If other, precise:

Recoverability *

1234
1. When a failure occurred, no much time was required before gradual start-up of the module/system.
2. Capability of the involved functionality in restoring itself after an abnormal event or at request.
If other, precise:

User interface aesthetics *

1234
1. Attractiveness of the user interface of the involved services/functions.
If other, precise:

User error protection *

1234
1. Support by the system in avoiding errors when using the services/functions.
If other, precise:

Time Behaviour *

1234
1. Satisfactory response time of the services/functionality.
2. Throughput of the operations close to the specified requirements.
If other, precise:

Resource utilisation *

1234
1. Proper utilisation of memory resources (did you, for example, encounter “low memory” problems?).
If other, precise:

Capacity *

1234
1. Ability for the system to remain operational when pushed to its limits in terms of number of users, frequency of requests, etc.
If other, precise:

Analysability *

1234
1. Ease of analysing a failure occurrence.
2. Ease of finding the cause of a failure.
3. Ability of recording individual activities during operation of the involved services/functions.
4. Ability of monitoring the execution status.
If other, precise:

Modifiability *

1234
1. Readiness of services to accept parameterisation.
2. Availability of the appropriate mechanisms to be ready for changes at any time.
If other, precise:

Modularity *

1234
1. Ability to decompose the service/functionality into smaller pieces, without affecting the operation of the others.
2. Keeping the effect of the modification of the involved services/functionality local.
If other, precise:

Testability *

1234
1. Availability of enough information on the module/system functionality, in order to perform the testing.
2. Acceptability of time needed for testing after a failure resolution.
If other, precise:

Reusability *

1234
1. Ability to take pieces of the service/functionality and use it in another context.
If other, precise:

Adaptability (please, rate based on best guess given the information available) *

1234
1. Adaptability of the involved services to several hardware and software operation environments and network facilities.
2. Adaptability of the involved services to other infrastructures of medical emergency response organisations.
3. Level of effort required for the involved services to be adapted to a specific operational environment.
If other, precise:

Install-ability *

1234
1. Documentation for the installation process.
2. Ease and flexibility of installation process.
3. Ease of performing subsequent installations.
If other, precise:

Replaceability *

1234
1. Ease of maintaining the functionality when replacements of other parts of the module or other modules, happen.
2. Ease of maintaining the continuation of the data flows at replacement requests.
If other, precise:

Co-existence *

1234
1. Ability to operate within a shared integration environment, together with other modules/services.
2. Degree of customisation required when the service needs to co-exist in a specific integration environment.
If other, precise:

Interoperability *

1234
1. Use of standard application programming interfaces.
2. Openness and ease of use of the interfaces.
If other, precise: