Hello BA community, Currently I am working on project related to web site integration. The requirement of the project is to integrated 3 different websites into one coherent system. There are 2 phases of the project 1) Must have requirements 2) Nice to have reequiremets I am almost done creating BRD for this project but still it needs some refinement from the business. My next task is to create a Functional Spec Document for the same. Since ther was no prior documentation for this project, I have to create it from the scratch. Can any one please help me out with the flow of Functional Spec for this particular project. I have not created a Functional Spec Doc before so not sure what information to include and what should be the flow of the document. Can any one please provide me the table of content for this particular project. Thanks in Advance.
Hello BA community,
Currently I am working on project related to web site integration.
The requirement of the project is to integrated 3 different websites into one coherent system.
There are 2 phases of the project 1) Must have requirements 2) Nice to have reequiremets
I am almost done creating BRD for this project but still it needs some refinement from the business.
My next task is to create a Functional Spec Document for the same. Since ther was no prior documentation for this project, I have to create it from the scratch.
Can any one please help me out with the flow of Functional Spec for this particular project. I have not created a Functional Spec Doc before so not sure what information to include and what should be the flow of the document.
Can any one please provide me the table of content for this particular project.
Thanks in Advance.
Hi:
I doubt if anyone is going to give you an intelligent answer to your question. Reason is that, dispite what you may have read, there is no need for both of the documents. BRD vs FRD came about because some people think that higher level business requirements need a different spec than do more concrete automated requirements. This is false; and having two specs only retards integration efforts.
Think Agile. Agile entails minimal, but quality requirements documentation. A few higher level data flow diagrams, showing all the manual and/or automated requirements within scope, some entity relationship diagrams, and maybe soome screen shots is alll the development staff typically really needs. The details they can handle in conversations. No need for detailed specifications, and certainly, no need for TWO detailed specs.
Tony
brought to you by enabling practitioners & organizations to achieve their goals using: