Thanks Chris. One more question.... "Can a BRD and FSD exist together ? " What I mean is can you have a BRD and a FSD for the same project as 2 seperate docments? The reason I ask this is because in all the examples/ samples that I have seen till now the FSD and BRD have similar contents for eg the BRD has refrences to the use cases etc. It seems like the BRD has the FSD components as well. Its either the FSD or BRD in a project. But can these 2 documents exixst together as seperate documents in one project ?
It would be a grt help if you could attach some links to BRD and FSD.
Thanks in advance.
Zaineb
Zaineb,
Sorry for the late reply, I took some time off to get some sun and relaxation. My first true vacation in about 10 months....sorely needed.
It looks like others have given you some good feedback. Things vary sooo much from company to company. You will see BRDs and FSDs as one signel document or as separate docs depending on the project and company. What really matters is what you place in each document. Again, I would refer you to my first post. BRDs represent the "what" and "why" while FSDs state the "How" in logical terms.
Guys, Could you point me to standarts which describe BRD and FSD. It seems hand-made docs which were suggested by someone as workaround. To correct one at this topic I would like to underline there are 3 types of requirements: * Business * User * System
You're not correcting me are you Bas?
:)
I would correct you Craig
brought to you by enabling practitioners & organizations to achieve their goals using: