Data IS Executed Policy

Abstract

Data is executed policy in that data represents the "proof' that policies are executed. From that it follows that the data definitions systems employ, that is, database schemas, are really policy. definitions. And from that, it can be concluded that if a database's definition is incorrect or incomplete, then, in essence, the enterprise's policies do not exist. Or at least, enterprise policy executions cannot be proven. This paper, Data Is Executed Policy, shows via a case study that if the underlying database design and the attendant software system's infrastructure are not synchronized with the policy of the enterprise, then the enterprise operates at best in a suboptimal fashion. What is presented is the nature of the enterprise, the existing database and information system's environment and consequences of that incompletely specified environment. The paper then presents the work accomplished to complete both policy definition and the development of the business system to mirror enterprise policy. Because Clarion for Windows was employed, the complete requirements analysis and design through production system implementation was able to be accomplished in nine staff months, not counting data conversion and database administration activities. The key statistics of the effort are: 60 tables,240 "programs," and about 90K lines of code. PU - KLUWER ACADEMIC/PLENUM PUBL PI - NEW YORK PA - 233 SPRING ST, NEW YORK, NY 10013 USA