It is generally accepted that use cases, specified in narrative form (also known as use case specifications), depict functional requirements. This is because a use case, via the main and alternate flows, shows how a user interacts with a system in order to achieve a desired result.
That's exactly the purpose of a "functional requirement" to describe the functions and behaviors that a system is or should be capable of.
Therefore, if use cases are used and narrated in detail for a project, there is no need for separate documentation to describe the functional requirements because the totality of all the use cases represent the set of functional requirements for a given system/project.
posted @ Thursday, May 1, 2008 11:41 PM by everest