Elaborating Requirements Using Model Checking and Inductive Learning

Alrajeh, Dalal; Kramer, Jeff; Russo, Alessandra; Uchitel, Sebastián

doi:10.1109/tse.2012.41

Cited by 26 publications

(35 citation statements)

References 35 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Several authors have proposed using logic programming to reason about software behaviour described in other formalisms [1,2,25].…”

Section: Conclusion and Related And Future Workmentioning

confidence: 99%

“…In recent years researchers in software engineering have responded to this by deploying a combination of verification and machine learning techniques to improve software specifications. For example, in [1] the authors describe a method for incrementally refining a consistent specification, expressed in first-order temporal logic, with respect to some given property using an integration of model checking and Inductive Logic Programming (ILP). In [2], the authors give a method for revising temporal specifications that may be incorrect or inconsistent using model checking and artificial neural networks.…”

Section: Introductionmentioning

confidence: 99%

See 1 more Smart Citation

Automated Error-Detection and Repair for Compositional Software Specifications

Alrajeh

Craven

2014

Software Engineering and Formal Methods

Self Cite

View full text Add to dashboard Cite

Abstract. The complexity of error diagnosis in requirements specifications, already high, is increased when requirements refer to various system components, on whose interaction the system's aims depend. Further, finding causes of error, and ways of overcoming them, cannot easily be achieved without a systematic methodology. This has led researchers to explore the combined use of verification and machine-learning to support automated software analysis and repair. However, existing approaches have been limited by using formalisms in which modularity and compositionality cannot be explicitly expressed. In this paper we overcome this limitation. We define a translation from a representative process algebra, Finite State Processes, into the action language C+. This enables forms of verification not supported by previous methods. We then use a logicprogramming equivalent of C+, to which we apply inductive logic programming for learning repairs to system components while ensuring no new errors are introduced and interactions with other components are maintained. These two phases are iterated until a correct specification is reached, enabling rigorous and scalable support for automated analysis and repair of component-based specifications.

show abstract

“…Several authors have proposed using logic programming to reason about software behaviour described in other formalisms [1,2,25].…”

Section: Conclusion and Related And Future Workmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

Automated Error-Detection and Repair for Compositional Software Specifications

Alrajeh

Craven

2014

Software Engineering and Formal Methods

Self Cite

View full text Add to dashboard Cite

show abstract

“…The specification notations used early in a system's life cycle, such as FLTL properties [8], triggered scenarios [19], and event invariants [2], are intuitive and inherently partial, focusing on narrow aspects of the system's behavior. For example, a scenario describes a single required sequence of interactions between the system's components, whereas a safety property proscribes some system behavior as illegal.…”

Section: Introductionmentioning

confidence: 99%

“…To avoid errors and to support requirements elicitation, the above, inherently partial requirements should ideally be supported with techniques that help (1) to detect the inconsistencies between the individual requirements, (2) to validate and verify the overall system behavior, and (3) to explore the currently underspecified behaviors. To this end, researchers have proposed synthesizing a system's partial behavior model [6], [7], [11], [12], [18], [19], [22], represented using an FSA-based formalism such as modal transition systems (MTS) [14], from the system requirements.…”

Section: Introductionmentioning

confidence: 99%

See 1 more Smart Citation

Distributing refinements of a system-level partial behavior model

Krka

Medvidović

2013

2013 21st IEEE International Requirements Engineering Conference (RE)

View full text Add to dashboard Cite

Abstract-Early in a system's life cycle, a system's behavior is typically partially specified using scenarios, invariants, and temporal properties. These specifications prohibit or require certain behaviors, while leaving other behaviors uncategorized into either of those. Engineers refine the specification by eliciting more requirements to finally arrive at a complete behavioral description. Partial-behavior models have been utilized to compactly capture, analyze, and elaborate the partial system specification. Under the current practices, software systems are reasoned about and their behavior specified exclusively at the system level, disregarding of the fact that a system typically consists of interacting components. However, exclusively refining a behavior specification at the system-level runs the risk of arriving at an inconsistent specification, i.e. one that is not realizable as a composition of the system's components. To address this problem, we propose a framework that provides the lacking support: when a system's partial behavior model is refined in accordance with a new requirement, our framework distributes the refinement to the components' models and ensures overall consistency. We discuss the framework's soundness and correctness, and demonstrate its features on a case study previously used in related literature.

show abstract

CiMPG+F: A Proof Generator and Fixer-Upper for CafeOBJ Specifications

Riesco

Ogata

2020

Lecture Notes in Computer Science

View full text Add to dashboard Cite

Elaborating Requirements Using Model Checking and Inductive Learning

Cited by 26 publications

References 35 publications

Automated Error-Detection and Repair for Compositional Software Specifications

Automated Error-Detection and Repair for Compositional Software Specifications

Distributing refinements of a system-level partial behavior model

CiMPG+F: A Proof Generator and Fixer-Upper for CafeOBJ Specifications

Contact Info

Product

Resources

About