Archive for the ‘iidtrackingsuite’ Category

Day 2: Early Morning

November 27, 2008

The day started with a quick standup meeting in the morning;

It included Shaun (the developer), Pat (the project manager/requirements guy) and Claire (the Development manager). Pat speaks first:

Pat: “..As you know I was on site at the clients yesterday. It was a good day, we captured a lot of general requirements and were able to delve into some specifics in certain areas. I will document this today. I also spoke to them about our approach, let them know that we would need their time also so we can make the best product we can for them. They were a little hesitant about that so I promised to come back and explain more on that matter when we meet next. Basically they want to get moving on this ASAP so they are looking for a quote. As always, i will document everything on the appropriate project wiki page..So today I will continue to document everything and document our approach with the customer etc..”

Shaun: “..I was doing some work on project x yesterday, I had an hour or two left at end of day and seeing that Pat said it was a web-based project, I began setting up the infrastructure for this project. I will continue this today and hook up Hudson to our projects. By the end of the day I should the infrastructure setup finished and if i have time will look at what Pat has written up…”

Claire: “..Great guys, Pat, when is the quote to be in by exactly? It would be great if we could get some time to do some (RAD) rapid application development, flesh out some of the quick wins and discover any possible problems we may encounter with the requirements so far. It would be great to give you a working prototype to show and help you flesh out the requirements further when you got back to them. We really want to impress this customer, we could end up getting alot of work from them…”

Pat: “..At least a week Claire, maybe two, I will be talking with them later in the day on the phone so will flesh that out. I agree, by the sounds of things they have plenty of ideas in the pipeline, it would be great if we could become their preferred supplier of bespoke software..”

So after 10mins of talking they break up and get back to their work for the day.

Day 1: Getting Started

November 26, 2008

The project started with a meeting between our project manager and the customer requiring the software.

They have arranged a meeting whereby they introduce their company and their specific needs. It is explained that they are filthy rich and have decided to reinvent the wheel again and wish to have their own custom bespoke defect tracking tool as they just simply haven’t been able to get to grips with the current products that exist out there…

So the first requirement we have from our customer is very general. We know that we will be developing a web-based defect tracking tool.

Our project manager slash requirements gathering expert (depending on the hat he is wearing) communicates with us (during a tea break) and lets us know that the project is required to be web based. Other than that so far there is no specifics but he says that they couldn’t care less about how we develop it or what tools and technologies we use, that’s your job they say.

We have one developer (Shaun) assigned to this project so far. The rest are putting the finishing touches to another project. It is hoped to ramp up the personnel on this project soon when the requirements/specifications start coming in. Once Shaun the developer heard it was a web based project, he quickly sets about creating the infrastructure that will allow him and others to develop a web based application.

Meanwhile our project manager continues to talk with the customer and gather the requirements for the project.

Its easy for Shaun, he has worked on several web-based projects in the company now and had good knowlege of the setup and the technologies. He also knows work has been done documenting the development environment on the wiki, Shaun opens the wiki page and reads down the checklist of preferred technologies:

  1. Java 1.5.0_xxx (latest update)
  2. Eclipse IDE (Ganymede) JEE version
  3. Subversion SCM for source control
  4. Hudson for continuous integration
  5. ANT for build management
  6. Spring, SpringMVC, Spring webflow
  7. JSP, HTML, CSS, JavaScript, JSF etc
  8. JUnit, TestNG for test automation frameworks
  9. Selenium, WebDriver for web-based in-browser testing (typically end-to-end tests)
  10. Tomcat, JBoss, Glassfish for supported containers/Application servers
  11. PMD, CPD, FindBugs, Checkstyle etc to automate inspections
  12. Cobertura, Emma for Code coverage
  13. and the list goes on…

Shaun has an hour left at work so he quickly creates a spring project and adds the default WAR project structure. He adds an ANT build to the project with support for developing with tomcat container. He quickly adds some basic test dependencies and some files so he can do a quick manual test to verify the ANT build generates a WAR file and can deploy it to the configured location. It works first time but it was easy, he just replicated the way they have did it before. Happy that his build is working, Shaun checks in the code as a new project on Subversion. You can view the code at the following:

svn command line

svn checkout http://iidtrackingsuite.googlecode.com/svn/trunk/ iidtrackingsuite-read-only

svn url: http://iidtrackingsuite.googlecode.com/svn/trunk/

Or

Browse the code online at http://code.google.com/p/iidtrackingsuite/source/browse/

IID Experiment

November 26, 2008

Today I create a new project on google.code called iidtrackingsuite.

The general idea is to use the project as an experiment to investigate the IID approach to developing software.