Best Microprocessor Design
The added chapters contain (1) a crisp condensation of all the propositions asserted in the original book, including Brooks' central argument in The Mythical Man-Month: that large programming projects suffer management problems different from small ones due to the division of labor; that the conceptual integrity of the product is therefore critical; and that it is difficult but possible to achieve this unity; (2) Brooks' view of these propositions a generation later; (3) a reprint of his classic 1986 paper "No Silver Bullet"; and (4) today's thoughts on the 1986 assertion, "There will be no silver bullet within ten years." My co-authors of that study, and our executive secretary, Robert L. Patrick, were invaluable in bringing me back into touch with real-world large software projects. In preparing my retrospective and update of The Mythical Man-Month, I was struck by how few of the propositions asserted in it have been critiqued, proven, or disproven by ongoing software engineering research and experience. In hopes that these bald statements will invite arguments and facts to prove, disprove, update, or refine those propositions, I have included this outline as Chapter 18. For a wonderful willingness to share views, to comment thoughtfully on drafts, and to re-educate me, I am indebted to Barry Boehm, Ken Brooks, Dick Case, James Coggins, Tom DeMarco, Jim McCarthy, David Parnas, Earl Wheeler, and Edward Yourdon. I thank Gordon Bell, Bruce Buchanan, Rick Hayes-Roth, my colleagues on the Defense Science Board Task Force on Military Software, and, most especially, David Parnas for their insights and stimulating ideas for, and Rebekah Bierly for technical production of, the paper printed here as Chapter 16. Analyzing the software problem into the categories of essence and accident was inspired by Nancy Greenwood Brooks, who used such analysis in a paper on Suzuki violin pedagogy. Two persons' contributions should be especially cited: Norman Stanton, then Executive Editor, and Herbert Boes, then Art Director.
Reviews
Find Best Price at Amazon"Fred Brooks was a software engineer at IBM for some decades and later chair of the UNC CS department."
"Classic book which is proven by time."
"It contains four additional chapters: No Silver Bullet, yet another influential essay by Brooks that was not in the original edition; an overview of all his points (the entire book) in an easy-to-digest format; his thoughts 20 years on from writing the original, and how the industry has changed in that time; and finally, his responses to various criticism he has received over the years specifically in response to the "No Silver Bullet" essay."
"Other topics include the distinction between the "essential" and "accidental" elements of software design; the distinction between building a computer program vs. designing a "programming a systems product" (and the ninefold difference in complexity and time between the two); the quest for software engineering's elusive "silver bullet"; the importance of documentation; the surprisingly small percentage of time that actual writing of code occupies on the timeline of a typical software-development project (as contrasted with time needed for testing and debugging); large teams vs. small "surgical teams" (and why the latter isn't always the answer for all projects); the "buy versus build" dilemma; and many others."
It explores this generational change with updated content featuring tablet computers, cloud infrastructure, and the ARM (mobile computing devices) and x86 (cloud computing) architectures. Winner of a 2014 Texty Award from the Text and Academic Authors Association Includes new examples, exercises, and material highlighting the emergence of mobile computing and the cloud Covers parallelism in depth with examples and content highlighting parallel hardware and software topics Features the Intel Core i7, ARM Cortex-A8 and NVIDIA Fermi GPU as real-world examples throughout the book Adds a new concrete example, "Going Faster," to demonstrate how understanding hardware can inspire software optimizations that improve performance by 200 times Discusses and highlights the "Eight Great Ideas" of computer architecture: Performance via Parallelism; Performance via Pipelining; Performance via Prediction; Design for Moore's Law; Hierarchy of Memories; Abstraction to Simplify Design; Make the Common Case Fast; and Dependability via Redundancy Includes a full set of updated and improved exercises. He served on the Information Technology Advisory Committee to the U.S. President, as chair of the CS division in the Berkeley EECS department, as chair of the Computing Research Association, and as President of ACM. Among his many awards are the 2001 Eckert-Mauchly Award for his contributions to RISC technology, the 2001 Seymour Cray Computer Engineering Award, and the 2000 John von Neumann Award, which he shared with David Patterson.
Reviews
Find Best Price at Amazon"Sometimes it was hard to relate two topics or subjects together because they weren't sequential in the book and they weren't explicitly linked."
"Good for those that have taken intro to assembly and computer architecture."
"I'm a Computer Science major and will not really benefit from the information in this book."
"This is a boring book, mostly term and definition."
"It gives readers solid framework of computer architecture and guides them to further specific technologies."
"Very detailed book, personally hard to understand and information was scattered in the online version."
"The biggest issue is that the problem sets are far harder than the actual text, and are essentially impossible to solve completely unless your professor teaches it in lecture or you use an external solutions manual (chegg)."
The added chapters contain (1) a crisp condensation of all the propositions asserted in the original book, including Brooks' central argument in The Mythical Man-Month: that large programming projects suffer management problems different from small ones due to the division of labor; that the conceptual integrity of the product is therefore critical; and that it is difficult but possible to achieve this unity; (2) Brooks' view of these propositions a generation later; (3) a reprint of his classic 1986 paper "No Silver Bullet"; and (4) today's thoughts on the 1986 assertion, "There will be no silver bullet within ten years." My co-authors of that study, and our executive secretary, Robert L. Patrick, were invaluable in bringing me back into touch with real-world large software projects. In preparing my retrospective and update of The Mythical Man-Month, I was struck by how few of the propositions asserted in it have been critiqued, proven, or disproven by ongoing software engineering research and experience. In hopes that these bald statements will invite arguments and facts to prove, disprove, update, or refine those propositions, I have included this outline as Chapter 18. For a wonderful willingness to share views, to comment thoughtfully on drafts, and to re-educate me, I am indebted to Barry Boehm, Ken Brooks, Dick Case, James Coggins, Tom DeMarco, Jim McCarthy, David Parnas, Earl Wheeler, and Edward Yourdon. I thank Gordon Bell, Bruce Buchanan, Rick Hayes-Roth, my colleagues on the Defense Science Board Task Force on Military Software, and, most especially, David Parnas for their insights and stimulating ideas for, and Rebekah Bierly for technical production of, the paper printed here as Chapter 16. Analyzing the software problem into the categories of essence and accident was inspired by Nancy Greenwood Brooks, who used such analysis in a paper on Suzuki violin pedagogy. Two persons' contributions should be especially cited: Norman Stanton, then Executive Editor, and Herbert Boes, then Art Director. Boes developed the elegant style, which one reviewer especially cited: "wide margins, and imaginative use of typeface and layout."
Reviews
Find Best Price at Amazon"Fred Brooks was a software engineer at IBM for some decades and later chair of the UNC CS department."
"Classic book which is proven by time."
"It contains four additional chapters: No Silver Bullet, yet another influential essay by Brooks that was not in the original edition; an overview of all his points (the entire book) in an easy-to-digest format; his thoughts 20 years on from writing the original, and how the industry has changed in that time; and finally, his responses to various criticism he has received over the years specifically in response to the "No Silver Bullet" essay."
"Other topics include the distinction between the "essential" and "accidental" elements of software design; the distinction between building a computer program vs. designing a "programming a systems product" (and the ninefold difference in complexity and time between the two); the quest for software engineering's elusive "silver bullet"; the importance of documentation; the surprisingly small percentage of time that actual writing of code occupies on the timeline of a typical software-development project (as contrasted with time needed for testing and debugging); large teams vs. small "surgical teams" (and why the latter isn't always the answer for all projects); the "buy versus build" dilemma; and many others."
Best Computer Systems Analysis & Design
By the time you finish this book, you’ll be able to take advantage of the best design practices and experiences of those who have fought the beast of software design and triumphed. Eric Freeman recently ended nearly a decade as a media company executive, having held the position of CTO of Disney Online & Disney.com at The Walt Disney Company. More recently, she's been a master trainer for Sun Microsystems, teaching Sun's Java instructors how to teach the latest technologies to customers, and a lead developer of several Sun certification exams.
Reviews
Find Best Price at Amazon"a nice intro to design patterns."
"I love these Head First books."
"I've always preferred and loved the idea of fun and learn being together, and this book does exactly that, it's a book so easy to read that helps you to keep reading, and invites you to actually do the excercises, and they look fun to do."
"Fun book."
"It presents exactly what you need to know in an easy and fun to read format, making it much less of a textbook and more of a "Hey look at all this cool stuff you can do with software!""
"While GOF book covers more patterns, it's not as nearly as much fun to read as Head First Design Patterns. Bottom line: - I definitely recommend this book to any junior developer who wants to get familiar with Design Patterns. - Experienced developers will skip quite a few pages (like I did), yet it's still a good read."
"Great book, I should have read it years ago."
"This book is definitely not the patterns Nirvana, and it may not make you the patterns guru, but it sure is a great book, extremely well written to welcome the beginner to the world of patterns. Once I master this book and practice the patterns, I am sure I will be able to move to the next level and maybe I will be better able to understand the GOF bible which I learn is a must read for any serious techie!"
Best IT Project Management
The added chapters contain (1) a crisp condensation of all the propositions asserted in the original book, including Brooks' central argument in The Mythical Man-Month: that large programming projects suffer management problems different from small ones due to the division of labor; that the conceptual integrity of the product is therefore critical; and that it is difficult but possible to achieve this unity; (2) Brooks' view of these propositions a generation later; (3) a reprint of his classic 1986 paper "No Silver Bullet"; and (4) today's thoughts on the 1986 assertion, "There will be no silver bullet within ten years." My co-authors of that study, and our executive secretary, Robert L. Patrick, were invaluable in bringing me back into touch with real-world large software projects. In preparing my retrospective and update of The Mythical Man-Month, I was struck by how few of the propositions asserted in it have been critiqued, proven, or disproven by ongoing software engineering research and experience. In hopes that these bald statements will invite arguments and facts to prove, disprove, update, or refine those propositions, I have included this outline as Chapter 18. For a wonderful willingness to share views, to comment thoughtfully on drafts, and to re-educate me, I am indebted to Barry Boehm, Ken Brooks, Dick Case, James Coggins, Tom DeMarco, Jim McCarthy, David Parnas, Earl Wheeler, and Edward Yourdon. I thank Gordon Bell, Bruce Buchanan, Rick Hayes-Roth, my colleagues on the Defense Science Board Task Force on Military Software, and, most especially, David Parnas for their insights and stimulating ideas for, and Rebekah Bierly for technical production of, the paper printed here as Chapter 16. Analyzing the software problem into the categories of essence and accident was inspired by Nancy Greenwood Brooks, who used such analysis in a paper on Suzuki violin pedagogy. Two persons' contributions should be especially cited: Norman Stanton, then Executive Editor, and Herbert Boes, then Art Director. Boes developed the elegant style, which one reviewer especially cited: "wide margins, and imaginative use of typeface and layout."
Reviews
Find Best Price at Amazon"Fred Brooks was a software engineer at IBM for some decades and later chair of the UNC CS department."
"A great book that tells you everything your project manager and lead architect are doing wrong, leading to the depressing realization that there is nothing you can do."
"Classic book which is proven by time."
"It contains four additional chapters: No Silver Bullet, yet another influential essay by Brooks that was not in the original edition; an overview of all his points (the entire book) in an easy-to-digest format; his thoughts 20 years on from writing the original, and how the industry has changed in that time; and finally, his responses to various criticism he has received over the years specifically in response to the "No Silver Bullet" essay."
"Other topics include the distinction between the "essential" and "accidental" elements of software design; the distinction between building a computer program vs. designing a "programming a systems product" (and the ninefold difference in complexity and time between the two); the quest for software engineering's elusive "silver bullet"; the importance of documentation; the surprisingly small percentage of time that actual writing of code occupies on the timeline of a typical software-development project (as contrasted with time needed for testing and debugging); large teams vs. small "surgical teams" (and why the latter isn't always the answer for all projects); the "buy versus build" dilemma; and many others."
Best Computer Hardware Design
Common failures in enterprise applications often occur because their developers do not understand the architectural lessons that experienced object developers have learned. Patterns of Enterprise Application Architecture is written in direct response to the stiff challenges that face enterprise application developers. The first section is a short tutorial on developing enterprise applications, which you can read from start to finish to understand the scope of the book's lessons. Armed with this book, you will have the knowledge necessary to make important architectural decisions about building an enterprise application and the proven patterns for use when building them. With the help of an expert group of contributors, Martin distills over forty recurring solutions into patterns. The first section is a short tutorial on developing enterprise applications, which you can read from start to finish to understand the scope of the book's lessons. Dividing an enterprise application into layers The major approaches to organizing business logic An in-depth treatment of mapping between objects and relational databases Using Model-View-Controller to organize a Web presentation Handling concurrency for data that spans multiple transactions Designing distributed object interfaces 0321127420B10152002.
Reviews
Find Best Price at Amazon"Awesome book to read to understand the underpinning patterns of frameworks- that definitely improves ones understanding of why and how to use pattern."
"I found this book really complete about the issues an enterprise application may encounter."
"The benefit of reading this book is understanding what the problem is, why it's a problem and how to solve the problem."
"A great book of well written information."
"Classic Book."
"This should clearly be a book that sits along with the Gang of Four book on your shelf (Design Patterns) for the Enterprise developer or someone interested in enterprise development."
"Microsoft has moved away from datasets (Thankfully) so some of what it's talking about doesn't make sense anymore."
Best PIC Microcontrollers
This book takes the novice from introduction of embedded systems through to advanced development techniques for utilizing and optimizing the PIC family of microcontrollers in your device. *Covers both assembly and C programming languages, essential for optimizing the PIC. *Amazing breadth of coverage moving from introductory to advanced topics covering more and more complex microcontroller families. *Details MPLAB and other Microchip design tools. Tim Wilmshurst is the author of Designing Embedded Systems with PIC Microcontrollers.
Reviews
Find Best Price at Amazon"From comparison to many other books I have read, I would consider this book to be excellent for beginners as well as nothing is bypassed even though the book is economically written."
"This book is a thorough guide on starting to use assembler and then C to design embedded systems on PIC uCs."
"Even with numerous PIC C tutorials on the web, the completeness and depth of this book make it a welcome addition on my journey into embedded programming."
"Very readable book."
"very nice book and nice layout."
"Has many examples and good explanations."
"Covers both assembly language and C. Detailed and deeply discussed."
"Very well written - Good core learning book for PIC MicroControllers."
Best Computer Hardware DSPs
This book presents the fundamentals of discrete-time signals, systems, and modern digital processing and applications for students in electrical engineering, computer engineering, and computer science.The book is suitable for either a one-semester or a two-semester undergraduate level course in discrete systems and digital signal processing.
Reviews
Find Best Price at Amazon"The reason for only 4/5 stars is mostly due to the poor coverage of terms in the index, which makes it hard to find where a particular concept is first introduced and defined."
"While very easy to read and understand, the material covered is presented with sufficient depth."
"The book demonstrates great details of Fourier Transform by constructing from mathematic components to a whole picture of Fourier Transform. I guess this textbook also much better than most textbooks, since most textbooks don't even bother to cover the real fundamental concepts."
"Great for beginning Engineering students."
"I applied the MathCAD 14.0 to solve the problem assignments and found a couple of typing errors in the solution guide. The solution manual is a great helper on assisting me to work on more problem assignments with confidence--It's the reason why I decided to purchase this textbook rather than other advance DSP books."
"Although the content is same as I expected the book is thicker and has different paper type which makes the book not easy to use and strong enough.This was acceptable because of low price."
"Poor book assembly."
"it is a clone of the book, it isnt the original book."
Best Computer Hardware Control Systems
INDUSTRIAL AUTOMATED SYSTEMS: INSTRUMENTATION AND MOTION CONTROL, is the ideal book to provide readers with state-of-the art coverage of the full spectrum of industrial maintenance and control, from servomechanisms to instrumentation. Terry Bartelt is currently an Electromechanical Instructor at Fox Valley Technical College, with more than twenty five years teaching experience in the field.
Reviews
Find Best Price at Amazon"2011C edition, Terry Bartelt, Industrial Automated Systems: Instrumentation and Motion Control. So far I recommend it, I'm an electrical design engineer on the accelerated learning path and find it useful."
"its quite a good book for beginners."
"I'm a Control Systems Engineer and have found this book useful."
"My son is using this book for his class."
"This book is very thorough and detailed."
"Pretty much as described."
"A required textbook for one of my classes."
Best Computer Hardware Embedded Systems
Exploring Raspberry Pi.
Reviews
Find Best Price at Amazon"I'm an EE with programming experience in Windows and I found the Linux section easy to understand, but very slow going, due to the vastness of Linux."
"Very comprehensive book on how to program the Rpi for physical computing."
"I've been playing with the Raspberry Pi for a few years now as a basic Linux computer, but I always felt that interfacing it to other devices would make this a much more powerful little platform. I'm fortunate to have enough background in these areas to weave through this, but those with less of a computer or electronics background might want to have a local geek or two handy to call in for help when needed. I'm an Electrical / Computer Engineer by trade, and I've had an interest in introducing hobby electronics to my kids."
"I can sum it up in one word."
"Really a very good book!!"
"This book is fantastic."
"I agree the the traditional paper book deserves the 5 star rating. The Kindle edition only has a 2 level outline, no sub topics, making it extremely cumbersome, if not useless, as a navigation tool. So minimal table of contents and no index makes the Kindle edition pretty useless as a convenient reference."