Graph based verification of software evolution requirements

Ciraci, Selim

doi:10.3990/1.9789036529563

Cited by 10 publications

(14 citation statements)

References 92 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Case studies conducted with the industry (Ciraci, 2009) show that it is hard to reformulate requirements as LTL/CTL formulas. Domain-specific languages can be used to specify requirements of certain type that allow generation of LTL/CTL formulas (Ciraci, 2009).…”

Section: Expressing Requirements In Logicmentioning

confidence: 99%

Generation and validation of traces between requirements and architecture based on formal trace semantics

Göknil

Kurtev²,

Berg

2014

Journal of Systems and Software

View full text Add to dashboard Cite

Please cite this article in press as: Goknil, A., et al., Generation and validation of traces between requirements and architecture based on formal trace semantics. J. Syst. Software (2013) The size and complexity of software systems make integration of the new/modified requirements to the software system costly and time consuming. The impact of requirements changes on other requirements, design elements and source code should be traced to determine parts of the software to be changed. Considerable research has been devoted to relating requirements and design artifacts with source code. Less attention has been paid to relating requirements (R) with architecture (A) by using well-defined semantics of traces. Traces between R&A might be manually assigned. This is time-consuming, and error prone. Traces might be incomplete and invalid. In this paper, we present an approach for automatic trace generation and validation of traces between requirements (R) and architecture (A). Requirements relations and architecture verification techniques are used. A trace metamodel is defined with commonly used trace types between R&A. We use the semantics of traces and requirements relations for generating and validating traces with a tool support. The tool provides the following: (1) generation and validation of traces by using requirements relations and/or verification of architecture, (2) generation and validation of requirements relations by using traces. The tool is based on model transformation in ATL and termrewriting logic in Maude.

show abstract

Section: Expressing Requirements In Logicmentioning

confidence: 99%

Generation and validation of traces between requirements and architecture based on formal trace semantics

Göknil

Kurtev²,

Berg

2014

Journal of Systems and Software

View full text Add to dashboard Cite

show abstract

“…In such a process, the software architect can gradually improve the quality of the traces and the requirements. Case studies conducted with the industry [5] shows that LTL/CTL is hard to reformulate and check requirements in the architecture. Domain-specific languages can be used for requirements of certain type that allow compilation of LTL/CTL formulas [5].…”

Section: Discussionmentioning

confidence: 99%

“…Case studies conducted with the industry [5] shows that LTL/CTL is hard to reformulate and check requirements in the architecture. Domain-specific languages can be used for requirements of certain type that allow compilation of LTL/CTL formulas [5]. Starting from natural language text, Semantics Business Vocabulary and Rules (SBVR) [25] can support reformulation requirements in terms of LTL/CTL formulas.…”

Section: Discussionmentioning

confidence: 99%

Tool support for generation and validation of traces between requirements and architecture

Göknil

Kurtev

Berg

2010

Proceedings of the 6th ECMFA Traceability Workshop

View full text Add to dashboard Cite

Traceability is considered crucial for establishing and maintaining consistency between software development artifacts. Although considerable research has been devoted to relating requirements and design artifacts with source code, less attention has been paid to relating requirements with architecture by using well-defined semantics of traces. We present a tool that provides trace establishment by using semantics of traces between R&A (Requirements and Architecture). The tool provides the following: (1) generation/validation of traces by using requirements relations and/or verification of architecture, (2) generation/validation of requirements relations by using traces. The tool uses the semantics of traces together with requirements relations and verification results for generating and validating traces. It is based on model transformations in ATL and term-rewriting logic in Maude.

show abstract

“…For both experiments, we conducted formal statistical analysis; interested readers on the analysis are referred to the thesis published about this work (Ciraci, 2009). These analysis yielded a significance value that is lower than the aimed significance value (p = 0.007 < p a imed = 0.05) showing that the experiment results of tool supported group and the manual evaluation group in both experiments is significantly different.…”

Section: Experiments With Studentsmentioning

confidence: 99%

Verifying Runtime Reconfiguration Requirements on UML Models

Ciraci

Broek

Akşit

2010

Views on Evolvability of Embedded Systems

Self Cite

View full text Add to dashboard Cite

Runtime reconfiguration is a method used for changing the structure and the call pattern such that the software can adapt itself to the client's computing environment. The current practice of verifying software models with respect to the reconfiguration requirements is rather subjective: based on the stakeholders' needs, architects define a set of reconfiguration scenarios and manually trace the models. This chapter presents a novel process and a tool for automating the verification of the UML class and sequence diagrams with respect to runtime reconfiguration requirements. In this process, the models are simulated, which generates the execution tree. In the execution tree, each path from root to a leaf node is an execution sequence. The branching in this tree is caused by the reconfiguration of the structure and the call pattern. The runtime reconfiguration requirements are expressed with a visual state-based language which is verified against the execution tree. If the verification fails, feedback about the possible location of the problem is presented to the designers. The process has been tested with case studies and experiments conducted on the UML class and sequence diagrams of a software system from Philips Healthcare MRI.

show abstract

Graph based verification of software evolution requirements

Cited by 10 publications

References 92 publications

Generation and validation of traces between requirements and architecture based on formal trace semantics

Generation and validation of traces between requirements and architecture based on formal trace semantics

Tool support for generation and validation of traces between requirements and architecture

Verifying Runtime Reconfiguration Requirements on UML Models

Contact Info

Product

Resources

About