Modelling Human Factors using the Systems Modelling Language

HFIDTC/2/WP2.8.9/1Version 2/ 24th September 2008Table 8-2 - Applicability of the SysML for modelling Human Views for MODAFHuman View Potential Data Source SysML Representation Comments Usage in this DocumentHV-A: PersonnelAvailability: Defines therequirements and processes toensure that personnel with theright characteristics and in theright numbers are available forPosts/jobs.HV-B: Quality Objectivesand Metrics: Provides arepository for human-relatedperformance criteria, includingqualitative values andquantifiable metrics withmeasurable targets.HV-C: Human InteractionStructure: Captures thestructure of human networkssupported by technology,including the operationaldependencies and constraintsunderlying informationhandling.Personnel Databases,Personnel Interviews,Target AudienceDescription (TAD),Analysis of Organisationand it's PersonnelHazard Identification(HAZID) / Process HazardAnalysis (PHA), Standards,Requirements, EarlyHuman Factors Analysis(EHFA), Task Analysis,Human PerformanceModellingSocial Network Analysis,Link analysis, TargetAudience Description,Organisation Charts, JobDescriptions, Doctrine,Subject Matter Eexpert(SME) Interviews, TaskAnalysisBlock DefinitionDiagram, ActivityDiagram, SequenceDiagram, RequirementsDiagramRequirements DiagramBlock DefinitionDiagram, ActivityDiagram, SequenceDiagramSysML can be used to deriveand document personnelrequirements as linked toRoles/Posts and also detailexpected competency levels.However, demographic andrecruitment/retention trends andpersonnel availability are betterrepresented in reports, tablesand graphs.SysML can be used to show thelogic of deriving specificrequirements from top levelvalues via requirementsdiagrams. Specific performancetargets can also be linked totasks identified in the model.SysML can be used to modelorganisational and interactionstructures through adaptation ofBlock Definition Diagrams.However, the complexity of anorganisation and the level ofgranularity shown need to beconsidered carefully. Thus anumber of linked views may beneeded to show interactions andsupporting technology at alllevels from unit to Post.- Figure 7-7 Expanded Block DefinitionDiagram of Posts- Figure 7-8 Block Definition Diagram ofcompetencies required for the ResourceAllocation Role- Figure 7-11 Block Definition Diagram -Role to Task Mapping for the GroundCommander Post- Figure 7-25 Requirements Diagram -Emergency Egress- Figure 7-25 Requirements Diagram -Emergency Egress- Figure 7-15 Block Definition Diagramshowing a stove piped centralised SocialNetwork Structure- Figure 7-16 Block Definition Diagramshowing a decentralised Social NetworkStructure56