O'Reilly logo
  • vik.sharma@consultant.com thinks this is interesting:

Business requirements should be understood in detail. A common misconception is that business requirements are high level only.


Cover of Seven Steps to Mastering Business Analysis


Do you elicit business and functional requirements at the same time for example, while creating a use case keeping it at a business use case level and then revisiting the use case to add more details (system use case) to derive functional requirements?