ANALYTICAL SOFTWARE DESIGN SYSTEM

• US 20130117727A1
• Filed: 12/21/2012
• Published: 05/09/2013
• Est. Priority Date: 05/05/2004
• Status: Active Grant

• Current Assignee: Cocotec Limited
• Original Assignee: Silverdata Limited
• Inventors: Broadfoot, Guy Hampson, Hopcroft, Philippa Jane
• Granted Patent: US 8,943,465 B2
• Time in Patent Office: Days
• US Class Current: 717/104
• CPC Class Codes: G06F 8/10 Requirements analysis; Specification techniques
• CPC Class Codes: G06F 8/20 Software design
• CPC Class Codes: G06F 8/24 Object-oriented

Abstract

An analytical software design system arranged to receive informal system design specifications and to convert them into verified design specifications for use in creating source code and carrying out implementation testing of the source code is described. The system comprises a verified black box specification generator arranged to process the received informal system design specifications to create formal specifications; to generate from the formal specifications mathematical models representing the system behaviour; to analyse the mathematical models to determine if they have the required behaviour; to adjust the formal specifications until the required behaviour is achieved; and to derive the required verified design specifications from the mathematical models.

Claims

1. (canceled)

2. An analytical software design system comprising:

a verified specification generator including a processor arranged to enable received informal design specifications of a software system to be developed for each component of the software system into;

(i) formal design specifications; and

(ii) formal interface specifications of required run-time interface behavior which capture run-time behavior present at respective interfaces of the each component with all other components with which the component interacts,

the verified specification generator comprising;

a model generator arranged to generate automatically, for each of the components, a mathematical model of run-time system behavior for the component with all other components with which the component interacts from the formal design specifications and the formal interface specifications; and

a model verifier arranged to analyze the mathematical models to determine if the mathematical models have required run-time system behavior for the corresponding components, to identify errors in the formal interface specifications and the formal design specifications, and to feedback the errors into at least one of the informal or formal design specifications;

wherein the verified specification generator is arranged to enable user adjustment of the formal interface specifications and the formal design specifications to generate corrected mathematical models respectively for the components, to analyze the corrected mathematical models, to identify errors, to feedback the errors until the required run-time system behavior for the corresponding component is achieved, and to derive the verified design specifications from error-free mathematical models.

3. The software design system according to claim 2, the informal system design specifications comprising informal requirement specifications, informal architecture specifications and informal component and specification designs.

4. The software design system according to claim 2, wherein the specification generator is arranged to ensure that formal component design specifications are created to be compatible with required run-time interface behavior.

5. The software design system according to claim 2, wherein the specification generator is arranged to generate a verified requirements specification, a verified architecture specification, a verified component design specification and a verified component interface specification.

6. The software design system according to claim 2, wherein the model generator is arranged to generate mathematical models in CSP notation.

7. The software design system according to claim 2, wherein the specification generator comprises a sequenced-based specification generator for processing the received informal system design specifications to create the formal specifications.

8. The software design system according to claim 7, wherein the sequenced-based specification generator is arranged to output analysis data for user consideration of the design specifications.

9. The software design system according to claim 2, wherein

i) the model generator is arranged to generate mathematical models in CSP notation,

ii) the specification generator includes:

a sequenced-based specification generator for processing the received informal system design specifications to create the formal specifications; and

the model verifier including an FDR model checker for checking mathematical models described in CSP notation.

10. The software design system according to claim 2, wherein

i) the model generator is arranged to generate mathematical models in CSP notation,

ii) the specification generator includes:

a sequenced-based specification generator for processing the received informal system design specifications to create the formal specifications; and

the model verifier being arranged to feedback specification and design defects to the sequenced-based specification generator such that corrected formal specifications can be created to compensate for the defects, thereby enabling the model generator to create corrected mathematical models.

11. The software design system according to claim 9, wherein model verifier is arranged to feedback specification and design defects to the sequenced-based specification generator such that corrected formal specifications can be created to compensate for the defects, thereby enabling the model generator to create corrected mathematical models.

12. The software design system according to claim 2, further comprising an editor module arranged to enable user editing of the formal and informal specifications via data input screens.

13. The software design system according to claim 12, wherein the editor module is arranged to store data as data files.

14. The software design system according to claim 2, further comprising an automated code generator for creating machine generated program source code from the verified specifications.

15. The software design system according to claim 2, further comprising an automated component test case generator for creating machine generated component test cases from the verified specifications.

16. The software design system according to claim 2, further comprising a verified implementation specification generator for creating verified implementation specifications from the verified specifications.

17. The software design system according to claim 16, wherein the verified implementation specification generator is arranged to process the received verified specifications to create formal implementation specifications;

to generate from the formal implementation specifications mathematical models representing run-time implementation behavior of the software design system;

to analyse the mathematical models representing the run-time implementation behavior to determine if the mathematical models representing the run-time implementation behavior have required run-time implementation behavior;

to adjust the formal implementation specifications until the required run-time implementation behavior is achieved; and

to derive required verified component implementation specifications from the mathematical models representing the run-time implementation behavior.

18. The software design system according to claim 17, wherein the system is arranged to process verified requirement specifications, verified architecture specifications and verified component design specifications.

19. The software design system according to claim 18, wherein the verified implementation specification generator is arranged to create formal implementation specifications meeting the verified requirement specifications.

20. The software design system according to claim 19, wherein the verified implementation specification generator is arranged to create the formal interface specifications as fully-specified specifications of the required run-time interface behavior.

21. The software design system according to claim 17, wherein the verified implementation specification generator is arranged compare the verified component implementation specifications against the verified component design specifications and to detect and remove any errors found.

22. The software design system according to claim 17, wherein the verified implementation specification generator is arranged to carry out a box structure development method for creating formal implementation specifications.

23. The software design system according to claim 22, wherein the verified implementation specification generator comprises a model generator for generating the mathematical models representing the run-time implementation behavior of the software design system from the formal implementation specifications.

24. The software design system according to claim 23, wherein the model generator of the verified implementation specification generator is arranged to generate mathematical models in CSP notation.

25. The software design system according to claim 17, wherein the implementation specification generator comprises a model verifier for analysing the mathematical models representing the run-time implementation behavior to determine if the mathematical models representing the run-time implementation behavior have the required run-time implementation behavior.

26. The software design system according to claim 22, wherein the implementation specification generator comprises a model verifier for analysing the mathematical models representing the run-time implementation behavior to determine if the mathematical models representing the run-time implementation behavior have the required run-time implementation behavior and the model verifier of the implementation specification generator comprises an FDR model checker for checking mathematical models described in CSP notation.

27. The software design system according to claim 22, wherein the implementation specification generator comprises a model verifier for analysing the mathematical models representing the run-time implementation behavior to determine if the mathematical models representing the run-time implementation behavior have the required run-time implementation behavior and the model verifier of the implementation specification generator is arranged to feedback specification and design defects to the verified implementation specification generator implementing the box-structured development method, such that corrected formal specifications can be created to compensate for the defects, thereby enabling the model generator of the implementation specification generator to create corrected mathematical models.

28. The software design system according to claim 17, further comprising an editor module arranged to enable user editing of the formal implementation specifications.

29. The software design system according to claim 28, wherein the editor module is arranged to store data as data files.

30. The software design system according to claim 2, further comprising an interface protocol verifier generator for creating machine-generated interface protocol verifiers from the verified specifications.

38. The system according to claim 12, wherein the editor module is arranged to generate the data input screens, each of the screens including a name of an interface, a unique identifier for each stimulus and response belonging to the interface, a list of input stimuli, and a list of responses.

39. The system according to claim 12, wherein the editor module is arranged to present enumeration tables which are each divided into sections, the sections including a section for a Canonical Sequence which results from the sequence-based specification.

40. The system according to claim 15, wherein the automated test case generator comprises:

a test sequence generator arranged to generate a set of test cases in the form of sequences of input stimuli with expected responses;

a test program generator which generates test programs corresponding to each of the test cases; and

a test oracle which takes data files, generated by the test programs, that record the results of the test and is arranged to analyze the results to determine whether the test succeeded.

42. The system of claim 2, wherein the formal interface specifications are achieved by introducing overlapping predicates to capture for a given stimulus a plurality of possible responses and subsequent behavior.

44. The system of claim 40, wherein the formal interface specifications are achieved by introducing overlapping predicates to capture for a given stimulus a plurality of possible responses and subsequent behavior.

31. An analytical software design system arranged to receive informal system design specifications of a software system and to convert them into verified design specifications for use in creating source code and carrying out implementation testing of the source code, the software design system being arranged to handle informal system design specifications comprising informal requirement specifications, informal architecture specifications and informal component and specification designs, the software design system comprising:

a verified specification generator including a processor to;

process the received informal system design specifications;

for each component of the software system, create formal design specifications;

create formal interface specifications of required run-time interface behavior of each of the components that is visible by its interfaces, the formal interface specifications being specifications of the required run-time interface behavior which captures run-time behavior present at the respective interfaces of the each component with all other components with which the component interacts;

generate from the formal design specifications and the formal interface specifications, for each of the components, a mathematical model representing run-time system behavior for the component with all other components with which the component interacts;

analyse the mathematical models to determine if the mathematical models have required run-time system behavior;

adjust at least one of the formal design specifications or the formal interface specifications until the required run-time system behavior is achieved; and

derive the verified design specifications from the mathematical models.

32. The software design system according to claim 31, wherein the specification generator comprises a sequenced-based specification generator for processing the received informal system design specifications to create the formal design specifications and the formal interface specification.

33. The software design system according to claim 32, wherein the sequenced-based specification generator is arranged to output analysis data for user consideration of the formal interface specifications and the formal design specifications.

34. The software design system according to claim 31, wherein the specification generator comprises a model verifier for analysing the mathematical models to determine if the mathematical models have the required run-time system behavior.

43. The system of claim 31, wherein the formal interface specifications are achieved by introducing overlapping predicates to capture for a given stimulus a plurality of possible responses and subsequent behavior.

35. An analytical software design system arranged to receive informal system design specifications of a software system and to convert the informal system design specifications into verified design specifications for use in creating source code and carrying out implementation testing of the source code, the software design system comprising:

a verified specification generator arranged to;

process the received informal system design specifications and for each component of the software system to create formal design specifications;

generate from the formal design specifications mathematical models representing run-time system behavior of the software system;

analyse the mathematical models to determine if the mathematical models have required run-time system behavior;

adjust the formal design specifications until the required run-time system behavior is achieved; and

derive verified design specifications from the mathematical models; and

a verified implementation specification generator for creating verified implementation specifications from the verified specifications, the verified implementation specification generator being arranged to;

process the received verified specifications to create formal implementation specifications;

generate from the formal implementation specifications, for each of the components, a mathematical model representing run-time implementation behavior for the component with all other components with which the component interacts;

analyse the mathematical models representing the run-time implementation behavior to determine if the mathematical models representing the run-time implementation behavior have required run-time implementation behavior;

adjust the formal implementation specifications until the required run-time implementation behavior is achieved; and

derive the verified implementation specifications from the mathematical models representing the run-time implementation behavior,

wherein at least one of the verified specification generator and the verified implementation specification generator includes a processor.

41. The system as claimed in claim 35, further comprising:

creating formal interface specifications of a required functional run-time behaviour of each component that is visible by its interfaces, the formal interface specifications being created as specifications of the required functional run-time behaviour which captures run-time behaviour present at the respective interface of the each component with all other components with which the component interacts.

36. A method of carrying out analytical software design by receiving informal system design specifications of a software system and converting the informal system design specifications into verified design specifications for use in creating source code and carrying out implementation testing of the source code, the method comprising:

processing the received informal system design specifications and for each component of the software system creating formal design specifications;

creating formal interface specifications of required run-time interface behavior of each of the components that is visible by its interfaces, the formal interface specifications capturing run-time behavior present at the respective interfaces of the each component with all other components with which the component interacts;

generating from the formal design specifications and the formal interface specifications, for each of the components, a mathematical model representing run-time system behavior for the component with all other components with which the component interacts;

analysing the mathematical models to determine if the mathematical models have required run-time system behavior;

adjusting at least one of the formal design specifications or the formal interface specifications until the required run-time system behavior is achieved; and

deriving the verified design specifications from the mathematical models,

wherein at least one of the processing, the creating, the generating, the analyzing, the adjusting and the deriving is by a processor.

45. The method of claim 36, wherein the formal interface specifications are achieved by introducing overlapping predicates to capture for a given stimulus a plurality of possible responses and subsequent behavior.

37. A non-transitory data carrier having stored thereon a program for a computer for configuring the computer to implement a method of carrying out analytical software design by receiving informal system design specifications of a software system and converting the informal system design specifications into verified design specifications for use in creating source code and carrying out implementation testing of the source code, the method comprising:

processing the received informal system design specifications and for each component of the software system creating formal design specifications;

creating formal interface specifications of required run-time interface behavior of each of the components that is visible by its interfaces, the formal interface specifications being created specifications of the required run-time interface behavior which captures run-time behavior present at the respective interfaces of the each component with all other components with which the component interacts;

generating, from the formal design specifications and the formal interface specifications, for each of the components, a mathematical model representing run-time system behavior for the component with all other components with which the component interacts;

analysing the mathematical models to determine if the mathematical models have required run-time system behavior;

adjusting at least one of the formal design specifications or the formal interface specifications until the required run-time system behavior is achieved; and

deriving the verified design specifications from the mathematical models.

46. The non-transitory data carrier of claim 37, wherein the formal interface specifications are achieved by introducing overlapping predicates to capture for a given stimulus a plurality of possible responses and subsequent behavior.