Competency information

Details

Document requirements and communicate the results of a system requirements gathering exercise in writing and verbally.

Considerations

  • The importance of accurately defining the requirements of a system.
  • Functional: what the product should do.
  • Data requirements: capture the type, volatility, size/amount, persistence, accuracy and the amounts of the required data.
  • Environmental requirements: (a) context of use; (b) social environment (e.g. collaboration and coordination): (c) how good is user support likely to be; (d) what technologies will it run on.
  • User requirements: capture the characteristics of the intended user group.
  • Usability requirement: usability goals associated measures for a particular product.
  • Data gathering techniques, including questionnaires, interviews, focus groups, naturalistic observation, studying documentation.
  • How to classify the task.
  • How to identify an appropriate stakeholder group.
  • Data interpretation and analysis.
  • Use cases.
  • Task descriptions.
  • Task analysis.
  • Requirements management.
  • Requirement of description documents.
  • Range of tools available.
  • Benefits identification and measurement.
  • Patient safety aspects of system design
  • Usability and accessibility.

Relevant learning outcomes

# Outcome
# 2 Outcome Perform a system requirements-gathering exercise, develop a specification of requirements and present findings in a functional requirement document to all stakeholders.