Barr Group's Embedded C Coding Standard was developed from the ground up to minimize bugs in firmware, by focusing on practical rules that keep bugs out, while also improving the maintainability and portability of embedded software. The coding standard book details a set of guiding principles as well as specific naming conventions and other rules for the use of data types, functions, preprocessor macros, variables and much more. Individual rules that have been demonstrated to reduce or eliminate certain types of bugs are highlighted.
"synopsis" may belong to another edition of this title.
Michael Barr is the CTO of Barr Group, an embedded systems consulting firm based in Germantown, Maryland. Barr is a former adjunct professor of electrical and computer engineering. Internationally recognized as an expert in the field of embedded software process and architecture, Barr has been admitted as a testifying expert witness in U.S. and Canadian court cases.
Barr is also the author of two other books and more than seventy articles and papers on embedded systems. For three and a half years Barr served as editor-in-chief of Embedded Systems Programming magazine.
In addition, Barr was a member of the advisory board and a track chair for the Embedded Systems Conference. He holds BSEE and MSEE degrees and has lectured in the Department of Electrical and Computer Engineering at the University of Maryland as well as the Department of Computer Science at the Johns Hopkins University.
The primary reason to adopt this coding standard is to reduce the number of bugs present in new embedded software (a.k.a., firmware) and in code later added or modified by maintainers. Whenever it is generally the case that one rule chosen from a set of alternatives has the ability to keep bugs out, that is the rule we recommend. Thus following these rules as a set will help you keep bugs out in the first place.
Of course, a coding standard cannot by itself eliminate all of the bugs from a complex embedded system. Thus this coding standard should be applied as part of the broader embedded software development and quality assurance process. An appropriate process may be lightweight but must emphasize the importance of software and system architecture as well as programmer skills training and should include design reviews, code reviews, and version control.
Other important reasons for adopting this coding standard include increasing the readability and portability of software, so that firmware may be maintained and reused at lower cost. A coding standard benefits a team of developers and larger organization by reducing the time required by individuals to understand or review the work of peers.
"About this title" may belong to another edition of this title.
FREE shipping within U.S.A.
Destination, rates & speedsSeller: ThriftBooks-Dallas, Dallas, TX, U.S.A.
Paperback. Condition: Good. No Jacket. Pages can have notes/highlighting. Spine may show signs of wear. ~ ThriftBooks: Read More, Spend Less 0.4. Seller Inventory # G1442164824I3N00
Quantity: 1 available
Seller: Ammareal, Morangis, France
Softcover. Condition: Très bon. Ancien livre de bibliothèque avec équipements. Edition 2008. Ammareal reverse jusqu'à 15% du prix net de cet article à des organisations caritatives. ENGLISH DESCRIPTION Book Condition: Used, Very good. Former library book. Edition 2008. Ammareal gives back up to 15% of this item's net price to charity organizations. Seller Inventory # G-388-613
Quantity: 1 available