|
|
【文件名】:07827@52RD_Symbian for Software Leaders - Principles of Successful Smartphone Development Projects - Wiley(2005).pdf
【格 式】:pdf
【大 小】:3115K
【简 介】:
【目 录】:
Principles of Successful Smartphone
Development Projects
To software leaders in the smartphone revolution
– the creators of outstanding products which will
yield high value to hundreds of millions of
mobile users[/COLOR]
Contents
Introduction: projects, projects, projects 1
Part 1 Symbian in context 3
1 At the heart of the smartphone revolution 5
1.1 The phenomenon of smartphones 5
1.2 Taking advantage of the smartphone opportunity 7
1.3 The role of the smartphone operating system 9
1.4 Regarding APIs and operating systems 11
1.5 Why Symbian OS? 13
1.6 Aside: from organizers to smartphones 16
1.7 Coming to terms with Symbian OS 17
2 The big picture of a Symbian OS project 19
2.1 High-level components of a smartphone 19
2.2 Providers of integrated solutions 20
2.3 The commercial model of a smartphone project 21
2.4 Some conclusions from the smartphone commercial
model 26
2.5 Typical smartphone project timescales 27
2.6 Warning regarding timescales 29
2.7 Factors influencing project timescales 30
2.8 The big picture: beyond timescales 31
3 Involving ISVs 33
3.1 ISV smartphone opportunity and risk 33
3.2 Beyond technical skill-sets 35
3.3 Different routes to market 36
3.4 Symbian endorsements 38
viii CONTENTS
3.5 Companion Technology Program 40
3.6 Symbian Signed 42
4 Twenty reasons why smartphones will win 45
4.1 Two kinds of battle 45
4.2 Multitasking 46
4.3 Messaging and entertainment 47
4.4 Mobile knowledge access 49
4.5 Organizers and finance 50
4.6 Pocket consolidators 51
4.7 Social tools 52
4.8 Personal development 53
4.9 Phones win 54
4.10 Openness wins 55
Part 2 Thriving on scale 57
5 Managing large projects 61
5.1 Smartphone projects vs. feature phone projects 61
5.2 Three approaches to large projects 62
5.3 How large projects differ from small projects 63
5.4 Project groupware 64
5.5 Confidentiality issues 65
5.6 Five central project documents 66
5.7 Auditing document readership 66
5.8 Processes and agility: education vs. processes 67
5.9 Problems when groupware is short-cut 69
5.10 Symbian’s use of groupware 69
6 Managing defects 73
6.1 Introduction to smartphone defect management 73
6.2 Living with defects 75
6.3 Aside: an embarrassing moment with defects 76
6.4 Defect priorities 78
6.5 The process of verifying a defect fix 79
6.6 Advanced defect investigation 80
6.7 Defect status values 82
6.8 Defect database requirements 83
6.9 The role of the project leader in managing defects 83
7 Managing configurations 85
7.1 Introduction to configuration management 85
7.2 Aside: learning about configuration management 86
CONTENTS ix
7.3 Consequences of weak configuration management 88
7.4 Basic principles of configuration management 89
7.5 Codeline strategy – single projects 90
7.6 Codeline strategy – multiple projects 93
7.7 Beyond codeline strategy 95
8 Managing integration 97
8.1 Integration vs. creation 97
8.2 Mainlines and development codelines 98
8.3 Iterative development 100
8.4 Gate-keeping and integration tests 102
8.5 Dealing with build or test failures 103
8.6 The weekly integration cycle 104
8.7 Integration discipline 105
9 Managing interfaces 107
9.1 Knowing when components belong together 107
9.2 Limits of rebuilding source code 108
9.3 Forms of compatibility 110
9.4 The compatibility virtuous cycle 111
9.5 System compatibility board 112
9.6 Responsibilities with regard to compatibility 113
9.7 Interface access and interface status 114
9.8 Versioning 116
9.9 Future-proofing interfaces 117
10 Managing testing 119
10.1 Beyond complete testing 119
10.2 Testing in context 120
10.3 Functional tests 121
10.4 Basic Acceptance Tests 123
10.5 Specialist tests 123
10.6 Friendly User Tests 125
10.7 Mandatory tests 128
10.8 Automated tests 128
11 Managing tools 131
11.1 The need for a tools champion 131
11.2 Debuggers 132
11.3 Emulators 135
11.4 Profilers and loggers 136
11.5 Static code analysis 137
11.6 Build system 139
11.7 Distribution system 141
x CONTENTS
11.8 Miscellaneous tools 142
11.9 Dangers with tools 143
12 Managing plans and change 145
12.1 Beyond complete planning 145
12.2 Causes of change 147
12.3 Handling change requests 148
12.4 Variable task estimates 151
12.5 Practical example of agile scheduling 154
12.6 Accepting slack 154
12.7 Aggressive vs. defensive scheduling 156
12.8 Authentic vs. inauthentic scheduling 158
12.9 Beyond meeting customer requests 159
13 Managing uncertainty 161
13.1 The 80–20 rule for planning 161
13.2 Identifying the project planning hot list 162
13.3 Iterating the project plan 163
13.4 Developing features outside the agreed core 165
13.5 The 80–20 rule for task estimation 167
13.6 Typical project trouble spots 168
13.7 Pros and cons of milestone reviews 169
13.8 Dealing with milestone delays 171
13.9 Cut features not corners 172
14 Simplifying smartphone projects 175
14.1 Beyond difficulty 175
14.2 Reuse rather than reinvent 176
14.3 The benefits of frequent releases 177
14.4 Symbian’s adoption of the frequent
release model 179
14.5 Use of reference designs 181
14.6 Silver bullets vs. disruption 182
Part 3 Symbian’s design philosophy 185
15 Design goals for Symbian OS 187
15.1 The birth of EPOC32 187
15.2 Defining the EPOC RISC architecture 188
15.3 Software goals from 1995 189
15.4 Separating the engine 192
15.5 Nine passions 193
CONTENTS xi
16 Designing for efficiency 197
16.1 The original electronic organizers 197
16.2 Limits of Moore’s Law thinking 198
16.3 Causes of code bloat 200
16.4 Designing algorithms 202
16.5 Understanding the compiler 204
16.6 Adopting OO 205
16.7 Selecting C++ 207
16.8 Text descriptors 209
17 Designing for robustness 213
17.1 Alloc heaven 213
17.2 Expecting the unexpected 215
17.3 The perils of multitasking 216
17.4 Exception handling 217
17.5 Common mistakes in destructors 219
17.6 Seeking out failure cases 220
17.7 Attitudes towards defects 220
17.8 Protecting the smartphone vital assets 222
18 Designing for usability 225
18.1 ‘‘The operation was a success,
but the patient died’’ 225
18.2 Enchantment 226
18.3 Designing the user interface 227
18.4 Multimedia performance 229
18.5 Understanding the real competition 229
18.6 Customer orientation for developers 230
18.7 Designing panics 231
19 Designing for longevity 233
19.1 Preparing for variants 233
19.2 Be ready to fail fast 234
19.3 Prepare your own SDK 235
19.4 The value of codevelopment 236
19.5 Basic principles for reusable solutions 237
19.6 The value of architecture 238
19.7 The value of ignorance 239
20 Designing for smartphones 241
20.1 The licensing question 241
20.2 Focus on strategy 242
20.3 Smartphone heritage 244
xii CONTENTS
20.4 Active objects 246
20.5 Power management 247
20.6 Beware stray signals 248
20.7 Final comments on asynchronous events 249
Part 4 Human aspects of smartphone
projects 251
21 The essential role of the project manager 253
21.1 Focus 253
21.2 Project manager vs. technical lead vs. product
manager 254
21.3 Project review meetings 255
21.4 Commercial negotiations with third parties 257
21.5 Project manager authority 258
22 The essential role of the support network 261
22.1 Pros and cons of support consultants 261
22.2 Cultivating connections 263
22.3 Building a team out of nothing 264
22.4 Helping consultants to be effective 265
23 The essential role of renewal 267
23.1 The role of the post partum 267
23.2 Line management skills 268
23.3 Circulation of team members 269
23.4 Principles of collaboration 270
23.5 The increasing importance of software 272
23.6 A guide for software leaders 273
23.7 Symbian OS renewal 274
Appendix 1 Annotated glossary of abbreviations 277
Appendix 2 Selected bibliography 285
Appendix 3 Acknowledgments 289
Index 291[br]<p align=right><font color=red>+5 RD币</font></p> |
本帖子中包含更多资源
您需要 登录 才可以下载或查看，没有账号？注册
×
|
IP卡
狗仔卡
发表于 2007-8-27 22:49:41
提升卡
置顶卡
沉默卡
喧嚣卡
变色卡
显身卡