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

More documents

Recommendations

Info

ExternalSourceNode ANode BNode CNode DExternalDestinationFlow 1Activity1.1Activity1.3Activity1.2Flow 2Activity2.1Activity2.2Flow 3Activity3 Flow 4Figure 4-17. UML Activity Diagram for Operational Activity Model (OV-5) – TemplateThe activities in the activity diagram must correspond to and provide detail for the usecases (operational activities of OV-5) appearing in the related use case diagram(s) to ensuremodel consistency. Objects used to define activity diagram swimlanes must also correspond tothe actors in related OV-2 collaboration diagrams (the same actors as in the related OV-5 usecase diagrams).4.5.3 Operational Activity Model (OV-5) – Data Element DefinitionsTable 4-5 describes the architecture data elements for OV-5.Table 4-5. Data Element Definitions for Operational Activity Model (OV-5)Data Elements Attributes Example Values/ExplanationGraphical Box TypesOperational Activity*Graphical Arrow TypesHierarchy ChartConnectorFlow Connector*Name*Level identifierDescription*ReferencesOperational ActivityCostParent OperationalActivity*Child OperationalActivityName*Type*Name of activityIf using hierarchical decomposition of activities: Identifier thatcorresponds to the activity’s place in the activity hierarchy –should be uniqueDescription of the activityAny policy or doctrine references that provide further explanationof the activityCost for activity derived from or used in activity-based costanalysisName or level identifier of an activity that has a decompositionName or level identifier of child (i.e., subordinate) activity(For process-oriented models)Label of connector on graphicIf using IDEF0: One of Input, Output, Control, Mechanism4-36
Data Elements Attributes Example Values/ExplanationFor Input/Output FlowConnector*Source*Name of source activity or ExternalFor subtype ControlFor subtype MechanismNon-graphical TypesCapabilityModelDiagramFacing Page TextOperational Activity I/OInformation*Referenced TypesOperational Node*Information Exchange*Human RoleSystemSystem FunctionRelationshipsCapability is Related toOperational ActivityOperational Activity I/OInformation isAssociated With anInformation ExchangeOperational Activity isPerformed byOperational Node*Destination*Operational ActivityI/O InformationName*SourceDestinationControl DescriptionSourceDestinationResource typeNameDescriptionNameTypePurposeViewpointTitleDiagram NumberIdentifierTextName*Content*CapabilityOperational ActivityOperational ActivityI/O Information NameInformationExchange IdentifierOperational ActivityName*Name of destination activity or ExternalName of the information associated with the flow(for IDEF0 models, if any)Name of source activity or ExternalName of destination activityDescription of the control information(for IDEF0 models, if any)Name of source activity, if relevant, otherwise N/AName of destination activityType of resource represented: operational node, systems node, orsystemMay be defined in terms of the attributes required to accomplish aset of activities in order to achieve a given mission objective;capability-related attributes may be associated with specificactivitiesName of capabilityDescription of the capabilityName /identifier of operational activity modelOperational activity hierarchy, IDEF0-style model, object-oriented,or other type of modelPurpose of modelViewpoint of modelTitle of diagram/graphicLevel number of diagram (for leveled families of diagrams)Identifier/title of a page of textText description of the content of a graphic/diagram and itsconstituent partsName of input or output information for an activityThe information content (information that is input or output by theactivity)See OV -2 Definition TableSee OV -3 Definition TableSee OV -4 Definition TableSee SV -1/2 Definition TableSee SV-4 Definition TableName or identifier of a capabilityName or identifier of an operational activity(Information produced or consumed by an activity may beassociated with multiple information exchanges)Name or label of information that is an input or output of anactivityIdentifier for an associated information exchange (from OV -3)Name/identifier of an operational activity4-37
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 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 114 and 115: 4.7.3 Logical Data Model (OV-7) - D
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 138 and 139:
5.3.2 UML RepresentationThere is no
Page 140 and 141:
Page 142 and 143:
FUNCTION 1SUBFUNCTION11SUBFUNCTION1
Page 144 and 145:
The systems use cases and classes a
Page 146 and 147:
Data Elements Attributes Example Va
Page 148 and 149:
used to identify an external source
Page 150 and 151:
Page 152 and 153:
Operational ActivitiesSystem Functi
Page 154 and 155:
5.5.2 UML RepresentationThere is no
Page 156 and 157:
Figure 5-24. CADM ER Diagram for Op
Page 158 and 159:
InterfaceIdentifierDataExchangeIden
Page 160 and 161:
Page 162 and 163:
Using these references, all the att
Page 164 and 165:
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

Create successful ePaper yourself

Delete template?

Save as template?