C++軟件設計 影印版 9787576605532 (德)克勞斯.伊格爾伯格(Klaus lglberger)著

*完成訂單後正常情形下約兩周可抵台。
*本賣場提供之資訊僅供參考，以到貨標的為正確資訊。
印行年月：202303*若逾兩年請先於客服中心或Line洽詢存貨情況，謝謝。
台灣(台北市)在地出版社，每筆交易均開具統一發票，祝您中獎最高1000萬元。
書名：C++軟件設計 影印版
ISBN：9787576605532
出版社：東南大學
著編譯者：(德)克勞斯.伊格爾伯格(Klaus lglberger)著
頁數：415
所在地：中國大陸 *此為代購商品
書號：1533553
可大量預訂，請先連絡。

【台灣高等教育出版社簡體書】 C++軟件設計 影印版 787576605532 (德)克勞斯.伊格爾伯格(Klaus lglberger)著

內容簡介

好的軟體設計對於項目成功至關重要，但設計軟體並非易事。你需要對設計決策的結果有深刻的理解，並很好地了解可用的設計方案。通過本書，有經驗的C++開發人員將對實用這種現代語言的軟體設計有一個透徹的、實用的、前所未有的理解。 C++培訓師和顧問Klaus Iglberger解釋了如何管理依賴性和抽象，提高軟體實體的可變性和可擴展性，以及應用和實現現代設計模式來幫助你利用現今的一切可能性。軟體設計是軟體項目最重要的一環，因為它影響到軟體最重要的屬性：可維護性、可變性和可擴展性。

作者簡介

克勞斯·伊格爾伯格 Klaus Iglberger是一名自由職業的C++培訓師和顧問。他在世界各地開辦的熱門培訓課程中分享了個人15年的C++專業知識，並經常在C++會議上發言。自2010年獲得博士學位以來，Klaus一直專註于大型軟體設計和提高軟體的可維護性。

目錄

Preface
1 The Art of Software Design
Guideline 1: Understand the Importance of Software Design
Features Are Not Software Design
Software Design: The Art of Managing Dependencies and Abstractions
The Three Levels of Software Development
The Focus on Features
The Focus on Software Design and Design Principles
Guideline 2: Design for Change
Separation of Concerns
An Example of Artificial Coupling
Logical Versus Physical Coupling
Don't Repeat Yourself
Avoid Premature Separation of Concerns
Guideline 3: Separate Interfaces to Avoid Artificial Coupling
Segregate Interfaces to Separate Concerns
Minimizing Requirements of Template Arguments
Guideline 4: Design for Testability
How to Test a Private Member Function
The True Solution: Separate Concerns
Guideline 5: Design for Extension
The Open-Closed Principle
Compile-Time Extensibility
Avoid Premature Design for Extension
2 The Art of Building Abstractions
Guideline 6: Adhere to the Expected Behavior of Abstractions
An Example of Violating Expectations
The Liskov Substitution Principle
Criticism of the Liskov Substitution Principle
The Need for Good and Meaningful Abstractions
Guideline 7: Understand the Similarities Between Base Classes and Concepts
Guideline 8: Understand the Semantic Requirements of Overload Sets
The Power of Free Functions: A Compile-Time Abstraction Mechanism
The Problem of Free Functions: Expectations on the Behavior
Guideline 9: Pay Attention to the Ownership of Abstractions
The Dependency Inversion Principle
Dependency Inversion in a Plug-In Architecture
Dependency Inversion via Templates
Dependency Inversion via Overload Sets
Dependency Inversion Principle Versus Single-Responsibility Principle
Guideline 10: Consider Creating an Architectural Document
3 The Purpose of Design Patterns
Guideline 11: Understand the Purpose of Design Patterns
A Design Pattern Has a Name
A Design Pattern Carries an Intent
A Design Pattern Introduces an Abstraction
A Design Pattern Has Been Proven
Guideline 12: Beware of Design Pattern Misconceptions
Design Patterns Are Not a Goal
Design Patterns Are Not About Implementation Details
Design Patterns Are Not Limited to Object-Oriented Programming or
Dynamic Polymorphism
Guideline 13: Design Patterns Are Everywhere
Guideline 14: Use a Design Pattern's Name to Communicate Intent
4 The Visitor Design Pattern
Guideline 15: Design for the Addition of Types or Operations
A Procedural Solution
An Object-Oriented Solution
Be Aware of the Design Choice in Dynamic Polymorphism
Guideline 16: Use Visitor to Extend Operations
Analyzing the Design Issues
The Visitor Design Pattern Explained
Analyzing the Shortcomings of the Visitor Design Pattern
Guideline 17: Consider std:variant for Implementing Visitor
Introduction to std::variant
Refactoring the Drawing of Shapes as a Value-Based， Nonintrusive Solution
Performance Benchmarks
Analyzing the Shortcomings of the std :variant Solution
Guideline 18: Beware the Performance of Acyclic Visitor
5 The Strategy and Command Design Patterns
Guideline 19: Use Strategy to Isolate How Things Are Done
Analyzing the Design Issues
The Strategy Design Pattern Explained
Analyzing the Shortcomings of the Naive Solution
Comparison Between Visitor and Strategy
Analyzing the Shortcomings of the Strategy Design Pattern
Policy-Based Design
Guideline 20: Favor Composition over Inheritance
Guideline 21: Use Command to Isolate What Things Are Done
The Command Design Pattern Explained
The Command Design Pattern Versus the Strategy Design Pattern
Analyzing the Shortcomings of the Command Design Pattern
Guideline 22: Prefer Value Semantics over Reference Semantics
The Shortcomi
詳細資料或其他書籍請至台灣高等教育出版社查詢，查後請於客服中心或Line或本社留言板留言，我們即儘速上架。

大陸簡體正版圖書，訂購後正常情形下約兩周可抵台。