On the interplay between consistency, completeness, and correctness in requirements evolution

Information and Software Technology

Volumn 45, Issue 14, 2003, Pages 993-1009

  Zowghi, Didar ^a   Gervasi, Vincenzo ^b  

^a UNIVERSITY OF TECHNOLOGY SYDNEY   (Australia)

^b UNIVERSITY OF PISA   (Italy)

Author keywords

Completeness; Consistency; Evolutionary correctness assurance; Software requirements

Indexed keywords

COMPUTER AIDED SOFTWARE ENGINEERING; EMBEDDED SYSTEMS; PROBLEM SOLVING; REAL TIME SYSTEMS;

SOFTWARE REQUIREMENTS;

COMPUTER SOFTWARE;

EID: 0141509896     PISSN: 09505849     EISSN: None     Source Type: Journal    
DOI: 10.1016/S0950-5849(03)00100-9     Document Type: Conference Paper

References (44)

1. Jackson M. Software Requirements and Specifications: a lexicon of practice, principles and prejudices. 1995;Addison Wesley, Great Britain.
2. Nuseibeh B. To be or not to be: On managing inconsistency in software development, Proceedings of the Eight IEEE International Workshop on Software Specifications and Design (IWSSD'96). Proceedings of the Eight IEEE International Workshop on Software Specifications and Design (IWSSD'96). 1996;IEEE Computer Society Press, Silver Spring, MD. pp. 164-169.
3. S. Easterbrook, B. Nuseibeh, Managing inconsistencies in an evolving specification, in: Proceedings of the Second International Symposium on Requirements Engineering (RE95), York, England, 1995, pp. 48-55.
4. Easterbrook S.M., Beck E.E., Goodlet J.S., Plowman L., Sharples M., Wood C.C. A survey of empirical studies of conflict. Easterbrook S.M. CSCW: Cooperation or Conflict? 1993;1-68 Springer, London.
5. W. Robinson, S. Volkov, A meta-model for restructuring stakeholders requirements, in: Proceedings of the International Conference on Software Engineering (ICSE97), Boston, USA, 1997, pp. 140-149.
6. Van Lamsweerde A., Darimont R., Letier E. Managing conflicts in goal-driven requirements engineering. IEEE Transactions on Software Engineering: special issue on Managing Inconsistency in Software Development. 24:(11):1998;908-926.
7. Cugola G., Nitto E.D., Fuggetta A., Ghezzi C. A framework for formalizing inconsistencies and deviations in human-centred systems. ACM Transactions on Software Engineering and Methodology. 5:(3):1996;191-230.
8. Hagensen T.M., Kristensen B.B. Consistency in software system development:Framework.Model,Techniques and Tools, Software Engineering Notes (Proceedings of ACM SIFSOFT Symposium on Software Development Environment). Software Engineering Notes (Proceedings of ACM SIFSOFT Symposium on Software Development Environment). vol. 17(5):1992;SIGSOFT and ACM Press. pp. 58-67.
9. Balzer R. Tolerating Inconsistency, Proceedings of the 13th IEEE International Conference on Sofware Engineering (ICSE13). Proceedings of the 13th IEEE International Conference on Sofware Engineering (ICSE13). 1991;IEEE Computer Society Press, Austin, TX. pp. 158-165.
10. Borgida A., Greenspan S., Mylopoulos J. Knowledge representation as the basis for requirements specifications. IEEE Computer. April:1985;82-91.
11. Cordes D.W., Carver D.L. Evaluation methods for user requirements documents. Information and System Technology. 31:(4):1989;181-188.
12. Dubois E., Du Bois P., Rifaut A. Elaborating, structuring and expressing formal requirements of composite systems, Proceedings of CAiSE. Proceedings of CAiSE. 1992;Springer, Berlin. pp. 327-347.
13. Easterbrook S., Nuseibeh B. Using viewpoints for inconsistency management. IEE Software Engineering Journal. 11:(1):1996;31-43.
14. Heitmeyer C.L., Jeffords R.D., Labaw B.G. Automated consistency checking of requirements specifications. ACM Transactions on Software Engineering and Methodology. 5:(3):1996;231-261.
15. Nuseibeh B., Kramer J., Finkelstein A. A framework for expressing the relationships between multiple views in requirements specification. IEEE Transactions on Software Engineering. 20:(10):1994;760-773.
16. Reubenstein H.B., Waters R.C. The requirements apprentice: automated assistance for requirements acquisition. IEEE Transactions on Software Engineering. 17:(3):1991;226-240.
17. Sommerville I., Sawyer P., Viller S. Viewpoints for requirements elicitation: A practical approach, Proceedings of the IEEE 3rd International Conference on Requirements Engineering, (ICRE98). Proceedings of the IEEE 3rd International Conference on Requirements Engineering, (ICRE98). 1998;IEEE Computer Society Press, Colorado springs. pp. 74-81.
18. Kowalski R. Logic for Problem Solving. 1979;North Holland Elsevier, New York.
19. R.R. Lutz, Analyzing software requirements errors in safety-critical, embedded systems, in: Proceedings of the First IEEE International Symposium on Requirements Engineering (RE93), 1993, pp. 35-46.
20. Davis A.M. Software Requirements: Analysis and Specification. 2nd ed:1993;Prentice Hall, Englewood Cliffs, NJ.
21. Boehm B.W. Verifying and validating software requirements and design specifications. IEEE Software. 1:(1):1984;75-88.
22. N. Leveson, Completeness in formal specification language design for processcontrol systems, in: Proceedings of the Third Workshop on Formal Methods in Software Practice, Portland, Oregon, 2000, pp. 75-87.
23. Jaffe M.S., Leveson N.G., Heimdahl M.P.E., Melhart B.E. Software requirements analysis for real-time process-control systems. IEEE Transactions on Software Engineering. 17:(3):1991;241-258.
24. Letier E., van Lamsweerde A. Requirements analysis: Deriving operational software systems for specification goals, Proceedings of the Tenth ACM SIGSOFT Symposium on Foundations of Software Engineering. ACM Press, Charleston, SC. pp. 119-128.
25. Mylopoulos J., Chung L., Yu E. From object-oriented to goal-oriented requirements analysis. Communications ACM. 42:(1):1999;31-37.
26. H. Kaiya, H. Horai, M. Saeki, AGORA: Attributed goal-oriented requirements analysis method, in: Proceedings of the Tenth IEEE Joint International Requirements Engineering Conference (RE02), Essen, Germany, 2002, pp. 13-22.
27. Woodside M., Petriu D., Siddiqui K. Proceedings of the 24th IEEE International Conference on Software Engineering (ICSE'02). Proceedings of the 24th IEEE International Conference on Software Engineering (ICSE'02). 2002;ACM Press, Orlando, FL. pp. 22-32.
28. A. Bouhoula, Simultaneous checking of completeness and ground conuence, in: Proceedings of the 15th IEEE International Conference on Automated Software Engineering (ASE'00), Grenoble, France, 2000, pp. 143-153.
29. F.T. Sheldon, H.Y. Kim, Z. Zhou, A case study: validation of guidance control software requirements for completeness, consistency and fault tolerance, in: Proceedings of the 2001 Pacific Rim International Symposium on Dependable Computing (PRDC 2001), Seoul, Korea, 2001, pp. 311-318.
30. K. Yue, What does it mean to say that a specification is complete?, in: Proceedings of the IEEE International Workshop on Software Specifications and Design (IWSSD'87), 1987, pp. 42-49.
31. C.M. Lott, Correctness is congruent with quality, ACM Software Engineering Notes 15 (5).
32. Jackson M. The World and the Machine, Proceedings of 17th IEEE International Conference on Software Engineering (ICSE17). Proceedings of 17th IEEE International Conference on Software Engineering (ICSE17). 1995;IEEE Computer Society Press, Seattle. pp. 283-292.
33. Zave P., Jackson M. Four dark corners of requirements engineering. ACM Transactions on Software Engineering and Methodology. 6:(1):1997;1-30.
34. Jackson M., Zave P. Proceedings of the First IEEE International Symposium on Requirements Engineering (RE93). Proceedings of the First IEEE International Symposium on Requirements Engineering (RE93). 1993;IEEE Computer Society Press, Silver Spring, MD. pp. 56-64.
35. D. Bjorner, C.W. George, B.S. Hansen, H. Laustrup, S. Prehn, Models of railway systems infrastructure, in: Proceedings of the First Workshop on Formal Methods in Railway Industry, Nieuwegein, Netherlands, 1997, http://www.ifad.dk/Projects/FMERail/proceedings1.html.
36. Jackson M. Problem Frames: Analyzing and structuring software development problems. 2001;Addison Wesley, Great Britain.
37. Katsuno H., Mendelzon A.O. On the difference between updating a knowledge base and revising it. Allen J.F., Fikes R., Sandewall E. Proceedings of the Second International Conference on Principles of Knowledge Representation and Reasoning (KR'91). 1991;387-394 Morgan Kaufmann, San Mateo, CA.
38. Heimdahl M.P.E., Leveson N.G. Completeness and consistency in hierarchical state-based requirements. IEEE Transactions on Software Engineering. 22:(6):1996;363-377.
39. Finkelstein A., Gabbay D., Hunter A., Kramer J., Nuseibeh B. Inconsistency handling in multi-perspective specifications. IEEE Transactions on Software Engineering. 20:(8):1994;569-577.
40. Hunter A., Nuseibeh B. Managing inconsistent specifications: reasoning, analysis and action. ACM Transactions on Software Engineering and Methodology. 7:(4):1998;335-367.
41. D. Zowghi, V. Gervasi, A. McRae, Using default reasoning to discover inconsistencies in natural language requirements, in: Proceedings of the Eight Asia-Pacific Software Engineering Conference (APSEC'01), Macau, China, 2001, pp. 133-140.
42. Gervasi V., Nuseibeh B. Lightweight validation of natural language requirements. Software: Practice and Experience. 32:(2):2002;113-133.
43. Zowghi D., Paryani S. Teaching requirements engineering through role playing, Proceedings of the 11th IEEE Joint International Requirements Engineering Conference (RE03). Proceedings of the 11th IEEE Joint International Requirements Engineering Conference (RE03). 2003;IEEE CS Press, Monterey Bay, CA.
44. D. Zowghi, R. J. Offen, A logical framework for modelling and reasoning about the evolution of requirements, in: Proceedings of the Third IEEE International Symposium on Requirements Engineering (RE97), 1997, pp. 247-259.