Principles of database and knowledge-base systems, Vol. I
Principles of database and knowledge-base systems, Vol. I
Conceptual database design: an Entity-relationship approach
Conceptual database design: an Entity-relationship approach
The engineering of knowledge-based systems: theory and practice
The engineering of knowledge-based systems: theory and practice
A first course in database systems
A first course in database systems
An analysis of the structural validity of ternary relationships in entity relationship modeling
Proceedings of the seventh international conference on Information and knowledge management
The entity-relationship model—toward a unified view of data
ACM Transactions on Database Systems (TODS) - Special issue: papers from the international conference on very large data bases: September 22–24, 1975, Framingham, MA
Improving database design through the analysis of relationships
ACM Transactions on Database Systems (TODS)
Applying UML and Patterns: An Introduction to Object-Oriented Analysis and Design and the Unified Process
PREPARE: A Tool for Knowledge Base Verification
IEEE Transactions on Knowledge and Data Engineering
| Hi-index | 0.00 |
This paper does a proposal, looking into certain delicate aspects of Unified Modelling Language (UML) and Unified Process (UP) usage, when applied to information systems. The usage of some tools and heuristics based on the gathered experience origined on the MERISE method evolution, gives place to comparative benefits while conceiving this type of informatic applications. The heuristic and tools used consists of starting from a higher level of abstraction provided with inverse engineering and re-engineering instrumentation methods. The knowledge of a minimal data schema enables a global vision and ensures, by means of certain verifications, reducing the number of modifications done to the initially built subsystems, assuring thus a better data integrity. Finally, the conceptual and organizational levels of treatment allows to evaluate organization solutions by comparison, yielding naturally into a usage manual and an analysis of the different actions taken by the different modules built with the given object's assemblies. This allows both the classical solution as well as the usage manual based one. We included some simplified examples to show the advantages of the proposed method.