[regrep-cc-review] Functional Points Mapping with Notes

["CHIUSANO, Joseph" <JCHIUSANO@lmi.org>]

Title: Functional Points Mapping with Notes

Hi All,

At our last call I mentioned that I would go ahead and take a cut at filling in the "Notes" column of the functional points mapping for Discovery/Submission - please see attached:

<<CC Spec-Registry Functional Points - DISCOVERY-SUBMISSION.doc>>
Please note regarding this document:

• I prefaced each of the Functional Point #'s (leftmost column) with "FP" - the reason for this will become clearer when I reference Requirements (further below)



• Each "notes item" is essentially a point (different use of term than above) derived from the Functional Point description - i.e. each can be thought of as a requirement derived from the functional point.  Ex: "Need to store BIE's".



• I provided a letter for each of the points in the Notes column - this will make it easier for discussion during calls and e-mail; i.e. can refer to "note FP1a, note FP5b, etc."



• For category codes ("Category" column), I provided a separate code for each of the notes (in cases where there was more than one note for a Functional Point) - the letters in the Category column correspond directly to the items in the Notes column.  This will become clear once you see the document.



• I created another category code "DUP", for those Functional Points that are duplicates of other Functional Points.  For these I simply entered "Duplicate of FPx" in Notes column.



• There are some questions in the Notes, such as "How to register re-use of ACC as ABIE in Registry".  I hope that for each of these we can discuss them as a subcommittee (through calls and e-mail) - and for those that we cannot resolve, we can bring them to the eBTWG folks.  These are given a category code of "D" (Discussion/research required)



• At the very bottom, I removed the information from the category codes description that was in ()'s - ex: (provide specifics in Notes) from the category code "C" description.  The reason will become clearer below (please see "What I envision beyond this") - but essentially I think that it is sufficient for the Functional Points Mapping document to simply specify that the functionality is covered, and expand on this in a separate document.

I'd like to discuss the above "techniques" that I used at our next call, to see if everyone feels that they make sense for us to use going forward.  As always, please feel free to provide feedback in the meantime.

What I envision beyond this:

As you know, we will come out of the functional points mapping with a set of "notes items", each of which will have an associated category code.  Here is how I envision us handling each category code (most of the codes are covered here):

• "C" (Covered in Registry architecture) - place in an "Already Covered" summary document, in which we will elaborate on how the functionality is already covered



• "U" (Update the Registry architecture required) - place in an "Updates Required" requirements document, in which we will elaborate on how the Registry architecture should be updated.  These documents (a total of 3, or we can combine all sections into one) will provide a basis for the creation of the document we will be creating for the full TC to review.  I envision this document tying requirements to the FP numbers so there is traceability back to the Functional Points document.  This will be helpful in case a Functional Point changes in the CC spec - we can trace the change to the requirement to see if it is affected.  As a sample, I've extracted all of the "U" notes items from the Functional Points mapping document attached above, and created a corresponding entry for each in the attached Requirements document with the FP number listed:

<<CC Spec-Registry Requirements - DISCOVERY-SUBMISSION.doc>>

• "D" (Discussion/research required) - as mentioned earlier, those notes items that we cannot resolve within the subcommittee can be placed on a master "eBTWG question" list

Regards,
Joe

**************************************************************************
  Joseph M. Chiusano
  Logistics Management Institute
  2000 Corporate Ridge
  McLean, VA 22102
  Email: jchiusano@lmi.org
  Tel: 571.633.7722
**************************************************************************

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

CC Spec-Registry Requirements - DISCOVERY-SUBMISSION.doc