[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [epf-dev] supporting requirements
|
I've saw this in supporting requirements template. I haven't
understand this yet. I'm confusing about what kind of requirements
should be in a use case, the requirements that fits better in "System
wide functional requirements" or "Business rule" sections of
supporting requirements template.
On 6/19/07, Nate Oster <noster@xxxxxxxxxxxxx> wrote:
Ronaldo,
I'm not sure where in OpenUP you're referencing, but I think the
distinction is SCOPE. "System wide Functional Requirements" are
*global* - they apply to the entire system. The entire system must
behave a certain way.
"Business Rules" might be associated with only part of the system. For
example, there may be many business rules about a Register Member use
case, but contradictory business rules for the Manage Member Profiles
use case. There could be any number of reasons for this, such as
different actors (perhaps one is an end user, the other a customer
support engineer).
Is there somewhere that this is too ambiguous in OpenUP? We can always
submit a bug! :)
Nate
-----Original Message-----
From: epf-dev-bounces@xxxxxxxxxxx [mailto:epf-dev-bounces@xxxxxxxxxxx]
On Behalf Of Ronaldo r
Sent: Monday, June 18, 2007 3:30 PM
To: Eclipse Process Framework Project Developers List
Subject: [epf-dev] supporting requirements
What's the difference of "System wide Functional Requirements" section
and "Business Rules"? What kind of rule fit in each of these?
_______________________________________________
epf-dev mailing list
epf-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/epf-dev
