this website is amazing
I was told to draft a business requirement spec for the data migration part of my project,
I am struggling with this. I am thinking a BRS is not appropriate, please prove me wrong
In my opinion, data migration project is data driven, I can only foresee one functional requirement in the project ie the target system shall update data from the source system.
can there be any other functional requirements?
under what category of non functional requirements can data load frequency be documented?
what should the structure of the BRS should b like?
should data requirements in d BRS be at column or entity level?
Your responses will be highly appreciated
I agree with what the other posters wrote, why does the business even care that there is a data migration. What are they trying to accomplish. However, given that there is a data migration focus on a mapping table that includes
1) the meaning of each individual data element (short description)
2) name of the element
3) the format of the element
4) the business rules associated with the data element (validation, calculation etc)
5) calculated or derived fields
6) a mapping to the new data model
7) stakeholders that own the data
If the data is more than a single object, it might be helpful to diagram the data structure using a Business Data Diagram
http://requirements.seilevel.com/blog/2009/08/rml%E2%84%A2-requirements-model-6-the-business-data-diagram-bdd.html
brought to you by enabling practitioners & organizations to achieve their goals using:
enabling practitioners & organizations to achieve their goals using: