Well, I'm (obviously) not Johanna, but I'd think a feature is a small, cohesive set of functionality that provides value to the customer/user.
I'm curious whether Johanna agrees...
The soul is dyed the color of its thoughts. Think only on those things that are in line with your principles and can bear the light of day. The content of your character is your choice. Day by day, what you do is who you become. Your integrity is your destiny - it is the light that guides your way. - Heraclitus
Joined: Aug 21, 2004
Originally posted by Ilja Preuss: Well, I'm (obviously) not Johanna ...
Obviously not . I've also an explanation but I like Johanna first say what she has in mind.
I agree with what Ilja said, but I may be more open to what I call "featurettes." Sometimes, you don't have a cohesive set of things that provide value. Sometimes, you know some of what you want to provide, but not all of it. You have to implement something before you know the rest.
For me, the smallest piece of cohesive functionality is still a feature, even if it's not everything the user might want in what Ilja called
small, cohesive set of functionality that provides value to the customer/user.
A cohesive set of things could be a use case to me. Can you give an example of a feature or featurette?
Joined: Feb 10, 2005
Let me try (this is so context dependent I hope my example makes sense). Let's say you're working on a bank application, and you want to do something that says "withdraw money." There are several ways to withdraw: fast cash with one of three specific amounts, and a normal withdrawal.
I call fast cash with one specific amount a featurette. It's not all of fast cash, and it's certainly not all of withdrawal. But it is something of value. Does that make some sense?