My two bits on the matter.
We do a fair amount of shoring works and we have used several of the commercially available software including PYwall and Plaxis. The results: We ended up writing our own software. Why?? none is complete, none addresses all of the practical day to day needs. Perhaps they should not be expected to be so ????
We have collected several published case studies, some of which have been already analysed by the authors using Plaxis or similar FE software. I am currently convinced that P-Y method (for most cases) is just as good as any and the impact of a good soil investigation and determining the proper design soil parameters far outweigh anything else. We also found out that, in general, it is very difficult to match both: the reactions and the deflections of the retaining system, that is when compared with the actual field cases. Again, as an overall conclusion, when you match the deflections, the calculated reactions are on the conservative side by, anywhere from 10% and up.
Furthermore, and especially when braced excavations are involved, it seems that there is more room for construction misshaps ranging from delays in the execution to faukty excutions to fauilure in accounting for sagging in the long braces which inevitably translates into a lateral translation in the shoring system, etc...
I'll be glad to provide a copy of this exercise/document should anyone be interested.
Moral of the story.
1. There is no substitute for a good soil investigation, good testing program, experience (especially local experience), and common sense.
2. More expensive software is not necessarily better nor should it be treated as the bible. The engineer should have the knowledge to analyze and determine what makes sense.
3. Know your software and its limitations and be sure you can verify its results, even if roughly, using quick hand calculations.
Good luck