没有合适的资源?快使用搜索试试~ 我知道了~
首页Documenting Software Architectures 2nd
Documenting Software Architectures 2nd
5星 · 超过95%的资源 需积分: 9 110 下载量 68 浏览量
更新于2023-06-29
评论 1
收藏 5.65MB PDF 举报
The purpose of this book is to answer the following question: How do you document an architecture so that others can successfully use it, maintain it, and build a system from it?
资源详情
资源评论
资源推荐
ptg
ptg
Software
Architecture
Document
Structures Designed
into the Architecture
Meeting
Documentation
Stakeholders’ Needs
(Chapter 9)
Set of Relevant
Views
View
View Packets
(Section 10.1.2)
1. P r i m a r y P r e s e n t a t i o n
2. Element Catalog
a. Elements and Their Properties (Chapters 1–5)
b. Relations and Their Properties (Chapters 1–5)
c. Element Interfaces (Chapter 7)
d. Element Behavior (Chapter 8)
3. Context Diagram (Section 6.3)
4. Variability Guide (Section 6.4)
5. Rationale (Section 6.5)
View Template
(Section 10.1)
(see inside back
cover)
Information That
Applies to More
Than One View
(Section 10.2)
Temp la te f or
Information Beyond
Views
(Section 10.2)
(see inside back
cover)
1. D o c u m e n t a t i o n
Roadmap
2. How a View Is
Documented
3. System Overview
4. Mapping
Between Views
5. Rationale
6. Directory
is documented
using
consists ofconsists of
consists of
consists of
includes
one or
more
is chosen
to document
based on
is chosen
to document
based on
may be
divided
into
is documented
using
Key
Concept A has relationship “label” with Concept B.
A B
label
ptg
such as
chosen for
use by
architect to
achieve
View
(Prologue Section P.3)
Style
(Prologue Section P.4)
Hybrid Style
(Section 6.6)
Allocation Style
(Chapter 5)
Component-and-
Connector Style
(Chapters 3 and 4)
Module Style
(Chapters 1 and 2)
Uses Style
(Section 2.2)
Generalization
Style
(Section 2.3)
Layered Style
(Section 2.4)
Aspects Style
(Section 2.5)
Decomposition
Style
(Section 2.1)
Data Model
Style
(Section 2.6)
Multi-tier Style
(Section 4.6.2)
Shared-Data
Style
(Section 4.5.1)
Pipe-and-Filter
Style
(Section 4.2.1)
Client-Server
Style
(Section 4.3.1)
Service-Oriented
Architecture
Style
(Section 4.3.3)
Peer-to-Peer
Style
(Section 4.3.2)
Publish-
Subscribe Style
(Section 4.4.1)
Quality Attributes
combines
one or
more
when applied to a
system, yields a
may
be
may
be
may
be
may
be
Work
Assignment
Style
(Section 5.4)
Deployment
Style
(Section 5.2)
Other Allocations
Styles
(Section 5.5)
Install Style
(Section 5.3)
such assuch as
Key
Concept A has relationship “label” with Concept B.
A B
label
ptg
Praise for the First Edition of Documenting Software Architectures
“For many years, box and line diagrams have decorated the text that describes system
implementations. These diagrams can be evocative, sometimes inspirational, occasionally
informative, but are rarely precise and never complete. Recent years have brought appreci-
ation for the importance of a deliberate structural design, or architecture, for a system. Now,
in Documenting Software Architectures, we have guidance for capturing that knowledge,
both to aid design and—perhaps more significantly—to inform subsequent maintainers,
who hold over half the total cost of a system’s software in their hands. Half of this cost goes
into figuring out how the system is organized and where to make the change. A documented
architecture is the essential roadmap for the system, leading the maintainer through the
implementation jungle.”
—Mary Shaw, Alan J. Perlis Professor of Computer Science, Carnegie Mellon University
Coauthor of Software Architecture: Perspectives on an Emerging Discipline
“Multiple software architecture views are essential because of the diverse set of stakeholders
(users, acquirers, developers, testers, maintainers, inter-operators, and others) needing to
understand and use the architecture from their viewpoint. Achieving consistency among
such views is one of the most challenging and difficult problems in the software architecture
field. This book is a tremendously valuable first step in defining analyzable software architec-
ture views and frameworks for integrating them.”
—Barry Boehm, TRW Professor of Software Engineering
Director, USC Center for Software Engineering
“There is probably no better set of authors to write this book. The material is readable. It uses
humor effectively. It is nicely introspective when appropriate, and yet in the end it is forthright
and decisive. The philosophical elements of the book are fascinating. The authors consider
concepts that few others even are aware of, present the issues related to those concepts,
and then resolve them! This is a tour de force on the subject of architectural documentation.”
—Robert Glass, Editor-in-Chief, Journal of Systems and Software
Editor/Publisher, The Software Practitioner
“We found this book highly valuable for our work with our business units and would recom-
mend it to anyone who wants to understand the needs for and improve their skills in describ-
ing software architectures for complex systems.”
—Steffen Thiel, Robert Bosch Corporation
ptg
“Since our projects involve numerous stakeholders, documenting the architecture from var-
ious views is of particular importance. For this task, this book provides pragmatic and well-
structured guidance and will be an important reference for industrial practice.”
—Martin Simons, Daimler Chrysler Research and Technology
“Software architecture is an abstract representation of the most essential design decisions.
It is expressed using concepts that are not directly visible in software implementation. How
to identify these decisions? How to represent them? How to find the concepts that make
complex software understandable? This excellent book is written by a group of expert archi-
tects sharing their experience and understanding of useful architectural concepts, essential
design decisions, and practical ways to represent architectural views of complex software.”
—Alexander Ran, Principal Scientist of Software Architecture, Nokia
“I particularly appreciate the major theme of the book: that a software architecture consists
of a variety of different structures, each defined by a set of elements and a relationship
among those elements. I further appreciate the authors pointing out why the diagrams that
seem so beloved by today’s software designers are often deceptive and of little value. (I fre-
quently say that in software engineering every diagram takes a thousand words to explain
it.) It was also refreshing to see an explanation of why ‘levels of abstraction,’ a favorite term
of many software designers, is an empty phrase. These are just a few of the elements that
made me impatient to see this book published.”
—David Weiss, Director of Software Technology Research, Avaya Laboratories
“The authors have written a solid book that discusses many of the most important issues
facing software designers. They point out many decisions that can be considered, dis-
cussed, and made before coding begins to provide guidance for the programmers. These
issues are far more important than most of the decisions that programmers focus on. Prop-
erly made and documented, the decisions discussed in this book will guide programmers
throughout the remainder of the software development process.”
—David Parnas, Director of the Software Engineering Programme, McMaster University
剩余581页未读,继续阅读
ramboOne
- 粉丝: 3
- 资源: 14
上传资源 快速赚钱
- 我的内容管理 收起
- 我的资源 快来上传第一个资源
- 我的收益 登录查看自己的收益
- 我的积分 登录查看自己的积分
- 我的C币 登录后查看C币余额
- 我的收藏
- 我的下载
- 下载帮助
会员权益专享
最新资源
- zigbee-cluster-library-specification
- JSBSim Reference Manual
- c++校园超市商品信息管理系统课程设计说明书(含源代码) (2).pdf
- 建筑供配电系统相关课件.pptx
- 企业管理规章制度及管理模式.doc
- vb打开摄像头.doc
- 云计算-可信计算中认证协议改进方案.pdf
- [详细完整版]单片机编程4.ppt
- c语言常用算法.pdf
- c++经典程序代码大全.pdf
- 单片机数字时钟资料.doc
- 11项目管理前沿1.0.pptx
- 基于ssm的“魅力”繁峙宣传网站的设计与实现论文.doc
- 智慧交通综合解决方案.pptx
- 建筑防潮设计-PowerPointPresentati.pptx
- SPC统计过程控制程序.pptx
资源上传下载、课程学习等过程中有任何疑问或建议,欢迎提出宝贵意见哦~我们会及时处理!
点击此处反馈
安全验证
文档复制为VIP权益,开通VIP直接复制
信息提交成功
评论8