MHonArc v2.5.2 -->
xacml message
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [Elist Home]
Subject: RE: [Use Case:] PFC
Title: RE: [Use Case:] PFC
I do
think change histories (or "revision history" as I am used to calling
them)
are
good. The granularity and implementation of these are possibly best
left
to the
people who are responsible for a particular type of document,
rather
than taking a vote. Inputs and comments such
as what Ken made below
are
good and helpful in arriving at a consensus solution that
works.
Cheers,
-Suresh
I
understand the points everyone is making. I feel a change history provides
valuable insight into any document if it is concise, exists as part of the
document and is focused on important changes or decisions. Let's vote on
it and if the group decides we don't need it, I'll live with
that.
Ken Yagen
Director, Software Development
CrossLogix,
Inc
www.crosslogix.com
Ken,
I do
hear your concern - we want to know what we built is really what we wanted to
build.
We
might get there one day. Change logs on individual use cases may be a
solution.
My
point really was that our interest in use cases is really in the requirements
they embody
for
policy expression language and the interpretation model. If the use cases
change, then
the
use case submitters are responsible for that. So, why worry.
Cheers,
-Suresh
Suresh,
One of my concerns is that 6-9 months from now when we finish up the
spec (or whatever our timetable is) we should be able to look back at the
use cases to verify they were adequately addressed and understand why they
are the way they are. I've seen before when this was done and the final
version of the use case was not fully addressed and no one could remember
why the use case was changed.
Ken Yagen
Director, Software Development
CrossLogix,
Inc
www.crosslogix.com
Bill has graciously agreed to lead the first phase
of getting the template out
and making sure we have a document with a uniform
format. I am under a time
crunch for the next 3
weeks.
The goal of this whole exercise, at least in my
opinion, is to get the major
"unique" requirements coming out of each use case.
Given this, I am not
a
proponent of polishing the use cases beyond what is necessary to
achieve
the above goal. Ken, do you see any point going
beyond this?
.
Regards,
-Suresh
Bill,
Looks pretty good. Could we use a change history log
detailing modifications to the use case with a date and brief description
for the change? Also, will we have seperate glossaries for each use case
or will the glossaries be merged into one?
Also, do we have a documentation standard for XACML
documents? We could use the one from SAML.
Ken Yagen
Director, Software
Development
CrossLogix, Inc
www.crosslogix.com
-----Original Message-----
From:
bill parducci [mailto:bill@parducci.net]
Sent: Monday, August 13, 2001 10:00 AM
To: xacml
Subject: [Use Case:] PFC
i am sending out a Plea For Comments with the hope that
this will spur
review of the use case template
that i submitted last week. my goal is
to have
this thing 'ready' by friday so that the use case owners can
began transposing their respective information.
thanks
b
------------------------------------------------------------------
To unsubscribe from this elist send a message with the
single word
"unsubscribe" in the body to:
xacml-request@lists.oasis-open.org
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [Elist Home]
Powered by eList eXpress LLC