Large-scale C++ software design
著者
書誌事項
Large-scale C++ software design
(Addison-Wesley professional computing series)
Addison-Wesley Pub. Co., c1996
- : pbk.
- タイトル別名
-
Large-scale C plus plus software design
大学図書館所蔵 全7件
  青森
  岩手
  宮城
  秋田
  山形
  福島
  茨城
  栃木
  群馬
  埼玉
  千葉
  東京
  神奈川
  新潟
  富山
  石川
  福井
  山梨
  長野
  岐阜
  静岡
  愛知
  三重
  滋賀
  京都
  大阪
  兵庫
  奈良
  和歌山
  鳥取
  島根
  岡山
  広島
  山口
  徳島
  香川
  愛媛
  高知
  福岡
  佐賀
  長崎
  熊本
  大分
  宮崎
  鹿児島
  沖縄
  韓国
  中国
  タイ
  イギリス
  ドイツ
  スイス
  フランス
  ベルギー
  オランダ
  スウェーデン
  ノルウェー
  アメリカ
注記
Includes bibliographical references (p. 833-834) and index
内容説明・目次
内容説明
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. 0201633620B04062001
目次
Preface.
0. Introduction.
From C to C++.
Using C++ to Develop Large Projects.
Reuse.
Quality.
Software Development Tools.
Summary.
I. BASICS.
1. Preliminaries.
Multi-File C++ Programs.
typedef Declarations.
Assert Statements.
A Few Matters of Style.
Iterators.
Logical Design Notation.
Inheritance versus Layering.
Minimality.
Summary.
2. Ground Rules.
Overview.
Member Data Access.
The Global Name Space.
Include Guards.
Redundant Include Guards.
Documentation.
Identifier-Naming Conventions.
Summary.
II. PHYSICAL DESIGN CONCEPTS.
3. Components.
Components versus Classes.
Physical Design Rules.
The DependsOn Relation.
Implied Dependency.
Extracting Actual Dependencies.
Friendship.
Summary.
4. Physical Hierarchy.
A Metaphor for Software Testing.
A Complex Subsystem.
The Difficulty in Testing "Good" Interfaces.
Design for Testability.
Testing in Isolation.
Acyclic Physical Dependencies.
Level Numbers.
Hierarchical and Incremental Testing.
Testing a Complex Subsystem.
Testing versus Tested.
Cyclic Physical Dependencies.
Cumulative Component Dependency (CCD).
Physical Design Quality.
Summary.
5. Levelization.
Some Causes of Cyclic Physical Dependencies.
Escalation.
Demotion.
Opaque Pointers.
Dumb Data.
Redundancy.
Callbacks.
Manager Class.
Factoring.
Escalating Encapsulation.
Summary.
6. Insulation.
From Encapsulation to Insulation.
C++ Constructs and Compile-Time Coupling.
Partial Insulation Techniques.
Total Insulation Techniques.
The Procedural Interface.
To Insulate or Not to Insulate.
Summary.
7. Packages.
From Components to Packages.
Registered Package Prefixes.
Package Levelization.
Package Insulation.
Package Groups.
The Release Process.
The main Program.
Start-Up Time.
Summary.
III. LOGICAL DESIGN ISSUES.
8. Architecting a Component.
Abstractions and Components.
Component Interface Design.
Degrees of Encapsulation.
Auxiliary Implementation Classes.
Summary.
9. Designing a Function.
Function Specification.
Fundamental Types Used in the Interface.
Special Case Functions.
Summary.
10. Implementing an Object.
Member Data.
Function Definitions.
Memory Management.
Using C++ Templates in Large Projects.
Summary.
Appendix A. Protocol Hierarchy.
Appendix B. Implementing an ANSI C-Compatible C++ Interface.
Appendix C. A Dependency Extractor/Analyzer Package.
Appendix D. Quick Reference.
Index. 0201633620T04062001
「Nielsen BookData」 より