Building formal requirements models for reliable software

Lecture Notes in Computer Science (including subseries Lecture Notes in Artificial Intelligence and Lecture Notes in Bioinformatics)

Volumn 2043, Issue , 2001, Pages 1-20

  van Lamsweerde, Axel ^a  

^a UNIVERSITÉ CATHOLIQUE DE LOUVAIN   (Belgium)

Author keywords

[No Author keywords available]

Indexed keywords

LIFE CYCLE; REQUIREMENTS ENGINEERING; SPECIFICATIONS;

AGENT BEHAVIOR; COMMON INTERFACES; MULTI-PARADIGM; NON-FUNCTIONAL REQUIREMENTS; RELATIVE STRENGTH; REQUIREMENTS MODELS; SOFTWARE LIFE CYCLES; SYSTEM MODELING;

SOFTWARE AGENTS;

EID: 34247104100     PISSN: 03029743     EISSN: 16113349     Source Type: Book Series    
DOI: 10.1007/3-540-45136-6_1     Document Type: Conference Paper

References (32)

1. Bay Area Rapid Transit District, Advance Automated Train Control System, Case Study Description. Sandia National Labs, http://www.hcecs.sandia.gov/bart.htm.
2. 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.
3. B.W. Boehm, Software Engineering Economics. Prentice-Hall, 1981.
4. F.P. Brooks “No Silver Bullet: Essence and Accidents of Software Engineering”. IEEE Computer, Vol. 20 No. 4, April 1987, pp. 10-19.
5. A. Dardenne, A. van Lamsweerde and S. Fickas, “Goal-Directed Requirements Acquisition”, Science of Computer Programming, Vol. 20, 1993, 3-50.
6. R. Darimont and A. van Lamsweerde, “Formal Refinement Patterns for Goal-Driven Requirements Elaboration”, Proc. FSE’4 - Fourth ACM SIGSOFT Symposium on the Foundations of Software Engineering, San Francisco, October 1996, 179-190.
7. 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.
8. European Software Institute, “European User Survey Analysis”, Report USV_EUR 2.1, ESPITI Project, January 1996.
9. C. Heitmeyer, R. Jeffords and B. Labaw, “Automated Consistency Checking of Requirements Specificatons”, ACM Transactions on Software Engineering and MethodologyVol. 5 No. 3, July 1996, 231-261.
10. 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.
11. M. Jackson, Software Requirements & Specifications - A Lexicon of Practice, Principles and Pejudices. ACM Press, Addison-Wesley, 1995.
12. R. Koymans, Specifying message passing and time-critical systems with temporal logic, LNCS 651, Springer-Verlag, 1992.
13. 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.
14. 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.
15. A. van Lamsweerde, “Requirements Engineering in the Year 00: A Research Perspective”, Keynote paper, Proc. ICSE’2000 - 22nd Intl. Conference on Software Engineering, IEEE Press, June 2000.
16. A. van Lamsweerde, “Formal Specification: a Roadmap”. In The Future of Software Engineering, A. Finkelstein (ed.), ACM Press, 2000.
17. A. van Lamsweerde and E. Letier, “Handling Obstacles in Goal-Oriented Requirements Engineering”, IEEE Transactions on Software Engineering, Special Issue on Exception Handling, October 2000.
18. þ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.
19. E. Letier, Reasoning About Agents in Goal-Oriented Requirements Engineering. PhD Thesis, University of Louvain, 2001.
20. N. Leveson, Safeware - System Safety and Computers. Addison-Wesley, 1995.
21. Z. Manna and A. Pnueli, The Temporal Logic of Reactive and Concurrent Systems, Springer-Verlag, 1992.
22. P. Massonet and A. van Lamsweerde, “Analogical Reuse of Requirements Frameworks”, Proc. RE-97 - 3rd Int. Symp. on Requirements Engineering, Annapolis, 1997, 26-37.
23. B. Meyer, “On Formalism in Specifications”, IEEE Software, Vol. 2 No. 1, January 1985, 6-26.
24. Mylopoulos, J., Chung, L., Nixon, B., “Representing and Using Nonfunctional Requirements: A Process-Oriented Approach”, IEEE Trans. on Sofware. Engineering, Vol. 18 No. 6, June 1992, pp. 483-497.
25. J. Mylopoulos, L. Chung and E. Yu, “From Object-Oriented to Goal-Oriented Requirements Analysis”, Communications of the ACM, Vol. 42 No. 1, January 1999, 31-37.
26. 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.
27. S. Owre, J. Rushby, and N. Shankar, “Formal Verification for Fault-Tolerant Architectures: Prolegomena to the Design of PVS”, IEEE Transactions on Software EngineeringVol. 21 No. 2, Feb. 1995, 107-125.
28. D.L. Parnas and J. Madey, “Functional Documents for Computer Systems”, Science of Computer Programming, Vol. 25, 1995, 41-61.
29. B. Potter, J. Sinclair and D. Till, An Introduction to Formal Specification and Z. Second edition, Prentice Hall, 1996.
30. J. Rumbaugh, I. Jacobson and G Booch, The Unified Modeling Language Reference Manual. Addison-Wesley, Object Technology Series, 1999.
31. The Standish Group, “Software Chaos”, http://www.standishgroup.com/chaos.html.
32. K. Yue, “What Does It Mean to Say that a Specification is Complete?”, Proc. IWSSD-4, Fourth International Workshop on Software Specification and Design, IEEE, 1987.