How do you deal with the relationship between use case and functional requirements? do you repeat the system funciton in functional requiremetns section with more details or just leave the system functions in the use case description?

for example, in use case it says:
user selects account type
system presents a list of transactions

appreciate it if you could shed some light

Regards,
Simon

I am helping to document the system requirements for the addition of several new reports to our existing reporting system. Our organization has a formal document to capture the business, user, and system (functional & non-functional) requirements, however these requirements are text-only. We would like to document the screen mockups of the reports, each of the individual report filters and the queries they call to get the data that's populated in the filter, etc.

Researchers from the University of Munich (Germany) and the University of Graz (Austria) are conducting a study to understand the information needs during requirements and release management.

Your opinion is very important and would be much appreciated. Please spend 5-10 minutes to answer these questions

Independently from the answers, you can take part in the lottery of one iPod Touch among the participants.
Your answers are voluntary and data can only be used in aggregated form for research purposes. An open source tool will be developed based on the answers.

Thanks!