Erp ax-user-requirements-UCD


Published on

How to Obtain user requirements.

Published in: Technology
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Erp ax-user-requirements-UCD

  1. 1. ERP- User Requirements MethodsP repared B y: A hmed R afik
  2. 2. Scope:- User Centered Design (UCD)- 3 Key Principles of UCD- Required Steps of UCD- Methods of User Requirements- Interview Method- Group Task Analysis
  3. 3. User Requirements ApproachUser Centered Design (UCD):It is a product development approach focus on the end-users of a product.UCD 3 Key Principles: Collecting User Testing Design Requirements PrototypeUser RequirementsMethods User Persona Scenarios Profile
  4. 4. User Requirements ApproachRequired Steps of User Centered Design (UCD): Learn About Learn About Conduct A The Product Users Method
  5. 5. Methods of User Requirements Field Study Survey Want & Needs Card Slot Analysis Focus Group Task Group Interview Analysis ERP Conducts Interview & Group Task Analysis
  6. 6. Interview Method DO:-In user requirement, Users are the experts.-Begin the interview that there are no right or wrong answers.-Your role, Make everyone participate.-Use Mind Mapping to take your notes.-Make your question have only one issue.-Use “Acknowledge tokens”, speakers expect reaction from the listener.-Judge the responses.-Begin with general questions and follow-up with specific questions.-Keep your questions under 20 words.-Use terms that are familiar to the user
  7. 7. Interview MethodDO NOT:-Don’t interrupt the speaker until finish his words.-Don’t use double negative in the same sentence.-Don’t Try to answer for them.-Don’t criticize anyone answers you.-Don’t use words like “Sometimes, Most, Few, Some, rarely”.-Don’t put your prestige in the question.-Don’t make the user predict the future.-Avoid Bias in your questions.-Avoid Leading Questions.
  8. 8. Group Task Analysis (GTA Method)Group Task Analysis:Is used to identify the steps users take to complete a particular task, andthe sequence of those steps.In a GTA, participants work in small groups and discuss the steps involved incompleting a particular task in order to create a task flow.
  9. 9. Group Task Analysis (GTA Method)Task analysis method produces three key results: User-Centered Task Objects Prototype GUI Task Flow Task to Object to GUI Task Analysis Object Mapping Mapping
  10. 10. Group Task Analysis (GTA Method) Type of data You can collect: End Decision Point Points Standard Trigger What choices Exceptions How does Steps the user users have toWhat is the Every step that make? These are stepstrigger that know when users take in that users take onlymakes users the task is order to in certain cases.start the task? complete? complete the task Additional Information
  11. 11. Group Task Analysis (GTA Method)Moderator Checklist:-Have personality. Be personable and approachable. Also, remember to smile!-Ask questions. There is no point collecting data that you do not understand.Ask questions throughout.-Stay focused. Small diversions, if relevant, are appropriate, but try to get backon track quickly. Asking participants to turn off all cell-phones at the beginningof the session will also go a long way to keeping them focused on the activity athand.-You are not a participant. Ask the questions and let participants answer them.Also, do not offer your opinions because you could bias your participants’responses.-Keep the activity moving. You need to control the direction of the activity andlevel of detail participants are providing or else you will never finish youractivity.
  12. 12. Group Task Analysis (GTA Method)Moderator Checklist (Cont.):-Keep the participants motivated and encouraged. A little encouragement goesa long way. Also keep an eye on your participants’ energy levels.-No critiquing. As a moderator, you should never challenge what a participanthas to say. It’s OK for a participant to disagree with a fellow participant, butremind everyone that there are no wrong ideas – there are simply differentexperiences and perspectives.-Everyone should participate. In a group activity, it can take a great deal ofenergy to draw out the quiet participants, but it is important to do so. This canbe done by calling on individuals by name and making eye contact,.-No one should dominate. When you notice a participant is beginning todominate the group, try to call on others in the group to balance things out anduse body language to quiet down the dominant participant (e.g., turning yourback to the participant, not making eye contact).
  13. 13. Ahmed Rafik – ERP