L15: Agile UX: Use Studies, Stories and Senarios Flashcards
Describe the difference between functional and non-functional requirements.
The difference between functional and non-functional requirements is a functional requirements communicate how it functions but it doesn’t dictate how to create it from a design. A non-functional requirements are constraints solution must satisfy for example usability requirements, look-and-feel requirements, performance requirements, etc.
Which of the following is NOT true of constraints?
a. They are also referred to as non-functional requirements
b. They can affect all or many user stories
c. They should be treated like any other user story
c. They should be treated like any other user story
Requirements should be:
Necessary: What is the worst thing that could happen if this requirement were not included?
Verifiable: What are the criteria for acceptance?
Attainable: Must be affordable in cost, time & practicality
Clear: Express a single thought, be concise & simple
Software requirements should address?
Functionality: What is the software supposed to do?
External Interfaces: How does the software interact with people, the system’s hardware, other hardware, and other software?
Performance: What is the speed, availability, response time, recovery time of various software functions.
Attributes: What are the portability, correctness, maintainability security, etc. considerations?
Design constraints imposed on an implementation.
Which of the following use case level is most relevant to interaction design…?
a. Cloud level
b. Clam level
c. Sea level
c. Sea Level
What is a Use case?
Describes interaction between the system (or component) and something external. The external entity can be anything: An organization, a user or a peripheral device.
High Summary = ____ Level
Cloud Level
Summary = ____ level
Kite Level
User Goal = _____ Level
Sea
Sub-function = _____ Level
Fish
Too Low = ____ Level
Clam
What do scenarios need?
Clarity, brevity, and precision. Short paragraphs focused on a single subject
Which of the following is NOT true of the differences between sketches and wireframes?
a. Wireframes are seen by users as being more malleable than sketches
b. Sketches provide less detail than wireframes
c. Wireframes are retained, sketches discarded
a. Wireframes are seen by users as being more malleable than sketches
How do sketches help?
It helps fill the gap between abstract requirements and concrete solutions. It’s quick, malleable, tentative, visualization an important part of design.
Sketches or wireframes are usually included with _____ ____ as the specification of a user story (or use case)
design maps