Top Banner
A Zachman Framework A Zachman Framework Populated with Populated with Baseball Models Baseball Models Terry Bahill Systems and Industrial Engineering University of Arizona [email protected] copyright ©, 2004-09, Bahill This file is located at http://www.sie.arizona.edu/sysengr/s lides/
118

Zachman Frameworks and Baseball

Nov 01, 2014

Download

Technology

Aamir97

 
Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Page 1: Zachman Frameworks and Baseball

A Zachman FrameworkA Zachman FrameworkPopulated with Populated with Baseball ModelsBaseball Models

Terry BahillSystems and Industrial EngineeringUniversity of [email protected] ©, 2004-09, BahillThis file is located at

http://www.sie.arizona.edu/sysengr/slides/

Page 2: Zachman Frameworks and Baseball

ReferencesReferences• 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/publishedPapers/ZachmanBaseball.pdf

• Bahill, A. T., Botta, R. and Daniels, J., A systems engineering approach to organizing baseball models, keynote address at the Asia-Pacific Congress on Sports Technology, Tokyo, September 11-14, 2005.

04/08/23 2 © 2009 Bahill

Page 3: Zachman Frameworks and Baseball

DefinitionsDefinitions• 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.

04/08/23 3 © 2009 Bahill

Page 4: Zachman Frameworks and Baseball

ExampleExample• 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

04/08/23 4 © 2009 Bahill

Page 5: Zachman Frameworks and Baseball

Model do not have to be smallerModel do not have to be smaller• Models do not have to be smaller than the entity

they model.• Geometrical lines are one-dimensional and,

therefore, cannot be seen with our eyes.

____________________________• Things like the above are models of the

geometrical concept of a line.• They have a measurable width and are, therefore,

not true lines.

04/08/23 5 © 2009 Bahill

Page 6: Zachman Frameworks and Baseball

Tasks in the modeling processTasks in the modeling process**

• Describe the system to be modeled• Determine the purpose of the model• Determine the level of the model• Gather experimental data describing system behavior• Investigate alternative models• Select a tool or language for the simulation• Make the model• Validate the model*

Show that the model behaves like the real system Emulate something not used in the model’s design Perform a sensitivity analysis Show interactions with other models

• Integrate with models for other systems• Analyze the performance of the model• Re-evaluate and improve the model• Suggest new experiments on the real system• State the assumptions

04/08/23 6 © 2009 Bahill

Page 7: Zachman Frameworks and Baseball

PhilosophyPhilosophy

RealSystem

Model ofReal

System

ComputerSimulationof Model

Modelers Modelers

GoodModelers

GoodModelers

Math

ematician

s

Exp

erim

enta

lists

04/08/23 7 © 2009 Bahill

Page 8: Zachman Frameworks and Baseball

• Models of behavior• Models of structure• Models of physical properties• Models for analysis

Kinds of modelsKinds of models

04/08/23 8 © 2009 Bahill

Page 9: Zachman Frameworks and Baseball

Purpose of modelsPurpose 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

04/08/23 9 © 2009 Bahill

Page 10: Zachman Frameworks and Baseball

Purpose of frameworksPurpose 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

04/08/23 10 © 2009 Bahill

Page 11: Zachman Frameworks and Baseball

FrameworksFrameworks• 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.

04/08/23 11 © 2009 Bahill

Page 12: Zachman Frameworks and Baseball

Common frameworksCommon frameworks• Zachman,

Zachman Enterprise Architecture Framework

• DoDAF,Department of Defense Architecture Framework

04/08/23 12 © 2009 Bahill

Page 13: Zachman Frameworks and Baseball

An empty Zachman frameworkAn empty Zachman framework 1. What

(data) 2. How (function)

3. Where (network)

4. Who (people)

5. When (time)

6. Why (motivation)

1. Scope (context)

2. Business model (concept)

3. System model (logical)

4. Technology model (physical)

5. Detailed representation (component)

6. Real system, i. e. executing the game of baseball

04/08/23 13 © 2009 Bahill

Page 14: Zachman Frameworks and Baseball

The rows presentThe rows present* *

• different perspectives of the enterprise • different views of the enterprise • different roles in the enterprise

04/08/23 14 © 2009 Bahill

Page 15: Zachman Frameworks and Baseball

The rowsThe rows1. Scope describes the system’s 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.

04/08/23 15 © 2009 Bahill

Page 16: Zachman Frameworks and Baseball

The columnsThe columnsI Keep six honest serving men(They taught me all I knew):Their names are What and Why and WhenAnd How and Where and Who.

From “The Elephant’s Child,” Rudyard Kipling, 1902.

04/08/23 16 © 2009 Bahill

Page 17: Zachman Frameworks and Baseball

The columns presentThe columns presentvarious aspects of the enterprise

04/08/23 17 © 2009 Bahill

Page 18: Zachman Frameworks and Baseball

The columnsThe columns1. 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.

04/08/23 18 © 2009 Bahill

Page 19: Zachman Frameworks and Baseball

GoalGoalJacques 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.

04/08/23 19 © 2009 Bahill

Page 20: Zachman Frameworks and Baseball

04/08/23 20

Column 1, What (data)Column 1, What (data)The object modeled in column 1 is the baseball bat.

© 2009 Bahill

Page 21: Zachman Frameworks and Baseball

A Zachman frameworkA Zachman framework 1.

What 2.

How 3.

Where 4.

Who 5.

When 6.

Why 1. Scope 2. Business model

3. System model

4. Technology model

5. Detailed representation

6. Real system, i. e. executing the game of baseball

Baseball bat

04/08/23 21 © 2009 Bahill

Page 22: Zachman Frameworks and Baseball

04/08/23 22

Column 1, Row 5 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 dcm-cop

dpivot-cop

© 2009 Bahill

Page 23: Zachman Frameworks and Baseball

A Zachman frameworkA Zachman framework 1.

What 2.

How 3.

Where 4.

Who 5.

When 6.

Why 1. Scope 2. Business model

3. System model

4. Technology model

5. Detailed representation

Sweet spot, MoI, CoP

6. Real system, i. e. executing the game of baseball

Baseball bat

04/08/23 23 © 2009 Bahill

Page 24: Zachman Frameworks and Baseball

Column 1, Row 5Column 1, Row 5The swing of a bat can be modeled with a translation and two rotations, one about the batter’s spine and the other between the two hands (Brancazio, 1987: Watts and Bahill, 2000); column 1 (what), row 5 (detailed representation).

04/08/23 24 © 2009 Bahill

Page 25: Zachman Frameworks and Baseball

04/08/23 25 © 2009 Bahill

Page 26: Zachman Frameworks and Baseball

04/08/23 26 © 2009 Bahill

Page 27: Zachman Frameworks and Baseball

A Zachman frameworkA Zachman framework 1.

What 2.

How 3.

Where 4.

Who 5.

When 6.

Why 1. Scope 2. Business model

3. System model

4. Technology model

5. Detailed representation

A swing, Sweet spot, MoI, CoP

6. Real system, i. e. executing the game of baseball

Baseball bat

04/08/23 27 © 2009 Bahill

Page 28: Zachman Frameworks and Baseball

04/08/23 28

Column 1, Row 4Column 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).

0

10

20

30

40

50

60

70

80

90

0 10 20 30 40 50 60 70

Bat Weight (oz)

Sp

ee

d (

mp

h)

Batted-ball Speed

Bat Speed

Ideal Bat Weight

© 2009 Bahill

Page 29: Zachman Frameworks and Baseball

A Zachman frameworkA Zachman framework 1. What 2. How 1. Scope (Commissioner of Baseball)

2. Business model (Team Owner)

3. System model (General Manager)

4. Technology model (Team Manager)

Ideal bat weight & weight distribution

5. Detailed representation (Individual Baseball Player)

A swing, Sweet spot, MoI, CoP

6. Real system, i. e. executing the game of baseball

Baseball bat

04/08/23 29 © 2009 Bahill

Page 30: Zachman Frameworks and Baseball

Column 1, Row 3Column 1, Row 3**

Each organization provides facilities for batting practice, conditioning and skills development; column 1 (what), row 3 (system model).

04/08/23 30 © 2009 Bahill

Page 31: Zachman Frameworks and Baseball

A Zachman frameworkA Zachman framework 1. What 2. How 1. Scope (Commissioner of Baseball)

2. Business model (Team Owner)

3. System model (General Manager)

Batting practice facilities

4. Technology model (Team Manager)

Ideal bat weight & weight distribution

5. Detailed representation (Individual Baseball Player)

A swing, Sweet spot, MoI, CoP

6. Real system, i. e. executing the game of baseball

Baseball bat

04/08/23 31 © 2009 Bahill

Page 32: Zachman Frameworks and Baseball

Column 1, Row 2Column 1, Row 2The 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).

04/08/23 32 © 2009 Bahill

Page 33: Zachman Frameworks and Baseball

A Zachman frameworkA Zachman framework 1. What 2. How 1. Scope (Commissioner of Baseball)

2. Business model (Team Owner)

NCAA bat rules

3. System model (General Manager)

Batting practice facilities

4. Technology model (Team Manager)

Ideal bat weight & weight distribution

5. Detailed representation (Individual Baseball Player)

A swing, Sweet spot, MoI, CoP

6. Real system, i. e. executing the game of baseball

Baseball bat

04/08/23 33 © 2009 Bahill

Page 34: Zachman Frameworks and Baseball

Column 1, Row 1Column 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).

04/08/23 34 © 2009 Bahill

Page 35: Zachman Frameworks and Baseball

A Zachman frameworkA Zachman framework 1. What 2. How 1. Scope (Commissioner of Baseball)

Equipment rules

2. Business model (Team Owner)

NCAA bat rules

3. System model (General Manager)

Batting practice facilities

4. Technology model (Team Manager)

Ideal bat weight & weight distribution

5. Detailed representation (Individual Baseball Player)

A swing, Sweet spot, MoI, CoP

6. Real system, i. e. executing the game of baseball

Baseball bat

04/08/23 35 © 2009 Bahill

Page 36: Zachman Frameworks and Baseball

SliversSlivers• 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.

04/08/23 36 © 2009 Bahill

Page 37: Zachman Frameworks and Baseball

InformationInformation11

• 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.

04/08/23 37 © 2009 Bahill

Page 38: Zachman Frameworks and Baseball

InformationInformation22

• 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/~a-nathan/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.

04/08/23 38 © 2009 Bahill

Page 39: Zachman Frameworks and Baseball

InformationInformation33

• 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.

04/08/23 39 © 2009 Bahill

Page 40: Zachman Frameworks and Baseball

Column 2, How (function)Column 2, How (function)• The activity modeled in column 2 is one pitch and

people’s response to it.

• One pitch and people’s 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.

04/08/23 40 © 2009 Bahill

Page 41: Zachman Frameworks and Baseball

04/08/23 41

Catcher Pitcher Umpire Batter Fielder

Pitch Ball

Predict When and

Where

Decide if Ball or Runner Got to the Base First

Run to First Base

Field Ball and Throw to

Appropriate Base

Give Sign to Pitcher

Wait for Batter

[yes]

[no]

Fork

Swing Bat?

Ball Hit?

[yes][no]

Merge

Fork

Join

{joinSpec = Runner OR Ball}

Catch Ball & Return it to

Pitcher

Signal Ready

Terry BahillSummer 2007

Runner Ball

Decision

Call Ball, Strike, Out, Walk or

Other

Other could be batterhit by pitch, foul ball with two strikes, catcher interference, time-out called before pitch, etc.

There could also be decisions for fair or foul andfly or grounder.

Umpire is a role that can be filled by one (for the minors in Little League) to six (for World Series games) people.

© 2009 Bahill

Page 42: Zachman Frameworks and Baseball

A Zachman frameworkA Zachman framework 1. What 2. How 3.

Where 4.

Who 5.

When 6.

Why 1. Scope Equipment

rules

2. Business model

NCAA bat rules

3. System model

Batting practice facilities

4. Technology model

Ideal bat weight & weight distribution

5. Detailed representation

A swing, Sweet spot, MoI, CoP

6. Real system, i. e. executing the game of baseball

Baseball bat One pitch & responses

04/08/23 42 © 2009 Bahill

Page 43: Zachman Frameworks and Baseball

Column 2, Row 5Column 2, Row 5**

The movement of the pitch depends only on gravity, the ball’s velocity, and the spin (Watts and Bahill, 2000: Bahill and Baldwin, 2004), the right-hand rules shows how the ball is deflected by spin-induced forces (Bahill and Baldwin, 2007); column 2 (how), row 5 (detailed representation).

BallBall direction

Dragforce

Magnusforce

Gravityforce

Spin

04/08/23 43 © 2009 Bahill

Page 44: Zachman Frameworks and Baseball

04/08/23 44

From the perspective of From the perspective of a right-handed pitchera right-handed pitcher

SaD Sid

© 2009 Bahill

Page 45: Zachman Frameworks and Baseball

Column 2, Row 5Column 2, Row 5Two 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).

04/08/23 45 © 2009 Bahill

Page 46: Zachman Frameworks and Baseball

Two strategiesTwo 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.

04/08/23 46 © 2009 Bahill

Page 47: Zachman Frameworks and Baseball

Column 2, Row 5Column 2, Row 5A 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).

04/08/23 47 © 2009 Bahill

Page 48: Zachman Frameworks and Baseball

Neurophysiological modelNeurophysiological model

PrimaryVisual

Processes

SpeedEstimator

Timer

TimeSinceRelease

TimeUntilContact

d/dt

d/dt

Other Sensory Inputs

Memory

EstimatedPitchSpeed

-Ball'sRetinal Image

zfall^

D0

^

D^

Ball Spin

04/08/23 48 © 2009 Bahill

Page 49: Zachman Frameworks and Baseball

04/08/23 49

Column 2, Row 5Column 2, Row 5Underestimating 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).

© 2009 Bahill

Page 50: Zachman Frameworks and Baseball

A Zachman frameworkA Zachman framework 1. What 2. How 3. Where 1. Scope (Commissioner of Baseball)

Equipment rules

2. Business model (Team Owner)

NCAA bat rules

3. System model (General Manager)

Batting practice facilities

4. Technology model (Team Manager)

Ideal bat weight & weight distribution

5. Detailed representation (Individual Baseball Player)

A swing, Sweet spot, MoI, CoP

Rising fastball, Eye movement strategies, Speed & spin

6. Real system, i. e. executing the game of baseball

Baseball bat One pitch & responses

04/08/23 50 © 2009 Bahill

Page 51: Zachman Frameworks and Baseball

Column 2, Row 4Column 2, Row 4Teamwork 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).

04/08/23 51 © 2009 Bahill

Page 52: Zachman Frameworks and Baseball

A Zachman frameworkA Zachman framework 1. What 2. How 3. Where 1. Scope (Commissioner of Baseball)

Equipment rules

2. Business model (Team Owner)

NCAA bat rules

3. System model (General Manager)

Batting practice facilities

4. Technology model (Team Manager)

Ideal bat weight & weight distribution

Teamwork & signals for hit and run, bunt, etc.

5. Detailed representation (Individual Baseball Player)

A swing, Sweet spot, MoI, CoP

Rising fastball, Eye movement strategies, Speed & spin

6. Real system, i. e. executing the game of baseball

Baseball bat One pitch & responses

04/08/23 52 © 2009 Bahill

Page 53: Zachman Frameworks and Baseball

Column 2, Row 3Column 2, Row 3Stadiums 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).

04/08/23 53 © 2009 Bahill

Page 54: Zachman Frameworks and Baseball

A Zachman frameworkA Zachman framework 1. What 2. How 3. Where 1. Scope (Commissioner of Baseball)

Equipment rules

2. Business model (Team Owner)

NCAA bat rules

3. System model (General Manager)

Batting practice facilities

Pitch trackers, Instant replay

4. Technology model (Team Manager)

Ideal bat weight & weight distribution

Teamwork & signals for hit and run, bunt, etc.

5. Detailed representation (Individual Baseball Player)

A swing, Sweet spot, MoI, CoP

Rising fastball, Eye movement strategies, Speed & spin

6. Real system, i. e. executing the game of baseball

Baseball bat One pitch & responses

04/08/23 54 © 2009 Bahill

Page 55: Zachman Frameworks and Baseball

Column 2, Row 2Column 2, Row 2Major League Baseball Inc. defines the strike zone and manages umpires; column 2 (how), row 2 (business model).

04/08/23 55 © 2009 Bahill

Page 56: Zachman Frameworks and Baseball

A Zachman frameworkA Zachman framework 1. What 2. How 3. Where 1. Scope (Commissioner of Baseball)

Equipment rules

2. Business model (Team Owner)

NCAA bat rules Define the strike zone

3. System model (General Manager)

Batting practice facilities

Pitch trackers; Instant replay

4. Technology model (Team Manager)

Ideal bat weight & weight distribution

Teamwork & signals for hit and run, bunt, etc.

5. Detailed representation (Individual Baseball Player)

A swing, Sweet spot, MoI, CoP

Rising fastball, Eye movement strategies, Speed & spin

6. Real system, i. e. executing the game of baseball

Baseball bat One pitch & responses

04/08/23 56 © 2009 Bahill

Page 57: Zachman Frameworks and Baseball

Column 2, Row 1Column 2, Row 1The 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).

04/08/23 57 © 2009 Bahill

Page 58: Zachman Frameworks and Baseball

A Zachman frameworkA Zachman framework 1. What 2. How 3. Where 1. Scope (Commissioner of Baseball)

Equipment rules Rules of baseball

2. Business model (Team Owner)

NCAA bat rules Define the strike zone

3. System model (General Manager)

Batting practice facilities

Pitch trackers; Instant replay

4. Technology model (Team Manager)

Ideal bat weight & weight distribution

Teamwork & signals for hit and run, bunt, etc.

5. Detailed representation (Individual Baseball Player)

A swing, Sweet spot, MoI, CoP

Rising fastball, Eye movement strategies, Speed & spin

6. Real system, i. e. executing the game of baseball

Baseball bat One pitch & responses

04/08/23 58 © 2009 Bahill

Page 59: Zachman Frameworks and Baseball

Column 3, Where (network)Column 3, Where (network)• The topic of column 3 is the baseball field; column 3

(where), row 6 (real system).• The human brain does not have x, y and z coordinates

of objects. Humans must track objects using neurophysiological parameters. As a result outfielders run a curved path when tracking down fly balls (McBeath, Shaffer and Kaiser, 1995); column 3 (where), row 5 (detailed representation).

• Batters must predict where and when the ball will cross the plate (Karnavas, Bahill and Regan, 1990: Bahill and Baldwin, 2004); column 3 (where), row 5 (detailed representation).

• Before every pitch all fielder rehearse where they will throw the ball if they receive a ground ball or a fly ball; column 3 (where), row 4 (technology model).

04/08/23 59 © 2009 Bahill

Page 60: Zachman Frameworks and Baseball

Column 3, Where (continued)Column 3, Where (continued)• Where home plate is placed in the stadium effects

the area behind the plate, the design of protective netting, the orientation to the sun, the distance to the fences and therefore safety and playing performance; column 3 (where), row 3 (system model).

• Stadiums can be designed for baseball only or they may be shared by baseball, football and other events; column 3 (where), row 2 (business model).

• Baseball is played in stadiums and broadcast on television. The teams are organized into leagues and divisions according to geography; column 3 (where), row 1 (scope).

04/08/23 60 © 2009 Bahill

Page 61: Zachman Frameworks and Baseball

Column 4, Who (people)Column 4, Who (people)• The people modeled in column 4 are major league baseball

players; column 4 (who), row 6 (real system).• Physiological state of individual players determines whether

and how well they play or if they are on the disabled list; column 4 (who), row 5 (detailed representation).

• The count is the model for how the batter is doing during an at-bat; column 4 (who), row 4 (technology model).

• Defining and locating the sweet spot of the bat is a human-machine interface: the teams help individuals understand this issue ; column 4 (who), row 4 (technology model).

• Individual player performances are published daily in the box scores in the sports sections of newspapers. Player average performances are published weekly; column 4 (who), row 4 (technology model).

04/08/23 61 © 2009 Bahill

Page 62: Zachman Frameworks and Baseball

Column 4, Who (continued)Column 4, Who (continued)• Individual player statistics, Markov models and manager

decisions (such as batting order) are used to simulate games and seasons: this is called fantasy baseball (Burkiet, Harold and Palacios, 1997; www.stats.com). Scouts make observations and evaluations of players’ performances and report this information back to their organizations; column 4 (who), row 3 (system model).

• The General Manager (GM) creates the 25-man roster and trades players to improve it. It must contain a balance of players at each position, including short relievers, long relievers, etc.; column 4 (who), row 3 (system model).

• Billy Beane, General Manager of the Oakland Athletics, evaluates the worth of players with innovative high-level metrics and he has the most successful low-salary team in the major leagues (Lewis, 2003). The GM must consider player positions, salaries, performance, etc.; column 4 (who), row 3 (system model).

04/08/23 62 © 2009 Bahill

Page 63: Zachman Frameworks and Baseball

Column 4, Who (continued)Column 4, Who (continued)• George Steinbrenner, owner of the New York Yankees,

evaluates the worth of his players with traditional metrics and he has the most successful high-salary team in the major leagues. The team owner must consider the team salary cap and return on investment; column 4 (who), row 2 (business model).

• Before the 2001 season, the owners of the Texas Rangers created a ten year $252 million contract for Alex Rodriguez (Cohen and Wallace, 2003); column 4 (who), row 2 (business model).

• The Commissioner of Baseball coordinates the teams; the Major League Baseball Players Association and players’ agents orchestrate the activities of the players. The Commissioner must consider drug testing, salary caps, retirement plans, profit sharing and the reserve clause; column 4 (who), row 1 (scope).

04/08/23 63 © 2009 Bahill

Page 64: Zachman Frameworks and Baseball

Column 5, When (time)Column 5, When (time)• The fundamental unit of time in a baseball game is one

pitch; column 5 (when), row 6 (real system).• The batter’s mental model for the pitch is based on the last

one or two pitches or perhaps on the last 20 seconds (Bahill and Baldwin, 2004: Gray, 2003); column 5 (when), row 5 (detailed representation).

• A successful tactic of pitchers is “work fast and change speed on every pitch” (Bahill and Baldwin, 2004); column 5 (when), row 5 (detailed representation).

• The pitcher pitches the ball. The batter swings and hits the ball. He runs toward first base, etc. Our activity diagrams show one pitch and subsequent activities; column 5 (when), row 5 (detailed representation).

04/08/23 64 © 2009 Bahill

Page 65: Zachman Frameworks and Baseball

Column 5, When (continued)Column 5, When (continued)• Pitch count -- pitchers are often removed after, say, 120

pitches; column 5 (when), row 4 (technology model).• Pitching rotations, e.g. “Spahn and Sain and pray for rain;”

column 5 (when), row 3 (system model)• Television networks determine the starting times of many

games; column 5 (when), row 3 (system model).• Season schedules for all of the teams are complex

because of the many constraints; column 5 (when), row 2 (business model)

• Decisions must be made about interleague play, playoff structure, expansion teams, etc.; column 5 (when), row 1 (scope).

04/08/23 65 © 2009 Bahill

Page 66: Zachman Frameworks and Baseball

Column 6, Why (motivation)Column 6, Why (motivation)• Column 6 concerns why baseball people think the way they do

and make the decisions they do; column 6 (why), row 6 (real system).

• Why does the pitcher decide to throw a fastball, a slider, a curveball or a changeup? column 6 (why), row 5 (detailed representation).

• Critical flicker fusion frequency explains why baseball players think there is a difference between the two-seam and the four-seam fastballs although Physics shows no difference (Bahill and Baldwin, 2004); column 6 (why), row 5 (detailed representation).

• Batters have many heuristics. Among them is, with a 3-0 count expect a fastball because the pitcher will have the greatest confidence in throwing it for a strike (Williams and Underwood, 1982: Bahill and Baldwin, 2004); column 6 (why), row 4 (technical model).

• The manager motivates his players by knowing when blame and when not to (Baldwin, 2001); column 6 (why), row 4 (technical model).

04/08/23 66 © 2009 Bahill

Page 67: Zachman Frameworks and Baseball

04/08/23 67

Thefourseamfastball

© 2009 Bahill

Page 68: Zachman Frameworks and Baseball

04/08/23 68 © 2009 Bahill

Page 69: Zachman Frameworks and Baseball

Four seam orientationFour seam orientation

04/08/23 69 © 2009 Bahill

Page 70: Zachman Frameworks and Baseball

04/08/23 70

Thetwoseamfastball

© 2009 Bahill

Page 71: Zachman Frameworks and Baseball

Two seam orientationTwo seam orientation

04/08/23 71 © 2009 Bahill

Page 72: Zachman Frameworks and Baseball

The effect is greater in real lifeThe effect is greater in real life• The four-seam fastball will present 80 seams

per second. • There will be no flicker. • The batter will have fewer clues about the spin. • Hence he will predict less accurately, and may

perceive more rising fastballs.

• The two-seam fastball might flicker between 20 and 40 Hz.

• If the batter could perceive this flicker,

then he could tune his mental model and predict more accurately.

04/08/23 72 © 2009 Bahill

Page 73: Zachman Frameworks and Baseball

Column 6, Why (continued)Column 6, Why (continued)• Why does a manager decide to pitch to a famous slugger or

intentionally walk him? In making this decision the manager considers the score, runners on base, batting average, slugging average, etc. (BRJ 2004); column 6 (why), row 4 (technical model).

• General Managers trade players in order to have a winning season within their constraints. They are motivated by their drive for success; column 6 (why), row 3 (system model).

• What motivates major league baseball players? Money, prestige, pride; column 6 (motivation), row 2 (business model)

• What motivates baseball team owners? Power, ego, money; column 6 (motivation), row 2 (business model)

• Easton Sports and Hillerich & Bradsby give wooden bats to major league players for free. Why? To build brand image so that they can sell more of their regular sports equipment; column 6 (motivation), row 2 (business model)

04/08/23 73 © 2009 Bahill

Page 74: Zachman Frameworks and Baseball

Column 6, Why (continued)Column 6, Why (continued)• The purpose of baseball is entertainment with two major

subdivisions: television and baseball stadiums; column 6 (why), row 1 (scope).

• Gould (2003) explains the intellectual complexity that causes sagacious Americans to be fascinated with baseball; column 6 (why), row 1 (scope).

04/08/23 74 © 2009 Bahill

Page 75: Zachman Frameworks and Baseball

04/08/23 75

A Zachman Framework Populated with Baseball Models Baseball 1. What 2. How 3. Where 4. Who 5. When 6. Why

1. Scope (Commissioner of Baseball)

Equipment rules

Rules of baseball

Stadiums & TV, Leagues & divisions

Revenue sharing, Reserve clause

Chronology Entertainment, Intellectual stimulation

2. Business model (Team Owner)

NCAA bat rules

Define the strike zone

Shared use of stadiums

A-Rod, Olympic teams

Season schedules

Money, Power, Pride; Free Bats

3. System model (General Manager)

Batting practice facilities

Pitch tracker, Stadium instant replay

Placement of home plate

Fantasy baseball, Player contracts, 25-man roster,

Pitching rotations

Wants a winning season

4. Technology model (Team Manager)

Ideal bat weight & weight distribution

Teamwork & signals for hit & run, bunt, etc.

Mental rehearsal & understandings

Weekly statistics, Box scores, Sweet spot

Pitch count Intentional walks, The blame game

5. Detailed representation (Scientist, Engineer, Coach)

A swing, CoP, MoI, CoR

Rising fastball, Eye movement strategies, Speed & spin

Predict where & when, Fielders run curved paths

Players’ physiological state, The count

Mental models, Work fast & change speeds

CFFF, Expect fastball with 3-0 count

6. Real system (Baseball Player)

Baseball bat

One pitch & responses

Baseball field Major league baseball players

Pitch interval

Motivation for decisions

© 2009 Bahill

Page 76: Zachman Frameworks and Baseball

04/08/23 76

Lessons learnedLessons learned

© 2009 Bahill

Page 77: Zachman Frameworks and Baseball

Increasing detailIncreasing detail11

• 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.

04/08/23 77 © 2009 Bahill

Page 78: Zachman Frameworks and Baseball

04/08/23 78

Column 1Row 1

Column 1Row 2

Column 1Row 2

Column 1Row 2

C 1Row 3

C 1Row 3

C 1Row 3

C 1Row 3

C 1Row 3

C 1Row 3

C 1Row 3

C 1Row 3

C 1Row 3

C 1R 4

C 1R 4

C 1R 4

C 1R 4

C 1R 4

C 1R 4

C 1R 4

C 1R 4

C 1R 4

C 1R 4

C 1R 4

C 1R 4

C 1R 4

C 1R 4

C 1R 4

C 1R 4

C 1R 4

C 1R 4

C 1R 4

C 1R 4

C 1R 4

C 1R 4

C 1R 4

C 1R 4

C 1R 4

C 1R 4

C 1R 4

C1R5

C 1R 5

C 1R 5

C 1R 5

C 1R 5

C 1R 5

C 1R 5

C 1R 5

C 1R 5

© 2009 Bahill

Page 79: Zachman Frameworks and Baseball

Other sliversOther 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

04/08/23 79 © 2009 Bahill

Page 80: Zachman Frameworks and Baseball

HierarchyHierarchy• 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.

04/08/23 80 © 2009 Bahill

Page 81: Zachman Frameworks and Baseball

Granularity, row 6, real systemGranularity, row 6, real system• What: the baseball bat

• How: one pitch and responses

• Where: the baseball field

• Who: major league baseball players

• Time: the pitch interval*

• Why: motivation for decisions

• Are these six things at equivalent levels of detail?

04/08/23 81 © 2009 Bahill

Page 82: Zachman Frameworks and Baseball

Granularity, row 1, scopeGranularity, row 1, scope**

• What: Equipment rules• How: Rules of baseball, in particular the strike

zone• Where: Baseball is played in stadiums and

broadcast on television• Who: Commissioner of Baseball coordinates the

teams; Major League Baseball Players Association and players’ agents orchestrate players’ activities

• When: Chronology; decisions about interleague play, playoff structure, world series dates

• Why: The purpose of baseball is entertainment

04/08/23 82 © 2009 Bahill

Page 83: Zachman Frameworks and Baseball

To help with granularityTo help with granularity• you should consider time scales as well as

perspectives and roles, e. g. • row 1 -- a few years• row 2 -- seasonal events• row 3 -- one game• row 4 -- one at-bat• row 5 -- one swing

04/08/23 83 © 2009 Bahill

Page 84: Zachman Frameworks and Baseball

Modeling generalitiesModeling 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 Zachman’s 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

04/08/23 84 © 2009 Bahill

Page 85: Zachman Frameworks and Baseball

04/08/23 85

Catcher Pitcher Umpire Batter Fielder

Pitch Ball

Predict When and

Where

Decide if Ball or Runner Got to the Base First

Run to First Base

Field Ball and Throw to

Appropriate Base

Give Sign to Pitcher

Wait for Batter

[yes]

[no]

Fork

Swing Bat?

Ball Hit?

[yes][no]

Merge

Fork

Join

{joinSpec = Runner OR Ball}

Catch Ball & Return it to

Pitcher

Signal Ready

Terry BahillSummer 2007

Runner Ball

Decision

Call Ball, Strike, Out, Walk or

Other

Other could be batterhit by pitch, foul ball with two strikes, catcher interference, time-out called before pitch, etc.

There could also be decisions for fair or foul andfly or grounder.

Umpire is a role that can be filled by one (for the minors in Little League) to six (for World Series games) people.

© 2009 Bahill

Page 86: Zachman Frameworks and Baseball

LevelsLevels11

• 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?

04/08/23 86 © 2009 Bahill

Page 87: Zachman Frameworks and Baseball

LevelsLevels22

• 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?

04/08/23 87 © 2009 Bahill

Page 88: Zachman Frameworks and Baseball

04/08/23 88

For the batter in the activity diagramFor the batter in the activity diagramHere is a class diagram at the

appropriate level

Here is a class diagram at the wrong level Batter (low level)

Count, OutsMentalModelsGameSituationSignals

predictWhenpredictWhereswingtakePitchbunt

talkToPresstalkWithAgentdealWithOwnertakeDrugTest

Batter (high level)ExperienceSalaryPhysiologyCompetition

© 2009 Bahill

Page 89: Zachman Frameworks and Baseball

04/08/23 89

1

1.1 1.31.2

1.3.2 1.3.31.3.1

1.3.1.2 1.3.1.31.3.1.1

20

No skip level links

No skip level links

© 2009 Bahill

Page 90: Zachman Frameworks and Baseball

InteroperabilityInteroperability• 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.

04/08/23 90 © 2009 Bahill

Page 91: Zachman Frameworks and Baseball

The right toolThe right toolThere is no correct modeling technique for any particular cell. For each cell, you should use which ever modeling tool is most appropriate, e. g.,

physical analogs, analytic equations, state machines, functional flow block diagrams, block diagrams of linear systems theory, transfer functions, state space models, differential or difference equations, object-oriented models, UML diagrams, SysML, Monte Carlo, statistical distributions, animations, mathematical programming, Markov processes, time-series models, financial models, Pert charts, Gantt charts, computer programs, use cases, mental models, tradeoff studies ...

04/08/23 91 © 2009 Bahill

Page 92: Zachman Frameworks and Baseball

Top-down or bottom-up?Top-down or bottom-up?• We discussed the models from bottom to top.

That is the way they were derived: in basic research, new models build on previous research.

• In designing systems, better results will usually be obtained with a top-down approach.

• Architects and Systems Engineers start at the top and work down.

• Discipline engineers usually start at the bottom and work up.

• Software engineers often start in the middle with use cases, objects and class diagrams.

• This means that different people might be working at different levels.

04/08/23 92 © 2009 Bahill

Page 93: Zachman Frameworks and Baseball

Column orderColumn 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.

04/08/23 93 © 2009 Bahill

Page 94: Zachman Frameworks and Baseball

Which cells are most important?Which cells are most important?• To increase the performance of baseball players,

the lower-left cells are the most important and the upper-right cells are least important.

UML diagrams are also most useful in the lower-left corner.

• A CEO would be most interested in the top rows and in particular the upper-right corner*

04/08/23 94 © 2009 Bahill

Page 95: Zachman Frameworks and Baseball

On which rows should you focus?On which rows should you focus?• Rows 1 and 2 are the domain of the President,

CEO, board of directors and rule making organizations.

• Rows 3 and 4 are owned by managers.• Row 5 tasks are performed by the worker bees.

04/08/23 95 © 2009 Bahill

Page 96: Zachman Frameworks and Baseball

04/08/23 96

Four collections of papersFour collections of papersNumber of Papers with Primary Emphasis in Each Cell 1.

What 2.

How 3.

Where 4.

Who 5.

When 6.

Why 1. Scope 1 1 2. Business model

5 1

3. System model

5 9 4 1

4. Technology model 12 34 8 2

5. Detailed representation

135 70 8 8 2 1

6. Real system

© 2009 Bahill

Page 97: Zachman Frameworks and Baseball

Classify this talkClassify this talk**

• Given that we are studying Modeling and Simulation in the Enterprise, in which row and column should this talk be placed?

• Who would pay for developing a framework such as this?

04/08/23 97 © 2009 Bahill

Page 98: Zachman Frameworks and Baseball

Purpose?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

04/08/23 98 © 2009 Bahill

Page 99: Zachman Frameworks and Baseball

To understand simulation To understand simulation in a particular companyin a particular company• The company could create a database and

answer these questions for each model and simulation they have created.

Purpose? Owner? Architecture? Inputs? Outputs? Functions? Interfaces? Interacts with? Cost? Business case? Level? Who? What? When? Where? Why? How? Standard (e.g. UML, RUP, CORBA)? Zachman row? Zachman column?

• Reduce the number of classes using affinity analysis.

• Abstract this into a metamodel that shows how that company does modeling and simulation.

04/08/23 99 © 2009 Bahill

Page 100: Zachman Frameworks and Baseball

Zachman and DoDAFZachman and DoDAF• The Zachman framework is very useful for

understanding existing enterprises.• DoDAF is intended to help document new

systems of complex systems. It is not requirements based. It is based on operational capabilities, so it

might be related to use cases.

04/08/23 100

© 2009 Bahill

Page 101: Zachman Frameworks and Baseball

DoDAF’s four viewsDoDAF’s four views• Operational View (OV), a description of the tasks,

activities, operational elements and information exchanges required to accomplish DoD missions.

• Systems and Services View (SV), a description of systems and interconnections supporting DoD functions.

• Technical Standards View (TV), rules governing arrangement, interaction and interdependence of system parts or elements, whose purpose is to ensure that a conformant system satisfies a specified set of requirements.

• All View (AV), information pertinent to the entire architecture. AV products set the scope and context of the architecture.

04/08/23 101

© 2009 Bahill

Page 102: Zachman Frameworks and Baseball

All View (AV) productsAll View (AV) products• All View (AV) products provide overarching

descriptions of the entire architecture and define the scope and context of the architecture. The AV products are

• AV-1 Overview and Summary Information* • AV-2 Integrated Dictionary

04/08/23 102

© 2009 Bahill

Page 103: Zachman Frameworks and Baseball

Operational View (OV) productsOperational View (OV) products• OV-1 High Level Operational Concept Graphic • OV-2 Operational Node Connectivity Description • OV-3 Operational Information Exchange Matrix • OV-4 Organizational Relationships Chart • OV-5 Operational Activity Model • OV-6a Operational Rules Model • OV-6b Operational State Transition Description • OV-6c Operational Event-Trace Description • OV-7 Logical Data Model

04/08/23 103

© 2009 Bahill

Page 104: Zachman Frameworks and Baseball

Product Product descriptionsdescriptions

Table 2-1: List of Products, DoDAF version 1.5Applicable View, Product, Product Name, General DescriptionAll View AV-1 Overview and Summary Information Scope, purpose, intended users, environment depicted, analytical findingsAll View AV-2 Integrated Dictionary Architecture data repository with definitions of all terms used in all productsOperational OV-1 High-Level Operational Concept Graphic High-level graphical/textual description of operational conceptOperational OV-2 Operational Node Connectivity Description Operational nodes, connectivity, and information exchange need lines between nodesOperational OV-3 Operational Information Exchange Matrix Information exchanged between nodes and the relevant attributes of that exchangeOperational OV-4 Organizational Relationships Chart Organizational, role, or other relationships among organizationsOperational OV-5 Operational Activity Model Capabilities, operational activities, relationships among activities, inputs, and outputs; overlays can show cost, performing nodes, or other pertinent informationOperational OV-6a Operational Rules Model One of three products used to describe operational activity — identifies business rules that constrain operationOperational OV-6b Operational State Transition Description One of three products used to describe operational activity — identifies business process responses to eventsOperational OV-6c Operational Event-Trace Description One of three products used to describe operational activity — traces actions in a scenario or sequence of eventsOperational OV-7 Logical Data Model Documentation of the system data requirements and structural business process rules of the Operational ViewSystems and Services SV-1 Systems Interface DescriptionIdentification of systems nodes, systems, system items, services, and service items and their interconnections, within and between nodesSystems and Services SV-2 Systems Communications DescriptionSystems nodes, systems, system items, services, and service items and their related communications laydownsSystems and Services SV-3 Systems-Systems Matrix, Services-Systems Matrix, Services-Services MatrixRelationships 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 functionsSystems and Services SV-4b Services Functionality Description Functions performed by services and the service data flow among service functionsSystems and Services SV-5a Operational Activity to Systems Function Traceability MatrixMapping of system functions back to operational activitiesSystems and Services SV-5b Operational Activity to Systems Traceability MatrixMapping of systems back to capabilities or operational activitiesSystems and Services SV-5c Operational Activity to Services Traceability Matrix Mapping of services back to operational activitiesSystems 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 exchangeSystems 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 implementationSystems 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 architectureSystems 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 implementationSystems and Services SV-10b Systems State Transition Description, Services State Transition Description One of three products used to describe system and service functionality—identifies responses of a system/service to eventsSystems 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 ViewSystems and Services SV-11 Physical Schema Physical implementation of the Logical Data Model entities, e.g., message formats, file structures, physical schemaTechnical Standards TV-1 Technical Standards Profile Listing of standards that apply to Systems and Services View elements in a given architectureTechnical Standards TV-2 Technical Standards ForecastDescription of emerging standards and potential impact on current Systems and Services View elements, within a set of time frames04/08/23 10

4© 2009 Bahill

Page 105: Zachman Frameworks and Baseball

Systems & Services View productsSystems & Services View products• SV-1 System Interface Description

• SV-2 Systems Communications Description

• SV-3 Systems-Systems Matrix

• SV-4 Systems Functionality Description

• SV-5 Operational Activity to Systems Functionality Traceability Matrix*

• SV-6 Systems Data Exchange Matrix

• SV-7 Systems Performance Parameters Matrix

• SV-8 Systems Evolution Description

• SV-9 Systems Technology Forecast

• SV-10a Systems Rules Model

• SV-10b Systems State Transition Description

• SV-10c Systems Event-Trace Description

• SV-11 Physical Schema

04/08/23 105

© 2009 Bahill

Page 106: Zachman Frameworks and Baseball

Technical Standards View (TV)Technical Standards View (TV)• The TV products define technical standards,

implementation conventions, business rules and criteria that govern the architecture. The TV products are

• TV-1 Technical Standards Profile • TV-2 Technical Standards Forecast

04/08/23 106

© 2009 Bahill

Page 107: Zachman Frameworks and Baseball

04/08/23 107

AV-1 OV-1

OV-5 OV-2

AV-2

OV-4

SV-4

SV-1

SV-2 TV-1

DoD Framework Products

Documents

Legend

Models

SV-8 SV-9

TV-2

Forecast

SV-10c

SV-10b

OV-6cOV-6b

Scenario

OV-7

SV-11

Data

OV-6a

SV-10a

Rules

OV-3

SV-5

SV-6

SV-3 SV-7

Matrices

© 2009 Bahill

Page 108: Zachman Frameworks and Baseball

Compared to our design process, Compared to our design process, DoDAF is missingDoDAF is missing• Document 2: Customer Requirements• Document 3: Derived Requirements• Document 4: System Test and Validation• Document 5: Concept Exploration• Tradeoff Matrix and Sensitivity Analysis• Schedule and Budget• Technical Analysis• Risk Management

04/08/23 108

© 2009 Bahill

Page 109: Zachman Frameworks and Baseball

Compared to DoDAF, Compared to DoDAF, our design process is missing our design process is missing • Operational OV-6a Operational Rules Model • Operational OV-6b Operational State Transition

Description • Operational OV-6c Operational Event-Trace

Description • Technical Standards TV-1 Technical Standards

Profile • Technical Standards TV-2 Technical Standards

Forecast• Wymore includes technical standards in the

Technology Requirement.

04/08/23 109

© 2009 Bahill

Page 110: Zachman Frameworks and Baseball

PurposePurpose11

• 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

04/08/23 110

© 2009 Bahill

Page 111: Zachman Frameworks and Baseball

PurposePurpose22

• 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.

04/08/23 111

© 2009 Bahill

Page 112: Zachman Frameworks and Baseball

StrengthsStrengths• DoDAF:

organized descriptive extensive product relationships identifies duplicate functions accepted DoD standard

• Zachman organized intuitive breath of coverage

04/08/23 112

© 2009 Bahill

Page 113: Zachman Frameworks and Baseball

DrawbacksDrawbacks• DoDAF

Cumbersome Inflexible Ponderous and hard to learn

• Zachman Elementary Does not prescribe

design tradeoffsdesign rationaledocumentation of architecture decisions

04/08/23 113

© 2009 Bahill

Page 114: Zachman Frameworks and Baseball

Zachman summaryZachman summary11

• 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 organization’s vision and mission statements

• Cells in a row should be at similar levels of detail (granularity)

04/08/23 114

© 2009 Bahill

Page 115: Zachman Frameworks and Baseball

Zachman summaryZachman summary22

• 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.

04/08/23 115

© 2009 Bahill

Page 116: Zachman Frameworks and Baseball

04/08/23 116

© 2009 Bahill

Page 117: Zachman Frameworks and Baseball

Seminar materialsSeminar materials• A ball• Perhaps the two-seam and four-seam video

04/08/23 117

© 2009 Bahill

Page 118: Zachman Frameworks and Baseball

How to print (in old MS Office)How to print (in old MS Office)• To print this file, do this one time.• Pick the View menu• Chose Color/grayscale• Grayscale• Settings• Light grayscale• Close grayscale view

04/08/23 118

© 2009 Bahill