In relation to the SDLC, where the function of the whole system is the ultimate test of quality and fitness for purpose, it could be argued that both the as-is and to-be process models are merely reductionist representations of reality like pictures or photographs of a scene, and in isolation, only lead to systems that do not ever meet customer expectations. (i.e. since pictures and models are not the "real thing", the nature of any representative model is inherently flawed and imperfect to begin with)

Discuss this statement and how you might ensure that both 'to-be' software and process development overcome such model limitations to best meet business process and customer requirements. In your answer express your understanding of DFD's and process modelling and at what point you think the 'as-is' systems analysis and DFD process mapping should stop - while ensuring adequate information is gathered to deliver the 'tobe' system or process?