Choose an application

• Reference Manager
• EndNote
• RefWorks (Direct export to RefWorks)

This book describes how to apply ICONIX Process (a minimal, use case-driven modeling process) in an agile software project. It's full of practical advice for avoiding common agile pitfalls. Further, the book defines a core agile subset so those of you who want to get agile need not spend years learning to do it. Instead, you can simply read this book and apply the core subset of techniques. The book follows a real-life .NET/C# project from inception and UML modeling, to working code through several iterations. You can then go on-line to compare the finished product with the initial set of use cases. The book also introduces several extensions to the core ICONIX Process, including combining test-driven development (TDD) with up-front design to maximize both approaches (with examples using Java and JUnit). And the book incorporates persona analysis to drive the projects goals and reduce requirements churn.

Computer software --- Development. --- Development of computer software --- Software development --- Information Technology --- Computer Science (Hardware & Networks) --- Java (Computer program language). --- Software engineering. --- Java. --- Software Engineering/Programming and Operating Systems. --- Computer software engineering --- Engineering --- Object-oriented programming languages --- JavaSpaces technology

Choose an application

• Reference Manager
• EndNote
• RefWorks (Direct export to RefWorks)

Rigor Without the Mortis Many people (especially agilists) associate a high-ceremony software development process with a dead project (i.e., rigor mortis), and this association is not entirely incorrect. Our approach aims to put back the rigor while le- ing out the mortis that is, we can do rigorous analysis and design without killing the project with an excessively high-ceremony approach. The goal of this book is to describe that process in full detail. Agility in theory is about moving ahead at speed, making lots of tiny course corrections as you go. The theory (and it's a good one) is that if you spend months or years producing dry specifications at the start of the project and then set them in concrete,  this doesn't necessarily (and in practice, doesn't) lead to a product that meets the c- tomer's requirements, delivered on time and with an acceptably low defect count. It's likely that the requirements will change over time, so we need to be prepared for that, and it's likely that a lot of the original requirements will turn out to be wrong or new requirements will be discovered after the requi- ments concrete  has set. Agile methods answer this problem in a number of different ways, but the overriding principle is to break things down into smaller chunks and not to go setting anything in concrete (least of all your requirements specs).

Programming --- Agile --- programmeren (informatica)