|
Replies:
1
-
Pages:
1
-
Last Post:
Feb 25, 2002 11:00 PM
by: import-bot
|
|
|
Posts:
20,296
Registered:
12/6/03
|
|
|
|
Requirements vs Rules...
Posted:
Aug 28, 2001 11:00 PM
|
|
[Originally posted by matthewanderson01]
Ben,
I read your book a while back (kudos BTW!) and I'm dealing with a particular
client who doesn't understand the difference between a software requirement
and a business rule. My take is that a set of rules (meaning 1 or more) make
up a requirement. Does your book describe how to drive out rules from
requirements (I can't remember)? With the emergence of business rule engines,
you could actually invalidate requirements by changing business rules. Do you
know of any organization that is researching how this can be managed?
Thanks,
Matt
|
|
Posts:
20,296
Registered:
12/6/03
|
|
|
|
Re: Requirements vs Rules...
Posted:
Feb 25, 2002 11:00 PM
in response to:
import-bot
|
|
[Originally posted by williamadams]
there are no business rules
there are guidelines
if they can't be ignored
then the special cases will kill you
exceptions need to be made
errors need to be fixed
real requirements are fixed
derived requirements need flexibility
in case or error or omission
and unanticipated usage
==========================
> Ben,
>
> I read your book a while back (kudos BTW!) and I'm dealing with a particular
> client who doesn't understand the difference between a software requirement
> and a business rule. My take is that a set of rules (meaning 1 or more) make
> up a requirement. Does your book describe how to drive out rules from
> requirements (I can't remember)? With the emergence of business rule engines,
> you could actually invalidate requirements by changing business rules. Do you
> know of any organization that is researching how this can be managed?
>
> Thanks,
>
> Matt
|
|
|
Legend
|
|
Gold: 300
+
pts
|
|
Silver: 100
- 299
pts
|
|
Bronze: 25
- 99
pts
|
|
Manning Author
|
|
Manning Staff
|
|
