Requirements engineering in the year 00: a research perspective

Proceedings - International Conference on Software Engineering

Volumn , Issue , 2000, Pages 5-19

  van Lamsweerde, Axel ^a  

^a UNIVERSITÉ CATHOLIQUE DE LOUVAIN   (Belgium)

Author keywords

[No Author keywords available]

Indexed keywords

CONFLICT MANAGEMENT; DOMAIN ANALYSIS;

COMPUTER ARCHITECTURE; COMPUTER SOFTWARE; CONSTRAINT THEORY; SOFTWARE ENGINEERING; SPECIFICATIONS;

REQUIREMENTS ENGINEERING;

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

References (115)

1. J.R. Abrial, "The Specification Language Z: Syntax and Semantics". Programming Research Group, Oxford Univ., 1980.
2. E.J. Amoroso, Fundamentals of Computer Security. Prentice-Hall, 1994.
3. R.M. Baker, N.M. Goldman, and D.S. Wile, "Operational Specification as the Basis for Rapid Prototyping", ACM SIGSOFT Softw. Eng. Notes Vol. 7 No. 5, Dec. 1982,3-16.
4. Bay Area Rapid Transit District, Advance Automated Train Control System, Case Study Description. Sandia National Labs, http://www.hcecs.sandia.gov/bart. htm.
5. P. Behm, P. Benoit, A. Faivre and J.M. Meynadier, "Mé téor: A Successful Application of B in a Large Project", Proc. FM-99 - World Conference on Formal Methods in the Development of Computing Systems, LNCS 1708, Springer-Verlag, 1999,369-387.
6. T.E. Bell and T.A. Thayer, "Software Requirements: Are They Really a Problem?", Proc. ICSE-2: 2nd Intrnational Conference on Software Enginering, San Francisco, 1976,61-68.
7. 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 Publisher B.V. (North-Holland), 1993, 117-134.
8. V. Berzins and Luqi, Software Engineering with Abstractions. Addison-Wesley, 1991.
9. B.W. Boehm, Software Engineering Economics. Prentice-Hall, 1981.
10. B. W. Boehm, P. Bose, E. Horowitz, and Ming June Lee, "Software Requirements Negotiation and Renegotiation Aids: A Theory-W Based Spiral Approach", Proc. ICSE-17 - 17th Intl. Conf: on Software Engineering, Seattle, 1995, pp. 243-253.
11. R.J. Brachman and H.J. Levesque (eds.), Readings in Knowledge Representation, Morgan Kaufmann, 1985.
12. M. Brodie, J. Mylopoulos, and J. Schmidt (eds.), On Conceptual Modeling: Perspectives from Artificial Intelligence, Databases, and Programming Languages. Springer-Verlag, 1984.
13. F.P. Brooks "No Silver Bullet: Essence and Accidents of Software Engineering". IEEE Computer, Vol. 20 No. 4, April 1987, pp. 10-19.
14. J. Bubenko, "Information Modeling in the Context of System Development", Proc. IFIP Congress '80, North Holland, 1980,395-411.
15. R.W. Butler, S.P. Miller, J.N. Potts and V.A. Carreno, "A Formal Methods Approach to the Analysis of Mode Confusion", Proceedings DASC98 - 17th Digital Avionics Systems Conference, Seattle, November 1998. See also http://shemesh.larc.nasa.gov/fm/fm-now-mode-confusion.html.
16. W. Chan, R. Anderson, P. Beame, S. Burns F. Modugno, D. Notkin, and J. Reese, "Model Checking Large Software Specifications", IEEE Transactions on Software Engineering Vol. 24 No. 7, 1998,498-520.
17. P. Chen, "The Entity Relationship Model - Towards a Unified View of Data", ACM Transactions on Database Systems, vol. 1, no. 1, March 1976,9-36.
18. E.M. Clarke, O. Grumberg, and D.A. Peled, Model Checking. MIT Press, 1999.
19. A. Dardenne, S. Fickas and A. van Lamsweerde, "Goal- Directed Concept Acquisition in Requirements Elicitation", Proc. IWSSD-6 - 6th Intl. Workshop on Software Specification and Design, Como, 1991, 14-21.
20. A. Dardenne, A. van Lamsweerde and S. Fickas, "Goal-Directed Requirements Acquisition", Science of Computer Programming, Vol. 20, 1993, 3-50.
21. R. Darimont and A. van Lamsweerde, "Formal Refinement Patterns for Goal-Driven Requirements Elaboration ", Proc. FSE'I - Fourth ACM SIGSOFT Symp. on the Foundations of Software Engineering, San Francisco, October 1996, 179-190.
22. T. DeMarco, Structured Analysis and System Specification, Yourdon Press, 1978.
23. E. Dubois, Ph. Du Bois and M. Petit, "Object-Oriented Requirements Analysis: An Agent Perspective", Proc. ECOOP93 - 7th European Conf. on Object-Oriented Programming, Springer-Verlag LNCS 707, 1993,458-481.
24. M.B. Dwyer, G.S. Avrunin and J.C. Corbett, "Patterns in Property Specifications for Finite-State Verification", Proc. ICSE-99: 21th Intmational Conference on Software Enginering, Los Angeles, 411-420.
25. S. Easterbrook, "Resolving Requirements Conflicts with Computer-Supported Negotiation". In Requirements Engineering: Social and Technical Issues, M. Jirotka and J. Goguen (Eds.), Academic Press, 1994,41-65.
26. European Software Institute, "European User Survey Analysis", Report USV-EUR 2.1, ESPITI Project, January 1996.
27. S.Faulk, J. Brackett, P. Ward and J. Kirby, "The CORE Method for Real-Time Requirements", IEEE Software, September 1992.22-33.
28. M. Feather, "Language Support for the Specification and Development of Composite Systems", ACM Trans. on Programming Languages and Systems 9(2), Apr. 87, 198-234.
29. M. Feather, S. Fickas, A. Finkelstein, and A. van Lamsweerde, "Requirements and Specification Exemplars", Automated Software Engineering Vol. 4, 1997,419-438.
30. M. Feather, S. Fickas, A. van Lamsweerde, and C. Ponsard, "Reconciling System Requirements and Runtime Behaviour", Proc. IWSSD'98 - 9th International Workshop on Software Specification and Design, Isobe, IEEE CS Press, April 1998.
31. S. Fickas and R. Helm, "Knowledge Representation and Reasoning in the Design of Composite Systems", IEEE Trans. on Software Engineering, June 1992,470-482.
32. A. Finkelstein and C. Potts, "Building Formal Specifications Using Structured Common Sense", Proc. IWSSD-4 - 4th International Workshop on Software Specification and Design (Monterey, Ca.), IEEE, April 1987, 108-113.
33. Gamma, E., Helm, R., Johnson, R., Vlissides, J., Design Patterns - Elements of Reusable Object-Oriented Software, Addison-Wesley, 1995.
34. D. Garlan, R. Monroe and D. Wile, "ACME: An Architecture Description Interchange Language", Proceedings CASCON97, Toronto, Nov. 1997, 169-183.
35. J. Goguen and C. Linde, "Techniques for Requirements Elicitation", Proc. RE'93 - First IEEE Symposium on Requirements Engineering, San Diego, 1993, 152-164.
36. J. Goguen and M. Jirotka (eds.), Requirements Engineering: Social ad Technical Issues. Academic Press, 1994.
37. O. Gotel and A. Finkelstein, "Contribution Structures", Proc. RE'95 - 2nd Intl. IEEE Symp. on Requirements Engineering, York, IEEE, 1995, 100-107.
38. S.J. Greenspan, J. Mylopoulos, and A. Borgida, "Capturing More World Knowledge in the Requirements Specification", Proc. ICSE-6: 6th Intrnational Conference on Sofiware Enginering, Tokyo, 1982.
39. S.J. Greenspan, A. Borgida and J. Mylopoulos, "A Requirements Modeling Language and its Logic", Information Systems Vol. 11 No. 1, 1986.9-23.
40. D. Harel, "Statecharts: A Visual Formalism for Complex Systems", Science of Computer Programming Vol. 8, 1987
41. D.Harel, H. Lachover, A. Naamad, A. Pnueli, M. Politi, R. Sherman, A. Shtull-Trauring, and M. Trakhtenbrot, "STATEMATE: A Working Environment for the Development of Complex Reactive Systems", IEEE Transactions on Software Engineering, Vol. 16 No. 4, April 1990,403-414.
42. D. Harel, "The STATEMATE Semantics of Statecharts", ACM Transactions on Software Engineering and Methodology Vol. 5 NO.4, 1996,293-333.
43. M.P. Heimdahl and N.G. Leveson, "Completeness and Consistency in Hierarchical State-Based Requirements", IEEE Transactions on Software Engineering Vol. 22 No. 6, June 1996,363-377.
44. C. Heitmeyer, R. Jeffords and B. Labaw, "Automated Consistency Checking of Requirements Specificatons", ACM Transactions on Software Engineering and Methodology Vol. 5 NO. 3, July 1996, 231-261.
45. C. Heitmeyer, J. Kirkby, B. Labaw, M. Archer and R. Bharadwaj, "Using Abstraction and Model Checking to Detect Safety Violations in Requirements Specifications", IEEE Transactions on Software Engineering Vol. 24 No. 11, November 1998,927-948.
46. C. Heitmeyer, J. Kirkby, B. Labaw, and R. Bharadwaj, "SCR*: A Toolset for specifying and Analyzing Software Requirements", Proc. CAV'98 - 10th Annual Conference on Comuter-Aided Verification, Vancouver, 1998,526-531.
47. K.L. Heninger, "Specifying Software Requirements for Complex Systems: New Techniques and their Application", IEEE Transactions on Software Engineering Vol. 6 No. 1, January 1980,2-13.
48. G.E Hice, W.S. Turner, and L.F. Cashwell, System Development Methodology. North Holland, 1974.
49. G. Holzman, "The Model Checker SPIN", IEEE Trans. on Software Engineering Vol. 23 No. 5, May 1997, 279-295.
50. P. Hsia, J. Samuel, J. Gao, D. Kung, Y. Toyoshima and C. Chen, "Formal approach to scenario analysis", IEEE Software, Mar 1994, 33-41.
51. A. Hunter and B. Nuseibeh, "Managing Inconsistent Specifications: Reasoning, Analysis and Action", ACM Transactions on Software Engineering and Methodology, Vol. 7 No. 4. October 1998,335-367.
52. M.A. Jackson, "Information Systems: Modeling, Sequencing, and Transformation", Proc. ICSE-3: 3rd Intmational Conference on Software Enginering, Munich, 1978,72-81.
53. M. Jackson, Software Requirements & Specifications - A Lexicon of Practice, Principles and Pejudices. ACM Press, Addison-Wesley, 1995.
54. I. Jacobson, M. Christerson, P. Jonsson and G. Overgaard, Object-Oriented Software Engineering. A Use Case Driven Approach. Addison-Wesley, ACM Press, 1993.
55. M.Jarke and R. Kurki-Suonio (eds.), Special Issue on Scenario Management, IEEE Trans. on Sofware. Engineering, December 1998.
56. A.J. Jones and M. Sergot, "On the Characterization of Law and Computer Systems: the Normative System Perspective", in J.Ch. Meyer and R.J. Wieringa (Eds.), Deontic Logic in Computer Science - Normative System Specification, Wiley, 1993.
57. S. Kent, T. Maibaum and W. Quirk, "Formally Specifying Temporal Constraints and Error Recovery", Proc. RE'93 - 1st Intl. IEEE Symp. on Requirements Engineering, Jan. 1993,208-215.
58. R. Koymans, Specifying message passing and time-critical systems with temporal logic, LNCS 651, Springer-Verlag, 1992.
59. A. van Lamsweerde and E. Letier, "Integrating Obstacles in Goal-Driven Requirements Engineering", Proc. ICSE-98: 20th International Conference on Software Enginering, Kyoto, April 1998.
60. A. van Lamsweerde, R. Darimont and E. Letier, "Managing Conflicts in Goal-Driven Requirements Engineering", IEEE Trans. on Sofware. Engineering, Special Issue on Inconsistency Management in Software Development, November 1998.
61. A. van Lamsweerde and L. Willemet, "Inferring Declarative Requirements Specifications from Operational Scenarios", IEEE Trans. on Sofware. Engineering, Special Issue on Scenario Management, December 1998, 1089-1114.
62. A. van Lamsweerde and E. Letier, "Handling Obstacles in Goal-Oriented Requirements Engineering", IEEE Transacrions on Software Engineering, Special Issue on Exception Handling, 2000.
63. A. van Lamsweerde, "Formal Specification: a Roadmap". In The Future of Software Engineering, A. Finkelstein (ed.), ACM Press, 2000.
64. Report of the Inquiry Into the London Ambulance Service, February 1993. The Communications Directorate, South West Thames Regional Authority, ISBN 0-905 133-70-6. See also the London Ambulance System home page, http://hsn.lond-amb. sthames.nhs.uk/http.dir/service/organisation/featurs/info.html.
65. E.Letier and A. van Lamsweerde, "KAOS in Action: the BART System". IFIP WG2.9 meeting, Flims, http://www.cis.gsu.edu/~wrobinso/ifip2- 9/Flims00.
66. N.G. Leveson, M.P. Heimdahl and H. Hildtreth, "Requirements Specification for Process-Control Systems", IEEE Transactions on Software Engineering Vol. 20 No. 9, September 1994,684-706.
67. N. Leveson, Software - System Safety and Computers. Addison-Wesley, 1995.
68. D. Luckham and J. Vera, "An Event-Based Architecture Definition Language", IEEE Transactions on Software Engineering, Vol. 21 No. 9, Sept. 1995,717-734.
69. R.R. Lutz, "Analyzing Software Requirements Errors in Safety-Critical, Embedded Systems", Proceedings RE'93 - First International Symposium on Requirements Engineering, San Diego, IEEE, 1993, 126-133.
70. J. Magee, N Dulay, S. Eisenbach and J Kramer, "Specifying Distributed Software Architectures", Proceedings ESEC'95 - 5th European Software Engineering Conference, Sitges, LNCS 989, Springer-Verlag, Sept. 1995, 137-153.
71. N.Maiden and A. Sutcliffe, "Exploiting Reusable Specifications Through Analogy", Communications of the ACM Vol. 35 NO. 4, 1993,55-64.
72. Z. Manna and A. Pnueli. The Temporal Logic of Reactive and Concurrent Systems, Springer-Verlag, 1992.
73. P. Massonet and A. van Lamsweerde, "Analogical Reuse of Requirements Frameworks", Proc. RE-97 - 3rd Inr. Symp. on Requirements Engineering, Annapolis, 1997,26-37.
74. K.L. McMillan, Symbolic Model Checking: An Approach to the State Explosion Problem, Kluwer, 1993.
75. B. Meyer, "On Formalism in Specifications", IEEE Software, Vol. 2 No. I, January 1985,6-26.
76. M. Moriconi, X. Qian, and R. Riemenschneider, "Correct Architecture Refinement", IEEE Transactions on Software Engineering, Vol. 21 No. 4, Apr. 1995,356-372.
77. E. Munford, "Participative Systems Design: Structure and Method, Systems, Objectives, Solutions, Vol. I, North-Holland, 1981,5-19.
78. Mylopoulos, J., Chung, L., Nixon, B., "Representing and Using Nonfunctional Requirements: A Process-Oriented Approach", IEEE Trans. on Sojivare. Engineering, Vol. 18 No. 6, June 1992, pp. 483-497.
79. J. Mylopoulos, "Information Modeling in the Time of the Revolution", Invited Review, Information Systems Vol. 23 No. 314, 1998, 127-155.
80. J. Mylopoulos, L. Chung and E. Yu, "From Object-Oriented to Goal-Oriented Requirements Analysis", Communications of the ACM, Vol. 42 No. I, January 1999,31-37.
81. N.J. Nilsson, Problem Solving Methods in Artificial Intelligence. McGraw Hill, 1971.
82. C. Niskier, T. Maibaum and D. Schwabe, "A Pluralistic Knowledge-Based Approach to Software Specification", Proc. ESEC-89 - 2nd European Software Engineering Conference, LNCS 387, September 1989,411-423.
83. B. A. Nixon, "Dealing with Performance Requirements During the Development of Information Systems", Proc. RE'93 - 1st Intl. IEEE Symp. on Requirements Engineering, Jan. 1993,42-49.
84. B. Nuseibeh, J. Kramer and A. Finkelstein, "A Framework for Expressing the Relationships Between Multiple Views in Requirements Specifications", IEEE Transactions on Software Engineering, Vol. 20 No. 10, October 1994,760-773.
85. D.L. Parnas and J. Madey, "Functional Documents for Computer Systems", Science of Computer Programming, Vol. 25, 1995,41-61
86. D. Perry and A. Wolf, "Foundations for the Study of Software Architecture", ACM Software Engineering Notes, Vol. 17 No. 4, October 1992,4042.
87. C. Potts, K. Takahashi and A.I. Anton, "Inquiry-Based Requirements Analysis", IEEE Software, March 1994, 21-32.
88. C. Potts, "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.
89. B. Potter, J. Sinclair and D. Till, An Introduction to Formal Specification and Z. Second edition, Prentice-Hall, 1996.
90. R. Quillian, Semantic Memory. In Semantic Information Processing, M. Minsky (ed.), MIT Press, 1968,227-270.
91. H.B. Reubenstein and R.C. Waters, "The Requirements Apprentice: Automated Assistance for Requirements Acquisition", IEEE Transactions on Software Engineering, Vol. 17 No. 3, March 1991,226-240.
92. R.A. Riemenschneider, "Checking the Correctness of Architectural Transformation Steps via Proof-Carrying Architectures", Proc. WI CSAI - First IFIP Conference on Software Architecture, San Antonio, February 1999.
93. Robinson, W.N., "Integrating Multiple Specifications Using Domain Goals", Proc. IWSSD-5 - 5th Intl. Workshop on Software Specification and Design, IEEE, 1989,219-225.
94. D.T. Ross, "Structured Analysis (SA): A Language for Communicating Ideas", IEEE Transactions on Software Engineering, Vol. 3, NO. 1, 1977, 16-34.
95. D.T. Ross and K.E. Schoman, "Structured Analysis for Requirements Definition", IEEE Transactions on Software Engineering, Vol. 3, No. 1, 1977,6-15.
96. K.S. Rubin and A. Goldberg, "Object Behavior Analysis", Communications of the ACM Vol. 35 No. 9, September 1992, 48-62.
97. J. Rumbaugh, M. Blaha, W. Prmerlani, F. Eddy and W. Lorensen, Object-Oriented Modeling and Design. Prentice-Hall, 1991.
98. J. Rumbaugh, I. Jacobson and G Booch, The Unified Modeling Language Reference Manual. Addison-Wesley, Object Technology Series, 1999.
99. M. Shaw and D. Garlan, Software Architecture: Perspectives on an Emerging Discipline. Prentice-Hall, 1996.
100. J. Smith and D. Smith, "Database Abstractions: Aggregation and Generalization", ACM Transactions on Database Systems Vol. 2 No. 2, 1977, 105-133.
101. J. Souquiéres and N. Levy, "Description of Specification Developments", Proc. RE'93 - First IEEE Symposium on Requirements Engineering, San Diego, 1993,216-223.
102. The Standish Group. Software Chaos. http://www.standishgroup.codchaos. html.
103. A. Sutcliffe, "A Technique Combination Approach to Requirements Engineering", Proc. RE'97 - 3rd Intl. Symp. on Requirements Engineering, Anapolis, IEEE, 1997,65-74.
104. R. Taylor, N. Medvidovic, K. Anderson J. Whitehead, J. Robbins, K. Nies, P. Oreizy, and D. Dubrow, "A Componentand Message-Based Architectural Style for CUI Software, IEEE Transactions on Software Engineering, Vol. 22 No. 6, June 1996,390-406.
105. J.M. Thompson, M.E. Heimdahl, and S.P. Miller, "Specification-Based Prototyping for Embedded Systems", Proc. ESEC/FSE'99, Toulouse, ACM SIGSOFT, LNCS 1687, Springer-Verlag, 1999, 163-179.
106. P.T. Ward and S.J. Mellor, Structured Development for Real-Time Systems. Prentice-Hall, 1985.
107. A. Wasserman, "A Specification Method for Inteactive Information Systems", Proceedings SRS - Specification of Reliable Software. IEEE Catalog No. 79 CH1401-9C, 1979,68-79.
108. K. Weidenhaupt, K. Pohl, M. Jarke, and P. Haumer, "Scenario Usage in System Development: A Report on Current Practice". IEEE Software, March 1998.
109. K. Yue, "What Does It Mean to Say that a Specification is Complete?', Proc. IWSSD-4, Fourth International Workshop on Software Specification and Design, Monterey, 1987.
110. E. Yu and J. Mylopoulos, "Understanding 'why' in software process modeling, analysis, and design", Proceedings ICSE'94, 16th International Conference on Software Engineering, Sorrento, IEEE, 1994, 159-168.
111. E. Yu, "Towards Modeling and Reasoning Support for Early-Phase Requirements Engineering", Proc. RE-97 - 3rd Int. Symp. on Requirements Engineering, Annapolis, 1997 226-235.
112. P. Zave and M. Jackson, "Conjunction as Composition", ACM Transactions on Software Engineering and Methodology, Vol. 2 No. 4, October 1993, 379-411.
113. P. Zave and M. Jackson, "Where Do Operations Come From? A Multiparadigm Specification Technique", IEEE Transactions on Software Engineering, Vol. 22 No. 7, July 1996,508-528.
114. P. Zave and M. Jackson, "Four Dark Corners of Requirements Engineering", ACM Transactions on Software Engineering and Methodology, 1997, 1-30.
115. P. Zave, "Classification of Research Efforts in Requirements Engineering", ACM Computing Surveys, Vol. 29 No. 4, 1997,315-321.