: Don Rosenberg, Mark Collins-Cope, Matt Stephens
: Agile Development with ICONIX Process People, Process, and Pragmatism
: Apress
: 9781430200093
: 1
: CHF 53.00
:
: Informatik
: English
: 261
: Wasserzeichen/DRM
: PC/MAC/eReader/Tablet
: PDF
*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.
Contents6
About the Authors13
About the Technical Reviewer14
Acknowledgments15
Introduction16
Part 1 ICONIX and Agility19
Chapter 1 What Is Agility? (And Why Does It Matter?)20
What Software Agility Isn t22
The Goals of Agility23
Why Is Agility Important?24
What Makes a Project Agile?25
Challenges of Being Agile28
Agile Methodologies30
Agile Fact or Fiction: What Does Being Agile Mean?39
Summary40
Top 10 Practices and Values That Make a Project Agile40
Chapter 2 Characteristics of a Good Software Process41
What s in a Software Development Process?42
What Makes a Good Agile Logical Process?44
Human Factors47
Agile Fact or Fiction: Team Structure and Human Factors50
Summary54
Chapter 3 ICONIX Process: A Core UML Subset55
A Brief History of ICONIX Process56
What Can ICONIX Process Do for My Project?57
ICONIX Process in Theory (aka Disambiguation and Prefactoring)57
ICONIX Process in a Nutshell60
More About Disambiguation69
More About Prefactoring and Model Refactoring72
Key Points to Remember72
Summary75
Chapter 4 A Core Subset of Agile Practices76
Why Define a Core Subset of Agile Practices?76
Agile ICONIX: The Core Subset of Agile Practices76
Refactoring the Agile Manifesto86
Agile Fact or Fiction (Continued)90
Summary100
Part 2 Agile ICONIX Process in Practice:The Mapplet Project101
Chapter 5 Introducing the Mapplet Project102
So, What s a Mapplet, Anyway?102
Mapplet Goals105
Mapplet Requirements105
Project Inception: A JumpStart Workshop in Action108
Mapplet Architecture109
Initial Use Case Modeling for the Mapplet110
First Release Plan111
More Information on ArcGIS As Used by the Mapplet112
Summary113
Chapter 6 Modeling the Mapplet (Release 1)114
Beginning with a Prototype (and Just a Little Bit of Modeling)114
Visual Acceptance Testing115
First Pass Modeling Efforts (and Some Typical Modeling Mistakes)116
Tightening Up the Model121
Let s Take a Look at Some Code126
Et Voila! The First (Working Prototype) Release134
Summary135
Chapter 7 Synchronizing the Model and Code: One Small Release at a Time136
Keeping It Agile136
Divergence of Code and Design over Time137
Design Review138
And Today s Lesson Is . . . 160
Summary160
Chapter 8 Mapplet Release 2161
Customer Feedback on the First Release161
How Persona Analysis Was Used to Drive the Requirements162
Planning the Second Release164
Analysis Review169
Designing Release 2170
Source Code: Refactoring Is Still Useful After Doing Use Case Driven Modeling172
Screenshots of the Finished Product179
Agile Scorecard for the Mapplet Project180
Summary181
Part 3 Extensions to ICONIX Process182
Chapter 9 Agile Planning183
Why Agile Planning?183
Agile Planning Terminology185
Agile Planning Building Blocks186
Agile Planning Phases193
Agile Planning Principles194
Summary198
Chapter 10 Persona Analysis199
Extending ICONIX Process with Persona Analysis199
The Three Pieces of the Jigsaw Puzzle200
Building the UI Around a Target User202
Using Interaction Design to Identify Alternate Scenarios205
Keeping a Tight Rein on Complexity206
Using Interaction Design to Identify Actors and Use Cases206
The Finished Use Case207
Visual Acceptance Test for Release 2208
Summary211
Chapter 11 A Vanilla Test-Driven Development Example212
A Brief Overview of TDD213
A Vanilla TDD Example214
Summary234
Chapter 12 Test-Driven Development with ICONIX Process235
How Agile ICONIX Modeling and TDD Fit Together235
The Vanilla Example Repeated Using ICONIX Modeling and TDD235
Summarizing ICONIX+TDD256
Stop the Presses: Model-Driven Testing257
Summary259
Index260