Reasoning with goals to engineer requirements

ICEIS 2003 - Proceedings of the 5th International Conference on Enterprise Information Systems

Volumn 1, Issue , 2003, Pages IS11-IS19

  Rolland, Colette ^a  

^a UNIVERSITÉ PARIS 1 PANTHÉON SORBONNE   (France)

Author keywords

Dial up networking; Goal driven requirements; Goal oriented requirements; Requirements elicitation Internet services; Requirements engineering; Systems goals

Indexed keywords

INFORMATION SYSTEMS; MANAGEMENT SCIENCE; REQUIREMENTS ENGINEERING;

DIAL-UP; ENGINEERING ACTIVITIES; GOAL DRIVEN; GOAL DRIVEN APPROACH; GOAL-ORIENTED; INTERNET SERVICES; REQUIREMENTS ELICITATION; SUPPORT REQUIREMENTS;

HUMAN COMPUTER INTERACTION;

EID: 67649845117     PISSN: None     EISSN: None     Source Type: Conference Proceeding    
DOI: None     Document Type: Conference Paper

References (73)

1. nd International Conference on Requirements Engineering ICRE'96, pp. 136-144.
2. Anton, A. I, and Potts C., 1998, The use of goals to surface requirements for evolving systems, International Conference on Software Engineering (ICSE'98), Kyoto, Japan, pp. 157-166, 19-25 April 1998.
3. Anton, A. I., Earp J.B., Potts C., and Alspaugh T.A., 2001, The role of policy and stakeholder privacy values in requirements engineering, IEEE 5th International Symposium on Requirements Engineering (RE'01), Toronto, Canada, pp. 138-145, 27-31 August 2001.
4. Ben Achour, C., 1999, Requirements extraction from textual scenarios. PhD Thesis, University Paris6 Jussieu, January 1999.
5. Boehm, B., 1976, Software engineering. IEEE Transactions on Computers, 25(12): 1226-1241.
6. Boehm, B., 1996, Identify Quality-requirements conflicts, 1996, Proceedings ICRE, Second International Conference on Requirements Engineering, April 15-18, 1996, Colorado spring, Colorado, 218.
7. Bowen, T. P., and Wigle., G. B., Tsai, J. T., 1985, Specification of software quality attributes. Report of Rome Air Development Center.
8. st Conference on Requirements Enginering, ICRE'94 pp. 154-158.
9. Cockburn, A., 1995, Structuring use cases with goals. Technical report. Human and Technology, 7691 Dell Rd, Salt Lake City, UT 84121, HaT.TR.95.1, http://members.aol.com/acocburn/papers/usecases.htm.
10. CREWS Team, 1998, The crews glossary, CREWS report 98-1, http://SUNSITE.informatik.rwthaachen.de/CREWS/reports.htm
11. Chung, K. L., Nixon B. A., and Yu E, Mylopoulos J., 2000, Non-Functional Requirements in Software Engineering. Kluwer Academic Publishers. 440 p.
12. Dano, B., Briand, H., and Barbier, F., 1997, A use case driven requirements engineering process. Third IEEE International Symposium On Requirements Engineering RE'97, Antapolis, Maryland, IEEE Computer Society Press.
13. Dardenne, A., and Lamsweerde., A. v., and Fickas, S., 1993, Goal-directed Requirements Acquisition, Science of Computer Programming, 20, Elsevier, pp. 3-50.
14. Davis, A.M., 1993, Software requirements: objects, functions and states. Prentice Hall.
15. Dik, S. C., 1989, The theory of functional grammar, part i: the structure of the clause. Functional Grammar Series, Fories Publications.
16. th International Workshop on software Specification and design. Isobe. IEEE CS Press. April 1998, 34-42.
17. ELEKTRA consortium, 1997, Electrical enterprise knowledge for transforming applications. ELEKTRA Project Reports.
18. ESI96, European Software Institute, 1996, "European User survey analysis", Report USV-EUR 2.1, ESPITI Project, January 1996.
19. Fillmore, C., 1968, The case for case. In "Universals in linguistic theory", Holt, Rinehart and Winston (eds.), Bach & Harms Publishing Company, pp. 1-90.
20. Gote, O., and Finkelstein A., 1994, Modelling the contribution structure underlying requirements, in Proc. First Int. Workshop on Requirements Engineering: Foundation of Software Quality, Utrech, Netherlands.
21. Haumer, P., Pohl K., and Weidenhaupt K., 1998, Requirements elicitation and validation with real world scenes. IEEE Transactions on Software Engineering, Special Issue on Scenario Management, M. Jarke, R. Kurki-Suonio (eds.), Vol. 24, No 12, pp. 11036-1054.
22. Heymans, P., and Dubois, E., 1998, Scenario-based techniques for supporting the elaboration and the validation of formal requirements. RE Journal, P. Loucopoulos, C. Potts (eds.), Springer, CREWS Deliverable No 98-30, http://SUNSITE.informatik.rwth-aachen.de/CREWS/
23. Jacobson, I., 1995, The Use case construct in object-oriented software engineering. In Scenario-Based Design: Envisioning Work and Technology in System Development, J.M. Carroll (ed.), pp. 309336.
24. Jarke, M., and Pohl, K., 1993, Establishing visions in context: towards a model of requirements processes. Proc. 12th Intl. Conf. Information Systems, Orlando.
25. Kaindl, H., 2000, "A design process based on a model combining scenarios with goals and functions", IEEE Trans. on Systems, Man and Cybernetic, Vol. 30 No. 5, September 2000, 537-551.
26. Kardasis P., and Loucopoulos P., 1998, Aligning legacy information system to business processes. Submitted to CAiSE'98.
27. Lamsweerde, A. v., Dardenne, B., Delcourt, and F. Dubisy, 1991, "The KAOS project: knowledge acquisition in automated specification of software", Proc. AAAI Spring Symp. Series, Track: "Design of Composite Systems", Stanford University, March 1991, 59-62.
28. nd Int. Symp. On Requirements Engineering, York, pp 194-204.
29. Lamsweerde A. v., and Willemet, L., 1998, "Inferring declarative requirements specifications from operational scenarios". In: IEEE Transactions on Software Engineering, Special Issue on Scenario Management. Vol. 24, No. 12, Dec. 1998, 1089-1114.
30. Lamsweerde, A. v., Darimont, R., and Letier, E., 1998a, "Managing conflicts in goal-driven requirements engineering", IEEE Trans. on Software. Engineering, Special Issue on Inconsistency Management in Software Development, Vol. 24 No. 11, November 1998, 908-926.
31. Lamsweerde, A. v., 2000, Requirements engineering in the year 00: A research perspective. In Proceedings 22nd International Conference on Software Engineering, Invited Paper, ACM Press, June 2000.
32. Lamsweerde, A. v., and Letier, E., 2000a, "Handling obstacles in goal-oriented requirements engineering", IEEE Transactions on Software Engineering, Special Issue on Exception Handling, Vol. 26 No. 10, October 2000, pp. 978-1005.
33. Lamsweerde, A.v., 2001, "Goal-oriented requirements engineering: a guided tour". Invited minitutorial, Proc. RE'01 International Joint Conference on Requirements Engineering, Toronto, IEEE, August 2001, pp. 249-263.
34. Le, T.L., 1999, Guidage des processus d'ingénierie des besoins par un approche de réutilisation de cas, Master Thesis, CRI, Université Paris-1, Panthéon Sorbonne.
35. Lee, S. P., 1997, Issues in requirements engineering of object-oriented information system: a review, Malaysian Journal of computer Science, Vol. 10, No 2, December 1997.
36. Leite, J. C.S, Rossi, G., Balaguer, F., Maiorana, A., Kaplan, G., Hadad, G., and Oliveros, A., 1997, Enhancing a requirements baseline with scenarios. In Third IEEE International Symposium On Requirements Engineering RE'97, Antapolis, Maryland, IEEE Computer Society Press, pp. 44-53.
37. Letier, E., 2001, Reasoning about agents in goal-oriented requirements engineering. Ph. D. Thesis, University of Louvain, May 2001; http://www.info.ucl.ac.be/people/eletier/thesis.html
38. Leveson, N. G., 2000, "Intent specifications: an approach to building human-centred specifications", IEEE Trans. Soft. Eng., Vol. 26, pp. 15-35.
39. 3 (from fuzzy to formal) view on requirements engineering. Ingénierie des systèmes d'information, Vol. 2 No 6, pp. 639-655.
40. Loucopoulos, P., Kavakli, V., and Prakas, N., 1997, Using the EKD approach, the modelling component. ELEKTRA project internal report.
41. Mylopoulos, J., Chung K.L., and Nixon, B.A., 1992, Representing and using non-functional requirements: a process-oriented approach. IEEE Transactions on Software Engineering, Special Issue on Knowledge Representation and Reasoning in Software Development, Vol. 18, No 6, June 1992, pp. 483-497.
42. Mylopoulos, J., Chung, K.L., and Yu, E., 1999, "From object-oriented to goal6oriented requirements analysis". Communications of the ACM. Vol 42 No 1, January 1999, 31-37.
43. Mostow, J., 1985, "Towards better models of the design process". AI Magazine, Vol. 6, pp. 44-57.
44. Nature, 1999, The nature of requirements engineering. Shaker Verlag Gmbh. (Eds.) Jarke M., Rolland C., Sutcliffe A. and Dömges R., Jily 1999.
45. Nuseibeh, B., Kramer, J., and Finkelstein, A., 1994, A framework for expressing the relationships between multiple views in requirements specification. In IEEE Transactions on Software Engineering, Volume 20, pages 760-773. IEEE CS Press, October 1994.
46. th International Conference on Software Process (ICSP'98), Chicago.
47. Pohl K., 1996, Process centred requirements engineering, J. Wiley and Sons Ltd.
48. Pohl K., and Haumer, P., 1997, Modelling contextual information about scenarios. Proceedings of the Third International Workshop on Requirements Engineering: Foundations of Software Quality REFSQ'97, Barcelona, pp. 187-204, June 1997.
49. Potts, C., Takahashi, K., and Anton, A. I., 1994, Inquiry-based requirements analysis. In IEEE Software 11(2), pp. 21-32.
50. Potts, C., 1995, "Using schematic scenarios to understand user needs", Proc. DIS'95 - ACM Symposium on Designing interactive Systems: Processes, Practices and Techniques, University of Michigan, August 1995.
51. Potts, C., 1997, Fitness for use: the system quality that matters most. Proceedings of the Third International Workshop on Requirements Engineering: Foundations of Software Quality REFSQ'97, Barcelona, pp. 15-28, June 1997.
52. Prat, N., 1997, Goal formalisation and classification for requirements engineering. Proceedings of the Third International Workshop on Requirements Engineering: Foundations of Software Quality REFSQ'97, Barcelona, pp. 145-156, June 1997.
53. nd Symposium on Requirements Engineering (RE'95), pp 89-95, UK.
54. Rasmussen, J., 1990, Mental models and the control of action in complex environments. Mental Models and Human-Computer Interaction, D. Ackermann and M.J. Tauber, eds., North-Holland: Elsevier, pp. 41-69.
55. Rolland, C, and Ben Achour, C., 1997, Guiding the construction of textual use case specifications. Data & Knowledge Engineering Journal Vol. 25 No 1, pp. 125-160, (ed. P. Chen, R.P. van de Riet) North Holland, Elsevier Science Publishers. March 1997.
56. Rolland, C., Grosz, G., and Nurcan, S., 1997a, Guiding the EKD process. ELEKTRA project report,
57. Rolland, C., Nurcan, S., and Grosz, G., 1997b, Guiding the participative design process. Association for Information Systems Americas Conference, Indianapolis, Indiana, pp. 922-924, August, 1997
58. Rolland, C., Souveyet, C., and Ben Achour, C., 1998, Guiding goal modelling using scenarios. IEEE Transactions on Software Engineering, Special Issue on Scenario Management, Vol. 24, No. 12, Dec. 1998.
59. Rolland, C., 2002, L'e-lyee: l'ecritoire and lyeeall, Information and software Technology 44 (2002) 185-194
60. Rolland, C., Grosz, G., and Kla, R., 1999, Experience with goal-scenario coupling. In requirements engineering, Proceedings of the Fourth IEEE International Symposium on Requirements Engineering, Limerik, Ireland,
61. Ross, D. T., and Schoman, K.E., 1977, Structured analysis for requirements definition. IEEE Transactions on Software Engineering, Vol. 3, No 1, 6-15.
62. Robinson, W. N., 1989, "integrating multiple specifications using domain goals", Proc. IWSSD-5-5th Intl. Workshop on Software Specification and Design, IEEE, 1989, 219-225.
63. Schank, R. C., 1973, Identification of conceptualisations underlying natural language. In "Computer models of thought and language", R.C. Shank, K.M. Colby (Eds.), Freeman, San Francisco, pp. 187-247.
64. Sommerville I., 1996, Software Engineering. Addison Wesley.
65. Sommerville, I., and Sawyer, P., 1997, Requirements engineering. Worldwide Series in Computer Science, Wiley.
66. Standish Group, 1995, Chaos. Standish Group Internal Report, http://www.standishgroup.com/chaos.html
67. Sutcliffe, A.G., Maiden, N.A., Minocha, S., and Manuel D., 1998, "Supporting scenario-based requirements engineering", IEEE Trans. Software Eng. Vol. 24, no. 12, Dec. 1998, 1072-1088.
68. Tawbi, M., 2001, Crews-L'Ecritoire: un guidage outillé du processus d'Ingénierie des Besoins. Ph.D. Thesis University of Paris 1, October 2001.
69. Thayer, R., Dorfman, M. (eds.), System and software requirements. IEEE Computer Society Press. 1990.
70. Vicente, K. J., and Rasmussen, J., 1992, Ecological interface design: Theoretical foundations. IEEE Trans. on Systems, Man, and Cybernetics, Vol. 22, No. 4 July/August 1992.
71. Yu, E., 1994, Modelling strategic relationships for process reengineering. Ph.D. Thesis, Dept. Computer Science, University of Toronto, Dec. 1994.
72. Yue, K., 1987, What does it mean to say that a specification is complete?, Proc. IWSSD-4. Four International Workshop on Software Specification and Design, Monterrey, 1987.
73. Zave P., and Jackson M., 1997, "Four dark corners of requirements engineering", ACM Transactions on Software Engineering and Methodology, 1-30. 1997.