Skip to main content

Abstract

Requirements engineering is a fundamental part in the development of safety related embedded systems. Requirements engineering comprises eliciting, developing, analysing, validating, communicating and managing requirements. As the development of systems is based on the identified and developed requirements it is important that requirements accurately capture the stakeholder needs, are well-understood and verifiable. Due to that, requirements engineering guidelines and safety standards request several constraints on requirement statements like well-formedness, unambiguity and formalization.

This is a preview of subscription content, log in via an institution to check access.

Access this chapter

Chapter
USD 29.95
Price excludes VAT (USA)
  • Available as PDF
  • Read on any device
  • Instant download
  • Own it forever
eBook
USD 129.00
Price excludes VAT (USA)
  • Available as EPUB and PDF
  • Read on any device
  • Instant download
  • Own it forever
Softcover Book
USD 169.99
Price excludes VAT (USA)
  • Compact, lightweight edition
  • Dispatched in 3 to 5 business days
  • Free shipping worldwide - see info
Hardcover Book
USD 169.99
Price excludes VAT (USA)
  • Durable hardcover edition
  • Dispatched in 3 to 5 business days
  • Free shipping worldwide - see info

Tax calculation will be finalised at checkout

Purchases are for personal use only

Institutional subscriptions

References

  1. Airbus Report, Typical pilot application description for aerospace domain. Cesar Deliverable I_SP6_R1.5_M1

    Google Scholar 

  2. A. Albinet, S. Begoc, J.-L. Boulanger, O. Casse, I. Dal, H. Dubois, F. Lakhal, D. Louar, M.-A. Peraldi-Frati, Y. Sorel, Q.-D. Van, The MeMVaTEx methodology: from requirements to models in automotive application design, in ERTS’08, Toulouse, France, 2008

    Google Scholar 

  3. ANSI/IEEE Std 500-1984 P & V, IEEE Standard Reliability Data for Pumps and Drivers, Valve Actuators, and Valves (IEEE, New York, 1984)

    Google Scholar 

  4. AUTOSAR GbR, Virtual Function Bus, V2.1.0, R4.0 Rev 2 (2010), http://www.autosar.org/download/R4.0/AUTOSAR_EXP_VFB.pdf

  5. A. Baumgart, A common meta-model for the interoperation of tools with heterogeneous data models, in Proceedings of the Third Workshop on Model Driven Tool and Process Integration (MDTPI), Paris, France, 16 June 2010, ed. by C. Hein, M. Wagner, R. Mader, A. Keis, E. Armengaud (Fraunhofer Verlag, Stuttgart, 2010), pp. 31–40

    Google Scholar 

  6. A. Baumgart, C. Ellen, M. Oertel, P. Rehkop, S. Farfeleder, S. Schulz, A reference technology platform with common interfaces for distributed heterogeneous data, in Proceedings of the Embedded World 2012 Exhibition and Conference, Nuremberg, March 2012

    Google Scholar 

  7. D. Carrizo, O. Dieste, N. Juristo, Study of elicitation techniques adequacy, in 11th Workshop on Requirement Engineering, España, 2008, pp. 104–114

    Google Scholar 

  8. H. Chuping, L. Peiqiong, Y. Yping, The application of failure modes and effect analysis for software in digital fly control systems, in 16th Digital Avionics Systems Conference (DASC) 1997, AIAA/IEEE, vol. 1 (IEEE, 1997)

    Google Scholar 

  9. P. Cimiano, J. Völker, Text2Onto – a framework for ontology learning and data-driven change discovery, in Proceedings of the 10th International Conference on Applications of Natural Language to Information Systems, NLDB 2005, Alicante, 15–17 June 2005

    Google Scholar 

  10. W. Damm, H. Hungar, S. Henkler, I. Stierand, B. Josko, P. Reinkemeier, A. Baumgart, M. Bueker, T. Gezgin, G. Ehmen, R.Weber, Spes2020 architecture modeling, 2010. SPES2020 Deliverable D3.5

    Google Scholar 

  11. J. Doerr, D. Kerkow, T. Koenig, T. Olsson, T. Suzuki, Non-functional requirements in industry-three case studies adopting an experience-based NFR method, in Proceedings of 13th IEEE International Conference on Requirements Engineering, 2005 (IEEE, Los Alamitos, 2005), pp. 373–382

    Google Scholar 

  12. ESTEC QS Division (Reliability and Maintainability Section), Guidelines for considering a software intensive system with FMECA studies. ESTEC, January 1992. QS/91/247/082/RA

    Google Scholar 

  13. S. Farfeleder, T. Moser, A. Krall, T. Stulhane, H. Zojer, C. Panis, DODT: increasing requirements formalism using domain ontologies for improved embedded systems development, in Design and Diagnostics of Electronic Circuits & Systems (DDECS) (IEEE, Piscataway, 2011), pp. 271–274

    Google Scholar 

  14. Formal notation suitable to express safety properties. ESACS report, Sept 2001

    Google Scholar 

  15. M. Glinz, R. Wieringa, Guest editor’s introduction: stakeholders in requirements engineering. IEEE Softw. 24, 18–20 (2007)

    Article  Google Scholar 

  16. P.L. Goddard, Software FMEA techniques, in Proceedings of the Annual Reliability and Maintainability Symposium, Los Angeles, 2000

    Google Scholar 

  17. C. Gonzalez-Perez, B. Henderson-Sellers, Templates and resources in software development methodologies. J. Object Technol. 4(4), 173–190 (2005)

    Article  Google Scholar 

  18. H. Hecht, A. Xuego, M. Hecht, Computer-Aided Software FMEA (SoHaR Incorporated, Culver City/Los Angeles, 2003)

    Google Scholar 

  19. A. Herrmann, D. Kerkow, J. Doerr, Exploring the characteristics of NFR methods: a dialogue about two approaches, in Proceedings of the 13th International Working Conference on Requirements Engineering: Foundation for Software Quality (Springer, Berlin/Heidelberg, 2007), pp. 320–334

    Google Scholar 

  20. IAEA, Vienna, Component Reliability Data for Use in Probalistic Safety Assesment (IAEA, Vienna, 1988)

    Google Scholar 

  21. ISO/IEC 12207:2008, Systems and software engineering - software life cycle processes, Technical report, ISO/IEC, 2008

    Google Scholar 

  22. ISO, ISO/IEC 15288:2008, Systems and software engineering – system life cycle processes. Technical report, ISO/IEC, 2008

    Google Scholar 

  23. ISO, ISO/IEC/IEEE 29148:2011, Systems and software engineering – life cycle processes – requirements engineering. Technical report, ISO/IEC/IEEE, 2011

    Google Scholar 

  24. P. Johannesen, F. Tørner, J.Torin, Actual based hazard analysis for satfety critical systems, in Proceedings of the 23th International Conference on Computer Safety, Reliability and Security, Potsdam, Germany, Sept 2004

    Google Scholar 

  25. H. Kaiya, M. Saeki, Ontology based requirements analysis: lightweight semantic processing approach, in 5th International Conference on Quality Software, Melbourne, 2005, pp. 223–230

    Google Scholar 

  26. A. Lamsweerde, Requirements Engineering: From System Goals to UML Models to Software Specifications (Wiley, Chichester/Hoboken, 2009)

    Google Scholar 

  27. J.D. Lawrence, Software safety hazard analysis. NUREG/CR-6430, UCRL-ID-1225 14, Lawrence Livermore National Laboratory, California, Feb 1996

    Book  Google Scholar 

  28. B. Li, M. Li, K. Chen, C. Smidts, Integrating software into PRA: a software related failure mode taxonomy. Risk Anal. 26, 997–1012 (2006)

    Article  Google Scholar 

  29. MathWorks, Simulink – simulation and model-based design, http://www.mathworks.com/products/simulink/

  30. N. Noy, D. McGuinness, Ontology Development 101: A Guide to Creating Your First Ontology (2001)

    Google Scholar 

  31. OMG, Systems modeling language, http://www.sysml.org/

  32. OMG, Software and systems process engineering metamodel specification (SPEM) Apr 2008, http://www.omg.org/spec/SPEM/2.0/

  33. O. Preiss, A. Wegmann, Stakeholder discovery and classification based on systems science principles, in Proceedings of the 2nd Asia-Pacific Conference on Quality Software, Hong Kong, 2001 (IEEE, 2001), pp. 194–198

    Google Scholar 

  34. Project SPEEDS: WP.2.1 Partners, SPEEDS L-1 Meta-Model, May 2009. SPEEDS deliverable D.2.1.5, revision 1.0.1, http://speeds.eu.com/downloads/SPEEDS_Meta-Model.pdf

  35. Protégé tool, http://protege.stanford.edu/

  36. Railway Applications – The Specification and Demonstration of Reliability, Availability, Maintainability and Safety (RAMS). Part 2: Guide to the application of EN 50126-1 for safety (2007)

    Google Scholar 

  37. B. Ramesh, M. Jarke, Toward reference models for requirements traceability. IEEE Trans. Softw. Eng. 27, 58–93 (2001)

    Article  Google Scholar 

  38. C. Seguin, Formal notation suitable to express safety properties. ESACS technical report, 17 Sept 2001

    Google Scholar 

  39. H. Sharp, A. Finkelstein, G. Galal, Stakeholder identification in the requirements engineering process, in Proceedings Tenth International Workshop on Database and Expert Systems Applications, Florence, 1999, pp. 387–391

    Google Scholar 

  40. G. Sindre, A. Opdahl, Eliciting security requirements by misuse cases, in Proceedings 37th International Conference on Technology of Object-Oriented Languages and Systems, TOOLS-Pacific 2000 (IEEE, Los Alamitos, 2000), pp. 120–131

    Google Scholar 

  41. SINTEF, OREDA Offshore Reliability Data, 5th edn. (OREDA Participants/Der Norske Veritas, Høvik, 2009)

    Google Scholar 

  42. I. Sommerville, Software Engineering, 8th edn. (Addison-Wesley, Harlow/New York, 2007)

    MATH  Google Scholar 

  43. SPEEDS Methodologie – a white paper, Technical report, SPEEDS, 2006

    Google Scholar 

  44. T. Stalhane, I. Omoronyia, F. Reichenbach, Ontology-guided requirements and safety analysis, in 6th International Conference on Safety of Industrial Automated Systems, Tampere, 2010

    Google Scholar 

  45. System Reliability Centre, Part failure mode distributions

    Google Scholar 

  46. Systems engineering measurement primer, Technical report, INCOSE Measurement Working Group, 1998

    Google Scholar 

  47. Technical Committee ISO/TC 22 Subcommittee SC 3 (ed.), ISO/WD26262: Road Vehicles – Functional Safety. (Automotive Standards Committee of the German Institute for Standardization, 2009)

    Google Scholar 

  48. The ATESST Consortium, EAST-ADL Domain Model Specification, June 2010, ATESST Deliverable D4.1.1, Version 2.1 RC3, http://www.atesst.org/home/liblocal/docs/ATESST2_D4.1.1_EAST-ADL2-Specification_2010-06-02.pdf

  49. S.R. Trammel, B.J. Davis, Using a modified HazOp/FMEA methology for assesssing system risk, in Proceedings of the Second International EMAT Workshop (IEEE, Los Alamitos, 2001)

    Google Scholar 

  50. R.J. Urbanic, W.H. ElMaraghy, Using a modified failure modes and effects analysis within the structured design recovery framework, in The Future of Product Development (2007), pp. 409–419

    Google Scholar 

  51. J. Wood, D. Silver, Joint Application Development (Wiley, New York, 1995)

    Google Scholar 

  52. Wordnet – a lexical database for English, http://wordnet.princeton.edu/

Download references

Author information

Authors and Affiliations

Authors

Corresponding author

Correspondence to Markus Ortel .

Editor information

Editors and Affiliations

Rights and permissions

Reprints and permissions

Copyright information

© 2013 Springer-Verlag Wien

About this chapter

Cite this chapter

Ortel, M. et al. (2013). Requirements Engineering. In: Rajan, A., Wahl, T. (eds) CESAR - Cost-efficient Methods and Processes for Safety-relevant Embedded Systems. Springer, Vienna. https://doi.org/10.1007/978-3-7091-1387-5_3

Download citation

  • DOI: https://doi.org/10.1007/978-3-7091-1387-5_3

  • Published:

  • Publisher Name: Springer, Vienna

  • Print ISBN: 978-3-7091-1386-8

  • Online ISBN: 978-3-7091-1387-5

  • eBook Packages: EngineeringEngineering (R0)

Publish with us

Policies and ethics