Symbian for software leaders principles of successful Smartphone development projects
As a co-founder of Symbian and former executive of Psion Software, David Wood has been actively involved in well over 100 smartphone development projects worldwide. Over the time spent on these projects, he has come to understand the key issues which determine the difference between successful and u...
| Autor principal: | |
|---|---|
| Otros Autores: | , |
| Formato: | Libro electrónico |
| Idioma: | Inglés |
| Publicado: |
Hoboken, NJ :
Wiley
c2005.
|
| Edición: | Repr. with corr |
| Colección: | Symbian Press
|
| Materias: | |
| Ver en Biblioteca Universitat Ramon Llull: | https://discovery.url.edu/permalink/34CSUC_URL/1im36ta/alma991009627261606719 |
Tabla de Contenidos:
- Symbian for Software Leaders; Contents; Introduction: projects, projects, projects; Part 1 Symbian in context; 1 At the heart of the smartphone revolution; 1.1 The phenomenon of smartphones; 1.2 Taking advantage of the smartphone opportunity; 1.3 The role of the smartphone operating system; 1.4 Regarding APIs and operating systems; 1.5 Why Symbian OS?; 1.6 Aside: from organizers to smartphones; 1.7 Coming to terms with Symbian OS; 2 The big picture of a Symbian OS project; 2.1 High-level components of a smartphone; 2.2 Providers of integrated solutions
- 2.3 The commercial model of a smartphone project2.4 Some conclusions from the smartphone commercial model; 2.5 Typical smartphone project timescales; 2.6 Warning regarding timescales; 2.7 Factors influencing project timescales; 2.8 The big picture: beyond timescales; 3 Involving ISVs; 3.1 ISV smartphone opportunity and risk; 3.2 Beyond technical skill-sets; 3.3 Different routes to market; 3.4 Symbian endorsements; 3.5 Companion Technology Program; 3.6 Symbian Signed; 4 Twenty reasons why smartphones will win; 4.1 Two kinds of battle; 4.2 Multitasking; 4.3 Messaging and entertainment
- 4.4 Mobile knowledge access4.5 Organizers and finance; 4.6 Pocket consolidators; 4.7 Social tools; 4.8 Personal development; 4.9 Phones win; 4.10 Openness wins; Part 2 Thriving on scale; 5 Managing large projects; 5.1 Smartphone projects vs. feature phone projects; 5.2 Three approaches to large projects; 5.3 How large projects differ from small projects; 5.4 Project groupware; 5.5 Confidentiality issues; 5.6 Five central project documents; 5.7 Auditing document readership; 5.8 Processes and agility: education vs. processes; 5.9 Problems when groupware is short-cut
- 5.10 Symbian's use of groupware6 Managing defects; 6.1 Introduction to smartphone defect management; 6.2 Living with defects; 6.3 Aside: an embarrassing moment with defects; 6.4 Defect priorities; 6.5 The process of verifying a defect fix; 6.6 Advanced defect investigation; 6.7 Defect status values; 6.8 Defect database requirements; 6.9 The role of the project leader in managing defects; 7 Managing configurations; 7.1 Introduction to configuration management; 7.2 Aside: learning about configuration management; 7.3 Consequences of weak configuration management
- 7.4 Basic principles of configuration management7.5 Codeline strategy - single projects; 7.6 Codeline strategy - multiple projects; 7.7 Beyond codeline strategy; 8 Managing integration; 8.1 Integration vs. creation; 8.2 Mainlines and development codelines; 8.3 Iterative development; 8.4 Gate-keeping and integration tests; 8.5 Dealing with build or test failures; 8.6 The weekly integration cycle; 8.7 Integration discipline; 9 Managing interfaces; 9.1 Knowing when components belong together; 9.2 Limits of rebuilding source code; 9.3 Forms of compatibility; 9.4 The compatibility virtuous cycle
- 9.5 System compatibility board
