[Haskell-beginners] Functional programming principles at higher levels?

[Christopher Howard]

Caveat: I have a lot to learn about functional programming. And it is 
probably going to take me years to get there, because of all the higher 
mathematics I need to catch up on. Having said that...

It seems to me like there are at least two core ideas to functional 
programming:

1. Seeing a program as an expression that is evaluated.
2. Referential transparency.

And these lead to or involve various other concepts: writing code that 
can easily be refactored; viewing computations as a set of dependencies 
to be resolved rather than steps to follow; mathematical rather than 
procedural approaches to solving problems; the exclusion or minimization 
of state.

But has anyone attempted to apply these principles to programming at 
higher levels than just writing the code? Say, overarching software 
architecture? Or resource management models?

I've been reading lately about various higher level software approaches 
and models like RESTful architectures and MVC frameworks and RM-ODP, and 
it is difficult to see what I should grab onto.

-- 
frigidcode.com
theologia.indicium.us