These heavily architected projects don't just happen by accident. There is probably a design somewhere. Ask around the enterprise architects for what tools are used for software architecture.
It could of course be that the guy was just using the class modeller in VisualStudio, in which case take a look out for class diagrams in the project itself.
Also these systems tend to be build by "TDD" these days, so there are probably a whole bunch of unit testing projects in the code repo as well. Start with these, and as DP says there might be a DI framework in the mix as well.
Stop thinking in terms of understanding the code, zoom out a little and try and identify some key objects, understand what they do and then start to drill in again and it should become a little clearer. Keep an open mind as this may revolutionise they way you think about software development and you may learn a nifty trick or too along the way. Seriously.
Take a look at Ninject, as this is the best DI framework IMVHO for noobies, and their documentation is friendly and accessible. They don't believe in the XML hell that is other DI frameworks.