![](https://padhegaindia.in/wp-content/themes/woodmart/images/lazy.png)
Save: 60%
![](https://padhegaindia.in/wp-content/themes/woodmart/images/lazy.png)
Save: 60%
Software Architecture in practice (3rd ED)
Publisher:
| Author:
| Language:
| Format:
Publisher:
Author:
Language:
Format:
₹659 ₹264
Save: 60%
In stock
Ships within:
In stock
☆ ☆ ☆ ☆
Book Type | |
---|---|
Signs of Wear | |
Weak Binding | |
Pages |
Pages are mostly clean with minor marks |
Pen/Pencil Marks |
Pen and pencil used minimally |
ISBN:
Page Extent:
The award-winning and highly influential Software Architecture in Practice, Third Edition, has been substantially revised to reflect the latest developments in the field. In a real-world setting, the book once again introduces the concepts and best practices of software architecture―how a software system is structured and how that system’s elements are meant to interact. Distinct from the details of implementation, algorithm, and data representation, an architecture holds the key to achieving system quality, is a reusable asset that can be applied to subsequent systems, and is crucial to a software organization’s business strategy.
The authors have structured this edition around the concept of architecture influence cycles. Each cycle shows how architecture influences, and is influenced by, a particular context in which architecture plays a critical role. Contexts include technical environment, the life cycle of a project, an organization’s business profile, and the architect’s professional practices. The authors also have greatly expanded their treatment of quality attributes, which remain central to their architecture philosophy―with an entire chapter devoted to each attribute―and broadened their treatment of architectural patterns.
If you design, develop, or manage large software systems (or plan to do so), you will find this book to be a valuable resource for getting up to speed on the state of the art.
Totally new material covers
- Contexts of software architecture: technical, project, business, and professional
- Architecture competence: what this means both for individuals and organizations
- The origins of business goals and how this affects architecture
- Architecturally significant requirements, and how to determine them
- Architecture in the life cycle, including generate-and-test as a design philosophy; architecture conformance during implementation; architecture and testing; and architecture and agile development
- Architecture and current technologies, such as the cloud, social networks, and end-user devices
The award-winning and highly influential Software Architecture in Practice, Third Edition, has been substantially revised to reflect the latest developments in the field. In a real-world setting, the book once again introduces the concepts and best practices of software architecture―how a software system is structured and how that system’s elements are meant to interact. Distinct from the details of implementation, algorithm, and data representation, an architecture holds the key to achieving system quality, is a reusable asset that can be applied to subsequent systems, and is crucial to a software organization’s business strategy.
The authors have structured this edition around the concept of architecture influence cycles. Each cycle shows how architecture influences, and is influenced by, a particular context in which architecture plays a critical role. Contexts include technical environment, the life cycle of a project, an organization’s business profile, and the architect’s professional practices. The authors also have greatly expanded their treatment of quality attributes, which remain central to their architecture philosophy―with an entire chapter devoted to each attribute―and broadened their treatment of architectural patterns.
If you design, develop, or manage large software systems (or plan to do so), you will find this book to be a valuable resource for getting up to speed on the state of the art.
Totally new material covers
- Contexts of software architecture: technical, project, business, and professional
- Architecture competence: what this means both for individuals and organizations
- The origins of business goals and how this affects architecture
- Architecturally significant requirements, and how to determine them
- Architecture in the life cycle, including generate-and-test as a design philosophy; architecture conformance during implementation; architecture and testing; and architecture and agile development
- Architecture and current technologies, such as the cloud, social networks, and end-user devices
About Author
Paul Clements is the Vice President of Customer Success at BigLever Software, Inc., where he works to spread the adoption of systems and software product line engineering. Prior to this position, he was Senior Member of the Technical Staff at the SEI, where, for 17 years, he lead or co-lead projects in software product line engineering and software architecture documentation and analysis. Other books Paul has coauthored include Documenting Software Architectures: Views and Beyond, Second Edition (Addison-Wesley, 2011) and Evaluating Software Architectures: Methods and Case Studies, (Addison-Wesley, 2002), and Software Product Lines: Practices and Patterns (Addison-Wesley, 2002). In addition, he has also published dozens of papers in software engineering reflecting his long-standing interest in the design and specification of challenging software systems. Paul was a founding member of the IFIP WG2.10 Working Group on Software Architecture.
Rick Kazman is a Professor at the University of Hawaii and a Visiting Scientist (and former Senior Member of the Technical Staff) at the SEI. He is a coauthor of Evaluating Software Architectures: Methods and Case Studies, (Addison-Wesley, 2002). Rick’s primary research interests are software architecture, design and analysis tools, software visualization, and software engineering economics. He is also interested in human-computer interaction and information retrieval. Rick was one of the creators of several highly influential methods and tools for architecture analysis, including the SAAM (Software Architecture Analysis Method), the ATAM (Architecture Tradeoff Analysis Method), the CBAM (Cost-Benefit Analysis Method), and the Dali architecture reverse engineering tool.
Reviews
There are no reviews yet.
Related products
Distributed Operating Systems Concept And Design (2004)
Save: 60%
Software Engineering A Practitioner’s Approach (7th Ed)
Save: 60%
Digital Communication Fundamentals And Applications (2nd Ed)
Save: 60%
RELATED PRODUCTS
Cryptography and Network Security (2nd Impression 2006)
Save: 60%
Digital Communication Fundamentals And Applications (2nd Ed)
Save: 60%
Distributed Operating Systems Concept And Design (2004)
Save: 60%
Oracle Database 11G The Complete Reference (India Edition 13th 2014)
Save: 50%
Software Engineering A Practitioner’s Approach (7th Ed)
Save: 60%
Reviews
There are no reviews yet.