TESTING FUNCTIONAL REQUIREMENTS USING B MODEL SPECIFICATIONS

Reasons for Requirement Testing

There are numerous economic reasons to improve the quality of software by testing the requirements:

Reducing the costs to detect and correct defects. Reducing the time it takes to deliver the software and Improving the probability of successfully installing the right solution

PROPOSED SOLUTION

In this paper, we proposed an approach that generates test cases for testing of functional requirements of the system. Following are the major conclusions drawn from the research work are:

Specifications annotated with requirement identifiers, help in later stages to detect which requirements are covered and which are yet to be tested.

Coverage matrices between requirements and generated test cases help to resolve the reach ability issues in system under test.

B specifications are more appropriate for testing requirements of the system as compared to Z because B covers whole lifecycle including specification, refinement and generating proof obligations.

Coverage of requirements in proposed approach is better than other approaches that we explored in section 2, in test case generation for testing requirements of the system.

Takes English textual written requirements which are providing the scope of system

Atelier-B tool then convert requirements into formal specification

Protest-B tool do model checking of developed formal specification of requirement

Test case is generated at the end

ADVANTAGES

Using B formal specification removes inconsistencies, ambiguousness and informality in requirements due to natural language

The tool provides requirements to be annotated with requirement identifiers, which provide help in later stages to detect which requirement are tested and which are not