In our rather small shop, programmers have traditionally acted as business analysts as well, gathering business/functional requirements from users. Our data administrator (DA) creates a logical data model based on requirements, but then wishes to review the model and requirements with the business users. This seems redundant to me. Shouldn't the data administrator be able to glean data requirements from documented functional requirements rather than having to essentially re-interview the business folks? Also, does the logical model really need to be reviewed by the business area? Isn't this more of a dialog between the DA and developer to make sure that the developer can implement desired functionality based on the data modeled? We're having trouble deciding just who does what and when they do it in the development life cycle. We really want to avoid forcing the business folks to go over the same ground repeatedly and/or causing confusion
Joe Oates' Answer: Actually, it has been my experience that reviewing logical data models with business people is quite valuable. If a businessperson is willing to review a logical model, in almost all cases, the logical modeler learns something that did not come out in interviews.
Register or login for access to this item and much more
All Information Management content is archived after seven days.
Community members receive:
- All recent and archived articles
- Conference offers and updates
- A full menu of enewsletter options
- Web seminars, white papers, ebooks
Already have an account? Log In
Don't have an account? Register for Free Unlimited Access