which of these OO books for 1st reading ?
in [OOP]
|
Prev: Change a group of static functions into a class: Is this a design pattern?
Next: Scholarships for PhD study in Informatics@Edinburgh
From: pandit on 3 Jan 2008 10:45 > On Jan 3, 1:38 am, "H. S. Lahman" <h...(a)pathfindermda.com> wrote: > If you had problems with the Booch book, then I think you will have > similar problems with the others. Booch's book is pretty introductory > OOA/D stuff and I believe his target audience was novice software > developers with little or no OOA/D experience. > I can only suggest going back and re-reading it from the beginning while > thinking about how he uses OO constructs to abstract the problem space. > Better yet would be finding someone with OO experience who could provide > some mentoring for you. I tried again with what you told you on my mind and this time I understood the things. This is what I think about Booch now: 1.) he talks about *business*. I mean, in C++, should I use std::copy algorithm of simply an array of pointers is a coding/programming issue but Booch's book seems like I am reading business management rather than programming. 2.) To me, it seem slike he is teaching me how to manage programmers, how to be a good manager and that is related with management,a totally different and unrelated issue. 3.) seems like he i steaching me how to runa corporate software business. so we have problems like Taxes, patents, administration issues. Look there is no talk about programming, we will just bu a bunch of idiotss carrying Master's degrees with 80% tags and they will worry about coding stuff. Our motive is about making money usign software as a way. this is all i felt about OOA & D with Applications. I started to consider should I spend money on "Algorithms and Data-Structures" book, at least that will be programming But As i said I just read a few pages, n ot the whole book, hence you know better. I will wait for your reply.
From: Phlip on 3 Jan 2008 10:59 pandit wrote: > 1.) he talks about *business*. I mean, in C++, should I use std::copy > algorithm of simply an array of pointers is a coding/programming issue > but Booch's book seems like I am reading business management rather > than programming. Read /Design Patterns/ first. Its only prerequisite is essentially you have attempted some OO models, in any language, first. > 2.) To me, it seem slike he is teaching me how to manage programmers, > how to be a good manager and that is related with management,a totally > different and unrelated issue. He might be practicing "translationism", where you describe a high-level model to low-level programmers, and they implement it. That's a worst-practice. > 3.) seems like he i steaching me how to runa corporate software > business. so we have problems like Taxes, patents, administration > issues. Look there is no talk about programming, we will just bu a > bunch of idiotss carrying Master's degrees with 80% tags and they will > worry about coding stuff. Our motive is about making money usign > software as a way. Read /Refactoring/, then /Refactoring to Patterns/. Programming is about implementing each feature (with its automated tests), and then merging each features' design together. (This is what "translationism" attempts to do, before coding, and without tests.) The tests help your business side request new features. -- Phlip http://www.oreilly.com/catalog/9780596510657/ ^ assert_xpath
From: H. S. Lahman on 3 Jan 2008 15:57 Responding to Pandit... > I tried again with what you told you on my mind and this time I > understood the things. This is what I think about Booch now: > > 1.) he talks about *business*. I mean, in C++, should I use std::copy > algorithm of simply an array of pointers is a coding/programming issue > but Booch's book seems like I am reading business management rather > than programming. That is correct. Booch's book is about software /design/, not software programming. Note that OOA/D has its own notation that is far more abstract than OOPLs. > > 2.) To me, it seem slike he is teaching me how to manage programmers, > how to be a good manager and that is related with management,a totally > different and unrelated issue. > > 3.) seems like he i steaching me how to runa corporate software > business. so we have problems like Taxes, patents, administration > issues. Look there is no talk about programming, we will just bu a > bunch of idiotss carrying Master's degrees with 80% tags and they will > worry about coding stuff. Our motive is about making money usign > software as a way. Not quite. He is teaching how to abstract the business domain context. The OO paradigm employs problem space abstraction to ensure that the software structure emulates the structure of the customer's business domain. The reason for doing that is to provide more efficient response to change. Customers do not like change any more than software developers. So they adopt to change in their environment in ways that minimize the disruption of their existing infrastructure. Eventually changes in the business domain will filter down to the software in the form of new or modified requirements. If the software structure closely parallels the business domain structure, then those changes should provide minimal disruption to the software structure when they are implemented. That's because the customer has already figured out the path of least resistance for change. IOW, the OO paradigm is about making the software more maintainable in the face of volatile requirements and the primary way it accomplishes that is through problem space abstraction as the software structure is designed. -- There is nothing wrong with me that could not be cured by a capful of Drano. H. S. Lahman hsl(a)pathfindermda.com Pathfinder Solutions http://www.pathfindermda.com blog: http://pathfinderpeople.blogs.com/hslahman "Model-Based Translation: The Next Step in Agile Development". Email info(a)pathfindermda.com for your copy. Pathfinder is hiring: http://www.pathfindermda.com/about_us/careers_pos3.php. (888)OOA-PATH
From: H. S. Lahman on 3 Jan 2008 16:05 Responding to Phlip... >> 1.) he talks about *business*. I mean, in C++, should I use std::copy >> algorithm of simply an array of pointers is a coding/programming issue >> but Booch's book seems like I am reading business management rather >> than programming. > > Read /Design Patterns/ first. Its only prerequisite is essentially you have > attempted some OO models, in any language, first. Design patterns assume one already has a solid OOA/D base. The OP doesn't have that so the GoF book will be like a foreign language. > >> 2.) To me, it seem slike he is teaching me how to manage programmers, >> how to be a good manager and that is related with management,a totally >> different and unrelated issue. > > He might be practicing "translationism", where you describe a high-level > model to low-level programmers, and they implement it. That's a > worst-practice. Nonsense. There are no "low level programmers" in a translation shop. Translation is about automation of the computing space. The application developers create the OOA model and the rest of the application implementation is completely automated. The transformation engine for an OOA model serves exactly the same function as a compiler for a 3GL. -- There is nothing wrong with me that could not be cured by a capful of Drano. H. S. Lahman hsl(a)pathfindermda.com Pathfinder Solutions http://www.pathfindermda.com blog: http://pathfinderpeople.blogs.com/hslahman "Model-Based Translation: The Next Step in Agile Development". Email info(a)pathfindermda.com for your copy. Pathfinder is hiring: http://www.pathfindermda.com/about_us/careers_pos3.php. (888)OOA-PATH
From: WALLYWORLD on 11 Jan 2008 11:54
i like a data analysis bok by von halle and fleming. these are both women who wrote this book as a handbook for relational database modelers. The handbook principle addresses some of the "technology friendliness" question, meaning that it is a general guide rather than on specifics. There is a god summary of the book's chapters in the front. Improtantly designer rules, and references for a review of your design. They use an example for Customer-Order system. GL (good luk) "pandit" <jalaf28(a)gmail.com> wrote in message news:1f596d14-29e1-43f7-9d00-460864b1922f(a)u10g2000prn.googlegroups.com... > > On Jan 3, 1:38 am, "H. S. Lahman" <h...(a)pathfindermda.com> wrote: > > If you had problems with the Booch book, then I think you will have > > similar problems with the others. Booch's book is pretty introductory > > OOA/D stuff and I believe his target audience was novice software > > developers with little or no OOA/D experience. > > > I can only suggest going back and re-reading it from the beginning while > > thinking about how he uses OO constructs to abstract the problem space. > > Better yet would be finding someone with OO experience who could provide > > some mentoring for you. > > > I tried again with what you told you on my mind and this time I > understood the things. This is what I think about Booch now: > > 1.) he talks about *business*. I mean, in C++, should I use std::copy > algorithm of simply an array of pointers is a coding/programming issue > but Booch's book seems like I am reading business management rather > than programming. > > 2.) To me, it seem slike he is teaching me how to manage programmers, > how to be a good manager and that is related with management,a totally > different and unrelated issue. > > 3.) seems like he i steaching me how to runa corporate software > business. so we have problems like Taxes, patents, administration > issues. Look there is no talk about programming, we will just bu a > bunch of idiotss carrying Master's degrees with 80% tags and they will > worry about coding stuff. Our motive is about making money usign > software as a way. > > this is all i felt about OOA & D with Applications. I started to > consider should I spend money on "Algorithms and Data-Structures" > book, at least that will be programming But As i said I just read a > few pages, n ot the whole book, hence you know better. I will wait for > your reply. |