Does Code Decay? Assessing the Evidence from Change Management Data
IEEE Transactions on Software Engineering
Accelerated business concept modeling: combining user interface design with object modeling
Object modeling and user interface design
Searle‘s Chinese Box: Debunking the Chinese Room Argument
Minds and Machines
Roles and Dynamic Subclasses: A Modal Logic Approach
ECOOP '94 Proceedings of the 8th European Conference on Object-Oriented Programming
A survey of approaches to automatic schema matching
The VLDB Journal — The International Journal on Very Large Data Bases
Adhocism in Software Architecture-Perspectives from Design Theory
SMT '00 Proceedings of the International Conference on software Methods and Tools (SMT'00)
Journal of the American Society for Information Science and Technology
Spinning the Semantic Web: Bringing the World Wide Web to Its Full Potential
Spinning the Semantic Web: Bringing the World Wide Web to Its Full Potential
Microformats: a pragmatic path to the semantic web
Proceedings of the 15th international conference on World Wide Web
Web Semantics: Science, Services and Agents on the World Wide Web
Measuring the understanding between two agents through concept similarity
Expert Systems with Applications: An International Journal
IEEE Transactions on Systems, Man, and Cybernetics, Part A: Systems and Humans
Hi-index | 0.00 |
Application interoperability and data exchange are desirable goals, but conventional system design practices make these goals difficult to achieve, since they create heterogeneous, incompatible conceptual structures. This conceptual incompatibility increases system development, maintenance and integration workloads unacceptably. Conceptual data independence (CDI) is proposed as a way of overcoming these problems. Under CDI, data is stored and exchanged in a form which is invariant with respect to conceptual structures; data corresponding to multiple schemas can co-exist within the same application without loss of integrity. The use of CDI to create domainindependent applications could reduce development and maintenance workloads and has potential implications for data exchange. Datasets can be merged without effort if stored in a conceptually-independent manner, provided that each implements common concepts. A suitable set of shared basic-level archetypal categories is outlined which can be implemented in domainindependent applications, avoiding the need for agreement about, and implementation of, complex ontologies.