Fundraising September 15, 2024 – October 1, 2024 About fundraising

Architecting Software Intensive Systems: A Practitioners...

Architecting Software Intensive Systems: A Practitioners Guide

Anthony J. Lattanze
How much do you like this book?
What’s the quality of the file?
Download the book for quality assessment
What’s the quality of the downloaded files?

Architectural design is a crucial first step in developing complex software intensive systems. Early design decisions establish the structures necessary for achieving broad systemic properties. However, today’s organizations lack synergy between software their development processes and technological methodologies. Providing a thorough treatment of the latest theory and best practices, Architecting Software Intensive Systems: A Practitioner’s Guide explains:

  • How and when to design architectures
  • How to weave architecture design processes into existing development processes
  • What to do with architecture design artifacts once created

The first section establishes key concepts in architectural design for software intensive systems, including architectural drivers, structures, and fundamental guidance for architectural design. The book goes on to describe the industry tested Architecture Centric Design Method. Each stage of the method is explained and the book provides all of the supporting templates and checklists. The last section discusses practical matters, including how to adopt disciplined architectural design practices into existing organizational development processes.

With the principled understanding of design provided by this book, architects can temper their visceral instinct to react and be better prepared to address a broader range of design problems regardless of business context or their domain experience.

Year:
2008
Publisher:
Auerbach Publications
Language:
english
Pages:
488
ISBN 10:
1420045695
ISBN 13:
9781420045697
File:
PDF, 10.50 MB
IPFS:
CID , CID Blake2b
english, 2008
Read Online
Conversion to is in progress
Conversion to is failed

Most frequently terms