program selection system

Founded on a resilient Open Standards Content Backbone, Fabasoft Folio and Fabasoft DUCX provide a powerful agile development platform for process-enabled content applications, portals and e-Services (Web 2.0). Fabasoft DUCX will enable you to rapidly develop business applications using Microsoft Visual Studio or Eclipse. In this session we will give an insight look and live-demonstrations, how quality, usability, and style can be achieved in less time.

Distributed operations, open source tools, mashups, and SaaS are breaking down the traditional boundaries between vendor-supplied and custom-developed software. It’s now possible – if not necessary – to integrate development and run-time activities onto a seamless distributed platform. During this vendor talk, Charlie Rudd, President and CEO of SolutionsIQ, will demonstrate key elements of SolutionsIQ’s Agile development platform: • Mashups of SaaS and open source tools for development and continuous integration

Agile Planner for digital tabletop (APDT) is an agile planning tool supporting collocated and distributed agile planning meetings. Utilizing digital tabletop technology, APDT supports group interactions and natural behavior of agile meeting attendees. APDT connects tabletops at different locations, creating a virtual-collocated platform that integrates distributed agile teams into a shared meeting scenario. APDT is a novel planning tool that addresses communication problems found in distributed agile planning meetings.

First, I’d like to present an experience report about real-life development with mock objects: the test-driven struggle. Then I will show how to improve the TDD experience and code quality through a slightly different approach to mocking: taking a step back from the invasive nature of interaction based testing and getting closer to the way we do state based testing. Finally, I will introduce a new mock library for java: Mockito which was driven by these observations. Mockito implements what Gerard Meszaros calls a Test Spy.

Process in short:

Experience report (shows the problem) -> tutorial of a new tool (tries to fix the problem)

With Continuous Integration, the chances rise exponentially with team size that as you fix a build or test problem, the integration of somebody else’s work creates a new build or test problem. Multi Stage CI addresses this problem by extending the practice of temporary individual isolation to features, teams, staging, QA, and release. This demonstration will show how Multi-Stage Continuous Integration works in the real world by drawing on the experiences of three large distributed teams. See changes by hundreds of simulated developers make their way through the system.

Agile Development teams can utilize a number of techniques to visualize and track the items they work on. There is also various models to manage your personal life, Getting Things Done and the Mark Forster models.
For Product Owners and analysts there is a lack of similar tools and techniques. This demonstration will show how a Kanban board (task board with “states”) can be combined with a “round robin” scheme to keep analysist and Product Owners working on multiple tasks of high priority, but with potentially long lead times and fuzzy done criteria.

JTestMe dynamically defines optimised smoke test suites for Java applications - dramatically improving the continuous integration cycle time. It is an Open Source project by ThoughtWorks, hosted on the Codehaus.

When a co-located team moves into multiple locations, sometimes across continents, it reduces team productivity and introduces lots of challenges with teams trying to deal with database and database design. Like any other aspect of Agile projects why not make the database design and development a shared task to be done by every one on the team. Why not link the database design to the feature being developed and make the database part of the Continuous Integration, such that build status is visible to everyone and database artifacts can be version controlled just like code.

We propose Exploratory Test Driven Development (ETDD): a methodology where the user writes Parameterized Unit Tests and lets an automated tool generate parameter values to cover all reachable statements. This exploratory code analysis makes ETDD different from traditional Test Driven Development. As a result the developer writes fewer, more expressive tests by hand and lets the automated tool systematically test all corner-cases. In this talk, we present ETDD for .Net using Pex, an Automated Exploratory Testing tool from Microsoft Research.

The tools and techniques needed to do Test Driven Development are extremely well documented for Object Oriented languages, but how do we do TDD data management and business intelligence projects using 4th generation ETL languages like Ab Initio?

In this talk, I will show you how to do TDD when transforming data is the sole aim of the project. The talk will be divided into two parts. First, the theory of TDD in data management applications and, second, the application of the practices using FIT4Data.