國立虎尾科技大學 |

Patterns in the Machine = A Software Engineering Guide to Embedded Development /

Record Type:	Language materials, printed : Monograph/item
Title/Author:	Patterns in the Machine/ by John T. Taylor, Wayne T. Taylor.
Reminder of title:	A Software Engineering Guide to Embedded Development /
Author:	Taylor, John T.
other author:	Taylor, Wayne T.
Description:	XIX, 293 p. 59 illus.online resource. :
Contained By:	Springer Nature eBook
Subject:	Hardware and Maker. -
Online resource:	https://doi.org/10.1007/978-1-4842-6440-9
ISBN:	9781484264409

Patterns in the Machine = A Software Engineering Guide to Embedded Development /
Taylor, John T.

Patterns in the MachineA Software Engineering Guide to Embedded Development /[electronic resource] :by John T. Taylor, Wayne T. Taylor. - 1st ed. 2021. - XIX, 293 p. 59 illus.online resource.

1: 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.

Discover 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.

ISBN: 9781484264409

Standard No.: 10.1007/978-1-4842-6440-9doiSubjects--Topical Terms:

1114124
Hardware and Maker.

LC Class. No.: QA76.75-.765

Dewey Class. No.: 004

Patterns in the Machine = A Software Engineering Guide to Embedded Development /
LDR:03754nam a22003855i 4500 001 1052090
003 DE-He213
005 20210621124734.0
007 cr nn 008mamaa
008 220103s2021 xxu| s |||| 0|eng d
020 $a 9781484264409 $9 978-1-4842-6440-9
024 7 $a 10.1007/978-1-4842-6440-9 $2 doi
035 $a 978-1-4842-6440-9
050 4 $a QA76.75-.765
072 7 $a U $2 bicssc
072 7 $a COM000000 $2 bisacsh
072 7 $a UX $2 thema
082 0 4 $a 004 $2 23
100 1 $a Taylor, John T. $e author. $4 aut $4 http://id.loc.gov/vocabulary/relators/aut $3 1356712
245 1 0 $a Patterns in the Machine $h [electronic resource] : $b A Software Engineering Guide to Embedded Development / $c by John T. Taylor, Wayne T. Taylor.
250 $a 1st ed. 2021.
264 1 $a Berkeley, CA : $b Apress : $b Imprint: Apress, $c 2021.
300 $a XIX, 293 p. 59 illus. $b online resource.
336 $a text $b txt $2 rdacontent
337 $a computer $b c $2 rdamedia
338 $a online resource $b cr $2 rdacarrier
347 $a text file $b PDF $2 rda
505 0 $a 1: 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.
520 $a Discover 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.
650 2 4 $a Hardware and Maker. $3 1114124
650 2 4 $a Circuits and Systems. $3 670901
650 2 4 $a Software Engineering/Programming and Operating Systems. $3 669780
650 1 4 $a Professional Computing. $3 1115983
650 0 $a Computer input-output equipment. $3 559611
650 0 $a Electronic circuits. $3 563332
650 0 $a Software engineering. $3 562952
650 0 $a Computer software. $3 528062
700 1 $a Taylor, Wayne T. $e author. $4 aut $4 http://id.loc.gov/vocabulary/relators/aut $3 1356713
710 2 $a SpringerLink (Online service) $3 593884
773 0 $t Springer Nature eBook
776 0 8 $i Printed edition: $z 9781484264393
776 0 8 $i Printed edition: $z 9781484264416
856 4 0 $u https://doi.org/10.1007/978-1-4842-6440-9
912 $a ZDB-2-CWD
912 $a ZDB-2-SXPC
950 $a Professional and Applied Computing (SpringerNature-12059)
950 $a Professional and Applied Computing (R0) (SpringerNature-43716)