Object Definition Files, I can live with that one :)
And I agree it's very useful to be able to put the whole "Application Lifecycle Landscape", as you call it, inside one of them.
But... the issue we're encountering is with the "full parameterization" part.
It's okay if every single property value within the Obj Def Files is within your control, but the moment you let the system generate a value for you that you need somewhere else things become more complex.
Of course if you can just set the host name of the backend's Route element everything is fine, but that isn't very useful for DEV and QA, DEV is most likely running things on minishift or using "oc cluster up". If you use a Route without a specified host name you get one generated for you nicely. But of course now we have the problem of how to tell the frontend what URL it should connect to! Which is what I'm trying to solve here:)