Contact Name:
Contact e-mail address:
Reference name for project (please do not use the real name, so that the form can remain unclassified)
Reason for assessment (using this form)
HS.2.4 Management
Purpose : To ensure that the HFI processes reflect the project needs and constraints
Successful outcomes:
For each of the activities below please select one of the following options:
No No - this doesn't happen
Partially This happens occasionally but there is no consistency
Largely Yes this usually happens
Fully This is recognised as the way we do business
Activity
N
P
L
F
1.The HFIP specifies how and when HFI activities integrate into the overall life cycle.
2. The HFIP specifies how input from HFI processes is used in the life cycle.
3. Plans that address HFI issues allow for iteration where necessary.
4. The HFIP identifies the need for and costing of user involvement.
5. The HFIP includes long-term monitoring of the system
6. The goals for the HFIP are derived from the goals of the user organisation.
7. Reporting structures and procedures are defined in the HFIP for people addressing HFI issues in different parts of the organisation and life cycle.
8.Resources for effective communication between project stakeholders are allocated.
9. HFI data requirements are defined.
10. The interfaces between HFI methods and other project activities are defined.
11. Outputs and success criteria for each activity are defined.
12. Milestones related to concrete stages and acheivements are defined.
13. A multi-disciplinary team approach is specified.
14. HFI-related activities performed as part of other jobs (e.g. software engineer) are defined.
15. The person with authority for HFI activities is defined.
16. Budgets related to Human-System processes are produced and reviewed.
17. Handover of HFI issues through life (e.g. from CWG to IPT to DLO) is defined.
18. Resources for corrective activity from in-service defect reporting are identified.
ŠLR 2001