| Description |
1 online resource (xiv, 359 pages) : illustrations (some color) |
| Contents |
Intro -- Preface -- Contents -- 1: What Is Software Design? -- 1.1 Overview -- 1.2 The Nature of Software Design -- 1.3 Software Design in the Context of Software Lifecycles -- 1.4 Software Design in the Context of Analytical Thinking -- 1.5 Software Design in the Context of Communication -- 1.6 Software Design in the Context of Design Formalism -- 1.7 Summary -- References -- 2: The Paradigm of Object Orientation and Beyond -- 2.1 Overview -- 2.2 What Is Object Orientation? -- 2.2.1 Data Abstraction -- 2.2.2 Object Types -- 2.2.3 Inheritance -- 2.3 The Paradigm of Object-Oriented Design |
|
2.4 Embracing Multi-paradigm Design -- 2.5 Summary -- References -- 3: Essentials of Object-Oriented Design -- 3.1 Overview -- 3.2 Data Type, Data Abstraction, and Type-Safe Practices -- 3.3 More About Interfaces -- 3.3.1 Software Sustainability -- 3.3.2 The Role of Interfaces Through the Lens of Data Structures -- 3.3.3 Programming to an Interface, Not to an Implementation -- 3.3.4 Interface Segregation -- 3.3.5 Section Summary -- 3.4 Abstract Classes and Design of Type Hierarchies -- 3.4.1 Use of Abstract Classes -- 3.4.2 A Case Study -- 3.4.3 Section Summary -- 3.5 When to Avoid Inheritance |
|
3.6 Subtyping with Consistent Object Behavior -- 3.6.1 Representation Invariants -- 3.6.2 Liskov Substitution Principle -- 3.6.3 Design by Contract -- 3.7 Lazy Object Creation Allowing Delayed Decision-Making -- 3.8 Object-Oriented Design in the Large: Design Principles -- 3.9 Summary -- References -- 4: Design of Methods -- 4.1 Overview -- 4.2 Essential Characteristics of a Method -- 4.2.1 Procedural Abstraction and Modularity -- 4.2.2 Design Attributes of a Method -- 4.3 Cohesion of a Method -- 4.4 Method Coupling -- 4.4.1 The Phenomenon of Coupling -- 4.4.2 Effects of Coupling |
|
4.4.3 Categorization of Coupling -- 4.5 Module Redesign and Code Refactoring -- 4.6 Method Specification -- 4.6.1 The Nature of a Module Specification -- 4.6.2 Method Specification with Some Formalism -- 4.7 A Case Study: Overriding ̀̀Equals ́́ -- 4.8 Summary -- References -- 5: Design of Objects -- 5.1 Overview -- 5.2 The Context and Process -- 5.3 Essentials of Object Design -- 5.3.1 Object to Model One Thing -- 5.3.2 Diverse Object Design Possibilities -- 5.3.3 Prototyping Object Interaction -- 5.3.4 Designing Objects Around a Structural Style -- 5.3.5 More About Object Discovery |
|
5.3.6 Design to Ensure Objects ́Behavioral Correctness -- 5.4 Design of Control Objects -- 5.4.1 Highly Centralized vs. Coordinated Controls -- 5.4.2 Process Control with a Framework -- 5.4.3 Controls for Event-Driven Systems -- 5.4.4 Different Control Roles -- 5.4.5 Objects Are Designed to Control -- 5.5 Object Cohesion and Coupling -- 5.5.1 What Are the Issues? -- 5.5.2 Law of Demeter -- 5.5.3 Objects with No Overlapping Behavior -- 5.6 Iterative Design of Objects -- 5.6.1 Initial Design of Domain Abstractions -- 5.6.2 Subsequent Design Validation and Refactoring -- 5.7 Summary |
| Summary |
This textbook provides a balanced coverage on software design, including design principles, methodologies, and techniques in contexts of designing modules of small and larger sizes with a multi-paradigm viewpoint emphasizing design trade-off. Commonly used design diagrams and patterns are also covered in terms of the design ideas behind and their effective use. The book also explores what (software) design thinking is, the role it plays in a design process, and ways to promote it. Despite object orientation being still the center of attention, there is a strong promotion throughout the book that software design should consider all appropriate design paradigms and methodologies. The book is organized in 10 chapters. Chapter 1 is dedicated to an exploration of what software design may be and entail. Next, chapters 2 and 3 are designed to help readers better understand object orientation, and the essentials of object-oriented design. Chapter 4 is then dedicated to the design of methods, while chapters 5, 6, and 8 respectively include topics about the design of objects, modeling with the Unified Modeling Language, and the use of design patterns. Larger software elements are often directly responsible for the formation of software architecture, thus chapter 7 covers four kinds of larger software elements: libraries, components, frameworks, and microservices, and their architectural implications. Chapter 9 finally brings the presentation of software design to an end with a coverage on software architecture focusing on software architectural views. Case studies are important in learning how to design software, hence chapter 10 then gathers some small design case studies that can be used in earlier chapters as appropriate. These case studies can be extended in different ways to provide additional design opportunities. This textbook book is intended for a junior level undergraduate course on software design, yet the depth of the book makes it also appropriate for a design course at beginning graduate level. Professionals may also find the book useful in their professional development |
| Notes |
Description based upon print version of record |
| Subject |
Computer software -- Development.
|
|
Software architecture.
|
|
Computer software -- Development
|
|
Software architecture
|
| Form |
Electronic book
|
| ISBN |
9783031283116 |
|
3031283112 |
|
