OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

provision message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]

Subject: [provision] General Use Case Comments

Firstly, again many thanks to Gavenraj and Yoav for pulling this draft together.  Often the hardest thing to do is make the first move.  Before analyzing each use case, I have the following general “global” comments:


1.     I propose we try where ever possible to avoid using the word account in use cases unless we are describing an exercised use case (“… and example being the creation of an account on NT…”).  Our charter does not restrict provisioned to accounts.  I do not have a better suggestion than maybe just using the term “data”.  If everyone finds this objectionable then we could simple add words to the glossary for account.

2.     I propose we change the titles of each use case to include a categorization of RA-PSP or PSP-PST. Use case 1 would thus become (considering 3 below) “PSP-PST Add Data”.

3.     I propose we settle on common wording for all use case titles to reflect the nature of the use case operations (wherever possible).   Back in my days as a DBA we used the term CRUD to summarize data operations (Create Read Update Delete ;-)  I’m not fixed on the term, just that when we are talking about a delete (say de-provision) we constantly include this in the UC.

4.     Many of the pre-conditions mention “knowledge of self”.  Could you please explain what this means



Darran Rolls  
MSIM  drolls_waveset@hotmail.com
AIM    drollswaveset
YIM    drolls_waveset


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]

Powered by eList eXpress LLC