Requirement: Observation on demand Acquisition Technology

Document directory

• Purpose
• Description
• Key Points
• Considerations

This article from: http://www.cnblogs.com/zhoujg/archive/2010/11/15/1877466.html

 

InRequirement: Document Analysis of requirement Retrieval TechnologyThe document analysis technology is introduced in this article. This technology is also used in daily life, just as I went fishing on Crab Island last Saturday and watched how others hooked up with bait to know how to get it.(Life: weekend Crab Island Tour)

Purpose

Observation is a way to obtain requirements by looking at the working environment of professionals. This method can be used when the details of the current process or the project needs to be enhanced or the current process needs to be changed.

Description

Observation depends on learning how others do things, that is, they need to stay with others. The observer needs to view the workflow. In some projects, this is an important way to understand the current process.

There are two basic observation techniques:

• Passive/invisible:
  • The observer observes the business experts and does not ask questions.
  • The observer only writes what he sees and does not start to ask questions until all the processes are completed.
  • The observer may watch it multiple times to make sure that he understands how the process works, and until why it does it in this way
• Active/visible
  • The observer observes how to do things and directly communicates with the worker during the observation.
  • The observer raises a question immediately when there is a problem, even if it interrupts the process being observed.
  • The observer may participate in the work to gain a more direct understanding.

In addition to the above two technologies, there are also a variety of other evolutionary technologies:

• In some cases, the observer will participate in the actual work to obtain first-hand information.
• The observer becomes a temporary apprentice
• How the observer works

Key Points

• Preparation
  1. Determine the observed user level (for example, experts, skilled workers or beginners) and the activities to be observed
  2. Prepare questions to be raised
• Observation
  1. Self-Introduction
     • Eliminate user resistance. You are not here to look for your problem, but to learn the current workflow and restrain yourself from discussing future better solutions (to-be)
     • Tell the user that if he feels that you are disturbing his work, he can immediately stop watching
     • Guide users to share their intentions, challenges, and concerns
  2. Start observation
     • Detailed notes
     • If it is an active/visible observation method, further explore why the current process and task are like this
• Submit Observation Analysis and confirmation
  1. Get answers to the questions you have prepared, or new questions during observation
  2. Summarize the observed content and send it back to the observer. If possible, check again.
  3. When observing multiple users, You need to identify what is common and what is different. Review these summaries to ensure that the covered content represents the entire group, not just individual

Considerations

• Benefits
  
  1. Provide first-hand business knowledge and know the actual and actual workflow.
  2. Through informal communication, you can obtain detailed information that is not recorded.

• Disadvantages
  
  1. Only observe the current process
  2. It may take a lot of time
  3. It may interrupt the work of the observer.
  4. Some unusual and important aspects may not occur during observation, so that some important points are left behind.
  5. If the current job is a highly intelligent job, but through observation, it cannot play a very good role.