软件架构经典全书：影印版60MB PDF下载

1星需积分: 43 68 浏览量更新于2024-07-18 3 收藏 59MB PDF 举报

《软件架构：基础、理论与实践》是一本由Richard N. Taylor（加州大学欧文分校）、Nenad Medvidovic（南加州大学）和Eric M. Dashofy（航空航天公司）合著的专业书籍。该书全面探讨了软件架构这一核心概念，旨在为读者提供一个深入理解软件设计原则、模式和技术的基础。书中内容涵盖了软件体系结构的各个方面，包括其定义、分类、设计过程、原则，以及在实际项目中的应用和挑战。作为一本影印版PDF，这本书具有60MB的大容量，表明它包含了大量的图表、示例和理论阐述，使得理论学习者和实践经验者都能从中受益。作者们从基础出发，探讨了软件架构的重要性，如何通过合理的架构设计来提升系统的可维护性、可扩展性和性能。此外，书中还可能涉及软件架构的生命周期管理，如架构评估、演化和转型策略。本书适合计算机科学、软件工程、系统架构师以及任何关注软件系统整体设计的专业人士阅读。书中不仅包含了理论框架，还提供了实用的案例研究和最佳实践，使读者能够将所学应用于实际项目之中。版权方面，这本书由John Wiley & Sons, Inc. 出版，并在2010年首次发行，所有权利受到保护，禁止未经许可的复制或存储。对于那些希望深入理解软件开发的复杂性和艺术性的读者来说，《软件架构：基础、理论与实践》无疑是一本不可或缺的参考书籍。通过阅读这本书，读者可以提升对软件架构的理论认知，掌握构建高效、可扩展和适应性强的软件系统的技能。无论是初次接触软件架构的新手，还是已经在领域内有一定经验的开发者，都可以从中获得新的视角和洞察。

xvi

architecture's critical role

software engineering, yet the text does

not

attempt to be

a general software engineering reference.

There

are, for example, many important parts

of software engineering

not

treated

all, such

source~code

testing strategies, general

project management, and development environments.

THE SCOPE

THE

BOOI{

This book

characterized by breadth. Rather

than

focus

one method, notation, tool,

or process, the book attempts to widely survey software development from

architectural

perspective, putting many

these elements

context, comparing

and

contrasting

them

withoneanother. A readershould expectto gaina broadappreciationfor

the

role ofsoftware

architecture across

the

wide variety

activities

that

characterize

the

development oflarge,

software~intensive

systems.

Our

assumption

that

readers seekfundamental insights and knowledge tosupplement

their own experience,

ratherthan

canned

solutions to specific problems (those, if they do

exist,

can

most likely be found else\vhere).

The

text

therefore focuses.

overarching

principles, general strategies,

and

broadly applicable techniques.

illustrates

them

with

manyspecific examples from various domains.

The

text

does

not

advocate a single approach

and it

not

a manual or advertisement for

one-even

the authors' own.

Audiences

The

book attempts

address

the

needs ofseveral audiences.

The

instructor

audience

supported

a detailed

treatment

of a broad spectrum

software

architecture~related

topics, from which

diff~rent

subsets

can

be selected for use

in courses with specific foci.

instructor will be able

tailor

the

materia] provided

the

book

both

the

length and

the

objective

a course. To date,

the

authors have

used this text in

five

quarter~long

(ten~week)

courses and two

semester~long

(fifteen~week)

courses,

both

the undergraduate and graduate levels.

The

courses have focused

soft~

ware engineering, software architecture, software design, software interoperability, and

distributed systems. Both

semester~

long courses have used the entire text, while the

quarter~

long courses have relied

different selections

the

chapters.

The

instructor using

the

text will be able to rely

a corhprehensive set oflecture slides, solutiuns to

end~of~chapter

exercises, sample exams with solutions, ahd a tool suite

that

will be described below.

The

student audience

supported with a presentation

that

comprehensive, making

relatively

few

assumptions about background knowledge and experience. We do assume

that

the student

generally familiar

with

the

most basic elements

software engineering

and programming.

The

order

the

text

and the way the material

presented makes

the

student the primary audience of

the

book-the

other

audiences will pick

and

choose

material from various parts

the text.

The

professional

audience

supported with, for example, comprehensive treatment

the

major modelingtechniques, architectural description standards,

and

the way they are

directly tied

the

implementation

software products.

Our

perspective

not

confined to

some presumed ivory tower:

The

standards

and

notations include commercial, government,

and

research products.

The

text

also attempts to provide, in the majority

chapters, specific

guidance

how to achieve various goals, such

how to design

achieve specific system

properties. References

and

examples draw from a wide range

industrial experience.

PREFACE

Professionals should expect to

encounter

realistic

and

frank assessments

the

techniques,

no[ations,

and

tools

with

which

they

are already familiar, while also being exposed to

projects

and

approaches

that

provide valuable insights

but

are nonetheless

not

well~known

practitioners' circles.

The

systems

engineer

will find

that

this book's perspective, while still focused

soft~

ware, has implications

that

are quite a

bit

broader. Insights

this

book

will enable

better

understanding

the

unique issues involved

the

development

of large software systems.

Many of

the

insights, however, are applicable to systems

development

general. Insights,

notations,

and

methods from

the

systems engineering

and

systems architecture community

are

not

ignored,

and

this book explores overlap

between

systems

and

software engineering

throughout.

The

systems and/or software

development

manager will find substantial material here

that

addresses

the

way in

which

architecture~centric

development

can

shape

and

improve

processes

and

organizations, especially with regard to

the

development

product families.

ASSUMPTIONS

AND

BACKGROUND

Depending

the

sections

the

book

used for reference or

class,

the

necessary

back~

ground varies. As a whole, however,

the

book assumes familiarity

with

the

basics

software

development.

This

includes

the

core ideas

software

development

activities

and

pro~

cesses,

notions

requirements, design, programming,

and

analysis

and

testing.

The

level

maturity required

is,

in some sense, only

what

would

acquired

a single,

quarter~

semester~long

introduction to software development/engineering.

Appreciation

for

the

problems

large~scale

development

very useful. Proficiency

any particular

program~

ming language, development

environment,

or modeling tool

such

UML

not

required.

Additional

experience will likely make

possible for

certain

readers to develop a

deeper understanding

and

appreciation

specific topics. For example,

the

implementation

chapter

will be

most value

those

with

substantive training

and

experience

program~

mingo

Similarly, appreciating

the

discussion

deployment

product

lines demands some

level ofunderstanding of

how

commercial

development

and

product~and~revenue

focused

businesses work. However,

none

the

chapters presuppose

extensive background

the

area

which

they focus.

HOW

THE

BOOK

CAN BE USED

The

text

designed to be used as a textbook

formal classroom settings,

both

the

undergraduate

and

graduate levels.

can

also

used

a reference for systems engineers,

software architects, managers, and programmers.

Chapters

through

5 present

the

critical

concepts

software architecture.

Chapter

5 also bridges to

the

section,

the

nuts

and

bolts of applying

the

concepts,

which

encompasses

Chapters

through

10.

Chapters

through 17 treat associated issues: topics

that

may

critical

one

development context,

but

not

another.

Classroom

Usage

There

adequate material

the book for a

year~

long class

the

master's degree level.

The

presentation

does

not

presuppose

that

this

the

normative

case however.

The

authors

_---

.....

_-----_....- ...

._-_

xvii

xviii

PREFACE

have

used

materl~l

from the book in

quarter~long

and

seinester~long

courses, including,

a primary text,

undergraduate software engineering course and a graduate software

engineering course.

The

book,

its preprint form, has also

been

used

several

other

uni~

versities, including Drexel University,

Southern

Methodist University, Seattle University,

and

the

University

Zurich.

Clearly, material has to bechosenbased

upon

the

level

the

instructionand

the

length

the

class. Nonetheless, a

few

comments are

order.

The

concepts

section-Chapters

1 through

5-is

essential to use

the

book.

The

material

the subsequent chapters

depends

these core concepts. How long

will take to cover those initial chapters,

however, will vary significantly.

The

first chapter, for instance, will be a very quick read for

the

experienced. Similarly,

Chapter

2 will be relatively quick for those with experience

software engineering,

but

will take a

bit

longer

undergraduate class

that

has minimal

prerequisites.

Chapter

a long chapter,

but

it covers a single, critical topic: how to

about designing a system. This

chapter

may thus be a majorfocus over many class sessions,

especially for those with little training or experience

design.

Selection

materials from Chapters 6 through 10 will depend upon the level

the

class,

the

course objectives, and

the

length

the

class.

The

authors recommend. a shallow

treatment

all

them

over a deep look

any individual chapters,

but

this

the

instructor.

Several suggested pathways through

the

book, depending

course type

and

length,

are

follows:

• A

fifteen~week

software architecture

course-Chapters

1 through

• A

ten~week

software architecture

course-Chapters

1 through

11, 12,

and

• A

ten~week

distributed systems

course-Chapters

1 through

6,7

through 15,

and

fifteen~week

software engineering

course-Chapters

1 through

and

• A

ten~'week

software engineering

course-Chapters

1 through

11, and 12

the book

used

a primary

text

for a software engineering course, the instructor

may want to supplement

with material covering topics such

software testing,

design patterns, software engineering economics, and project management.

The

book can

also be used

a companion text

a software analysis

and

quality assurance course; the

relevant chapters would be Chapters 8, 12,

and

14.

A key issue the instructor will have

deal with

use

the exercises. Each chapter

has a number

exercises listed. Software architecture

not

a topic like algebra where

numerous simple questions

can

be posed and

the

answers given in

the

back

the

book.

Software architecture concerns itself with design, with complex systems, and with

long~

lived products.

Hence

difficult to pose exercises

that

fit nicely into

the

constraints

a modern college class. Many

the

exercises included

the

text could be assigned

mini~projects.

The

instructor will thus have

tailor

the

scope of the assignments and

provide guidance

the

students regarding

the

level

detail expected in

the

answers.

Assessing

the

answers similarly will require

thought

and discretion.

Use

Professionals

The

authors

have

tried to include substantial material to make the book a superior

rer

erence for

the

professional. A theme running through

the

entire book

software reuse

and, more generally, reuse

corporate

and

domain

knowledge. Similarly, there

explicit

PREFACE

reliance

the

presented techniques

the

use

frameworks to help achieve rapid system

implementation. A wide range

modeling

notations

discussed,

and

a complete

chapter

standards

included to provide a thoughtful basis for choosing a

notation

approach

for a project. Similarly,

the

discussion ofdesigning for

nonAunctional

properties

targeted

at providing

proven

techniques capable

addressing these difficult issues.

Chapter

designing similarly will be useful

a reference to

the

professional.

Without

being a

hand~

book

field techniques, it nevertheless presents a wide range of architectural styles

and

design techniques, with

the

styles summarized individually

and

a comparison table

aid

the

professional in choosing

the

right

technique

for

the

job

hand.

Tool

Support

Use of

the

book in

the

classroom

by professionals

practice does

not

require

the

use

of any particular tool or programming language. Clearly, however,

the

subject

designing

and building

applications-products-and

that

only happens effectively

the

presence

good tools.

The

professional may be constrained by

the

choice of

the

modeling

notation

required

a particular

development

context.

AADL,

for example,

mandated

the

architecture description language for a project,

then

the

die

cast.

For those contexts where

external

constraints do

not

dictate,

the

instructor or reader

encouraged to use technologies

that

not

only help model

architecture,

but

build

implementations based

upon

those models.

modeling alone

supported,

then

the

value

of a tool over a simple

boxes~and~arrows

drawing tool rests

upon

the

value

obtained

from

analyses

that

can

be performed

the

model. If building real products

the

goal,

then

tool suite

that

addresses

the

full range ofdevelopers' needs

required.

To this latter

end

encourage

the

book's users to use

the

ArchStudio

tool suite,

it has

been

developed for this purpose.

The

tool

can

benefit faculty, students,

and

even

professionals using this text.

The

tool

free,

integrated

with

the

Eclipse

devel~

opment

environment,

and

has

been

used

the

classroom

and

industry. A

community

of developers

and

users has formed

around

this project,

with

dozens

projects around

the

world using

and

contributing. Further details

can

be found

the

project's

Web

site:

www.isr.uci.edu/projects/archstudio/.

Chapter

Summaries

Chapter

The Big Idea

The

chapter

introduces software architecture through discussion

three primary examples

of its application: in

the

very large

(the

architecture

the

World

Wide

Web),

the

very

small

(pipe~and~filter

the

desktop),

and

the

product/in

the

many

(the

Philips/Koala

architecture for consumer electronics).

Chapter

Architectures in Context: The Reorientation

of Software Engineering

The

role

software architecture

the

major activities ofsoftware engineering

explored,

including application conception, design, implementation,

and

analysis.

architecture~

centric perspective

development

presented.

Chapter

Basic

Concepts

Definitions

the

key terms

and

concepts are presented.

The

definitions build from

the

examples

the

preceding chapters

and

form

the

foundation

for

the

subsequent chapters.

xix

Chapter

4: Designing Architectures

The

concepts

the

preceding chapters are made productive

this one. This

chap~

ter presents,

length, techniques

and

approaches for designing applications from

architecture~centric

perspective.

The

central focus

the

ways

which refined

experi~

ence may be used to guide new developments.

Chapter

5: Connectors

Connectors

playa

distinguished role in

architecture~centric

development.

They

are also,

perhaps,

the

most unfamiliar concept to those unskilled

the

art

system design. This

chapter reveals the breadth

and

depth

the

concept,

and

includes

extensive guide to

the

numerous techniques available.

Chapter

Modeling

This chaptersurveys

extensive range

modeling notations used for capturing

the

design

decisions

that

make up architecture. Notations from research

and

practice are examined,

and

the

distinctive aspects

each

notation

are called out. A consistent running example

application

used throughout

the

chapter

demonstrate each notation. -

Chapter

Visualization

This

chapter draws a distinction between how architectures are

modeled-the

syntax

and

semantics of how design decisions are

documented-from

how they are visualized.

Visualization encompasses

both

depiction-how

design decisions are

presented-and

interaction-the

"user interface" through which stakeholders interact

with

those

depic~

tions. Various visualization approaches are surveyed and compared, along with techniques

for constructing and integrating new visualizations.

Chapter

8: Analysis

One

the

primary benefits

software architecture

that

can

enable early assessment

given system, before significant resources are invested

the

system's implementation

and deployment. This chapter provides a broad overview

the

various analysis techniques

that

can

be applied

the architectural level,

their

strengths, and limitations.

Chapter

Implementation

This chapter describes

the

problem

moving from architectural design decisions to

implementation artifacts. Special

attention

paid to the use of

architecture

implementation

framewor1<s,

special~purpose

middleware

that

bridges

the

gap between architectural styles

and

existing platform services. Two complete implemented applications

alternative

frameworks are presented with commentary.

Chapter

10:

Deployment

and

Mobility

This

chapter addresses deployment and mobility, two related topics

that

have become

important in contemporary distributed, embedded,

and

pervasive systems.

The

objec~

tive

the chapter

not

to provide a complete

treatment

these two topics,

but

rather to isolate

and

focus

their characteristics from

explicit software architectural

perspective.

剩余731页未读，继续阅读

qq_35978445

粉丝: 0
资源: 5

软件架构经典全书：影印版60MB PDF下载

《Software Architecture Design Patterns in Java》原版PDF 下载

Software Architecture

Fundamentals of Computer Architecture and Design 无水印原版pdf

Software Architecture - 完整版.rar

ns-3 Software Architecture-2007

安卓毕业设计a源码网站-Software-Architecture-Patterns:软件架构模式

transactional-memory-synthesis-lectures-on-computer-architecture.pdf

01 Beyond Software Architecture.pdf

Software Architecture in Practice(软件架构实践)英文第二版(pdf完整文字版)

ISO-IEC-IEEE 42010：2011 Systems and software engineering — Architecture description（系统和软件工程—体系结构描述）- 完整英文电子版（46页）.pdf

最新资源