I believe this is primarily a process or methodology question. It has to do with responsibilities of the data administrator on a software development project. 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. 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?
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