國立高雄大學圖資館 |

Language: English

Back

Patterns in the machinea software en...

SpringerLink (Online service)

Patterns in the machinea software engineering guide to embedded development /

Record Type:	Electronic resources : Monograph/item
Title/Author:	Patterns in the machineby 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.
Published:	Berkeley, CA :Apress :2021.
Description:	xix, 293 p. :ill., digital ;24 cm.
Contained By:	Springer Nature eBook
Subject:	Embedded computer systemsProgramming.
Online resource:	https://doi.org/10.1007/978-1-4842-6440-9
ISBN:	9781484264409$q(electronic bk.)

Patterns in the machinea 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. - Berkeley, CA :Apress :2021. - xix, 293 p. :ill., digital ;24 cm.

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$q(electronic bk.)

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

189352
Embedded computer systems
--Programming.

LC Class. No.: TK7895.E42 / T395 2021

Dewey Class. No.: 005.1

Patterns in the machinea software engineering guide to embedded development /
LDR:03464nmm a2200325 a 4500 001 597373
003 DE-He213
005 20210630163430.0
006 m d
007 cr nn 008maaau
008 211019s2021 cau s 0 eng d
020 $a 9781484264409$q(electronic bk.)
020 $a 9781484264393$q(paper)
024 7 $a 10.1007/978-1-4842-6440-9 $2 doi
035 $a 978-1-4842-6440-9
040 $a GP $c GP
041 0 $a eng
050 4 $a TK7895.E42 $b T395 2021
072 7 $a U $2 bicssc
072 7 $a COM000000 $2 bisacsh
072 7 $a UX $2 thema
082 0 4 $a 005.1 $2 23
090 $a TK7895.E42 $b T238 2021
100 1 $a Taylor, John T. $3 890604
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.
260 $a Berkeley, CA : $b Apress : $b Imprint: Apress, $c 2021.
300 $a xix, 293 p. : $b ill., digital ; $c 24 cm.
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 0 $a Embedded computer systems $x Programming. $3 189352
650 0 $a Computer software. $3 180007
650 0 $a Software engineering. $3 184729
650 0 $a Electronic circuits. $3 182223
650 0 $a Computer input-output equipment. $3 250187
650 1 4 $a Professional Computing. $3 763344
650 2 4 $a Software Engineering/Programming and Operating Systems. $3 273711
650 2 4 $a Circuits and Systems. $3 274416
650 2 4 $a Hardware and Maker. $3 760520
700 1 $a Taylor, Wayne T. $3 890605
710 2 $a SpringerLink (Online service) $3 273601
773 0 $t Springer Nature eBook
856 4 0 $u https://doi.org/10.1007/978-1-4842-6440-9
950 $a Professional and Applied Computing (SpringerNature-12059)