Description

Q1

Review the UCD Interview Transcript and any data you may have collected for the project. Use a hierarchical task inventory (HTI) to demonstrate the task structure. A HTI shows the structure of a task by decomposing it into a series of subtasks. The HTI will help to reveal sets of functionalities that we will need to provide in the new interface and how they are related. 1. To start your HTI read the interview transcripts carefully then try to write a usage scenario that captures a typical user interaction with the system. From here you can then start thinking about the tasks the user has to carry out and order in which they occur. Are some tasks part of another task? If so, then they are a subtask! When you have worked out a rough sequence, think about whether further decomposition is needed for any of the subtasks identified. Note: You can include your scenario as an appendix to this task

Example

Decomposition can be taken down to a very low level. You will need to make some decisions about which tasks to leave and which tasks to analyse in more detail.

·         HTI on energy shifter app

Q2

Write requirements based on HTI

When you have finished your HTI identify some requirements based on your analysis. Remember, the requirements you specify in this task must relate to your HTI analysis.

[Name of major feature or category] [ID Number of requirement] [Name of second level feature or category] Requirement statement: [with source if possible] Rationale (if useful): [Rationale statement] Note (optional): [Commentary about requirement]

·         I want three requirements and its description

·         Note: The requirement statement must NOT specify how the feature is implemented. You can make a suggestion for how it might be implemented in the note, but not the requirement itself

Q3

Try to write the details related to the features (what system is supposed to do in response to user expectations). Follow the recommended requirement format. 'System/user must be able to' FIX AND RESUBMIT