[regrep-cc-review] Core Components/Registry Functional Points Mapping

Title: Core Components/Registry Functional Points Mapping

Hi All,

In advance of our Wednesday call, I thought I'd share with you some of the work I've done to date on the functional mapping, as a potential point of reference.  The attached document is a first cut at the Discovery and Submissions sections of the CC spec v1.75 (pp.17-29).  Please note the following:

I've added a "Point #" column to the left - just a sequential number that we can refer to in discussions (please feel free to add to your versions as well)

I created entries only for those places that specifically referenced the Registry.  For instance, on p.20 bottom there is the following point:  "Document the context(s) of the business process being analysed.  Identify what is applicable for each category of context,...".  This point is an instruction to the user, and does not involve the Registry.  Therefore, it was not included in the functional points document.

I did not break sentences up (we can change this if we'd like).  For example, the following sentence - "The resulting MIG, DTD or Schema is submitted to the repository where it is associated with the Business Information Entities it represents" - is really 2 points:  (1) The resulting MIG, DTD or Schema is submitted to the repository, and (2) it is associated with the Business Information Entities it represents.

Some point are duplicate (ex: #20 and #21) - I decided to include both of these (at least for now) and will probably list "DUPLICATE OF #20" in notes for #21

I look forward to talking about our next steps during our call - i.e. how do we go about mapping these function points to our Registry architecture?  Some will certainly be covered by the current architecture - but for those that are not, should we:

        (1) Work only within our subcommittee to determine how the Registry architecture can be updated, or

        (2) Take a first cut within the subcommittee and then escalate to TC for ideas over list-serve, or

        (3) Escalate to TC immediately for ideas over list-serve

Please give these some thought if you have a chance between now and our call.

Thanks,

Joe

 <<CC Spec-Registry Functional Points - DISCOVERY-SUBMISSION.doc>> 

**************************************************************************

  Joseph M. Chiusano

  Logistics Management Institute

  2000 Corporate Ridge

  McLean, VA 22102

  Email: 

  Tel: 571.633.7722

**************************************************************************

CC Spec-Registry Functional Points - DISCOVERY-SUBMISSION.doc