Someone not just starting with VAJ might be able to give you better ways, but here is my quick try. Once you do enough to get the slightest feel for how VAJ works (e.g., Stanchfield chapters 1-3), it is easy to do the kind of navigation required for your questions 1 and 2. (As I understand it, this is one of VAJ's particular strengths.)
So, assuming I'm understanding your questions...
"1. Can we find out, which classes in the workspace implement the interface, i.e. does VA4J help us to find out dependencies?"
Yes. In the Workbench, Interfaces tab, right-click the interface (StepEvent) and pick Implementors. There you will see all matches (maybe one in this case). Select one to see full name in status bar. Open it up (e.g., double click it), and you can see whatever you want.
"2. If the class/interface is being used in the workspace, does VA4J provide a mechanism to find the package where this class is defined?"
Yes. If you pick the type out the Class or Interfaces tab of Workbench, and check the status line for package name, or double-click to open and see whatever you want.
Or, if you select a type name it in, say, a method body, right-click, then Open on Selection.
(Of course, I didn't remember that "Open on Selection" existed, but I did know that if I right-clicked, I'd probably find what I needed.)
"3. Once the package has been identified,do we need to import that package in the workspace.Alternatively, would it be OK if we put the path of the Jar(or class file) in the Workspace classpath?"
So far, I've preferred to import thinks I'm using into the workspace so I could use VAJ to navigate the classes.
I think you can refer to external code if all you want to do is excute, not browse, but I'm just starting that chapter of the my book. I've not tried it so cannot quickly verify the details off the top of my head. I'm sure your books or the help will tell you how. (The IDE.PDF is well worth printing, especially if your books don't do a good job with the
IDE.)