Skip to main content
SpringerLink
Log in

The Eclipse Requirements Modeling Framework

  • Chapter
  • First Online:
Managing Requirements Knowledge

Abstract

This chapter is concerned with the Requirements Modeling Framework (RMF) (http://eclipse.org/rmf), an Eclipse-based open-source platform for requirements engineering. The core of RMF is based on the emerging Requirements Interchange Format (ReqIF), which is an OMG standard [1]. The project uses ReqIF as the central data model. At the time of this writing, RMF was the only open-source implementation of the ReqIF data model.

By being based on an open standard that is currently gaining industry support, RMF can act as an interface to existing requirements management tools. Further, by based on the Eclipse platform, integration with existing Eclipse-based offerings is possible.

In this chapter, we will describe the architecture of the RMF project, as well as the underlying ReqIF standard. Further, we give an overview of the GUI, which is called ProR. A key strength of RMF and ProR is the extensibility, and we present the integration ProR with Rodin, which allows traceability between natural language requirements and Event-B formal models.

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

Access this chapter

Log in via an institution
Chapter
USD 29.95
Price excludes VAT (USA)
  • Available as PDF
  • Read on any device
  • Instant download
  • Own it forever
eBook
USD 84.99
Price excludes VAT (USA)
  • Available as EPUB and PDF
  • Read on any device
  • Instant download
  • Own it forever
Softcover Book
USD 109.00
Price excludes VAT (USA)
  • Compact, lightweight edition
  • Dispatched in 3 to 5 business days
  • Free shipping worldwide - see info
Hardcover Book
USD 109.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

Notes

  1. 1.

    http://www.ibm.com/software/awdtools/doors/.

  2. 2.

    http://www.visuresolutions.com/irqa-requirements-tool.

  3. 3.

    http://www.gebit.de/loesungen/technische-loesungen/trend-analyst-requirements.html.

  4. 4.

    http://www.mediawiki.org/.

  5. 5.

    To be precise, whether the controller is aware of the temperature or not depends on where the line is drawn between system and environment. In this simple example, the sensor is not part of the system (the controller).

  6. 6.

    http://www-01.ibm.com/software/awdtools/doors/.

  7. 7.

    At the time of its creation, the format was called RIF and only later on, renamed into ReqIF.

  8. 8.

    http://www.automotive-his.de/.

  9. 9.

    http://www.deploy-project.eu/.

  10. 10.

    http://www.itea-verde.org/.

  11. 11.

    http://www.youtube.com/watch?v=sdfTNZduvZ4.

  12. 12.

    http://subclipse.tigris.org/.

  13. 13.

    http://www.eclipse.org/subversive/.

  14. 14.

    http://www.eclipse.org/egit/.

References

  1. OMG (2011) Requirements interchange format (ReqIF) 1.0.1.http://www.omg.org/spec/ReqIF/

  2. Jastram M, Graf A (2011) Requirement traceability in topcased with the requirements interchange format (RIF/ReqIF). First Topcased Days Toulouse

    Google Scholar 

  3. IEEE (1997) Recommended practice for software requirements specifications. Technical Report IEEE Std 830–1998, IEEE

    Google Scholar 

  4. Kruchten P (2004) The rational unified process: an introduction. Addison-Wesley, Boston

    Google Scholar 

  5. Gunter CA, Jackson M, Gunter EL, Zave P (2000) A reference model for requirements and specifications. IEEE Softw 17:37–43

    Google Scholar 

  6. Jackson M (2001) Problem frames: analysing and structuring software development problems. Addison-Wesley/ACM Press, Harlow/New York

    Google Scholar 

  7. Darimont R, Delor E, Massonet P, van Lamsweerde A (1997) GRAIL/KAOS: an environment for goal-driven requirements engineering. In: Proceedings of the 19th international conference on software engineering, ACM, Boston, MA, USA, pp 612–613

    Google Scholar 

  8. Parnas DL, Madey J (1995) Functional documents for computer systems. Sci Comp Program 25(1):41–61

    Article  Google Scholar 

  9. Van Lamsweerde A et al. (2001) Goal-oriented requirements engineering: a guided tour. In: Proceedings of the 5th IEEE international symposium on requirements engineering, Toronto, Canada, vol 249, p 263

    Google Scholar 

  10. Clarke E, Wing J (1996) Formal methods: state of the art and future directions. ACM Comput Surv (CSUR) 28(4):626–643

    Article  Google Scholar 

  11. Gotel O, Finkelstein A (1994) An analysis of the requirements traceability problem. In: Proceedings of the first international conference on requirements engineering, Colorado Springs, CO, U.S.A., p 94101

    Google Scholar 

  12. Jastram M, Hallerstede S, Leuschel M, Russo AG Jr (2010) An approach of requirements tracing in formal refinement. In: VSTTE. Springer, Edinburgh, Scotland

    Google Scholar 

  13. Steinberg D, Budinsky F, Peternostro M, Merks E (2009) EMF eclipse modeling framework, 2nd edn. Addison-Wesley, Upper Saddle River

    Google Scholar 

  14. Part B (2008) Deploy project

    Google Scholar 

  15. Coleman J, Jones C, Oliver I, Romanovsky A, Troubitsyna E (2005) RODIN (rigorous open development environment for complex systems). EDCC-5, Budapest, Supplementary Volume p 2326

    Google Scholar 

  16. Jastram M, Graf A (2011) Requirements modeling framework. Eclipse magazine 6.11

    Google Scholar 

  17. Jastram M, Hallerstede S, Ladenberger L (2011) Mixing formal and informal model elements for tracing requirements. In: Automated Verification of Critical Systems (AVoCS), Newcastle / UK

    Google Scholar 

  18. Jastram M, Graf A (2011) Requirements, traceability and DSLs in eclipse with the requirements interchange format (RIF/ReqIF). In: Tagungsband des Dagstuhl-Workshop MBEES: Modellbasierte Entwicklung eingebetteter Systeme VII. fortiss GmbH, Dagstuhl, Germany

    Google Scholar 

  19. Efftinge S, Völter M (2006) oAW xText: a framework for textual DSLs. In: Workshop on modeling symposium at eclipse summit, Esslingen, Germany, vol 32

    Google Scholar 

Download references

Author information

Authors and Affiliations

  1. Formal Mind GmbH, Düsseldorf, Germany

    M. Jastram

Authors
  1. M. Jastram
    View author publications

    You can also search for this author in PubMed Google Scholar

Corresponding author

Correspondence to M. Jastram .

Editor information

Editors and Affiliations

  1. Department of Informatics / MOBIS, University of Hamburg, Vogt-Kölln-Str. 30, Hamburg, 22527, Germany

    Walid Maalej

  2. Harman Becker Automotive Systems GmbH, Moosacher Str. 48, Munich, 80809, Germany

    Anil Kumar Thurimella

Rights and permissions

Reprints and permissions

Copyright information

© 2013 Springer-Verlag Berlin Heidelberg

About this chapter

Cite this chapter

Jastram, M. (2013). The Eclipse Requirements Modeling Framework. In: Maalej, W., Thurimella, A. (eds) Managing Requirements Knowledge. Springer, Berlin, Heidelberg. https://doi.org/10.1007/978-3-642-34419-0_16

Download citation

  • DOI: https://doi.org/10.1007/978-3-642-34419-0_16

  • Published:

  • Publisher Name: Springer, Berlin, Heidelberg

  • Print ISBN: 978-3-642-34418-3

  • Online ISBN: 978-3-642-34419-0

  • eBook Packages: Computer ScienceComputer Science (R0)

Publish with us

Policies and ethics

Search

Navigation