Skip to main content

A Method for Requirements Elicitation and Formal Specification

  • Conference paper
  • First Online:
Conceptual Modeling — ER ’99 (ER 1999)

Part of the book series: Lecture Notes in Computer Science ((LNCS,volume 1728))

Included in the following conference series:

Abstract

We propose a method for the elicitation and the expression of requirements. The requirements are then transformed in a systematic way into a formal specification. The approach — which distinguishes between requirements and specifications — gives methodological support for requirements elicitation and specification development. It avoids introducing new notations but builds on known techniques.

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 39.99
Price excludes VAT (USA)
  • Available as PDF
  • Read on any device
  • Instant download
  • Own it forever
Softcover Book
USD 54.99
Price excludes VAT (USA)
  • Compact, lightweight 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

Preview

Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.

References

  1. P. Chen. The entity-relationship model-towards a unified view of data. ACM Transactions on Database Systems, 1(1), 1976.

    Google Scholar 

  2. A. Dardenne, A.v. Lamsweerde, and S. Fickas. Goal-directed requirements acquisition. Science of Computer Programming, 20:3–50, 1993.

    Article  Google Scholar 

  3. R. Darimont and A. v. Lamsweerde. Formal Refinement for Patterns for Goal-Driven Requirements Elaboration. In Proc FSE-4, ACM Symposium on the Foundation of Software Engineering, pages 179–190, 1996.

    Google Scholar 

  4. S. Easterbrook and B. Nuseibeh. Using ViewPoints for inconsistency management. Software Engineering Journal, pages 31–43, January 1996.

    Google Scholar 

  5. M.S. Feather, S. Fickas, and R.B. Helm. Composite System Design: the Good News and the Bad News. In Proc. 6th Knowledge-Based Software Engineering Conference, pages 16–25. IEEE Computer Society Press, 1991.

    Google Scholar 

  6. M.D. Fraser, K. Kumar, and V.K. Vaisnavi. Strategies for Incorporating Formal Specifications in Software Development. CACM, 37(10):74–86, Oct. 1994.

    Article  Google Scholar 

  7. M. Heisel. Agendas-a concept to guide software development activites. In R. N. Horspool, editor, Proc. Systems Implementation 2000, pages 19–32. Chapman & Hall, 1998.

    Google Scholar 

  8. M. Heisel and J. Souquières. A heuristic approach to detect feature interactions in requirements. In K. Kimbler and W. Bouma, editors, Proc. 5th Feature Interaction Workshop, pages 165–171. IOS Press Amsterdam, 1998.

    Google Scholar 

  9. IEEE94. Software development. IEEE publications office, IEEE Standard 1498, Los Alamitos, CA, March 1994.

    Google Scholar 

  10. M. Jackson and P. Zave. Deriving specifications from requirements: an example. In Proceedings 17th Int. Conf. on Software Engineering, Seattle, USA, pages 15–24. ACM Press, 1995.

    Google Scholar 

  11. M. Jarke. Requirements tracing. Communications of the ACM, pages 32–36, December 1998.

    Google Scholar 

  12. N. Lévy and J. Souquières. A “Coming and Going” Approach to Scenario. In W. Schafer, J. Kramer, and A. Wolf, editors, Proc. 8th Int. Workshop on Software Specification and Design, pages 115–158. IEEE Computer Society Press, 1996.

    Google Scholar 

  13. N. Lévy and J. Souquières. Modelling Specification Construction by Successive Approximations. In M. Johnson, editor, 6th International AMAST conference, pages 351–364. Springer Verlag LNCS 1349, 1997.

    Google Scholar 

  14. D.L. Parnas. Using Mathematical Models in the Inspection of Critical Systems. In M. Hinchey and J. Bowen, editors, Applications of Formal Methods, pages 17–31. Prentice Hall, 1995.

    Google Scholar 

  15. S. Sadaoui and J. Souquières. Quelques approches de la réutilisation dans le modèle Proplane. In Conférence AFADL, Approches formelles dans l’assistance au développement de logiciels, pages 85–96, Toulouse, 1997. Onera-Cert. 318

    Google Scholar 

  16. J. M. Spivey. The Z Notation-A Reference Manual. Prentice Hall, 2nd edition, 1992.

    Google Scholar 

  17. P. Zave and M. Jackson. Four dark corners for requirements engineering. ACM Transactions on Software Engineering and Methodology, 6(1):1–30, January 1997.

    Article  Google Scholar 

Download references

Author information

Authors and Affiliations

Authors

Editor information

Editors and Affiliations

Rights and permissions

Reprints and permissions

Copyright information

© 1999 Springer-Verlag Berlin Heidelberg

About this paper

Cite this paper

Heisel, M., Souquières, J. (1999). A Method for Requirements Elicitation and Formal Specification. In: Akoka, J., Bouzeghoub, M., Comyn-Wattiau, I., Métais, E. (eds) Conceptual Modeling — ER ’99. ER 1999. Lecture Notes in Computer Science, vol 1728. Springer, Berlin, Heidelberg. https://doi.org/10.1007/3-540-47866-3_21

Download citation

  • DOI: https://doi.org/10.1007/3-540-47866-3_21

  • Published:

  • Publisher Name: Springer, Berlin, Heidelberg

  • Print ISBN: 978-3-540-66686-8

  • Online ISBN: 978-3-540-47866-9

  • eBook Packages: Springer Book Archive

Publish with us

Policies and ethics