Rosenberg / Collins-Cope / Stephens Agile Development with ICONIX Process

People, Process, and Pragmatism
1. ed
ISBN: 978-1-4302-0009-3
Verlag: Apress
Format: PDF
Kopierschutz: 1 - PDF Watermark

E-Book, Englisch, 261 Seiten

*Describes an agile process that works on large projects *Ideal for hurried developers who want to develop software in teams *Incorporates real-life C#/.NET web project; can compare this with cases in book

A bio is not available for this author.

Autoren/Hrsg.

Rosenberg, Don

Collins-Cope, Mark

Stephens, Matt

Inhaltsverzeichnis

1;Contents;6
2;About the Authors;13
3;About the Technical Reviewer;14
4;Acknowledgments;15
5;Introduction;16
6;Part 1 ICONIX and Agility;19
6.1;Chapter 1 What Is Agility? (And Why Does It Matter?);20
6.1.1;What Software Agility Isn’t;22
6.1.2;The Goals of Agility;23
6.1.3;Why Is Agility Important?;24
6.1.4;What Makes a Project Agile?;25
6.1.5;Challenges of Being Agile;28
6.1.6;Agile Methodologies;30
6.1.7;Agile Fact or Fiction: What Does “Being Agile” Mean?;39
6.1.8;Summary;40
6.1.9;Top 10 Practices and Values That Make a Project Agile;40
6.2;Chapter 2 Characteristics of a Good Software Process;41
6.2.1;What’s in a Software Development Process?;42
6.2.2;What Makes a Good Agile Logical Process?;44
6.2.3;Human Factors;47
6.2.4;Agile Fact or Fiction: Team Structure and Human Factors;50
6.2.5;Summary;54
6.3;Chapter 3 ICONIX Process: A Core UML Subset;55
6.3.1;A Brief History of ICONIX Process;56
6.3.2;What Can ICONIX Process Do for My Project?;57
6.3.3;ICONIX Process in Theory (aka Disambiguation and Prefactoring);57
6.3.4;ICONIX Process in a Nutshell;60
6.3.5;More About Disambiguation;69
6.3.6;More About Prefactoring and Model Refactoring;72
6.3.7;Key Points to Remember;72
6.3.8;Summary;75
6.4;Chapter 4 A Core Subset of Agile Practices;76
6.4.1;Why Define a Core Subset of Agile Practices?;76
6.4.2;Agile ICONIX: The Core Subset of Agile Practices;76
6.4.3;Refactoring the Agile Manifesto;86
6.4.4;Agile Fact or Fiction (Continued);90
6.4.5;Summary;100
7;Part 2 Agile ICONIX Process in Practice:The Mapplet Project;101
7.1;Chapter 5 Introducing the Mapplet Project;102
7.1.1;So, What’s a Mapplet, Anyway?;102
7.1.2;Mapplet Goals;105
7.1.3;Mapplet Requirements;105
7.1.4;Project Inception: A JumpStart Workshop in Action;108
7.1.5;Mapplet Architecture;109
7.1.6;Initial Use Case Modeling for the Mapplet;110
7.1.7;First Release Plan;111
7.1.8;More Information on ArcGIS As Used by the Mapplet;112
7.1.9;Summary;113
7.2;Chapter 6 Modeling the Mapplet (Release 1);114
7.2.1;Beginning with a Prototype (and Just a Little Bit of Modeling);114
7.2.2;Visual Acceptance Testing;115
7.2.3;First Pass Modeling Efforts (and Some Typical Modeling Mistakes);116
7.2.4;Tightening Up the Model;121
7.2.5;Let’s Take a Look at Some Code;126
7.2.6;Et Voila! The First (Working Prototype) Release;134
7.2.7;Summary;135
7.3;Chapter 7 Synchronizing the Model and Code: One Small Release at a Time;136
7.3.1;Keeping It Agile;136
7.3.2;Divergence of Code and Design over Time;137
7.3.3;Design Review;138
7.3.4;“And Today’s Lesson Is . . .”;160
7.3.5;Summary;160
7.4;Chapter 8 Mapplet Release 2;161
7.4.1;Customer Feedback on the First Release;161
7.4.2;How Persona Analysis Was Used to Drive the Requirements;162
7.4.3;Planning the Second Release;164
7.4.4;Analysis Review;169
7.4.5;Designing Release 2;170
7.4.6;Source Code: Refactoring Is Still Useful After Doing Use Case–Driven Modeling;172
7.4.7;Screenshots of the Finished Product;179
7.4.8;Agile Scorecard for the Mapplet Project;180
7.4.9;Summary;181
8;Part 3 Extensions to ICONIX Process;182
8.1;Chapter 9 Agile Planning;183
8.1.1;Why Agile Planning?;183
8.1.2;Agile Planning Terminology;185
8.1.3;Agile Planning Building Blocks;186
8.1.4;Agile Planning Phases;193
8.1.5;Agile Planning Principles;194
8.1.6;Summary;198
8.2;Chapter 10 Persona Analysis;199
8.2.1;Extending ICONIX Process with Persona Analysis;199
8.2.2;The Three Pieces of the Jigsaw Puzzle;200
8.2.3;Building the UI Around a Target User;202
8.2.4;Using Interaction Design to Identify Alternate Scenarios;205
8.2.5;Keeping a Tight Rein on Complexity;206
8.2.6;Using Interaction Design to Identify Actors and Use Cases;206
8.2.7;The Finished Use Case;207
8.2.8;Visual Acceptance Test for Release 2;208
8.2.9;Summary;211
8.3;Chapter 11 A “Vanilla” Test-Driven Development Example;212
8.3.1;A Brief Overview of TDD;213
8.3.2;A Vanilla TDD Example;214
8.3.3;Summary;234
8.4;Chapter 12 Test-Driven Development with ICONIX Process;235
8.4.1;How Agile ICONIX Modeling and TDD Fit Together;235
8.4.2;The “Vanilla” Example Repeated Using ICONIX Modeling and TDD;235
8.4.3;Summarizing ICONIX+TDD;256
8.4.4;Stop the Presses: Model-Driven Testing;257
8.4.5;Summary;259
9;Index;260