Home > Research > Publications & Outputs > Integrating safety analysis and requirements en...

Research

Links

Text available via DOI:

View graph of relations

Integrating safety analysis and requirements engineering

Research output: Contribution in Book/Report/Proceedings - With ISBN/ISSN › Conference contribution/Paper › peer-review

Published

Standard

Integrating safety analysis and requirements engineering. / Kotonya, G.; Sommerville, I.
APSEC '97: Proceedings of the Fourth Asia-Pacific Software Engineering and International Computer Science Conference. Washington, DC, USA: IEEE Computer Society, 1997. p. 259-271.

Research output: Contribution in Book/Report/Proceedings - With ISBN/ISSN › Conference contribution/Paper › peer-review

Harvard

Kotonya, G & Sommerville, I 1997, Integrating safety analysis and requirements engineering. in APSEC '97: Proceedings of the Fourth Asia-Pacific Software Engineering and International Computer Science Conference. IEEE Computer Society, Washington, DC, USA, pp. 259-271. https://doi.org/10.1109/APSEC.1997.640183

APA

Kotonya, G., & Sommerville, I. (1997). Integrating safety analysis and requirements engineering. In APSEC '97: Proceedings of the Fourth Asia-Pacific Software Engineering and International Computer Science Conference (pp. 259-271). IEEE Computer Society. https://doi.org/10.1109/APSEC.1997.640183

Vancouver

Kotonya G, Sommerville I. Integrating safety analysis and requirements engineering. In APSEC '97: Proceedings of the Fourth Asia-Pacific Software Engineering and International Computer Science Conference. Washington, DC, USA: IEEE Computer Society. 1997. p. 259-271 doi: 10.1109/APSEC.1997.640183

Author

Kotonya, G. ; Sommerville, I. / Integrating safety analysis and requirements engineering. APSEC '97: Proceedings of the Fourth Asia-Pacific Software Engineering and International Computer Science Conference. Washington, DC, USA : IEEE Computer Society, 1997. pp. 259-271

Bibtex

@inproceedings{4728b6ede7f84315a344359e066f127b,
title = "Integrating safety analysis and requirements engineering",
abstract = "Some systems failures are due to defects in manufacturing and design, however that there are a significant number of system failures which result from errors, omissions and inconsistencies in the system requirements. We thus need methods to support a `safe' requirements engineering process whose objectives are to specify system requirements such that system states which compromise safety are avoided and to include, along with the requirements, a justification or safety case which explains why the specified system is indeed safe. This paper describes the extension of a viewpoint-based requirements method to incorporate safety analysis.",
author = "G. Kotonya and I. Sommerville",
year = "1997",
doi = "10.1109/APSEC.1997.640183",
language = "English",
isbn = "0-8186-8271-X",
pages = "259--271",
booktitle = "APSEC '97: Proceedings of the Fourth Asia-Pacific Software Engineering and International Computer Science Conference",
publisher = "IEEE Computer Society",

}

RIS

TY - GEN

T1 - Integrating safety analysis and requirements engineering

AU - Kotonya, G.

AU - Sommerville, I.

PY - 1997

Y1 - 1997

N2 - Some systems failures are due to defects in manufacturing and design, however that there are a significant number of system failures which result from errors, omissions and inconsistencies in the system requirements. We thus need methods to support a `safe' requirements engineering process whose objectives are to specify system requirements such that system states which compromise safety are avoided and to include, along with the requirements, a justification or safety case which explains why the specified system is indeed safe. This paper describes the extension of a viewpoint-based requirements method to incorporate safety analysis.

AB - Some systems failures are due to defects in manufacturing and design, however that there are a significant number of system failures which result from errors, omissions and inconsistencies in the system requirements. We thus need methods to support a `safe' requirements engineering process whose objectives are to specify system requirements such that system states which compromise safety are avoided and to include, along with the requirements, a justification or safety case which explains why the specified system is indeed safe. This paper describes the extension of a viewpoint-based requirements method to incorporate safety analysis.

U2 - 10.1109/APSEC.1997.640183

DO - 10.1109/APSEC.1997.640183

M3 - Conference contribution/Paper

SN - 0-8186-8271-X

SP - 259

EP - 271

BT - APSEC '97: Proceedings of the Fourth Asia-Pacific Software Engineering and International Computer Science Conference

PB - IEEE Computer Society

CY - Washington, DC, USA

ER -