论文信息 - A Method for Requirements Elicitation and Formal Specification

A Method for Requirements Elicitation and Formal Specification

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.

Maritta Heisel | Jeanine Souquières | J. Souquières | M. Heisel

[1] Kuldeep Kumar,et al. Strategies for incorporating formal specifications in software development , 1994, CACM.

[2] M. Heisel. Agendas—a concept to guide software development activities , 1998 .

[3] J. Michael Spivey,et al. The Z notation - a reference manual , 1992, Prentice Hall International Series in Computer Science.

[4] Matthias Jarke,et al. Requirements tracing , 1998, CACM.

[5] Pamela Zave,et al. Deriving Specifications from Requirements: an Example , 1995, 1995 17th International Conference on Software Engineering.

[6] Axel van Lamsweerde,et al. Formal refinement patterns for goal-driven requirements elaboration , 1996, SIGSOFT '96.

[7] Steve M. Easterbrook,et al. Using ViewPoints for inconsistency management , 1996, Softw. Eng. J..

[8] Michael Jackson,et al. Four dark corners of requirements engineering , 1997, TSEM.

[9] Jeanine Souquières,et al. Modelling Specification Construction by Successive Approximations , 1997, AMAST.

[10] Stephen Fickas,et al. Goal-Directed Requirements Acquisition , 1993, Sci. Comput. Program..

[11] Peter P. Chen. The entity-relationship model: toward a unified view of data , 1975, VLDB '75.

[12] Maritta Heisel,et al. A Heuristic Approach to Detect Feature Interactions in Requirements , 1998, FIW.

[13] Martin S. Feather,et al. Composite System Design: The Good News And The Bad News , 1991, Proceedings., 6th Annual Knowledge-Based Software Engineering Conference.