An Approach of Requirements Tracing in Formal Refinement
Formal modeling of computing systems yields models that are intended to be correct with respect to the requirements that have been formalized. The complexity of typical computing systems can be addressed by formal refinement introducing all the necessary details piecemeal. We report on preliminary results that we have obtained for tracing informal natural-language requirements into formal models across refinement levels. The approach uses the WRSPM reference model for requirements modeling, and Event-B for formal modeling and formal refinement. The combined use of WRSPM and Event-B is facilitated by the rudimentary refinement notion of WRSPM, which provides the foundation for tracing requirements to formal refinements.
We assume that requirements are evolving, meaning that we have to cope with frequent changes of the requirements model and the formal model. Our approach is capable of dealing with frequent changes, making use of corresponding techniques already built into the Event-B method.
KeywordsRequirements Traceability WRSPM Formal Modeling Refinement Event-B
Unable to display preview. Download preview PDF.
- 1.Abrial, J.-R.: The B-Book: Assigning Programs to Meanings. Cambridge University Press, Cambridge (2005)Google Scholar
- 2.Abrial, J.-R.: Formal Methods in Industry: Achievements, Problems, Future. In: Proc. of the 28th Int. Conf. on Software Engineering, pp. 761–768 (2006)Google Scholar
- 6.Bjørner, D.: From Domain to Requirements. In: Concurrency, Graphs and Models: Essays dedicated to Ugo Montanari on the Occasion of his 65th Birthday, pp. 278–300. Springer, Heidelberg (2008)Google Scholar
- 9.Darimont, R., Delor, E., Massonet, P., van Lamsweerde, A.: GRAIL/KAOS: An Environment for Goal-Driven Requirements Engineering. In: Proc. of the 19th Int. Conf. on Software Engineering, pp. 612–613. ACM, New York (1997)Google Scholar
- 10.Gotel, O., Finkelstein, A.: An Analysis of the Requirements Traceability Problem. In: Proc. of the First Int. Conf. on Requirements Engineering, pp. 94–101 (1994)Google Scholar
- 11.Gunter, C.A., Jackson, M., Gunter, E.L., Zave, P.: A Reference Model for Requirements and Specifications. IEEE Software 17, 37–43 (2000)Google Scholar
- 12.Hallerstede, S., Leuschel, M.: How to Explain Mistakes. In: Gibbons, J., Oliveira, J.N. (eds.) TFM 2009. LNCS, vol. 5846, pp. 105–124. Springer, Heidelberg (2009)Google Scholar
- 13.Hoare, C.A.R., He, J.: Unifying Theories of Programming. Prentice-Hall, Englewood Cliffs (1998)Google Scholar
- 14.Jackson, M.: Problem Frames: Analysing and Structuring Software Development Problems. Addison-Wesley/ACM Press (2001)Google Scholar
- 15.Jastram, M.: Requirements Traceability. Technical report, U. Southampton (2009)Google Scholar
- 18.Loesch, F., Gmehlich, R., Grau, K., Jones, C., Mazzara, M.: Report on Pilot Deployment in Automotive Sector. Technical Report D7, DEPLOY Project (2010)Google Scholar
- 19.Marincic, J., Wupper, H., Mader, A.H., Wieringa, R.J.: Obtaining Formal Models Through Non-Monotonic Refinement (2007)Google Scholar
- 21.Plagge, D., Leuschel, M.: Seven at One Stroke: LTL Model Checking for High-Level Specifications in B, Z, CSP, and More. Int. Journal on Software Tools for Technology Transfer (1) (2008)Google Scholar
- 22.Praxis: Reveal – A Keystone of Modern Systems Engineering. Technical report (2003)Google Scholar