Change search
CiteExportLink to record
Permanent link

Direct link
Cite
Citation style
  • apa
  • harvard1
  • ieee
  • modern-language-association-8th-edition
  • vancouver
  • Other style
More styles
Language
  • de-DE
  • en-GB
  • en-US
  • fi-FI
  • nn-NO
  • nn-NB
  • sv-SE
  • Other locale
More languages
Output format
  • html
  • text
  • asciidoc
  • rtf
Safety Practices in Requirements Engineering: The Uni-REPM Safety Module
Universidade Federal do Ceara, BRA.
Universidade Federal de Pernambuco, BRA.
Universidade Federal de Sao Paulo, BRA.
Blekinge Institute of Technology, Faculty of Computing, Department of Software Engineering.
2018 (English)In: IEEE Transactions on Software Engineering, ISSN 0098-5589, E-ISSN 1939-3520Article in journal (Refereed) Epub ahead of print
Abstract [en]

Context: Software is an important part in safety- critical system (SCS) development since it is becoming a major source of hazards. Requirements-related hazards have been as- sociated with many accidents and safety incidents. Requirements issues tend to be mitigated in companies with high processes maturity levels since they do their business in a systematic, consistent and proactive approach. However, requirements en- gineers need systematic guidance to consider safety concerns early in the development process. Goal: the paper investigates which safety practices are suitable to be used in the Requirements Engineering (RE) process for SCS and how to design a safety maturity model for this area. Method: we followed the design science methodology to propose Uni-REPM SCS, a safety module for Unified Requirements Engineering Process Maturity Model (Uni-REPM). We also conducted a static validation with two practitioners and nine academic experts to evaluate its coverage, correctness, usefulness and applicability. Results: The module has seven main processes, fourteen sub-processes and 148 practices that form the basis of safety processes maturity. Moreover, we describe its usage through a tool. Conclusions: The validation indicates a good coverage of practices and well receptivity by the experts. Finally, the module can help companies in evaluating their current practices. IEEE

Place, publisher, year, edition, pages
Institute of Electrical and Electronics Engineers Inc. , 2018.
Keywords [en]
Capability maturity model, Companies, Maturity Models, Requirements engineering, Safety, Safety Engineering, Safety-critical systems, Software, Standards, Systematics, Uni-REPM, Accident prevention, Computer software, Hazards, Industry, Security systems, Software engineering, Capability maturity models, Maturity model, Safety critical systems
National Category
Software Engineering
Identifiers
URN: urn:nbn:se:bth-16642DOI: 10.1109/TSE.2018.2846576Scopus ID: 2-s2.0-85048550515OAI: oai:DiVA.org:bth-16642DiVA, id: diva2:1228533
Available from: 2018-06-28 Created: 2018-06-28 Last updated: 2018-06-29Bibliographically approved

Open Access in DiVA

No full text in DiVA

Other links

Publisher's full textScopus

Authority records BETA

Gorschek, Tony

Search in DiVA

By author/editor
Gorschek, Tony
By organisation
Department of Software Engineering
In the same journal
IEEE Transactions on Software Engineering
Software Engineering

Search outside of DiVA

GoogleGoogle Scholar

doi
urn-nbn

Altmetric score

doi
urn-nbn
Total: 18 hits
CiteExportLink to record
Permanent link

Direct link
Cite
Citation style
  • apa
  • harvard1
  • ieee
  • modern-language-association-8th-edition
  • vancouver
  • Other style
More styles
Language
  • de-DE
  • en-GB
  • en-US
  • fi-FI
  • nn-NO
  • nn-NB
  • sv-SE
  • Other locale
More languages
Output format
  • html
  • text
  • asciidoc
  • rtf