Head First Object Oriented Analysis and Design A Brain


Head First Object Oriented Analysis and Design A Brain Friendly Guide to OOAD Head First [PDF / Epub] ✎ Head First Object Oriented Analysis and Design A Brain Friendly Guide to OOAD Head First ☂ Brett McLaughlin – Thomashillier.co.uk 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 fo Head First Object Oriented Analysis Object Oriented PDF Í 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 Head First PDF/EPUB or of OOAD accessible usable for the practitioner Ivar Jacobson Ivar Jacobson ConsultingI just finished reading HF OOAD and I loved it The thing I liked most about this book was its focus First Object Oriented PDF/EPUB æ on why we do OOAD to write great software Kyle Brown Distinguished Engineer IBMHidden behind the funny pictures and crazy fonts is a serious intelligent extremely well crafted presentation of OO Analysis First Object Oriented Analysis and PDF or 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 OOAD can help you write great software every time software that makes your boss happy your customers satisfied and gives you time to do what makes you happyBut how.

  • Paperback
  • 600 pages
  • Head First Object Oriented Analysis and Design A Brain Friendly Guide to OOAD Head First
  • Brett McLaughlin
  • English
  • 24 October 2015
  • 9780596008673

10 thoughts on “Head First Object Oriented Analysis and Design A Brain Friendly Guide to OOAD Head First

  1. Masterofoneinchpunch Masterofoneinchpunch says:

    I like the Head First series and even Head Rush for its innovative and fun approach for introductory software topics I've had small concerns on all of them but I have never been as ambivalent as I have for this book I know a big part of this problem was that it was rewritten expeditious I am still not sure of the reason why and it shows throughout the book with spelling logic and code errorsYou can tell that the first chapter was rushed There are several spelling and programming mistakes The most egregious is where they ask you to look through some code to find what FIRST you change and then they answer that uestion with a much smaller problem the main problem was they forgot to add a return statement pg5 and they write about the inconsistency of using String based searching It has also been mentioned by several reviewers of the use of the method name matches which only makes sense for regex not for an euals operation I also did not like the search example how can you not think of price in a search? The best part of this chapter is the mantra that should be practiced by many engineers Make sure your software does what the customer wants it to doThe next few chapters are definitely better though still some spelling mistakes They are a good read for beginners and intermediate programmers on gathering reuirements change of these reuirements and analysis The ideas are a bit simplistic though it is good to get many programmers used to the idea of UML and use cases and using them to drive reuirement gathering and textual analysis Intermediate and advanced readers familiar with use cases will gain from reading Alistair Cockburn's Writing Effective Use Cases or will already have read it and for further UML reading should go with UML Distilled by Martin FowlerWhen the book gets back to design I see some problems with the coding The designer has this bizarre idea of abstracting all properties under the guise of encapsulate what varies into a Map attribute to lessen the amount of subclasses for instruments While initially this may seem a good idea it gets rid of all type safe coding you can now safely assign an instrument type to a backwood for the instrument you cannot have behavior from the instruments this is mentioned in the book and if you put a property with one letter misspelled or capitalized out of place you now have a bug one that you might have trouble finding thereby increasing maintenance costs Too much flexibility makes the code ambiguousAfter design the studies get to solving really big problems architecture design principles and iterating and testing These chapters I enjoyed much especially the chapter on design principles with the beginning mantra that Originality is Overrated This chapter goes over basic principles such as OCP open closed principle DRY don't repeat yourself SRP single responsibility principle and LSP Liskov Substitution PrincipleThen the book last chapter the ooad lifecycle sums the lessons in the book in one large somewhat contrived but these type of examples always are program for the Objectville Subway Then two terse appendixes dealing with ten additional OOAD topics and OO concepts should make the reader realize that this book is just an introductory sliver of what needs to be learned for a sagacious software acumenThis book is useful for programmers with a bit of Java or C# knowledge who want to get a good overview of OOAD This book is useful because it teaches important OO vernacular and a simple holistic approach to iterative development If the book did not have a uickly done feeling better design and fewer mistakes I would have liked this book This book is a good candidate for a second edition If you want a thorough explanation of these topics I recommend The Object Primer by Scott Ambler as one of my favorite books for a good introduction to OOAD

  2. Nariman Nariman says:

    Head First Object Oriented Analysis and Design tries to cover most of the Object Oriented principles and paradigms in a completely non boring way It is a good starting point to think about software in terms of objects and classes

  3. Antony Thomas Antony Thomas says:

    Very practical reads like a novel My style of writing if I were to write a book

  4. Nimrod Daniel Nimrod Daniel says:

    I started the book a long time time got to the 80 85% pretty uickly it's a uick read and left the book for a very loooong time until nowAll in all It's a nice book on Object Oriented design and analysis though most of my reading I felt like the book tries to explain things to a 10 years old kid It tries to convey the principles of OO though I think it could have been much better in a shorter book Some OO tutorials and stackoverflow provide a better source for that topic355

  5. Madhur Bhargava Madhur Bhargava says:

    The book is very well written and covers many basic aspects of analysis and design of software from the beginner's point of view One of the plus points is due to the reason that apart from the regular analysis and design this book also discusses other important aspects of software development such as being customer centric and managing riskto name a few However some of the readers may find the pace of the book as slow as it really hammers a point down to its details Highly recommend this book especially to engineers who are in nascent stages of their career

  6. Ben Rand Ben Rand says:

    Another good book in the Head First series This covers the process of preparing to code mostly So if you're expecting much code you'll need to look elsewhere A lot of this was review to me which is why I only gave it 4 stars It was well written with clear examples of everything discussed

  7. Gökçe Gökçe says:

    A great brain friendly introductory book for OOAD A reader of this book can get a very good grasp of the OOAD fundamentals and will be ready to go to the advanced software architecture design with UML

  8. Fernando Fernandes Fernando Fernandes says:

    It's an OK book The writing style is not my cup of tea it tries too hard to simplify things to a point where it becomes difficult to focus on the original concept take OO for instance But I would recommend the title for beginners

  9. William Lou William Lou says:

    Chapter1 class GuitarSpec is abstracted from Guitar so that it can be easily modified without changing class Guitar and Inventory;Guitar is used in Guitar Inventory

  10. Yonathan Yonathan says:

    This book doesn't consider all possibilities that could happen for its early to mid chapter programming cases However in overall the book explains difficult OOAD materials superbly

Leave a Reply

Your email address will not be published. Required fields are marked *