Software Architecture for Developers

Купить бумажную книгу и читать

Купить бумажную книгу

По кнопке выше можно купить бумажные варианты этой книги и похожих книг на сайте интернет-магазина "Лабиринт".

Using the button above you can buy paper versions of this book and similar books on the website of the "Labyrinth" online store.

Реклама. ООО "ЛАБИРИНТ.РУ", ИНН: 7728644571, erid: LatgCADz8.

Название: Software Architecture for Developers

Автор: Simon Brown

Издательство: Lean Publishing

Год: 2015

Страниц: 275

Язык: English

Формат: pdf

Размер: 13,6 Mb

The agile and software craftsmanship movements are helping to push up the quality of the software systems that we build, which is excellent. Together they are helping us to write better software that better meets the needs of the business while carefully managing time and budgetary constraints. But there's still more we can do because even a small amount of software architecture can help prevent many of the problems that projects face. Successful software projects aren't just about good code and sometimes you need to step away from the IDE for a few moments to see the bigger picture.

This book is about that bigger picture and its role in delivering better software. It's a collection of essays that together form a practical and pragmatic guide to software architecture, with the overall goal being to demystify what it means to be a software architect and provide guidance on how to do software architecture effectively.

The book is aimed at software developers that want to learn more about software architecture as well as those that are new to the role. It fills the gap between software development and high-level architecture that probably seems a little "enterprisey" for most developers.

About the Book

This book is a practical and pragmatic guide to lightweight software architecture for developers. You'll learn:

The essence of software architecture.

Why the software architecture role should include coding, coaching and collaboration.

The things that you *really* need to think about before coding.

How to visualise your software architecture using simple sketches.

A lightweight approach to documenting your software.

Why there is *no* conflict between agile and architecture.

What "just enough" up front design means.

How to identify risks with risk-storming.

Дата создания страницы: