Abstract: A method for verifying reachability of a transition path between states with respect to Simulink/Stateflow models; (a) a concrete simulation model is generated and an abstract model is generated; (c) an abstract path is generated that is a sequence of transition steps from a start state to a target state; (d) a validity of the abstract path is checked utilizing the concrete simulation model; (e) a result is output to a user that identifies the abstract path as a reachable result; (f) partitioning a respective state of the transition step that was invalid in the abstract path; (g) recomputing a next abstract model based on partitioned start state; (h) generating an next abstract path; (i) determining whether the next abstract path is valid; (j) outputting a result to the user that identifies whether the recomputed abstract path is a valid result; otherwise proceeding to step (f).

Abstract: A method allows for testing software under test (SUT) with respect to a partial design model (PDM) having a boundary which differs from a boundary of the SUT. The method includes recording input information including the SUT, the PDM, and coverage criteria defining a required number of the test cases. Variables in the SUT are identified that correspond to boundary signals for the PDM. Test cases are extracted meeting the coverage criteria. The method may include generating additional test cases at the PDM level and mapping the additional cases with corresponding constraint functions to the boundary of the SUT using a forward/backward propagation and/or heuristics guided technique. A system for testing the SUT includes a host machine and memory. The host machine executes process instructions from memory to identify variables in the SUT that correspond to boundary signals for the PDM, and extracts test cases meeting the coverage criteria.

Abstract: A method allows for testing software under test (SUT) with respect to a partial design model (PDM) having a boundary which differs from a boundary of the SUT. The method includes recording input information including the SUT, the PDM, and coverage criteria defining a required number of the test cases. Variables in the SUT are identified that correspond to boundary signals for the PDM. Test cases are extracted meeting the coverage criteria. The method may include generating additional test cases at the PDM level and mapping the additional cases with corresponding constraint functions to the boundary of the SUT using a forward/backward propagation and/or heuristics guided technique. A system for testing the SUT includes a host machine and memory. The host machine executes process instructions from memory to identify variables in the SUT that correspond to boundary signals for the PDM, and extracts test cases meeting the coverage criteria.

Abstract: An automatic test-case generation system generates test-cases for validating a test specification for timing constraints, fault tolerances, distributed deadlocks, and synchronization at a system integration level of a distributed system. The automatic test-case generation system includes a model transformer for integrating functional model and platform specification. The functional model relates to an abstract model of at least one controller and the platform specification relates to details of platform components. A test specification transformer integrates platform specification, real-time requirements, and structural coverage criteria for generating an enhanced test specification for testing the distributed system. A requirements transformer integrates real-time requirements and functional requirements for the distributed system.

Abstract: A method for developing a specification includes receiving a plurality of requirements that define the functionality of the specification, wherein the plurality of requirements are expressed using a formal model. The method further includes analyzing the plurality of requirements using algorithms and determining if the plurality of requirements satisfies a predetermined set of criteria. The method further includes generating a summary of the formal analysis and refining the requirements by incorporating corrected analysis results.