Inferring declarative requirements specifications from operational scenarios

IEEE Transactions on Software Engineering

Volumn 24, Issue 12, 1998, Pages 1089-1114

  Van Lamsweerde, Axel ^a  

^a UNIVERSITÉ CATHOLIQUE DE LOUVAIN   (Belgium)

Author keywords

Goal oriented requirements engineering; Inductive inference of specifications; Lightweight formal methods; Scenario based requirements elicitation; Specification refinement and analysis

Indexed keywords

COMPUTER HARDWARE DESCRIPTION LANGUAGES; COMPUTER SOFTWARE SELECTION AND EVALUATION; FORMAL LOGIC; HIGH LEVEL LANGUAGES; INFERENCE ENGINES; REQUIREMENTS ENGINEERING;

GOAL-ORIENTED REQUIREMENTS ENGINEERING; LIGHTWEIGHT FORMAL METHODS; SCENARIO-BASED REQUIREMENTS ELICITATION;

SOFTWARE ENGINEERING;

EID: 0032296216     PISSN: 00985589     EISSN: None     Source Type: Journal    
DOI: 10.1109/32.738341     Document Type: Article

References (74)

1. J.S. Anderson and S. Fickas, "A Proposed Perspective Shift: Viewing Specification Design as a Planning Problem," Proc. IWSSD-5, Fifth Int'l Workshop Software Specification and Design, pp. 177-184, IEEE, 1989.
2. A.I. Anton, W.M. McCracken, and C. Potts, "Goal Decomposition and Scenario Analysis in Business Process Reengineering," Proc. CAKE'94, Sixth Conf. Advanced Information Systems Eng., pp. 94-104, Lecture Notes in Computer Science 811, Springer-Verlag, 1994.
3. K.M. Benner, "The ARIES Simulation Component," Proc. KBSE'93.
4. K.M. Benner, M.S. Feather, W.L. Johnson, and L.A. Zorman, "Utilizing Scenarios in the Software Development Process," Information System Development Process, Elsevier Science, B.V. NorthHolland, pp. 117-134,1993.
5. F. Bergadano and D. Gunetti, "Testing by Means of Inductive Program Learning," ACM Trans. Software Eng. and Methodology, vol. 5, no. 2, Apr. 1996.
6. A.W. Biermann and R. Krishnaswamy, "Constructing Programs from Example Computations," IEEE Trans. Software Eng., vol. 2, no. 9, pp. 141-153,1976.
7. A. Borgida, J. Mylopoulos, and R. Reiter, "On the Frame Problem in Procedure Specifications," IEEE Trans. Software Eng., vol. 21, no. 10, pp. 785-798, Oct. 1995.
8. RJ. Brachman and H.J. Levesque, eds., Readings in Knowledge Representation. Morgan Kaufmann, 1985.
9. J.M. Carroll and M.B. Rosson, "Narrowing the Specification Implementation Gap in Scenario-Based Design," Scenario-Based Design: Envisioning Work and Technology in System Development, J.M. Carroll, éd., pp. 247-278, John Wiley & Sons, 1995.
10. E.M. Clarke and E.A. Emerson, "Automatic Verification of FiniteState Concurrent Systems Using Temporal Logic Specifications," ACM Trans. Program. Language Systems ,vol. 8, no. 2, pp. 244-263, 1986.
11. A. Dardenne, A. van Lamsweerde, and S. Fickas, "Goal-Directed Requirements Acquisition," Science of Computer Programming, vol. 20, pp. 3-50,1993.
12. A. Dardenne, "On the Use of Scenarios in Requirements Acquisition," Technical Report CIS-TR-93-17, Dept. of Computer and Information Science, Univ. of Oregon, Aug. 1993.
13. R. Darimont and A. van Lamsweerde, "Formal Refinement Patterns for Goal-Driven Requirements Elaboration," Proc. FSE'4Fourth ACM SIGSOFT Symp. Foundations of Software Eng., pp. 179190, San Francisco, Oct. 1996.
14. R. Darimont and E. Delor, "Goal-Driven Requirements Specification of a Copyright Tracking System," CEDITI Deliverable, Sept. 1996. In French
15. R. Darimont, E. Delor, P. Massonet, and A. van Lamsweerde, "GRAIL/KAOS: An Environment for Goal-Driven Requirements Engineering," Proc. ICSE'97-19th Int'l Conf. Software Eng., Boston, Apr. 1997.
16. J. Desharnais, M. Frappier, R. Khedri, and A. Mili, "Integration of Sequential Scenarios," Proc. ESEC'97-Sixth European Software Eng. Conf., pp. 310-326, Zurich, Lecture Notes in Computer Science 1301, Springer-Verlag, Sept. 1997.
17. J. Douglas and R.A. Kemmerer, "Aslantest: A Symbolic Execution Tool for Testing ASLAN Formal Specifications," Proc. ISTSTA '94-Int'l Symp. Software Testing and Analysis, ACM Software Engineering Notes, pp. 15-27,1994.
18. E. Dubois, Ph. Du Bois, and M. Petit, "Object-Oriented Requirements Analysis: An Agent Perspective," Proc. ECOOP'93-Seventh European Conf. Object-Oriented Programming, pp. 458-481, Lecture Notes in Computer Science 707, Springer-Verlag, 1993.
19. M. Feather, "Language Support for the Specification and Development of Composite Systems," ACM Trans. Programming Languages and Systems, vol. 9, no. 2, pp. 198-234, Apr. 1987.
20. M. Feather, "Towards a Derivational Style of Distributed System Design," Automated Software Eng., vol. 1, no. 1, pp. 31-60,1994.
21. M. Feather, S. Fickas, A. van Lamsweerde, and C. Ponsard, "Reconciling System Requirements and Runtime Behaviour," Proc. IWSSD'98-Ninth Int'l Workshop Software Specification and Design, Isobe, IEEE CS Press, Apr. 1998.
22. S. Fickas and R. Helm, "Knowledge Representation and Reasoning in the Design of Composite Systems," IEEE Trans. Software Eng., pp. 470-482, June 1992.
23. M. Fowler, UML Distilled-Applying the Standard Object Modeling Language. Addison-Wesley, 1997.
24. P.K. Garg and S. Bhansali, 'Process Programming by Hindsight," Proc. ICSE14-14th Int'l Conf. Software Eng., Melbourne, pp. 280293,1992.
25. M. Glinz, "An Integrated Formal Model of Scenarios Based on Statecharts," Proc. ESEC'95-Fourth European Software Eng. Conf., Lecture Notes in Computer Science 989, Springer-Verlag, 1995.
26. D. Gries, The Science of Programming. Springer-Verlag, 1981.
27. RJ. Hall, "Systematic Incremental Validation of Reactive Systems via Sound Scenario Generalization," Automated Software Eng., vol. 2, pp. 131-166,1995.
28. RJ. Hall, "Explanation-Based Scenario Generation for Reactive System Models," Proc. ASE'98, Hawaii, Oct. 1998.
29. P. Haumer, K. Pohl, and K. Weidenhaupt, "Requirements Elicitation and Validation with Real World Scenes," CREWS Report 9816,1998.
30. C. Heitmeyer, R. Jeffords, and B. Labaw, "Automated Consistency Checking of Requirements Specifications," ACM Trans. Software Eng. and Methodology vol. 5, no. 3, pp. 231-261, July 1996.
31. S. Hekmatpour and D. Ince, Software Prototyping, Formal Methods, and VDM. Addison-Wesley, 1988.
32. P. Hsia, J. Samuel, J. Gao, D. Kung, Y. Toyoshima, and C. Chen, "Formal Approach to Scenario Analysis," IEEE Software, pp. 3341, Mar. 1994.
33. ITU-T, Message Sequence Charts. Recommendation Z.120,1993.
34. I. Jacobson, M. Christerson, P. Jonsson, and G. Overgaard, ObjectOriented Software Engineering: A Use Case Driven Approach. Addison-Wesley, ACM Press, 1993.
35. M. Jackson and P. Zave, "Domain Descriptions," Proc. RE'93First Int'l IEEE Symp. Requirements Eng., pp. 56-64, Jan. 1993.
36. M. Jackson, Software Requirements & Specifications-A Lexicon of Practice, Principles and Prejudices. ACM Press, Addison-Wesley, 1995.
37. D. Jackson, "Elements of Style: Analyzing a Software Design Feature with a Counterexample Detector," Proc. ACM ISSTA'96, pp. 239-249, San Diego, 1996.
38. S.E. Keller, L.G. Kahn, and R.B. Panara, "Specifying Software Quality Requirements with Metrics," Tutorial: System and Software Requirements Engineering, R.H. Thayer and M. Dorfman, eds., pp. 145-163, IEEE CS Press, 1990.
39. V Kelly and U. Nonnenmann, "Reducing the Complexity of Formal Specification Acquisition," Automated Software Design, M. Lowry and R. McCartne, eds., pp. 41-64, AAAI Press, 1991.
40. R. Koymans, Specifying Message Passing and Time-Critical Systems with Temporal Logic, Lecture Notes in Computer Science 651, Springer-Verlag, 1992.
41. A. van Lamsweerde, "Learning Machine Learning," Introducing a Logic Based Approach to Artificial Intelligence, A. Thayse, ed., vol. 3, pp. 263-356, John Wiley & Sons, 1991.
42. A. van Lamsweerde, R. Darimont, and P. Massonet, "GoalDirected Elaboration of Requirements for a Meeting Scheduler: Problems and Lessons Learned," Proc. RE'95-Second Int'l Symp. on Requirements Eng., York, IEEE, 1995.
43. A. van Lamsweerde, "Divergent Views in Goal-Driven Requirements Engineering," Proc. Viewpoints'96-ACM SIGSOFT Workshop Viewpoints in Software Development, Oct. 1996.
44. A. van Lamsweerde and E. Letier, "Integrating Obstacles in GoalDriven Requirements Engineering," Proc. ICSE-98: 20th Int'l Conf. Software Eng., Kyoto, Apr. 1998.
45. A. van Lamsweerde, R. Darimont, and E. Letier, "Managing Conflicts in Goal-Driven Requirements Engineering," IEEE Trans. Sofware. Eng., special issue on Inconsistency Management in Software Development, Nov. 1998.
46. J.C. Leite and P.A. Freeman, "Requirements Validation Through Viewpoint Resolution," IEEE Trans. Software Eng., pp. 1,253-1,269, Dec. 1991.
47. J.C. Leite, G. Rossi, F. Balaguer, V. Maiorana, G. Kaplan, G. Hadad, and A. Oliveros, "Enhancing a Requirements Baseline with Scenarios," Proc. RE'97-Third Int'l Symp. Requirements Eng., pp. 44-53, Anapolis, IEEE, 1997.
48. Z. Manna and A. Pnueli, The Temporal Logic of Reactive and Concurrent Systems. Springer-Verlag, 1992.
49. Z. Manna and the STep Group, "STeP: Deductive-Algorithmic Verification of Reactive and Real-Time Systems," Proc. CAV'96Eighth Int'l Conf. Computer-Aided Vérification, pp. 415-418, Lecture Notes in Computer Science 1102. Springer-Verlag, July 1996.
50. D. Marca and M. Harandi, "Problem Set for the Fourth Int'l Workshop on Software Specification and Design," Proc. Fourth Int'I Workshop Software Specification and Design, IEEE CS Press, 1987.
51. K.L. McMillan, Symbolic Model Checking: An Approach to the State Explosion Problem. Kluwer, 1993.
52. B. Meyer, "On Formalism in Specifications," IEEE Software, vol. 2, no. 1, pp. 6-26, Jan. 1985.
53. T. Mitchell, "Generalization as Search," Artificial Intelligence, vol. 18, pp. 203-226,1982.
54. J. Mylopoulos, L. Chung, and B. Nixon, "Representing and Using Nonfunctional Requirements: A Process-Oriented Approach," IEEE Trans. Sofware. Eng., vol. 18, no. 6, pp. 483-497, June 1992.
55. N.J. Nilsson, Principles of Artificial Intelligence. Springer-Verlag, 1982.
56. B. Nuseibeh, J. Kramer, and A. Finkelstein, "A Framework for Expressing the Relationships Between Multiple Views in Requirements Specifications," IEEE Trans. Software Eng., vol. 2, no. 10, pp. 760-773, Oct. 1994.
57. D.L. Parnas and J. Madey, "Functional Documents for Computer Systems," Science of Computer Programming, vol. 25, pp. 41-61, 1995.
58. C. Potts, K. Takahashi, and A.I. Anton, "Inquiry-Based Requirements Analysis," IEEE Software, pp. 21-32, Mar. 1994.
59. C. Potts, "Using Schematic Scenarios to Understand User Needs," Proc. DIS'95-ACM Symp. Designing Interactive Systems: Processes, Practices and Techniques, Univ. of Michigan, Aug. 1995.
60. B. Potter, J. Sinclair, and D. Till, An Introduction to Formal Specification and Z, second edition. Prentice Hall, 1996.
61. B. Regnell, K. Kimbler, and A. Wesslen, "Improving the Use Case Driven Approach to Requirements Engineering," Proc. RE'95Second Int'l Symp. Requirements Eng., pp. 40-47, York, IEEE, 1995.
62. W.N. Robinson, "Integrating Multiple Specifications Using Domain Goals," Proc. IWSSD-5-Fifth Int'l Workshop Software Specification and Design, pp. 219-225, IEEE, 1989.
63. C. Rolland, C. Ben Achour, C. Cauvet, J. Ralyte, A. Sutcliffe, N. Maiden, M. Jarke, P. Haumer, K. Pohl, E. Dubois, and P. Heymas, "A Proposal for Scenario Classification Framework," Requirements Eng. J., vol. 3, no. 1,1998.
64. C. Rolland and C. Ben Achour, "Guiding the Construction of Textual Use Case Specifications," Data and Knowledge Eng. }., vol. 25, nos. 1-2, pp. 125-160, Mar. 1998.
65. C. Rolland, C. Souveyet, and C. Ben Achour, "Guiding Goal Modelling Using Scenarios," CREWS Report Series no. 98-27.
66. D. Rosca, S. Greenspan, M. Feblovitz, and C. Wild, "A Decision Making Methodology in Support of the Business Rules Lifecycle," Proc. RE'97-Third Int'l Symp. Requirements Eng., pp. 236-246, Anapolis, IEEE, 1997.
67. K.S. Rubin and J. Goldberg, "Object Behaviour Analysis," Comm. ACM, vol. 35, no. 9, pp. 48-62, Sept. 1992.
68. J. Rumbaugh, M. Blaha, W. Prmerlani, F. Eddy, and W. Lorensen, Object-Oriented Modelling and Design. Prentice Hall, 1991.
69. I. Sommerville and P. Sawyer, Requirements Engineering: A Good Practice Guide. John Wiley & Sons, 1997.
70. A. Sutcliffe, "A Technique Combination Approach to Requirements Engineering," Proc. RE'97-Third Intl. Symp. Requirements Eng., pp. 65-74, Anapolis, IEEE, 1997.
71. A. Sutcliffe, N. Maiden, S. Minocha, and D. Manuel, "Supporting Scenario-Based Requirements Engineering," CREWS Report 9808,1998.
72. K. Weidenhaupt, K. Pohl, M. Jarke, and P. Haumer, "Scenario Usage in System Development: A Report on Current Practice," IEEE Software, Mar. 1998.
73. K. Yue, "What Does It Mean to Say that a Specification is Complete?" Proc. IWSSD-4, Fourth Int'l Workshop Software Specification and Design, Monterey, 1987.
74. P. Zave and M. Jackson, "Four Dark Corners of Requirements Engineering," ACM Trans. Software Eng. and Methodology, pp. 1-30, 1997.