Skip to content
ISBN: 0646458418
ISBN13: 9780646458410

A Software Architecture Primer

ISBN: 0646458418
ISBN13: 9780646458410
Formats

Conditions

Formats

Conditions

See all 1 editions

Book Overview

A Software Architecture Primer presents a fresh, pragmatic approach to the study of software architecture. Written by two practitioners with extensive industry and academic experience, it contains a series of chapters that introduce and develop an understanding of software architecture, by means of careful explanation and elaboration of a range of key concepts. Chapters on architectural analysis and design, on fundamental views of complex software systems, and on architectural styles and quality attributes, combine to ensure that the reader or student will master the art of "architectural thinking." This book will be of value to anyone involved in software systems analysis, design, or development. A complete set of course materials is available to support the use of this book as an undergraduate or post-graduate textbook. This description may be from another edition of this product.
Format:
Paperback
Language:
English
ISBN:
0646458418
ISBN13:
9780646458410
Release Date:
March 2006
Publisher:
Angophora Press
Length:
192 Pages
Weight:
5.05 lbs.
Dimensions:
0.4″ × 7.5″ × 9.3″
ComputersComputers & TechnologyEducationEducation & ReferenceLanguages & ToolsProgrammingSchools & TeachingSoftware Design, Testing & EngineeringSoftware Development

Customer Reviews

1 customer rating | 1 review
Write a Review

Masterpiece of simplicity

A Software Architecture Primer beautifully describes a small set of light-weight practices that can streamline and systematize your software design process without bogging you down in a beureaucratic process. Usually when I think of software engineering process, I think of a set of burdensome tasks that drag me down and make it more difficult to explore or change my design. Each design change can result in hours or days updating countless documents, recommunicating those changes in reviews, and so on. At the same time, it is usefult to have a structure for fleshing out a software design and communicating it to your team. In contrast to most other authors I've read in this space, Reekie and McAdam realize that there is a tension between process (structure) and getting real work done. So rather than going on and on about the minutiae of different software design formalisms and whatnot, they clearly and succinctly describe a set of techniques and exercises that will help you systematically design better software and communicate your design to others without slowing you down. This is the first software architecture book that I will actually put to practice in my next software project, rather than picking and choosing from the huge body of literature in this space.

0