aStrategyChooser.strategy = new EagleMovement();
aStrategyChooser.Move(); // will output specific Eagle … movement ..
aStrategyChooser.strategy = new PenguinMovement();
aStrategyChooser.Move(); // will output specific Penguin … movement ..
// … etc
………..

class EagleMovement implements IMovementStrategy{
Move():void
{
trace (’Im moving .. Im flying .. maybe I will migrate … so for sure Im an eagle …’)
}
}

class CarMovement implements IMovementStrategy{
Move():void
{
trace (’Im moving .. I have wheels .. I can be a car .. .lets say some kind of animal … and this is my movement strategy ‘);
}
}

Now defining the “KEY” class of the Strategy Pattern -> the “director and manipulator” of strategies we ca do smt like that:
class MovementStrategyManager
{
private var _strategy:IMovementStrategy;

public function set strategy( strategy_:IMovementStrategy):void
{
_strategy = strategy_;
}

public function Move():void
{
if (_strategy) _strategy.Move();
else
trace (’I want to move .. but i dont have a strategy of movement … ‘)
}
}// end class

Why and how this can be usefull:

aStrategyChooser = new MovementStrategyManager();
aStrategyChooser.Move(); // you’ll get … I want to move .. but have no strategy …
aStrategyChooser:IMovementStrategy = new EagleMovement();
aStrategyChooser.Move(); // will output specific Eagle … movement ..
// … etc

… so (in my opinion) this can be a more correct( based on your example ) strategy pattern.

With all respect,
Ciprian