UML引导的大型软件架构实践指南

需积分: 35 65 浏览量更新于2024-07-19 收藏 4.57MB PDF 举报

《大型软件架构：使用UML的实践指南》是一本由Jeff Garland和Richard Anthony合著的专业书籍，两位作者均来自业界知名公司——Crystal Clear Software Inc. 和 Object Computing Inc.。本书的核心主题是将软件架构作为开发过程中的关键工具，而非仅仅在设计决策完成后再记录架构细节。它旨在提供一种实用的方法，帮助读者理解和应用大型软件架构，特别强调了统一建模语言（UML）在该领域的应用。书中首先对UML在大型系统架构中的应用给出了简洁明了的描述，让读者能够快速掌握如何通过UML图形化表示法来设计、理解和管理复杂的软件系统。UML是一种广泛使用的标准化建模语言，它支持多种视图，如用例视图、类图、组件图、部署图等，这些视图有助于沟通设计思想，确保团队间的协作一致。接下来，作者深入讨论了软件架构和设计原则，包括但不限于模块化、松耦合、开闭原则、单一职责原则等，这些都是构建健壮、可维护和可扩展系统的基础。书中的内容强调了架构设计的重要性，它不仅仅关注实现细节，而是着眼于系统的整体结构和行为，以便于在整个项目生命周期中进行有效的调整和优化。此外，由于书中强调技术与供应商的独立性，读者可以放心，所学到的原则和技术不会受限于特定的技术栈或供应商解决方案，使得知识更具有普适性和持久价值。作者们分享的经验和最佳实践，使读者能够在各种环境下灵活运用这些架构策略。版权信息部分提到了这本书的出版商John Wiley & Sons Ltd.，以及购买和客户服务的相关联系方式。同时，关于版权的声明强调了未经许可不得复制、存储或传输文本内容，除非符合版权法的规定或者获得版权所有者的书面许可。总结来说，《大型软件架构：使用UML的实践指南》是一本实用的指南，适合软件开发者、架构师、项目经理和团队领导者阅读，它提供了在设计和管理大规模软件项目时，如何利用UML来指导系统设计和决策的重要知识和技巧。通过学习本书，读者将能更好地理解和构建出结构清晰、可维护且适应不断变化需求的大型软件系统。

dealing with the complexity of large-scale projects. However, there is still

little agreement about how to develop and describe software architecture

effectively. The agreement usually ends with the use of UML for design,

although this is not universal either. The UML provides a huge set of

constructs for describing the software architecture, and includes many

extensibility features. However, this ﬂexibility creates a large number of

possibilities for software architecture representation. In addition, most of the

books and articles on software architecture and UML do not address large-

scale development. The literature typically doesn’t provide guidelines on how

to get started in the deﬁnition of the software architecture, and doesn’t

provide speciﬁc representations which convey appropriate information to the

stakeholders in a software architecture. This book is an attempt to meet

these needs, which are critical to the software architect and the software

development team.

Some areas where this book will provide practical guidance include:

• Modeling of architectural constructs, including components, subsystems,

dependencies, transactions, and interfaces

• Modeling of environmental elements, including processes, nodes, and

physical databases

• Insight into useful techniques for development of software architectures

• Various software architecture development processes

• Roles and responsibilities of the software architect and the architecture

team

• Traps and pitfalls of architecture development

• Utilization of reusable and off-the-shelf software frameworks and compo-

nents

• Addressing non-functional requirements such as performance and main-

tainability

This book does not purport to describe the best or only way to represent

software architecture. Some systems may require additional representations

from the ones shown in this book, and others may require only a subset of

those shown here. However, most software development projects could beneﬁt

from at least some of the techniques and architecture representations de-

scribed here.

Preface xiii

In this book, we stick closely to the UML without major extensions. In

some cases, this results in some limitations in formality or model semantics.

Regardless of these limitations, these viewpoints have helped us solve complex

problems in large systems. Note that over the course of several projects, the

views described within were upgraded to utilize the UML. In many cases, we

were using ad-hoc notations before the UML had reached its current state. In

addition, future changes to the UML and the associated proﬁles may allow for

improvements of the architecture views described in the book. Any that we

are aware of are highlighted. Finally, although the focus is on modeling

architecture with the UML, we discuss other representations where appro-

priate.

While a major portion of the book focuses on the application of the UML

to software architecture, we also discuss the role of the software architect and

how architecture development ﬁts within the software development process.

We have applied the architectural viewpoints described within on several

projects across different organizations and within different development

processes. Large projects tend to utilize relatively formal processes for which

the described viewpoints ﬁt nicely. However, we have also used these view-

points and techniques on projects using highly iterative and agile processes.

We believe that architecture-based development does not need to imply heavy-

weight processes.

The intended audience for this book includes those practitioners who are

currently in the role of software architect, those who are currently software

developers or designers and who will soon be in this role, and developers

working on large-scale software development who want to better understand

successful techniques for software architecture. We have assumed the reader

has a working knowledge of the UML and at least a few years experience as a

software developer or designer. Experience in the role of software architect or

on a software architecture team would allow the reader to gain even more

from reading this book.

This book is organized to provide general information and overview in the

ﬁrst chapters and discussion of speciﬁc architectural viewpoints in the later

chapters. Chapter 1 provides our view of what ‘software architecture’ means.

Chapters 2–3 discuss roles and process related to architecture. Chapter 4

gives an overview of a banking system example we use to illustrate the various

viewpoints in the later chapters. Chapter 5 summarizes the UML diagrams

and the viewpoints described in later chapters. Chapters 6–10 discuss and

describe the various viewpoints of software architecture. Chapter 11 describes

architecture development techniques and principles.

At the end of each chapter is a recommended reading list of key books and

xiv Preface

papers. These references contain additional information on the topics covered

in that chapter. Many of the books, papers, and Web page references in the

recommended readings provide detail in areas where we only touch lightly.

This list is intended to contain the information we have found most useful.

The books and papers are summarized in the Bibliography. URLs can be

found at the book’s web site.

Chapter 1 introduces the deﬁnition of software architecture and other

terms. In addition, the UML-based architecture viewpoints are introduced

and compared with other contemporary architecture methods.

Chapter 2 describes the role of the software architect. This includes topics

such as the skills and background required to be an effective software

architect, the ways an organization can support the architect, and the organi-

zation and structure of the software architecture team.

Chapter 3 discusses how software architecture relates to the overall soft-

ware development process and describes processes for the development of

software architecture. Topics include the creation of an effective review

process, development of software infrastructure, technology roadmap man-

agement, process traps and pitfalls, and a brief discussion on tools.

Chapter 4 gives an overview of the banking system example that will be

used to illustrate the architectural viewpoints described in the remainder of

the book.

Chapter 5 provides a quick overview of the UML diagrams and concepts

used in later chapters to build architectural viewpoints.

Chapter 6 provides an overview of representations and techniques for

deﬁning system context and performing domain analysis. Included is a discus-

sion of conceptual diagrams, context views, and views used for domain

analysis.

Chapter 7 explains architecture representations to facilitate component

development. This includes the Component View, Component Interaction

View, and Component State Views. Component messaging and interfaces are

also discussed.

Chapter 8 discusses subsystem and layer representations. These views

include the Layered Subsystem View and the Subsystem Interface Dependency

View. These views serve as some of the fundamental diagrams utilized for

software architecture.

Chapter 9 describes transaction and logical data modeling. This includes a

discussion of mapping designs to relational databases.

Chapter 10 discusses representations for the modeling of physical system

constructs, including nodes, databases, and process. These include Physical

Data Views, Process Views, and Deployment Views.

Preface xv

剩余280页未读，继续阅读

啊哈_天问

粉丝: 7
资源: 55

UML引导的大型软件架构实践指南

Large-Scale Software Architecture A Practical Guide using UML

John Wiley & Sons - Large-Scale Software Architecture A Practical Guide using UML

分别详细介绍以下的GCC编译选项的功能原理，每条不少于50字： --param large-function-insns=2800 --param large-stack-frame=208 --param large-function-growth=60 --param prefetch-min-insn-to-mem-ratio=0

<text class="iconfont icon-dianzan-copy icon-large" :class="{ 'active-icon': isClicked }" @click="isClicked = !isClicked"></text>点击图标没反应ying css为 .icon-large{ font-size:36rpx; .active-icon { color: red; } }

InternImage: Exploring Large-Scale Vision Foundation Models with Deformable Convolutions

albert预训练模型下载地址

.index-title { width: 82%; height: 6.5%; background-image: url(“@/assets/large-screen/index-img/标题.svg”); 怎么实现边框是倒着的等腰梯形 边框颜色为蓝色

最新资源

.index-title { width: 82%; height: 6.5%; background-image: url(“@/assets/large-screen/index-img/标题.svg”); 怎么实现边框是倒着的等腰梯形边框颜色为蓝色