Hi Paul,
The TC already has:
Use Case IDM Categorizations:
http://wiki.oasis-open.org/id-cloud/UseCaseCategories
Use Case Template (with cloud service/deployment
model categorizations):
Text/HTML Overview: http://wiki.oasis-open.org/id-cloud/UseCaseTemplate
MS Word Doc: http://www.oasis-open.org/apps/org/workgroup/id-cloud/download.php/40706/OASIS%20ID%20Cloud%20-%20Use%20Case%20Template%202011-01-10.doc
As you can see in the latest version
of the draft use case document, I created matrices that show which use
cases (of the 26 already reviewed) were applicable to each of the categorizations.
On our last call, I indicated that some use cases listed more categorizations
than were actually covered in the use case (such as audit) and that we
would need during our reviews to assure that the use cases (process steps)
reflect the categorization (interactions).
Are there others you would propose?
-Matt
"Lipton, Paul C"
<>
02/03/2011 08:50 PM
To
Matt Rutkowski/Austin/IBM@IBMUS, "Anil
Saldhana" <>
cc
"id-cloud" <>
Subject
RE: [id-cloud] Meetings in February
(Use Case Discussion)
From what I've seen, it is useful to establish a basic
taxonomy, if one does not exist, adequate to normalized the use cases to
common terms/entities/concepts, and then merge use cases that are essentially
the same in order to derive a smaller number of use cases expressed in
such a way that they are easier to analyze, prioritize, etc. Otherwise,
it is more difficult to find the common frames of reference that are needed.
In short, analysis is easier once you are sure you are comparing apples
to apples within each use case and between use cases.
Just a thought.
Thanks,
Paul
Paul Lipton
CA Technologies
VP, Industry Standards and Open Source
Member, CA Council for Technical Excellence
Office Phone: +1 609 583-9718
Mobile: +1 267 987-6887
Email:
THIS MESSAGE MAY CONTAIN CONFIDENTIAL, PRIVILEGED OR OTHER LEGALLY PROTECTED
INFORMATION. IT IS INTENDED FOR THE ADDRESSEE ONLY. IF YOU ARE NOT THE
ADDRESSEE (OR SOMEONE THE ADDRESSEE AUTHORIZED TO RECEIVE THIS MESSAGE),
YOU ARE PROHIBITED FROM COPYING, DISTRIBUTING OR OTHERWISE USING IT. PLEASE
NOTIFY THE SENDER AND RETURN IT AT OUR COST. THANK YOU.
From: Matt Rutkowski [mailto:]
Sent: Thursday, February 03, 2011 3:48 PM
To: Anil Saldhana
Cc: id-cloud
Subject: Re: [id-cloud] Meetings in February (Use Case Discussion)
Anil,
My thoughts...
Firstly, we should only schedule for review those use cases that are submitted
in the template format. Perhaps we need to provide a February deadline
for this as part of the understanding that Feb. could be used by submitters
to update their already submitted use cases?
For reviewing purposes, we need to likely schedule additional (dedicated)
use case only review meetings (some of which can extend from our regular
meetings), With a rough ave. estimate of 1/2 hour per use case (set)
it is likely we need to plan for 4 hours of additional meetings.
As for email... this method has not proved effective in getting constructive
comments on existing use cases nor to get additional use cases created
for sparsely represented categories. In addition, many "templated"
use cases likely need help towards normalization (the template only does
so much in providing guidance).
Kind regards,
Matt
Anil Saldhana <>
02/03/2011 11:27 AM
To
id-cloud <>
cc
Subject
[id-cloud] Meetings in February (Use Case Discussion)
Hi All,
just got out of Blizzard in Chicago - maybe 25inches of snow on
ground (or more). Please pardon my absence over the list amidst the
flow of new use cases from members. Thank you so much for the
submissions. :)
While we have the new use cases, it poses a new problem for us. How
can
we accommodate discussions of all these new submissions during our
regular meetings?
Options:
* Extend our TC calls by 30mins in the month of February and accommodate
short discussion of all submissions.
* Discuss the use cases over email and summarize during meetings.
Please suggest or choose.
Regards,
Anil
---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that
generates this mail. Follow this link to all your TCs in OASIS at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
