Effective Development and Verification of Railway Control Software

Publication: ResearchReport – Annual report year: 2011

Standard

Effective Development and Verification of Railway Control Software. / Haxthausen, Anne Elisabeth.

2011.

Publication: ResearchReport – Annual report year: 2011

Harvard

APA

CBE

MLA

Vancouver

Author

Haxthausen, Anne Elisabeth / Effective Development and Verification of Railway Control Software.

2011.

Publication: ResearchReport – Annual report year: 2011

Bibtex

@book{ae27566dba1b4cca856d0f0b09a0480b,
title = "Effective Development and Verification of Railway Control Software",
author = "Haxthausen, {Anne Elisabeth}",
note = "This document is a delivery to Rail Net Denmark (Banedanmark) as a part of the Public Sector Consultancy service offered by the Technical University of Denmark.",
year = "2011",

}

RIS

TY - RPRT

T1 - Effective Development and Verification of Railway Control Software

A1 - Haxthausen,Anne Elisabeth

AU - Haxthausen,Anne Elisabeth

PY - 2011

Y1 - 2011

N2 - This document presents a method for effective development of software for a product line of similar railway control systems. The software is constructed in three steps: first a specifications in a domain-specific language is created, then a formal behavioural controller model is automatically created from the specification, and finally the model is compiled into executable object code. Formal verification is performed automatically by tools at three levels: (1) the specification is checked to follow the rules of the domain, (2) the controller model is checked to ensure safety, and (3) the object code is verified to be a correct implementation of the controller model.

AB - This document presents a method for effective development of software for a product line of similar railway control systems. The software is constructed in three steps: first a specifications in a domain-specific language is created, then a formal behavioural controller model is automatically created from the specification, and finally the model is compiled into executable object code. Formal verification is performed automatically by tools at three levels: (1) the specification is checked to follow the rules of the domain, (2) the controller model is checked to ensure safety, and (3) the object code is verified to be a correct implementation of the controller model.

BT - Effective Development and Verification of Railway Control Software

ER -