1. bookVolume 116 (2019): Issue 1 (January 2019)
Journal Details
License
Format
Journal
eISSN
2353-737X
First Published
20 May 2020
Publication timeframe
1 time per year
Languages
English
access type Open Access

Engineering Safety- and Security-Related Quality Requirements

Published Online: 16 May 2020
Volume & Issue: Volume 116 (2019) - Issue 1 (January 2019)
Page range: 231 - 235
Received: 21 Dec 2018
Journal Details
License
Format
Journal
eISSN
2353-737X
First Published
20 May 2020
Publication timeframe
1 time per year
Languages
English
Abstract

Safety- and security-related problems for software intensive systems are often due to poor or missing relevant engineering requirements. Although there is nothing really new in our presentation, specified problems and methods are well worth revisiting because they are still far from being widely recognized and put into industrial practice.

Keywords

[1] Nuseibeh B., Easterbrook S., Requirements engineering: A roadmap, [in:] Proc. Conf. ICSE ’00 The Future of Software Engineering, ACM New York, 2000, 35–46.10.1145/336512.336523Search in Google Scholar

[2] Zave P., Classification of research efforts in requirements engineering, “ACM Computing Surveys”, Vol. 29(4)/1997, 315–321.10.1145/267580.267581Search in Google Scholar

[3] Boehm B., Papaccio P., Understanding and controlling software costs, “IEEE Transactions on Software Engineering”, Vol. 14(10)/1988, 1462–1477.10.1109/32.6191Search in Google Scholar

[4] Mellado D., Blanco C., Sánchez L., Fernández-Medina E., A systematic review of security requirements engineering, “Computer Standards & Interfaces”, Vol. 32(4)/2010, 153–165.10.1016/j.csi.2010.01.006Search in Google Scholar

[5] Firesmith D., Common concepts underlying safety, security, and survivability engineering, Technical Note CMU/SEI-2003-TN-033, Carnegie Mellon University 2003.10.21236/ADA421683Search in Google Scholar

[6] Firesmith D., Engineering safety- and security-related requirements for software-intensive systems, [in:] Proc. ICSE’10 32nd ACM/IEEE Int. Conf. on Software Engineering, Vol. 2, 2010, 489–490.10.1145/1810295.1810444Search in Google Scholar

[7] Brooks F., No silver bullet – essence and accident in software engineering, “IEEE Computer”, Vol. 20(4)/1987, 10–19.10.1109/MC.1987.1663532Search in Google Scholar

[8] Firesmith, D., Specifying good requirements, “Journal of Object Technology”, Vol. 2(4)/2003, 77–87.10.5381/jot.2003.2.4.c7Search in Google Scholar

[9] Firesmith, D., Using quality models to engineer quality requirements, “Journal of Object Technology”, Vol. 2(5)/2003, 67–75.10.5381/jot.2003.2.5.c6Search in Google Scholar

[10] Firesmith, D., Engineering safety requirements, safety constraints, and safety-critical requirements, “Journal of Object Technology”, Vol. 3(3)/2004, 27–42.10.5381/jot.2004.3.3.c3Search in Google Scholar

[11] Firesmith D., Are your requirements complete?, “Journal of Object Technology”, Vol. 4(1)/2005, 27–43.10.5381/jot.2005.4.1.c3Search in Google Scholar

[12] Firesmith D., Common requirements problems, their negative consequences, and industry best practices to help solve them, “Journal of Object Technology”, Vol. 6(1)/2007, 17–33.10.5381/jot.2007.6.1.c2Search in Google Scholar

[13] Vilela J., Castro J., Martins L., Gorschek T., Integration between requirements engineering and safety analysis: A systematic literature review, “The Journal of Systems and Software”, Vol. 125/2017, 68–92.10.1016/j.jss.2016.11.031Search in Google Scholar

Recommended articles from Trend MD

Plan your remote conference with Sciendo