XML Programming and Project Lifecycle

XML Programming
The Psychology of Computer Programming (ISBN: 0-442-20764-6) by Gerald Weinberg has an interesting account of a development project that mirrors many integration projects. On pages 72-74 is an account of how a wayward program in phase 2 of 7 caused problems that didn't show up until phase 5. How can you design an integration project so that you don't just blindly pass along problems, only to have them surface in some downstream component?
XML Project Lifecycle
XML IDEs have all suffered from the same problem — they let you design and debug the individual components, but never in situ. The typical project goes like this for the components — Edit >> Compile >> Debug >> Rinse and Repeat — but what does it do for the entire flow, the entire pipeline? Up until now, it's been Assemble >> Deploy, and wait for the crash.

---

Audi 100 Parts