larimar,
BABOK 1.6 does make a distinction between business requirements and functional requirements. Version 2.0 does clarify this a little. We may consider that 'functional requirements' a subset of User Requirements and therefore a type of business requirement even though there is a slight distinction if you go by the text of the BABOK.
Everything a BA does focuses on the WHAT of the system. Here is my personal requirement breakdown. I have attached a PDF of an example traceability model which may help.
Business Requirements according to Perry McLeod
click here for my example : http://www.pjmlimited.com/downloads/RequirementsTraceabilityModel.ppt
Specifications according to Perry McLeod
I hope this is of help. Please see the attached models. I use them all the time to show how it all fits together.
Perry, my powerpoint says it needs a text converter or something to read this file - could you pdf it?
Thanks,
Guy
I think I was the first person to state that there is a difference between business and functional equirements (in this thread.)
Perry is right, all requirements should be servicing the business problem.
I believe I am right also; there is a heirarchy of requirements. Think of a Venn diagram with each layer sitting inside the one above. I have posted this image at the Better Projects blog (here) of you want to take a look.
Craig, I see where you're coming from and agree that all requirements should service the business problem, although I'm not sure I like the idea of a hierarchy of requirements from a clarity perspective. If a requirement can be several categories at once I think that can lead to confusion when discussing requirements with the business and operational stakeholders. From my interpretation of the V1.6 BABOK requirement definitions, each category is purposely distinct so that there is no confusion about what type of requirement a given statement is.
Again, I understand your viewpoint but think from a practical perspective it makes more sense to keep each category of requirements separate via their definitions.
Perry, thanks for your clarification and detailed response.
Guy,
http://www.pjmlimited.com/downloads/RequirementsTraceabilityModel.pdf
If you have any issues, let me know and I will email it to you. We need the ability to add attachments. Good issue for the Core members!
Could anybody please let me know where I can still download a PDF of BABOK V2.0?
I just started reading BABOK V1.6. Since everybody says V2.0 is a good improvement, I want to go directly from there and avoid some possible confusion.
Irene
brought to you by enabling practitioners & organizations to achieve their goals using: