Establishing requirements

Establishing requirements

1. Why?

   • Understand as much as possible about the users.
   • To produce a set of stable requirements that form a sound basis to start designing.
   • Requirements gathering
   • Requirements capture
   • Requirements elicitation
   • Requirements analysis
   • Requirements enigenerring

2. Requirements

   • Is a statement about an intended product that specifies what it should do or how it´s should perform.
     • Make the requirements as specific, unambiguous, and clear as possible.
       • FUNCTIONAL REQUIREMENTS
         • What the system should do
       • NON-FUNCTIONAL REQUIREMENTS
         • What constraints there are on the system and its development.
   • Data Gathering
     • Interviews
     • Questionnaires
     • Observation
     • Studying documentation
     • Researching similar products
     • Contextual Inquiry
       • Approach that emerged from the ethnographic approach to data gathering.
       • Context
       • Partnership
       • Interpretation
       • Focus
     • Data gathering guidelines
       • Focus on identifying the stakeholders needs
       • Involve all the stakeholder groups
       • Support the data gathering sessions
     • Interpretation and presentation
       • Volere shell
       • Diagrams
       • Sequence

3. Task Description

   • Scenarios
   • Use cases

4. Task Analysis

   • Hierarchical task

5. Preece, Jenny, Helen Sharp, Yvonne Rogers. Interaction Design: Beyond Human-Computer Interaction, 4th Edition. John Wiley & Sons UK, 2015-05-18. VitalBook file.

   • Anna Christina Muhlbach Castelán A01196259

Images and files in the map