Object-oriented requirements: reusable, understandable, verifiable
暂无分享,去创建一个
[1] C. A. R. HOARE,et al. An axiomatic basis for computer programming , 1969, CACM.
[2] Nadia Polikarpova,et al. AutoProof: auto-active functional verification of object-oriented programs , 2015, International Journal on Software Tools for Technology Transfer.
[3] Mark Rouncefield,et al. The State of Practice in Model-Driven Engineering , 2014, IEEE Software.
[4] Bertrand Meyer,et al. Unifying Requirements and Code: An Example , 2015, Ershov Memorial Conference.
[5] Nikolai Tillmann,et al. Parameterized unit tests , 2005, ESEC/FSE-13.
[6] Kai Petersen,et al. A systematic literature review of software requirements reuse approaches , 2018, Inf. Softw. Technol..
[7] Florian Galinier,et al. Expressing and verifying embedded software requirements , 2017, ArXiv.
[8] Xavier Franch,et al. Natural Language Processing for Requirements Engineering: The Best Is Yet to Come , 2018, IEEE Software.
[9] Carme Quer,et al. Requirements reuse and requirement patterns: a state of the practice survey , 2017, Empirical Software Engineering.
[10] Bertrand Meyer,et al. Seamless requirements , 2017, Comput. Lang. Syst. Struct..
[11] George S. Avrunin,et al. Patterns in property specifications for finite-state verification , 1999, Proceedings of the 1999 International Conference on Software Engineering (IEEE Cat. No.99CB37002).
[12] A. Opdahl,et al. A Reuse-Based Approach to Determining Secur ity Requirements , 2003 .
[13] Ioannis Stamelos,et al. An Empirical Study on the Reuse of Third-Party Libraries in Open-Source Software Development , 2015, BCI.
[14] Bertrand Meyer,et al. Complete Contracts through Specification Drivers , 2016, 2016 10th International Symposium on Theoretical Aspects of Software Engineering (TASE).
[15] Bertrand Meyer,et al. On Formalism in Specifications , 1985, IEEE Software.