Once completed the Business Analyst (BA) will hand this document over to a data designer or modeller who then has to understand what the list of fields or user stories mean and where to find them.
Or we will capture a set of high level user stories that are focused on the presentation of the data (i,e reports and dashboards) and pretty much ignores the data altogether. This is will typically have a list of fields required, plus a specification of layout and a bunch of functional and non-functional requirements. We will often capture our data requirements in a traditional application-centric requirements document which is used to document the requirements for a report or a dashboard. Let’s look at the way we typically capture data requirements. Second we need to document the requirements in a way the team delivering the data can understand, so they know what they need to build. There are two typical challenges when we gather data requirements.įirst, we need to capture and document the requirements in a way the person providing them understands, so they can review them and be confident you have understood what they need.
0 kommentar(er)
