Modelling Human Factors using the Systems Modelling Language

More documents

Recommendations

Info

HFIDTC/2/WP2.8.9/1Version 2/ 24th September 2008Note that this Use Case Diagram includes Use Cases for maintaining and deploying thesystem as well as using the system operationally. For the H-Fly case study we will beusing the ‘Conduct H-Fly Operation’ and ‘Conduct Ground Operation’ Use Cases, but itis important to note that for HFI we must also consider the trainers, maintainers andlogistics operators that would be involved in the other Use Cases presented here.Figure 7-3 shows another Use Case Diagram, which decomposes the ‘Conduct H-FlyOperation’ Use Case in the top level diagram. Note that this Use Case Diagram’s title isthe Use Case that is being decomposed.Figure 7-3 - Conduct H-Fly Operation Use Case diagramIn producing this diagram we have gone further in defining requirements by describing inmore detail how the Actors will use the system to achieve goals. By choosing Actors that18
HFIDTC/2/WP2.8.9/1Version 2/ 24th September 2008are Organisational Units we have avoided any consideration of human Roles; this will bedone at a later stage of our modelling. During early modelling Roles are not assigned toentities, but it is important to know what the Roles are. The possible exception to thiswould be if we knew a specific entity existed, e.g. a Force Commander, and wouldperform that Role.At this stage we should add the following new terms to the project glossary in Section11.1; ‘Situation Awareness (SA)’, ‘H-Fly Mission’, ‘UAV’, ‘Ground Deployment (GD)’,‘HQ’ and ‘GCS’. Of course our definitions will be based on what we know at the currenttime, so we may well update them in future as we learn more about the system.Use Cases are usually associated with a text specification, which provides further details.An example is provided in Table 7-1.Table 7-1 - Use Case specification for the 'Request SA Information' Use CaseUse Case: Request SA InformationID: 1Brief description:Request video and map data to be sent.Primary Actors:GD, HQ and GCS.Preconditions:H-Fly System is deployed and operational in theatre.Main Flow:The Use Case starts when a person contacts the GCS and requests SAinformation.The GCS assesses the request and decides if the information can be supplied.The GCS informs the requestor that the information will be compiled and sentto them.Post-conditions:The requestor of the SA information is expecting the information to be sent tothem.Alternative flows:The GCS decides that the requested information cannot be supplied.The details provided in the Use Case specification can also be expressed further in otherSysML diagrams that can be used to model the different scenarios associated with a Use19
Page 1 and 2: Modelling Human Factors usingthe Sy
Page 4 and 5: HFIDTC/2/WP2.8.9/1Version 2/ 24th S
Page 8: HFIDTC/2/WP2.8.9/1Version 2/ 24th S
Page 17: HFIDTC/2/WP2.8.9/1Version 2/ 24th S
Page 72 and 73:
HFIDTC/2/WP2.8.9/1Version 2/ 24th S
Page 74 and 75:
Page 76:
show all

Modelling Human Factors using the Systems Modelling Language

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?