Gathering requirements is an art. Probably the most beneficial way of getting requirements is talking with end-users. There are really two schools of thought on interviews to elicit requirements. The first is to allow them to give you the Taj Mahal view of everything they want regardless of time and cost restraints. The second is to narrow the discussion to their job focus and what they need from the system to do their job. What are your thoughts on this process and how to make sure we get full coverage of the requirements for 'the system'?