Modelling Human Factors using the Systems Modelling Language

HFIDTC/2/WP2.8.9/1Version 2/ 24th September 2008The map will be movedby dragging anddropping with themouse. It will bezoomed in/out usingthe spin button on themouseUAV icon with velocityvector line showingspeed and direction oftravelTactical PictureSoldier icon500mID – 561349Golf 4OpacityMap graphic with scaleTooltip showing soldierid and callsignControl to alter themap’s opacityFigure 7-23 - Situation Display Window7.2.6.1 Value addedThe SysML diagrams produced in this section are a specification for the design of the UIand have started to document which Posts will require which UIs. Such diagrams wouldbe a useful source for a more detailed UI specification document that would include thesort of graphical representations of the UI illustrated by Figure 7-22 and Figure 7-23above. The design of the UI will result in updates to the SysML diagrams that representthe UI, and these will in turn drive changes to views of the model. A benefit to definingthe UI in this way is that UML is a language understood by most Software Developers,and most modelling tools can produce code directly from the UML.7.2.7 Modelling Quality Objectives and MetricsEarlier in the document we used Use Case Diagrams to capture requirements. Thissection details further how requirements can be captured, detailed and satisfied using theSysML. In relation to the Human Views, HV-B defines how HFI values link to HFIrequirements and how these requirements can be turned into quantifiable metrics andsatisfied. The SysML allows us to show these linkages. Here we will use ‘safety’ as ourtop level HFI value.44