This content is not included in your SAE MOBILUS subscription, or you are not logged in.
Approaches to Determining Beneficial Use of Simulink and UML in Automotive Embedded Software Systems
ISSN: 0148-7191, e-ISSN: 2688-3627
Published March 28, 2017 by SAE International in United States
This content contains downloadable datasetsAnnotation ability available
Simulink is a very successful and popular method for modelling and auto-coding embedded automotive features, functions and algorithms. Due to its history of success, university feeder programs, and large third party tool support, it has, in some cases, been applied to areas of the software system where other methods, principles and strategies may provide better options for the software and systems engineers and architects. This paper provides approaches to determine when best to apply UML and when best to apply Simulink to a typical automotive feature. Object oriented software design patterns as well as general guidelines are provided to help in this effort. This paper's intent is not to suggest a replacement for Simulink but to provide the software architects and designers additional options when decomposing high level requirements into reusable software components.
CitationMiloser, J., "Approaches to Determining Beneficial Use of Simulink and UML in Automotive Embedded Software Systems," SAE Technical Paper 2017-01-0008, 2017, https://doi.org/10.4271/2017-01-0008.
Data Sets - Support Documents
|[Unnamed Dataset 1]|
- Laplante, P.A, “What Every Engineer Should Know about Software Engineering,” (CRC Press, 2007), 85-93, isbn: 9781420006742.
- Aspiring Craftsman, “The Art of Separation of Concerns,” http://aspiringcraftsman.com/2008/01/03/art-of-separation-of-concerns/, accessed Oct. 2016.
- Wikipedia, “Separation of concerns,” https://en.wikipedia.org/wiki/Separation_of_concerns#cite_ref-7, accessed Oct. 2016.
- Apple Inc., “Concepts in Objective-C Programming,” (MVC as a Compound Design Pattern), https://developer.apple.com/library/content/documentation/General/Conceptual/CocoaEncyclopedia/Model-View-Controller/Model-View-Controller.html#//apple_ref/doc/uid/TP40010810-CH14, accessed Oct. 2016.
- The International Council on Systems Engineering (INCOSE), “Systems Engineering Vision 2025,” http://www.incose.org/AboutSE/sevision, accessed Oct. 2016.
- Department of Defense, “Systems Engineering Fundamentals,” (Supplementary Text, Defense Acquisition University Press, 2001)
- Object Management Group (OMG), “OMG Systems Modeling Language,” http://www.omgsysml.org/
- Object Management Group (OMG), “Unified Modeling Language,” http://www.omg.org/spec/UML/
- IBM, “The Harmony Process,” http://www.ibm.com/support/knowledgecenter/SSB2MU_8.1.5/com.btc.tcatg.user.doc/topics/atgreqcov_SecSysControllerHarmony.html, accessed Oct. 2016.
- Wikipedia, “List of software architecture styles and patterns,” https://en.wikipedia.org/wiki/List_of_software_architecture_styles_and_patterns, accessed Oct. 2016.
- Richards Mark, “Software Architecture Patterns, Second Edition,” (O’Reilly Media, Inc., 2015), 11-18.
- IBM Rational Rhapsody, “Frameworks and Operating Systems Reference,” ftp://public.dhe.ibm.com/software/rationalsdp/documentation/product_doc/Rhapsody/version_7-5/framework.pdf
- Gamma, Helm, Johnson, Vlissides, “Design Patterns Elements of Reusable Object-Oriented Software,” (Addison-Wesley)
- Lee, E.A, “The Past, Present and Future of Cyber-Physical Systems: A Focus on Models,” Sensors: 4839-4840, Feb. 2015.
- IBM, “MicroC Framework (MXF),” http://www.ibm.com/support/knowledgecenter/en/SSB2MU_8.1.3/com.ibm.rhp.microc.doc/topics/r_mxf.html, version Rational Rhapsody 8.1.3.