Re: [soa-eerp] I048: Use Case Document and additional justification

[William Cox <wtcox@CoxSoftwareArchitects.com>]

I think this should be addressed by creating a folder for Use Cases and Models as a placeholder, and starting with several of the contributions. Closing this issue is OK, need to open new one for that new document.

bill cox
--

William Cox
Email: wtcox@CoxSoftwareArchitects.com
Web: http://www.CoxSoftwareArchitects.com
+1 862 485 3696 mobile
+1 908 277 3460 fax

eerp_sy@changfeng.org.cn wrote:

380-22009632435354331@M2W032.mail2web.com" type="cite">

Same as Issue I052, it is proposed to change the protocol of this issue to: 

Protocol: examples

Artifact: example 

Type: design 

That is the issue to be addressed in the Example document. No spec changes
are required on this issue for now. 



Szu Chang 

Original Message:
-----------------
From: eerp_sy@changfeng.org.cn eerp_sy@changfeng.org.cn
Date: Sun, 21 Jun 2009 15:39:09 -0400
To: wtcox@coxsoftwarearchitects.com, soa-eerp@lists.oasis-open.org
Subject: [soa-eerp] I048: Use Case Document and additional justification


Issue # I048

The protocol change to "examples" 

Original Message:
-----------------
From: William Cox wtcox@CoxSoftwareArchitects.com
Date: Sat, 20 Jun 2009 22:43:19 -0400
To: soa-eerp@lists.oasis-open.org
Subject: [soa-eerp] NEW Issue: Use Case Document and additional
justification


PLEASE DO NOT REPLY TO THIS EMAIL OR START A DISCUSSION THREAD UNTIL THE 
ISSUE IS ASSIGNED A NUMBER.

The issues coordinators will notify the list when that has occurred.

Protocol: bqos rating sla

Artifact: spec

Type: design

Title: Use Case Document and additional justification

Description:

This issue applies to
BusinessQualityOfService-v1.0-spec-wd04.pdf
BusinessRating-v1.0-spec-wd05.pdf
BusinessServiceLevelAgreement-v1.0-spec-wd04.pdf

On reading all three specifications together, it's not clear what the 
relationships are and the intended use cases.

A use case document would help described the intended usage and 
approach, and clarify issues I've separately raised..  In particular, 
the justification for the mechanisms in the three current 
specifications, and a large integrated example, would be very useful.

This issue may be addressed after the current Committee Draft in 
progress is completed, but would help the public review be more 
effective if addressed before Public Review.

Related issues:

Proposed Resolution:

Write a use case and relationships/background document. This could be a 
non-normative white paper, or could coordinate with the information from 
the non-normative sections (to be written) for the three specifications. 
I think that a single use case and relationships document would be best.


bill cox
--
*William Cox*
Email: wtcox@CoxSoftwareArchitects.com 
<mailto:wtcox@CoxSoftwareArchitects.com>
Web: http://www.CoxSoftwareArchitects.com
+1 862 485 3696 mobile
+1 908 277 3460 fax



--------------------------------------------------------------------
mail2web.com – Enhanced email for the mobile individual based on Microsoft®
Exchange - http://link.mail2web.com/Personal/EnhancedEmail



---------------------------------------------------------------------
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 



--------------------------------------------------------------------
mail2web.com - Microsoft® Exchange solutions from a leading provider -
http://link.mail2web.com/Business/Exchange