Hi, here's another question that stands up at least for me:)

What is the color modeling statement about business vs. system roles? How do
they corressponds to each other? How does their relation affects the model?

Details:

First let me clearly define what I mean about the above terms. By "business
role" I mean real world roles within a business processes. By "system role" I
mean roles that authorize to do something in the system.

Theoratically speaking I can imagine 3 types of relations:
A. A business role that has a corresponding system role. Sample: The student
registration application is a self service one. Every student can register
himself to a course.
B. A business role without a corressponding system role. Sample: The student
registration application is a not self service one. Student can register
themselves (in the systems) thru office clerks.
C. The inverse of the above (which doesn't make much sense from the analysis
point of view)


Why do I ask it? In my experience system roles are usually designed as generic
entities: there is only one role object holding every possible system roles and
the semantics are captured through security policy configurations. Meanwhile
business roles are many times designed as first class ("strongly typed")
entities in the system. This seems to me a mismatch.

What is the DNC solution for the above problem? Does DNC cover system roles at
all? Any real life example from someone who met similar questions? For the "A"
and the "B" type...

Cheers
Gyula