PofoliaShared via Pofolia

· 2017· Book chapter

Clean Architecture: A Craftsman's Guide to Software Structure and Design

Robert Martin

Short summary

Robert Martin's Clean Architecture provides universal rules for software structure, detailing critical choices and core disciplines for architects to improve developer productivity and prevent project failures.

AI-generated from the title and abstract; the full text is not read.

Key points

  • Applies universal rules of software architecture to improve developer productivity.
  • Details essential software design principles for function, component separation, and data management.
  • Explains how programming paradigms restrict developers and influence design.
  • Provides solutions for high-level structures in web, database, thick-client, console, and embedded applications.
  • Addresses common design failures and offers prevention or remediation strategies.

AI-generated from the title and abstract; the full text is not read.

Abstract

By applying universal rules of software architecture, you can dramatically improve developer productivity throughout the life of any software system. Now, building upon the success of his best-selling books Clean Code and The Clean Coder, legendary software craftsman Robert C. Martin (“Uncle Bob”) reveals those rules and helps you apply them. Martin’s Clean Architecture doesn’t merely present options. Drawing on over a half-century of experience in software environments of every imaginable type, Martin tells you what choices to make and why they are critical to your success. As you’ve come to expect from Uncle Bob, this book is packed with direct, no-nonsense solutions for the real challenges you’ll face—the ones that will make or break your projects. Learn what software architects need to achieve—and core disciplines and practices for achieving it Master essential software design principles for addressing function, component separation, and data management See how programming paradigms impose discipline by restricting what developers can do Understand what’s critically important and what’s merely a “detail” Implement optimal, high-level structures for web, database, thick-client, console, and embedded applications Define appropriate boundaries and layers, and organize components and services See why designs and architectures go wrong, and how to prevent (or fix) these failures Clean Architecture is essential reading for every current or aspiring software architect, systems analyst, system designer, and software manager—and for every programmer who must execute someone else’s designs.

The authors' abstract, as published at the source., 2017 · DOI ↗

TakeawaysPremium
Ask the paperFree account

Continue with a free account

Ask the paper: 3 free questions a day about this paper; save it, get its citation, new summaries every day for your field. Takeaways are Premium.

Continue free on the web

Sign in with Google or Apple; no card needed. You come back to this paper.

On your phone:

Field: Architecture

ArchitectureEngineering