Many people expect from the system architect that he decomposes the system in
smaller components and defines and guards the interfaces. 
The conventional waterfall model for software development and this
architecture view form a dangerous combination: an extremely limited
integral understanding with a very late feedback.

A multi-view architecting approach tackles the problem of integral understanding.
In combination with spiral or incremental development models a powerful method
becomes available for creating complex systems.