LEADER 03766oam 2200457 450 001 9910483374903321 005 20210618185146.0 010 $a1-4842-6440-1 024 7 $a10.1007/978-1-4842-6440-9 035 $a(CKB)4100000011728495 035 $a(DE-He213)978-1-4842-6440-9 035 $a(MiAaPQ)EBC6460391 035 $a(CaSebORM)9781484264409 035 $a(PPN)253256518 035 $a(EXLCZ)994100000011728495 100 $a20210618d2021 uy 0 101 0 $aeng 135 $aurnn|008mamaa 181 $ctxt$2rdacontent 182 $cc$2rdamedia 183 $acr$2rdacarrier 200 10$aPatterns in the machine $ea software engineering guide to embedded development /$fJohn T. Taylor, Wayne T. Taylor 205 $a1st ed. 2021. 210 1$aBerkeley, CA :$cApress,$d[2021] 210 4$d©2021 215 $a1 online resource (XIX, 293 p. 59 illus.) 311 $a1-4842-6439-8 327 $a1: Introduction -- 2: Core Concepts -- 3: Design Theory For Embedded Programming -- 4: Persistent Storage Example -- 5: Software Architecture -- 6: Automated Unit Testing -- 7: Functional Simulator -- 8: Continuous Integration -- 9: Data Model -- 10: Finite State Machines -- 11: Documentation -- 12: File Organization and Naming -- 13: More About Late Bindings -- 14: Initialization and Main -- 15: More Best Practices -- 16: PIM Thermostat Example -- 17: The Tao of Development -- Appendix A: Terminology -- Appendix B: UML Notation for State Machines -- Appendix C: UML Cheat Sheet -- Appendix D: Why C++ -- Appendix E: Package Management and Outcast -- Appendix F: Requirements vs. Design Statements. 330 $aDiscover how to apply software engineering patterns to develop more robust firmware faster than traditional embedded development approaches. In the authors? experience, traditional embedded software projects tend towards monolithic applications that are optimized for their target hardware platforms. This leads to software that is fragile in terms of extensibility and difficult to test without fully integrated software and hardware. Patterns in the Machine focuses on creating loosely coupled implementations that embrace both change and testability. This book illustrates how implementing continuous integration, automated unit testing, platform-independent code, and other best practices that are not typically implemented in the embedded systems world is not just feasible but also practical for today?s embedded projects. After reading this book, you will have a better idea of how to structure your embedded software projects. You will recognize that while writing unit tests, creating simulators, and implementing continuous integration requires time and effort up front, you will be amply rewarded at the end of the project in terms of quality, adaptability, and maintainability of your code. You will: Incorporate automated unit testing into an embedded project Design and build functional simulators for an embedded project Write production-quality software when hardware is not available Use the Data Model architectural pattern to create a highly decoupled design and implementation Understand the importance of defining the software architecture before implementation starts and how to do it Discover why documentation is essential for an embedded project Use finite state machines in embedded projects. 606 $aEmbedded computer systems$xProgramming 615 0$aEmbedded computer systems$xProgramming. 676 $a004.16 700 $aTaylor$b John T.$0340604 702 $aTaylor$b Wayne T. 801 0$bMiAaPQ 801 1$bMiAaPQ 801 2$bUtOrBLW 906 $aBOOK 912 $a9910483374903321 996 $aPatterns in the machine$92846513 997 $aUNINA LEADER 01590oam 2200421 a 450 001 9910697556803321 005 20110610082444.0 035 $a(CKB)5470000002389384 035 $a(OCoLC)424633928 035 $a(EXLCZ)995470000002389384 100 $a20090714d2009 ua 0 101 0 $aeng 135 $aurmn||||||||| 181 $ctxt$2rdacontent 182 $cc$2rdamedia 183 $acr$2rdacarrier 200 00$aHow to develop a pedestrian safety action plan$b[electronic resource] $efinal report /$fCharles V. Zegeer ... [and others] 205 $aRevised. 210 1$a[Washington, D.C.] :$cU.S. Federal Highway Administratrion, Office of Highway Safety,$d[2009] 215 $a1 online resource (189 pages) $ccolor illustrations, color maps 300 $aTitle from PDF title page (viewed on July 14, 2009). 320 $aIncludes bibliographical references (pages 157-170). 517 $aHow to develop a pedestrian safety action plan 606 $aPedestrians$zUnited States$xSafety measures$xPlanning 606 $aTraffic safety$zUnited States$xPlanning 615 0$aPedestrians$xSafety measures$xPlanning. 615 0$aTraffic safety$xPlanning. 701 $aZegeer$b Charles V$01385327 712 02$aUnited States.$bFederal Highway Administration.$bOffice of Safety. 712 02$aPedestrian and Bicycle Information Center (U.S.) 801 0$bCBT 801 1$bCBT 801 2$bCBT 801 2$bGPO 906 $aBOOK 912 $a9910697556803321 996 $aHow to develop a pedestrian safety action plan$93537556 997 $aUNINA