UNIFIED ARCHITECTURE FRAMEWORK (UAF) HUMAN · PDF fileunified architecture framework (uaf) human views ... the unified architecture framework (uaf) modaf v1.2.004 ... p e r s o n in

UNIFIED ARCHITECTURE FRAMEWORK (UAF) HUMAN VIEWS

Matthew Hause PTC Engineering Fellow

October 2016

2 2

HUMAN FACTORS/PERSONNEL VIEWS - AGENDA

• Background

• Views – Taxonomy – Structure – Connectivity – Processes – States – Interaction – Constraints – Roadmap – Traceability

• Conclusion

3

THE UNIFIED ARCHITECTURE FRAMEWORK (UAF)

MODAF v1.2.004

DoDAF 2.02

change 1

UML profile

based

3.0 IDEAS

based

MODEM

NAF v4.0

DNDAF

Other influences…

DMM

IDEAS brings a high degree of

formality to the domain meta-

model

4

WHY A UNIFIED ARCHITECTURE FRAMEWORK

• Proliferation of frameworks that UPDM was being asked to support

• Need to support industry and federal usage as well as military – Commercialization, whilst still supporting Warfighter needs

• Ability to support other frameworks – By Extension – By Mapping

• IDEAS based format for DMM Allows implementation by non-SysML based tools – Same format as DoDAF 2.02

5

Taxonomy Tx

Structure Sr

Connectivity Cn

Processes Pr

States St

Interaction Scenarios Is

Information If

Parameters Pm

Constraints Ct

Roadmap Rm

Traceability Tr

Metadata Md

Metadata Taxonomy

Md-Tx

Architecture

Viewpoints a Md-Sr

Metadata Connectivity

Md-Cn

Metadata

Processes a Md-Pr

- -

Conceptual Data Model,

Logical Data Model,

Physical schema, real world results

Environment Pm-En

Measurements Pm-Me

Metadata

Constraints a Md-Ct

Metadata

Traceability Md-Tr

Strategic St

Strategic Taxonomy St-Tx

Strategic Structure St-Sr

Strategic Connectivity

St-Cn -

Strategic States St-St

- Strategic Constraints St-Ct

Strategic Deployment, St-Rm Strategic Traceability

St-Tr Stategic Phasing St-Rm

Operational 0p

Operational Taxonomy Op-Tx

Operational Structure Op-Sr

Operational Connectivity

Op-Cn

Operational Processes

Op-Pr

Operational States Op-St

Operational Interaction Scenarios

Op-Is

Operational Constraints

Op-Ct - -

Services Sv

Service Taxonomy Sv-Tx

Service Structure Sv-Sr

Service Connectivity Sv-Cn

Service Processes Sv-Pr

Service States Sv-St

Service Interaction Scenarios

Sv-Is

Service Constraints Sv-Ct

Service Roadmap Sv-Rm

Service Traceability Sv-Tr

Personnel Pr

Personnel Taxonomy Pr-Tx

Personnel Structure Pr-Sr

Personnel Connectivity

Pr-Cn

Personnel Processes Pr-Pr

Personnel States Pr-St

Personnel Interaction Scenarios

Pr-Is

Competence, Drivers, Performance

Pr-Ct

Personnel Availability, Personnel

Traceability Pr-Tr

Personnel Evolution,

Personnel Forecast Pr-Rm

Resources Rs

Resource Taxonomy Rs-Tx

Resource Structure Rs-Sr

Resource Connectivity

Rs-Cn

Resource Processes Rs-Pr

Resource States Rs-St

Resource Interaction Scenarios

Rs-Is

Resource Constraints Rs-Ct

Resource evolution, Resource forecast

Rs-Rm

Resource Traceability Rs-Tr

Security Sc

Security Taxonomy Sc-Tx

Security Structure Sc-Sr

Security Connectivity Sc-Cn

Security Processes - -

Security Constraints - -

Sc-Pr Sc-Ct

Projects Pj

Project Taxonomy Pj-Tx

Project Structure Pj-Sr

Project Connectivity Pj-Cn

- - - - Project Roadmap

Pj-Rm Project Traceability

Pj-Tr

Standards Sd

Standard Taxonomy Sd-Tx

Standards Structure Sd-Sr

- - - - - Standards Roadmap

Sr-Rm

Standards Traceability

Sr-Tr

Actuals Resources Ar

Actual Resources Structure,

Ar-Sr

Actual Resources Connectivity,

Ar-Cn Simulation b

Parametric Execution/Evaluation

b - -

Dictionary * Dc

Summary & Overview SmOv

Requirements Rq

6

WHY THE GRID ?

• Demilitarizes UPDM • Still the same underlying metamodel and view constructs that support:

• DoDAF

• MODAF

• NAF

• Different presentation layers

• Very hard to manage the views with so many contributing frameworks • Lead to very complex mapping tables • Unwieldy descriptions

• Possible to map many other frameworks onto the MM • HSI views and SoS views

6

7 7

HUMAN FACTORS/PERSONNEL VIEWS

• Stakeholders: Human resources, Solution Providers, PMs.

• Concerns: human factors.

• Definition: aims to clarify the role of Human Factors (HF) when creating architectures in order to facilitate both Human Factors Integration (HFI) and systems engineering (SE).

• Based on Human Factors work done at the MOD/NATO

• Dr Anne Bruseberg was one of the principal authors

• Informed by a MODAF/Human Factors gap analysis that found that 95% of human factors views elements were already in MODAF

HVs between OV and SV level

OV-4

OV-2OV-3

OV-6

SV-10

OV-

1a,b

SV-7

OV-5

OV-

1c

SV-2

SV-3SV-8

SV-9

SV-6

SV-5

SV-1

StV-

3,5

StV-2

StV-4

SV-4

HV-A:

Personnel

Availability

HV-B: Quality

Objectives and

Metrics

HV-C: Human

Interaction

Structure

HV-D:

Organisation

HV-E: Human

Functions and

Tasks

HV-G: Dynamic

Drivers of Human

Behaviour

HV-F:

Roles and

Competencies

FormalDependencies

Part-whole

Rank

Conditions

OperationalConfigurations/States 1...n

HumanFunctions/Tasks

Facilities

Detailed

through

Human Performance

Criteria & Metrics

Methods of

Compliance

Mapped

to

Target

Measures

Specified

with

Mapped

to

Informationaccess,

transmissionand sharing

Systems

Locations

actual virtual

Roles/Responsibilities

Competency Requirements

Skills Attributes Knowledge

PersonnelDevelopment

Need

OrganisationalUnits

Units Teams Posts

FormalProcesses/

Procedures/Values

Enable

Relate

through

At

At

Are

defined

through

Define

Define

Needs

Require

Trends/

Forecasts

Fulfill

Human-computerInterface

Have

System

Functions

Affect

Actual

People

Personin Post

Has

Environment

With

Use

HFI Value

Level 1...nHFI Value




definitions

Level 1...n

Conduct

Require

Interactionwith

Equipment

Teamwork/Interaction

Taskwork(decom-position)

Require

Require

Peopleavailability

Define

Numbers Characteristics

Have

Person(throughPost) in

Role

Define

Have

Ensures Have

At

Time/Epoch

Behaviours

HCITeam

work

Task

work

Assessed

through

Define

Affect

StateChanges

TimeUnits

Have

For

Scenario 1...n(representative)

For

Describe

Define

At

Dynamic properties

HaveInterface

with

Have

status

of

Display

Display

DisplayDisplay

Consist of

HV-AHV-G

HV-E

HV-D

HV-F

HV-C

HV-B

FormalTask-Based

OrganisationAffect

Affect

10

THE “YACHT IN DISTRESS” SCENARIO

• The Sample Problem applies UPDM to a common scenario in civilian maritime Search and Rescue (SAR) operations -- a Yacht in distress. A Monitor Unit picks up the Distress Signal from the Yacht and passes it on to the Command and Control (C2 Center). The C2 Center coordinates the search and rescue operation among the Rescue Helicopter, a Naval Ship and a Rescue Boat.

• This model is based on a UK MOD example model.

11 11

OV-1: OPERATIONAL CONTEXT GRAPHIC

12


• Concerns: organizational resource types.

• Definition: shows the taxonomy of types of organizational resources.

• Recommended Implementation: SysML Block Definition Diagram.

Pr-Tx Personnel Taxonomy

The Pr-Tx view specifies the taxonomy of types of organizational resources.

13

PR-TX PERSONNEL TAXONOMY

14

PR-TX PERSONNEL TAXONOMY

15


• Concerns: typical organizational structure used to support a capability(ies).

• Definition: shows organizational structures and possible interactions between organizational resources.

• Recommended Implementation: SysML Block Definition Diagram, SysML Internal Block Diagram.

Pr-Sr Personnel Structure Specification

16

PR-SR PERSONNEL STRUCTURE SPECIFICATION

17


18


Pr-Sr [Capability Configuration] Maritime Rescue Unit v1

«CapabilityConfiguration»

Maritime Rescue Unit v1

«ResourceRole»

MR Aircraft : Aircraft

«ResourceRole»

Beacon : Lighting Device

«ResourceRole»

Radio : Communication Device

«ResourceRole»

MR Boat : Boat

«ResourceRole»

Life Preserver : Life Saving Device

«ResourceRole»

: Maritime Rescue Team

«ResourceRole»

Driver : MRT Boat Driver

«ResourceRole»

Pilot : MRT Helicopter Pilot

«ResourceRole»

Radio Operator : MRT Communicator

«ResourceRole»

Rescue Swimmer : MRT Swimmer

«ResourceRole»

Searcher : MRT Searcher

RI : radioInstruction

«ResourceExchange» «ResourceConnector»

LPI : lifePreserverInstruction

«ResourceExchange»«ResourceConnector»

AI : aircraftInstruction

«ResourceExchange»«ResourceConnector»

BI : boatInstruction


BCI : beaconInstruction


19

• Stakeholders: Solution providers.

• Concerns: interaction of organizational resources.

• Definition: captures the possible interactions between organizational resources, including command relationships. Interactions typically illustrate the fundamental roles and management responsibilities.

• Recommended Implementation: tabular format.

Pr-Cn Personnel Connectivity Specification

20

PR-CN PERSONNEL CONNECTIVITY SPECIFICATION

21

PR-CN PERSONNEL CONNECTIVITY SPECIFICATION

22

• Stakeholders: Systems engineers, Solution providers.

• Concerns: functions that have to be carried out by organizational resources.

• Definition: specifies organizational resource functions in relation to resource definitions.

• Recommended Implementation: SysML Activity Diagram, SysML Block Definition Diagram, BPMN Process Diagram

Pr-Pr Personnel Processes Specification

23

PR-PR PERSONNEL PROCESSES SPECIFICATION

24

PR-PR PERSONNEL PROCESSES SPECIFICATION

«Cap

abili

tyC

onfi .

..

: Mar

itim

e R

escu

eU

nit v

1

: MR

T S

earc

her

location

destination

: Determine Destination

location

: Move

destination

: Transport

condition updatedCondition

: Apply First Aid

victimName

: Reassure Victim : Recover

Victim

reportedLocation

reportedConditionname updatedCondition updatedLocation

Rescue Victim

«Function»

25

• Stakeholders: Systems Engineers, Software Engineers.

• Concerns: capture state-based behavior of an organizational resource.

• Definition: it is a graphical representation of states of an organizational resource and how that organizational resource responds to various events and actions.

• Recommended Implementation: SysML State Diagram.

Pr-St Personnel States Specification

26

PR-ST PERSONNEL STATES SPECIFICATION

27

PR-ST PERSONNEL STATES SPECIFICATION

Waiting for Mission

do : Mission Training

do : Sleep

do : Eat

do : Maintain Equipment

Planning Mission

do : Determine Destination

Team Preparation

Searching for Person in Distress

do : Move

do : Search

AreaOfInterestUpdatePh2/Determine Destination

Person in Distress Found

do : Apply First Aid

do : Recover Victim

do : Reassure Victim

do : Transport

Returning to Base

do : Move

Post Mission Processing

do : Unload Equipment

do : Debrief

Maritime Rescue Team Phase 3

«ResourceStateDescription»

/

Distress Beacon/

Route Info/

BoardRescueVessel/

DistressedPartyFound/

DistressedPartyRescued/

Arrive at Base/

when( Complete )/

DistressedPartyRescued/

SearchCancelled/

/

28

• Stakeholders: Software Engineers, Systems Engineers.

• Concerns: interactions between organizational resources (roles).

• Definition: provides a time-ordered examination of the interactions between organizational resources.

• Recommended Implementation: SysML Sequence Diagram, BPMN Collaboration Diagram.

Pr-Is Personnel Interaction Scenario Specification

29

PR-IS PERSONNEL INTERACTION SCENARIO SPECIFICATION

30

PR-IS PERSONNEL INTERACTION SCENARIO SPECIFICATION

SAR Organization Context Phase 3

Description

:Distressed Party

«ResourceRole»

:MSAR C2 Operator

«ResourceRole»

:SAR C2 manager

«ResourceRole»

:Military C2 Manager

«ResourceRole»

:MRT Communicator

«ResourceRole»

:MRT Boat Driver

«ResourceRole»

:MRT Helicopter Pilot

«ResourceRole»

:MRT Searcher

«ResourceRole»

Distress Signal Sent«ResourceExchange»

Resource Exchange : distressSignalOperator Informs Manager

«Command»

Command : emergencyNotification

Operator provides track info

«Command»

Command : trackInfo

SAR Manager requests Assistance

«Command»

Command : request

Military C2 Manager Tasks Pilot

«Command»

Command : tasking

Pilot Updats Status«Command»

Command : statusMilitary C2 updates SAR C2

«Command»

Command : status

Operator tasks Rescue Team

«Command»

Command : radioInstruction

Communicator Relays Command

«Command»

Command : control

Operator Updates Track info

«Command»

Command : trackInfo

Communicator Tasks Searcher

«Command»

Command : control

Searcher Updates Status

«Command»

Command : status

Communicator Updates Operator

«Command»

Command : status

31

• Stakeholders: Systems engineers, Solution providers.

• Concerns: allocation of competencies to actual posts.

• Definition: specifies requirements for actual organizational resources – by linking competencies and actual posts.


Pr-Cta Personnel Constraints Specification (Competencies to Posts)

32

PR-CTA PERSONNEL CONSTRAINTS SPECIFICATION (COMPETENCIES TO POSTS)

33


Definitions and Requires Competence

1

1

1

1

1

1

1

1

1

1

1

1

1

1

Pr-Cta [Architectural Description] Personnel Competencies

«Post»

MRT Communicator

«Post»

MRT Swimmer

«Post»

MRT Helicopter Pilot«Post»

MRT Searcher

«Post»

MRT Boat Driver

«Post»

Soa Responsible

«Post»

SAR C2 manager

«Competence»

Communicate Effectively

«Competence»

Render First Aid

«Competence»

Navigation

«Competence»

Good Vision

«Competence»

Marine Awareness

«Competence»

Coordination

«Competence»

Manage Teams

«Responsibility»

Communicate Status

«Responsibility»

Save Lives

«Responsibility»

Air Transit

«Responsibility»

Find Victim

«Responsibility»

Sea Rescue

«Responsibility»

Status Update

«Responsibility»

Allocate Resources

1

1

«ResourceRole»1

1

«ResourceRole» 1

1

«ResourceRole»1

1

«ResourceRole»1

1

«ResourceRole»1

1

«ResourceRole»1

1

«ResourceRole»

«RequiresCompetence»




«RequiresCompetence»«RequiresCompetence» «RequiresCompetence»

34


Roles and Actuals for Provides Competence

Lifeboat Driver

«ActualPost»

Rscr soa

«ActualPost»

Rescue Helo Pilot

«ActualPost»

c2 chief

«ActualPost»

C2 soa

«ActualPost»

Radio Operator

«ActualPost»

Rescue swimmer

«ActualPost»

Srchr soa

«ActualPost»

Communicate Effectively

«Competence»

Render First Aid

«Competence»

Navigation

«Competence»

Good Vision

«Competence»

Marine Awareness

«Competence»

Coordination

«Competence»

Driver

«ResourceRole»

Manage Teams

«Competence»

Pilot

«ResourceRole»

Radio Operator

«ResourceRole»

Rescue Swimmer

«ResourceRole»

Searcher

«ResourceRole»

«ProvidesCompetence»

«ProvidesCompetence» «ProvidesCompetence»



«ProvidesCompetence»«ProvidesCompetence»


«CompetenceForRole»«CompetenceForRole»

«CompetenceForRole»



Pr-Cta Personnel Constraints Specification (Competencies to Posts)

35

• Stakeholders: Systems engineers, Solution providers, Human resources.

• Concerns: optimization of organizational resource behavior.

• Definition: captures the factors that affect, constrain and characterize organizational resource behavior as the basis for performance predictions at the level of actual persons and actual organizations. It creates a bridge between static architectural definitions and behavior predictions through executable models.

• Recommended Implementation: tabular format, SysML Parametric Diagram, SysML Block Definition Diagram.

Pr-Ctb Personnel Constraints Specification (Drivers)

36

PR-CTB PERSONNEL CONSTRAINTS SPECIFICATION (DRIVERS)

37

MD-TX ENVIRONMENTS, CONDITIONS, ETC.

Conditions

38 38

AV-3 MEASUREMENTS DEFINITIONS

Measurement Set

Measurements

Measurement Sub-

Type

Definition of metrics

for reuse throughout

the architecture.

39 39

AV-3 ACTUAL MEASUREMENTS

Actual Property Set

Measurement

Values

40

PR-CTB PERSONNEL CONSTRAINTS SPECIFICATION (DRIVERS)

Properties and Constraints (Rules)

Pr-Ctb [Architectural Description] Drivers Personnel Drivers

«Post»

MRT Searcher

«Function»

Apply First Aid

«Function»

Reassure Victim

«Function»

activityPerformableUnderCondition«Environment» Artic Water«Environment» Cold Water«Environment» Temperate Water

Recover Victim

«Function»

Find Victim

«Performs»

«Performs» «Performs»

«Performs»

actualPropertySet«ActualMeasureSet»

Final Values : Maritime

SAR Measurements

actualPropertySet«ActualMeasureSet»

Final Values : Maritime

SAR Measurements

propertySet«Condition» Calm Sea«Condition» High Seas«Condition» Medium Waves«Environment» Artic Water«Environment» Cold Water«Environment» Temperate Water«GeoPoliticalExtentType» Ocean«LightCondition» Bright Sunlight«LightCondition» Darkness«LightCondition» Low Clouds«LightCondition» Low Light

propertySet«Condition» Calm Sea«Condition» High Seas«Condition» Medium Waves«Environment» Artic Water«Environment» Cold Water«Environment» Temperate Water«GeoPoliticalExtentType» Ocean«LightCondition» Bright Sunlight«LightCondition» Darkness«LightCondition» Low Clouds«LightCondition» Low Light

«ResourceConstraint»{Search personnel shall operate on a shift system to ensure that they can perform to maximum efficiency}

41

• Stakeholders: Human resources, solution providers.

• Concerns: how well an actual organizational resource matches the needs of the actual organization.

• Definition: provides a repository for human-related measures (i.e. quality objectives and performance criteria (HFI values)), targets and competences.


Pr-Ctc Personnel Constraints Specification

(Performance/ Quality Objectives)

42

PR-CTC PERSONNEL CONSTRAINTS SPECIFICATION (PERFORMANCE/ QUALITY OBJECTIVES)

43

PR-CTC PERSONNEL CONSTRAINTS SPECIFICATION (PERFORMANCE/ QUALITY OBJECTIVES)

Pr-Ctc [Architectural Description] Drivers [Performance]

«Post»

MRT Searcher

desiredState«OperationalAtomicState» DeliverDistressedPartyToSafePlace«OperationalAtomicState» DistressedPartyFound«OperationalAtomicState» StayingAsLongAsPossible

desiredState«OperationalAtomicState» DeliverDistressedPartyToSafePlace«OperationalAtomicState» DistressedPartyFound«OperationalAtomicState» StayingAsLongAsPossible

actualPropertySet«ActualMeasureSet» Final Values : Maritime SAR Measurements«ActualMeasureSet» Initial Values : Maritime SAR Measurements«ActualMeasureSet» Required Values : Maritime SAR Measurements

actualPropertySet«ActualMeasureSet» Final Values : Maritime SAR Measurements«ActualMeasureSet» Initial Values : Maritime SAR Measurements«ActualMeasureSet» Required Values : Maritime SAR Measurements

44

• Stakeholders: Human Resources, Training, Logisticians, Solution Providers.

• Concerns: the staffing and training of resources.

• Definition: defines the requirements and functions to ensure that actual persons with the right competencies, and in the right numbers, are available to fulfill actual posts.

• Recommended Implementation: Timeline, SysML Block Definition Diagram

Pr-Rma Personnel Roadmap Specification (Availability)

45

PR-RMA PERSONNEL ROADMAP SPECIFICATION (AVAILABILITY)

46


Definition

Pr-Rm [Architectural Description] Actual Organizations [Availability]

«ActualPerson»

Ron Radio : Marine Radio Operator

«ActualPerson»

Danny Driver : Qualified Lifeboat Driver

«ActualPerson»

Peter Pilot : Qualified Helo Pilot

«ActualPost»

Radio Operator : MRT Communicator

«ActualPost»

Lifeboat Driver : MRT Boat Driver«ActualPost»

Rescue Helo Pilot : MRT Helicopter Pilot

«FillsPost»«FillsPost» «FillsPost»

endDate2014-01-01 00:00:00

startDate2010-01-01 00:00:00

endDate2014-01-01 00:00:00

startDate2010-01-01 00:00:00

endDate2014-01-01 00:00:00

startDate2010-01-01 00:00:00

endDate2014-01-01 00:00:00

startDate2010-01-01 00:00:00

endDate2014-01-01 00:00:00

startDate2010-01-01 00:00:00

endDate2014-01-01 00:00:00

startDate2010-01-01 00:00:00

47


Report

48

• Stakeholders: Human resources, Solution Providers.

• Concerns: organizational structure changes over time.

• Definition: provides an overview of how a organizational structure changes over time. It shows the structure of several organizational structures mapped against a timeline.

• Recommended Implementation: timeline, SysML Block Definition Diagram, SysML Internal Block Diagram.

Pr-Rmb Personnel Availability Specification (Evolution)

49

PR-RMB PERSONNEL AVAILABILITY SPECIFICATION (EVOLUTION)

50


Organizations

1

1

1

1

1

1

1

1

1

1

1

1

1

1

Pr-Tx [Architectural Description] Forecast [Phase 1]

«Post»

MRT Communicator

«Post»

MRT Searcher

«Post»

MRT Helicopter Pilot

«Post»

MRT Swimmer

«Post»

MSAR C2 Operator

«Post»

MRT Boat Driver

«Organization»


«Organization»


1

1

«ResourceRole»1

1

«ResourceRole»

1

1

«ResourceRole» 1

1

«ResourceRole» 1

1

«ResourceRole»

1

1

«ResourceRole»

1

1

«ResourceRole»

1

1

1

1

1

1

1

1

1

1

1

1

1

1

1

1

1

1


«Post»

SAR C2 manager

«Post»

MRT Communicator

«Post»

MRT Searcher

«Post»


«Post»

MRT Swimmer

«Post»

MSAR C2 Operator

«Post»

Soa Responsible«Post»

MRT Boat Driver

«Organization»


«Organization»


1

1

«ResourceRole» 1

1

«ResourceRole»

1

1

«ResourceRole» 1

1

«ResourceRole»

1

1

«ResourceRole»1

1

«ResourceRole»

1

1

«ResourceRole»

1

1

«ResourceRole»

1

1

«ResourceRole»

1

1

11

1

1

1

1

1

1

1

1

1

1

1

1

1

1

1

1

1

1


«Post»

SAR C2 manager

«Post»

MRT Communicator

«Post»

MRT Searcher

«Post»


«Post»

MRT Swimmer

«Post»

MSAR C2 Operator

«Post»

Soa Responsible«Post»

MRT Boat Driver

«Post»

Military C2 Manager

«Organization»


«Organization»


«Organization»

C2 Organization

1

1

«ResourceRole»

11«ResourceRole»

1

1

«ResourceRole» 1

1

«ResourceRole» 1

1

«ResourceRole»

1

1

«ResourceRole» 1

1

«ResourceRole»1

1

«ResourceRole»

1

1

«ResourceRole» 1

1

«ResourceRole» 1

1

«ResourceRole»

51


Pr-Rmb [Architectural Description] Forecast [Pr-Cn]

«ActualProject»

endDate2015-12-15 00:00:00

startDate2014-01-01 00:00:00

Org Phase 1 : Development

«IncrementMilestone»

date2014-01-01 00:00:00

resource«Organization» SAR Organization Context Phase 1

Phase 1 Available : Development Milestone

«OutOfServiceMilestone»

date2015-12-15 00:00:00


Phase 1 OOS : Development Milestone

«NoLongerUsedMilestone»

date2015-12-15 00:00:00


Phase 1 NLU : Development Milestone

«ActualProject»

endDate2018-12-31 00:00:00

startDate2015-12-16 00:00:00



date2015-12-16 00:00:00




date2018-12-31 00:00:00




date2018-12-31 00:00:00



«ActualProject»

endDate2022-12-31 00:00:00

startDate2019-12-31 00:00:00



date2019-01-01 00:00:00




date2022-12-31 00:00:00




date2022-12-31 00:00:00



52


53

• Stakeholders: Human resources, Logisticians, Solution Providers.

• Concerns: competencies and skills forecast.

• Definition: defines the underlying current and expected supporting competencies and skills of organizational resources.

• Recommended Implementation: timeline, tabular format, SysML Block Definition Diagram.

Pr-Rmc Personnel Roadmap Forecast Specification

54

PR-RMC PERSONNEL ROADMAP FORECAST SPECIFICATION

55


Definition

56


Report

57

• Stakeholders: Systems Engineers, Enterprise Architects, Solution Providers, Business Architects.

• Concerns: traceability between operational activities and functions that implements them.

• Definition: depicts the mapping of functions (performed by organizational resources) to operational activities and thus identifies the transformation of an operational need into a purposeful function performed by an organizational resource or solution.

Pr-Tr Personnel Traceability Specification

58

PR-TR PERSONNEL TRACEABILITY SPECIFICATION

59


Definition Pr-Tr [Architectural Description] System View (Implementation Definition)

«Function»

Recover Victim

«OperationalActivity»

implementedBy«Function» Determine Destination (in location, out destination)

performedBy«Operational Performer» SafePlace

Process Warning Order«Function»

implements«OperationalActivity» Process Warning Order (in warningOrder)

performedBy«CapabilityConfiguration» Maritime Rescue Unit v1

Determine Destination

«Function»

implements«OperationalActivity» Rescue ()«OperationalActivity» Search ()

performedBy«CapabilityConfiguration» Maritime Rescue Unit v1

Move

«Function»

Reassure Victim

«Function»

Transport

«Function»

implements«OperationalActivity» Rescue ()

Rescue Victim

«Function»

implements«OperationalActivity» Rescue ()«OperationalActivity» Search ()

performedBy«Post» MRT Searcher

Apply First Aid


Rescue


Search

«Implements»

«Implements»

«Implements»

«Implements»

«Implements»«Implements»«Implements»

«Implements»«Implements»

«Implements»

60


Report

61

• The UAF defines enterprise architectures – At various levels of abstraction

– From multiple viewpoints

• The UAF implements DoDAF, NAF and MODAF in SysML – Traces to systems engineering

– Provides multiple forms of trade-off analysis

• Human Factors have been integrated into the UAF as a set of personnel views

• This will enable systems that are fit for humans

CONCLUSIONS

62

QUESTIONS AND ANSWERS

DescriptionDescription You

:Attendee

Me

:Speaker

loop1

You

:Attendee

Me

:Speaker

loop1 while open questions exist

Question1.1

end loop

while open questions exist

Question1.1Question

Answer1.1.1Question

Answer1.1.1AnswerAnswer

end loop

{Speech Time}{Speech Time}

Documents

UNIFIED ARCHITECTURE FRAMEWORK (UAF) HUMAN · PDF fileunified architecture framework (uaf) human views ... the unified architecture framework (uaf) modaf v1.2.004 ... p e r s o n in