Architecting Software Intensive Systems: A Practitioners Guide

Anthony J. Lattanze

November 18, 2008 by Auerbach Publications
Reference - 416 Pages - 416 B/W Illustrations
ISBN 9781420045697 - CAT# AU4569

USD$102.95

Add to Wish List
FREE Standard Shipping!

Features

  • Demonstrates how to design and evaluate software architectures
  • Explains how to integrate the architecture design process into existing organizational processes
  • Shows how software architecture design can be used to schedule estimates, establish development plans, and track projects
  • Addresses the general iterative model, the waterfall model, rational unified process, team software process, and more
  • Provides mapping to process areas in the capability maturity model integrated
  • Summary

    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.