Process for handover between Business Req to Functional Specs
I am working as a Business Analyst for an ISP.
Our IT Manager has decided that we need two teams of BA's. The first team of BA's will work in the Feasability stages of the project and the second team will work in the Design stage.
I have been asked to come up with a process for the handover from one BA to the next for working on a single project.
This would have one BA working on the Business Requirements document, and the new BA working on the Functional Specifications.
Can anyone out there share any ideas on things that should be done for a "Brain Dump" from one BA to the next?
[This message has been edited by kiwi-ba (edited 05-28-2001).]
Re: Process for handover between Business Req to Functional Specs
I see a Business Analyst as someone who knows how a business is run, such as management issues, economical issues, workflow issues etc.
That role in the software development process is very crucial in understanding the real needs of a customer, and may help the customer in approving their way of working.
I don't see how a business analysist fits in the process of a feasability study nor a design study. Where I work that are totaly different jobs.
The feasability study can only be done once the real requirements are known (gathered by the business analyst) and once the budget and timing is known.
A functional analyst looks for answers how to work out the functional requirements, in a pure functional way, no technical solutions are given at this stage.
A technical analyst will work out a technical design that is capable of handling the non-functional requirements and the functional solutions the functional analyst worked out.
A possible flow is the following :
1. requirements analysis by a business analyst
2. Functional design by a functional analyst
3. Technical design by a technical analyst
5. Unit testing, integration testing, system testing, acceptance testing.
What is necessary between stages are very descriptive documents that contain all the necessary information for the next phase.
Therefore we are looking to implement the Inspection process. This process validates documents before they pass to the next stage.
For more information about Inspection, I can recommend the book Software Inspection by Tom Gilb and Dorothy Graham (Addison Wesley).
Hope this helps.