ML20198N999
| ML20198N999 | |
| Person / Time | |
|---|---|
| Issue date: | 12/30/1998 |
| From: | Compton E NRC OFFICE OF NUCLEAR MATERIAL SAFETY & SAFEGUARDS (NMSS) |
| To: | Schmit M NRC OFFICE OF NUCLEAR MATERIAL SAFETY & SAFEGUARDS (NMSS) |
| References | |
| SSD, NUDOCS 9901060270 | |
| Download: ML20198N999 (3) | |
Text
December 30, 1998 e
'[ -
MEMORANDUM TO:
Matt Schmit PMDA FROM:
Eric Compton, Engineering Aide (orig, signed by)
Materials Safety Branch, INMS
SUBJECT:
COMMENTS OF NRC DATA ARCHITECTURE NAMING STANDARDS AND CONVENTIONS DOCUMENT IMNS has reviewed the document, in response to Francine Goldberg's memorandum dated December 15,1998. Please find attached our comments concerning this document. This closes IMNS Ticket 199800617.
If you have any questions, please contact me at 415-5799 or Mr. John Jankovich at 415-790f
Attachment:
As stated NMSS199800617 Distribution:
IMNS r/f NE02-SSD-7 CPoland NMSS r/f CEstep Closes IMNE 199800617 NRC Central File DOCUMENT NAME: H:\\ERIC\\ MISC \\lMNS0617 T* receive a copo of this document. Indcate in the box: "C" = Copy without attachment / enclosure "E" = Copy with attachment / enclosure
'N' = No copy OFFICE MSB l< MSB LS,
C l
NAME ECompton f c <
CRa$th J-K DATE 12/.50/98 12/?J/98 i OFFICIAL RECORD COPY 9901060270 981230 PDR RC l
SSD PDR
_, v
, _,,_.M'
1 1
l [
ATTACHMENT 1
Comments Concerning NRC Data Architecture Naming Standards and Convention Document 1.
The document is very confusing, especially for those without an understanding of data structures. Examples, throughout the document proved helpful, however, more could be used.
2.
The Table of Contents indicated Appendices A-D, however only appendices A and B were present in our copy of the document.
3.
Page 1-3, please define and/or distinguish between " logical view" and " physical view" conceming a Relational Table. Perhaps these are (or should be) defined in the Glossary (Appendix D) which we did not have.
4.
Page 3-1/2, last/first bulleted items (and throughout t.0cument) snould be changed, to avoid name ambiguity:
Possessive nouns will not be used as the entit? name.
)
Proper nouns may be used in the entity name if generally accepted.
5.
Page 3-2, second bulleted item (and throughout document) should be changed.
Throughout document this text is stated, with slight variations:
Allowable characters are uppercase letters A-Z and the space character. Punctuation marks, or special characters, including the slash (/), the hyphen (-), and the underscore
(_.) are not allowable characters. Numerals 0-9 are allowable but must be authorized by the NRC Corporate Data Model Administrator. The first character must be a letter.
6.
Page 3-2, no limitation was given as to the maximum length of the " Entity Description",
j as was for the " Entity Name" (28 characters).
7.
Page 3-2, last bulleted item: Please note the difference between " business rules",
"information processing rules" or " physical consideration". Perhaps these are (or should be) defined in the Glossary (Appendix D) which we did not have.
8.
Page 3-3, The table indicates an Entity Type of " Associative Entity", while the corresponding Section 3.1.4 is titled " Associative Entity or Intersecting Entity". We suggest adding either "or Intersecting Entity" to above table or removing it from Section heading (s), for consistency.
9.
Page 3-6, Section 3.1.8, " Class terms" are first discussed here, but only defined in j
Ap; andix A. Class Term should also be defined in this section.
10.
Page 3-8, first bulleted item, For lookup tables, only one method should be used: either "T" or *LOOK"; having both will be redundant.
l 1
I
... ~.. -.
F L, '
l*.
11.
Page 3-9, Section 3.2 Process Objects (and other incidences), Please define what the CASE tool is or will be.'
12.
Page 3-9, Section 3.2.1 Process, An appendix should be included listing valid process l
names for consistency.
- 13.
Page 3-10, second bulleted item: I believe that there is a typo here.: NCR should be changed to NRC.
14.
Page 3-10, Section 3.2.2 Data Flow, " entity" should be used instead of " noun" here.-
15.
Page 3-11, first bulleted item: There should be an appendix listing valid Data Flow modifiers for consistency.-
.16.
Page 3-11, Section 3.2.3 Data Store, states data store name consists of a noun that may be preceded by modifiers. Again, " entity" should be used instead of " noun" Format then should be changed to:
Format:
S (0-1) Modifiers Entity (Noun) 17.
Page 3-12, bulleted item 8 should be changed,since it appears urging the use of acronyms in bulleted items 6 and 9:
Use complete name if abbreviation is not common and within the limitation.
18.
. Page 4-4, Section 4.4 Data Type: It would be helpful to have some examples of data types.
I l
e I
l l
2
.