Nothing Special   »   [go: up one dir, main page]

skip to main content
article

A SysML-based approach to traceability management and design slicing in support of safety certification: Framework, tool support, and case studies

Published: 01 June 2012 Publication History

Abstract

Context: Traceability is one of the basic tenets of all safety standards and a key prerequisite for software safety certification. In the current state of practice, there is often a significant traceability gap between safety requirements and software design. Poor traceability, in addition to being a non-compliance issue on its own, makes it difficult to determine whether the design fulfills the safety requirements, mainly because the design aspects related to safety cannot be clearly identified. Objective: The goal of this article is to develop a framework for specifying and automatically extracting design aspects relevant to safety requirements. This goal is realized through the combination of two components: (1) A methodology for establishing traceability between safety requirements and design, and (2) an algorithm that can extract for any given safety requirement a minimized fragment (slice) of the design that is sound, and yet easy to understand and inspect. Method: We ground our framework on System Modeling Language (SysML). The framework includes a traceability information model, a methodology to establish traceability, and mechanisms for model slicing based on the recorded traceability information. The framework is implemented in a tool, named SafeSlice. Results: We prove that our slicing algorithm is sound for temporal safety properties, and argue about the completeness of slices based on our practical experience. We report on the lessons learned from applying our approach to two case studies, one benchmark and one industrial case. Both studies indicate that our approach substantially reduces the amount of information that needs to be inspected for ensuring that a given (behavioral) safety requirement is met by the design.

References

[1]
Functional safety of electrical/electronic/programmable electronic safety-related systems (IEC 61508), International Electrotechnical Commission: International Electrotechnical Commission, 2005.
[2]
DO-178B - software considerations in airborne systems and equipment certification, Radio Technical Commission for Aeronautics (RTCA) Inc., 1992.
[3]
Road vehicles - functional safety, ISO draft standard, 2009.
[4]
J. Holt, S. Perry, SysML for systems engineering: Institute of Engineering and Technology, 2008.
[5]
International Council on Systems Engineering, <http://www.incose.org/>.
[6]
D. Falessi, S. Nejati, M. Sabetzadeh, L. Briand, A. Messina, Safeslice: a model slicing and design safety inspection tool for sysml, in: SIGSOFT FSE, 2011, pp. 460-463.
[7]
M. Sabetzadeh, S. Nejati, L. Briand, A. Evensen Mills, Using SysML for modeling of safety-critical software-hardware interfaces: guidelines and industry experience, in: HASE, 2011, pp. 193-201.
[8]
W. Schafer, H. Wehrheim, The challenges of building advanced mechatronic systems, in: FOSE '07, 2007, pp. 72-84.
[9]
OMG Systems Modeling Language (OMG SysML), Object Management Group (OMG), version 1.1., 2008. <http://www.omg.org/docs/formal/08-11-02.pdf>.
[10]
Friedenthal, S., Moore, A. and Steiner, R., A Practical Guide to SysML: The Systems Modeling Language. 2008. Morgan Kaufman.
[11]
Survey of model-based systems engineering (MBSE) methodologies, INCOSE Survey, 2008.
[12]
. In: Lewerentz, C., Lindner, T. (Eds.), LNCS, vol. 891. Springer.
[13]
Gomaa, H., Designing Concurrent, Distributed, and Real-Time Applications with UML. 2000. Addison-Wesley.
[14]
Bruegge, B. and Dutoit, A., Object-Oriented Software Engineering - Using UML, Patterns and Java. 2009. third ed. Prentice Hall.
[15]
L. Briand, T. Coq, T. Klykken, S. Nejati, R. Panesar-Walawege, M.Sabetzadeh., Using SysML to support safety certification: a methodology and case study. Tech. Rep. 2, SRL-DNV, December 2009, 92 pp. <http://vefur.simula.no/shiva/report2.pdf>.
[16]
T. Klykken, A case study using SysML for safety-critical systems, Ph.D. thesis, University of Oslo, 2009. <http://vefur.simula.no/shiva/tonje.pdf>.
[17]
Jackson, D. and Thomas, M., Software for Dependable Systems: Sufficient Evidence?. 2007. National Academy Press.
[18]
van Lamsweerde, A., Requirements Engineering: From System Goals to UML Models to Software Specifications. 2009. Wiley.
[19]
Harel, D. and Marelly, R., Specifying and executing behavioral requirements: the play-in/play-out approach. Software and System Modeling. v2 i2. 82-107.
[20]
Ericson, C., Hazard Analysis Techniques for System Safety. 2005. John Wiley & Sons.
[21]
Reliability study of complex physical systems using SysML. Reliability Engineering & System Safety. v95 i4. 431-450.
[22]
K. Androutsopoulos, D. Clark, M. Harman, Z. Li, L. Tratt, Control dependence for extended finite state machines, in: FASE, 2009, pp. 216-230.
[23]
M. Abadi, L. Lamport, The existence of refinement mappings, in: LICS, 1988, pp. 165-175.
[24]
Clarke, E., Grumberg, O. and Peled, D., Model Checking. 1999. MIT Press.
[25]
S. Barbey, C. Peraire, D. Buchs, A case study for testing object-oriented software: a production cell, 1998.
[26]
Bazzana, G., Brigliadori, R., Cole, R., Kirkwood, K. and Seigneur, F., Techniques and tools for software assessment and certification. Annual Review in Automatic Programming. v16 iPart 2. 153-160.
[27]
Juristo Juzgado, N. and Morant, J., Common framework for the evaluation process of kbs and conventional software. Knowledge-Based Systems. v11 i2. 145-159.
[28]
Task-directed software inspection. Journal of Systems and Software. v73. 361-368.
[29]
Cleland-Huang, J., Berenbach, B., Clark, S., Settimi, R. and Romanova, E., Best practices for automated traceability. IEEE Computer. v40 i6. 27-35.
[30]
A. Egyed, A scenario-driven approach to traceability, in: ICSE, 2001, pp. 123-132.
[31]
Jirapanthong, W. and Zisman, A., XTraQue: traceability for product line systems. Software and System Modeling. v8 i1. 117-144.
[32]
Ramesh, B. and Jarke, M., Toward reference models for requirements traceability. IEEE TSE. v27 i1. 58-93.
[33]
R.K. Panesar-Walawege, M. Sabetzadeh, L. Briand, T. Coq, Characterizing the chain of evidence for software safety cases: a conceptual model based on the IEC 61508 standard, in: ICST, 2010, pp. 335-344.
[34]
P. Mader, O. Gotel, I. Philippow, Getting back to basics: promoting the use of a traceability information model in practice, in: IEEE TEFSE '09: ICSE09 Wrkshp, 2009, pp. 21-25.
[35]
Software Change Impact Analysis. 1996. IEEE Computer Society.
[36]
Briand, L., Labiche, Y. and Yue, T., Automated traceability analysis for uml model refinements. Information & Software Technology. v51 i2. 512-527.
[37]
D. ten Hove, A. Göknil, I. Kurtev, K. van den Berg, K. de Goede, Change impact analysis for sysml requirements models based on semantics of trace relations, in: Proceedings of the ECMDA Traceability Workshop (ECMDA-TW), 2009, pp. 17-28.
[38]
M. Weiser, Program slicing, in: Proceedings of the 5th International Conference on Software Engineering (ICSE'81), 1981, pp. 439-449.
[39]
F. Tip, A survey of program slicing techniques, Tech. rep., Amsterdam, The Netherlands, 1994.
[40]
Binkley, D. and Gallagher, K., Program slicing. Advances in Computers. 1-50.
[41]
B. Korel, I. Singh, L. Ho Tahat, B. Vaysburg, Slicing of state-based models, in: 19th International Conference on Software Maintenance (ICSM'03), 2003, pp. 34-43.
[42]
H. Kagdi, J. Maletic, A. Sutton, Context-free slicing of uml class models, in: 21st IEEE International Conference on Software Maintenance (ICSM'05), 2005, pp. 635-638.
[43]
dos Santos Soares, M., Vrancken, J. and Verbraeck, A., User requirements modeling and analysis of software-intensive systems. Journal of Systems and Software. v84 i2. 328-339.
[44]
ISO/IEC 42010:2007 - originally IEEE Std 1471:2000 - Recommended Practice for Architectural Description of Software-intensive Systems, 2007.
[45]
Lago, P., Avgeriou, P. and Hilliard, R., Guest editors' introduction: Software architecture: framing stakeholders' concerns. IEEE Software. v27. 20-24.
[46]
Clements, P., Kazman, R. and Klein, M., Evaluating Software Architecture: Methods and Case Studies. 2002. Addison-Wesley, Boston.
[47]
T. Yue, L. Briand, Y. Labiche, A use case modeling approach to facilitate the transition towards analysis models: concepts and empirical evaluation, in: 12th International Conference on Model Driven Engineering Languages and Systems (MODELS'09), 2009, pp. 484-498.
[48]
Weissman, A., Petrov, M. and Gupta, S., A computational framework for authoring and searching product design specifications. Advanced Engineering Informatics. v25 i3. 516-534.
[49]
L. Briand, D. Falessi, S. Nejati, M. Sabetzadeh, T. Yue, Traceability and sysml design slices to support safety inspections: a controlled experiment, Tech. Rep. 2010-08, Simula Research Laboratory, 2010.
[50]
S. Maoz, J. Ringert, B. Rumpe, ADDiff: semantic differencing for activity diagrams, in: FSE, 2011, pp. 179-189.

Cited By

View all
  • (2024)Towards Leveraging the Concept of Influence to Enhance Collaborative Cyber-Physical Systems DevelopmentProceedings of the ACM/IEEE 27th International Conference on Model Driven Engineering Languages and Systems10.1145/3652620.3688568(935-944)Online publication date: 22-Sep-2024
  • (2024)TRIAD: Automated Traceability Recovery based on Biterm-enhanced Deduction of Transitive Links among ArtifactsProceedings of the IEEE/ACM 46th International Conference on Software Engineering10.1145/3597503.3639164(1-13)Online publication date: 20-May-2024
  • (2024)Recovering Trace Links Between Software Documentation And CodeProceedings of the IEEE/ACM 46th International Conference on Software Engineering10.1145/3597503.3639130(1-13)Online publication date: 20-May-2024
  • Show More Cited By

Recommendations

Comments

Please enable JavaScript to view thecomments powered by Disqus.

Information & Contributors

Information

Published In

cover image Information and Software Technology
Information and Software Technology  Volume 54, Issue 6
June, 2012
134 pages

Publisher

Butterworth-Heinemann

United States

Publication History

Published: 01 June 2012

Author Tags

  1. Model slicing
  2. Safety certification
  3. SysML
  4. Traceability

Qualifiers

  • Article

Contributors

Other Metrics

Bibliometrics & Citations

Bibliometrics

Article Metrics

  • Downloads (Last 12 months)0
  • Downloads (Last 6 weeks)0
Reflects downloads up to 27 Nov 2024

Other Metrics

Citations

Cited By

View all
  • (2024)Towards Leveraging the Concept of Influence to Enhance Collaborative Cyber-Physical Systems DevelopmentProceedings of the ACM/IEEE 27th International Conference on Model Driven Engineering Languages and Systems10.1145/3652620.3688568(935-944)Online publication date: 22-Sep-2024
  • (2024)TRIAD: Automated Traceability Recovery based on Biterm-enhanced Deduction of Transitive Links among ArtifactsProceedings of the IEEE/ACM 46th International Conference on Software Engineering10.1145/3597503.3639164(1-13)Online publication date: 20-May-2024
  • (2024)Recovering Trace Links Between Software Documentation And CodeProceedings of the IEEE/ACM 46th International Conference on Software Engineering10.1145/3597503.3639130(1-13)Online publication date: 20-May-2024
  • (2022)Using Consensual Biterms from Text Structures of Requirements and Code to Improve IR-Based Traceability RecoveryProceedings of the 37th IEEE/ACM International Conference on Automated Software Engineering10.1145/3551349.3556948(1-1)Online publication date: 10-Oct-2022
  • (2020)Improving the effectiveness of traceability link recovery using hierarchical bayesian networksProceedings of the ACM/IEEE 42nd International Conference on Software Engineering10.1145/3377811.3380418(873-885)Online publication date: 27-Jun-2020
  • (2020)A novel approach to tracing safety requirements and state-based design modelsProceedings of the ACM/IEEE 42nd International Conference on Software Engineering10.1145/3377811.3380332(848-860)Online publication date: 27-Jun-2020
  • (2019)Using tool integration for improving traceability management testing processesJournal of Software: Evolution and Process10.1002/smr.217131:6Online publication date: 24-Jun-2019
  • (2018)Evolving software trace links between requirements and source codeEmpirical Software Engineering10.1007/s10664-017-9561-x23:4(2198-2231)Online publication date: 1-Aug-2018
  • (2017)Incrementally slicing editable submodelsProceedings of the 32nd IEEE/ACM International Conference on Automated Software Engineering10.5555/3155562.3155677(913-918)Online publication date: 30-Oct-2017
  • (2017)Preventing Defects: The Impact of Requirements Traceability Completeness on Software QualityIEEE Transactions on Software Engineering10.1109/TSE.2016.262226443:8(777-797)Online publication date: 11-Aug-2017
  • Show More Cited By

View Options

View options

Login options

Media

Figures

Other

Tables

Share

Share

Share this Publication link

Share on social media