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

More documents

Recommendations

Info

Precedence linkindicatesorder betweenUOBsJunction, showsdecisionlogic (alternatepaths)UOBCustomerCustomerConfirmsReservation2.1.1Customer CareOperationalNode orSwimlaneCheckReservation Details2.1.2A114XReserve Room2.1.5A213Take PaymentDetailsXSend Confirmationto Client2.1.6A414Go-to/Release RoomOV-5ActivityReferenceNumberAnnotation2.1.3A311Inform ClientPayment Invalid2.1.7A414AccountsCheck PaymentDetails2.1.4A3114.6.12 UML RepresentationFigure 4-28. Operational Event-Trace Description (OV-6c) – IDEF3 ExampleUML sequence diagrams may be used to model OV-6c (see section 4.6.11 for adescription and Figure 4-28 for a template).The objects appearing as lifelines in OV-6c are instances of the actors appearing in theuse case diagrams of OV-5. They map to the same instances depicted in OV-2 collaborationdiagram. Objects (actor instances) referenced in the sequence diagrams should also be traceableto class diagrams of OV-4.4.6.13 Operational Event-Trace Description (OV-6c) – Data Element DefinitionsTable 4-8 describes the architecture data elements for OV-6c.Table 4-8. Data Element Definitions for Operational Event-Trace Description (OV-6c)Data Elements Attributes Example Values/ExplanationGraphical Box TypesLifeline or Swimlane*Name*Name of the lifeline or swimlaneDescription*Text description of any assumptions or scope constraints on theOperational ActivityGraphical Arrow TypesEvent*Name*Description*Originating NodeName*Terminating NodeName*nodeIf using IDEF3; see OV-5 Definition Table (referred to as task inIDEF3)Event label or name of eventTextual description of eventName of node where event beginsName of node where event ends4-58
Data Elements Attributes Example Values/ExplanationLink If using IDEF 3NameName of linkDescriptionTextual description of linkTypeType of link - Temporal or LogicalOriginating Activity Name of activity where link beginsNameTerminating Activity Name of activity where link endsNameNon-graphical TypesOperational ThreadNameName /identifier of operational thread or scenarioTypeModel type used to develop operational thread (e.g., IDEF3-stylemodel, UML sequence diagram, or other type of model)Capability Name Name of capability that the operational thread supportsEvent Time*Identifier*Identifier for the time when an event stops or startsPosition On Lifeline* Relative position of event on lifeline (e.g., top-most or first,second, etc.)FormulaAlgebraic formula for calculating the time of event occurrence (i.e.,starting or stopping of the event) relative to beginning of nodelifelineReferenced TypesOperational Node*See OV -2 Definition TableInformation Exchange*See OV -3 Definition TableCapabilitySee OV -5 Definition TableAction*See OV -6b Definition TableEvent*See OV -6b Definition TableGuardSee OV -6b Definition TableRelationshipsDiagram RepresentsOperational ThreadDiagram Identifier Identifier of the diagram that represents the Operational ThreadOperational ThreadDefines CapabilityNode Lifeline (orSwimlane) isAssociated With anOperational Node*Event Starts at Time*Event Ends at Time*Event Originates FromLifeline*Operational ThreadNameOperational ThreadNameCapability NameNode Lifeline Name*Operational NodeName*Event Name*Starting Event TimeIdentifier*Event Name*Ending Event TimeIdentifier*Event Name*Originating LifelineName*Name of the operational thread or scenarioName of the operational thread or scenarioName of the capability that is enabled or defined by theoperational threadName of the node lifelineName of the operational node associated with the node lifelineLabel of the event on the graphicIdentifier of the time at which the event occurs or starts; gives therelative position of the event on its starting lifeline; may beidentical to the ending timeLabel of the eventIdentifier of the time at which the event ends; gives the relativeposition of the event on its ending lifeline; value of time should begreater than or equal to the value of the starting time, in terms oflifeline positionLabel of the event on the graphicName of the lifeline from which the event originates4-59
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 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 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 160 and 161:
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

Create successful ePaper yourself

Delete template?

Save as template?