Models are increasingly recognized as an effective means for elaborating requirements and exploring designs. For complex systems, model building is far from an easy task. Efforts were therefore recently made to automate parts of this process, notably, by synthesizing behavior models from scenarios of interactions between the software-to-be and its environment. In particular, our previous interactive synthesizer generates labelled transition systems (LTS) from simple message sequence charts (MSC) provided by end-users. Compared with others, the synthesizer requires no additional input such as state or flowcharting information. User interactions consist in simple scenarios generated by the synthesizer that the user has to classify as example ...
Synthesis of operational behaviour models from scenario-based specifications has been extensively st...
The requirements analysis, modeling, and simulation have consistently been one of the main challenge...
peer-reviewedEarly system requirements are often captured by declarative and property-based artifact...
Models are increasingly recognized as an effective means for elaborating requirements and exploring ...
Requirements-related scenarios capture typical examples of system behaviors through sequences of des...
Abstract — Requirements-related scenarios capture typical examples of system behaviors through seque...
Models play a significant role for analyzing requirements and exploring designs of software systems....
Synthesis of behaviour models from software development artifacts such as scenario-based description...
There are many examples in the literature of algorithms for synthesizing state machines from scenari...
Abstract—Scenario-based specifications such as Message Sequence Charts (MSCs) are useful as part of ...
Triggered scenarios are sequence charts that represent interactions between the system agents’. Grap...
Early system requirements are often captured by declarative and property-based artifacts, such as sc...
peer-reviewedEarly system requirements are often captured by declarative and property-based artefact...
Several scenario description languages and associated behaviour synthesis processes have been develo...
Abstract. Constructing a program from a specification is a long-known general and fundamental proble...
Synthesis of operational behaviour models from scenario-based specifications has been extensively st...
The requirements analysis, modeling, and simulation have consistently been one of the main challenge...
peer-reviewedEarly system requirements are often captured by declarative and property-based artifact...
Models are increasingly recognized as an effective means for elaborating requirements and exploring ...
Requirements-related scenarios capture typical examples of system behaviors through sequences of des...
Abstract — Requirements-related scenarios capture typical examples of system behaviors through seque...
Models play a significant role for analyzing requirements and exploring designs of software systems....
Synthesis of behaviour models from software development artifacts such as scenario-based description...
There are many examples in the literature of algorithms for synthesizing state machines from scenari...
Abstract—Scenario-based specifications such as Message Sequence Charts (MSCs) are useful as part of ...
Triggered scenarios are sequence charts that represent interactions between the system agents’. Grap...
Early system requirements are often captured by declarative and property-based artifacts, such as sc...
peer-reviewedEarly system requirements are often captured by declarative and property-based artefact...
Several scenario description languages and associated behaviour synthesis processes have been develo...
Abstract. Constructing a program from a specification is a long-known general and fundamental proble...
Synthesis of operational behaviour models from scenario-based specifications has been extensively st...
The requirements analysis, modeling, and simulation have consistently been one of the main challenge...
peer-reviewedEarly system requirements are often captured by declarative and property-based artifact...