Confronta offerte su Amazon
Con la fotocamera del cellulare scansiona il codice di seguito e scarica l'app Kindle.
Head First Object-Oriented Analysis and Design: A Brain Friendly Guide to OOA&D: The Best Introduction to Object Orientated Programming Copertina flessibile – 19 dicembre 2006
- Scegli tra gli oltre 8.500 punti di ritiro in Italia
- Spedizione GRATUITA senza alcun importo minimo. I clienti Prime beneficiano di consegne illimitate presso i punti di ritiro senza costi aggiuntivi
- Trova il tuo punto di ritiro preferito ed aggiungilo alla tua rubrica degli indirizzi
- Indica il punto di ritiro in cui vuoi ricevere il tuo ordine nella pagina di conferma d’ordine
Migliora il tuo acquisto
"Head First Object Oriented Analysis and Design is a refreshing look at subject of OOAD. What sets this book apart is its focus on learning. The authors have made the content of OOAD accessible, usable for the practitioner."
Ivar Jacobson, Ivar Jacobson Consulting
"I just finished reading HF OOA&D and I loved it! The thing I liked most about this book was its focus on why we do OOA&D-to write great software!"
Kyle Brown, Distinguished Engineer, IBM
"Hidden behind the funny pictures and crazy fonts is a serious, intelligent, extremely well-crafted presentation of OO Analysis and Design. As I read the book, I felt like I was looking over the shoulder of an expert designer who was explaining to me what issues were important at each step, and why."
Edward Sciore,Associate Professor, Computer Science Department, Boston College
Tired of reading Object Oriented Analysis and Design books that only makes sense after you're an expert? You've heard OOA&D can help you write great software every time-software that makes your boss happy, your customers satisfied and gives you more time to do what makes you happy.
Head First Object-Oriented Analysis & Design shows you how to analyze, design, and write serious object-oriented software: software that's easy to reuse, maintain, and extend; software that doesn't hurt your head; software that lets you add new features without breaking the old ones. Inside you will learn how to:
- Use OO principles like encapsulation and delegation to build applications that are flexible
- Apply the Open-Closed Principle (OCP) and the Single Responsibility Principle (SRP) to promote reuse of your code
- Leverage the power of design patterns to solve your problems more efficiently
- Use UML, use cases, and diagrams to ensure that all stakeholders arecommunicating clearly to help you deliver the right software that meets everyone's needs.
By exploiting how your brain works, Head First Object-Oriented Analysis & Design compresses the time it takes to learn and retain complex information. Expect to have fun, expect to learn, expect to be writing great software consistently by the time you're finished reading this!
Descrizione del libro
Brett McLaughlin is a bestselling and award-winning non-fiction author. His books on computer programming, home theater, and analysis and design have sold in excess of 100,000 copies. He has been writing, editing, and producing technical books for nearly a decade, and is as comfortable in front of a word processor as he is behind a guitar, chasing his two sons and his daughter around the house, or laughing at reruns of Arrested Development with his wife.
Brett spends most of his time these days on cognitive theory, codifying and expanding on the learning principles that shaped the Head First series into a bestselling phenomenon. He's curious about how humans best learn, why Star Wars was so formulaic and still so successful, and is adamant that a good video game is the most effective learning paradigm we have.
Gary Pollice is a self-labeled curmudgeon (that's a crusty, ill- tempered, usually old man) who spent over 35 years in industry trying to figure out what he wanted to be when he grew up. Even though he hasn't grown up yet, he did make the move in 2003 to the hallowed halls of academia where he has been corrupting the minds of the next generation of software developers with radical ideas like, "develop software for your customer, learn how to work as part of a team, design and code quality and elegance and correctness counts, and it's okay to be a nerd as long as you are a great one." Gary is also a co-author of Head First Object-Oriented Analysis and Design.Gary is a Professor of Practice (meaning he had a real job before becoming a professor) at Worcester Polytechnic Institute. He went to WPI because he was so impressed with the WPI graduates that he's worked with over the years. He lives in central Massachusetts with his wife, Vikki, and their two dogs, Aloysius and Ignatius. When not working on geeky things he ... well he's always working on geeky things. You can see what he's up to by visiting his WPI home page at http://web.cs.wpi.edu/~gpollice/. Feel free to drop him a note and complain or cheer about the book.
Dave West would like to describe himself as sheik geek. Unfortunately no one else would describe him in that way. They would say he is a professional Englishman who likes to talk about software development best practices with the passion and energy of an evangelical preacher. Recently Dave has moved to Ivar Jacobson Consulting, where he runs the Americas and can combine his desire to talk about software development and spread the word on rugby and football, and argue that cricket is more exciting that baseball.Before running the Americas for Ivar Jacobson Consulting, Dave worked for a number of years at Rational Software (now a part of IBM). Dave held many positions at Rational and then IBM, including Product Manager for RUP where he introduced the idea of process plug-ins and agility to RUP. Dave still laments the days when he use to sit in a cube and write software in the city of London. This is where he believes he cut his teeth writing big insurance systems with nothing but a green screen and a process flow chart.
Dave can be contacted at firstname.lastname@example.org, and if he is not with customers or drinking warm beer with his friends in Boston, he will email you back.
- Editore : O'Reilly Media; 1° edizione (19 dicembre 2006)
- Lingua : Inglese
- Copertina flessibile : 636 pagine
- ISBN-10 : 0596008678
- ISBN-13 : 978-0596008673
- Peso articolo : 1.2 kg
- Dimensioni : 20.32 x 3.51 x 23.5 cm
- Posizione nella classifica Bestseller di Amazon: n. 2,769 in Programmazione (Libri)
- n. 132,467 in Libri in inglese
- Recensioni dei clienti:
Informazioni sugli autori
Le recensioni migliori da altri paesi
My first impression was that it was fairly dull, and I actually put it aside about halfway through to read something else. I came back to it last week and finished it off, and ended up very pleased with it.
If you're a programmer (like me), you'll probably be frustrated by the lack of code in the first half of the book. In fairness, this is more a factor of the design process. Much as we love to jump in and start coding, this isn't the best way to do it. This book teaches the way it should be done, so you don't get to write code until some time later.
Once you've got to the end, the whole process seems much clearer and easier to follow than it looked earlier. The book ends with a decent case study of analysis of an application to work out routes on a subway, and working through this clarified what the rest of the book had been explaining.
So, if you're prepared for the fact that "doing it the right way" means not writing code straight away, then this book is excellent.
HOWEVER, there is a big negative against this book, and this is something the Head First people need to think about as it affected the otherwise excellent Head First Design Patterns in the same way...
Amazing as it may seem, there are some people who write applications in languages other than Java. I know the Head First team won't believe this, but Java isn't the only OO language out there. In fact, I'll let you into a secret, design patterns and OO analysis are actually language agnostic. You don't need to tie yourself to ANY language. You can teach all this stuff without tying yourself down to any specific language.
Sure, when you supply code, you have to use a language, and I don't think anyone would have any strong objections to that language being Java. It's a common, fully OO language, whose syntax is so close to C# and C++ that programmers in those languages shouldn't have any problem reading the Java.
The problem is when the text and explanation keep droning on about Java when it's irrelevant, and (worse) when they use Java-specific things in the code. There is no necessity for this, and it makes the book less accessible for non-Java developers. It would be really easy to have written this book in a language-agnostic way, even with code samples in Java. This is something that really needs to be done for both of these books, and would have made both of them five star books.