Object-oriented Analysis and design

The object-oriented paradigm is a new and radically different way of thinking about programming, and many people begin to frown on how to construct a project. In fact, we can make a "good" design that leverages all the benefits that OOP offers.

Most of the books on OOP analysis and design are unsatisfactory. Most of these books are filled with inexplicable words, clumsy style, and many statements that seem important (note ⑨). I think this kind of book is best compressed into a chapter or so in the space, at most a very thin book. Ironically, those who specialize in the management of complex things tend to have a lot of trouble writing plain, clear books. If you can not speak simple and direct, not many people like to see this aspect of the content. After all, the whole purpose of OOP is to make the process of software development easier. While this may affect the livelihoods of those who like to solve complex problems, why not make things simpler from the start? Therefore, I hope I can lay a good foundation for everyone from the beginning, as far as possible in a few paragraphs to clear analysis and design problems.

⑨: The best entry book is still the object-oriented design withapplications, 2nd edition of Grady Booch, Wiely & Sons was published in 1996. The book is very deep and easy to understand, although his notation is unnecessarily complicated for most designs.