图书介绍

对象软件项目求生法则PDF|Epub|txt|kindle电子书版本网盘下载

（美）考克伯恩（Cockburn，A.）编著著
出版社：北京：科学出版社
ISBN：7030124898
出版时间：2004
标注页数：250页
文件大小：15MB
文件页数：274页
主题词：面向对象语言－软件开发－英文

PDF下载

点此进入-本书在线PDF格式电子书下载【推荐-云解压-方便快捷】直接下载PDF格式图书。移动端-PC端通用
种子下载[BT下载速度快]温馨提示：（请使用BT下载软件FDM进行下载）软件下载地址页直链下载[便捷但速度慢] [在线试读本书] [在线获取解压码]

点击复制MD5值：26a28d110d4b836ea03abec2f89ca71d

下载说明

对象软件项目求生法则PDF格式电子书版下载

下载的文件为RAR压缩包。需要使用解压软件进行解压得到PDF格式图书。

点击复制85GB完整离线版磁力链接到迅雷FDM等BT下载工具进行下载详情点击-查看共享计划

建议使用BT下载工具Free Download Manager进行下载,简称FDM(免费,没有广告,支持多平台）。本站资源全部打包为BT种子。所以需要使用专业的BT下载软件进行下载。如BitComet qBittorrent uTorrent等BT下载工具。迅雷目前由于本站不是热门资源。不推荐使用！后期资源热门了。安装了迅雷也可以迅雷进行下载！

（文件页数要大于标注页数，上中下等多册电子书除外）

注意：本站所有压缩包均有解压码： 点击下载压缩包解压工具

图书目录

Chapter 1 Success and Failure1

Basic Concepts4

Object Technology4

Class5

Object5

Inheritance6

Encapsulation7

Polymorphism9

Framework9

Incremental and Iterative Development10

Project Histories11

Chapter 2 Project Expectations11

ContentsForeword11

Alfred:Success with Changing Requirements12

Preface13

Brooklyn Union Gas:Success Through Attentiveness13

Ingrid:Success in Migrating to C++14

Manfred:Failure in Prototyping15

Mentor Graphics:Trouble Migrating to C++16

Acknowledgments17

Object Technology International:Success in Productivity and Speed17

Reginald: Failure with Changing Rules18

Stanley: Too Much Cutting Edge18

Tracy: Failure Through Naiveté19

Udall: Success by Restarting Smaller20

Winifred: Inattentive But Persistent21

Responsiveness to Variations on a Theme23

Responsiveness to Change23

Possible Benefits of Object Technology23

Time-to-Market24

Communication Between Developers, Users, and Executives24

Maintainability24

Reuse25

Productivity25

Window-Based User Interfaces26

Morale26

Automated Code Generation27

Software Process27

OO Desing,Encapsulation,and System Evolutlon(Tom Morgan)28

Costs28

Are You Underestimating?28

Time to Get New Developers Productive28

Establishing a Software Process29

Business Modeling versus Software Design29

Immaturity of the OO Industry29

The Difficulty of Reuse29

Hazards of C++29

The Cost of CASE Modeling Tools30

Probable Costs30

Nonobject Issues Checklists31

Chapter 3 Selecting and Setting Up an OO Project33

Project Suitability34

Variations on a Theme34

Simplified Program Structure35

Memory Management Features35

What Is Not Suited?36

Project Purpose36

Investigative37

SWAT37

Production40

Full-Commit41

Other Project Categories41

People42

Executive Sponsor42

Project Manager43

Technical Lead44

Technical Staff44

Users45

Personality Types46

Technology47

The Selection Process47

The Team Knows a Similar Technology48

One Person ls Persuasive or Stubborn48

The Technology ls Safe, Popular, or Standard49

The Technology Is the Rational Choice50

Programming Languages51

Managing Smalltalk52

Managing C++53

Disciplined Use of C++ (Jeremy Raw)58

Managing OO COBOL59

Managing Java60

Tools61

Upper-CASE Tools61

Using Java (Sam Griffith)62

The Scanner Challenge65

Minimum CASE Tool Requirements65

The Cutting Edge66

Training and Getting Advice67

What to Teach68

Developers do not know how to think in objects.68

Developers do not know how to make design trade-offs.69

Developers program poorly or use tools badly.69

Different programmers write differently, making the code hard to learn.69

Developers create redundant classes because they do not know whatis in the class library.70

No one knows how to document a framework well.70

Developers do not understand their role on the project and who depends on them.71

When to Teach71

Getting Advice72

Legacy Issues72

Mainframes72

Relational Databases73

Project Setup (C.D.)74

Review75

Chapter 4 Getting Started77

Methodology77

Big-M Methodology78

A Base Methodology to Tailor81

Discussion of the Methodology82

Roles, Skills, TechniquesTools87

Teams88

Ownership89

Deliverables89

Standards91

Activities92

Building Consumer Understanding of the Design (Ward Cunningham)94

Estimates95

Domain Classes96

Screen Classes96

Two Weeks per Noncommercial Class96

Utility Classes97

Frameworks97

Plans98

An Estimation and Planning Session (Alistair Cockburn)100

Milestones100

Measurements102

Take the Time to Design104

Design, and Two Smalltalk Projects (K.L)106

Chapter 5 Making Corrections109

A Study Project109

Stage 0: The Usual Ignorance109

Stage 2: Rebuild110

Stage 1: Disaster110

Stage 3: Improve111

Stage 4: Functioning111

Stage 5: Overconfidence in Scaling Up111

Lessons From This Study Project112

Managing Precision, Accuracy, and Scale112

Managing Work According to Precision and Accuracy115

Increments and Iterations117

Increments and V-W Staging118

Iterations123

Combining Increments and Iterations126

Burn some Pancakes(Luke Hohmann)128

Project Increments129

Increment 1129

The Architecture Team129

The Intentions130

The Training Team130

Two Stories131

Increment 2132

Pause and Learn132

Move On133

Increment N134

User Involvement134

Watching Users(K.L)136

Project Teams136

Ownership137

Involve the Users (Jon Marshall)138

Total-Ownership Teams138

Matrixed Teams138

The Domain Model140

Hazardous Situations140

Domain Modeling and Reuse140

The Common Domain Model141

Why Are There Multiple Valid Domain Models?143

PolyBloodyHardReuse146

Conflicting Reward Systems148

Lack of Trust149

I Can Write It Faster Myself149