appendix a human view data for the commander daily update brief …978-3-030-11629... ·...

Appendix AHuman View Data for the Commander’sDaily Update Brief Example

A.1 Introduction

The original Human Viewpoint described a set of outcome products similar to otherarchitecture viewpoints at the time. These products were diagrams, tables, figures orother descriptions of human focused data. In the context of today’s HumanViewpoint, these products are equivalent to the data tables used to collect thehuman focused data that can then be rendered in different models, providing theindividual Human Views. This appendix presents a comprehensive example of thehuman view data from the Commander’s Daily Update Brief Process(NATO 2010).

A.2 Example

The Commander’s Daily Update Brief is an operational brief that provides updatesregarding the readiness and operational assets throughout the command, with afocus on the previous 24 hours and the next 24 hours. A Commander’s DailyUpdate Brief Process is in place in virtually every US military command. The staffprocess that produces the brief includes analyzing data sources, creating MicrosoftPower Point slides, and numerous review cycles. Historically, the production of thebrief has been a manual, staff intensive process that often resulted in static infor-mation which was often several hours old. Prior to the implementation of theIntegrated Interactive Data Briefing Tool (IIDBT), this process consumed staffmembers working the night shift, while the day shift’s personnel devoted themorning hours to its production (Pester-DeWan et al. 2003). The IIDBT automatedthe data gathering process using Web services that pull data directly from

© Springer Nature Switzerland AG 2019H. A. H. Handley, The Human Viewpoint for System Architectures, Topics in Safety,Risk, Reliability and Quality 35, https://doi.org/10.1007/978-3-030-11629-3

151

https://doi.org/10.1007/978-3-030-11629-3

authoritative sources; the automation of these formerly manual processes saved thestaff an estimated 3.5 h a day while at the same time allowing them to present morecurrent information (Higgins and Hall 2004). While production time was cut sig-nificantly, the process is still largely stove-piped along functional area divisions.Coalescing the information for the brief typically requires 15–20 people andnumerous reviewers from various functional areas to create a series of Power Pointslides that are organized into a single presentation that is catered to the comman-der’s information requirements (Handley and Heacox 2005).

A.3 Concept

The Concept provides the different conditions under which the process will beexamined and defines the outcomes to be measured. For this example, the area ofconcern is the performance of the briefing process with and without the IIDBTunder different conditions of operational tempo, i.e., the rate at which information isavailable, and levels of connectivity, i.e., the number of communication channelsavailable for information exchange. The Concept data is shown in Table A.1.

A.4 Tasks

The Tasks data decomposes higher level activities into discrete tasks that can beassigned to roles. In Table A.2, the top row is the high-level activities, and eachassociated column is the decomposed set of tasks required to accomplish theactivity.

Additionally, a second set of data was collected that identifies the systeminterfaces that are required by the tasks. Table A.3 identifies the systems requiredby the high-level activities. This is important for the stakeholder evaluation of theIIDBT system.

Table A.1 Concept data for Commander’s Daily Update Brief

Process with IIDBT Process without IIDBT Performancemeasure

Operationaltempo

Connectivity Operationaltempo

Connectivity Brief completiontime

Low Low Low Low

Low High Low High

High Low High Low

High High High High

152 Appendix A: Human View Data for the Commander’s Daily Update …

Table A.2 Task decomposition for Commander’s Daily Update Brief

1.0 Identifynewinformationfor assignedtopics

2.0 Createassignedslides

3.0 Approveslides at celllevel

4.0 Compilethe briefingform postedslides

5.0Approveslides atcommandlevel

6.0 Briefcommanderand staff

Select topicsfor briefingcontent

Obtaintemplates forbriefing

Advisereviewers ofreadiness

Access slidesposted byassigned cells

Advisereviewers ofreadiness

Send link forcollaborativesession

Reviewpreviouslysubmitted data

Import data Reviewslides

Assess if allslides havebeen posted

Reviewslides

Accesssession

Identify datasources forrelevantupdates

Create slide Provideupdates andcomments

Notifyappropriatecell staff thatslides are due

Provideupdates andcomments

Initiatecollaborativesession

Accesssources andidentifyinformation

Revise slidesand notes

Reviewcomments

Access statusof requestedslides

Reviewcomments

Take roll call

Assesscurrency ofinformation

Assess needfor more info

Notify BWCto proceedwithout slides

Access andrevise slides

Present thebrief

Assessaccuracy offields andspelling

Accesssources andidentify newinformation

Arrangeposted slidesin order forbriefing

Postreviewedslides

Discussissues andimplications

Revise slidefields andspelling

Import data Ensureorder andcontent ofpostedslides

Determineaction items

Assess needto makechanges tonotes

Assess needto makechanges toslides

Distributeaction items

Revise slidenotes

Access andrevise slides

Assess needfor sharingwith foreignpartners

Postreviewedslides

Assesscompliancewithdisclosurepolicies

Postcompletedslide

Appendix A: Human View Data for the Commander’s Daily Update … 153

Tab

leA.3

System

interfacematrixforCom

mander’sDaily

Upd

ateBrief

Tasks

System

Crisisactio

npage

Digital

ROE

SIPR

NET

Electronic

book

marks

IIDBT

Shared

folder

Email

Same

time

1.1Select

topics

forbriefing

content

xx

1.2Review

previously

subm

itted

data

x

1.3Identifydata

sourcesforrelevant

updates

x

1.4Accesssourcesandidentify

inform

ation

xx

2.1Obtaintemplates

forbriefing

x

2.2Im

portdata

x

2.3Createslide

x

2.4Reviseslides

andno

tes

x

2.7Reviseslidefields

andspellin

gx

2.9Reviseslideno

tes

x

2.11

Assesscomplianceof

data

with

disclosure

policies

x

2.12

Postcompleted

slide

x

3.1Adv

isereview

ersof

readiness

x

3.2Review

slides

x

3.3Prov

ideup

datesandcomments

x

3.4Review

comments

x

3.6Accesssourcesandidentifynew

inform

ation

xx

3.7Im

portdata

x

3.9Accessandrevise

slides

x(con

tinued)


Tab

leA.3

(con

tinued)

Tasks

System

Crisisactio

npage

Digital

ROE

SIPR

NET

Electronic

book

marks

IIDBT

Shared

folder

Email

Same

time

3.10

Postreview

edslides

x

4.1Accessslides

posted

byassign

edcells

x

4.3Notifyapprop

riatecellstaffthatslides

aredu

ex

4.5NotifyBWCto

proceedwith

outslid

esx

4.6Arrange

posted

slides

inorderfor

briefing

x

5.1Adv

isereview

ersof

readiness

x

5.2Review

slides

x

5.3Prov

ideup

datesandcomments

x

5.4Review

comments

x

5.5Accessandrevise

slides

x

5.6Po

streview

edslides

x

5.7Ensureorderandcontentof

posted

slides

x

6.2AccessSession

x

6.3InitiateCollabo

rativ

esession

x

6.4Takerollcall

x

6.5Presentthebrief

x

6.6Discuss

issues

andim

plications

x

6.7Determineactio

nitems

x

6.8Distributeactio

nitems

x


A.5 Roles

The Roles table defines the roles for the Commander’s Daily Update Brief process.Table A.4 lists the roles required by this process with some associated attributessuch as multiplicity, competency and authority.

The role to task assignment matrix allocates task responsibilities to the differentroles, as shown in Table A.5. This table indicates the role responsibilities for theprocess tasks. Note that some tasks are assigned to role “teams” while others areassigned to individual roles.

A.6 Training

For the Commander’s Daily Update Brief example, the Training data focuses on therequired qualifications for personnel to assume the defined roles. These qualifica-tions, which include rank, military designator, clearance level and location, areshown in Table A.6.

A.7 Human Network

The Human Network data focuses on the information exchange requirementsbetween the roles to support task completion. Roles that need to exchange infor-mation, along with the systems that are used, are shown in Table A.7.

A.8 Metrics

Human performance objectives, indicators and risks associated with specific tasks areidentified in Table A.8. The Metrics data are used in the evaluation of alternativeinstantiations of the process under the different technical conditions of the concept.

A.9 Summary

This example presents the different sets of data that can be collected to support aHuman Viewpoint development. In the original Human Viewpoint description,these tables would have been considered outcome products. With the evolution ofthe Human Viewpoint, these tables now provide the data to render relevant modelsto support the Human Viewpoint analysis.


Tab

leA.4

Roles

forCom

mander’sDaily

Upd

ateBrief

Title

Multip

licity

Team

Com

petency

Autho

rity

Com

mander

Individu

alGW36

—gu

idingdirecting,

andmotivatingsubo

rdinates

Level

0

Directorof

manpo

wer

andperson

nel

Individu

alCelld

irectors

GW36

—gu

idingdirecting,

andmotivatingsubo

rdinates

Level

1

Upd

atedevelopm

entstaff

Group

CFM

CCstaff

GW09

—analyzingdata

orinform

ation

Level

2

Directorof

intelligence

Individu

alCelld

irectors

GW36

—gu

idingdirecting,

andmotivatingsubo

rdinates

Level

1

Upd

atedevelopm

entstaff

Group

CFM

CCstaff

GW09

—analyzingdata

orinform

ation

Level

2

Specialsecurity

officer

Individu

alGW07

—evaluatin

ginform

ationto

determ

inecompliancewith

standards

Level

2

Directorof

operations

Individu

alCelld

irectors

GW33

—coordinatin

gtheworkandactiv

ities

ofothers

Level

1

Upd

atedevelopm

entstaff

Group

CFM

CCstaff

GW09

—analyzingdata

orinform

ation

Level

2

Current

operations

(COPS

)Individu

alGW26

—commun

icatingwith

supervisors,peers,or

subo

rdinates

Level

2

Battle

watch

captain(BWC)

Individu

alGW26

—commun

icatingwith

supervisors,peers,or

subo

rdinates

Level

2

Directorof

logistics

Individu

alCelld

irectors

GW36

—gu

idingdirecting,

andmotivatingsubo

rdinates

Level

1

Upd

atedevelopm

entstaff

Group

CFM

CCstaff

GW09

—analyzingdata

orinform

ation

Level

2

Directorof

planning

Individu

alCelld

irectors

GW36

—gu

idingdirecting,

andmotivatingsubo

rdinates

Level

1

Upd

atedevelopm

entstaff

Group

CFM

CCstaff

GW09

—analyzingdata

orinform

ation

Level

2

Directorof

C4I

Individu

alCelld

irectors

GW36

—gu

idingdirecting,

andmotivatingsubo

rdinates

Level

1

Upd

atedevelopm

entstaff

Group

CFM

CCstaff

GW09

—analyzingdata

orinform

ation

Level

2

Directorof

training

Individu

alCelld

irectors

GW36

—gu

idingdirecting,

andmotivatingsubo

rdinates

Level

1

Upd

atedevelopm

entstaff

Group

CFM

CCstaff

GW09

—analyzingdata

orinform

ation

Level

2

Directorof

experimentatio

nIndividu

alCelld

irectors

GW36

—gu

idingdirecting,

andmotivatingsubo

rdinates

Level

1

Upd

atedevelopm

entstaff

Group

CFM

CCstaff

GW09

—analyzingdata

orinform

ation

Level

2


Tab

leA.5

Taskrespon

sibilitymatrixforCom

mander’sDaily

Upd

ateBrief

Tasks

Respo

nsibility

Director

operations

CFM

CC

staff

Cell

directors

Specialsecurity

officer

Battle

watch

captain

COPS

Rem

ote

staff

Com

mander

1.1Select

topics

forbriefing

content

x

1.2Review

previously

subm

itted

data

x

1.3Identifydata

sourcesforrelevant

updates

x

1.4Accesssourcesandidentify

inform

ation

x

2.1Obtaintemplates

forbriefing

x

2.2Im

portdata

x

2.3Createslide

x

2.4Reviseslides

andno

tes

x

2.5Assesscurrency

ofinform

ation

x

2.6Assessaccuracy

offields

andspellin

gx

2.7Reviseslidefields

andspellin

gx

2.8Assessneed

tomakechangesto

notes

x

2.9Reviseslideno

tes

x

2.10

Assessneed

forsharingwith

foreign

partners

x

2.11

Assesscomplianceof

data

with

disclosure

policies

x

2.12

Postcompleted

slide

x

3.1Adv

isereview

ersof

readiness

x

3.2Review

slides

x

3.3Prov

ideup

datesandcomments

x(con

tinued)


Tab

leA.5

(con

tinued)

Tasks

Respo

nsibility

Director

operations

CFM

CC

staff

Cell

directors

Specialsecurity

officer

Battle

watch

captain

COPS

Rem

ote

staff

Com

mander

3.4Review

comments

x

3.5Assessneed

formoreinfo

x

3.6Accesssourcesandidentifynew

inform

ation

x

3.7Im

portdata

x

3.8Assessneed

tomakechangesto

slides

x

3.9Accessandrevise

slides

x

3.10

Postreview

edslides

x

4.1Accessslides

posted

byassign

edcells

x

4.2Assessifallslides

have

been

posted

x

4.3Notifyapprop

riatecellstaffthatslid

esaredu

ex

4.4Accessstatus

ofrequ

estedslides

x

4.5NotifyBWC

toproceedwith

out

slides

x

4.6Arrange

posted

slides

inorderfor

briefing

x

5.1Adv

isereview

ersof

readiness

x

5.2Review

slides

x

5.3Prov

ideup

datesandcomments

x

5.4Review

comments

x

5.5Accessandrevise

slides

x(con

tinued)


Tab

leA.5

(con

tinued)

Tasks

Respo

nsibility

Director

operations

CFM

CC

staff

Cell

directors

Specialsecurity

officer

Battle

watch

captain

COPS

Rem

ote

staff

Com

mander

5.6Po

streview

edslides

x

5.7Ensureorderandcontentof

posted

slides

x

6.1Send

linkforcollabo

rativ

esession

x

6.2Accesssession

xx

xx

x

6.3Initiatecollabo

rativ

esession

x

6.4Takerollcall

x

6.5Presentthebrief

x

6.6Discuss

issues

andim

plications

x

6.7Determineactio

nitems

x

6.8Distributeactio

nitems

x


Tab

leA.6

Rolerequ

irem

entsforCom

mander’sDaily

Upd

ateBrief

Cod

eTitle

Rank

Designator

Clearance

Location

J00

Com

mander(CDR)

O-9

1310

TS

Afloat

J1Directorof

manpo

wer

andperson

nel

O-5

1315

SAshore

J2Directorof

intelligence

O-6

1630

TS/SC

IAshore

SSO

Specialsecurity

officer

E-6

CTA

TS/SC

IAshore

J3Directorof

operations

(OPS

)O-6

1110

TS/SC

IAfloat

J33

Current

operations

(COPS

)O-5

1147

TS

Afloat

BWC

Battle

watch

captain

O-4

1320

TS

Afloat

J4Directorof

logistics

O-6

3100

SAshore

J5Directorof

planning

O-5

1310

TS

Afloat

J6Directorof

C4I

O-6

1120

TS

Ashore

J7Directorof

training

O-5

1310

SAshore

J9Directorof

experimentatio

nO-6

1320

TS

Ashore


Tab

leA.7

Inform

ationcoordinatio

nforCom

mander’sDaily

Upd

ateBrief

Operatio

ns/Tasks

inthisactiv

ityTechnology/Applications

Inform

ationflo

w

From

To

1.1Select

topics

forbriefing

content

Rou

tine:

CASWeb

(Battle

Rhy

thm)Sp

ecial:e-mail,chat

OPS

CFM

CCStaff

1.2Review

previously

subm

itted

data

CASWeb

(view

previous

posting),e-mail,chat

(CFM

CCStaffworkin

progress)

1.3Identifydatasourcesforrelevant

updates

DISA

Federatedor

othersearch

tool,electronic

bookmarks,e-mail,chat

(CFM

CCStaffworkin

progress)

1.4Accesssourcesandidentifyinform

ation

DISA

Federatedtool,SIPR

NET

(CFM

CCStaffworkin

progress)

2.1–2.3Im

portdata

into

templates

(CFM

CCStaffworkin

progress)

2.4–2.9Ensureaccuracy

ofinform

ationand

presentatio

n,andpostupdatedinfo

IIDBT,Po

werPo

int,Cell’sprivateshared

folders,Pu

blic

shared

folders

(CFM

CCStaffworkin

progress)

2.10

Assessneed

forsharingwith

foreign

partners

e-mail,chat

CFM

CCStaff

SSO

2.11

Assesscomplianceof

data

with

disclosure

policies

Public

shared

folders,e-mailchat

SSO

CFM

CCStaff

2.12

Postcompleted

slide

DISA

Federatedor

othersearch

tool,electronic

bookmarks,e-mail,chat,

Public

shared

folders,SIPR

NET,IIDBT,Cell’sprivateshared

folders

(CFM

CCStaffworkin

progress)

3.1Advisereview

ersof

readiness

e-mail,chat

CFM

CCStaff

CellDirector

3.2–3.3Condu

ctcell-levelreview

and

providefeedback

Public

shared

folders,e-mail,chat

CellDirector

CFM

CCStaff

3.4–3.10

Review

feedback,revise

materials

perreview

asnecessaryandre-post

DISA

Federatedor

othersearch

tool,electronic


Public

shared

folders,SIPR

NET,IIDBT,Cell’sprivateshared

folders

(CFM

CCStaffworkin

progress)

4.1–4.2Assessifrequ

ired

materialhasbeen

posted

Public

shared

folders

(BWCworkin

progress)

4.3Requestadditio

nalmaterials

e-mail,chat

BWC

CFM

CCStaff

4.4–4.5Develop

additio

nalmaterialper

requ

est,re-postandno

tify

DISA

Federatedor

othersearch

tool,electronic


Cell’sprivateshared

folders,Pu

blic

shared

folders,SIPR

NET,IIDBT

CFM

CCStaff

BWC

(con

tinued)


Tab

leA.7

(con

tinued)

Operatio

ns/Tasks

inthisactiv

ityTechnology/Applications

Inform

ationflo

w

From

To

4.6Arrange

posted

slides

inorderfor

briefing

andno

tifyreview

ers

Public

shared

folders,e-mail,chat

BWC

CellDirectors

5.1–5.3Condu

ctcommand-levelreview

and

providefeedback

Public

shared

folders,e-mail,chat

CellDirectors

CFM

CCstaff,

(copyBWC)

5.4–5.5Review

feedback,revise

materials

perreview

asnecessary,

re-postandno

tify

DISA

Federatedor

othersearch

tool,electronic


Cell’sprivateshared

folders,Pu

blic

shared

folders,SIPR

NET,IIDBT

CFM

CCStaff

BWC

5.6–5.7Finalizeandpostmaterialfor

briefing

Public

shared

folders,CASWeb,e-mail,chat

BWC

COPS

6.1Send

linkforcollabo

rativ

esession

e-mail,chat

COPS

OPS

,Cells,C

DR,

Rem

otes,BWC

6.2Accesssession

VOIP/VTC,CASWeb,Same-Tim

e,IW

S,e-mail,chat

OPS

,Cells,

CDR,Rem

otes,

BWC

COPS

6.3Initiatecollaborativ

esession

VOIP/VTC,Same-Tim

e,IW

SCOPS

OPS

,Cells,C

DR,

Rem

otes,BWC

6.4Takerollcall

VOIP/VTC,Same-Tim

e,IW

SBWC

OPS

,Cells,C

DR,

Rem

otes,COPS

6.6–6.7Presentthebrief,discuss

implications


e,IW

SOPS

,Cells,

Rem

otes

CDR

6.7DetermineCOA


e,IW

SCDR

OPS

,Cells,

Rem

otes,BWC

6.8Distributedecision/actionitems

e-mail,chat

BWC

OPS

,Cells,

Rem

otes,CDR


Tab

leA.8

Metrics

forCom

mander’sDaily

Upd

ateBrief

Tasks

Objectiv

esIndicators

Risks

1.0Identifynew

inform

ationforassign

edtopics

1.Relevantnew

inform

ationisidentifi

ed;2.

Requestsfor

briefing

,bo

thstandard

andspecialareactedup

on

1.1Select

topics

for

briefing

content

Brief

developm

entisstarted

with

intim

etargets

Missedtriggerto

begin

process

1.3Identifydata

sources

forrelevant

updates

Inform

ationidentifi

edisthe

mostup

-to-date

available

Top

ical

requ

irem

entsare

misun

derstood

1.4Accesssourcesand

identifyinform

ation

Inform

ationidentifi

edis

relevant

tothesituation

Datasourcesareno

taccessible

2.0Createassign

edslides

1.Allavailableinform

ationrequ

ired

torespon

dto

situationis

includ

ed;2.

Preparationiswith

intim

elim

its

2.2Im

portdata

There

isalack

ofconn

ectiv

ityto

sources

2.3Createslide

Inform

ationon

theslideis

relevant

tothesituation

Dataup

datesareno

tim

ported

2.5Assesscurrency

ofinform

ation

Inform

ationon

theslideisthe

mostup

-to-date

available

2.6Assessaccuracy

offields

andspellin

gThe

requ

estforaspecial

form

atismissed

2.12

Postcompleted

slide

Slidepreparationiswith

intim

elim

itsDevelop

mentschedu

leis

notfollo

wed

3.0App

rove

slides

atcell

level

1.Adh

erence

tothedevelopm

entscheduleismaintained;

2.The

review

processresults

inhigh

erqu

ality

slides

3.1Adv

isereview

ersof

readiness

Reviewersareavailablewhen

needed

Reviewersareno

tavailable

3.2Review

slides

Review

isatechnicality

(con

tinued)


Tab

leA.8

(con

tinued)

Tasks

Objectiv

esIndicators

Risks

Requested

slides

arepo

sted

andaccessible

3.3Prov

ideup

datesand

comments

Accuracyof

inform

ationis

improv

ed

3.6Accesssourcesand

identifynew

inform

ation

Inform

ationidentifi

edis

relevant

tothesituation

Datasourcesareno

taccessible

3.10

Postreview

edslides

Slides

arereview

edand

changedwith

intim

etargets

4.0Com

pile

thebriefing

form

posted

slides

1.Adh

erence

tothedevelopm


2.The

compiledbriefcontains

allrequ

estedslides

4.1Accessslides

posted

byassign

edcells

Requested

slides

arepo

sted

andaccessible

Posted

slides

are

inaccessible/incompatib

le

4.3Notifyapprop

riatecell

staffthat

slides

aredu

eMissedtriggerto

begin

briefdevelopm

entprocess

4.4Accessstatus

ofrequ

estedslides

Requested

slides

arepo

sted

andaccessible

4.6Arrange

posted

slides

inorderforbriefing

Brief

iscompleted

with

intim

etargets

5.0App

rove

slides

atcomman

dlevel

1.Adh

erence

tothedevelopm


2.The

review

processresults

inhigh

erqu

ality

slides

5.1Adv

isereview

ersof

readiness

Reviewersareavailablewhen

needed

Reviewersareno

tavailable

5.2Review

slides

Requested

slides

arepo

sted

andaccessible

Review

isatechnicality

5.3Prov

ideup

datesand

comments

Accuracyof

inform

ationis

improv

ed(con

tinued)


Tab

leA.8

(con

tinued)

Tasks

Objectiv

esIndicators

Risks

5.6Po

streview

edslides

Slides

arereview

edand

changedwith

intim

etargets

5.7Ensureorderand

contentof

posted

slides

Brief

iscompiledwith

intim

etargets

6.0Brief

comman

deran

dstaff

1.Briefing

schedu

leismaintained;

2.Com

mandergainsup

todate

SAof

thesituation;

3.Fo

llow-ontasksareassign

ed

6.1Send

Linkfor

collabo

rativ

esession

The

briefiscond

uctedwith

inthetim

etarget

Delayscausethebriefing

tobe

late

6.2AccessSession

Allstaffareableto

access

the

session

Staffareun

able

toaccess

thebrief

6.4Takerollcall

Allrequ

estedstaffarepresent

6.5Presentthebrief

Current

inform

ationis

presented

The

mostcurrent

inform

ationisno

tpresented

6.6Discuss

issues

and

implications

Relevantinform

ationis

presented

6.7Determineactio

nitems

Actionitemsaredeveloped

6.8Distributeactio

nitems

Actionitemsareno

trelayed


References

Handley H, Heacox N (2005) DoDAF products for the commander’s daily update brief process,baseline version. Technical Report, Pacific Science & Engineering, San Diego, CA

NATO (2010) Human systems integration for network centric warfare. Technical Report, NorthAtlantic Treaty Organization Research Technology Organization, TR-HFM-155, Brussels,Belgium

Higgins E, Hall J (2004) The IIDBT meets the demands of modern warfare with speed andaccuracy. Chips Magazine July–September 2004

Pester-DeWan J, Moore R, Morrison J (2003) Knowledge engineering for command and controltransformation. Technical Report, Pacific Science & Engineering, San Diego, CA


Appendix BHuman View SysML Models for Reactto Contact Example

B.1 Introduction

A sample scenario, React to Contact, was used to create a demonstration set ofHuman View models using System Modeling Language (SysML) diagrams. Thiseffort specifically focused on attempting to incorporate all types of SysML diagramsin order to evaluate their utility for use as alternative template options for theHuman View models.

B.2 React to Contact Scenario

The React to Contact scenario is an action sequence that an Army Platoon takes toreturn fire while seeking cover and concealment. The squads are moved by theirleaders to establish firing positions to suppress the enemy. This is done by iden-tifying and assuming a firing position that is conductive to achieving fire superiority(Taylor 2014). The Package Diagram, shown in Fig. B.1, indicates the organizationof the Human View models for this scenario.

The stakeholder interest in the React to Contact scenario is understanding thecognitive and physical aspects of the soldier actions with respect to different rifletypes (Taylor 2014). Table B.1 identifies the different types of physical and cog-nitive actions under consideration (DOA 2007).

© Springer Nature Switzerland AG 2019H. A. H. Handley, The Human Viewpoint for System Architectures, Topics in Safety,Risk, Reliability and Quality 35, https://doi.org/10.1007/978-3-030-11629-3

169

https://doi.org/10.1007/978-3-030-11629-3

B.3 Concept

The Concept view is visualized using a SysML Use Case diagram. It representshow the React to Contact scenario interacts with external entities, i.e., the soldiers.Use Cases are behavior diagrams and represent the highest level of abstraction ofthe system. Figure B.2 shows the Use Case for the Human View Concept. On theleft-hand side is the Use Case with the React to Contact system boundary and theInfantry Platoon as the actor that interacts with the system. On the right-hand side isa decomposition of the first series in the React to Contact process, with the indi-vidual tasks that will occur and the roles that will interact with these tasks.

B.4 Tasks

SysML Activity diagrams represent behavior in terms of the ordering of actionsbased on the availability of inputs, outputs, and controls, and how the actionstransform the inputs to outputs. For the Tasks view, an Activity diagram is used to

pkg Human Viewpoint

RequirementsMetrics

Behavior

Use Case Concept

Activity DiagramTasks

Sequence DiagramHuman Networks

State MachineDynamics

Structure

Block DiagramRoles

Internal Block Diagram Training

ParametricsConstraints

Fig. B.1 Package diagram for “React to Contact” Human Viewpoint

Table B.1 Rifle physical and cognitive actions

Physicalactions

Cognitiveactions

1. Detect targets depending on position, skill in scanning, andability to observe the area and recognize target indicators

X

2. Select position; the position should protect from enemy fire andobservation, yet allow effective fire on targets in the sector of fire

X

3. Determine range to targets X

4. Identify targets in your designated sector of fire X

5. Fire on targets using correct fundamentals of marksmanship andappropriate aiming and engagement techniques

X

170 Appendix B: Human View SysML Models for React to Contact Example

ucR

eact

to C

onta

ct

Infa

ntry

Pl

atoo

n

1. S

oldi

ers

unde

r dire

ct fi

re

imm

edia

tely

retu

rn fi

re a

nd

seek

the

near

est c

over

ed

posi

tions

. Cal

ls o

ut d

ista

nce

and

dire

ctio

n of

dire

ct fi

re.

Rea

ct to

Con

tact

2. E

lem

ent l

eade

rs lo

cate

and

eng

age

know

n or

sus

pect

ed e

nem

y po

sitio

ns

with

ìw

ell-a

imed

î fir

e an

d pa

ss

info

rmat

ion

to th

e un

it le

ader

uc1.

Sol

dier

s un

der d

irect

fire

Infa

ntry

Pl

atoo

n

Seek

Cov

er

1. S

oldi

ers

unde

r dire

ct fi

re

Cov

er

Mov

emen

t

Mov

e Fo

rwar

d

Voic

e C

omm

s

Han

d Si

gnal

s

PSG

MG

PLT

LDR

SL TL

Ret

urn

Fire

Fig.B.2

Use

case

diagram

forHum

anView

concept

Appendix B: Human View SysML Models for React to Contact Example 171

detail the different task processes in the React to Contact scenario. Figure B.3shows the Activity diagrams for “Soldiers under Direct Fire”. For each task, aseparate Activity diagram is included, with the task number, and the actions to beperformed labeled with either Physical Action (PA) or Cognitive Action (CA). Alsonote that the name of the task is given above the diagram, while its referencenumber is used in the title of the diagram.

B.5 Roles

For the Roles view, a SysML Block Definition diagram was used. Block diagramsrepresents structural elements and can include information on their composition andclassification, as well as associations. Block diagrams provide a general-purposecapability to model system components. Figure B.4 uses a Block diagram to showthe relationship of the roles within the Platoon. The Platoon leader commands twosquads, each of which consists of two teams. Additionally, the Platoon leader has astaff of personnel that report directly. The personnel qualifiers are provided beloweach role abbreviation and the legend on the side of the diagram provides the fullrole names.

act 071-326-0608

1. (PA) Ensure the Soldiers you are signaling can see you.

2. (PA) Perform the visual signals for combat formations, Battle drills, and movement techniques.

act 071-326-0510

1. (PA) Shout ìIncoming!î in a loud, recognizable voice.

3. (PA) Seek the nearest appropriate cover.

4. (CA) Assess your situation.

5. (CA) Report your situation to your leader.

2. (CA) React to the instructions of your leader by listening and looking for guidance .

act 071-100-0030

1. (CA) Detect targets using one of several methods .

2. (CA) Select position.

3. (CA). Determine range to targets.

Engage Targets with an M16-Series Rifle/M4 Series Carbine

act 113-571-1022

Perform Voice Communica ons

Use Visual Signaling TechniquesReact to Indirect Fire while Dismounted

act 071-010-0006

1. (PA) Assume a suitable firing position.

2. (PA) Fire the weapon using the correct sight picture.

3. (PA) Fire the Weapon in three-round bursts at the rate of fire appropriate for the target size .

Engage Targets with an M249 Machine Gun

4. (CA) Apply the correct engagement technique based on target types.

4. (PA) Fire on targets using correct fundamentals of marksmanship and appropriate aiming and engagement techniques.

Ac on Types(CA) – Cogni ve Ac on(PA) – Physical Ac on

6. (PA) Continue the mission.

1. (CA) Enter the net.

2. (CA) Send a message.

3. (CA) Leave the net in alphanumeric sequence.

Fig. B.3 Activity diagram for Human View tasks


B.6 Training

A Block diagram was also used to represent the Training requirements based on therequired cognitive and physical competencies. This was rendered as a SysMLInternal Block diagram to represent the interface between a role and the assignedtasks. This is shown in Fig. B.5.

bdd Infantry Platoon

«role»PLT LDR(O2-11A)

«role»PSG

(E7-11B40)

«role»SL1

(E6-11B30)

«role»FO

(E6-13F30)

«role»MG

(E6-11B30)

«role»SL2

(E6-11B30)

«role»TL1

(E6-11B20)

«role»TL2

(E6-11B20)

«role»TL3

(E6-11B20)

«role»TL4

(E6-11B20)

«role»AR

(E4-11B10)

«role»GRN

(E4-11B10)

«role»RFLM

(E4-11B10)

«role»MG

(E6-11B30)

«role»AR

(E4-11B10)

«role»GRN

(E4-11B10)

«role»RFLM

(E4-11B10)

«role»AR

(E4-11B10)

«role»GRN

(E4-11B10)

«role»RFLM

(E4-11B10)

«role»AR

(E4-11B10)

«role»GRN

(E4-11B10)

«role»RFLM

(E4-11B10)

Ac ve Roles for Use CasePLT LDR – Platoon LeaderPSG – Platoon SergeantMG – Machine GunnerSL – Squad LeaderTL – Team LeaderAR – Automa c RiflemanGRN - GrenadierRFLM – RiflemanFO- Forward Observer

Fig. B.4 Block diagram for Human View roles

ibd AR M4 Key Competencies

1. Detection of Targets3. Determine Range of Targets4. Identify Targets

«Competency»Cognitive

«Training»Task 071-100-0030

(Engage Targets with M4)

2. Select Position5. Apply Fundamentals of Marksmanship and Engagement Techniques

«Competency»Physical

«role»AR

(E4-11B10)

2. React to Guidance4. Assess Situation

«Competency»Cognitive

«Training»Task 071-326-0510

(React to Indirect Fire)

3. Seek Appropriate Cover

«Competency»Physical

Fig. B.5 Internal block diagram for Human View training


B.7 Human Network

A SysML Sequence diagram can be used to represent the behavior of a process andthe information exchanged as roles complete tasks. Figure B.6 represents theHuman Networks view using a Sequence diagram. It depicts the sequence of taskscompleted by specific roles for “Soldiers under Direct Fire”. Time runs from top tobottom of the diagram, and the high-level task process is shown on the left-handside of the diagram while the individual tasks are referenced by task number undereach role. The horizontal lines between tasks are the communications that occurbetween the roles.

B.8 Metrics

The SysML Requirements diagram is used for the Metrics view, as shown inFig. B.7. The Requirements diagram represents text-based requirements and theirrelationship with the other model elements. The requirement is expressed in thetop-level block using a text string; the subsequent callouts detail how thatrequirement can be met through the associated metrics. For the React to Contactscenario, the different rifle types evaluated in the scenario will result in differentvalues for the metrics, impacting the overall mission success requirement.

sd Soldier under direct fire

«role»PLT LDR(02-11A)

«role»PSG

(E7-11B40)

«role»MG

(E6-11B30)«role»SL1

(E6-11B30)«role»TL1

(E6-11B20)

071-326-0510

071-010-000607

1-100-0030

113-571-1022

071-326-0502

071-326-0608

«role»AR

(E4-11B10)

«role»GRN

(E4-11B10)

«role»RFLM

(E4-11B10)

Seek Cover

Hand Signals

Cover Movement

Move Forward

Voice Comms

071-326-0510

071-326-0510

071-326-0510

113-571-1022

071-311-2130

071-100-0030

Return Fire

113-571-1022

113-571-1022

113-571-1022

AssessmentAssessment

SituationSituation071-326-0502

071-326-0502

071-326-0608

Fig. B.6 Sequence diagram for Human Network view


B.9 Constraints

The Constraints view is rendered using a SysML Parametric diagram. TheParametric diagram represents real world constraints and is used to support theanalysis of stakeholder concerns. Figure B.8 shows the constraints that indicate thelimiting physical, cognitive and temporal workload of the soldier.

req Soldier Under Direct Fire

Successfully return fire and seek covered position

«requirement»Soldier Under Direct Fire

Probability of Overall Success =95

Factors that impact:1. Rifle Failure Rate2. Soldier Failure due to ...

«requirement»Activity Success Rate

Number of Rounds Fired over Time = 20

Factors that impact:1. Capability of Rifle2. Ability to Reload

«requirement»Productivity

Accuracy of Identifying Environmental Elements = 85

Factors that impact:1. Type of scope2 Night Vision

«requirement»Situation Awareness

Fig. B.7 Requirements diagram for metrics Human View

par AR

parametersWeapon SubsystemHead SubsystemBody Subsystem

constraintsTotal Equipment Weight < 50lbsResults = Distracted

«constraint»Physical Workload

«role»AR

(E4-11B10)

parametersCognitiveVisualAuditoryPsychomotor

ConstraintsTotal Workload < 40Results = Overloaded

«constraint»Cognitive Workload

parametersAlert TimePerforming TimeResting Time

constraintsTotal Hours since last sleep period < 24Results = Fatigued

«constraint»Temporal Workload

Fig. B.8 Parametric diagram for Human View constraints


B.10 Dynamics

A representation of soldier behavior can be depicted using a SysML StateMachine diagram. The diagram represents behavior in terms of transitions betweenstates triggered by events, as shown in Fig. B.9. In this case the diagram repre-sents a soldier’s transition through perception, cognition, and action as a task isexecuted.

B.11 Conclusion

This example completed a rendering of a full set of Human Views using SysMLdiagrams. In this case, a different diagram was chosen for each view to exercise thefull library of SysML diagrams. However, depending on the view content, differentdiagrams may be chosen for each model than illustrated here, and the same diagramtype may be used for multiple views within the same viewpoint. The SysMLimplementations shown are at a rudimentary level in order to evaluate the diagramuse for the view, and may not fully conform to the SysML standard.

Fig. B.9 State diagram for Human View dynamics


References

Taylor A (2014) React to contact, Use case. Version 4.0, US Army Soldier RDEC, Natick, MADOA (2007) The infantry rifleman handbook: common battle drills for all infantry units—TASK:

React to contact (07-3-D9501). Department of the Army Field Manual 3-21.8,Washington, DC


appendix a human view data for the commander daily update brief …978-3-030-11629... ·...

Documents