- 1.J. Atlee and J. Gannon. State-based model check-ing of event-driven system requirements. In Pro-ceedings of the ACM SIGSOFT '91 Conference on Software for Critical Systems. Software Engineering Notes. Volume 16 Number 5, 1991. Google ScholarDigital Library
- 2.G. R. Bruns, S. L. Gerhart, 1. Forman, and M. Graf. Design technology assessment: The statecharts approach. Technical Report STP-107- 86, MCC, March 1986.Google Scholar
- 3.R. E. Bryant. Graph-based algorithms for boolean function manipulation. IEEE Trans-actions on Computers, C-35(8) :677-691, August 1986. Google ScholarDigital Library
- 4.J.R. Burch, E.M. Clarke, K.L. McMillan, D.L. Dill, and L.J. Hwang. Symbolic model checking: 1020 states and beyond. In Proceedings of the Fifth Annual Symposium on Logic in Computer Science, June 1990.Google Scholar
- 5.E. M. Clarke, M. C. Browne, E. A. Emerson, and A. P. Sistla. Using temporal logic for automatic verification of finite state systems. In K.R. Apt, editor, Logics and Models of Concurrent Systems, pages 3-26. Springer-Verlag, Berlin, 1985. Google ScholarDigital Library
- 6.E. M. Clarke, E. A. Emerson, and A. P. Sistla. Automatic verification of finite-state concurrent systems using temporal logic. ACM Transactions on Programming Languages and Systems, 8(2):244-263, April 1986. Google ScholarDigital Library
- 7.Patrice Godefroid, Gerhard J. Holzmann, and Dieder Pirottin. State space caching revisited. In Proceedings of the Fourth Workshop on Computer-Aided Verification, pages 175-186, 1992. Google ScholarDigital Library
- 8.D. Harel. Statecharts: A visual formalism for complex systems. Science of Computer Program-ming, 8:231-274, 1987. Google ScholarDigital Library
- 9.D. Harel. On visual formalisms. Communications of the ACM, 31(5):514-530, May 1988. Google ScholarDigital Library
- 10.D. Harel and A. Pnueli. On the development of reactive systems. In K.R. Apt, editor, Logics and Models of Concurrent Systems, pages 477-498. Springer-Verlag, 1985. Google ScholarDigital Library
- 11.Mats P.E. Heimdahl. Static Analysis of State- Based Requircments: Analyaia for Completeness and Consistency. PhD thesis, University of California, Irvine, 1994. Google ScholarDigital Library
- 12.Gerhard J. Holzmann. Tracing protocols. ATtY T Technical Journal, 64(10), December 1985.Google Scholar
- 13.Gerhard J. Holzmann. Automated protocol validation in Argos: Assertion proving and scatter searching. IEEE Transactions on Sofiware Engineering, 13(6):683-696, June 1987. Google ScholarDigital Library
- 14.M. S. Jaffe, N. G. Leveson, M. P.E. Heimdahl, and B. Melhart. Software requirements analysis for real-time process-control systems. IEEE Transactions on Soflware Engineering, 17(3):241-258, March 1991. Google ScholarDigital Library
- 15.N. G. Leveson, M. Heimdahl, H. Hildreth, and J. Reese. TCAS II requirements specification.Google Scholar
- 16.N. G. Leveson, M. P.E. Heimdahl, H. Hildreth, and J. D. Reese. Requirements specification for process-control systems. IEEE Transactions on Software Engineering, 20(9), September 1994. Google ScholarDigital Library
- 17.A. Pnueli and M. Shalev. What is in a step? In J. Klop, J. Meijer, and J. Rutten, editors, J. W. De Baker, Liber Amicorum, pages 373-400. CWI Amsterdam, 1989.Google Scholar
- 18.A. P. Ravn and H. Rlchel. Requirements capture for embedded real-time systems. In IMA CS Symposium MCTS, 1991.Google Scholar
- 19.H. Richel and A. P. Ravn. Requirements capture for computer based systems. Technical Report ID/DTH HR 2/2, Technical University of Den-mark, October 1990.Google Scholar
Index Terms
- Completeness and consistency analysis of state-based requirements
Recommendations
Completeness and Consistency Analysis on Requirements of Distributed Event-Driven Systems
TASE '08: Proceedings of the 2008 2nd IFIP/IEEE International Symposium on Theoretical Aspects of Software EngineeringFor many event-driven systems, the completeness and consistency (C&C) are the most important characteristics of those software requirements. This paper presents a systematic approach to perform C&C analysis on the requirements, and an intelligent ...
Automatic analysis of requirements consistency with the B method
A consistent requirements specification is a fundamental success factor for quality software development projects. On the one hand, writing requirements in a natural language is not good for an automated conflict detection process. On the other hand, ...
Comments