Abstract
Formal methods tools can be used to detect and prevent errors so researchers assume that industry will use them. We are often frustrated when we see industrial projects where tools could have been used to detect or prevent errors in the final product. Researchers often fail to realize that there is a significant gap between aa potentially useful tool and its use in a standards compliant, commercially viable, development process. In this talk I take a look at seemingly mundane industrial requirements - qualification (certification) of tools for use in standards compliant development process for general safety (IEC 61508), Automotive (ISO 26262) and Avionics (DO-178C), Model Based Design coding guidelines compliance, standards compliance documentation generation and integration with existing industry partner development processes. For each of these topics I show how “stupid tool tricks” can be used to not only increase adoption of academic methods and tools, but also lead to interesting research questions with industry relevant results.
Access this chapter
Tax calculation will be finalised at checkout
Purchases are for personal use only
References
Bender, M., Laurin, K., Lawford, M., Pantelic, V., Korobkine, A., Ong, J., Mackenzie, B., Bialy, M., Postma, S.: Signature required: making Simulink data flow and interfaces explicit. In: Science of Computer Programming, Part 1, vol. 113, pp. 29–50 (2015). Model Driven Development (Selected & extended papers from MODELSWARD 2014)
Eles, C., Lawford, M.: A tabular expression toolbox for Matlab/Simulink. In: Bobaru, M., Havelund, K., Holzmann, G.J., Joshi, R. (eds.) NFM 2011. LNCS, vol. 6617, pp. 494–499. Springer, Heidelberg (2011). doi:10.1007/978-3-642-20398-5_38
Pantelic, V., Postma, S., Lawford, M., Korobkine, A., Mackenzie, B., Ong, J., Bender, M.: A toolset for Simulink: improving software engineering practices in development with Simulink. In: 3rd International Conference on Model-Driven Engineering and Software Development (MODELSWARD), pp. 50–61. IEEE, February 2015
Parnas, D.L.: Software design. In: Hoffman, D.M., Weiss, D.M. (eds.) Software Fundamentals: Collected Papers by David L. Parnas, pp. 137–142. Addison-Wesley (2011)
The MathWorks. Japan MathWorks Automotive Advisory Board (JMAAB): Control Algorithm Modeling Guidelines Using MATLAB, Simulink, and Stateflow, Version 4.01, March 2015. www.mathworks.com/solutions/automotive/standards/maab.html. Accessed Feb 2016
Wassyng, A., Lawford, M.: Lessons learned from a successful implementation of formal methods in an industrial project. In: Araki, K., Gnesi, S., Mandrioli, D. (eds.) FME 2003. LNCS, vol. 2805, pp. 133–153. Springer, Heidelberg (2003). doi:10.1007/978-3-540-45236-2_9
Wassyng, A., Lawford, M.: Software tools for safety-critical software development. Int. J. Softw. Tools Technol. Transf. (STTT) 8(4–5), 337–354 (2006)
Acknowledgments
The author would like to acknowledge the work of all of the researchers and students in the McMaster Centre for Software Certification (McSCert). This work would not have been possible without the support of our industry partners.
Author information
Authors and Affiliations
Corresponding author
Editor information
Editors and Affiliations
Rights and permissions
Copyright information
© 2016 Springer International Publishing AG
About this paper
Cite this paper
Lawford, M. (2016). Stupid Tool Tricks for Smart Model Based Design. In: Blazy, S., Chechik, M. (eds) Verified Software. Theories, Tools, and Experiments. VSTTE 2016. Lecture Notes in Computer Science(), vol 9971. Springer, Cham. https://doi.org/10.1007/978-3-319-48869-1_1
Download citation
DOI: https://doi.org/10.1007/978-3-319-48869-1_1
Published:
Publisher Name: Springer, Cham
Print ISBN: 978-3-319-48868-4
Online ISBN: 978-3-319-48869-1
eBook Packages: Computer ScienceComputer Science (R0)