Reply to thread

Message: <blockquote data-quote="soundless" data-source="post: 13474329" data-attributes="member: 415227"><img src="http://i40.fastpic.ru/big/2012/0921/9b/98bf5cc84203647c0bdf4dddb6b10e9b.jpg" alt="" class="fr-fic fr-dii fr-draggable " style="" /> Published: 1996-07-10 | ISBN: 0201633620 | DJVU | 896 pages | 18 MB    Developing a large-scale software system in C++ requires more than just a sound understanding of the logical design issues covered in most books on C++ programming. To be successful, you will also need a grasp of physical design concepts that, while closely tied to the technical aspects of development, include a dimension with which even expert software developers may have little or no experience.This is the definitive book for all C++ software professionals involved in large development efforts such as databases, operating systems, compilers, and frameworks. It is the first C++ book that actually demonstrates how to design large systems, and one of the few books on object-oriented design specifically geared to practical aspects of the C++ programming language.In this book, Lakos explains the process of decomposing large systems into physical (not inheritance) hierarchies of smaller, more manageable components. Such systems with their acyclic physical dependencies are fundamentally easier and more economical to maintain, test, and reuse than tightly interdependent systems. In addition to explaining the motivation for following good physical as well as logical design practices, Lakos provides you with a catalog of specific techniques designed to eliminate cyclic, compile-time, and link-time (physical) dependencies. He then extends these concepts from large to very large systems. The book concludes with a comprehensive top-down approach to the logical design of individual components. Appendices include a valuable design pattern "Protocol Hierarchy" designed to avoid fat interfaces while minimizing physical dependencies; the details of implementing an ANSI C compatible C++ procedural interface; and a complete specification for a suite of UNIX-like tools to extract and analyze physical dependencies. Practical design rules, guidelines, and principles are also collected in an appendix and indexed for quick reference.Download:[code]http://www.ortofiles.com/6tml7cnhs3mr/Large-Scale_C__.zip[/code]</blockquote>

Verification: Payakata winadi keeyak tibeda?

Top Bottom

Search

Latest ads

Reply to thread