1. How to manage the testing phase of the PSIP(s)
Isidoros Passas URENIO

2. In case of STRATINC: A process as well
Testing phase
In case of STRATINC: A process as well
Definition :
Testing is the process of executing a program with the intent of finding errors
Glen Myers
Objective explained:
Testing is obviously concerned with errors, faults, failures and incidents. A test is the act of exercising software with test cases with an objective of
Finding failure
Demonstrate correct execution
Paul Jorgensen

3. Classification of Test
One classification is based on the following methodologies:
Black box (Functional) Testing: inspects specified behavior
White box (Structural) Testing: inspects programmed behavior

4. Test methodologies
Structural (White box)
Functional (Black box)

5. Presentation methods of the testing phase
The cause-effect graph:
Examine the requirements and restate them as logical relation between inputs and outputs.
The result is a Boolean graph representing the relationships called a cause-effect graph.
The decision table:
each column of the decision table corresponds to a test case for functional testing.

6. Steps to create cause-effect graph
Study the functional requirements.
Mark and number all causes and effects.
Numbered causes and effects become nodes of the graph.
Draw causes on the LHS
Draw effects on the RHS
Draw logical relationship between causes and effects as edges in the graph.
Extra nodes can be added to simplify the graph

7. Cause Effect Graph

8. Decision Table
Two dimensional mapping of condition against actions to be performed
Conditions evaluate to Boolean
Action corresponds to expected activity
They can be derived from Cause Effect graph too
Map cause as condition
Map effect as action

9. Cause effect graph- Decision table
Test 1
Test 2
Test 3
Test 4
Test 5
Cause 1 I S
Cause 2 X
Cause 3
Cause 4
Cause 5
Effect 1 P A
Effect 2
Causes: I=Invoked X=don’t care S=suppressed
Effects: P=present A=absent

10. IEEE Standard 829 - 1998 Test plan identifier Introduction Test Items
Features to be tested
Features not to be tested
Approach
Item pass/fail criteria
Suspension criteria and resumption requirements

11. The testing phase of the PSIP in Region of Central Macedonia and the ICT cluster

12. Testing phase and STRATINC
Two main scopes
(a) Test the flow system of Information for the Strategic Intelligence platform
(b) Test the functionality of the software Pilot platform
Proposed Methodology
White Box for scope (a)
Black Box for scope (b)

13. Proposed testing process of the PSIP in RCM
The Information collection process into the PSIP will be tested based on the white box methodology by a Strategic Intelligent expert from URENIO.
The functions of the installed PSIP will be tested by the 20 companies that answered the questionnaires.

14. URENIO RCM Requirements
Investigation
Watch-Alert
Analysis & output
Information diffusion
Type of watch
Technological & scientific
Products
Market
Managerial
Supplier/provider
Costumer
Patents

15. Points that will be assessed during the Usability tests
All aspects of user interfaces are tested:
Display screens
messages
report formats
navigation and selection problems

16. Test Summary Report
Will be generated towards the end of the testing phase.
It will cover each subsystem:
Information collection process
And a summary of the tests which have been applied to the PSIP.

17. Testing phase deliverables
Test deliverables
Testing tasks
Responsibilities
Staffing and training needs
Risk and contingencies
Approvals