Just read this article from Alistair Cockburn. I appreciate his focus on requirements gathering.
Alistair.Cockburn.us | Why I still use use cases
Alistair.Cockburn.us | Why I still use use cases
Wednesday, December 31, 2008
Monday, December 22, 2008
Using RUP As A Scaling Framework For Scrum
Check out this SlideShare Presentation:
Monday, November 17, 2008
Saturday, March 01, 2008
Mockito
No, it's not a new coffee blend.
Some Thoughtworks people gave a talk today about various Mock frameworks, this was after taking a look at our existing codebase - there is a lot of mocking going on (perhaps too much in some areas) and the mock framework of choice is Easymock.
Easymock would have to be (was?) the best framework, well that's until Mockito was introduced. To cut to the chase, it is much easier when it comes to dealing with expectations. Instead of the Easymock style of expect-run-verify, there is a mockito style of run-did stuff happen?
Take a read.
Some Thoughtworks people gave a talk today about various Mock frameworks, this was after taking a look at our existing codebase - there is a lot of mocking going on (perhaps too much in some areas) and the mock framework of choice is Easymock.
Easymock would have to be (was?) the best framework, well that's until Mockito was introduced. To cut to the chase, it is much easier when it comes to dealing with expectations. Instead of the Easymock style of expect-run-verify, there is a mockito style of run-did stuff happen?
Take a read.
Thursday, November 01, 2007
Model-Driven Design Using Business Patterns
Looks like a good book for developers and analysts. I'll look at getting this for sure.
Model-Driven Design Using Business Patterns: "I wrote a book with Jesper Kiehn and Christian Vibe Scheller on Model-Driven Design Using Business Patterns. We believe the approach described in this book is is going to revolutionize the way the software business applications are developed. This book describes the REA (resources, events, agents) model, which specifies the fundamental laws of the business domain. Knowing these laws radically enhances the application designers’ potential to configure business solutions without omissions, and ensures consistency of software applications from the business perspective. This book shows how to apply REA in business software applications, and presents more than 20 structural and behavioral patterns that use the REA as a common backbone."
Model-Driven Design Using Business Patterns: "I wrote a book with Jesper Kiehn and Christian Vibe Scheller on Model-Driven Design Using Business Patterns. We believe the approach described in this book is is going to revolutionize the way the software business applications are developed. This book describes the REA (resources, events, agents) model, which specifies the fundamental laws of the business domain. Knowing these laws radically enhances the application designers’ potential to configure business solutions without omissions, and ensures consistency of software applications from the business perspective. This book shows how to apply REA in business software applications, and presents more than 20 structural and behavioral patterns that use the REA as a common backbone."
Monday, June 25, 2007
Yet another reason to practice TDD - joeyDotNet
This is a great article that discusses the pros/cons of TDD, non TDD.
Yet another reason to practice TDD - joeyDotNet
Yet another reason to practice TDD - joeyDotNet
Yet another reason to practice TDD
Things have been a little slow on the blog lately because this week is the start of a new job/company for me. I'm still getting a feel for things and of course one of the first things I'm trying to get folks interested in is TDD. I have a usual list of advantages and points that I use for getting across to folks the benefits of practicing TDD. Most of which center around the fact that TDD is primarily a design tool, and the fact that you get a nice set of automated regression tests is just a nice side effect. TDD is not about testing!
But today, after looking at some existing code, I thought of another example that does explain one way in which the "Test" part of TDD is very beneficial.
(For you fellow experienced TDD practitioners, this will be very obvious to you. So this is mainly for those who are still struggling with "why do I need TDD/Unit Testing?"...)
Powered by ScribeFire.
Tuesday, June 12, 2007
Embrace change, your life depends on it
Embrace change, your life depends on it: "Let me first start by warning you that this is a fairly long post. I suspect most people won’t make it to the end. However, if you are serious about being happy, I hope you can at least spend 5 mins reading what I have written.
It will change your life. I promise.
I have been an independent software contractor for several years, performing all sorts of IT development services for clients about town. The agency whom I have been representing at client sites is currently undergoing a major change - they have just been sold to a big consultancy.
Boom! Scary!
As a result of the merger, lots of change is happening. Some folks are questioning where things are headed, what management have planned, how their lives will change etc. Most certainly, there will be job losses as the two companies consolidate things, in particular administrative positions.
With the chaos that’s been unfolding, I’ve thought a bit about “change” in general. What is it? Why do people resist it? Is it always a good thing? What should I do?
With some reflection, I realised that with all inspiration, creation, thought and progress, some form of change must be a precursor. Things just don’t happen on their own. You know the old scientific principle of “energy cannot be "
It will change your life. I promise.
I have been an independent software contractor for several years, performing all sorts of IT development services for clients about town. The agency whom I have been representing at client sites is currently undergoing a major change - they have just been sold to a big consultancy.
Boom! Scary!
As a result of the merger, lots of change is happening. Some folks are questioning where things are headed, what management have planned, how their lives will change etc. Most certainly, there will be job losses as the two companies consolidate things, in particular administrative positions.
With the chaos that’s been unfolding, I’ve thought a bit about “change” in general. What is it? Why do people resist it? Is it always a good thing? What should I do?
With some reflection, I realised that with all inspiration, creation, thought and progress, some form of change must be a precursor. Things just don’t happen on their own. You know the old scientific principle of “energy cannot be "
Subscribe to:
Posts (Atom)
