DDQ MON 2020-10-12 @ 12:40 PM

20. Requirements Analysis

20.1. Agenda

  1. General Announcements

  2. Exam 1 grades will be released tomorrow.

  3. CSCI 4800H/6800 Paper Presentations begin THU 2020-10-15.

    • J.K. will present Ghosh et al. “Commanding and Re-Dictation: Developing Eyes-Free Voice-Based Interaction for Editing Dictated Text.” from the ACM Transactions on Computer-Human Interaction, August 2020. [2020FA:1]

  4. Term Project: Milestone 3 details coming soon.

  5. Activity

20.2. Activity

In an interaction design process, requirements analysis is a phase that collects all of the necessary requirements for an interactive system or device and yields a requirements specification or document as its outcome [M3:3].

functional requirements

Requirements that define the specific behavior that the system should support [Book:1].

Example: Mobile App

The app shall be able to send messages at all times, even when out of the service area (in which case they are saved for later sending).

non-functional requirements

Requirements that specify overall criteria governing the operation of the interactive system without being tied to a specific action or behavior (e.g., hardware, software, system performance, reliability, etc.) [Book:1].

Example: Mobile App

Messages should send within 2 seconds, returning the user to the new message window (continuing in the background if necessary).

user experience requirements

Non-functional requirements for the user experience and user interface of the interactive system (e.g., navigation, input, colors, etc.) [Book:1].

Example: Mobile App

The mobile app shall support customization such as color schemes, skins, and sounds.

pain point

A persistent or recurring problem (as with a product or service) that frequently inconveniences or annoys customers (users).

user story

An agile requirement, stated as a sentence or two without jargon. A user story is often expressed from the user’s point of view, and describes a unit of desired functionality [1].

User Story Template

As a type of user, I want some goal so that some reason.

use case

A formalized scenario that captures an operation between an actor and the system in a step-by-step manner [Book:1].

20.2.1. Breakout Rooms

Duration: \(\sim\) 15-20 minutes

  1. Quick introductions, if needed.

  2. As a group, respond to the following in a followup discussion here.

    1. Pick an app that everyone is the group has used and pretend to be the developers of that app. Provide the name of the app, and, If possible, provide a screenshot.

    2. List two functional requirements for the app as user stories.

    3. List two non-functional requirements for the app as constraints with justifications.

    4. List two user experience requirements for the app as user stories.

    5. Make sure all group / room members are listed in your followup discussion post.

  3. Pick a group representative. This person will briefly share your group’s conceptual model to the class. No pressure, seriously!

  4. Respond to other followup discussions until the breakout rooms end.

20.3. References

1

The Agile Dictionary. “user story, n.”. URL: http://agiledictionary.com/277/user-story/.