Thanks to Mr. Vic from London Metropolitan University for what he has taught me about Obstacle Analysis. After two years of classroom education now I really think that the Business/System Analysts should do some obstacle analysis in an organized way.
Obstacle Analysis is a technique used to identify obstacles to goals being fulfilled in goal directed requirement engineering as goal directed requirement engineering only focus to produce goals for the software system. There are few approaches for obstacle analysis but I am only going to describe what I think is easy to understand and use and that is called IROA approach. The approach is based on two heuristic.
Heuristic A: There is at least one group of obstacles for every requirement. These are obstacle found by negating each assumption made about requirement.
Heuristic B: The failure of an external entity or actor to behave as assumed could cause an obstacle to that assumption.
Heuristic A & B will be used in facilitated workshop (JAD workshop) for finding obstacles to assumptions made about requirements. Further heuristics will be defined as the work progress.
Obstacle Analysis is a technique used to identify obstacles to goals being fulfilled in goal directed requirement engineering as goal directed requirement engineering only focus to produce goals for the software system. There are few approaches for obstacle analysis but I am only going to describe what I think is easy to understand and use and that is called IROA approach. The approach is based on two heuristic.
Heuristic A: There is at least one group of obstacles for every requirement. These are obstacle found by negating each assumption made about requirement.
Heuristic B: The failure of an external entity or actor to behave as assumed could cause an obstacle to that assumption.
Heuristic A & B will be used in facilitated workshop (JAD workshop) for finding obstacles to assumptions made about requirements. Further heuristics will be defined as the work progress.
