Too often, business analysts focuses entirely on what the system should do at the cost of understanding how users will interact with it. This leads to tomes of documentation with the ever typical "system shall.." statements. Clearly system functionality needs to be captured, but focusing on the system alone won't cut it. User workflow and productivity requirements cannot be gleened from taking "system shall" statements from an end user's bosses boss.

Analysis Activities:

• Meeting facilitation
• JAD Sessions
• Stakeholder Interviews
  
• Contextual Engineering Interviews
  

Analysis Deliverables:

• User Class Definitions
• End User Personas
• Goal Mapping
• Task Analysis