Compositional Reasoning in Model-Based Verification of Adaptive Embedded Systems

Schaefer, Ina; Poetzsch-Heffter, Arnd

doi:10.1109/sefm.2008.16

Cited by 6 publications

(3 citation statements)

References 23 publications

(35 reference statements)

Supporting

Mentioning

Contrasting

Order By: Relevance

“…In order to make them more complete they are passed through verification cycle. Verification cycle starts from the scheduling step in which arbitrator guarantees that the item is primed for examination, chooses the scrutiny group and appoints roles, plans the meeting place and time, and guarantees the conveyance of examination materials [18]. The next phase outline is a non-compulsory phase that is planned if the scrutiny group is not acquainted with the material being analyzed and its experience.…”

Section: A Designing a Frameworkmentioning

confidence: 99%

A process improvement in requirement verification and validation using ontology

Nazir

Motla

Abbas

et al. 2014

Asia-Pacific World Congress on Computer Science and Engineering

View full text Add to dashboard Cite

The success of software projects depends on fully conveyed requirements. Contribution of stakeholders contributing in software requirements have a place with distinctive domains, because of which ambiguities, inconsistencies might arise moreover giving rise to incorrectness. Many tools are available for software requirements verification and validation but the issue of stakeholders belonging to different domains is still under consideration. As these requirements are not understood properly, it causes schedule delay and greater cost in the last stages of software. Requirements verification and validation are the most vital activities in requirement engineering that guarantees software quality and has an extraordinary impact on software cost and its success. The requirements verification and validation are an affirmation that the product requirements record is free of unwanted requirements and totally reliable. Keeping in mind the end goal of removing conflict, recognizing failures and making the product requirements document completely useful is the key component. So these requirements should be appropriately confirmed and accepted by the clients before conveying to the development team. Thus, ontology might be picked as an answer for checking and approving the requirements among stakeholders of distinctive domains. In this study improving requirement verification and validation process through ontology. We have used expert reviews and case study to evaluate the developed ontology that indicates different concepts, properties and constraints in the process of requirement verification and validation. With the help of the developed ontology, it is shown that its use for requirement verification and validation shows improvement in consistency, applicability and other factors.

show abstract

Section: A Designing a Frameworkmentioning

confidence: 99%

A process improvement in requirement verification and validation using ontology

Nazir

Motla

Abbas

et al. 2014

Asia-Pacific World Congress on Computer Science and Engineering

View full text Add to dashboard Cite

show abstract

“…[21]. Other software verification and validation (V & V) techniques appear in [14,24,27,30,32]. Popular trends in requirements elicitation favour an active participation of all stakeholders in the process.…”

Section: Stakeholder Expectationsmentioning

confidence: 99%

A four-way framework for validating a specification

Dongmo

Poll

2010

Proceedings of the 2010 Annual Research Conference of the South African Institute of Computer Scientists and Information Techno

View full text Add to dashboard Cite

The validation of a software specification may be viewed as a function of what the specification is to be used for and any comprehensive validation exercise needs to address possibly conflicting requirements. In this paper we develop a framework which embodies a 4-way validation strategy to develop and measure a specification against requirements from users, the application domain, restrictions in the notation and language and finally the operational system, obtained through appropriate refinement. Our framework is modelled on Boehm's spiral model and at each iteration of the spiral, the specification is validated in line with the evolving requirements of each of the above four aspects. The process continues until convergence is reached and no further amendments are made to the specification during a subsequent iteration. For each of the four aspects, a sequence of processes is defined to facilitate the validation of the specification from the viewpoint presented by the relevant aspect. The utility of our framework is illustrated through a case study in Object Z.

show abstract

“…There are other model based tools for embedded control with verification abilities integrated, e.g., [18], but verifying fault-tolerance mechanisms is not their primary focus. Also we find in most cases, the deployment from the model is synchronous, where FTOS is focusing on the deployment over either synchronous or asynchronous systems.…”

Section: Related Workmentioning

confidence: 99%

FTOS-Verify: Analysis and Verification of Non-Functional Properties for Fault-Tolerant Systems

Cheng,

Buckl,

Esparza

et al. 2009

Preprint

View full text Add to dashboard Cite

The focus of the tool FTOS is to alleviate designers' burden by offering code generation for non-functional aspects including fault-tolerance mechanisms. One crucial aspect in this context is to ensure that user-selected mechanisms for the system model are sufficient to resist faults as specified in the underlying fault hypothesis. In this paper, formal approaches in verification are proposed to assist the claim. We first raise the precision of FTOS into pure mathematical constructs, and formulate the deterministic assumption, which is necessary as an extension of Giotto-like systems (e.g., FTOS) to equip with fault-tolerance abilities. We show that local properties of a system with the deterministic assumption will be preserved in a modified synchronous system used as the verification model. This enables the use of techniques known from hardware verification. As for implementation, we develop a prototype tool called FTOS-Verify, deploy it as an Eclipse add-on for FTOS, and conduct several case studies.

show abstract

Compositional Reasoning in Model-Based Verification of Adaptive Embedded Systems

Cited by 6 publications

References 23 publications

A process improvement in requirement verification and validation using ontology

A process improvement in requirement verification and validation using ontology

A four-way framework for validating a specification

FTOS-Verify: Analysis and Verification of Non-Functional Properties for Fault-Tolerant Systems

Contact Info

Product

Resources

About