Book Image

Real-World Implementation of C# Design Patterns

By : Bruce M. Van Horn II
5 (3)
Book Image

Real-World Implementation of C# Design Patterns

5 (3)
By: Bruce M. Van Horn II

Overview of this book

As a software developer, you need to learn new languages and simultaneously get familiarized with the programming paradigms and methods of leveraging patterns, as both a communications tool and an advantage when designing well-written, easy-to-maintain code. Design patterns, being a collection of best practices, provide the necessary wisdom to help you overcome common sets of challenges in object-oriented design and programming. This practical guide to design patterns helps C# developers put their programming knowledge to work. The book takes a hands-on approach to introducing patterns and anti-patterns, elaborating on 14 patterns along with their real-world implementations. Throughout the book, you'll understand the implementation of each pattern, as well as find out how to successfully implement those patterns in C# code within the context of a real-world project. By the end of this design patterns book, you’ll be able to recognize situations that tempt you to reinvent the wheel, and quickly avoid the time and cost associated with solving common and well-understood problems with battle-tested design patterns.

Related Content you might be interested in

Current Title:

Small book image
Real-World Implementation of C# Design Patterns
Bruce M. Van Horn II
Oct, 2022 | 442 pages
Small book image
Hands-On Application Development with PyCharm
Quan Nguyen | Bruce M Van Horn II
Oct, 2023 | 652 pages
Table of Contents (16 chapters)
Preface
Preface
Who this book is for
What this book covers
To get the most out of this book
Download the example code files
Download the images
Conventions used
Get in touch
Share Your Thoughts
1
Part 1: Introduction to Patterns (Pasta) and Antipatterns (Antipasta)
Part 1: Introduction to Patterns (Pasta) and Antipatterns (Antipasta)
Free Chapter
2
Chapter 1: There’s a Big Ball of Mud on Your Plate of Spaghetti
Chapter 1: There’s a Big Ball of Mud on Your Plate of Spaghetti
Technical requirements
No battle plan survives first contact with the enemy
The Big Ball of Mud
The Golden Hammer
A throwaway code example
How can patterns help?
Summary
Questions
Further reading
3
Chapter 2: Prepping for Practical Real-World Applications of Patterns in C#
Becoming a prepper
Technical requirements
Spaghetti < lasagna < ravioli – software evolution explained with pasta
The foundational principle – writing clean code
Creating maintainable systems using SOLID principles
Measuring quality beyond the development organization
Summary
Further reading
4
Part 2: Patterns You Need in the Real World
Part 2: Patterns You Need in the Real World
5
Chapter 3: Getting Creative with Creational Patterns
Chapter 3: Getting Creative with Creational Patterns
Technical requirements
The following story is fictitious
The initial design
No pattern implementation
The Simple Factory pattern
The Factory Method pattern
The Abstract Factory pattern
The Builder pattern
The Object Pool pattern
The Singleton pattern
Summary
Questions
Further reading
6
Chapter 4: Fortify Your Code With Structural Patterns
Chapter 4: Fortify Your Code With Structural Patterns
Technical requirements
B2B (back to bicycles)
The Decorator pattern
The Façade pattern
The Composite pattern
The Bridge pattern
Summary
Questions
Further reading
7
Chapter 5: Wrangling Problem Code by Applying Behavioral Patterns
Chapter 5: Wrangling Problem Code by Applying Behavioral Patterns
Technical requirements
Meanwhile, back at the bicycle factory
The Command pattern
The Iterator pattern
The Observer pattern
The Strategy pattern
Summary
Questions
8
Part 3: Designing New Projects Using Patterns
Part 3: Designing New Projects Using Patterns
9
Chapter 6: Step Away from the IDE! Designing with Patterns Before You Code
Chapter 6: Step Away from the IDE! Designing with Patterns Before You Code
Technical requirements
A bad day at the agency
Bumble Bikes factory – Dallas, Texas
A physical rehabilitation clinic – Dallas, Texas
Designing with patterns
The first pass
Adding patterns
The first design meeting
The second pass
The Builder pattern
The Singleton pattern
The Composite pattern
The Bridge pattern
The Command pattern
Summary
Questions
Further reading
10
Chapter 7: Nothing Left but the Typing – Implementing the Wheelchair Project
Chapter 7: Nothing Left but the Typing – Implementing the Wheelchair Project
The crack of noon
Setting up the project
Finishing up the composite
Implementing the Builder pattern
Adding the Singleton pattern
Painting the chairs with the Bridge pattern
Summary
Questions
Further reading
11
Chapter 8: Now You Know Some Patterns, What Next?
Chapter 8: Now You Know Some Patterns, What Next?
Patterns we didn’t discuss
Patterns beyond the realm of OOP
Creating your own patterns
Not everybody likes patterns
Summary
Sundance Square – Fort Worth, Texas
Further reading
12
Index
Index
Why subscribe?
13
Other Books You May Enjoy
Other Books You May Enjoy
Packt is searching for authors like you
Share Your Thoughts
Appendix 1: A Brief Review of OOP Principles in C#
Appendix 1: A Brief Review of OOP Principles in C#
Technical requirements
A quick background of C#
Language mechanics in C#
Encapsulation
Inheritance
Interfaces
IDEs for C# development
Summary
Further reading
Appendix 2: A Primer on the Unified Modeling Language (UML)
Appendix 2: A Primer on the Unified Modeling Language (UML)
Technical requirements
The structure of a class diagram
Connectors
Notes
Best practices
Summary
Further reading

Measuring quality beyond the development organization

We’ve spent a lot of time in this chapter talking about quality code from the perspective of software engineering. Software is never developed in a bubble. It is always developed in concert with business professionals working to solve business problems. That means a great many people on your project might not be developers or engineers. All of our discussions so far have revolved around specific engineering practices. However, you need to realize that these views won’t be shared by your business-oriented colleagues.

For them, quality is often defined as conformance to requirements. That means quality code is code that meets its requirements. I would argue that this is a far too basic definition. The corporate quality movements of the 80s and 90s, such as the lean manufacturing and zero defects ideals espoused by Deming, have been coopted into our field by well-meaning managers. They want to focus 100 percent on...

Previous Section
End of Section 6
Next Section