Dan Bunea

CHAPTER 4: Learning and adapting

2008-04-25T08:28:15Z

4. Learning and Adapting Introduction Software development is a continuous learning activity between the customer who knows the business domain and the developers who know the software. Since the software product needs to combine the two areas of knowledge, the customers must teach the software developers about the business domain and the software developers must teach the customer enough about software so that they can better express their requirements. This learning activity is done throughout...(read more)

CHAPTER 3 (continued) : 3.4 Collaborating

2008-04-17T09:51:47Z

3.4 Collaborating Introduction One of the values of the agile manifesto states: “Customer collaboration over following a contract” being completed then in the principles by: “ Business people and developers must work together daily throughout the project”. It is very clear that day by day collaboration, between team members or between programmers and customers can deliver better software and, as a result, close collaboration stands at the base of all agile methodologies. Why is collaboration important...(read more)

CHAPTER 3: Communicating and Collaborating

2008-04-11T07:06:21Z

3.1 Introduction Communication is considered to be the main factor in a project’s success or failure. Alistair Cockburn calls software development “a game of communication and invention”, in his book “Agile Software Development”, where a big part is dedicated to explaining communication problems and how communication influences the development of a software project. In all agile methodologies, communication and close collaboration with the customer is emphasized as a “must do” practice; in XP two...(read more)

CHAPTER 2: Agile methodologies

2008-04-04T08:25:40Z

2.1 Introduction What is a methodology? A methodology for software is a set of related rules, principles and practices that, once put in practice, can help deliver valuable software, to the client on time, over and over again. Your methodology is everything you do regularly to get your software out. It includes who you hire, what you hire them for, how they work together, what they produce and how they share. [Cockburn, 2004] Characteristics of an agile methodology Agile methodologies are characterized...(read more)

CHAPTER 1: Problems and causes with the way we develop software

2008-03-28T12:37:43Z

Troughout this chapter I will try to show briefly how the software industry went from one extreme to another, in the processes used to develop software. If at first chaos was the main problem, then the software industry went straight into the other extreme adopting the extremely heavyweight "waterfall" process, where software was very hard to develop because there were too many rules. As an example at the beginning of Mary and Tom Poppendieck’s book “Lean Software Development: An Agile...(read more)

The agile mini book - a 6 week series

2008-03-21T14:51:05Z

About 2 years, ago, I spoke with someone about writing an agile mini book. I wrote the book, but things changed, and it wasn't published. Now I decided, to publish it, chapter by chapter, week by week so for the next 6 weeks this is what can be expected: CH1: Problems and causes CH2: Agile methodologies 2.1 Introduction 2.2 Agile menifesto and principles 2.3 Agile methodologies, practices, properties and tools 2.4 XP 2.5 SCRUM 2.6 Crystal Clear 2.7 Lean Software Development 2.8 AMDD 2.9 DSDM...(read more)

Lucene indexes as agile databases

2007-10-21T20:06:43Z

Download Source code Introduction In product development, as opposed to bespoke project development where each client gets its own software, you deliver the same software to each client. This has some advantages: single development stream, with multiple sales but in reality each client will want to be able to customize its own product. Each will divide its products differently, will have different fields and if your product is not flexible enough to allow these policies they will reject your product...(read more)

Testing drag'n'drop with WatiN

2007-03-28T11:35:27Z

Many of the recent Web 2.0 applications require drag and drop functionality. Sometimes it is useful, sometimes it is just marketing, but if you have to do it and at the same time you want to write all your code test first (TDD), a new problem arises: how to write a functional test to test the drag drop? Starting from a wonderful article on the 'Z Bar Zone' blog, I modified it to work with WatiN in C#. The code tests the wonderful scripta.aculo.us based drag'n'shop : using System.Threading;...(read more)

Test First Web Applications: TDDing a Castle MonoRail application with C# and Selenium

2007-02-23T08:36:42Z

Published on InfoQ.com Download Source code Introduction TDD samples are mostly based on very simple unit tests. But how could we do something like building a web application test first. What we need to do Let's say that we need to write test first the following feature for an application -manage users (add new, delete, edit user details, list all). Each user will have a Full Name, a Username , a Password and an Email all mandatory. What is TDD Following TDD steps: 1. write the test 2. make it...(read more)

Model View Presenter - is testing the presenter enough?

2007-01-24T15:13:52Z

Source code: Download Lately, I have noticed that the Humble Dialog Box or Model View Presenter are gaining more and more acceptance among software developers, especially in agile communities, because of its benefits regarding the very good separation between the view and the behavior and because it can be very easily unit tested, on a problematic field: user interface. Let's meet Model View Presenter In model view presenter just as Martin Fowler or Michael Feathers [2] say, the logic of the...(read more)

Ajax Scaffolding with Castle MonoRail and C#

2007-01-23T14:21:36Z

Download Sources, and view demos Goal Let's say we need to write an application very fast, that can do the basic CRUD operations for a Product. Ruby on rails ( www.rubyonrails.org ) came up with the excellent idea of scaffolding, and the idea was ported into the Castle Monorail project ( www.castleproject.org ). However, the default generator both in ROR and in MR, do not generate ajax based code. For ROR the solution is at: www.ajaxscaffold.com but nothing so far for MR. So I decided to take...(read more)

Ajax Scaffolding generator with Monorail: a VS.NET 2005 addin

2007-01-18T14:24:02Z

Download the VS 2005 addin In my previous article, I explained how by modifying Marc Andre Cournoyer's generator, we made it generate Ajax based, scaffolding code for Castle MonoRail. In the meantime, my colleague Gabi Munteanu, managed to put together a Visual Studio 2005 addin, exactly for this purpose. 1. Generate the model Let's start from an generated ActiveRecord class called Project we had the last time, generating the ajax scaffolding code needed for the project: obtaining: using...(read more)

To obtain good code, writing tests and code is faster then code alone

2007-01-12T05:38:33Z

A few weeks ago on the TestDrivenDevelopment mailing list, Ron Jeffies, one of the XP gurus stated that "in order to obtain good code, writing tests and code is faster then just code". To find out if this is true or not let's make a small experiment. The mini TDD experiment We assume that we are programmers and we need to code a function that divides two positive numbers. For this experiment we will compare the traditional and the TDD approaches. Approach #1. Code and fix As programmers...(read more)

Agile adaptive planning and fast delivery sample

2006-11-27T18:34:07Z

After seeing that there are very many people that find it hard to see how agile handles adaptive planning, letting the customer not know from the beginning what he wants, I wanted to develop a mini sample to show these concepts in practice. A small agile process practice sample Let’s consider that we have a new client who wants a new software product to manage and track his sales and customers. He wants the system to go live in 2 months. We meet and establish what is required, then plan to meet the...(read more)

How TDD improves development speed and is very cost effective

2006-11-26T02:31:25Z

When it comes to automated tests the first impression everyone (including myself) thinks that that would certainly increase the amount of time a certain feature is developed in. However as I started to practice TDD, Test First Programming, increasing the number of tests I came to the conclusion that automated tests actually allow you and the team to develop faster then without. Move faster ahead in development A simple comparison of programming vs walking on a rope. When walking on a rope, at a height...(read more)