I noticed that there were very few mentions and little elaboration on output/reports. Is this not a consideration with this project? Almost all of the larger projects I've worked on have core requirements in this area (whether in written or electronic form).

In the few instances where I've made design mistakes, they usually stemmed from the fact that I failed to examine the required output/reports closely enough or made wrong assumptions (though usually valid) based on experience. Recently I was given an example (publication) to work from and found out later in development that they had changed their example substantially without telling me. Thus the need for constant design/programmer/customer feedback throughout the life cycle of the project.

--Jim