Architecting Software Intensive Systems: A Practitioners Guide |  | Author: Anthony J. Lattanze
Publisher: Auerbach Publications
Category: Book
List Price: $83.95
Buy New: $56.66
as of 9/7/2010 10:52 CDT details
You Save: $27.29 (33%)
New (18) Used (11) from $56.66
Seller: Amazon.com
Rating:  1 reviews
Sales Rank: 1055609
Media: Hardcover
Pages: 416
Number Of Items: 1
Shipping Weight (lbs): 2.3
Dimensions (in): 10 x 7.2 x 1.3
ISBN: 1420045695
Dewey Decimal Number: 005.12
EAN: 9781420045697
ASIN: 1420045695
Publication Date: November 18, 2008
Shipping: Eligible for FREE Super Saver Shipping
Availability: Usually ships in 24 hours
| |
| Similar Items:
| |
| Editorial Reviews:
Product Description
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.
|
| Customer Reviews:
the soft skills needed to succeed as a software architect January 13, 2009
T. Anderson (PA USA)
8 out of 8 found this review helpful
This book does an excellent job of introducing the reader to the soft skills needed to succeed as a software architect.
The book starts by covering the architectural lifecycle. It discusses chaos, dissemination, adaptation, harvest, and sunset. It also discusses external influences that affect the lifecycle such as stakeholders, business models, marketplace, technological environment, and organizational structure.
The book continues on by putting software architecture into context. It shows how it's related to enterprise architecture, system architecture, and detailed software design and the constraints that they place on each other.
The author covers how to interact with stakeholders and manage the architectural drivers that each group of stakeholders places on the architecture. It covers high-level functionality, quality attribute requirements, technical constraints, and business constraints.
This section also covers architectural structures which include structure and perspective, structures and systematic properties, styles and patterns of reasoning framework tactics and quality attributes. The work of an architect is covered in this section and documenting the architectural design which covers UML, technical writing guidance, and document structures.
Section 2 covers the Architectural Centric Design Method (ACDM). The author goes into great detail covering all eight stages. They include Discovering the Architectural Drivers, Establishing Project Scope, Create/Refine the Architecture, Evaluate the Architecture Design, The Go/No -- Go Decision, Experimentation, Production Planning, and Production.
The last section covers transitioning design practices, processes, and methods as well as other design considerations including legacy, designed by selection, and maintenance. The author then covers using the ACDM with software development frameworks which include Waterfall, Extreme Programming, SCRUM, Team Software Process, and RUP and CMMI.
I highly recommend this book to anyone considering getting into software architecture. The book is for architecting software intensive systems but many of the practices found in the book can be applied to building applications. An example of what I mean by applications is Web applications, RIAs, or thick client applications that are not delivered as bundled software releases or any system that is not hardware intensive.
The author does a great job pulling in industry-standard processes that are already in place for example SEI's ATAM and how to apply tactics to quality attributes. This is one of the best architecture books that cover the soft skills necessary to achieve success.
|
|
|
