From: Andrew Gabb (agabb@tpgi.com.au)
Date: Sat Apr 24 2004 - 16:13:43 EST
Debbie Lawther wrote:
> The 'taxonomy' question comes from trying to find different words for
> 'requirements' at the level of business need, as opposed to those
> related to developing a specific system. The difference would be, say,
> 'PC users want to be able to send emails and do calculations and store
> pictures', vs. 'a calculator implemented on a PC needs to take input
> from both numeric keys and the key-pad'. Another dimension might be
> requirement states at different points in the development life-cycle.
I guess the answer is yes and no. Some folks have tried to, but I've never seen a taxonomy that I'd regard as complete, or one where the criteria for classification are sufficiently robust to ensure that different people would end up with the same classifications. As one example, you may like to check out the Requirements Categorization paper at http://www1.tpgi.com.au/users/agabb/
With regard to your two examples, I'd regard the first as operational requirements, ie what the users or operators want to *do* with the system, often derived from operational concepts, scenarios or user level use cases. The second is often called a functional requirement (what the system should do), but there are many levels of these as the design progresses.
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 Apr 26 2004 - 09:00:17 EST