Software Design Principles
Minimum price
Suggested price

Software Design Principles

A Practical Guide

About the Book

Software design principles are guidelines that help developers to make an object-oriented system design resilient to future changes.

Our original design degrades whenever we introduce new change requirements, and this degradation is because of different factors, for example:

• Poor understanding of object-oriented concepts,

• Mismanagement with the introduction of new dependencies,

• High dependency on volatile documents like SRS - Software Requirements Specification - instead of good comments in the code.

Software design principles provide guidelines to handle the complexity of the design process and prepare our code when changes arise and minimize the impact of introducing bugs.

Following these guidelines make our code more readable and easier to maintain.

  • This book aims to make you a better software designer within the object-oriented paradigm.

Connect with Me:


  • Share this book

  • Categories

    • Software Engineering
    • Computers and Programming
    • Software Architecture
    • Software
  • Feedback

    Email the Author(s)

About the Author

Moises Gamio
Moises Gamio

Moises Gamio has been working for 20 years as a Software Engineer for several companies from different economic sectors such as Government, Financial, Industrial, Educative, Consulting, Retail, and Research. He has been using several technological tools such as Java, C, Cobol, C#, Visual Basic, PHP, and JScript, in operating systems such as Windows, Linux, Unix, and RISC 6000, in databases such as SQL Server, Oracle, MySQL, DB2, and Lotus Notes. His tasks are related to Software Development, Stages of Analysis, Design, Testing, and Deployment.

For eight years, he worked as a System Analyst for the Bank Sector. Since 2015 he is working as a Software Engineer in a B2B company in Berlin, Germany.

At the moment, he is passionate about the following things:

  • Clean Code
  • Automated testing
  • Software Design
  • Software Architecture
  • Data Structure and Algorithms
  • Web Services
  • Spring Framework
  • Distributed Systems
  • Learning new technologies

Connect with Me:



Table of Contents

PREFACE Object-Oriented Programming Concepts Class Object State Behavior Constructors Abstraction Encapsulation and Data Hiding Interface Implementations Inheritance Polymorphism Overloading Overriding Relationships among Classes Association Aggregation Composition Creating and Reusing classes Loose coupling High cohesion Advantages of object-oriented programming UML Diagrams for developers Why do we model? UML Class Notation Relationships among classes Association Aggregation Composition Dependency Inheritance (or Generalization) Realization The implemented code reflects the intent of the UML designer Why do we model with UML? Coding Practices Clean code has Intention-Revealing names Clean Code tells a story Functions should do one thing Don’t comment on bad code; rewrite it Comment on what is necessary SOLID PRINCIPLES Single Responsibility Principle (SRP) The Problem: A Class has more than one responsibility The solution: Create Classes with only one responsibility Open-closed Principle (OCP) When we cannot visualize future requirements When suddenly, an unexpected scenario arises Enabling the Open-Closed Principle Liskov Substitution Principle (LSP) Describe an Object with the minimal behavior required When the minimal behavior required is broken Interface Segregation Principle (ISP) When a Class includes no-related functionalities Enabling the Interface Segregation Principle Dependency Inversion Principle (DIP) Changes made to dependent code are always risky. Dependency Inversion removes tight dependency between classes Apache Log4j Vulnerability When Clients target to an interface B2B Integration Project Duplicated effort The requirement Your creative process in action Know what you are trying to achieve The company policies influence your design Read and understand the requirements documentation. Divide and Conquer DRY (Don’t Repeat Yourself) Communicating software design decisions Visualizing software architecture Context diagram Container diagram Component diagram Code diagram How the new design handle complexity better

The Leanpub 60-day 100% Happiness Guarantee

Within 60 days of purchase you can get a 100% refund on any Leanpub purchase, in two clicks.

See full terms

80% Royalties. Earn $16 on a $20 book.

We pay 80% royalties. That's not a typo: you earn $16 on a $20 sale. If we sell 5000 non-refunded copies of your book or course for $20, you'll earn $80,000.

(Yes, some authors have already earned much more than that on Leanpub.)

In fact, authors have earnedover $12 millionwriting, publishing and selling on Leanpub.

Learn more about writing on Leanpub

Free Updates. DRM Free.

If you buy a Leanpub book, you get free updates for as long as the author updates the book! Many authors use Leanpub to publish their books in-progress, while they are writing them. All readers get free updates, regardless of when they bought the book or how much they paid (including free).

Most Leanpub books are available in PDF (for computers) and EPUB (for phones, tablets and Kindle). The formats that a book includes are shown at the top right corner of this page.

Finally, Leanpub books don't have any DRM copy-protection nonsense, so you can easily read them on any supported device.

Learn more about Leanpub's ebook formats and where to read them

Write and Publish on Leanpub

You can use Leanpub to easily write, publish and sell in-progress and completed ebooks and online courses!

Leanpub is a powerful platform for serious authors, combining a simple, elegant writing and publishing workflow with a store focused on selling in-progress ebooks.

Leanpub is a magical typewriter for authors: just write in plain text, and to publish your ebook, just click a button. (Or, if you are producing your ebook your own way, you can even upload your own PDF and/or EPUB files and then publish with one click!) It really is that easy.

Learn more about writing on Leanpub