Software Architecture in PracticeAddison-Wesley, 1998 - 452 lappuses This book introduces the concepts and practices of software architecture-what a software system is designed to do and how that systems components are meant to interact with each other. An architecture is an abstract view distinct from the details of implementation, algorithm, and data representation. Architecture is, increasingly, a crucial part of a software organizations business strategy because it is a reusable asset that can be reapplied to subsequent systems. Reuse leads to the architecture business cycle, allowing an organization to leverage the effort invested in an architecture to enter whole new business areas. Drawing on their extensive experience building and evaluating architectures, the authors cover the essential technical topics for specifying and validating a system. For the first time in a book, they also emphasize the importance of the business context in which large systems are designed. Their aim is to present software architecture in a real-world setting, reflecting both the constraints and the opportunities that companies encounter. To that end, key points of both technical and organizational discussions are illuustrated by a selection of industrial-str |
Saturs
What Is Software Architecture? | 21 |
A Case Study in Utilizing Architectural | 45 |
PART TWO CREATING AND ANALYZING | 73 |
Autortiesības | |
14 citas sadaļas nav parādītas.
Citi izdevumi - Skatīt visu
Software Architecture in Practice Len Bass,Paul Clements,Rick Kazman Ierobežota priekšskatīšana - 2021 |
Software Architecture in Practice Len Bass,Paul Clements,Rick Kazman Priekšskatījums nav pieejams - 2021 |
Bieži izmantoti vārdi un frāzes
ability abstract achieve affect allows analysis application approach architect architectural styles areas behavior building called Chapter clients communication complete components concepts concerns connections cost created decisions defined described discuss documentation domain engineering environment evaluation event example execution existing Figure functionality goals implementation important influences input integration interaction interface issues kinds language layer maintain means method modifiability module object operations organization particular patterns performance possible present problem procedure processors product line quality attributes questions reference represent requirements resource responsible reuse runtime scenarios separate server shared shows simulation software architecture solution specific standards structure style Table technical techniques tion types understand unit
Atsauces uz šo grāmatu
Design and Use of Software Architectures: Adopting and Evolving a Product ... Jan Bosch Priekšskatījums nav pieejams - 2000 |
Agile Modeling: Effective Practices for eXtreme Programming and the Unified ... Scott Ambler Priekšskatījums nav pieejams - 2002 |