2016
DOI: 10.1007/s10009-016-0442-1
|View full text |Cite
|
Sign up to set email alerts
|

Exact finite-state machine identification from scenarios and temporal properties

Abstract: Finite-state models, such as finite-state machines (FSMs), aid software engineering in many ways. They are often used in formal verification and also can serve as visual software models. The latter application is associated with the problems of software synthesis and automatic derivation of software models from specification. Smaller synthesized models are more general and are easier to comprehend, yet the problem of minimum FSM identification has received little attention in previous research. This paper pres… Show more

Help me understand this report
View preprint versions

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
25
0

Year Published

2016
2016
2022
2022

Publication Types

Select...
3
2
1

Relationship

1
5

Authors

Journals

citations
Cited by 26 publications
(25 citation statements)
references
References 37 publications
0
25
0
Order By: Relevance
“…6 Note, however, that our algorithms perform better in terms of execution time than approaches that solve exact identification problems. For example, [47] report experiments where learning a Mealy machine of 18 states requires more than 29 hours. The majority of the execution time here is spent in proving that there exists no machine with fewer than 18 states which is also consistent with the examples.…”
Section: Experimental Comparisonmentioning
confidence: 99%
“…6 Note, however, that our algorithms perform better in terms of execution time than approaches that solve exact identification problems. For example, [47] report experiments where learning a Mealy machine of 18 states requires more than 29 hours. The majority of the execution time here is spent in proving that there exists no machine with fewer than 18 states which is also consistent with the examples.…”
Section: Experimental Comparisonmentioning
confidence: 99%
“…The works [6]- [8] are among the ones which propose solutions for this problem along with the tools which implement them. Then, note that operator X allows representing behavior traces in LTL, but for the purpose of computational efficiency it is possible to consider them separately [9]. Finally, there are approaches, such as [10], which treat behavior traces as the only kind of input data.…”
Section: Basic Block Modelsmentioning
confidence: 99%
“…On each iteration, the analyst first attempts to synthesize the models which comply with L (line 3). Since multiple synthesis tools are known [6]- [9], different tools can be used to obtain different models. In this paper, we use the following tools: Unbeast (https://www.react.uni-saarland.de/tools/unbeast), G4LTL-ST (https://sourceforge.net/projects/g4ltl), BoSy (https://github.com/reactive-systems/bosy), EFSM-Tools (https://github.com/ulyantsev/EFSM-tools).…”
Section: Workflowmentioning
confidence: 99%
“…6 Note, however, that our algorithms perform better in terms of execution time than approaches that solve exact identification problems. For example, [47] report experiments where learning a Mealy machine of 18 states requires more than 29 hours. The majority of the execution time here is spent in proving that there exists no machine with fewer than 18 states which is also consistent with the examples.…”
Section: Experimental Comparisonmentioning
confidence: 99%
“…Scenarios can be provided in various forms, e.g. message sequence charts [5], event sequence charts [24], or simply, input-output examples [47]. Requirements can be temporal logic formulas as in [5,47], or other types of constraints such as the scenario constraints used in [24].…”
Section: Introductionmentioning
confidence: 99%