Method and apparatus for capture and formalization of system requirements and their transformation to test instructions

• US 20060010348A1
• Filed: 07/09/2004
• Published: 01/12/2006
• Est. Priority Date: 07/09/2004
• Status: Abandoned Application

• Current Assignee: Erik Magnus Hyllander, Karl Svante Lidman, Stefan Erik Bylund, Stig Nils-Olof Franzen
• Original Assignee: Erik Magnus Hyllander, Karl Svante Lidman, Stefan Erik Bylund, Stig Nils-Olof Franzen
• Inventors: Franzen, Stig Nils-Olof, Lidman, Karl Svante, Bylund, Stefan Erik, Hyllander, Erik Magnus
• Application Number:
  US10/886,691
• Publication Number:
  US 20060010348A1
• Time in Patent Office: Days
• US Class Current: 714/38
• CPC Class Codes: G06F 30/3323 using formal methods, e.g. equivalence checking or property checking

Abstract

A method for capturing requirements on a system and subsequently transforming the requirements into a test instruction for the system is disclosed. In a exemplary embodiment, a set of flows that captures the requirements of the system are created by repeatedly combining predefined templates of natural language text and populating them with information particular to the system and annotations to support identification of test data such as inputs to and outputs from the system. Based on the requirements specification a test instruction is prepared. This is done by first identifying points in the specified flow where input data must be provided or output data must be verified when testing an actual implementation of the specified system. By combining different specified flows and by giving the identified input and output data specific values a complete test instruction is created.

Claims

1. A method for capturing requirements on a system and transforming said requirements into test instructions for the system, the method comprising:

Specifying requirements by creating sequences of natural language sentences derived from a set of configurable templates and preexisting formalized knowledge about the systems users and the structure of the possible uses of the system and then transforming the captured requirements into a set of test instructions for the system.

2. The method of claim 1, wherein:

the system is a digital processing system, or part thereof, comprising a combination of the following;

commercially available software, custom built software, commercially available hardware, custom built hardware.

3. The method of claim 1, wherein:

the system is a business or enterprise seen as a set of business processes that communicates with their environment.

4. The method of claim 1, wherein:

the requirements on the system are captured as a set of flows describing various paths or parts of paths through the system.

5. The method of claim 1, wherein:

templates for valid sentences are adapted to take into account any pre-existing description of the system.

6. The method of claim 5, wherein:

the pre-existing description of the system is on the form of a Unified Modeling Language use-case model.

7. The method of claim 1, wherein:

the application of a template results in annotations of the resulting requirements specification.

8. The method of claim 7, wherein:

the annotations are used to transform the requirements specification into a test instruction.

9. The method of claim 8, wherein:

the annotations are used to identify points in an execution of the system, for the purpose of testing, where data is input to or output from the system or where the continuation of the execution depends on conditions internal or external to the system.

10. The method of claim 9, wherein:

the input test data needed at the data input points are categorized into the following categories;

valid, invalid, upper bound, lower bound, or not applicable.

11. The method of claim 9, wherein:

it is identified what the concrete values to be provided at input data points and what the concrete values to be expected at output data points should be.

12. The method of claim 4, wherein:

the structure of a test instruction is determined by creating combinations of flows that form concrete test scenarios.

13. The method of claim 12, wherein:

the application of a template results in annotations of the resulting requirements specification.

14. The method of claim 13, wherein:

the annotations are used to transform the requirements specification into a test instruction.

15. The method of claim 14, wherein:

the annotations are used to identify points in an execution of the system, for the purpose of testing, where data is input to or output from the system or where the continuation of the execution depends on conditions internal or external to the system.

16. The method of claim 15, wherein:

the input test data needed at the data input points are categorized into the following categories;

valid, invalid, upper bound, lower bound, or not applicable.

17. The method of claim 15, wherein:

it is identified what the concrete values to be provided at input data points and what the concrete values to be expected at output data points should be for each combination of flows.

18. The method of claim 1, wherein:

a complete test instruction suitable for machine processing or for carrying out a manual test procedure is generated.

19. A storage medium encoded with a machine readable computer program code for capturing requirements on a system and transforming said requirements into test instructions for the system, the storage medium including instructions causing a computer to implement a method, the method comprising:

Specifying requirements by creating sequences of natural language sentences derived from a set of configurable templates and preexisting formalized knowledge about the systems users and the structure of the possible uses of the system and then transforming the captured requirements into a set of test instructions for the system.

20. The storage medium of claim 19, wherein:

the system is a digital processing system, or part thereof, comprising a combination of the following;

commercially available software, custom built software, commercially available hardware, custom built hardware.

21. The storage medium of claim 19, wherein:

the system is a business or enterprise seen as a set of business processes that communicates with their environment.

22. The storage medium of claim 19, wherein:

the requirements on the system are captured as a set of flows describing various paths or parts of paths through the system.

23. The storage medium of claim 19, wherein:

templates for valid sentences are adapted to take into account any pre-existing description of the system.

24. The storage medium of claim 23, wherein:

the pre-existing description of the system is on the form of a Unified Modeling Language use-case model.

25. The storage medium of claim 19, wherein:

the application of a template results in annotations of the resulting requirements specification.

26. The storage medium of claim 25, wherein:

the annotations are used to transform the requirements specification into a test instruction.

27. The storage medium of claim 26, wherein:

the annotations are used to identify points in an execution of the system, for the purpose of testing, where data is input to or output from the system or where the continuation of the execution depends on conditions internal or external to the system.

28. The storage medium of claim 27, wherein:

the input test data needed at the data input points are categorized into the following categories;

valid, invalid, upper bound, lower bound, or not applicable.

29. The storage medium of claim 27, wherein:

it is identified what the concrete values to be provided at input data points and what the concrete values to be expected at output data points should be.

30. The storage medium of claim 22, wherein:

the structure of a test instruction is determined by creating combinations of flows that form concrete test scenarios.

31. The storage medium of claim 30, wherein:

the application of a template results in annotations of the resulting requirements specification.

32. The storage medium of claim 31, wherein:

the annotations are used to transform the requirements specification into a test instruction.

33. The storage medium of claim 32, wherein:

the annotations are used to identify points in an execution of the system, for the purpose of testing, where data is input to or output from the system or where the continuation of the execution depends on conditions internal or external to the system.

34. The storage medium of claim 33, wherein:

the input test data needed at the data input points are categorized into the following categories;

valid, invalid, upper bound, lower bound, or not applicable.

35. The storage medium of claim 33, wherein:

it is identified what the concrete values to be provided at input data points and what the concrete values to be expected at output data points should be for each combination of flows.

36. The storage medium of claim 19, wherein:

a complete test instruction suitable for machine processing or for carrying out a manual test procedure is generated.

37. A computer digital signal for capturing requirements on a system and transforming said requirements into test instructions, the computer digital signal comprising code configured to cause a processor to implement a method, the method comprising:

Specifying requirements by creating sequences of natural language sentences derived from a set of configurable templates and preexisting formalized knowledge about the systems users and the structure of the possible uses of the system and then transforming the captured requirements into a set of test instructions for the system.

38. The computer digital signal of claim 37, wherein:

the system is a digital processing system, or part thereof, comprising a combination of the following;

commercially available software, custom built software, commercially available hardware, custom built hardware.

39. The computer digital signal of claim 37, wherein:

the system is a business or enterprise seen as a set of business processes that communicates with their environment.

40. The computer digital signal of claim 37, wherein:

the requirements on the system are captured as a set of flows describing various paths or parts of paths through the system.

41. The computer digital signal of claim 37, wherein:

templates for valid sentences are adapted to take into account any pre-existing description of the system.

42. The computer digital signal of claim 41, wherein:

the pre-existing description of the system is on the form of a Unified Modeling Language use-case model.

43. The computer digital signal of claim 37, wherein:

the application of a template results in annotations of the resulting requirements specification.

44. The computer digital signal of claim 43, wherein:

the annotations are used to transform the requirements specification into a test instruction.

45. The computer digital signal of claim 44, wherein:

the annotations are used to identify points in an execution of the system, for the purpose of testing, where data is input to or output from the system or where the continuation of the execution depends on conditions internal or external to the system.

46. The computer digital signal of claim 45, wherein:

the input test data needed at the data input points are categorized into the following categories;

valid, invalid, upper bound, lower bound, or not applicable.

47. The computer digital signal of claim 45, wherein:

it is identified what the concrete values to be provided at input data points and what the concrete values to be expected at output data points should be.

48. The computer digital signal of claim 40, wherein:

the structure of a test instruction is determined by creating combinations of flows that form concrete test scenarios.

49. The computer digital signal of claim 48, wherein:

the application of a template results in annotations of the resulting requirements specification.

50. The computer digital signal of claim 49, wherein:

the annotations are used to transform the requirements specification into test instruction.

51. The computer digital signal of claim 50, wherein:

the annotations are used to identify points in an execution of the system, for the purpose of testing, where data is input to or output from the system or where the continuation of the execution depends on conditions internal or external to the system.

52. The computer digital signal of claim 51, wherein:

the input test data needed at the data input points are categorized into the following categories;

valid, invalid, upper bound, lower bound, or not applicable.

53. The computer digital signal of claim 51, wherein:

it is identified what the concrete values to be provided at input data points and what the concrete values to be expected at output data points should be for each combination of flows.

54. The computer digital signal of claim 37, wherein:

a complete test instruction suitable for machine processing or for carrying out a manual test procedure is generated.