De l'élicitation des besoins à la spécification formelle

Cet article presente une methode pour l'elicitation et l'expression des besoins. Elle est basee sur une analyse Cet article presente une methode pour l'elicitation et l'expression des besoins. Elle est basee sur une analyse detaillee des besoins permettant une meilleure comprehension du probleme a resoudre. l'approche -- qui etablit une distinction claire entre besoins et specifications -- conduit naturellement a l'expression d'une specification formelle. Elle ne presente pas de nouveaux langages mais repose sur l'utilisation de techniques existantes. Les agendas sont utilises pour decrire la methode. || This paper proposes a method for the elicitation and the expression of requirements.It is based on a detailed analysis of requirements, leading to a better understanding of the problem to be solved. The approach -- which clearly distinguishes between req

[1]  William E. Lorensen,et al.  Object-Oriented Modeling and Design , 1991, TOOLS.

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

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

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

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

[6]  Chris Dollin,et al.  Object-oriented development: the fusion method , 1994 .

[7]  J. Souquieres,et al.  A "coming and going" approach to specification construction: a scenario , 1996, Proceedings of the 8th International Workshop on Software Specification and Design.

[8]  Jennifer Stapleton Review: UML Distilled: Applying the Standard Object Modelling Language , 1998 .

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

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

[11]  Harlan D. Mills Software Development , 1976, IEEE Transactions on Software Engineering.

[12]  Barry W. Boehm,et al.  A spiral model of software development and enhancement , 1986, Computer.

[13]  Maritta Heisel,et al.  A Method to Express Requirements and Transform them into a Formal Specification , 1998 .

[14]  Annie I. Antón,et al.  The use of goals to surface requirements for evolving systems , 1998, Proceedings of the 20th International Conference on Software Engineering.

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

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

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

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

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

[20]  M. Heisel,et al.  Expression of Styles in Formal Speciication , 1996 .

[21]  Maritta Heisel,et al.  Detecting Feature Interactions - A Heuristic Approach , 1998 .