Formal methods and requirements engineering: Challenges and synergies

Journal of Systems and Software

Volumn 40, Issue 3, 1998, Pages 263-273

  Jones, Sara ^a   Till, David ^b   Wrightson, Ann M ^a  

^a UNIVERSITY OF HERTFORDSHIRE   (United Kingdom)

^b CITY UNIVERSITY   (United Kingdom)

Author keywords

[No Author keywords available]

Indexed keywords

COMPUTER AIDED SOFTWARE ENGINEERING; COMPUTER ARCHITECTURE; DATA ACQUISITION; MATHEMATICAL MODELS; THEOREM PROVING;

FORMALLY BASED REQUIREMENTS ACQUISITION STRATEGIES; REQUIREMENTS ENGINEERING (RE);

FORMAL LOGIC;

EID: 0032029005     PISSN: 01641212     EISSN: None     Source Type: Journal    
DOI: 10.1016/S0164-1212(97)00171-4     Document Type: Article

References (66)

1. Abrial, Jean-Raymond, The B book. Cambridge University Press, 1996.
2. Ben-Abdallah, H., Lee, I., and Kim, Y. S., The integrated specification and analysis of functional, temporal and resource requirements. In [Heitmeyer and Mylopoulos, 1997].
3. Bolton, D., Jones, S., Till, D., Furber, D., and Green, S., Knowledge-based support for requirements engineering. International Journal of Software Engineering and Knowledge Engineering, 2(2), (1992).
4. Butler, Ricky W., Caldwell, James L., Carreño, Victor A., Hayhurst, Kelly J., Holloway, C. Michael, Miner, Paul S., and Di Vito, Ben L., NASA Langley's research and technology-transfer program in formal methods. Technical report, NASA Langley Research Center, 1996. Also see:-http://atb-www.larc.nasa.gov/fm.html.
5. Carnegie Mellon University Software Engineering Institute, The Capability Maturity Model. Addison-Wesley, 1995. Chapter 6.
6. Cugola, G., di Nitto, E., Fuggetta, A., and Ghezzi, C. A framework for formalising inconsistencies and deviation in human-centred systems. Transactions on Software Engineering and Methodology, 1996.
7. Darimont, R., Delor, E., Massonet, P., and van Lamsweerde, A., GRAIL/KAOS: an environment for goal-directed requirements analysis integration and layout. In [Heitmeyer and Mylopoulos, 1997].
8. Davis, A. M., Software requirements: objects, functions and states. Prentice-Hall, 1993.
9. Di Vito, Ben L., Formalizing new navigation requirements for NASA's space shuttle. In Formal Methods Europe FME '96, volume 1051 of Lecture Notes in Computer Science, pages 160-178, Oxford, UK, March 1996. Springer-Verlag.
10. Di Vito, Ben L., and Roberts, Larry W., Using formal methods to assist in the requirements analysis of the Space Shuttle GPS Change Request. NASA Contractor Report 4752, NASA Langley Research Center, August 1996. Also see:-http://atb-www.larc.nasa.gov/fm.html.
11. Dill, David L., Drexler, Andreas J., Hu, Alan J., and Yang, C. Han, Protocol verification as a hardware design aid. In IEEE International Conference on Computer Design: VLSI in Computers and Processors, pages 522-525, 1992.
12. Du Bois, P., Dubois, E., and Zeippen, J.-M., On the use of a formal RE language: The generalized railroad crossing problem. In [Heitmeyer and Mylopoulos, 1997].
13. Easterbrook, S., and Callahan, J., Formal methods for V & V of partial specifications: An experience report. In [Heitmeyer and Myolopoulos, 1997].
14. Fiadeiro, J. L., and Maibaum, T., Interconnecting formalisms: supporting modularity, reuse and incrementality. In Proceedings of the Conference on Foundations of Software Engineering. ACM, 1995.
15. Fickas, Stephen, and Finkelstein, Anthony (editors), Proceedings of the First International Symposium on Requirements Engineering. IEEE Computer Society Press, 1993.
16. Finkelstein, A., Spanoudakis, G., and Till, D., Managing interference. In Proceedings of the International Workshop on Multiple Perspectives in Software Development. ACM, 1996.
17. Fuchs, N. E., Specifications are (preferably) executable. Software Engineering Journal, 7(5), (1992).
18. Gabbay, Dov M., Labelled deductive systems, volume 1: Foundations. Technical Report MPI-I-94-223, MaxPlanck-Institut für Informatik, Saarbrücken, Germany, 1994.
19. Garlan, D., and Perry, D. (eds), Special issue on software architecture. IEEE Transactions on Software Engineering, April 1995.
20. Garlan, D., and Shaw, M., An introduction to software architecture. In Advances in Software Engineering and Knowledge Engineering. World Scientific Publishing Co., 1993.
21. Garlan, David (editor), Proceedings of the Fourth ACM SIGSOFT Symposium on the Foundations of Software Engineering, 1996.
22. Goguen, J. A., and Messeguer, J., Unifying functional, object-oriented and relational programming with relational semantics. In B. Shriver and P. Wegner (editors), Research Directions in Object-Oriented Programming. MIT Press, 1987.
23. Gotel, O. C. Z., and Finkelstein, A. C. W., An analysis of the requirements traceability problem. In [Fickas and Finkelstein, 1993].
24. Gravell, A., and Henderson, P., Executing formal specifications need not be harmful. Software Engineering Journal, 11(3), (1996).
25. Guerra, S., Ryan, M. D., and Sernadas, A., Feature-oriented specification. Technical report, Computer Science Department, Birmingham University, November 1996.
26. Harker, S. D. P., and Eason, K. D., The change and evolution of requirements as a challenge to the practice of software engineering. In [Fickas and Finkelstein, 1993].
27. Harrison, Michael, and Zave, Pamela (editors), Proceedings of the Second International Symposium on Requirements Engineering. IEEE Computer Society Press, 1995.
28. Hayes, I. J., and Jones, C. B., Specifications are not (necessarily) executable. Software Engineering Journal, 4(6), (1989).
29. Heitmeyer, C., Labau, B., and Kiskis, D., Consistency checking of SCR-style requirements specifications. In [Harrison and Zave], 1995.
30. Heitmeyer, Connie, and Mylopoulos, John (editors), Proceedings of the Third International Symposium on Requirements Engineering. IEEE Computer Society Press, 1997.
31. Holland, J., Sönksen, P., Carson, E., and Cohen, B., The directorate information system at St. Thomas's hospital: a study in domain analysis. In [IEEE Computer Society Press, 1994].
32. Hunter, Anthony, and Nuseibeh, Bashar, Analysing inconsistent specifications. In [Heitmeyer and Mylopoulos, 1997].
33. IEEE Computer Society Press, Proceedings of the First International Conference on Requirements Engineering. IEEE Computer Society Press, 1994.
34. IEEE Computer Society Press, Proceedings of the Third ACM SIGSOFT Symposium on the Foundations of Software Engineering, 1995.
35. IEEE Computer Society Press, Proceedings of the Second International Conference on Requirements Engineering. IEEE Computer Society Press, 1996.
36. Jackson, Michael, Problems and requirements. In [Harrison and Zave, 1995].
37. Jackson, Michael, Software requirements and specifications: a lexicon of practice, principles and prejudices. Addison-Wesley, 1995.
38. Jackson, Michael, and Zave, Pamela, Domain descriptions. In [Fickas and Finkelstein, 1993].
39. Jarke, M., Bubenko, J., Rolland, C., Sutcliffe, A., and Vassiliou, Y., Theories underlying requirements engineering: an overview of NATURE at genesis. In [Fickas and Finkelstein, 1993].
40. Johnson, C. W., and Harrison, M. D., Prelog - a system for presenting and rendering logic specifications of interactive systems. In C. E. Vandoni and D. A. Duce (editors), Eurographics 90. Elsevier Science Publishers, 1990.
41. Kramer, J., and Ng, K., Animation of requirements specifications. Software Practice and Experience, 18(8), (1988).
42. Loomes, M., and Vinter, R., Formal methods: No cure for faulty reasoning. In F. Redmill and T. Anderson (editors), Safer Systems. Proceedings of the Fifth Safety-Critical Systems Symposium. Springer-Verlag, 1997.
43. Macfarlane, I. A., and Reilly, I., Requirements traceability in an integrated project environment. In [Harrison and Zave, 1995].
44. Madhavji, N. H., Impact of environmental evolution on requirements change. In [Heitmeyer and Mylopoulos, 1997].
45. Massonet, P., and van Lamsweerde, A., Analogical reuse of requirements frameworks. In [Heitmeyer and Mylopoulos, 1997].
46. McCluskey, T. L., Porteous, J. M., Naik, Y., Taylor, C. N., and Jones, S., A requirements capture method and its use in an air traffic control application. Software Practice and Experience, 25(1), (1995).
47. McCluskey, T. L., Porteous, J. M., West, M. M., and Bryant, C. H., The validation of formal specifications of requirements. In Proceedings of the BCS-FACS Northern Formal Methods Workshop. Electronic Workshops in Computing Series, Springer, September 1996.
48. Miller, Steven P., and Srivas, Mandayam, Formal verification of the AAMP5 microprocessor: A case study in the industrial use of formal methods. In Proceedings of the Workshop on Industrial-Strength Formal Specification Techniques. IEEE Computer Society, 1995.
49. Nobe, C. R., and Warner, W. E., Lessons learned from a trial application of requirements modeling using state-charts. In [IEEE Computer Society Press, 1996].
50. Ormsby, B., and Draper, C., Formal verification of safety requirements and design. Technical Report SafeFM-045-GEC-1, GEC-Marconi Avionics Ltd, March 1996.
51. Owre, S., Shankar, N., and Rushby, J. M., The PVS proof checker. Technical report, SRI, Menlo Park, 1993b.
52. Owre, S., Shankar, N., and Rushby, J. M., The PVS specification language. Technical report, SRI, Menlo Park, 1993a.
53. Owre, S., Shankar, N., and Rushby, J. M., A tutorial on specification and verification using PVS, Tutorial Material, First International Symposium of Formal Methods Europe (Peter Gorm, ed.). Formal Methods Europe, 1993c.
54. Pinheiro, F. A. C., and Goguen, J. A., An object-oriented tool for tracing requirements. IEEE Software, 13(2), (1996).
55. Rushby, John, Formal methods and the certification of critical systems. Technical Report SRI-CSL-93-7, Computer Science Laboratory, SRI International, Menlo Park, CA, 1993.
56. Shaw, M., and Garlan, D., Software Architecture: Perspectives on an Emerging Discipline. Prentice-Hall, 1996.
57. Stubbs, C., Ramesh, B., Powers, T., and Edwards, M., Implementing requirments traceability: A case study. In [Harrison and Zave, 1995].
58. van Lamsweerde, Axel, Dardenne, Anne, and Fickas, Stephen, Goal-directed requirements acquisition. Science of Computer Programming, 20, (1993).
59. Vidai, L., and Wolf, A. (editors). Second International Software Architecture Workshop, 1996.
60. West, M. M., Bryant, C. H., and McCluskey, T. L. Transforming general program proofs: A meta interpreter which expands negative literals. In Norbert E. Fuchs, editor, Proceedings of the Seventh International Workshop on Logic Program Synthesis and Transformation. To be published by Springer-Verlag in Lecture Notes in Computer Science series, 1997.
61. West, M. M., Bryant, C. H., McCluskey, T. L., and Porteus, J. M., The use of machine learning in the validation of a formal requirements specification: the work of IMPRESS. Technical Report IMPRESS/1/01/1, School of Computing and Mathematics, University of Huddersfield, UK, 1996.
62. Wordsworth, John, Software Engineering with B. Addison-Wesley, 1996.
63. Zave, Pamela, and Jackson, Michael, Requirements for telecommunication services: an attack on complexity. In [Heitmeyer and Mylopoulos, 1997].
64. Zave, Pamela, and Jackson, Michael, Conjunction as composition. Transactions on Software Engineering and Methodology, 2(4), (1993).
65. Zave, Pamela, and Jackson, Michael, Four dark corners of requirements engineering. Transactions on Software Engineering and Methodology, 6(1), January (1997).
66. Zowghi, D., and Offen, R. A logical framework for modeling and reasoning about the evolution of requirements. In [Heitmeyer and Mylopoulos, 1997].