Beruflich Dokumente
Kultur Dokumente
Terry Bahill Systems and Industrial Engineering University of Arizona terry@sie.arizona.edu copyright , 2004-09, Bahill
This file is located at http://www.sie.arizona.edu/sysengr/slides/
References
Bahill, A. T., Botta, R. and Daniels, J., The Zachman Framework Populated with Baseball Models, Journal of Enterprise Architecture, 2(4): 50-68, 2006. This paper is available at http://www.sie.arizona.edu/sysengr/publishedP apers/ZachmanBaseball.pdf Bahill, A. T., Botta, R. and Daniels, J., A systems engineering approach to organizing baseball models, keynote address at the AsiaPacific Congress on Sports Technology, Tokyo, September 11-14, 2005.
4/28/2014
2009 Bahill
Definitions
A model is a simplified representation of some view of a real system. A simulation is an implementation of a model, often on a digital computer.
4/28/2014
2009 Bahill
Example
This is a perfect model for the vertical movement of a major league fastball [Bahill does a demonstration here]* That is how long the pitch is in the air That is how far a fastball drops due to gravity It is a good model because The model is simpler than the real system It models only one aspect of the real system Vertical movement It illustrates that all models are not mathematical
4/28/2014 4 2009 Bahill
4/28/2014
2009 Bahill
4/28/2014
Philosophy
Experimentalists Mathematicians
Real System Modelers Good Modelers Model of Real System Modelers Good Modelers Computer Simulation of Model
4/28/2014
2009 Bahill
Kinds of models
Models of behavior Models of structure Models of physical properties Models for analysis
4/28/2014
2009 Bahill
Purpose of models
Guide decisions Understand or improve an existing system or organization Create a new design or system Control a system Suggest new experiments Guide data collection activities Allocate resources Identify cost drivers Increase return on investment Identify bottlenecks Help sell the product Reduce risk
4/28/2014 9 2009 Bahill
Purpose of frameworks
Organize integrated models of an enterprise Assess completeness of the descriptive representation of an enterprise Understand an organization or a system Assist in identification and categorization Provide a communication mechanism Help manage complexity Identify the flow of money in the enterprise
4/28/2014
10
2009 Bahill
Frameworks
Frameworks help people organize and assess completeness of integrated models of their enterprises. There are few public examples where a framework has been completely populated. This paper will fill in a complete framework for Baseball. We know of no other enterprise that has models in as many cells, where the models are not proprietary, where the models will be understood by a large number of people without a steep learning curve.
4/28/2014 11 2009 Bahill
Common frameworks
Zachman,
Zachman Enterprise Architecture Framework
DoDAF,
Department of Defense Architecture Framework
4/28/2014
12
2009 Bahill
4/28/2014
13
2009 Bahill
4/28/2014
14
2009 Bahill
The rows
1. Scope describes the systems vision, mission, boundaries, architecture and constraints. The scope states what the system is to do. It is called a black box model, because we see the inputs and outputs, but the not the inner workings. 2. Business model shows goals, strategies and processes that are used to support the mission of the organization. 3. System model contains system requirements, objects, activities and functions that implement the business model. The system model states how the system is to perform its functions. It is called a white box model, because we see its inner workings. 4. Technology model considers the constraints of humans, tools, technology and materials. 5. Detailed representation presents individual, independent components that can be allocated to contractors for implementation. 6. Real system depicts the operational system under consideration.
4/28/2014 15 2009 Bahill
The columns
I Keep six honest serving men (They taught me all I knew): Their names are What and Why and When And How and Where and Who.
From The Elephants Child, Rudyard Kipling, 1902.
4/28/2014
16
2009 Bahill
4/28/2014
17
2009 Bahill
The columns
1. What (data) describes the entities involved in each perspective of the enterprise. Examples include equipment, business objects and system data. 2. How (functions) shows the functions within each perspective. 3. Where (networks) shows locations and interconnections within the enterprise. This includes major business geographical locations, networks and the playing field. 4. Who (people) represents the people within the enterprise and metrics for assessing their capabilities and performance. The design of the enterprise organization has to do with the allocation of work and the structure of authority and responsibility. 5. When (time) represents time, or the event relationships that establish performance criteria. This is useful for designing schedules, the processing architecture, the control architecture and timing systems. 6. Why (motivation) describes the motivations of the enterprise. This reveals the enterprise goals, objectives, business plan, knowledge architecture, and reasons for thinking, doing things and making decisions.
4/28/2014 18 2009 Bahill
Goal
Jacques Barzun* said, Whoever wants to know the heart and mind of America had better learn baseball, the rules and realities of the game. Zachman says the way to learn Baseball is to understand the models in the 36 cells of a Zachman framework. Our goal was to populate a Zachman framework with objective simulatable models for the science of baseball that were published in peer reviewed journals.
4/28/2014
19
2009 Bahill
4/28/2014
20
2009 Bahill
A Zachman framework
1. What 1. Scope 2. Business model 3. System model 4. Technology model 5. Detailed representation 6. Real system, Baseball i. e. executing bat the game of baseball 2. How 3. 4. 5. 6. Where Who When Why
4/28/2014
21
2009 Bahill
Column 1, Row 5
Many models for the baseball bat explain the sweet spot, moment of inertia (MoI), center of percussion (CoP), etc. (Adair, 1994: Cross, 1998: Nathan, 2000 and 2003); column 1 (what), row 5 (detailed representation).
knob pivot cm cop
dknob-pivot
dpivot-cm dpivot-cop
dcm-cop
4/28/2014
22
2009 Bahill
A Zachman framework
1. What 1. Scope 2. Business model 3. System model 4. Technology model 5. Detailed representation 2. How 3. 4. 5. 6. Where Who When Why
Sweet spot, MoI, CoP 6. Real system, Baseball i. e. executing bat the game of baseball
4/28/2014
23
2009 Bahill
Column 1, Row 5
The swing of a bat can be modeled with a translation and two rotations, one about the batters spine and the other between the two hands (Brancazio, 1987: Watts and Bahill, 2000); column 1 (what), row 5 (detailed representation).
4/28/2014
24
2009 Bahill
4/28/2014
25
2009 Bahill
4/28/2014
26
2009 Bahill
A Zachman framework
1. What 1. Scope 2. Business model 3. System model 4. Technology model 5. Detailed representation 2. How 3. 4. 5. 6. Where Who When Why
A swing, Sweet spot, MoI, CoP 6. Real system, Baseball i. e. executing bat the game of baseball
4/28/2014
27
2009 Bahill
Column 1, Row 4*
There is an ideal bat weight and a best weight distribution for each batter (Bahill and Karnavas, 1989 and 1991: Bahill and Morna Freitas, 1995: Bahill, 2004). The team helps the individual select and acquire the right bat; column 1 (what), row 4 (technology model).
90 80 70
Speed (mph)
60 50 40 30 20 10 0 0 10 20
30
40
50
60
70
A Zachman framework
1. What 1. Scope (Commissioner of Baseball) 2. Business model (Team Owner) 3. System model (General Manager) 4. Technology model (Team Manager) 5. Detailed representation (Individual Baseball Player) 6. Real system, i. e. executing the game of baseball 2. How
Ideal bat weight & weight distribution A swing, Sweet spot, MoI, CoP
Baseball bat
4/28/2014
29
2009 Bahill
Column 1, Row 3*
Each organization provides facilities for batting practice, conditioning and skills development; column 1 (what), row 3 (system model).
4/28/2014
30
2009 Bahill
A Zachman framework
1. What 1. Scope (Commissioner of Baseball) 2. Business model (Team Owner) 3. System model (General Manager) 4. Technology model (Team Manager) 5. Detailed representation (Individual Baseball Player) 6. Real system, i. e. executing the game of baseball 2. How
Batting practice facilities Ideal bat weight & weight distribution A swing, Sweet spot, MoI, CoP Baseball bat
4/28/2014
31
2009 Bahill
Column 1, Row 2
The NCAA has created rules governing the allowed dimensions and performance of aluminum bats (Crisco, 1997: Nathan, 2003), For example, the bat shall not weigh less (in ounces) than its length (in inches); column 1 (what), row 2 (business model).
4/28/2014
32
2009 Bahill
A Zachman framework
1. What 1. Scope (Commissioner of Baseball) 2. Business model (Team Owner) 3. System model (General Manager) 4. Technology model (Team Manager) 5. Detailed representation (Individual Baseball Player) 6. Real system, i. e. executing the game of baseball 2. How NCAA bat rules Batting practice facilities Ideal bat weight & weight distribution A swing, Sweet spot, MoI, CoP Baseball bat
4/28/2014
33
2009 Bahill
Column 1, Row 1*
The rules of ball and stick games (baseball, softball, cricket, tennis) are written to challenge the physiological limits of the human in many dimensions (Regan, 1992). There are rules for each piece of equipment; column 1 (what), row 1 (scope).
4/28/2014
34
2009 Bahill
A Zachman framework
1. What 1. Scope (Commissioner of Baseball) 2. Business model (Team Owner) 3. System model (General Manager) 4. Technology model (Team Manager) 5. Detailed representation (Individual Baseball Player) 6. Real system, i. e. executing the game of baseball Equipment rules NCAA bat rules Batting practice facilities Ideal bat weight & weight distribution A swing, Sweet spot, MoI, CoP Baseball bat 2. How
4/28/2014
35
2009 Bahill
Slivers
We cannot present all baseball models in one study. So we only present slivers. The sliver used in column 1 (what) was the physical baseball bat. An alternate sliver for column 1 is information.
4/28/2014
36
2009 Bahill
Information1
Multiple TV cameras in major league stadiums pick up the flight of the pitch. The TV signals can be used to construct a computer model for the flight of the ball. When these data are used by the TV networks to display to the TV audience the location of the pitch relative to the strike zone, then they are being used as a Detailed Representation: row 5, column 1, role TV audience. These data could be used to determine if the ball passed through the strike zone and this Technology Model information could be transmitted in real time to the umpire to help him call balls and strikes, this would be row 4, column 1, role umpire. 37 2009 Bahill 4/28/2014
Information2
These data could also be put on the Internet for researchers to use to help determine the speed and spin of the ball, to allow them to model the movement of the ball and for sports fans to play fantasy baseball; this would be row 4, column 1, role researcher. http://webusers.npl.uiuc.edu/~anathan/pob/pitchtracker.html When this information is put on a CD and given to the umpire at the end of the game to give him feedback to improve the consistency of the set of umpires, then it is being used in a System Model (www.QuesTec.com): row 3 column 1, role umpires.
4/28/2014 38 2009 Bahill
Information3
When knowledge about the difference in the strike zones of American and National League umpires is used to regulate enforcement of baseball rules, then it is being used in the Business Model: row 2, column 1, role commissioner and owners. If such information were gathered and analyzed for cricket and tennis, then the derived wisdom would transcend baseball and become row 1, column 1.
4/28/2014
39
2009 Bahill
One pitch and peoples response to it is called a sliver of Baseball. I cannot present all of the thousands of Baseball models. So to limit the scope, I present only a few slivers. To enlarge the coverage I use a different sliver in each column.
4/28/2014
40
2009 Bahill
Catcher
Umpire
Fielder
Umpire is a role that can be filled by one (for the minors in Little League) to six (for World S eries games) people.
Merge
Fork
Ball
{joinS pec = Runner OR Ball}
Fork
Other could be batter hit by pitch, foul ball with two strikes, catcher interference, time-out called before pitch, etc.
4/28/2014
41
2009 Bahill
A Zachman framework
1. What 1. Scope 2. How 3. 4. 5. 6. Where Who When Why Equipment rules 2. Business NCAA bat model rules 3. System Batting model practice facilities 4. Technology Ideal bat model weight & weight distribution 5. Detailed A swing, representation Sweet spot, MoI, CoP 6. Real system, Baseball bat One pitch i. e. executing & the game of responses baseball
4/28/2014 42 2009 Bahill
Column 2, Row 5*
The movement of the pitch depends only on gravity, the balls velocity, and the spin (Watts and Bahill, 2000: Bahill and Baldwin, 2004), the right-hand rules shows how the ball is deflected by spininduced forces (Bahill and Baldwin, 2007); column 2 (how), row 5 (detailed representation).
Magnus force Spin
Ball
Ball direction
4/28/2014
43
Drag force
Gravity force
2009 Bahill
SaD Sid
4/28/2014
44
2009 Bahill
Column 2, Row 5
Two strategies are used by the batter for tracking the pitch using the saccadic and smooth pursuit eye movement systems (Bahill and LaRitz, 1984: McHugh and Bahill, 1985); column 2 (how), row 5 (detailed representation).
4/28/2014
45
2009 Bahill
Two strategies
The optimal hitting strategy: track the ball with smooth pursuit eye movements and fall behind in the last five feet. The optimal learning strategy: track the ball over the first part of its trajectory with smooth pursuit eye movements, make a fast saccadic eye movement to the predicted point of bat-ball collision, then let the ball catch up to the eye. The batter observes the ball, makes a prediction of where it will hit his bat, sees the actual position of the ball when it hits the bat, and uses this feedback to learn to predict better next time.
4/28/2014
46
2009 Bahill
Column 2, Row 5
A neurophysiological model shows how the batter predicts where and when the ball will cross the plate (Karnavas, Bahill and Regan, 1990: Bahill and Baldwin, 2004); column 2 (function, how), row 5 (detailed representation).
4/28/2014
47
2009 Bahill
Neurophysiological model
Other Sensory Inputs Memory Ball Spin Ball's Retinal Image Time Since Release Speed Estimator Estimated Pitch Speed
^
D0
Timer
d/dt d/dt
D
^ zfall
4/28/2014
48
2009 Bahill
Column 2, Row 5
Underestimating the pitch speed can induce the perceptual illusion of the rising fastball (Karnavas, Bahill and Regan, 1990: Bahill and. Karnavas, 1993); column 2 (how), row 5 (detailed representation).
4/28/2014
49
2009 Bahill
A Zachman framework
1. What 1. Scope (Commissioner of Baseball) 2. Business model (Team Owner) 3. System model (General Manager) 4. Technology model (Team Manager) 5. Detailed representation (Individual Baseball Player) 6. Real system, i. e. executing the game of baseball Equipment rules NCAA bat rules Batting practice facilities Ideal bat weight & weight distribution A swing, Sweet spot, MoI, CoP Rising fastball, Eye movement strategies, Speed & spin One pitch & responses 2. How 3. Where
Baseball bat
4/28/2014
50
2009 Bahill
Column 2, Row 4
Teamwork and signals allow the manager, the batter and the runners to execute tactics such as hit and run, bunt, steal, take the pitch, swing away, etc.; column 2 (how), row 4 (technology model).
4/28/2014
51
2009 Bahill
A Zachman framework
1. What 1. Scope (Commissioner of Baseball) 2. Business model (Team Owner) 3. System model (General Manager) 4. Technology model (Team Manager) Equipment rules NCAA bat rules Batting practice facilities Ideal bat weight & weight distribution Teamwork & signals for hit and run, bunt, etc. Rising fastball, Eye movement strategies, Speed & spin One pitch & responses 2. How 3. Where
5. Detailed representation A swing, Sweet spot, MoI, CoP (Individual Baseball Player) 6. Real system, i. e. executing the Baseball bat game of baseball
4/28/2014
52
2009 Bahill
Column 2, Row 3
Stadiums can be equipped with a variety of optional equipment that can record and playback the pitch, such as the multiple television cameras used to aid the umpires (www.QuesTec.com) or entertain the TV audience (http://www.gueziec.org/kzone.html) and the stadium instant replay screens for the benefit of the players and spectators; column 2 (how), row 3 (system model).
4/28/2014
53
2009 Bahill
A Zachman framework
1. What 1. Scope (Commissioner of Baseball) 2. Business model (Team Owner) 3. System model (General Manager) 4. Technology model (Team Manager) Equipment rules NCAA bat rules Batting practice facilities Ideal bat weight & weight distribution Pitch trackers, Instant replay Teamwork & signals for hit and run, bunt, etc. Rising fastball, Eye movement strategies, Speed & spin One pitch & responses 2. How 3. Where
5. Detailed representation A swing, Sweet spot, MoI, CoP (Individual Baseball Player) 6. Real system, i. e. executing the Baseball bat game of baseball
4/28/2014
54
2009 Bahill
Column 2, Row 2
Major League Baseball Inc. defines the strike zone and manages umpires; column 2 (how), row 2 (business model).
4/28/2014
55
2009 Bahill
A Zachman framework
1. What 1. Scope (Commissioner of Baseball) 2. Business model (Team Owner) 3. System model (General Manager) 4. Technology model (Team Manager) Equipment rules NCAA bat rules Batting practice facilities Ideal bat weight & weight distribution Define the strike zone Pitch trackers; Instant replay Teamwork & signals for hit and run, bunt, etc. Rising fastball, Eye movement strategies, Speed & spin One pitch & responses 2. How 3. Where
5. Detailed representation A swing, Sweet spot, MoI, CoP (Individual Baseball Player) 6. Real system, i. e. executing the Baseball bat game of baseball
4/28/2014
56
2009 Bahill
Column 2, Row 1
The rules of baseball evolved over its first 50 years, but have been relatively stable over the last century (Gould, 2003); column 2 (how), row 1 (scope).
4/28/2014
57
2009 Bahill
A Zachman framework
1. What 1. Scope (Commissioner of Baseball) 2. Business model (Team Owner) 3. System model (General Manager) 4. Technology model (Team Manager) Equipment rules NCAA bat rules Batting practice facilities Ideal bat weight & weight distribution 2. How Rules of baseball Define the strike zone Pitch trackers; Instant replay Teamwork & signals for hit and run, bunt, etc. Rising fastball, Eye movement strategies, Speed & spin One pitch & responses 3. Where
5. Detailed representation A swing, Sweet spot, MoI, CoP (Individual Baseball Player) 6. Real system, i. e. executing the Baseball bat game of baseball
4/28/2014
58
2009 Bahill
4/28/2014
61
2009 Bahill
4/28/2014
64
2009 Bahill
4/28/2014
65
2009 Bahill
4/28/2014
67
2009 Bahill
4/28/2014
68
2009 Bahill
4/28/2014
69
2009 Bahill
4/28/2014
70
2009 Bahill
4/28/2014
71
2009 Bahill
4/28/2014
74
2009 Bahill
A Zachman Framework Populated with Baseball Models Baseball 1. What 2. How 3. Where 1. Scope Equipment (Commissioner rules of Baseball) 2. Business model (Team Owner) 3. System model (General Manager) NCAA bat rules Rules of baseball Define the strike zone Stadiums & TV, Leagues & divisions Shared use of stadiums
Pitch tracker, Batting practice Stadium instant facilities replay Teamwork 4. Technology Ideal bat & signals model weight & for hit & (Team weight run, bunt, Manager) distribution etc. Rising fastball, 5. Detailed representation A swing, Eye CoP, MoI, movement (Scientist, Engineer, CoR strategies, Speed & Coach) spin 6. Real system One pitch Baseball (Baseball & bat Player) responses
4. Who Revenue sharing, Reserve clause A-Rod, Olympic teams Fantasy baseball, Player contracts, 25man roster,
5. When
6. Why
Entertainment, Chronology Intellectual stimulation Season schedules Money, Power, Pride; Free Bats Wants a winning season
Pitching rotations
Weekly Mental statistics, Box rehearsal & scores, Sweet understandings spot Players physiological state, The count Major league baseball players
Pitch count
Mental models, CFFF, Expect Work fast & fastball with 3change 0 count speeds Pitch interval Motivation for decisions
Baseball field
4/28/2014
75
2009 Bahill
Lessons learned
4/28/2014
76
2009 Bahill
Increasing detail1
In going from top to bottom more and more detail is introduced. The number and size of the models in each cell increases from top to bottom, perhaps 3 times per row. Thus a row 5 cell could contain 100 times the mass (money, effort, pages of documentation, lines of code, number of diagrams, etc.) of a row 1 cell. Our tables do not show this mushrooming.
4/28/2014
77
2009 Bahill
Column 1 Row 1
Column 1 Row 2
Column 1 Row 2
Column 1 Row 2
C1 Row 3 C1 R4 C1 R4 C1 R4 C1 R4
C1 Row 3 C1 R4 C1 R4
C1 Row 3 C1 R4 C1 R4
C1 Row 3 C1 R4 C1 R4 C1 R4
C1 Row 3 C1 R4 C1 R4 C1 R4
C1 Row 3 C1 R4 C1 R4 C1 R4
C1 Row 3 C1 R4 C1 R4 C1 R4
C1 Row 3 C1 R4 C1 R4 C1 R4
C1 Row 3 C1 R4 C1 R4 C1 R4
C1 R5
C1 R5
C1 R5
C1 R4
C1 R5
C1 R5
C1 R5
C1 R5
C1 R5
C1 R5
4/28/2014
78
2009 Bahill
Other slivers
Instead of focusing on the bat, the lower rows of column 1 could have included other equipment, such as the ball, gloves, bases, masks, and the scoreboard. They could have included* system state training equipment actions of the pitcher teamwork finances
4/28/2014
79
2009 Bahill
Hierarchy
A Zachman framework is hierarchical: each cell can contain a framework of its own. We could make a framework for Baseball the major leagues the Arizona Diamondbacks Brandon Webb, etc.
4/28/2014
80
2009 Bahill
4/28/2014
81
2009 Bahill
4/28/2014
82
2009 Bahill
4/28/2014
83
2009 Bahill
Modeling generalities
All components in a model should be at the same level. Models should only exchange inputs and outputs with other models of the same level, or maybe one level higher or lower. Level means level of detail or level of abstraction. This is not synonymous with Zachmans rows.
Reference: A. T. Bahill, R. Botta and E. Smith, What Are Levels? Proceedings of the 15th Annual International Symposium of the International Council on Systems Engineering (INCOSE), July 10-15, 2005, Rochester, NY
4/28/2014
84
2009 Bahill
Catcher
Umpire
Fielder
Umpire is a role that can be filled by one (for the minors in Little League) to six (for World S eries games) people.
Merge
Fork
Ball
{joinS pec = Runner OR Ball}
Fork
Other could be batter hit by pitch, foul ball with two strikes, catcher interference, time-out called before pitch, etc.
4/28/2014
85
2009 Bahill
Levels1
Consider the Batter object in the activity diagram of the previous slide We could model the state of his mind with the following attributes and states Experience: rookie, veteran, imminent free agent Salary: considered too low, considered too high, commensurate with earned respect Physiology: age, health, on disabled list Competition: other players at his position Would this be easy to understand?
4/28/2014
86
2009 Bahill
Levels2
Again consider the Batter object in that activity diagram We could model the state of his mind with the following attributes and states Balls, strikes, outs Speed of last pitch Runners on base Last signal from coach Is this easier to understand?
4/28/2014
87
2009 Bahill
Here is a class diagram at the appropriate level Batter (low level) Count, Outs MentalModels GameSituation Signals
predictWhen predictWhere swing takePitch bunt
88 2009 Bahill
4/28/2014
1.1
1.2
1.3
1.3.1
1.3.2
1.3.1.2
1.3.1.3
4/28/2014
89
2009 Bahill
Interoperability
Company models should interact with each other. ISO AP233 is an application protocol that is creating an information model to capture the semantics needed for the interchange of information between tools. Interoperability standards will help with reuse.
4/28/2014
90
2009 Bahill
Top-down or bottom-up?
We discussed the models from bottom to top. That is the way they were derived: in basic
Column order
A newspaper article should start with who, what, when, where, why and sometimes how, usually in that order. A Zachman framework has a different purpose and therefore a different column order.
4/28/2014
93
2009 Bahill
4/28/2014
94
2009 Bahill
4/28/2014
95
2009 Bahill
1 2 1
4/28/2014
96
2009 Bahill
4/28/2014
97
2009 Bahill
Purpose?
What is the purpose of a framework? Understand an organization or a system What is the purpose of models? Understand or improve an existing system or organization Create a new design or system Control a system Suggest new experiments Guide data collection activities Allocate resources Identify cost drivers Increase return on investment
4/28/2014 98 2009 Bahill
Reduce the number of classes using affinity analysis. Abstract this into a metamodel that shows how that company does modeling and simulation.
4/28/2014
99
2009 Bahill
4/28/2014
100
2009 Bahill
4/28/2014
102
2009 Bahill
4/28/2014
103
2009 Bahill
4/28/2014
Table 2-1: List of Products, DoDAF version 1.5 Applicable View, Product, Product Name, General Description All View AV-1 Overview and Summary Information Scope, purpose, intended users, environment depicted, analytical findings All View AV-2 Integrated Dictionary Architecture data repository with definitions of all terms used in all products Operational OV-1 High-Level Operational Concept Graphic High-level graphical/textual description of operational concept Operational OV-2 Operational Node Connectivity Description Operational nodes, connectivity, and information exchange need lines between nodes Operational OV-3 Operational Information Exchange Matrix Information exchanged between nodes and the relevant attributes of that exchange Operational OV-4 Organizational Relationships Chart Organizational, role, or other relationships among organizations Operational OV-5 Operational Activity Model Capabilities, operational activities, relationships among activities, inputs, and outputs; overlays can show cost, performing nodes, or other pertinent information Operational OV-6a Operational Rules Model One of three products used to describe operational activity identifies business rules that constrain operation Operational OV-6b Operational State Transition Description One of three products used to describe operational activity identifies business process responses to events Operational OV-6c Operational Event-Trace Description One of three products used to describe operational activity traces actions in a scenario or sequence of events Operational OV-7 Logical Data Model Documentation of the system data requirements and structural business process rules of the Operational View Systems and Services SV-1 Systems Interface Description Identification of systems nodes, systems, system items, services, and service items and their interconnections, within and between nodes Systems and Services SV-2 Systems Communications Description Systems nodes, systems, system items, services, and service items and their related communications laydowns Systems and Services SV-3 Systems-Systems Matrix, Services-Systems Matrix, Services-Services Matrix Relationships among systems and services in a given architecture; can be designed to show relationships of interest, e.g., system-type interfaces, planned vs. existing interfaces, etc. Systems and Services SV-4a Systems Functionality Description Functions performed by systems and the system data flows among system functions Systems and Services SV-4b Services Functionality Description Functions performed by services and the service data flow among service functions Systems and Services SV-5a Operational Activity to Systems Function Traceability Matrix Mapping of system functions back to operational activities Systems and Services SV-5b Operational Activity to Systems Traceability Matrix Mapping of systems back to capabilities or operational activities Systems and Services SV-5c Operational Activity to Services Traceability Matrix Mapping of services back to operational activities Systems and Services SV-6 Systems Data Exchange Matrix, Services Data Exchange Matrix Provides details of system or service data elements being exchanged between systems or services and the attributes of that exchange Systems and Services SV-7 Systems Performance Parameters Matrix, Services Performance Parameters Matrix Performance characteristics of Systems and Services View elements for the appropriate time frame(s) Systems and Services SV-8 Systems Evolution Description, Services Evolution Description Planned incremental steps toward migrating a suite of systems or services to a more efficient suite, or toward evolving a current system to a future implementation Systems and Services SV-9 Systems Technology Forecast, Services Technology Forecast Emerging technologies and software/hardware products that are expected to be available in a given set of time frames and that will affect future development of the architecture Systems and Services SV-10a Systems Rules Model, Services Rules Model One of three products used to describe system and service functionality identifies constraints that are imposed on systems/services functionality due to some aspect of systems design or implementation Systems and Services SV-10b Systems State Transition Description, Services State Transition Description One of three products used to describe system and service functionalityidentifies responses of a system/service to events Systems and Services SV-10c Systems Event-Trace Description, Services Event-Trace Description One of three products used to describe system or service functionality identifies system/service-specific refinements of critical sequences of events described in the Operational View Systems and Services SV-11 Physical Schema Physical implementation of the Logical Data Model entities, e.g., message formats, file structures, physical schema Technical Standards TV-1 Technical Standards Profile Listing of standards that apply to Systems and Services View elements in a given architecture Technical Standards TV-2 Technical Standards Forecast Description of emerging standards and potential impact on current Systems and Services View elements, within a set of time frames
Product descriptions
104
2009 Bahill
4/28/2014
4/28/2014
106
2009 Bahill
OV-2 OV-6a
Models
Matrices Forecast
SV-2
Scenario Data Rules
TV-1
TV-2 SV-10c SV-10b SV-3 SV-4 SV-5 SV-7 SV-8 SV-9 SV-10a AV-2
4/28/2014
107
2009 Bahill
4/28/2014
108
2009 Bahill
Purpose1
DoDAF: ensue that architectural descriptions can be compared and related across organizational boundaries In a net-centric warfighting environment, there is a great need for integration and interoperability in order to achieve warfighting capabilities. Describe the operation of interrelated systems Zachman: provide a basic structure that supports organization, integration, development, and management of a set of architectural representations
4/28/2014 110 2009 Bahill
Purpose2
Neither DoDAF nor Zachman are design processes. They can help document existing designs. DoDAF is intended for unprecedented large systems of complex systems. Zachman is intended for enterprises.
4/28/2014
111
2009 Bahill
Strengths
DoDAF: organized descriptive extensive product relationships identifies duplicate functions accepted DoD standard Zachman organized intuitive breath of coverage
4/28/2014
112
2009 Bahill
Drawbacks
DoDAF Cumbersome Inflexible Ponderous and hard to learn Zachman Elementary Does not prescribe design tradeoffs design rationale documentation of architecture decisions
4/28/2014
113
2009 Bahill
Zachman summary1
To understand an enterprise, you should have a model in every cell of a Zachman framework For each cell, use which ever modeling tool is most appropriate Because a framework is hierarchical, cells in the lower rows will have many models Cells in the top rows should trace to the organizations vision and mission statements Cells in a row should be at similar levels of detail (granularity)
4/28/2014
114
2009 Bahill
Zachman summary2
Filling in a Zachman framework will help convince your customer that you understand the system to be designed and built. Frameworks help promote integration of models. Frameworks help show the flow of money.
4/28/2014
115
2009 Bahill
4/28/2014
116
2009 Bahill
Seminar materials
A ball Perhaps the two-seam and four-seam video
4/28/2014
117
2009 Bahill
4/28/2014
118
2009 Bahill