The Artima Developer Community
Sponsored Link

Java Buzz Forum
My thoughts on TDD after one small project

0 replies on 1 page.

Welcome Guest
  Sign In

Go back to the topic listing  Back to Topic List Click to reply to this topic  Reply to this Topic Click to search messages in this forum  Search Forum Click for a threaded view of the topic  Threaded View   
Previous Topic   Next Topic
Flat View: This topic has 0 replies on 1 page
Mike Shoemaker

Posts: 158
Nickname: mikeshoe
Registered: Sep, 2004

Mike Shoemaker is senior Java developer using Ruby
My thoughts on TDD after one small project Posted: Sep 25, 2004 6:10 PM
Reply to this message Reply

This post originated from an RSS feed registered with Java Buzz by Mike Shoemaker.
Original Post: My thoughts on TDD after one small project
Feed Title: Unruly Rambling (java category)
Feed URL: http://www.shoesobjects.com/blog/feed.xml?flavor=rss20&category=java
Feed Description: My thoughts on software, technology, and life in general
Latest Java Buzz Posts
Latest Java Buzz Posts by Mike Shoemaker
Latest Posts From Unruly Rambling (java category)

Advertisement

First, I must disclose that I really only did Test Driven Development in the beginning while coming up with the object model and basic methods. It worked out well for this. I found that it was much harder to drive the detailed design using TDD at later stages. Although, i'll give the approach the benefit of the doubt and say that it was my lack of experience using TDD that caused this.

The project that I worked on was a calculation engine that takes two objects, each with various numbers of subclasses(I won't bore you with the business details) and outputs numeric values. The computation is fairly simple but output is pretty detailed and isn't easy to see problems by simply eye balling the data. Unit tests worked out fantastic here. We have over 120 unit tests that exercise positive and negative paths. I can honestly say that if management came to us tomorrow and asked for another calculation scenario, we could introduce it and be confident that we didn't break anything else almost immediately. Pretty slick.

Although this was a very positive experience, there were some downfalls. When approaching a project with TDD in mind. I'm having a hard time determining how to estimate it. Since you are not doing BDUF (Big Design Up Front), the scope of change is quite unknown. If you haven't worked with a given project before(legacy or new), it would be very hard to estimate resources or timelines.

In my world at work, we are typically give a production date and then figure the timeline out backwards. This allows us to determine how many people it will take to meet the predetermined date. I realized, this approach is less than optimal, but I have to live with it. With this being the case, how can you not do BDUF?

Read: My thoughts on TDD after one small project

Topic: Instance Variables Hiding Previous Topic   Next Topic Topic: Death to Struts! Long live Struts!

Sponsored Links



Google
  Web Artima.com   

Copyright © 1996-2019 Artima, Inc. All Rights Reserved. - Privacy Policy - Terms of Use