Views are unnecessary in modeling
Opponent: Views may be useful. Since they can be defined on the basis of the schema we have no need to integrate view design into conceptual design.
Proponent: Often database applications are exclusively managed on the basis of views. Inserting, manipulating and deleting objects is allowed exclusively on the basis of views. Thus, views are made updateable. In this case, view design is essential whenever a database application must run efficiently. In this case, views need to be integrated.
Opponent: Yes, this observation is correct. But theoreticians have shown that vie integration is undecidable. Thus, we better develop schemata first and then views instead of developing views without a chance to integrate them.
Proponent: The better approach is to develop schemata and views together as we did in the codesign approach. Codesign of structuring and functionality allows to handle views and schemata at the same time. In this case we do not fall into the trap of undecidability and will be able to use views for user groups.
`Other related information you find in page':More readings