From: Andrew Gabb (agabb@tpgi.com.au)
Date: Sat Dec 06 2003 - 15:16:50 EST
Ed Eykholt wrote:
> In product development teams I've been involved with, we often use the
> term feature to indicate a set of functionality in the *solution* space.
> I like using the terms Requirement to indicate the problem (or
> constraint) space and Feature for the solution space. This is closest
> to definition 4 below. How does that resonate with this list?
Suits me - that's what I was getting at, but nothing is black and white. Remember that you also have requirements in the 'solution space' as system design proceeds.
> Under this definition, it would be legitimate to group requirements by
> features when there is a clear solution concept already in mind.
Perhaps, but the *actual* features, as designed and built, may be different. I tend to write 'specs' for small bespoke software systems somewhat this way, particularly where the clients have no real concept of what requirements are.
Note also that the word 'feature' really means 'prominent characteristic' or 'highlight', so the features of a system are the major advantages it offers to potential users.
Andrew
-- Andrew Gabb email: agabb@tpgi.com.au Adelaide, South Australia phone: +61 8 8342-1021, fax: +61 8 8269-3280 ----- ------------------------------------------------------------------------------- To send a message to this mailing list send it to re-online@it.uts.edu.au. To unsubscribe from this mailing list, email majordomo@it.uts.edu.au with the message `unsubscribe re-online' in the BODY of the mail.
This archive was generated by hypermail 2.1.6 : Mon Dec 08 2003 - 09:00:13 EST