adelsone's picture
From adelsone rss RSS  subscribe Subscribe

Lecture_4.4-DoDAF_Ov.. 

Lecture_4.4-DoDAF_Ov..

 

 
 
Tags:  architecture  information technology architecture  enterprise architecture repository 
Views:  197
Published:  November 24, 2011
 
0
download

Share plick with friends Share
save to favorite
Report Abuse Report Abuse
 
Related Plicks
Knotion Consulting

Knotion Consulting

From: baback
Views: 255 Comments: 0

 
Architecture Consulting

Architecture Consulting

From: bndid
Views: 364 Comments: 0
Architecture Consulting
 
5-1 CHAPTER 5 IT ARCHITECTURES

5-1 CHAPTER 5 IT ARCHITECTURES

From: atlaso
Views: 250 Comments: 0
5-1 CHAPTER 5 IT ARCHITECTURES
 
See all 
 
More from this user
Sales & Business Development in Finance and Technology

Sales & Business Development in Finance and Technology

From: adelsone
Views: 176
Comments: 0

GNW 2004AR ir

GNW 2004AR ir

From: adelsone
Views: 617
Comments: 0

DecisionDirector System Assessment

DecisionDirector System Assessment

From: adelsone
Views: 118
Comments: 0

Mac Fotorettung

Mac Fotorettung

From: adelsone
Views: 191
Comments: 0

Julian Peachment Coversations

Julian Peachment Coversations

From: adelsone
Views: 618
Comments: 0

[Finance]Insurance Companies Set To Pay Out More Frequently[16144]

[Finance]Insurance Companies Set To Pay Out More Frequently[16144]

From: adelsone
Views: 472
Comments: 0

See all 
 
 
 URL:          AddThis Social Bookmark Button
Embed Thin Player: (fits in most blogs)
Embed Full Player :
 
 

Name

Email (will NOT be shown to other users)

 

 
 
Comments: (watch)
 
 
Notes:
 
Slide 1: Lecture 4.4: DoDAF Overview (Vol. II, Chs 1 & 2) Dr. John MacCarthy UMBC CMSC 615 Fall, 2006 1
Slide 2: Agenda  Overview 2
Slide 3: Overview (1.1) and Purpose (1.2)  DoDAF provides a “common approach for DoD architecture description development, presentation, and integration”  Supports Requirements Development    Complete Consistent Allocated to Components Complete Consistent Meets Requirements  Supports Design Development     Definitions  Architecture refers to both:   An architecture description An architecture implementation    Architecture Description is “a representation of a defined domain … in terms of constituent parts, what those parts do, how the parts relate to each other and to the environment and the rules and constraints governing them” Architecture Implementation is “a real implementation of capabilities and assets in the field” Integrated Architecture is “an architecture description that ahs integrated OVs, SVs and TVs” 3
Slide 4: Architecture Views (2.1)  The Framework defines three views:      “All View (AV)” products are those provide overarching information describing the architecture plans, scope, and definitions Operational View (OV): describes tasks, activities, operational elements, and information exchanges required to accomplish DoD Missions, i.e., “enterprise” mission aspects. System View (SV): describes systems and interconnections providing for, or supporting, DoD functions. It associates systems resources to the OV. Technical Standards View (TV): provides the technical systems implementation guidelines upon which engineering specifications are based, common building blocks are established, and product lines are developed, e.g., policies and technical standards. Each View is composed of sets of architecture data elements that are depicted via graphic, tabular, and textual products. The Core Architecture Data Model (CADM) defines the entities and relationships for architecture data. DoDAF recognizes that the term “Architecture” is overloaded. As such, it divides the term into different views and products (for each view).   4
Slide 5: Architecture Products (2.2) 5
Slide 6: Architecture Products (2.2): All Views, Operational Views and Technical Views Applicable View All Views All Views Operational Operational Operational Operational Operational Operational Operational Operational Operational Technical Technical Framework Product AV-1 AV-2 OV-1 OV-2 OV-3 OV-4 OV-5 OV-6a OV-6b OV-6c OV-7 TV-1 TV-2 Framework Product Name Overview and Summary Information Integrated Dictionary High-Level Operational Concept Graphic Operational Node Connectivity Description Operational Information Exchange Matrix Organizational Relationships Chart Operational Activity Model Operational Rules Model Operational State Transition Description Operational Event-Trace Description Logical Data Model Technical Standards Profile Technical Standards Forecast General Description Scope, purpose, intended users, environment depicted, analytical findings Architecture data repository with definitions of all terms used in all products High-level graphical/ textual description of operational concept Operational nodes, connectivity and information exchange needlines between nodes Information exchanged between nodes and the relevant attributes of that exchange Organizational, role, or other relationships among organizations Capabilities, Operational Activities, relationships among activities, inputs and outputs. Overlays can show cost, performing nodes, or other pertinent information One of the three products used to describe operational activity— identifies business rules that constrain operation One of three products used to describe operational activity— identifies business process responses to events One of three products used to describe operational activity— traces actions in a scenario or sequence of events Documentation of the system data requirements and structural business process rules of the Operational View. Listing of standards that apply to systems view elements in a given architecture Description of emerging standards and potential impact on current systems view elements, within a set of timeframes 6
Slide 7: Architecture Products (2.2): Systems Views Applicable View Systems Systems Systems Systems Systems Systems Systems Systems Systems Systems Systems Systems Systems Framework Product SV-1 SV-2 SV-3 SV-4 SV-5 SV-6 SV-7 SV-8 SV-9 SV-10a SV-10b SV-10c SV-11 Framework Product Name Systems Interface Description Systems Communications Description Systems-Systems Matrix Systems Functionality Description Operational Activity to Systems Function Traceability Matrix Systems Data Exchange Matrix Systems Performance Parameters Matrix Systems Evolution Description Systems Technology Forecast Systems Rules Model Systems State Transition Description Systems Event-Trace Description Physical Schema General Description Identification of systems nodes, systems, and system items and their interconnections, within and between nodes Systems nodes, systems, and system items, and their related communications lay-downs Relationships among systems in a given architecture; can be designed to show relationships of interest, e.g., system-type interfaces, planned vs. existing interfaces, etc. Functions performed by systems and the system data flows among system functions Mapping of systems back to capabilities or of system functions back to operational activities Provides details of system data elements being exchanged between systems and the attributes of that exchange Performance characteristics of systems view elements, for the appropriate timeframe(s) Planned incremental steps toward migrating a suite of systems to a more efficient suite, or toward evolving a current system to a future implementation Emerging technologies and software/hardware products that are expected to be available in a given set of timeframes, and that will affect future development of the architecture One of three products used to describe systems functionality— identifies constraints that are imposed on systems functionality due to some aspect of systems design or implementation One of three products used to describe systems functionality— identifies responses of a system to events One of three products used to describe systems functionality— identifies system-specific refinements of critical sequences of events described in the operational view Physical implementation of the Logical Data Model entities, e.g., message formats, file structures, physical schema 7
Slide 8: Architecture Data Elements (2.3)    Architecture Data Elements (ADEs) are the underlying basic elements that comprise the architecture (examples will be provided later) These ADEs are captured in the a Architecture Data Model that is specific to each AV, OV, SV, or TV graphics (examples will be provided later) The All-DoD Core Architecture Data Model (CADM) specifies the ADE fields for each View 8
Slide 9: Architecture Product Development (2.4)      Supports both Structured Analysis (IDEF) and UML methodologies Most products may be decomposed to multiple levels Decomposition should be to the level required for the stated objective (user) Products should be developed iteratively (per SE Process) Templates should be developed 9
Slide 10: Integrated Dictionary Legend  Entry Types:         Reference ID:           Operational Node (ON) Operational Element (OE) System (Sys) Subsystem Element (SE) Actor (Actor) External System (ES) External Subsystem Element (ESE) Function/Activity (Fnc) Rule Model (RM) State (State) Data Entity (DE) Data Attribute (DA) Function/Activity: A1.X.y System/Subsystem Element: C1.X.y External System/Subsystem Element: ESX.Y Rule Model: RM1.X.y Data Entity (DE): DEX.y    Acronym Term Definitions      Functions should indicate I/O Des and Rule Models System/Subsystem Elements should include alllocated Functions DEs should include list of DAs DAs should include data type, visibility, and ranges. RMs should include reference to functions and DEs 10
Slide 11: AV-2: Integrated Dictionary WBRS Example Type System Ops Node Ops Node Reference Acronym Term Number S0 WBRS Web-Based Registration Sytem ON 1 University ON 2 User Registrar Definition The System that provides web-based registration capabiltity. The University consists of the Registrar and the WBRS The Users of the WBS consist of Students and Faculty. The User provides Input_Login (DE3.3) The body responsible for maintaining Account Information (DE 2), Course Information (DE 7), Student Information (DE 8), and Registration Data (feed by DE Z). Ops Element OE 1.2 Function Function Function Data Entity Data Entity A0 A1 A1.1 DE 1 DE 10 Provide Web-Based Highest level function in the WBRS functional heirarchy. Registration System Provide Student Services Provides the WBRS services to students. Provide Student Menu University Policy Student Registration Update Permits the student to select a student service. A set of rules for Security, Registration, and Prerequisite Waivers, that reflect University Policies. This message contains the student's registration information (All its attributes are defined in other Data Entities). When valid, it is sent to the University Server to update the Registrar's Database. An indication of the Type of account that the user has based on the UserID. This determines what services are provided. Unique ID number for each student Unique ID number for each faculty Indicates that there was an error in the information provided. Student input to the CourseID (see DE4.1) Data Attrib Data Attrib Data Attrib Data Attrib Data Attrib State Transition State Transition Rule Model DA2-2 DA2-4 DA2-5 DA2-6 DA3.1-1 S12.1 S12.2 AccountType StudentID FacultyID ErrorStatus CourseIDInput Displaying Student Menu This State Transition provides the Man-Machine interface to the student. Waiting This State Transition provides a non-operational state for the system while it is waiting for input This rule-model provides the student the ability to register for classes. R.1.4 Provide Registration Services 11
Slide 12: Conclusions    AV-1 and AV-2 are essential products for every architecture AV-1 is usually developed in a Word document Initially one may want to develop the AV-2 in Word or Excel until you figure out the desired format or until a CASE Architecture Tool is selected. 12

   
Time on Slide Time on Plick
Slides per Visit Slide Views Views by Location