DoD Architecture Framework Version 1.0, Volume 2 - AcqNotes.com

More documents

Recommendations

Info

4.7.3 Logical Data Model (OV-7) – Data Element DefinitionsTable 4-9 describes the architecture data elements for OV-7.Table 4-9. Data Element Definitions for Logical Data Model (OV-7)Data Elements Attributes Example Values/ExplanationGraphical Box TypesEntity Type*Name*Name of the type of person, place, thing, or message ofinterestGraphical Arrow TypesRelationship Type*Category RelationshipTypeNon-graphical TypesAttribute TypeData Model RuleData DomainReferenced TypesRuleStandardRelationshipsEntity Type is Described byAttribute TypeRelationship Type isDescribed by AttributeTypeDescription*ReferenceName*Description*Source Entity Type Name*Target Entity Type Name*Cardinality Designation*NameDescriptionSource Discriminated EntityType NameDiscriminant Attribute TypeNameNumber of DiscriminantValuesNameDefinitionReferenceNameTypeTextNameDescriptionRange ConstraintSize ConstraintEntity Type NameAttribute Type NameRole of AttributeRelationship Type NameAttribute Type NameTextual description of the entity typeReference to accepted definition of entity, if one exists(e.g., DDDS reference)Name/identifier of the relationship typeTextual description of the relationship representedName of the entity type at the source of the relationshipName of the entity type at the target of the relationshipExamples: one to one, one to many, etc.Name of the subtyping relationshipTextual description of the subtype relationshiprepresentedName of the supertype that is the source of therelationshipName of the attribute type that provides the discriminantfor the entity type (should be an attribute associated withthe entity)Number of different subtypes (if known)Name of attribute typeDefinition of attributeReference to accepted definition of attribute, if one exists(e.g., DDDS reference)Name/identifier of ruleExamples: Null rule; child delete rule, child update ruleText of ruleName of data domainTextual description of data domainValue range allowable for attributes in data domainMaximum number of characters in display representationSee OV -6a Definition TableSee TV-1 Definition TableName of entity typeName of an associated attribute typeFor example: Key, Foreign Key, Non-KeyName of a relationship typeName of an associated attribute type4-64
Data Elements Attributes Example Values/ExplanationData Domain ConstrainsValues of Attribute TypeRelationship Type has RuleEntity Type Has RuleAttribute Type has RuleData Model Rule isAssociated with aStructural Assertion TypeRuleCategory RelationshipType has DestinationEntity TypeEntity is Related toInformation Element*Entity is Related toOperational Activity I/OInformation*Data Model Conforms toData Modeling StandardData Domain NameAttribute Type NameRelationship Type NameRule NameEntity Type NameRule NameAttribute Type NameRule NameData Model Rule NameRule NameCategory Relationship TypeNameDestination Entity TypeNameDiscriminant ValueEntity Type Name*Information ElementIdentifier*Description of Relationship*Entity Type Name*Operational Activity I/OInformation Name*Description of Relationship*Data Model NameData Model Standard Name4.7.4 CADM Support for Logical Data Model (OV-7)Name of data domainName of attribute type whose values are selected from thedata domainName of a relationship typeName/identifier of a rule associated with that relationshiptypeSee OV -6a Data Element Definition TableName of an entity typeName/identifier of a rule associated with that entity typeName of an attribute typeName/identifier of a rule associated with an attributeName of a data model ruleName/identifier of a structural assertion type ruleassociated with a data model ruleName of subtyping relationshipName of entity type that is a subtypeValue of the discriminant attribute that is associated withthe entity subtypeName of an entity typeIdentifier of an information elementText description of the relationship between the entitytype and the information element (e.g., same, is subset of,contains)Name of an entity typeName of the information associated with an activity inputor outputText description of the relationship between the entity andactivity I/O (e.g., same, is subset of, contains)Name of data modelName of data modeling standard from TV-1Figure 4-32 provides a high-level diagram from the CADM showing key entities that areused to store architecture data for OV-7 in a CADM-conformant database. Each OV-7 isrepresented as an instance of LOGICAL-DATA-MODEL, a subtype of DOCUMENT. LOGICAL-DATA-MODEL cites a specific instance of CONCEPTUAL-DATA-MODEL (a subtype of INFORMATION-ASSET). The OV-7 use of the CONCEPTUAL-DATA-MODEL is limited to the relevant set of DoDdata standards from the Information Management View of the DoD Data Architecture (DDA)data model. The key entities in this specification include DATA-ENTITY, DATA-ATTRIBUTE, and4-65
Page 2 and 3:
SECTIONTABLE OF CONTENTSPAGE1 INTRO
Page 4 and 5:
SECTIONTABLE OF CONTENTS (Cont)PAGE
Page 6 and 7:
Page 8 and 9:
Page 10 and 11:
SECTIONANNEXTABLE OF CONTENTS (Cont
Page 12 and 13:
FIGURELIST OF FIGURES (Cont)PAGE4-1
Page 14 and 15:
FIGURELIST OF FIGURES (Cont)PAGE5-3
Page 16 and 17:
TABLELIST OF TABLES (Cont)PAGE5-13
Page 18 and 19:
Hereafter in this document, the ter
Page 20 and 21:
architecture that should be capture
Page 22:
2.1.2 Definition of the Systems Vie
Page 25 and 26:
The following legend is used in the
Page 27 and 28:
2.3 ARCHITECTURE DATA ELEMENTSAs st
Page 29 and 30:
Within each perspective, all produc
Page 31:
software systems, as well as for bu
Page 34 and 35:
Figure 2-5. CADM Distinctions for A
Page 36 and 37:
Tools and File Formats Used identif
Page 38 and 39:
Data Elements Attributes Example V
Page 40 and 41:
Data Elements Attributes Example V
Page 42 and 43:
• TASK and ARCHITECTURE-TASK (whi
Page 44 and 45:
3.2.2 TaxonomiesAV-2 defines the ar
Page 46 and 47:
TAXONOMY TYPES STRUCTURE AVOperatio
Page 48 and 49:
Taxonomies relate two instances, of
Page 50 and 51:
• INFORMATION-ELEMENT-DOCUMENT•
Page 52 and 53:
geographical distribution of assets
Page 54 and 55:
Data Elements Attributes Example Va
Page 56 and 57:
Figure 4-3. CADM ER Diagram for Hig
Page 58 and 59:
and their attributes (such as perio
Page 60 and 61:
GenericSubscriber NodeRequiringServ
Page 62 and 63:
Hierarchy ChartConnectorReferenced
Page 64 and 65: • Information content of IERs (or
Page 66 and 67: 4.3 OPERATIONAL INFORMATION EXCHANG
Page 68 and 69: 4.3.2 UML RepresentationThere is no
Page 70 and 71: DataElementsInformationExchange has
Page 72 and 73: • INFORMATION-EXCHANGE-REQUIREMEN
Page 74 and 75: AGREEMENT IDENTIFIER in INFORMATION
Page 76 and 77: Figure 4-10. CADM ER Diagram for Op
Page 78 and 79: WorkingGroupTop-LevelOrganizationCo
Page 80 and 81: 4.4.4 CADM Support for Organization
Page 82 and 83: OV-5 is a key product for describin
Page 84 and 85: Flow 1$A1Activity 1Node ANode CFlow
Page 86 and 87: ExternalSourceNode ANode BNode CNod
Page 88 and 89: Data Elements Attributes Example Va
Page 94 and 95: Threads of activities are specified
Page 96 and 97: • Action Assertions: These rules
Page 98 and 99: Table 4-6. Data Element Definitions
Page 100 and 101: model element. Behavior is modeled
Page 102 and 103: Processes receiving multiple inputs
Page 106 and 107: of the activities, and includes the
Page 108 and 109: Precedence linkindicatesorder betwe
Page 112 and 113: 4.7 LOGICAL DATA MODEL (OV-7)4.7.1
Page 116 and 117: DATA-DOMAIN (all subtypes of INFORM
Page 118 and 119: nodes. The term system in the frame
Page 120 and 121: second, logically distinct interfac
Page 122 and 123: Interface 1Node ASystem 1Node BSyst
Page 126 and 127: • ORGANIZATION-TYPE-ESTABLISHMENT
Page 128 and 129: 5.2 SYSTEMS COMMUNICATIONS DESCRIPT
Page 130 and 131: SV-2 intranodal perspective may be
Page 134 and 135: • NETWORK-DETAIL• NETWORK-NODE
Page 136 and 137: Figure 5-11. CADM ER Diagram for Sy
Page 142 and 143: FUNCTION 1SUBFUNCTION11SUBFUNCTION1
Page 144 and 145: The systems use cases and classes a
Page 148 and 149: used to identify an external source
Page 152 and 153: Operational ActivitiesSystem Functi
Page 158 and 159: InterfaceIdentifierDataExchangeIden
Page 162 and 163: Using these references, all the att
Page 164 and 165:
Figure 5-26. CADM ER Diagram for Sy
Page 166 and 167:
System NameHardware Element 1Mainta
Page 168 and 169:
Data Elements Attributes Example va
Page 170 and 171:
5.8 SYSTEMS EVOLUTION DESCRIPTION (
Page 172 and 173:
Page 174 and 175:
Page 176 and 177:
A template for SV-9 is shown in Tab
Page 178 and 179:
Page 180 and 181:
Page 182 and 183:
Page 184 and 185:
Because the structural assertion ru
Page 186 and 187:
Page 188 and 189:
terms of triggers or events (genera
Page 190 and 191:
Page 192 and 193:
Table 5-14. Data Element Definition
Page 194 and 195:
5.11 PHYSICAL SCHEMA (SV-11)5.11.1
Page 196 and 197:
Object classes defined here should
Page 198 and 199:
Figure 5-42. CADM ER Diagram for Ph
Page 200 and 201:
documents are used, then the relati
Page 202 and 203:
Table 6-2. TV-1 Template with Corre
Page 204 and 205:
Table 6-4. Data Element Definitions
Page 206 and 207:
Page 208 and 209:
Figure 6-3. INFORMATION-TECHNOLOGY-
Page 210 and 211:
Figure 6-5 provides a high-level di
Page 212 and 213:
6.2 TECHNICAL STANDARDS FORECAST (T
Page 214 and 215:
Page 216 and 217:
7 FRAMEWORK ARCHITECTURE DATA ELEME
Page 218 and 219:
• The Technical Standards Profile
Page 220 and 221:
• Events in the Operational State
Page 222 and 223:
• Rules in the Systems Rules Mode
Page 224 and 225:
7.6 SUMMARY OF ARCHITECTURE DATA EL
Page 226 and 227:
LINK TO… BY:SV-4 System data flow
Page 228 and 229:
ANNEX AGLOSSARYA&IA&TACCACLAFWGAMSA
Page 230 and 231:
FIPSFNAFOCFoSFPIFRPFSAGCCSGIGGUIHCI
Page 232 and 233:
OAOASDOIEMOMBOMGONCDOOOPLANOSDOVPMP
Page 234 and 235:
ANNEX BDICTIONARY OF TERMSThe terms
Page 236 and 237:
Initial CapabilitiesDocumentIntegra
Page 238 and 239:
SystemSystem Data ElementAny organi
Page 240 and 241:
AssociationAttributeBuildingBlocksC
Page 242 and 243:
NotesObjectObject DiagramOperations
Page 244 and 245:
Use Case Model A model that describ
Page 246 and 247:
COST-BASISCOUNTRYDATA-ITEM-TYPEDECI
Page 248 and 249:
NETWORK-TYPENODEMODELING-AND-SIMULA
Page 250 and 251:
INTERFACE-TYPETECHNICAL-SERVICETECH
Page 252 and 253:
[DEB, 2000][DeMarco, 1979][Departme
Page 254:
[OMG, 2000][OMG, 2001][Rumbaugh, 19
show all

DoD Architecture Framework Version 1.0, Volume 2 - AcqNotes.com

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?