Evaluate human-computer interaction principles and the discovery process.

Purpose

This assignment involves creativity and the completion of a project management-style template. You will gather requirements for a hypothetical one-screen interface (dashboard) project.

Assignment Instructions

This assignment takes you through the steps to create a requirements document for a hypothetical one-screen interface (dashboard) project. First, make sure that you understand the course definition of a monitoring dashboard by thoroughly reading the content in the textbook. Then choose one of the following topics for this assignment.

Topic choices:

• Business health dashboard: Displays sales history and trends, revenue and costs; could also include geographic data or specific products.
• Human resources dashboard: Displays aggregate data relating to employee turnover, absences, vacations taken, payroll structure; could be labeled by department.
• Call center dashboard: Displays average call duration, calls handled per person or team, sales targets; could also include number of calls waiting in queue.

Completion of the Template

Use the Unit 3 Assignment template. Retain the single-spacing; it is not intended to be an APA-formatted assignment. Provide a name for the dashboard project in the given location at the top of the template.

Part 1: Project Definition

Write 2 paragraphs (using full sentences) to give an overview of the project. The minimum length requirement for this part is 75 words.

In the first paragraph:

• State the general purpose of the dashboard, including what kind of information would be shown (example: “A weather dashboard shows temperature, rain/snow, and…”).
  In the second paragraph:
• Explain who would be primary users and stakeholders, and why.

Part 2: Requirements Collection

This section is comprised of a list of 7 open-ended questions you would ask potential users in a focus group to better understand how they would like to see information presented, what kind of information might be most useful, what kind of options they might like, under what circumstances the data would be most helpful, etc.

• Questions should focus on the data and what should be displayed on the dashboard – not on colors.
• Be specific. (Example of a bad question: “What data would you like to see on the screen?”)
• Write in full sentences, but keep a bulleted or numbered list format.

Part 3: Requirements Document

This section can also be a bulleted and/or numbered list, or it may be written in paragraph form. The minimum length requirement for this part of the template is 300 words. Include the following:

• Functional requirements
• Information requirements
• Hardware and software requirements
• Inputs and outputs
• Constraints and mitigations

Part 4: Conclusion (Reflection)

Provide a paragraph of at least 50 words that sums up the value of the project. You may include an explanation of additional methods of requirements collection, comparisons to similar projects, or other information that could potentially help you sell your dashboard idea to the client.